Method, device and system for adjusting eviction procedures - Patents.com

Abstract

The present disclosure describes methods, systems, and devices for configuring signal resources to coordinate leaving procedures for one or more devices that include multiple subscriber identity modules (multi-SIM) or that connect one subscriber identity module (SIM) with multiple networks. One method includes configuring, by a user equipment (UE), leaving procedures for the multiple networks by determining, by the UE, an leaving type in response to a particular scenario, and coordinating the leaving procedures based on at least one of the leaving type or the particular scenario.

Description

[Technical field]

[0001] The present disclosure is directed generally to wireless communications. In particular, the present disclosure relates to methods, devices, and systems for coordinating leaving procedures for one or more devices that include multiple subscriber identity modules (multi-SIMs) or that connect multiple networks with one subscriber identity module (SIM). [Background technology]

[0002] Wireless communication technologies are moving the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and radio access network nodes (including, but not limited to, base stations). New generation networks are expected to provide high-speed, low-latency, and ultra-reliable communication capabilities to meet requirements from different industries and users.

[0003] For the fifth generation mobile communication technology, a user equipment (UE), e.g., a smartphone, may have multiple subscriber identity modules (multi-SIMs). The UE may register and connect to two or more network nodes, e.g., two or more radio access network (RAN) nodes and / or two or more core network (CN) nodes. The UE may connect to a first network. When the UE needs to connect to a second network, the UE needs to configure and / or coordinate the evacuation procedures for the first network and the second network to provide an efficient system for various scenarios. However, the details of the evacuation procedures and the configuration / coordination of the evacuation procedures between the UE and two or more networks remain unclear, which hinders an efficient wireless communication system.

[0004] The present disclosure may describe various embodiments relating to departure procedures and their configuration / adjustment that address at least some of the challenges / problems associated with existing systems and improve performance of wireless communications. Summary of the Invention [Means for solving the problem]

[0005] This document relates to a method, system, and device for wireless communication, and more particularly to a method, system, and device for coordinating an exit procedure for one or more devices including multiple subscriber identity modules (multi-SIM) or one or more devices connecting one subscriber identity module (SIM) with multiple networks. For one or more devices connecting one subscriber identity module (SIM) with multiple networks, it includes the following two scenarios: for a roaming UE, it may connect multiple networks for different slices, which may also require UE coordination among multiple networks; for video, imaging, and audio for specialized applications (VIAPA), it may require experimental means to enable the UE to simultaneously receive data services, paging, and data services from one network, which also requires UE coordination among multiple networks.

[0006] In one embodiment, the present disclosure describes a method for wireless communication that includes configuring, by a user equipment (UE), a leave procedure for a plurality of networks by determining, by the UE, a leave type in response to a particular scenario, and adjusting, by the UE, the leave procedure based on at least one of the leave type or the particular scenario.

[0007] In another embodiment, the present disclosure describes a method for wireless communication that includes receiving, by a Radio Access Network (RAN) node, a switch notification indicating an evacuation type or scenario, determining, by the RAN node, a switch configuration for the evacuation type or scenario, and transmitting, by the RAN node, a switch response to a user equipment (UE).

[0008] In another embodiment, the present disclosure describes a method for wireless communication, the method including receiving, by a RAN node, information of simple procedure instructions, and receiving, by the RAN node, information to avoid triggering a particular procedure.

[0009] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and processing circuitry in communication with the memory, the processing circuitry being configured, when the instructions are executed, to perform the methods described above.

[0010] In some other embodiments, a device for wireless communication may include a memory that stores instructions and processing circuitry in communication with the memory, the processing circuitry being configured, when the instructions are executed, to perform the methods described above.

[0011] In some other embodiments, a computer readable medium comprises instructions that, when executed by a computer, cause the computer to perform the above-described methods.

[0012] These and other aspects and their implementations are described in more detail in the drawings, description, and claims. The present invention provides, for example, the following: (Item 1) 1. A method for wireless communication, the method comprising: and configuring, by a user equipment (UE), a leave procedure for a plurality of networks, the leave procedure comprising: determining, by the UE, an exit type in response to a particular scenario; adjusting, by the UE, an evacuation procedure based on at least one of the evacuation type or the particular scenario; A method of doing something. (Item 2) The UE, Registering multiple subscriber identity modules (multi-SIMs) with the multiple networks; or Registering a subscriber identity module (SIM) with the plurality of networks 2. The method of claim 1, wherein the plurality of networks are registered by at least one of the following: (Item 3) The plurality of networks include: a plurality of Radio Access Networks (RANs) including a first RAN and a second RAN; A plurality of core networks (CNs), each of which comprises a first CN and a second CN; or RAN and CN Item 1, comprising at least one of the following: (Item 4) The withdrawal type is: a long-term leave type for a switch notification procedure that transitions the UE to an idle or inactive state with the first RAN; a periodic leave type for the switching notification procedure that keeps the UE in RRC_CONNECTED with the first RAN; or A one-time leave type for a switch notification procedure that keeps the UE in RRC_CONNECTED with the first RAN The method according to any one of items 1 to 3, comprising at least one of the following: (Item 5) 2. The method of claim 1, further comprising: determining, by the UE, a long-term absence type in response to a data service or a voice service. (Item 6) Determining the exit type in response to the particular scenario includes: The UE may receive the following scenarios: higher layer triggering control plane (CP) procedures, MO signaling, or Radio Resource Control (RRC) Triggered CP Procedure 2. The method of claim 1, further comprising determining whether to use a long-term or short-term departure type in response to at least one of the above. (Item 7) The upper layer trigger CP procedure comprises a registration procedure; the MO signaling comprises a Short Message Service (SMS); or 7. The method of claim 6, wherein the RRC triggered CP procedure comprises a routing area update (RAU). (Item 8) The higher layer comprises a UE Non-Access Stratum (NAS) layer; The lower layer comprises a UE Access Stratum (AS) layer; 8. The method according to claim 7, wherein the upper layer determines the leaving type and indicates the leaving type to the lower layer for the upper layer triggered CP procedure and the MO signaling. (Item 9) the higher layer sends an indication to the lower layer comprising a trigger reason and an expected duration; 9. The method according to claim 8, wherein the lower layer triggers the removal procedure according to the instruction. (Item 10) In response to determining the move-out type as a long-term move-out, 4. The method according to any of items 1-3, wherein the UE AS layer sends UE assistance information to the first RAN, whereby the first RAN decides whether to enter an inactive state or an idle state, and the UE assistance information comprises mobile terminated (MT) filter information. (Item 11) The UE is responsive to a periodic switching to determine an exit type as periodic exit, the periodic switching comprising: Synchronization signal block (SSB) detection, Paging opportunity (PO) reception, Serving cell measurement, Intra-frequency cell detection, Intra-frequency cell measurements, Inter-frequency cell detection, Inter-frequency cell measurements, Inter-Radio Access Technology (Inter-RAT) cell discovery, or Inter-RAT cell measurements The method according to any one of items 1 to 3, further comprising at least one of the following: (Item 12) The UE, Synchronization signal block (SSB) detection, Paging opportunity (PO) reception, Serving cell measurement, Intra-frequency cell detection, Intra-frequency cell measurements, Inter-frequency cell detection, Inter-frequency cell measurements, Inter-Radio Access Technology (Inter-RAT) cell discovery, or Inter-RAT cell measurements 12. The method of claim 11, wherein the first RAN is provided with one or more gap patterns for at least one of the first RAN and the second RAN. (Item 13) In response to the exit type being determined as periodic exit, sending, by the UE, a switch notification to the first RAN; receiving, by the UE, a configuration message from the first RAN; The method according to any one of items 1 to 3, further comprising: (Item 14) The switching notification is the method according to any one of items 13, comprising one or more gap patterns. (Item 15) The method according to any one of items 13, further comprising the configuration message comprising a configuration for one or more gap patterns. (Item 16) The one or more gap patterns comprise at least one set of a reference subcarrier spacing (SCS) for at least one gap pattern, a gap start time, a gap repetition period, a duration, and at least one of one or more gap purposes, the method according to items 12 - 13x2. (Item 17) The duration of the gap is a number of Ts, or a number of symbols and comprises at least one of them, the method according to item 16. (Item 18) The reference SCS is implicitly indicated by using the SCS of the initial bandwidth part (BWP) of the first RAN, the method according to item 17. (Item 19) The gap purpose is at least one of synchronization signal block (SSB) detection, paging opportunity (PO) reception serving cell measurement, intra - frequency cell detection, intra - frequency cell measurement, inter - frequency cell detection, inter - frequency cell measurement, radio access technology - to - radio access technology (RAT - to - RAT) cell detection, or RAT - to - RAT cell measurement and comprises at least one of them, the method according to item 16. (Item 20) The UE receives system information block type 1 (SIB1) or system information (SI) from at least one of neighboring cells or the serving cell, radio access network / core network (RAN / CN) paging response, upper layer trigger control plane (CP) procedure, MO signaling, radio resource control (RRC) trigger CP procedure, intra - frequency cell detection, intra - frequency cell measurement, inter - frequency cell detection, inter - frequency cell measurement, radio access technology - to - radio access technology (RAT - to - RAT) cell detection, or RAT - to - RAT cell measurement and determines the departure type as the one - time departure type in response to at least one of them, the method according to any one of items 1 - 4. (Item 21) Whether the upper layer trigger CP procedure comprises a registration procedure, Whether the MO signaling comprises a short message service (SMS), Whether the RRC trigger CP procedure comprises a routing area update (RAU), or Whether the RAN / CN paging response comprises a busy indication, the method according to item 20. (Item 22) In response to the exit type being determined as the one-time exit type, sending, by the UE, a switch notification to the first RAN; receiving, by the UE, a switching response from the first RAN; 21. The method of any of items 20, further comprising: (Item 23) The switching notification is RRC signaling with gapped mode, One-time eviction instruction, Duration of withdrawal, or Reason for leaving 23. The method of claim 22, further comprising at least one of the following: (Item 24) The UE is configured to: Measurements for cell reselection comprising at least one of intra-frequency detection, inter-frequency detection, or inter-radio access technology (inter-RAT) detection; receiving a system information block type 1 (SIB1) or system information (SI) from at least one of a neighbor cell or a serving cell; Radio Access Network / Core Network (RAN / CN) paging response, higher layer triggering control plane (CP) procedures, MO signaling, or Radio Resource Control (RRC) Triggered CP Procedure 24. The method of claim 23, further comprising indicating to the first RAN an exit trigger cause comprising at least one of: (Item 25) 23. The method of claim 22, wherein the switching response comprises RRC signaling involving a gapped mode. (Item 26) The gap mode is Long-term scheduling gaps, A gap with a time division multiplexing (TDM) pattern, or Autonomy Gap 26. The method according to claim 23, further comprising at least one of the following: (Item 27) In response to the gap mode being configured as a long term scheduling gap, The gap duration is equal to the exit duration, 26. The method of claim 25, wherein the UE avoids downlink (DL) and uplink (UL) reception during the gap duration. (Item 28) in response to the gap mode being determined as a gap with a TDM pattern, 26. The method of claim 25, wherein the UE periodically communicates a number of gaps with the second RAN during a short leave duration. (Item 29) the UE indicates a gap with the TDM pattern to the second network; Item 29. The method according to item 28. (Item 30) The TDM pattern is A bitmap for one or more subframes, A bitmap for one or more frames, or One or more indications regarding start time, duration, periodicity, and reference SCS 30. The method according to claim 28, further comprising at least one of the following: (Item 31) in response to the gap mode being determined as an autonomous gap, 26. The method of claim 25, wherein during a gap duration, the UE decides to communicate with the first RAN or the second RAN. (Item 32) The UE receives information of the gap mode from the first RAN; 31. The method of any of claims 22-30, wherein the UE vacates the first RAN based on the information of the gap mode. (Item 33) The UE, starting a timer upon receiving said gap mode configuration; stopping the timer when the procedure with the second network is completed; or when the timer expires, aborting the procedure on the second network and resuming it back on the first RAN. 33. The method of claim 32, further comprising using a timer to control the gap duration by at least one of: (Item 34) Item 34. The method of item 33, wherein the length of the timer is equal to a gap duration configured in the gap mode. (Item 35) The gap duration is broadcast in system information (SI), or 35. The method of claim 34, wherein the gap duration is configured by the RAN node through dedicated signaling. (Item 36) The gap duration is a gap duration for the long term scheduling gap; Gap duration for gaps involving a time division multiplexing (TDM) pattern, or Gap duration for autonomous gap 35. The method of claim 34, further comprising at least one of the following: (Item 37) 23. The method of claim 22, wherein in response to the UE not receiving any information of the gap mode from the first RAN, the UE implements a gap mode or remains connected to the first RAN. (Item 38) the UE notifies the second RAN that a short leave procedure occurs on the first RAN; or The UE, Mobility Procedures, Measurement procedure, Dual Connectivity (DC) related procedures, or Carrier Aggregation (CA) Related Procedures 23. The method of claim 22, further comprising: notifying the second RAN of an instruction to avoid at least one of the following: (Item 39) 1. A method for wireless communication, the method comprising: receiving, by a Radio Access Network (RAN) node, a switching notification indicating leaving assistance information; determining, by the RAN node, a switching configuration for a leaving configuration; sending, by the RAN node, a switching response to a user equipment (UE); A method comprising: (Item 40) 40. The method of claim 39, comprising receiving, by the RAN node, a switch notification or release indication from a core network (CN) and determining whether to enter an inactive state or an idle state. (Item 41) and receiving, by the RAN node, the switching notification from the UE, the switching notification comprising: Synchronization signal block (SSB) detection, Paging opportunity (PO) detection, Serving cell measurement, Intra-frequency cell detection, Intra-frequency cell measurements, Inter-frequency cell detection, Inter-frequency cell measurements, Inter-Radio Access Technology (Inter-RAT) cell discovery, or Inter-RAT cell measurements 40. The method of claim 39, further comprising one or more gap patterns for at least one of: (Item 42) 42. The method of claim 41, wherein the RAN node determines one or more gap reservations based on the one or more gap patterns. (Item 43) 40. The method of claim 39, wherein the RAN node transmits the switching response to the UE comprising one or more gap patterns. (Item 44) The one or more gap patterns include 44. The method according to any of items 41-43, comprising at least one set of a reference subcarrier spacing (SCS), a gap start time, a gap repetition period, and a duration for at least one gap pattern. (Item 45) The gap purpose is Synchronization signal block (SSB) detection, Paging Opportunity (PO) Reception Serving cell measurement, Intra-frequency cell detection, Intra-frequency cell measurements, Inter-frequency cell detection, Inter-frequency cell measurements, Inter-Radio Access Technology (Inter-RAT) cell discovery, or Inter-RAT cell measurements 45. The method according to claim 44, comprising at least one of the following: (Item 46) The duration of the gap is The number of T's, or Number of symbols 45. The method of claim 44, further comprising at least one of the following: (Item 47) Item 45. The method of item 44, wherein in response to not receiving an SCS, the RAN node uses an SCS in an initial bandwidth portion (BWP). (Item 48) RRC signaling with gapped mode, One-time eviction instruction, Duration of withdrawal, or Reason for leaving 40. The method of claim 39, wherein the switch notification comprises at least one of: (Item 49) The reasons for eviction are the following scenarios: Measurements for cell reselection comprising at least one of intra-frequency detection, inter-frequency detection, or inter-radio access technology (inter-RAT) detection; receiving a system information block type 1 (SIB1) or system information (SI) from at least one of a neighbor cell or a serving cell; Radio Access Network / Core Network (RAN / CN) paging response, higher layer triggering control plane (CP) procedures, MO signaling, or Radio Resource Control (RRC) Triggered CP Procedure Item 49. The method of item 48, comprising at least one of the following: (Item 50) 40. The method of claim 39, wherein the switching response comprises RRC signaling involving gapped mode. (Item 51) The gap mode is Long-term scheduling gaps, A gap with a time division multiplexing (TDM) pattern, or Autonomy Gap 51. The method according to any one of items 48-50, further comprising at least one of the following: (Item 52) In response to the gap mode being determined as a long term scheduling gap, The gap duration is equal to the exit duration, 52. The method of claim 51, wherein the RAN node avoids downlink (DL) and uplink (UL) scheduling during the gap duration. (Item 53) 52. The method of claim 51, wherein in response to the gap mode being determined as a gap with a TDM pattern, the RAN node periodically reserves a number of gaps for a short leave duration. (Item 54) 54. The method of claim 53, wherein the RAN node avoids the DL and UL scheduling in the reserved periodic gaps during a short leave duration. (Item 55) 52. The method of claim 51, wherein the RAN node determines the TDM pattern based on a recommendation from the UE, an ongoing service, or a radio environment. (Item 56) A gap duration for a gap mode with said TDM pattern is broadcast in system information (SI); or a gap duration for a gap mode with said TDM pattern being configurable through dedicated signaling; 52. The method of claim 51, further comprising: (Item 57) The TDM pattern is A bitmap for one or more subframes, A bitmap for one or more frames, or One or more indications regarding start time, duration, periodicity, and reference SCS 57. The method according to any one of items 53-56, comprising at least one of the following: (Item 58) in response to the gap mode being determined as an autonomous gap, 52. The method of claim 51, wherein the RAN node indicates the autonomous gap mode to the UE. (Item 59) The gap duration is broadcast in system information (SI), or 52. The method of claim 51, wherein the gap duration is configured by the RAN node through dedicated signaling. (Item 60) The gap duration is a gap duration for the long term scheduling gap; Gap duration for gaps involving a time division multiplexing (TDM) pattern, or Gap duration for autonomous gap 60. The method of claim 59, comprising at least one of the following: (Item 61) The RAN node, starting the timer upon sending the gap mode configuration or upon receiving a confirmation from the UE; stopping the timer when a procedure involving receiving a return from the UE indicates that the timer has been stopped; reinstating said scheduling when said timer is stopped or expires. 52. The method of claim 51, further comprising using a timer to control the gap duration by at least one of the following: (Item 62) The length of the timer is equal to the gap duration configured for each gap mode. Item 62. The method according to item 61. (Item 63) The RAN node, One or more ongoing service types, or Quality of Service (QoS) for one or more Protocol Data Unit (PDU) sessions, 52. The method of claim 51, wherein the gap mode is determined based on at least one of the following: (Item 64) 40. The method of claim 39, wherein the first RAN rejects a switch notification from the UE without allocating any gap. (Item 65) 1. A method for wireless communication, the method comprising: receiving, by the RAN node, simple procedure instruction information; and avoiding triggering a specific procedure upon receipt of said information by said RAN node. A method comprising: (Item 66) Item 66. The method of item 65, wherein the simple procedure indication informs the RAN node that a short leave procedure is occurring on another network or an indication to indicate that the particular procedure should be avoided. (Item 67) The specific procedure is: Mobility Procedures, Measurement procedure, Dual Connectivity (DC) related procedures, or Carrier Aggregation (CA) Related Procedures 67. The method according to any one of items 65-66, comprising at least one of the following: (Item 68) The mobility procedure comprises: A handover procedure, or Redirect Procedure Item 68. The method of item 67, comprising at least one of the following: (Item 69) Item 68. The method according to item 67, wherein the measurement procedure comprises a measurement configuration with any purpose. (Item 70) The DC-related procedure includes: Add sequence number (SN), SN correction, or SN release Item 68. The method of item 67, comprising at least one of the following: (Item 71) The CA-related procedure is: Add secondary cell (SCell), SCell modification, or SCell release Item 68. The method of item 67, comprising at least one of the following: (Item 72) Item 66. The method of item 65, wherein the RAN node receives the information from the UE through RRC signaling. (Item 73) The RRC signaling includes: Msg 5 with the RRCSetupComplete or RRCResumeComplete message, or Msg 3 with one or more probabilistic causes 73. The method of claim 72, further comprising at least one of the following: (Item 74) The cause is, the UE and the first RAN; the UE and a core network (CN) node; the first RAN and the CN node; the second RAN and the CN node; or The first RAN and the second RAN Item 74. The method of any of items 1-73, further comprising: indicating multi-SIM or multiple network connections between at least one of the SIM cards. (Item 75) A wireless communication device comprising a processor and a memory, the processor configured to read code from the memory and implement a method according to any one of claims 1-74. (Item 76) A computer program product comprising computer readable program medium code stored thereon, the computer readable program medium code, when executed by a processor, causing the processor to implement a method according to any one of items 1-74. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates an example of a wireless communication system including two or more network nodes and one or more user equipment.

[0014] [Diagram 2] FIG. 2 shows an example of a network node.

[0015] [Diagram 3] FIG. 3 illustrates an example of a user equipment.

[0016] [Figure 4] FIG. 4 illustrates a flow diagram of a method for wireless communication.

[0017] [Diagram 5] FIG. 5 illustrates a flow diagram of a method for wireless communication.

[0018] [Figure 6] FIG. 6 illustrates a flow diagram of a method for wireless communication.

[0019] [Figure 7]FIG. 7 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0020] [Figure 8] FIG. 8 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0021] [Figure 9] FIG. 9 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0022] [Figure 10] FIG. 10 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0023] [Figure 11] FIG. 11 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0024] [Figure 12] FIG. 12 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0025] [Figure 13] FIG. 13 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0026] [Figure 14] FIG. 14 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0027] [Figure 15] FIG. 15 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0028] [Figure 16] FIG. 16 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0029] [Figure 17] FIG. 17 shows a schematic diagram of an exemplary embodiment for wireless communication.

[0030] [Figure 18] FIG. 18 shows a schematic diagram of an exemplary embodiment for wireless communication. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0031] The present disclosure will now be described in detail hereinafter with reference to the accompanying drawings, which form a part hereof and which show, by way of illustration, specific examples of embodiments. It should be noted, however, that the present disclosure may be embodied in a variety of different forms, and thus, the subject matter directed or claimed is not intended to be construed as limited to any of the embodiments that will be described below.

[0032] Throughout this specification and claims, terms may have subtle meanings that are suggested or implied in the context beyond those explicitly stated. Similarly, the phrases "in one embodiment" or "in some embodiments" as used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" as used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" as used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" as used herein do not necessarily refer to different implementations. For example, it is intended that the claimed subject matter includes a combination of example embodiments or implementations, whether in whole or in part.

[0033] Generally, terminology may be understood, at least in part, from usage in context. For example, terms such as "and," "or," or "and / or" as used herein may include various meanings that may depend, at least in part, on the context in which such terms are used. Typically, "or," when used to relate a list such as A, B, or C, is intended to mean A, B, and C, which are used herein in an inclusive sense, and A, B, or C, which are used herein in an exclusive sense. In addition, the terms "one or more" or "at least one" as used herein may be used, at least in part, to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense, depending at least in part on the context. Similarly, again, terms such as "a," "an," or "the" may be understood to convey a singular use or to convey a plural use, depending at least in part on the context. In addition, the terms "based on" or "determined by" may be understood as not necessarily intended to convey an exclusive set of factors, but instead may allow for the existence of additional factors not necessarily explicitly described, again depending at least in part on the context.

[0034] The present disclosure describes methods and devices for coordinating exit procedures for one or more devices that include multiple subscriber identity modules (multi-SIMs).

[0035] New generation (NG) mobile communication systems are moving the world towards an increasingly connected and networked society. High speed and low latency wireless communication relies on efficient network resource management and allocation between user equipment and radio access network nodes (including but not limited to radio base stations). It is expected that new generation networks will provide high speed, low latency, and ultra-reliable communication capabilities to meet requirements from different industries and users.

[0036] This disclosure describes various embodiments for transmitting initial access information to user equipment. Figure 1 shows a wireless communication system 100 including two or more radio network nodes (118 and 119) and one or more user equipments (UEs) (110, 111, and 112).

[0037] With respect to the fifth generation mobile communication technology, the UE 110, e.g., a smartphone, may have a single subscriber identity module (SIM) or multiple subscriber identity modules (multi-SIM). When the UE has a single SIM, the UE may connect to one network node 118, e.g., a radio access network (RAN) node and / or a core network (CN) node, or may connect to two or more network nodes (118 and 119), e.g., two RAN nodes and / or two CN nodes. When the UE has a multi-SIM, the UE may connect to two or more network nodes (118 and 119), e.g., two RAN nodes, two CN nodes, and / or one RAN node and one CN node.

[0038] The radio network nodes (118 and 119) may include network base stations, which may be NodeBs (NBs, e.g., gNBs) in a mobile communication context. Each of the UEs (110, 111, and / or 112) may wirelessly communicate with the radio network nodes (118 and / or 119) via one or more radio channels 115. For example, a first UE 110 may wirelessly communicate with a first network node 118 during a period of time via a channel that includes multiple radio channels, and during another period of time, the first UE 110 may wirelessly communicate with a second network node 119 via a channel that includes multiple radio channels.

[0039] When a UE has a multi-SIM, the UE can be referred to as a multi-SIM device. A UE with a multi-SIM can register in two or more networks. For example, the first SIM (USIM1) of the UE registers in network A (the first network), and the second SIM (USIM2) of the UE registers in network B (the second network). When USIM1 is in a connected state with network A and the UE decides to perform an operation on network B, the UE needs to make an adjustment with network A. In various embodiments, "a certain operation on network B" can include several scenarios, for example, but not limited to, the following scenarios.

[0040] The first scenario may include periodic switching that includes at least one of paging reception or serving cell measurement. In one implementation, the scenario may include at least one of the following: synchronization signal block (SSB) detection, and / or paging opportunity (PO) reception.

[0041] The second scenario may include measurements for cell reselection that include at least one of intra-frequency detection, inter-frequency detection, or radio access technology (RAT) - to - RAT detection. In one implementation, the scenario may include at least one of the following: serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, RAT - to - RAT cell detection, or RAT - to - RAT cell measurement.

[0042] The third scenario may include receiving system information block type 1 (SIB1) or system information (SI) from at least one of neighboring cells or serving cells.

[0043] The fourth scenario may include at least one of an upper layer triggered control plane (CP) procedure, a mobile originated (MO) signaling, or a radio resource control (RRC) triggered CP procedure. In one implementation, the upper layer triggered CP procedure includes a registration procedure, the MO signaling includes a short message service (SMS), or the RRC triggered CP procedure includes a routing area update (RAU).

[0044] A fifth scenario may include a Radio Access Network / Core Network (RAN / CN) paging response. In one implementation, the RAN / CN paging response includes a busy indication.

[0045] A sixth scenario may involve MO data / call services.

[0046] This disclosure describes various embodiments for coordinating an exit procedure for at least one scenario, including, but not limited to, multiple scenarios as discussed above. This disclosure describes methods, systems, and storage media that classify at least one scenario into different exit types and implement detailed exit procedures for the different exit types.

[0047] 2 illustrates an example of an electronic device 200 for implementing a network node or a network base station. The exemplary electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with UEs and / or other base stations. The electronic device 200 may also include network interface circuitry 209 (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols) for allowing the base station to communicate with other base stations and / or a core network. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communicating with an operator, etc.

[0048] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of processors 221 to perform functions of a network node. Parameters 228 may include parameters to support execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0049] FIG. 3 illustrates an example of an electronic device for implementing a terminal device 300 (e.g., user equipment (UE)). The UE 300 may be a mobile device, e.g., a smartphone or a mobile communication module disposed in a vehicle. The UE 300 may include a communication interface 302, system circuitry 304, an input / output interface (I / O) 306, display circuitry 308, and storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuitry 304 may be implemented, for example, with one or more systems on chips (SoCs), application specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be part of an implementation of any desired functionality in the UE 300. In that regard, system circuitry 304 may include logic to facilitate: by way of example, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; launching applications; receiving user input; storing and retrieving application data; establishing, maintaining, and terminating cellular calls or data connections (for Internet connections, by way of example only); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying associated information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include graphical user interfaces, touch-sensitive displays, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements.Additional examples of I / O interface 306 may include microphones, video, still cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0050] 3, the communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 that handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuitry, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, wave shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and coding. As one specific example, the communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below are also applicable to other wireless communication technologies, whether arising from Third Generation Partnership (3GPP), GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

[0051] 3, the system circuitry 304 may include one or more processors 321 and memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to perform desired functionality for the UE 300. The parameters 328 may provide and define configuration and operation options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will transmit or is receiving through the communication interface 302. In various implementations, system power for the UE 300 may be supplied by a power storage device, such as a battery or a converter.

[0052] The present disclosure describes several following embodiments, which may be implemented partially or fully on the network base stations and / or user equipment described above in FIGS. 2-3.

[0053] 4, the present disclosure describes an embodiment of a method 400 for configuring, by a user equipment (UE), an evacuation procedure for multiple networks. The method 400 may include some or all of the following steps: step 410: determining, by the UE, an evacuation type in response to a particular scenario; step 420: adjusting, by the UE, the evacuation procedure based on at least one of the evacuation type or the particular scenario.

[0054] 5, the present disclosure describes an embodiment of a method 500 for configuring an evacuation procedure by a radio access network (RAN) node. The method 500 may include some or all of the following steps: step 510: receiving, by the RAN node, a switch notification indicating evacuation assistance information; step 520: determining, by the RAN node, a switch configuration for the evacuation configuration; step 530: sending, by the RAN node, a switch response to a user equipment (UE).

[0055] 6, the present disclosure describes an embodiment of a method 600 for configuring an evacuation procedure by a Radio Access Network (RAN) node. The method 600 may include some or all of the following steps: step 610: receiving, by the RAN node, information of a simple procedure instruction; step 620: receiving, by the RAN node, information to avoid triggering a specific procedure.

[0056] In various embodiments, the UE registers with multiple networks by at least one of the following: registering multiple networks with multiple subscriber identity modules (multi-SIM); or registering multiple networks with one subscriber identity module (SIM).

[0057] In various embodiments, the multiple networks comprise at least one of the following: multiple Radio Access Networks (RANs) comprising a first RAN and a second RAN; multiple Core Networks (CNs) comprising a first CN and a second CN; or a RAN and a CN.

[0058] In various embodiments, the eviction type may include one of two types: a long eviction type and a short eviction type. In one implementation, for the long eviction type, the UE may enter an idle / inactive state in network A (first network) and enter a connected state in network B (second network); for the short eviction type, the UE may stay in a connected state. In another implementation, the short eviction type may include a periodic eviction type and a one-time eviction type.

[0059] In various embodiments, the leaving type includes at least one of the following: a long-term leaving type for a switching notification procedure that transitions the UE to an idle or inactive state with the first RAN; a periodic leaving type for a switching notification procedure that keeps the UE RRC_CONNECTED with the first RAN; a one-time leaving type for a switching notification procedure that keeps the UE RRC_CONNECTED with the first RAN.

[0060] In various embodiments, a cause may be added to indicate a multi-SIM or multiple network connection between at least one of the following: a UE and a first RAN; a UE and a core network (CN) node; a first RAN and a CN node; a second RAN and a CN node; or a first RAN and a second RAN. (Determining the type of move-out)

[0061] In various embodiments, the first, second, third, and fifth scenarios discussed above may be determined as short-term exit types, and the sixth scenario may be determined as a long-term exit type. The fourth scenario may be determined as a long-term or short-term exit type depending on other factors.

[0062] In one implementation, the second network may not specify the situation in the fourth scenario as a long-term leave trigger condition, and thus it is left to the UE to implement whether it is a long-term leave type or a short-term leave type.

[0063] In another implementation, the second network may define some or all of the conditions in the fourth scenario as long-term or short-term exit types, for example, as short-term one-time exit trigger conditions.

[0064] For the triggering event in the fourth scenario, the time delay may be different. For example, but not limited to, the registration procedure may be triggered by a parameter change or by moving to a new Tracking Area Identification (TAI). For a parameter change, the registration procedure may not involve an Access and Mobility Management Function (AMF) change, but for a move to a new TAI, an AMF change may be involved. Furthermore, this may also be determined by the ongoing serving type, and for the case where only non-guaranteed bit rate (non-GBR) bearers are present, the UE may adopt a long-term leave procedure, or else a short-term leave procedure to keep the connection as long as possible.

[0065] In various embodiments as shown in FIG. 7, in the fourth scenario, for the higher layer (e.g., UE NAS layer 710) triggering CP plane procedures (e.g., registration, other MO signaling (e.g., SMS)), the higher layer may determine the leave type and indicate the leave type to the UE lower layer (e.g., UE AS 720) in step 751. In one implementation, the UE higher layer may also indicate the trigger reason and / or expected duration. In another implementation, the UE lower layer may trigger the leave procedure according to the higher layer indication in step 752. (Long-term Retreat Type Procedure)

[0066] In various embodiments, a long-term switch procedure for a long-term absence type may be used for the switch notification procedure, which transitions the UE to an idle or inactive state in network A (first network) after sending a switch notification to network A. In one implementation, the idle or inactive state may be indicated using RRC_IDLE or RRC_INACTIVE.

[0067] In various embodiments, certain auxiliary information for mobile terminated (MT) restrictions may include at least one of the following: information to temporarily restrict / filter MT data / signaling handling; an indication that the UE should be paged for voice only (MMTel voice (for EPS) or CS domain voice), an indication that the UE should not be paged at all, or a packet data network (PDN) connection for MT notification / paging restrictions.

[0068] For long term abandonment, the UE may enter an idle / inactive state and this auxiliary information shall be transmitted to the network, therefore it is more preferable to employ NAS signaling for long term abandonment procedures.

[0069] FIG. 8 illustrates an example of a NAS signaling-based long-term leaving procedure. Referring to step 851, the UE 810 sends a service request to the AMF 830, for example, including MUSIM MT filter assistance information and a leaving instruction. In step 852, the AMF sends an N2 message to the NG-RAN 820, including MUSIM MT filter assistance information indicating service approval. In step 853, the NG-RAN decides whether to enter an inactive / idle state. Optionally, in step 854, the NG-RAN indicates its service approval to the UE. In step 855, the NG-RAN sends a radio resource control (RRC) signaling to the UE to indicate the idle / inactive state. Optionally, in step 856.1, the NG-RAN sends a UE context release request to the AMF. In step 856.2, the NG-RAN proceeds to an inactive state and RAN filter paging according to the assistance information. In step 856.1a, the AMF proceeds to idle state and CN filter paging according to the assistance information.

[0070] Another issue concerns whether the UE needs to indicate a preferred state: if NAS signaling would be employed, the network could distinguish between long-term and short-term leave, and it would be up to the network to decide the idle / inactive state, and therefore there would be no need to indicate a preferred state.

[0071] FIG. 9 shows an example of an AS signaling-based long-term leave procedure. Referring to step 951, the UE NAS 910 sends MT filter assistance information to the UE AS 920. In step 952, the UE AS sends UE assistance information with the MT filter information to the NG-RAN 930. In step 953, the NG-RAN decides whether to enter an inactive / idle state. In step 954, the NG-RAN sends an RRCConnection release to the UE AS. In step 955.1, the NG-RAN sends a UE context release request with the MT filter assistance information to the AMF 940. In step 955.2, the NG-RAN proceeds to an inactive state according to the RAN filter paging according to the assistance information. In step 955.1a, the AMF proceeds to an idle state using CN filter paging according to the assistance information. (Short-term move-out types: Periodic short-term move-outs and one-time short-term move-outs)

[0072] In various embodiments, the short leave type may include a periodic leave type and a one-time leave type. In one implementation, the periodic leave type includes a switch notification procedure that keeps the UE in RRC_CONNECTED with the first network, and the one-time leave type includes a switch notification procedure that keeps the UE in RRC_CONNECTED with the first network. In another implementation, the short switch procedure may be used for a switch notification procedure that keeps the UE in RRC_CONNECTED in network A (the first network) after sending a switch notification to network A.

[0073] In various embodiments, the third, fourth, and fifth scenarios discussed above may be determined to belong to a one-time leave type, and the paging detection in the first scenario may be determined to belong to a periodic leave type.

[0074] In one implementation, with regard to serving cell measurements in the first scenario, the UE may measure the SS-RSRP and SS-RSRQ levels of the serving cell and evaluate the cell selection criterion S for the serving cell at least once every M1×N1 DRX cycles, where M1=2 if SMTC periodicity (TSMTC)>20 milliseconds (ms) and DRX cycle≦0.64 seconds, and M1=1 otherwise.

[0075] In another implementation, the UE may use at least two measurements to filter the serving cell's SS-RSRP and SS-RSRQ measurements, where in the set of measurements used for filtering, the at least two measurements shall be spaced at least DRX cycle / 2 apart.

[0076] In another implementation, the measurement for the serving cell may also be considered as a periodic event, and therefore periodic leaving may also be required. Thus, the measurement for the serving cell in the first scenario may also be considered as a periodic event, and periodic leaving may also be required.

[0077] In various embodiments, the second scenario discussed above may be determined to belong to a periodic or one-time leaving type. According to the reselection requirements, it may have a periodic attribute. For example, for intra-frequency reselection, if the serving cell is within the range of Srxlev≦S IntraSearchP Or Squal≦S IntraSearch If T is satisfied, the UE may perform intra-frequency measurements according to the following requirements: When the UE detects a newly detectable intra-frequency cell with T detect,NR_IntraThe UE may be able to evaluate whether the intra-frequency cell identified and measured in accordance with the measurement rules satisfies the reselection criteria in at least T measure,NR_Intra SS-RSRP and SS-RSRQ can be measured every 10 minutes (see Table 1). [Table 1]

[0078] Based on Table 1, for intra-frequency measurement, during a DRX cycle, the UE may first detect the SSB to synchronize to and then detect paging, and after paging detection, the UE may perform detection, or measurement, or both. The detection / measurement gap may or may not be adjacent to the PO, depending on the intra-frequency SMTC.

[0079] 10 shows an example for a periodic gap pattern. For example, but not by way of limitation, the DRX cycle may be adopted as 0.32 seconds for FR1, and the UE may require the following gaps: T1 = DRX cycle (length = SSB detect (optional) + PO) (1010); T2 = 36 DRX cycles (length = SSB detect (optional) + PO + in-frequency detect) (1020); and T3 = 4 DRX cycles (length = SSB detect (optional) + PO + measurement) (1030).

[0080] In one implementation, the one or more gap patterns may include at least one set of a reference subcarrier spacing (SCS), a gap start time, a gap repetition period, a duration, one or more gap purposes for the at least one gap pattern. The gap duration may include at least one of the following: a number of T, or a number of symbols. The reference SCS may be implicitly indicated by using the SCS of the initial bandwidth part (BWP) of the first network.

[0081] In various embodiments, inter-frequency and inter-RAT measurements may be similar to intra-frequency and detection / measurements may also require periodic gaps. In one implementation, intra-frequency, inter-frequency and inter-RAT detection / measurements may also require periodic gaps.

[0082] In various embodiments, it may also belong to the UE implementation. When adopting the measurement for cell reselection as one short-term event, the UE may need to frequently coordinate the leaving with network A, which will seriously affect the performance of network A.

[0083] In various embodiments, the UE may indicate one or more gap patterns with one or more objectives to the network. In one implementation, the objectives may include at least one of the following: SSB detection, PO detection, serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, inter-RAT cell detection, and inter-RAT cell measurement.

[0084] In various embodiments, the network may receive one or more gap patterns with one or more objectives from the UE. In one implementation, the objectives may include at least one of the following: SSB detection, PO detection, serving cell measurement, intra-frequency cell detection, intra-frequency cell measurement, inter-frequency cell detection, inter-frequency cell measurement, inter-RAT cell detection, and inter-RAT cell measurement. In another implementation, the network decides or does not decide gap reservation according to the objective. (Periodic short-term departure type (or periodic departure type))

[0085] 11 shows an example of a periodic leaving procedure. In step 1151, the UE 1110 sends a switch notification indicating a short period of time to network A (first network, 1120). In step 1152, network A sends an RRCReconfiguration message to the UE. In step 1153, the UE sends an RRCReconfigurationComplete to network A.

[0086] In various embodiments for the first scenario discussed above, including paging reception and serving cell measurements, the paging-related parameters for indicating the gap may include at least one of the following: an indication of the need for a gap (e.g., the UE may need a gap or may disable the need for a gap (e.g., if the other SIM is disabled)); a gap pattern requirement (e.g., gap start time, gap repetition period, etc.); and / or a gap length.

[0087] In one implementation, the gap length may be calculated using T or the number of symbols. When the number of symbols is used, the SCS of the initial BWP of network A may be adopted.

[0088] Figure 12 shows an example of cyclic gap duration. The UE may map the cyclic gap pattern of network B (second network 1220) to network A (first network 1210). For example, the parameter set with (start FN, SFN, symbols, duration) may be (x, 2, n, 2) instead of (y, 0, m, 4).

[0089] In various embodiments, for each gap pattern, the UE may indicate a gap duration, a gap start time, a gap repetition period, and a reference SCS. In one implementation, the gap duration may be a number of T or a number of symbols. In another implementation, in terms of a number of symbols, the SCS of the initial BWP of the current network may be adopted as the reference SCS. In another implementation, the current network may refer to the network to which the UE will transmit the gap information.

[0090] In various embodiments, the network may receive the duration of each gap and make scheduling decisions based on the duration and the SCS of the initial BWP or the reference SCS indicated by the UE.

[0091] For example, the Asn.1 coding for one or more gap patterns with one or more objectives may be expressed as follows: [Table 2]

[0092] where startSFN may refer to the starting subframe number of the periodic gap, which is based on the timing of the cell that will reserve the periodic gap; startSFN may refer to the starting frame number of the gap, which is based on the timing of the cell that will reserve the periodic gap; subcarrierSpacing may refer to the reference SCS of the periodic gap, and if not included, the SCS of the initial BWP of the cell reserving the periodic gap will be taken as the reference SCS; startSymbol may refer to the starting symbol of the periodic gap, which is based on the timing of the cell that will reserve the periodic gap; duration may refer to the duration in symbols of the periodic gap; period may refer to the period of the periodic gap. (One-time move-out type)

[0093] In various embodiments, the second, third, fourth, and fifth scenarios discussed above may trigger a one-time exit type procedure.

[0094] 13 shows an example of a one-time leaving procedure. In step 1351, the UE 1310 sends a switch notification to network A (first network, 1320) indicating a one-time short period of time. In step 1352, network A sends a switch response to the UE. In step 1353, the UE sends a return message to network A.

[0095] In one implementation, the switch response includes RRC signaling with gapped mode.

[0096] In another implementation, the gap mode includes at least one of the following: a long-term scheduling gap; a gap with a time division multiplexing (TDM) pattern; or an autonomous gap.

[0097] In another implementation, in response to the gap mode being configured as a long-term scheduling gap, the gap duration is equal to the leave duration and the UE avoids downlink (DL) and uplink (UL) reception during the gap duration.

[0098] In another implementation, in response to the gap mode being determined as gap with TDM pattern, the UE communicates multiple gaps with the second RAN periodically during the short leave duration.

[0099] In another implementation, the UE indicates a gap with a TDM pattern to the second network.

[0100] In another implementation, the TDM pattern includes at least one of the following: a bitmap for one or more subframes; a bitmap for one or more frames; or one or more indications regarding start time, duration, periodicity, and reference SCS.

[0101] In another implementation, in response to the gap mode being determined as autonomous gap, the UE determines to communicate with the first RAN or the second RAN during the gap duration.

[0102] In various embodiments, the UE receives gap mode information from the first RAN, and the UE exits the first RAN based on the gap mode information. In one implementation, the UE uses a timer and controls the gap duration by at least one of the following: starting the timer when receiving a gap mode configuration; stopping the timer when the procedure with the second network is completed; or aborting the procedure on the second network and resuming back to the first RAN when the timer expires. In another implementation, the length of the timer is equal to the gap duration configured in the gap mode.

[0103] FIG. 14 shows an example for a long-term scheduling gap (or long-term scheduled gap). Network A 1410 is a first network and Network B 1420 is a second network. The gap length may be equal to the short-term leave duration, and during the gap, the network may avoid both DL and UL scheduling. In one implementation, for a dual Rx UE, it may adopt reduced Rx capacity for DL ​​scheduling, for example, for the second and third scenarios, as discussed above. This mode may impact the UE experience, considering that both DL and UL cannot be scheduled and that the one-time procedure may take tens of milliseconds.

[0104] FIG. 15 shows an example of a gap with a TDM pattern. Network A 1510 is a first network and network B 1520 is a second network. A scheduled gap with a TDM pattern may be similar to a measurement gap, where network A may reserve some gaps periodically during the leave duration. In one implementation, the UE may inform the network of a preferred TDM pattern as assistance information. In another implementation, the UE needs to provide sufficient assistance information for network A to determine the TDM pattern during the scheduled gap.

[0105] 16 shows an example of an autonomous gap. Network A 1610 is a first network and network B 1620 is a second network. For an autonomous gap, it is left to the UE to implement a method to communicate with the two networks (1610 and 1620) during the gap, similar to a conventional MUSIM UE. In one implementation, during the autonomous gap, the UE may remain in a temporary short-term dual active state by a TDM method.

[0106] Referring to Figure 17, in step 1751, the UE 1710 sends a one-time leave instruction to the NG-RAN 1720. The one-time leave instruction may include at least one of a leave cause or a leave duration. In step 1752, the NG-RAN determines a preferred gap mode. In step 1753, the NG-RAN sends RRC signaling with the preferred gap mode. Optionally, in step 1754, the UE sends a response message to the NG-RAN.

[0107] In various embodiments, the network may indicate a gap mode to the UE for leaving.

[0108] In one implementation, the gap mode may be a long-term scheduling gap, a gap with a TDM mode, or an autonomous gap.

[0109] In another implementation, for a long-term scheduled gap, the gap length may be equal to the short-term leave duration, and during the gap the network shall avoid both DL and UL scheduling.

[0110] In another implementation, the gap length may be broadcast in the system information or configured through dedicated signaling, for which the network may adopt the value recommended by the UE.

[0111] In another implementation, for gaps with a TDM pattern, network A may reserve gaps periodically during the leave duration.

[0112] In another implementation, the duration for which the gap with TDM mode is adopted may be broadcast in the system information or may be configured through dedicated signaling, for which the network may adopt the value recommended by the UE.

[0113] In another implementation, the network may determine the TDM mode based on the TDM mode recommended by the UE, ongoing services, and the radio environment.

[0114] In another implementation, the TDM mode may be a bitmap for a subframe or frame, or may be indicated by a start time, duration, period, and / or reference SCS.

[0115] In another implementation, for an autonomous gap, it is left to the UE implementation as to how to communicate with the two networks during the gap.

[0116] In another implementation, the network may determine the gap mode based on the ongoing service type and / or quality of service (QoS) of the PDU session.

[0117] In another implementation, the network may transmit the gap mode information through RRC signaling.

[0118] In another implementation, the RRC signal may be an RRC Reconfiguration message.

[0119] In another implementation, the network may reject the leave request by not allocating any gaps.

[0120] In various embodiments, the UE may receive gap mode information from the gNB and move out of its current activity based on the gap.

[0121] In one implementation, the gap mode may be a long-term scheduling gap, a gap with a TDM mode, or an autonomous gap.

[0122] In another implementation, for a scheduled gap, the gap length may be equal to the short leave duration, and during the gap the network shall avoid both DL and UL scheduling.

[0123] In another implementation, the UE may indicate the gap length to the network or may indicate the leave trigger cause.

[0124] In another implementation, the exit trigger causes may include the second, third, fourth, and fifth scenarios as discussed above.

[0125] In another implementation, for gaps with a TDM pattern, the gaps may be reserved periodically during the leave duration.

[0126] In another implementation, the UE may indicate the TDM pattern to the network.

[0127] In another implementation, the TDM mode may be a bitmap for a subframe or frame, or may be indicated by a start time, duration, period, and / or reference SCS.

[0128] In another implementation, for an autonomous gap, it is left to the UE to implement how to communicate with the two networks during the gap.

[0129] In another implementation, for an autonomous gap, the UE may start a timer and control the autonomous gap duration.

[0130] In another implementation, for an autonomous gap, the UE may stop the autonomous gap timer when work with the other USIM is terminated.

[0131] In another implementation, for an autonomous gap, the UE may abort the procedure with the other USIM and return to the first USIM when the timer expires.

[0132] In another implementation, the UE may receive the gap mode information through RRC signaling.

[0133] In another implementation, the RRC signal may be an RRC Reconfiguration message.

[0134] In another implementation, when the UE does not receive any gap mode information from the gNB, it is left to the UE implementation or remains connected to the current network.

[0135] In the present disclosure, various embodiments may address at least one of the following issues regarding one-time leave: whether the UE needs to indicate to network A when communication with network B is terminated before the scheduled / autonomous gap; and / or whether network A should stay connected or return to an idle / inactive state when communication with network B cannot be terminated before the scheduled / autonomous gap. In one implementation, regarding the first issue, the UE may send an indication to network A when communication with network B is terminated: and network A may restore the previous configuration and data transmission as soon as possible. In another implementation, regarding the second issue, whether network A stays connected or returns to an idle / inactive state may be determined based on the service / procedure priority of one or more USIMs. For example, the one-time leave procedure may be adopted for the second, third, fourth, and fifth scenarios, as discussed above. It may have a lower priority for the second and third scenarios, as discussed above, compared to the data / voice service on network A. For the fourth scenario, for registration, according to the CT1 specification, the UE may retransmit it several times. For MO signaling, e.g., SMS, if it has high priority, it may adopt a long-term leave procedure. For RAU, it may lead the UE to enter the idle state, and this kind of problem may be reduced by configuring a sufficiently long gap. For the fifth scenario, the UE may retransmit it in the next DRX cycle and, if still needed, may detect paging again, e.g., in the next DRX cycle.

[0136] As discussed above, the intention of the one-time leave procedure may be to reduce the impact on network A as much as possible, and therefore it is more preferable to keep network A connected. In another implementation, the decision to stay connected or not may also be decided by network A, or a suggestion may be given when the UE requests a gap.

[0137] In another implementation, when communication with network B is not able to finish before the scheduled / autonomous gap timer expires, the ongoing procedure in network B may be aborted and proceed to service on network A.

[0138] In another implementation, with regard to the short-term leave procedure for the fourth and fifth scenarios, the UE may try to finish the procedure on network B as soon as possible. Meanwhile, network B may know that the UE is in short-term leave state on the other USIM, and therefore network B may not trigger mobility, such as but not limited to handover or redirection, measurement, and DC related procedures, while the UE may also not trigger re-establishment procedures.

[0139] In another implementation, the UE may inform network B that it is in a short leave procedure on another network, so that network B may avoid triggering mobility (e.g., handover, redirection), measurement, and / or DC related procedures.

[0140] In another implementation, for the idle state, the UE may indicate this information in msg5. During the inactive state, the UE may also enter the connected state, unless the procedure involves rna-Update, and therefore the UE may also include this information in message 5.

[0141] In another implementation, the UE may inform network B through RRC signaling that it is in a short leave procedure on the other network.

[0142] In another implementation, the RRC signaling may be Msg5, for example, RRCSetupComplete / RRCResumeComplete.

[0143] In another implementation, the RRC signaling may be Msg3 with a different establishment cause.

[0144] FIG. 18 shows an example of a short leaving procedure indication to a second network. In step 1851, SIM1 1820 is in a connected state, so SIM2 1810 needs to establish a connection with SIM2 gNB 1840, so the UE coordinates the leaving with SIM1 gNB 1830, and after coordination, SIM2 establishes an RRC connection with SIM2. In step 1852, the SIM2 AS sends an RRC setup request or resume request to the SIM2 gNB. In step 1853, the SIM2 gNB sends an RRC setup or RRC resume to the SIM2 AS. In step 1854, the SIM2 AS sends an RRC setup or resume completion (with an indication, e.g., MUSIMShortLeavingIndication or simple procedure indication) to the SIM2 gNB. In step 1855, the SIM2 gNB avoids triggering handover or measurements.

[0145] In various embodiments, for Msg5, the Asn.1 coding for a Multi-Sim Short Term Exit Indication may be as follows:

[0146] [Table 3]

[0147] In the above, one or more indications (e.g., shortLeavingIndication or simpleProcedureIndication) may be used for a multi-SIM UE. When the UE is in a short-leaving state on another USIM card, the UE may indicate this indication to the current network so that the current network may finish the procedure as soon as possible, and the network may not trigger a handover / measurement procedure.

[0148] In various embodiments, a UE may have multiple SIMs, USIM1 with network A and USIM2 with network B. When USIM1 is in a connected state with network A and short-term leaves for network B, the QoS of USIM1 may be affected. Certain PDU sessions may need to be affected or released, and therefore a clear cause (e.g., MUSIM or MUSIM Short-Term Leave) may be added to the UE / RAN node / CN node interface. For example, with regard to the PDU session resource notification message, the purpose of the PDU session resource notification procedure may be to notify that an already established QoS flow or PDU session for a given UE is released or is no longer satisfied or is again filled by the NG-RAN node, for which notification control is required. When a PDU session is released or is no longer satisfied due to MUSIM Short-Term Leave, it may include a new cause (e.g., MUSIM or MUSIM Short-Term Leave) to the CN node.

[0149] In one implementation, a new cause (e.g., MUSIM or MUSIM short departure) may be added between the UE and the RAN node, or between the UE and the CN node, or between the RAN and the CN node, or between two CN nodes.

[0150] The present disclosure describes a method, an apparatus, and a computer-readable medium for wireless communication. The present disclosure addresses problems involved in coordinating leave procedures for one or more devices including multiple subscriber identity modules (multi-SIMs). The method, the device, and the computer-readable medium described in the present disclosure may facilitate performance of wireless transmissions between user equipment and multiple network nodes, thus improving efficiency and overall performance. The method, the device, and the computer-readable medium described in the present disclosure may improve the overall efficiency of a wireless communication system.

[0151] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that may be realized using the solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, discussions of features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0152] Furthermore, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize in light of the description herein that the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in an embodiment that may not be present in all embodiments of the solution.

Claims

1. 1. A method for wireless communication, comprising: The method includes a user equipment (UE) configuring a leaving procedure for a plurality of networks; Configuring the removal procedure further comprises: determining, by the UE, an exit type in response to a particular scenario; The UE adjusts a leaving procedure based on the leaving type, wherein the plurality of networks includes a plurality of Radio Access Networks (RANs), the plurality of RANs includes a first RAN and a second RAN; In response to determining that the exit type is a predefined type, the UE sending a switch notification to the first RAN, where in response to the leaving type being a periodic leaving type, the switch notification includes one or more gap patterns, and in response to the leaving type being a one-time leaving type, the switch notification includes an leaving duration; receiving a configuration message from the first RAN by the UE; A method carried out by.

2. The method of claim 1 , wherein the UE indicates one or more gap patterns for paging occasion (PO) reception to the first RAN.

3. The method of claim 1 , wherein the predefined types include the periodic departure type.

4. The method of claim 3 , wherein the configuration message includes configuration for one or more gap patterns.

5. The method of claim 1 , wherein the predefined types include the one-time exit type.

6. The method according to claim 5, wherein the configuration message includes an RRC signaling with gap mode. The method described.

7. The method of claim 6 , wherein the gap mode comprises a long-term scheduling gap.

8. The method of claim 6 , wherein in response to the gap mode being configured as a long-term scheduling gap, a gap duration is equal to an evacuation duration.

9. 1. A method for wireless communication, the method comprising: receiving, by a radio access network (RAN) node, a switching notification indicating leaving assistance information from a user equipment (UE), in response to a corresponding leaving type being a periodic leaving type, the switching notification including one or more gap patterns, and in response to the corresponding leaving type being a one-time leaving type, the switching notification including an leaving duration; the RAN node determining a switching configuration for a leaving configuration; the RAN node sending a configuration message to the UE; A method comprising:

10. The method of claim 9, wherein the switch notification from the UE includes one or more gap patterns for paging occasion (PO) detection.

11. The method of claim 9 , wherein the configuration message comprises RRC signaling with gapped mode.

12. The method of claim 11 , wherein the gap mode comprises a long-term scheduling gap.

13. The method of claim 12 , in response to the gap mode being determined as a long term scheduling gap, a gap duration is equal to an exit duration.

14. An apparatus, comprising: A memory for storing instructions; a processor in communication with the memory; Equipped with When the processor executes the instructions, the processor is configured to cause the device to configure an exit procedure for a plurality of networks; Configuring the removal procedure further comprises: Determining an exit type in response to a particular scenario; and adjusting a leaving procedure based on the leaving type, wherein the plurality of networks includes a plurality of radio access networks (RANs), the plurality of RANs includes a first RAN and a second RAN; In response to determining that the exit type is a predefined type, sending a switch notification to the first RAN, where in response to the leaving type being a periodic leaving type, the switch notification includes one or more gap patterns, and in response to the leaving type being a one-time leaving type, the switch notification includes an leaving duration; receiving a configuration message from the first RAN; An apparatus for performing an

15. A wireless node, the wireless node comprising: A memory for storing instructions; a processor in communication with the memory; Equipped with When the processor executes the instructions, the processor: receiving a switching notification from a user equipment (UE) indicating leave assistance information, in response to a corresponding leave type being a periodic leave type, the switching notification including one or more gap patterns, and in response to the corresponding leave type being a one-time leave type, the switching notification including an leave duration; determining a switching configuration for a leaving configuration; sending a configuration message to the UE; The wireless node is configured to cause the wireless node to execute:

Images