Patent Description:
Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices (i.e., user equipment devices or UEs) now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities. Additionally, there exist numerous different wireless communication technologies and standards. Some examples of wireless communication standards include GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE <NUM> (WLAN or Wi-Fi), BLUETOOTH™, etc..

The increasing number of features and functionality introduced in wireless communication devices also creates a continuous need for improvement in both wireless communications and in wireless communication devices. In particular, it is important to ensure the accuracy of transmitted and received signals through user equipment devices (UEs), e.g., through wireless devices such as cellular phones, base stations and relay stations used in wireless cellular communications. For example, some UEs may include multiple subscriber identity modules (SIMs) which may be active concurrently. Under some circumstances, collisions may occur between transmissions to such UEs associated with different SIMs. Such collisions may negatively impact user experience and performance of the UE. In addition, increasing the functionality of a UE device can place a significant strain on the battery life of the UE device. For example, certain paging schedules for different SIMs may require increased power use. Thus, it is very important to also reduce power requirements in UE device designs while allowing the UE device to maintain good transmit and receive abilities for improved communications. <CIT> shows a pre-5th-Generation (<NUM>) or <NUM> communication system to be provided for supporting higher data rates Beyond 4th-Generation (<NUM>) communication system such as long term evolution (LTE). A method for providing voice call and data service simultaneously on plurality of SIM in EN-DC capable UE is shown. A first SIM is registered to a first network in a DCNR supported mode using a T1 and a second SIM is registered to a second network in the DCNR not supported mode using a T2. Then, determining a <NUM> bearer is established on the T1 and a <NUM> bearer is established on the T2 by the first network using the first SIM. Further, determining the voice call is being initiated on the second SIM when the data service is active on the first SIM through the T1 and the T2; followed by configuration of the second SIM to provide the voice call over the T2 and the first SIM to provide the data services over the T1. <CIT> shows a mobile communication device including a first RF device, a second RF device, and a controller. The first RF device performs wireless transmission and reception utilizing a first RAT. The second RF device performs wireless transmission and reception utilizing a second RAT. The controller uses a first subscriber identity to make a first call or conduct a first data session via the first RF device, determining a dual connectivity on the first RAT and the second RAT is supported in response to a request for using a second subscriber identity to start a second call or a second data session via the second RF device, and allows the second call or the second data session to start during the first call or the first data session in response to the dual connectivity on the first RAT and the second RAT being supported. <CIT> shows operation of a dual-subscriber identity module (SIM) dual-standby (DSDS) user equipment device (UE) configured with a first SIM and a second SIM. The UE performs communications with a first cellular network using the first SIM and a first radio resource control (RRC) connection and receives a request to perform a higher priority communication using the second SIM. In response to the request to perform the higher priority communication, the UE transmits a request to the first network to suspend the first RRC connection. After transmission of the request to suspend the first RRC connection, the UE receives a message from the first network to place the first RRC connection in an inactive state, and initiates a timer, wherein the timer is used to determine whether the first RRC connection remains in the inactive state or transitions to an idle state.

To increase coverage and better serve the increasing demand and range of envisioned uses of wireless communication, in addition to the communication standards mentioned above, there are further wireless communication technologies under development, including fifth generation (<NUM>) new radio (NR) communication. Accordingly, improvements in the field in support of such development and design are desired. This object is achieved by the subject-matter according to the independent claims. Advantageous embodiments are the subject matter of the dependent claims, the description and the figures.

The invention is disclosed by the independent claims.

While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the scope of the subject matter as defined by the appended claims.

Memory Medium - Any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

Computer System - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

User Equipment (UE) (or "UE Device") - any of various types of computer systems or devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

Processing Element (or Processor) - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, individual processors, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a "cellular base station"), and may include hardware that enables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may be referred to as a "cell. " The base station 102A and the UEs <NUM> may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), <NUM> new radio (<NUM> NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, it may alternately be referred to as an 'eNodeB' or 'eNB'. Note that if the base station 102A is implemented in the context of <NUM> NR, it may alternately be referred to as a 'gNodeB' or 'gNB'.

In some embodiments, base station 102A may be a next generation base station, e.g., a <NUM> New Radio (<NUM> NR) base station, or "gNB". In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). For example, it may be possible that that the base station 102A and one or more other base stations <NUM> support joint transmission, such that UE <NUM> may be able to receive transmissions from multiple base stations (and/or multiple TRPs provided by the same base station).

Note that a UE <NUM> may be capable of communicating using multiple wireless communication standards. For example, the UE <NUM> may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, <NUM> NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE <NUM> may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M/H), and/or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

<FIG> illustrates user equipment <NUM> (e.g., one of the devices 106A through 106N) in communication with a base station <NUM>, according to some embodiments. The UE <NUM> may be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer, a laptop, a tablet, a smart watch or other wearable device, or virtually any type of wireless device.

The UE <NUM> may include a processor (processing element) that is configured to execute program instructions stored in memory. Alternatively, or in addition, the UE <NUM> may include a programmable hardware element such as an FPGA (field-programmable gate array), an integrated circuit, and/or any of various other possible hardware components that are configured to perform (e.g., individually or in combination) any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

The UE <NUM> may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE <NUM> may be configured to communicate using, for example, NR or LTE using at least some shared radio components. As additional possibilities, the UE <NUM> could be configured to communicate using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio and/or GSM or LTE using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE <NUM> may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.

For example, the UE <NUM> might include a shared radio for communicating using either of LTE or <NUM> NR (or either of LTE or 1xRTT, or either of LTE or GSM, among various possibilities), and separate radios for communicating using each of Wi-Fi and Bluetooth.

<FIG> illustrates an example simplified block diagram of a communication device <NUM>, according to some embodiments. It is noted that the block diagram of the communication device of <FIG> is only one example of a possible communication device. According to embodiments, communication device <NUM> may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and/or a combination of devices, among other devices. As shown, the communication device <NUM> may include a set of components <NUM> configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components <NUM> may be implemented as separate components or groups of components for the various purposes. The set of components <NUM> may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device <NUM>.

For example, the communication device <NUM> may include various types of memory (e.g., including NAND flash <NUM>), an input/output interface such as connector I/F <NUM> (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display <NUM>, which may be integrated with or external to the communication device <NUM>, and wireless communication circuitry <NUM> (e.g., for LTE, LTE-A, NR, UMTS, GSM, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS, etc.).

The wireless communication circuitry <NUM> may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antenna(s) <NUM> as shown. The wireless communication circuitry <NUM> may include cellular communication circuitry and/or short to medium range wireless communication circuitry, and may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communication circuitry <NUM> may include one or more receive chains (including and/or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for <NUM> NR). For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with a second radio. The second radio may be dedicated to a second RAT, e.g., <NUM> NR, and may be in communication with a dedicated receive chain and the shared transmit chain.

As shown, the SOC <NUM> may include processor(s) <NUM>, which may execute program instructions for the communication device <NUM> and display circuitry <NUM>, which may perform graphics processing and provide display signals to the display <NUM>. The processor(s) <NUM> may also be coupled to memory management unit (MMU) <NUM>, which may be configured to receive addresses from the processor(s) <NUM> and translate those addresses to locations in memory (e.g., memory <NUM>, read only memory (ROM) <NUM>, NAND flash memory <NUM>) and/or to other circuits or devices, such as the display circuitry <NUM>, wireless communication circuitry <NUM>, connector I/F <NUM>, and/or display <NUM>. The MMU <NUM> may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU <NUM> may be included as a portion of the processor(s) <NUM>.

As noted above, the communication device <NUM> may be configured to communicate using wireless and/or wired communication circuitry. As described herein, the communication device <NUM> may include hardware and software components for implementing any of the various features and techniques described herein. The processor <NUM> of the communication device <NUM> may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor <NUM> may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor <NUM> of the communication device <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be configured to implement part or all of the features described herein.

Further, as described herein, wireless communication circuitry <NUM> may include one or more processing elements. In other words, one or more processing elements may be included in wireless communication circuitry <NUM>. Thus, wireless communication circuitry <NUM> may include one or more integrated circuits (ICs) that are configured to perform the functions of wireless communication circuitry <NUM>. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of wireless communication circuitry <NUM>.

As another possibility, the base station <NUM> may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., <NUM> NR and LTE, <NUM> NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

In addition, as described herein, processor(s) <NUM> may include one or more processing elements.

Further, as described herein, radio <NUM> may include one or more processing elements.

<FIG> illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of <FIG> is only one example of a possible cellular communication circuit; other circuits, such as circuits including or coupled to sufficient antennas for different RATs to perform uplink activities using separate antennas, or circuits including or coupled to fewer antennas, e.g., that may be shared among multiple RATs, are also possible. According to some embodiments, cellular communication circuitry <NUM> may be included in a communication device, such as communication device <NUM> described above. As noted above, communication device <NUM> may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices.

The cellular communication circuitry <NUM> may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-b and <NUM> as shown. In some embodiments, cellular communication circuitry <NUM> may include dedicated receive chains (including and/or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for <NUM> NR). For example, as shown in <FIG>, cellular communication circuitry <NUM> may include a first modem <NUM> and a second modem <NUM>. The first modem <NUM> may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and the second modem <NUM> may be configured for communications according to a second RAT, e.g., such as <NUM> NR.

As shown, the first modem <NUM> may include one or more processors <NUM> and a memory <NUM> in communication with processors <NUM>.

Similarly, the second modem <NUM> may include one or more processors <NUM> and a memory <NUM> in communication with processors <NUM>.

Thus, when cellular communication circuitry <NUM> receives instructions to transmit according to the first RAT (e.g., as supported via the first modem <NUM>), switch <NUM> may be switched to a first state that allows the first modem <NUM> to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry <NUM> and UL front end <NUM>). Similarly, when cellular communication circuitry <NUM> receives instructions to transmit according to the second RAT (e.g., as supported via the second modem <NUM>), switch <NUM> may be switched to a second state that allows the second modem <NUM> to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry <NUM> and UL front end <NUM>).

As described herein, the first modem <NUM> and/or the second modem <NUM> may include hardware and software components for implementing any of the various features and techniques described herein. The processors <NUM>, <NUM> may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processors <NUM>, <NUM> may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processors <NUM>, <NUM>, in conjunction with one or more of the other components <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> may be configured to implement part or all of the features described herein.

In addition, as described herein, processors <NUM>, <NUM> may include one or more processing elements. Thus, processors <NUM>, <NUM> may include one or more integrated circuits (ICs) that are configured to perform the functions of processors <NUM>, <NUM>. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors <NUM>, <NUM>.

In some embodiments, the cellular communication circuitry <NUM> may include only one transmit/receive chain. For example, the cellular communication circuitry <NUM> may not include the modem <NUM>, the RF front end <NUM>, the DL front end <NUM>, and/or the antenna 335b. As another example, the cellular communication circuitry <NUM> may not include the modem <NUM>, the RF front end <NUM>, the DL front end <NUM>, and/or the antenna 335a. In some embodiments, the cellular communication circuitry <NUM> may also not include the switch <NUM>, and the RF front end <NUM> or the RF front end <NUM> may be in communication, e.g., directly, with the UL front end <NUM>.

In some implementations, fifth generation (<NUM>) wireless communication will initially be deployed concurrently with other wireless communication standards (e.g., LTE). For example, whereas <FIG> illustrates a possible standalone (SA) implementation of a next generation core (NGC) network <NUM> and <NUM> NR base station (e.g., gNB <NUM>), dual connectivity between LTE and <NUM> new radio (<NUM> NR or NR), such as in accordance with the non-standalone (NSA) architecture illustrated in <FIG>, has been specified as part of the initial deployment of NR. Thus, as illustrated in <FIG>, evolved packet core (EPC) network <NUM> may continue to communicate with current LTE base stations (e.g., eNB <NUM>). In addition, eNB <NUM> may be in communication with a <NUM> NR base station (e.g., gNB <NUM>) and may pass data between the EPC network <NUM> and gNB <NUM>. In some instances, the gNB <NUM> may also have at least a user plane reference point with EPC network <NUM>. Thus, EPC network <NUM> may be used (or reused) and gNB <NUM> may serve as extra capacity for UEs, e.g., for providing increased downlink throughput to UEs. In other words, LTE may be used for control plane signaling and NR may be used for user plane signaling. Thus, LTE may be used to establish connections to the network and NR may be used for data services. As will be appreciated, numerous other non-standalone architecture variants are possible.

In some embodiments, the UE <NUM> may include multiple subscriber identity modules (SIMs, sometimes referred to as SIM cards). In other words, the UE <NUM> may be a multi-SIM (MUSIM) device, such as a dual-SIM device. Any of the various SIMs may be physical SIMs (e.g., SIM cards) or embedded (e.g., virtual) SIMs. Any combination of physical and/or virtual SIMs may be included. Each SIM may provide various services (e.g., packet switched and/or circuit switched services) to the user. In some embodiments, UE <NUM> may share common receive (Rx) and/or transmit (Tx) chains for multiple SIMs (e.g., UE <NUM> may have a dual SIM dual standby (DSDS) architecture). Other architectures are possible. For example, UE <NUM> may be a dual SIM dual active (DSDA) architecture, may include separate Tx and/or Rx chains for the various SIMs, may include more than two SIMs, etc..

The different identities (e.g., different SIMs) may have different identifiers, e.g., different UE identities (UE IDs). For example, an international mobile subscriber identity (IMSI) may be an identity associated with a SIM (e.g., in a MUSIM device each SIM may have its own IMSI. The IMSI may be unique. Similarly, each SIM may have its own unique international mobile equipment identity (IMEI). Thus, the IMSI and/or IMEI may be examples of possible UE IDs, however other identifiers may be used as UE ID.

The different identities may have the same or different relationships to various public land mobile networks (PLMNs). For example, a first identity may have a first home PLMN, while a second identity may have a different home PLMN. In such cases, one identity may be camped on a home network (e.g., on a cell provided by BS <NUM>) while another identity may be roaming (e.g., while also camped on the same cell provided by BS <NUM>, or a different cell provided by the same or different BS <NUM>). In other circumstances, multiple identities may be concurrently home (e.g., on the same or different cells of the same or different networks) or may be concurrently roaming (e.g., on the same or different cells of the same or different networks). As will be appreciated, numerous combinations are possible. For example, two SIM subscriptions on a MUSIM device may belong to the same equivalent/carrier (e.g., AT&T/AT&T or CMCC/CMCC). As another possibility, SIM-A may be roaming into SIM-B's network (SIM-A CMCC user roaming into AT&T and SIM-B is also AT&T).

Furthermore, for a UE with a MUSIM configuration (e.g., SIM1 and SIM2) in DSDS architecture, when the UE performs an RF (radio frequency) re-tuning from SIM1 to SIM2, Tx/Rx may be suspended for SIM1. However, for UEs supporting <NUM> NR mmWave frequencies, a dedicated FR2 Tx/Rx RF capability may be included as hardware in the UE while some current MUSIM designs may not take full benefit of this capability. For example, a UE with a MUSIM configuration including a SIM1 with support for LTE and FR2 (mmWave) with active packet switching may be considered a data preferred or data default SIM (DDS). Additionally, in some examples, certain high-range FR1 frequencies may also use a dedicated Tx/Rx. The UE may also include a non-data or non-data default SIM (e.g., SIM2) with support for LTE but not FR2 (mmWave). Accordingly, there may exist a scenario in which the UE is operating in enhanced dual connectivity (EN-DC) mode with SIM1 active and upon SIM2 receiving or placing a voice call, SIM1 may become out of service due to the suspension of Tx/Rx on SIM1. For a UE with a MUSIM configuration in DSDA architecture, there may not be a suspension of Tx/Rx capability on both SIM1 and SIM2.

<FIG> is a communication flow diagram illustrating example aspects of updating a UE's configuration from NSA (non-standalone) to SA (standalone) after the UE has performed a RF re-tuning as described above (e.g., from SIM1 to SIM2).

More specifically, in <NUM>, SIM1 may be operating in EN-DC mode, be in an RRC-Connected state and may further support LTE and NR (FR2) in a DDS role. In other words, SIM1 may be communicating with a NR supported base station (e.g., gNB (FR2)) in addition to an LTE supported base station (e.g., eNB). Additionally, or alternatively SIM2 may take on a non-data default (nDDS) role through communicating with the LTE supported eNB (and not the gNB) and may further be in an RRC-IDLE state. In <NUM>, SIM2 may place a voice call using voice over LTE (VoLTE) or via circuit-switched fallback.

Next, in <NUM>, SIM1 may disable its LTE Tx/Rx resources in response to SIM2 placing the voice call. Accordingly, SIM2 may then utilize said SIM1 disabled resources for use in its LTE communications with the eNB (e.g., the voice call). Additionally, or alternatively in <NUM> the UE (e.g., SIM1) may utilize a copy of a LTE system information block (SIB) (e.g., SIB24) corresponding to the gNB and may further decide in <NUM> to upgrade its configuration from a NSA to a SA signaling gateway (SG) associated with the gNB. Correspondingly, the UE (e.g., SIM1) may then in <NUM> transmit a REGISTRATION REQUEST message to the <NUM> Core Access and Mobility Management Function (AMF) corresponding to the gNB and further receive a REGISTRATION ACCEPT message from the AMF of the gNB in <NUM>. In other words, <NUM>-<NUM> describe an example scenario in which SIM1 may utilize a NR Tx/Rx path to inform the network of its LTE unavailability and may alter its configuration for simultaneous data transfer over a NR link in SIM1 while a voice call is active on SIM2, according to some embodiments.

In case of some multi-SIM cellular devices, Dual SIM Dual Standby (DSDS) may be the more widely adopted technology. In particular, while utilizing DSDS, both SIMs may be active when the cellular connection for both SIMs is in "RRC-Idle" mode. Conversely, in the scenario of connected mode (e.g., RRC-Connected) DSDS operation, only one SIM may have an active connection with the network due to the fact that many cellular devices only have one modem to support both SIMs. In other words, SIM2 may be "out of service" when there is an active call on SIM1 or vice-versa. Moreover, cellular devices that support NR-NSA (non-standalone) and NR-SA (standalone), the UE may be capable of processing signals originating from both technologies at the same time (e.g., simultaneously).

<FIG> is a flow diagram illustrating example aspects of a method for updating a UE's configuration from DSDS to DSDA in order to gain active access on both SIMs at the same time when one of the SIMs is actively communicating on NR-SA. (e.g., when RF front-end paths are different). For example, a <NUM> NR UE or wireless device capable of supporting DSDS in <NUM> may determine if DSDS is active in <NUM>. Accordingly, if DSDS is not active, the UE may proceed from <NUM> through <NUM> without change to proceed to <NUM> in which a timer may expire or an event may be detected in order to restart the flow diagram at <NUM>.

Additionally, or alternatively if DSDS is activated in <NUM>, the UE may proceed to <NUM> in which the UE further determines if the DDS carrier supports a NR-SA configuration. If not, the UE may proceed to use legacy DSDS operations in <NUM> and further continue to <NUM>. For example, in connected mode DSDS operation, the UE may only have one SIM with an active connection to the network while the other SIM may be out of service. This legacy mode DSDS operation may be caused by the fact some cellular devices may only have one modem to support both SIMs. In other words, the UE may only be able to keep the DDS stack active. However, if the DDS carrier does support a NR-SA configuration, the UE may proceed to <NUM> in which the UE further determines if the DDS NR bands and nDDS LTE bands are different. If the DDS NR bands and nDDS LTE bands are different, the UE may keep both DDS and nDDS protocol stacks active in <NUM>, but otherwise may proceed to <NUM>. Finally, the UE may proceed to <NUM> and ultimately restart the process again at <NUM> upon expiry of a timer or detection of a particular event.

In some embodiments, a UE supporting MUSIM and including SIM1 and SIM2 may further have NR enabled for both SIMs. However, in the NSA configuration, the subscriber data management (SDM) of the UE may be utilized to disable NR measurements on a dormant SIM in order to conserve battery power.

<FIG> illustrates an example communication flow diagram in which <NUM> (e.g., NR) Mobile Data Switching is not supported. More specifically, <FIG> illustrates the user initiated switching of the UI setting of one or more SIMs (e.g., SIM1 and SIM2) from DDS to nDDS or vice versa. For example, in 1002a the UE may have a UI setting with SIM1 configured as DDS. Consequently, in 1004a, SIM1 may attached to the NG-RAN with NR enabled. However, as a nDDS, SIM2 may only attach to the NG-RAN with LTE as seen in 1006a. However, if the user switches the UI setting of SIM2 to DDS as shown in 1008a and 1010a, the SIMs may essentially reverse roles with regard to how they connect to the NG-RAN. In other words and as shown in 1012a, since SIM2 has been switched to DDS by the user, SIM1 may only attach to the NG-RAN using LTE and SIM2 may attach to the NG-RAN with NR enabled as shown in 1014a. However, the nDDS SIMs attached to the NG-RAN may still be consuming power through NR measurement reports (MRs). Additionally, or alternatively in some embodiments the example above in regard to <FIG> may be extended to support a UE that may attach to a <NUM>-RAN (e.g., LTE) and also include a NSA capability which is enabled and disabled in SIM1 and SIM2 respectively.

In a different embodiment, <FIG> illustrates an example communication flow diagram in which <NUM> (e.g., NR) Mobile Data Switching is supported. More specifically, <FIG> illustrates the implementation of said switching for a UE in utilizing a NSA DSDS configuration. For example, as shown in 1002b, a UE communicating with a next-generation-random access network (NG-RAN) may have a user interface (UI) setting in which SIM1 has been designated as DDS. Accordingly, in 1004b the DDS SIM1 may attach to the NG-RAN if NR is enabled. In 1006b, the nDDS SIM2 may also attach to the NG-RAN due to NR being enabled. Additionally, or alternatively in 1006b the SDM may also disable NR measurement reports (MR) for SIM2.

In 1008b, the UE may utilize its supported Mobile Data Switching capability in order to reconfigure SIM1 and SIM2 and their DDS and/or nDDS configurations. In other words, as shown in 1010b, the UE may utilize said Mobile Data Switching capability to reconfigure SIM1 to be a nDDS rather than its previous configuration as a DDS and reconfigure SIM2 to be a DDS rather than its previous configuration as a nDDS. Additionally, or alternatively in 1010b the UE may disable NR MR for the nDDS SIM1. This may provide some power conservation benefits to the UE by reducing <NUM> communications (e.g., measurement reports) with the NG-RAN. Next, in 101b2, having reconfigured SIM2 as a DDS, the UE may then re-enable NR MR for SIM2. Accordingly, the UE may then begin to communicate and benefit from measurement reports from the NG-RAN.

In some embodiments, a UE supporting MUSIM and including a first SIM (e.g., SIM1) and a second SIM (e.g., SIM2) may further be utilizing a NSA DSDA configuration. In other words, the UE may be able to support active DDS and nDDS stacks at the same time. More specifically, in some embodiments, SIM2 may be using SIM1 data to support a voice call via Wi-Fi. Accordingly, improvements in regard to battery conservation may be desired for the aforementioned configuration.

For example, as shown in <FIG>, in <NUM> SIM2 may be supporting a Wi-Fi voice call through use of SIM1's NR data due to SIM2 being out of service. In <NUM>, the UE may support a NSA DSDA configuration in which the SDM is active and may further disable NR on SIM1 in order to conserve battery power in <NUM>. Additionally, or alternatively in <NUM>, the UE may trigger semi-persistent scheduling for the NSA SIM1 due to the disabled NR and may further notify the network (e.g., NG-RAN) that a voice call is being performed. Accordingly, in <NUM>, once the SIM2 Wi-Fi voice call using SIM1's data has ended, the SDM may be de-activated in <NUM>.

<FIG> illustrates an example solution for a data preferred SIM call. More specifically, for a UE supporting MUSIM and including one or more SIMs, a first SIM (SIM1) <NUM> may be configured as a data preferred SIM (e.g., DDS) while a second SIM (SIM2) <NUM> may be configured as an nDDS. In some embodiments, SIM1 may be supporting a Wi-Fi voice call through use of an IP multimedia subsystem (IMS) and may further utilize SIM2's IMS capability via tunnel over internet to provide data support to SIM1 while SIM1 maintains said IMS supported Wi-Fi call. In other words, a UE may be configured to draw additional data support from an nDDS while supporting a Wi-Fi call via IMS while simultaneously utilizing data for other purposes involving the internet (e.g., downloading files from a browser).

<FIG> illustrates an example of cellular and iWLAN activity related to a UE with two modems and a DSDA configuration, according to some embodiments. For example, in <NUM>, a mobile originated (MO) call may be placed or be active through use of Modem <NUM> (TMO). Additionally, the TX/RX capability of Modem <NUM> (AT&T) may be suspended as shown in <NUM> due to Modem <NUM> being out of service (OOS) in <NUM>. Correspondingly, in <NUM>, the UE may perform an iWLAN registration procedure in order to support the call and camp using modem <NUM> cellular data. In other words, the UE with a first SIM (SIM1) utilizing Modem <NUM> may suspend its Tx/Rx resources and further utilize its iWLAN capability to support a second SIM (SIM2) with an active Wi-Fi call (e.g., the Modem <NUM> MO call). Additionally, by utilizing this iWLAN capability, both modems may be able to make or receive MO or mobile terminated (MT) calls as shown in <NUM>. In other words, due to the fact that Modem <NUM> and Modem <NUM> may have a different phone numbers with which to receive calls, a user with a mobile device in the shown configuration may wish to maintain a call using the particular Modem <NUM> phone number through use of iWLAN registration using Modem <NUM> cellular data to support said call.

Once the MO call has ended in <NUM> and Modem <NUM>'s TX/RX resources become idle in <NUM>, the UE may deregister the iWLAN camp on Modem <NUM>'s cellular data shown by <NUM> may in turn further cause Modem <NUM>'s Tx/Rx resources to become idle as shown by <NUM>.

In some embodiments, a UE may support MUSIM as well as a SA DSDA configuration in which the UE's first SIM's (SIM1) data is in connected mode and is being used by the UE's second SIM (SIM2) due to SIM2 being out of service while supporting a Wi-Fi voice call. Accordingly, the UE may be able to implement certain solutions in order to conserve battery consumption in the aforementioned scenario.

For example, as shown in <FIG>, in <NUM> SIM2 may be supporting a Wi-Fi voice call through use of SIM1's data due to SIM2 being out of service. In <NUM>, the UE may support a SA DSDA configuration in which the SDM is active. In <NUM>, the SIM1 SA may disable carrier aggregation (CA) if any secondary cell (Scell) is active, according to some embodiments. In some embodiments, the SIM1 SA may transition to the lowest bandwidth part (BWP) as part of <NUM>. Additionally, or alternatively in <NUM> the SIM1 SA may trigger semi-persistent scheduling and may further notify the network (e.g., NG-RAN) that data for the voice call is being utilized. In some embodiments, in <NUM> the SIM1 SA may also perform a fallback procedure to use LTE data if the screen is off. Accordingly, in <NUM>, once the SIM2 Wi-Fi voice call using SIM1's data has ended, the SDM may be de-activated in <NUM>.

In some embodiments, a UE may support MUSIM as well as a SA DSDA configuration in which the UE's first SIM's (SIM1) data is supporting an Evolved Packet System Fallback (EPSFB) call in addition to SIM1's data also being used by the UE's second SIM (SIM2) due to SIM2 being out of service while supporting a Wi-Fi voice call. Accordingly, the UE may be able to implement certain solutions in order to conserve battery consumption in the aforementioned scenario.

For example, as shown in <NUM> of <FIG>, a UE's SIM1 may be supporting an active EPSFB call while SIM2 is using SIM1 data for a Wi-Fi voice call. However, even after the EPSFB call of SIM1 is ended in <NUM> and the SDM becomes active in <NUM>, the SIM1 may remain on LTE in <NUM>. In other words, when the SIM1 call has ended, the SDM may become active while the SIM1 keeps camping on LTE rather than immediately returning to NR. Accordingly, once the SIM2 Wi-Fi voice call using the data of SIM1 has ended in <NUM>, the SDM may become inactive in <NUM> and SIM1 may further reestablish its NR connection from its current LTE connection in <NUM>.

In some embodiments and as shown in <FIG>, in <NUM> a UE's SIM1 may be supporting an active NR or EPSFB call while SIM2 is using SIM1 data for a Wi-Fi voice call. However, after the NR or EPSFB call of SIM1 is ended in <NUM> and the SDM becomes active in <NUM>, the SIM2 Wi-Fi voice call may be handed over to voice over LTE (VoLTE). In other words, when the SIM1 EPSFB call has ended, the SDM may become active and the UE may initiate a handover such that the SIM2 Wi-Fi voice call is transferred to VoLTE rather than immediately reestablishing its NR connection to complete the call using voice over NR (VoNR). Accordingly, once the SIM2 Wi-Fi VoLTE call has ended in <NUM>, the SDM may become inactive in <NUM> and SIM1 may further reestablish its NR connection from its current LTE connection in <NUM>.

In some embodiments, a UE operating in enhanced dual connectivity (EN-DC) and supporting a dual SIM-dual standby (DSDS) configuration may include a first SIM (SIM1) that further supports frequency range <NUM> (FR2) communications on the NR leg. Furthermore, if a second SIM (SIM2) of the UE receives a voice call, the first SIM (SIM1) may inform the NR supporting base station (e.g., gNB) via a MAC control element, UCI or via the SRB3 interface that the LTE communication link between the SIM1 and eNB may be suspended for "x" seconds. The NR supporting base station (e.g., gNB) may send a SGNB MODIFICATION REQUIRED message to the LTE supporting base station (e.g., eNB). This SGNB MODIFICATION REQUIRED message may further include information elements (IEs) related to parameters or values used to inform the eNB to not de-register the UE, but rather maintain the context or connection for a certain time period "x". For example, in some embodiments, if the UE returns to service within the indicated time period "x", the UE context may be restored in LTE. Additionally, or alternatively if the UE does not return to service within "x", the NR-leg may be released. Furthermore, the gNB may have the capability to extend the time period "x", according to some embodiments.

According to some embodiments, a UE operating in a similar EN-DC and DSDS configuration in which the UE includes a first SIM (SIM1) that further supports frequency range <NUM> (FR2) communications on the NR leg and a second SIM (SIM2) of the UE receives a voice call, the first SIM (SIM1) may inform the NR supporting base station (e.g., gNB) via a MAC control element, UCI, or via the SRB3 interface that the LTE communication link between SIM1 and eNB may be suspended for "x" seconds. The SIM1 network gNB may send a SGNB MODIFICATION REQUIRED message to the SIM1 eNB. Furthermore, this SGNB MODIFICATION REQUIRED message may include IEs which may indicate or inform the eNB to not drop the UE's master node (MN) context, but rather maintain the MN context in a suspended state for a certain time period "x". In some embodiments, this suspended state may be similar to the RRC Inactive state. Additionally, or alternatively the SIM1 eNB may send a SGNB MODIFICATION CONFIRM message to the gNB in response to receiving the SGNB MODIFICATION REQUIRED message.

For example, in some embodiments, if the UE returns to service within the indicated time period "x", the UE context may be restored in LTE. Additionally, or alternatively if the UE does not return to service within the time period "x", the NR-leg may be released by the UE. Moreover, the value or parameter "x" may be either provided by the UE, or the UE may initiate a procedure for an RF tune away for a voice call or other signaling and the RAN may appropriately derive the value "x". Furthermore, the gNB or UE may have the capability to periodically extend the time period "x" based on how long the voice call on the SIM may continue, according to some embodiments. Additionally, or alternatively while the MN leg is tuned away, the wireless device (e.g., UE) may continue data transfer on SIM1's secondary cell group (SCG) over FR2.

Moreover, in some embodiments, the SGNB MODIFICATION REQUIRED message may correspond to or indicate E-UTRAN Radio Access Bearers (E-RABs) which are to be modified such that the eNB can react accordingly with regard to the maintaining the UE's context. For example, E-RAB IDs, EN-DC Resource Configurations (which may indicate the packet data convergence protocol (PDCP) and lower layer MCG or SCG configurations), CHOICE Resource Configuration, uplink configuration, or SgNB Resource Configuration Information (used to coordinate resource utilization between the en-gNB and the MeNB) may be modified to provide information to the eNB regarding the appropriate reaction regarding the UE's context. For example, the SGNB MODIFICATION REQUIRED message may include a validity timer with corresponding value "x seconds" in addition to indicating that the UE context should be retained such that the UE remains in a MM-Registered (Mobility Management-Registered) and CM-Connected (Connection Management-Connected) state.

<FIG> illustrates a communication flow corresponding to a wireless device configured for EN-DC and DSDS operation. More specifically, <FIG> illustrates an example method of how SIM1 may utilize the NR Tx/Rx path to inform the network of LTE unavailability. This may allow for simultaneous data transfer over the NR link in SIM1 while an active voice call is being performed on SIM2.

For example, in some embodiments and as shown by <NUM>, the wireless device (e.g., UE) may support MUSIM and include a first SIM (SIM1) in EN-DC mode corresponding to LTE and NR (FR2) being active in an RRC-Connected state. Additionally, or alternatively in <NUM> the UE's second SIM (SIM2) may be in an RRC-IDLE state and may further place a voice call using VoLTE or CSFB in <NUM>. Correspondingly, in <NUM>, SIM1's LTE Tx/Rx resources may be disabled and may further be utilized by SIM2 in its LTE leg as shown in <NUM>. Next in <NUM>, the UE may inform the gNB using the NR leg (via MAC-CE, UCI, and/or SRB3) that SIM1 MCG will be without Tx/Rx for x seconds.

In <NUM>, the SIM1 gNB may then transmit a SGNB Modification Required message to the SIM1 eNB which may include IEs used to indicate a validity timer of "x" seconds and that the UE context should be retained. In response, the SIM1 eNB may transmit back to the SIM1 gNB a SGNB Modification Confirm message as shown in <NUM>. Finally, in <NUM>, the gNB may inform the UE (via MAC-CE and/or DCI) that all uplink/downlink (UL/DL) data could pass through the gNB over the NR leg.

<FIG> illustrates a call flow corresponding to a wireless device configured for EN-DC and DSDS operation. More specifically, <FIG> illustrates an example method of how the network may initiate an RF tune away through use of piggybacking information in a NAS message. This may allow for simultaneous data transfer over the NR link in SIM1 while an active voice call is being performed on SIM2.

For example, in some embodiments and as shown by <NUM>, the wireless device (e.g., UE) may support MUSIM and include a first SIM (SIM1) in EN-DC mode corresponding to LTE and NR (FR2) being active in an RRC-Connected state. Additionally, or alternatively in <NUM> the UE's second SIM (SIM2) may be in an RRC-IDLE state and may further place a voice call using VoLTE or CSFB in <NUM>. Correspondingly, in <NUM>, SIM1's Tx/Rx resources may be disabled and may further be utilized by SIM2 in its LTE leg as shown in <NUM>. Next in <NUM>, the UE may inform the gNB using the NR leg (via MAC-CE, UCI, and/or SRB3) that the SIM1 MCG will be without Tx/Rx for x seconds.

In <NUM>, the SIM1 gNB may then transmit a SGNB Modification Required message to the SIM1 eNB which may include IEs used to indicate a validity timer of "x" seconds and that the UE context should be retained. In response, the SIM1 eNB may transmit back to the SIM1 gNB a SGNB Modification Confirm message as shown in <NUM>. In <NUM>, the gNB may inform the UE (via MAC-CE and/or DCI) that all uplink/downlink (UL/DL) data could pass through the gNB over the NR leg.

Next, in <NUM>, the eNB may receive a NAS message from the mobility management entity (MME). This message may indicate to the eNB that the UE should perform an RF tune away. Correspondingly, in <NUM> the SIM1 eNB may transmit an RRC Transfer message to the SIM1 gNB based on this received information in the NAS message. Furthermore, in <NUM> the gNB may then "piggyback" or include with an LTE NAS message sent to the UE (via a SRB3 link, for example) a DLInformationTransfer IE to indicate that the UE should perform an RF tune away procedure. Finally, in <NUM>, having received the piggybacked information in the LTE NAS message from the gNB, the UE may then transmit a RRCReconfiguration Complete message to the gNB.

<FIG> illustrates a communication flow corresponding to a wireless device configured for EN-DC and DSDS operation. More specifically, <FIG> illustrates an example method of how a UE may initiate an RF tune away through use of piggybacking information in a NAS message. This may allow for simultaneous data transfer over the NR link in SIM1 while an active voice call is being performed on SIM2.

Next, in <NUM>, the UE may transmit a RRC/NAS message to the eNB. This message may indicate to the eNB that the UE should perform an RF tune away or may further correspond to the UE sending a short message service (SMS). Correspondingly, in <NUM> the UE may transmit, to the SIM1 gNB, an UEAssistanceInformation message on SRB3 piggybacked with the LTE NAS message. Furthermore, in <NUM>, having received the piggybacked LTE NAS information in the UEAssistanceInformation message from the UE, the gNB may then forward the LTE NAS information via a RRC Transfer message to the eNB. Correspondingly, in <NUM> the gNB may also send an RRCReconfiguration message piggybacked with the LTE NAS response message and an acknowledgement (ACK). Finally, in response to this and upon completing the RRC transfer procedure, the UE may transmit a RRCReconfiguration Complete message to the gNB in <NUM>.

<FIG> is a flow diagram corresponding to a wireless device configured for EN-DC and DSDS operation. More specifically, <FIG> illustrates an example method of how the network may assist a UE in maintaining its NR leg connection without breaking it due to a worsening RF connection. This may allow for simultaneous data transfer over the NR link in SIM1 while an active voice call is being performed on SIM2.

For example, in some embodiments and as shown in <NUM>, the wireless device (e.g., UE) may support MUSIM and include a first SIM (SIM1) in NSA DDS mode corresponding to an LTE connection with a MCG and a NR (mmWave) connection with a SCG. Furthermore, the UE may include a second SIM (SIM2) operating in LTE mode. Additionally, or alternatively in <NUM> the UE may perform an RF tune away operation to SIM2 corresponding to an LTE paging check.

Correspondingly, in <NUM>, SIM1's Tx/Rx resources may be disabled and may further be utilized by SIM2 in its NR leg through use of the mmWave antenna module with separate Tx/Rx capability. Additionally, or alternatively in <NUM> SIM2 may have an active voice call.

Accordingly, in 2010a, the AP may inform the baseband that SIM2 has an active voice call. Additionally, or alternatively in 2010b the UE may inform the gNB via MAC-CE or UCI to maintain the LTE RRC-state for "x" minutes instead of releasing the RRC connection due to timeout. Correspondingly, in 2010c, the gNB may forward this message to the eNB via the Xx-C interface and in response the eNB may optionally increase the RRC-release timer by "x" minutes in 2010d.

In <NUM>, it may be determined whether or not the NR leg has a SRB3 interface. For example, in 2014a if the NR leg is determined to have a SRB3 interface, the UE may be capable of sending NR-Measurement Reports (MRs) directly to the gNB and further maintain this NR leg even in mobility (e.g., roaming). Additionally, or alternatively in 2014b, if the NR leg is determined to lack a SRB3 interface and therefore the UE cannot send measurement reports, the UE may inform the gNB that the RF connection is degrading and to accordingly release the connection. For example, if the NR-RSRP reaches a level of -115dBm, the UE may inform the gNB to release the connection. In response, the gNB may additionally inform the eNB to release the RRC-connection of the LTE leg.

In <NUM>, once the voice call in SIM2 has ended (e.g., disconnected) and the UE has performed an RF tuning back to SIM1, the UE may inform the gNB that the MCG could become active in 2018a. Additionally, or alternatively, in 2018b, the gNB may receive altered PCI/EARFCN information and further transmit this information to the UE. Correspondingly, the UE may then perform a System Selection procedure on the SIM1 MCG in 2018c. Finally, in 2018d, the eNB may associate the RRC connection with the SCG so as to maintain the NR leg without breaking and re-making the connection.

the SIM1 gNB may then transmit a SGNB Modification Required message to the SIM1 eNB which may include IEs used to indicate a validity timer of "x" seconds and that the UE context should be retained. In response, the SIM1 eNB may transmit back to the SIM1 gNB a SGNB Modification Confirm message as shown in <NUM>. In <NUM>, the gNB may inform the UE (via MAC-CE and/or DCI) that all uplink/downlink (UL/DL) data could pass through the gNB over the NR leg.

Next, in <NUM>, the UE may transmit a RRC/NAS message to the eNB. This message may indicate to the eNB that the UE should perform an RF tune away. Correspondingly, in <NUM> the UE may transmit, to the SIM1 gNB, an LTE NAS message including UEAssistanceInformation on SRB3 piggybacked with the message. Furthermore, in <NUM>, having received the piggybacked information in the LTE NAS message from the UE, the gNB may then transmit a RRC Transfer message to the eNB. Correspondingly, in <NUM> the gNB may also send an RRCReconfiguration message piggybacked with the LTE NAS message and an acknowledgement (ACK). Finally, in response to this and upon completing the RRC transfer procedure, the UE may transmit a RRCReconfiguration Complete message to the gNB in <NUM>.

In some embodiments, a UE may be configured for MUSIM and have a first SIM (SIM1) supporting LTE and NR communications and a second SIM (SIM2) supporting LTE communications in an IDLE state. Based on SIM2's DRX cycle, SIM1's network may not schedule downlink data on SIM1. However, if SIM1 UE is performing an RF tune away procedure from the MCG leg, the network may still be able to utilize the SCG leg to schedule resources and transfer data to the UE. Accordingly, it may be beneficial for the UE to indicate to the network that SIM1 is performing said RF tune away from the MCG leg.

Still another example embodiment may include a device, comprising: an antenna; a radio coupled to the antenna; and a processing element operably coupled to the radio, wherein the device is configured to implement any or all parts of the preceding examples.

Yet another example embodiment may include a method, comprising: by a device: performing any or all parts of the preceding examples.

A further embodiment may include a non-transitory computer accessible memory medium comprising program instructions which, when executed at a device, cause the device to implement any or all parts of any of the preceding examples.

A still further example embodiment may include a computer program comprising instructions for performing any or all parts of any of the preceding examples.

A yet further example embodiment may include an apparatus comprising means for performing any or all of the elements of any of the preceding examples.

Still another example embodiment may include an apparatus comprising a processing element configured to cause a wireless device to perform any or all of the elements of any of the preceding examples.

For example some embodiments may be realized as a computer-implemented method, a computer-readable memory medium, or a computer system.

Claim 1:
A wireless device, comprising:
a first modem (<NUM>) for performing communication using a first radio access technology (RAT);
a second modem (<NUM>) for performing communication using a second RAT;
at least one processor coupled to the first and second modems (<NUM>; <NUM>), configured to:
establish, for simultaneous data transfer, a first connection using a first subscriber identity module, SIM, (<NUM>) to a first base station (<NUM>; 102A; 102B...102N) according to the first RAT and a second connection using the first SIM to a second base station (<NUM>; 102A; 102B...102N) according to the second RAT, wherein the connections correspond to an RRC-Connected state;
establish an additional connection, using a second SIM (<NUM>), to a third base station (<NUM>; 102A; 102B ...102N) according to the first RAT, wherein the additional connection corresponds to an RRC-Idle state;
perform a call using the second SIM (<NUM>) and according to the first RAT;
in response to performing the call using the second SIM (<NUM>): transmit (<NUM>),
using the first SIM (<NUM>), an indication to the second base station (<NUM>; 102A; 102B...102N) indicating that the first RAT for the first SIM (<NUM>) is to be disabled;
disable (<NUM>) the first RAT for the first SIM (<NUM>), wherein when the first RAT for the first SIM (<NUM>) is disabled, transmission (Tx) and reception (Rx) resources associated with the first RAT for the first SIM (<NUM>) are not utilizable by the wireless device for connection with the first base station (<NUM>; 102A; 102B...102N);
receive (<NUM>) from the second base station (<NUM>; 102A; 102B...102N), while the first RAT for the first SIM (<NUM>) is disabled and based at least in part on the indication, information indicating that all uplink/downlink data could pass through the second base station over the second connection and
perform, using the first SIM (<NUM>), the simultaneous data transfer over the second connection while the call is performed using the second SIM (<NUM>).