Multiple sim scheduling gap

Abstract

The present disclosure relates to multiple SIM scheduling gaps. A user equipment (UE) is configured to enter a radio resource control (RRC) connected state on a first network using a first subscriber identity module (SIM) and enter an RRC inactive state or an RRC idle state on a second network using a second SIM, transmit, to the first network, a request for a scheduling gap (SG) configuration in which the first network refrains from scheduling resources to the UE during a duration of the SG, receive, from the first network, an indication of the SG configuration to use, tune away from the first network to perform operations on the second network during the duration of the SG, and tune back to the first network after the duration of the SG, wherein the RRC connected state is maintained on the first network during the duration of the SG.

Description

[0001] This application is a divisional application of invention patent application 202180012264.7 entitled "Multi-SIM Scheduling Gap", filed on August 5, 2021. Technical Field

[0002] This application generally relates to wireless communication, and more specifically to multi-SIM scheduling gaps. Background Technology

[0003] User equipment (UE) can be equipped with multiple user identity modules (SIMs), and each SIM enables the UE to establish an independent network connection. Therefore, a multi-SIM UE can use a first SIM to establish a first network connection and a second SIM to establish a second network connection.

[0004] During multi-SIM operation, the UE can currently perform operations in a Radio Resource Control (RRC) connected state with the first network while remaining in an idle or inactive state with the second network. The UE can temporarily switch its operations from the first network to the second network, for example, to listen for paging messages or receive system information from the second network, perform Public Land Mobile Network (PLMN) search, cell recovery, or any other user-triggered protocol activity. Summary of the Invention

[0005] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. These operations include: entering a Radio Resource Control (RRC) connected state on a first network using a first User Identity Module (SIM), and entering an RRC inactive state or an RRC idle state on a second network using a second SIM; transmitting a request to the first network for a scheduling gap (SG) configuration, wherein the first network avoids scheduling resources for the UE during the duration of the SG; receiving an indication from the first network of the SG configuration to be used; tuning away from the first network to perform operations on the second network during the duration of the SG; and tuning back to the first network after the duration of the SG, wherein the RRC connected state was maintained on the first network during the duration of the SG.

[0006] Other exemplary embodiments relate to a processor of a user equipment (UE) configured to perform operations. The operations include: entering a Radio Resource Control (RRC) connected state on a first network using a first User Identity Module (SIM), and entering an RRC inactive state or an RRC idle state on a second network using a second SIM; transmitting to the first network an indication of the ability to perform a Scheduling Gap (SG) configuration, wherein the first network avoids scheduling resources for the UE during the duration of the SG; receiving from the first network an indication of the SG configuration to be used; tuning away from the first network to perform operations on the second network during the duration of the SG; and tuning back to the first network after the duration of the SG, wherein the RRC connected state was maintained on the first network during the duration of the SG.

[0007] Another exemplary embodiment relates to a processor of a base station of a first network configured to perform an operation. The operation includes: entering a Radio Resource Control (RRC) connection state with a user equipment, wherein the UE accesses the first network using a first User Identity Module (SIM), wherein the UE also enters an RRC inactive state or an RRC idle state in a second network using a second SIM; receiving from the UE a request for a scheduling gap (SG) configuration, wherein during the duration of the SG, the first network avoids scheduling resources for the UE; transmitting to the UE an indication of the SG configuration to be used, wherein during the duration of the SG, the UE tunes away from the first network to perform the operation on the second network; and maintaining the RRC connection state with the UE during the duration of the SG.

[0008] Additional exemplary embodiments relate to a processor of a base station of a first network configured to perform operations. The operations include: entering a Radio Resource Control (RRC) connection state with a user equipment (UE), wherein the UE accesses the first network using a first User Identity Module (SIM), and wherein the UE also enters an RRC inactive state or an RRC idle state on a second network using a second SIM; receiving from the UE an indication of the ability to perform a Scheduling Gap (SG) configuration, wherein during the duration of the SG, the first network avoids scheduling resources for the UE; transmitting to the UE an indication of the SG configuration to be used, wherein during the duration of the SG, the UE tunes away from the first network to perform operations on the second network; and maintaining the RRC connection state with the UE during the duration of the SG. Attached Figure Description

[0009] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0010] Figure 2 Exemplary multi-SIM UEs according to various exemplary implementations are shown.

[0011] Figure 3 An exemplary network base station according to various exemplary embodiments is shown.

[0012] Figure 4 An exemplary signaling diagram of scheduling gap (SG) operation according to various exemplary embodiments is shown.

[0013] Figure 5 An exemplary signaling diagram of scheduling gap (SG) operation according to a first option is shown according to various exemplary embodiments.

[0014] Figure 6 An exemplary signaling diagram is shown, based on various exemplary embodiments, of a scheduling gap (SG) activated according to a first option.

[0015] Figure 7 Signaling diagrams are shown for scheduling gap configuration and activation according to the second option, based on various exemplary embodiments.

[0016] Figure 8 Signaling diagrams for deactivating scheduling gaps according to various exemplary implementations are shown.

[0017] Figure 9 A first exemplary method for configuring and activating / deactivating scheduling gaps according to various exemplary implementations is shown.

[0018] Figure 10 A second exemplary method for configuring and activating / deactivating scheduling gaps according to various exemplary implementations is shown. Detailed Implementation

[0019] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. This exemplary embodiment describes devices, systems, and methods for a user equipment (UE) to implement one or more scheduling gaps (SGs) during its operation with a first network to temporarily tune away from the first network to perform operations on a second network. As will be described below, this exemplary embodiment relates to a UE equipped with multiple user identity modules (SIMs).

[0020] The exemplary embodiments are described with respect to the UE. However, reference to the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component capable of establishing a connection to a network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein is used to represent any electronic component.

[0021] Throughout this specification, the UE is characterized as a multi-SIM UE. The term "multi-SIM UE" can refer to a UE equipped with multiple (e.g., two or more) SIMs. Each SIM can be used to establish an independent network connection, and each network connection can exist simultaneously. Therefore, each SIM can be associated with its own phone number and / or a subscription with a cellular service provider. Thus, a single UE can be associated with two or more phone numbers and / or subscriptions. Throughout this specification, SIM A and SIM B will be referenced for the purpose of distinguishing SIMs. However, this is only intended to distinguish between two SIMs and is not intended to indicate any type of priority / preference between either SIM A or SIM B. Furthermore, the descriptions of SIM A, SIM B, NW A, and NW B are for illustrative purposes only, and the principles described in this disclosure can be applied to any number of SIMs and network combinations.

[0022] Those skilled in the art will understand that a SIM contains information used by a UE to establish a network connection. For example, a SIM may include an International Mobile Subscriber Identifier (IMSI) that can be used to authenticate with a network provider. A user may have a first subscription with a cellular service provider enabled by SIM A and a second subscription with a cellular service provider enabled by SIM B. The network that a UE can use SIM A to connect to may be referred to as Network A (NW A), and the network that a UE can use SIM B to connect to may be referred to as Network B (NW B). In one example, the same cellular service provider is associated with both SIM A and SIM B. In another example, different cellular service providers are associated with each SIM. References to any particular type of information contained within a SIM are provided for illustrative purposes only. A SIM may contain a wide variety of different types of information that may be referred to by different names for different networks or different entities. Therefore, exemplary embodiments are applicable to SIMs containing any type of information used by multi-SIM UEs to establish network connections.

[0023] An exemplary embodiment will be described with respect to a multi-SIM UE equipped with two SIMs (e.g., SIM A and SIM B). However, those skilled in the art will understand that the exemplary embodiment is also applicable to devices with more than two SIMs.

[0024] A multi-SIM UE can utilize the same hardware, software, and / or firmware components to perform operations related to both the network connection associated with SIM A and the network connection associated with SIM B. For example, a multi-SIM UE can be configured to use the same transceiver to perform operations related to both network connections. Using the same components to perform operations for both network connections can create scenarios where a multi-SIM UE cannot perform operations related to the network connection associated with either SIM A or SIM B, because the multi-SIM UE is currently using that component to perform operations related to the network connection associated with another SIM.

[0025] During RRC connection operation with NW A, a multi-SIM UE can be in an RRC inactive state or an RRC idle state on NW B. An exemplary implementation describes configuring a scheduling gap (SG) on NW A that allows the UE to temporarily tune away from NW A to perform operations on NW B. During the SG, the UE can maintain an RRC connection state on NW A such that when the UE retunes to NW A after the SG duration, the UE and NW A can resume normal RRC connection operation without transitioning back to the RRC connected state from either the RRC idle state or the RRC inactive state.

[0026] Figure 1 A network arrangement 100 according to an exemplary embodiment is illustrated. The network arrangement 100 includes a multi-SIM UE 110, which comprises at least two SIMs. Those skilled in the art will understand that the multi-SIM UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet, smartphone, phablet, embedded device, wearable device, Cat-M device, Cat-M1 device, MTC device, eMTC device, other types of Internet of Things (IoT) devices, etc. A practical network arrangement can include any number of UEs used by any number of users. Therefore, the example of a single multi-SIM UE 110 is provided merely for illustrative purposes.

[0027] The multi-SIM UE 110 can communicate with one or more networks. In the example of network configuration 100, the networks with which the multi-SIM UE 110 can wirelessly communicate are a 5G New Radio (NR) radio access network (5G NR-RAN) 120, an LTE radio access network (LTE-RAN) 122, a legacy access network (legacy RAN), and a wireless local access network (WLAN) 126. However, the multi-SIM UE 110 can also communicate with other types of networks, and the multi-SIM UE 110 can also communicate with networks via a wired connection. Therefore, the multi-SIM UE 110 may include a 5G NR chipset communicating with the 5G NR-RAN 120, an LTE chipset communicating with the LTE-RAN 122, a legacy chipset communicating with the legacy RAN 124, and an ISM chipset communicating with the WLAN 126.

[0028] The multi-SIM UE 110 can establish multiple independent network connections that can coexist. For example, the multi-SIM UE 110 can use SIM A to establish a first network connection and SIM B to establish a second network connection. The first and second network connections can be independent of each other and coexist. In the example of network configuration 100, the multi-SIM UE 110 pre-occupies the gNB 120A of 5G NR-RAN 120 for the first network connection and the eNB 122A of LTE-RAN 122 for the second network connection. However, this is provided for illustrative purposes only. For example, the multi-SIM UE 110 can establish a first network connection to 5G NR-RAN 120 via gNB 120A and a second network connection to traditional RAN 124 via the corresponding base station 124A. Therefore, in actual network configuration, the multi-SIM UE110 can camp on a first cell corresponding to the first network for the first network connection and a second cell corresponding to the second network for the second network connection.

[0029] 5G NR-RAN 120, LTE-RAN 122, and traditional RAN 124 can be parts of a cellular network that can be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122, and 124 may include, for example, base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 126 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0030] Base stations (e.g., gNB 120A, eNB 122A, base station 124A) may include one or more communication interfaces to exchange data and / or information with the pre-assigned UE, the corresponding RAN, cellular core network 130, Internet 140, etc. Furthermore, the base station may include a processor configured to perform various operations. For example, the base station's processor may be configured to perform paging-related operations. However, references to processors are for illustrative purposes only. The operation of the base station may also be represented as a standalone component of the base station, or as a modular component coupled to the base station, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some base stations, the functionality of the processor is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary embodiments may be implemented according to any of these or other configurations of the base station.

[0031] Those skilled in the art will understand that any relevant procedures can be performed to connect the multi-SIM UE 110 to 5G NR-RAN 120, LTE-RAN 122, and legacy RAN 124. For example, the 5G NR-RAN 120 can be associated with a specific cellular service provider where the multi-SIM UE 110 and / or its users have protocol and credential information (e.g., stored on each of SIM A and SIM B). In the case of the multi-SIM UE 110, each SIM will connect independently to its corresponding network. Upon detecting the presence of the 5G NR-RAN 120, the multi-SIM UE 110 can transmit the corresponding credential information to associate with the 5G NR-RAN 120. More specifically, the multi-SIM UE 110 can be associated with a specific cell (e.g., gNB 120A of the 5G NR-RAN 120). Similar association procedures can be performed for the multi-SIM UE 110 to connect to LTE-RAN 122 and legacy RAN 124.

[0032] In addition to networks 120, 122, 124, and 126, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the multi-SIM UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the multi-SIM UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the multi-SIM UE 110 to communicate with various networks.

[0033] Figure 2 An exemplary multi-SIM UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe the multi-SIM UE 110. The multi-SIM UE 110 can represent any electronic device and may include a processor 205, a memory layout 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, a battery providing a limited power source, data acquisition devices, ports for electrically connecting the multi-SIM UE 110 to other electronic devices, sensors for detecting the status of the UE 110, etc. The multi-SIM UE 110 may include SIM A 240 and SIM B 245. However, as described above, the exemplary embodiment can be applied to UEs equipped with more than two SIMs.

[0034] Processor 205 can be configured to execute multiple engines for the multi-SIM UE 110. For example, an engine may include a scheduling gap engine 235. Scheduling gap engine 235 can perform operations configured for scheduling gaps (SGs) for network operations, during which the UE 110 may temporarily tune away from the current network connection to perform operations on a second network. Examples of these operations will be described in more detail below.

[0035] The engine described above, as an application (e.g., a program) executed by processor 205, is merely exemplary. The functionality associated with the engine can also be represented as a separate integrated component of the multi-SIM UE 110, or as a modular component coupled to the multi-SIM UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine can also be embodied as one application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0036] Memory 210 may be a hardware component configured to store data related to operations performed by the multi-SIM UE 110. As will be described in further detail below, memory 210 may store data associated with the status of the multi-SIM UE 110 when determining an operating mode. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with LTE-RAN 120, LTE-RAN 122, legacy RAN 124, and WLAN 126, etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., consecutive frequency groups).

[0037] Figure 3 An exemplary network cell, in this example gNB 120A, is shown according to various exemplary aspects. As described above with respect to UE 110, gNB 120A may represent the serving cell of UE 110. gNB 120A may represent any access node belonging to the 5G NR network that UE 110 can use to establish connections and manage network operations.

[0038] The gNB 120A may include a processor 305, a memory arrangement 310, input / output (I / O) devices 320, a transceiver 325, and other components 330. Other components 330 may include, for example, audio input devices, audio output devices, a battery, data acquisition devices, and ports for electrically connecting the gNB 120A to other electronic devices.

[0039] Processor 305 can be configured to execute multiple engines of gNB 120A. For example, an engine may include a scheduling gap engine 335 for performing operations including configuring a scheduling gap (SG) for UE 110, during which UE 110 may temporarily tune away from the current network connection to perform operations on a second network. Examples of these operations will be described in more detail below.

[0040] The engines described above, each acting as an application (e.g., a program) executed by processor 305, are merely exemplary. The functionality associated with the engines may also be represented as a separate integrated component of gNB 120A, or as a modular component coupled to gNB 120A, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Furthermore, in some gNBs, the functionality described for processor 305 is split among multiple processors (e.g., a baseband processor, an application processor, etc.). Exemplary aspects may be implemented according to any configuration of these or other configurations of the gNB.

[0041] Memory 310 may be a hardware component configured to store data related to operations performed by UE 110. I / O device 320 may be a hardware component or port enabling a user to interact with gNB 120A. Transceiver 325 may be a hardware component configured to exchange data with UE 110 and any other UE in system 100. Transceiver 325 may operate on a variety of different frequencies or channels (e.g., a set of consecutive frequencies). Therefore, transceiver 325 may include one or more components (e.g., radio components) to enable data exchange with various networks and UEs.

[0042] The Radio Resource Control (RRC) protocol includes a state machine that defines the operational states of a UE, each state having a different radio resource associated with it. In 5G NR and LTE, RRC states include RRC Connected State, RRC Inactive State, and RRC Idle State. The UE enters the RRC Idle State upon power-up and can perform operations including receiving broadcast messages, receiving paging messages, PLMN selection, and cell reselection mobility. While in the RRC Idle State, the UE follows a Discontinuous Receive (DRX) cycle for periodic wake-up to listen for paging messages from the network. The UE can perform initial access operations (including the Random Access (RACH) procedure) to pre-occupy a network cell and enter the RRC Connected State to establish a network connection and exchange transmissions. If, while in the RRC Connected State, there is no communication traffic to or from the UE for some predefined time period, the network can suspend the RRC connection and instruct the UE to enter the RRC Inactive State. In the RRC Inactive State, the UE can perform operations similar to those in the RRC Idle State. Additionally, the access layer (AS) context can be stored at both the UE and the network, allowing the UE to quickly re-enter the RRC connection state using a recovery process when the UE / network receives network activity targeting the UE.

[0043] Regarding dynamic handover between two pre-owned networks A and B (NW A and NW B), a multi-SIM UE (MUSIM UE) may encounter the following two scenarios. In the first scenario, the UE is in an RRC connected state on NW A and attempts to perform a network handover to NW B without leaving the RRC connected state on NW A. In the second scenario, the UE is in an RRC connected state on NW A and attempts to perform a network handover to NW B that includes leaving the RRC connected state on NW A. In the second scenario, this use case requires establishing an RRC connection on NW B.

[0044] Regarding the first scenario, network handover between NW A and NW B can be achieved by creating a scheduling gap (SG) on NW A, without leaving the RRC connection state on NW A. The SG provides a mechanism between the multi-SIM UE and NW A for the UE to temporarily switch from its operation on NW A to perform some other protocol activities on NW B. During the handover period defined by the SG, NW A stops scheduling resources (DL and UL) to the multi-SIM UE. The UE performs operations with NW B and hands back to NW A when the SG ends. When the multi-SIM UE hands back to NW A, the UE can resume normal RRC connection mode operation with NW A. In this method, the handover of the MUSIM UE from NW A to NW B and back to NW A is coordinated with NW A.

[0045] Figure 4 An exemplary signaling diagram 400 is shown illustrating scheduling gap (SG) operation according to various exemplary embodiments described herein. Signaling diagram 400 includes a multi-SIM UE 405 performing operations with a first network (NW A) 410 and a second network (NW B) 415. As described above, NW A 410 may refer to UE 405 with its network having a subscription enabled by the first SIM (SIM A), and NW B 415 may refer to UE 405 with its network having a subscription enabled by the second SIM (SIM B). NW A 410 and NW B 415 may refer to the same network or different networks (e.g., PLMN). UE 405 may represent the above-described... Figure 1 The description refers to a multi-SIM UE 110. NW A 410 and NW B 415 may refer to a 5G NR-RAN 120, which can be accessed by UE 405 via gNB 120A. Alternatively, NW A 410 and NW B 415 may be accessed by UE 405 via different gNBs. Additionally, NW A 410 and NW B 415 may refer to different networks that can be accessed by the UE via the same access node or different access nodes.

[0046] In 420, UE 405 enters an RRC idle or RRC inactive state with NW B 415. For example, UE 405 may have previously been in an RRC connected state with NW B 415 and transitioned to an idle / inactive state, or the SIM B used to connect to the NWB may have recently been activated.

[0047] In step 425, UE 405 enters the RRC connection state with NWA 410. Step 425 requires UE 405 to tune to NWA 410 to perform network operations with NWA 410 to establish an RRC connection. As part of the initial registration process, UE 405 may report its UE capabilities for network handover to NWA 410. Additionally, as part of the initial RACH procedure, recovery procedure, or reconfiguration procedure, the UE may request a scheduling gap (SG) configuration from NWA 410, which will be described in further detail below.

[0048] In 430, the NWA 410 configures a scheduling gap (SG) for UE 405. As will be described in further detail below, the SG can be requested by the UE. The request may only include an indication of the required SG, or it may include additional parameters of the SG, including the SG type (periodic / non-periodic) and the timing aspect of the SG. In one implementation, the network configures a set of SGs, wherein one or more of the configured SGs can be activated by the UE based on the use case of the operation to be performed on the NWA.

[0049] In 435, during the duration prior to the start of SG, UE 405 and NWA 410 perform communication exchanges while in RRC connected state.

[0050] In 440, the SG begins in the time domain. During the agreed SG period, NWA 410 will not schedule any resources for UE405 to transmit / receive data with NWA 410 during the SG period. Multi-SIM UE 405 leaves NWA 410 and tunes to NWA B 415, but maintains its RRC connection state with NWA 410.

[0051] In 445, UE 405 performs pre-scheduled protocol activities with NW B 415 during SG. These activities may involve, for example, listening to paging messages, performing mobility measurements, receiving system information (SI) broadcasts, etc., which will be described in further detail below. It is worth noting that in this example, UE 405 does not enter RRC connected state on NW B 415, but remains in an RRC inactive or RRC idle state on NW B 415. If it is to enter RRC connected state on NW B 415 and the MUSIM UE does not have two independent Rx and Tx capabilities (e.g., it is a dual Rx / single Tx or single Rx / single Tx UE), the RRC connection on NW A is released. If the MUSIM UE has dual Rx / dual Tx capabilities, the RRC connected state can be maintained on NW A even when entering RRC connected state on NW B.

[0052] In 450, SG ends in the time domain. Multi-SIM UE 405 leaves NW B 415 and tunes to NW A 410. In 455, after retuning to NW A 410, NW A 410 resumes scheduling resources for UE 405 in RRC connected state.

[0053] Different types of scheduling intervals (SGs) can be configured based on the reason the UE is triggered to switch the network from NW A to NW B. The first type of SG is a periodic SG involving only Rx activity on NW B and no Tx activity. For example, during a first-type SG, the UE can perform idle / inactive paging surveillance on NW B. Alternatively, the UE can perform primary serving cell (PCell) measurements or neighboring cell (NCell) measurements (inter-frequency, intra-frequency, or inter-RAT) on NW B. The second type of SG is a non-periodic SG involving only Rx activity on NW B and no Tx activity. For example, during a second-type SG, the UE can perform a single measurement, PLMN search, or SI acquisition on NW B. The third type of SG is a non-periodic SG involving both Tx and Rx activities, where the UE does not enter RRC connected state on NW B. For example, during a third-type SG, the UE can perform on-demand SI acquisition on NW B. The fourth type of SG is a non-periodic SG involving both Tx and Rx activities, in which the UE enters the RRC connected state on NW B. For example, during the fourth type of SG, the UE can perform periodic TAU / RANU signaling, send a BUSY indicator, etc. When the UE enters the RRC connected state on NW B, the UE exits the RRC connected state on NW A.

[0054] As described above, the UE can perform various types of operations on the NW B. The exemplary implementation described herein relates to a signaling scheme for configuring scheduling gaps on the NW A based on various use cases for the NW B.

[0055] According to some exemplary implementations, the UE transmits a request for a scheduling gap (SG) to a first network (e.g., NW A), for example, indicating to the first network its need for an SG. In response, the first network may configure a set of SGs for the UE, wherein the UE may activate one or more SGs based on its intended use case with a second network (e.g., NW B).

[0056] The type of message used by the UE to indicate a need for an SG can depend on the UE's current RRC state with the network. If the UE enters a connected state from an idle state, for example, by performing a RACH procedure with the network, the UE can indicate a need for an SG in the RRCSetupRequest message (Msg3). If the UE enters a connected state from an inactive state, for example, by restoring an RRC connection, the UE can indicate a need for an SG in the RRCResumeRequest message. If the UE is already in a connected state, the UE can indicate a need for an SG in the UEAssistanceInformation message. In any of these cases, the UE can indicate additional information about the intended use case on the NW B, such as the idle / inactive DRX length on the NW B. However, given the limited space available in RRCSetupRequest and RRCResumeRequest, it may be more practical to simply signal the need for an SG (including a single bit) in both message types.

[0057] As part of the network configuration of the SG, which will be described in further detail below, a disable timer can be defined to ensure the proper use of the SG request by the UE by the network. The UE can only re-initiate a scheduling gap request to the network until the disable timer expires. Once the disable timer expires, if the network still has not configured the expected SG for the UE, the UE is allowed to re-request the SG. The new requested SG can be the same as the previous request, or it can include new parameters to request a new SG configuration.

[0058] After receiving an SG mode request, the network can configure a set of SGs, where each gap configuration is uniquely identified by a gap ID. This configuration can be sent as part of a response to a request message, such as an RRCSetup message (in response to an RRCSetupRequest message), an RRCResume message (in response to an RRCResumeRequest message), or an RRCReconfiguration message (in response to a UEAssistanceInformation message).

[0059] Figure 5An exemplary signaling diagram 500 is shown, configured according to a scheduling gap (SG) of a first option. Similar to signaling diagram 400, signaling diagram 500 includes a multi-SIM UE 505 performing operations with a first network (NW A) 510 and a second network (NW B) 515. As described above, NW A 510 may refer to the UE 505 and its network having a subscription enabled by the first SIM (SIM A), and NW B 515 may refer to the UE 505 and its network having a subscription enabled by the second SIM (SIM B), wherein NW A 510 and NW B 515 may refer to the same network or different networks accessed by the UE 505.

[0060] In 520, similar to 420, UE 505 enters the RRC idle state or RRC inactive state with NW B 515.

[0061] Box 525 represents a method for configuring one or more SGs for UE 505 according to a first alternative scheme, wherein UE 505 begins in an idle state on NWA 510, as described above. In 530, as part of the RACH procedure, UE 505 sends a Multi-SIM (MUSIM) Scheduling Gap (SG) request to NWA 510 as part of an RRCSetupRequest message (Msg3). In 535, UE 505 receives the MUSIM SG configuration from NWA 510 as part of an RRCSetup message (Msg4). In 540, UE 505 sends an RRCSetupComplete message on the uplink resources allocated to NWA 510 and is in an RRC connected state.

[0062] Box 545 illustrates a method for configuring one or more SGs for UE 505 according to a second alternative scheme, wherein UE 505 begins in an inactive state on NWA 510, as described above. In 550, the inactive UE 505 sends a MUSIM SG request to NWA 510 as part of an RRCResumeRequest message. In 555, UE 505 receives a MUSIM SG configuration from NWA 510 as part of an RRCResume message. In 560, UE 505 sends an RRCResumeComplete message on the uplink resources allocated to NWA 510 and is in an RRC connected state.

[0063] Box 565 represents a method for configuring one or more SGs for UE 505 according to a third alternative scheme, wherein UE 505 begins in a connected state on NW A 510, as described above. In 570, UE 505 sends a MUSIM SG request to NW A 510 as part of a UEAssistanceInformation message. In the SG request, UE 505 may include parameters related to the intended use case on NW B, such as DRX loop information. In 575, UE 505 receives the MUSIM SG configuration from NW A 510 as part of an RRCReconfiguration message. In 580, UE 505 sends an RRCReconfigurationComplete message on the uplink resources allocated to NW A 510 and remains in an RRC connected state.

[0064] The scheduling gaps configured in the network can include the following information: SG type (e.g., periodic or aperiodic (one-off)), SG timing lead, and SG length. Additionally, when the SG is periodic, the periodicity of the SG is configured. Each gap configuration in the gap configuration is associated with a unique gap ID, such as gap ID 1, gap ID 2, etc. As mentioned above, the SG configuration can also include parameters defining the disabling of timers.

[0065] The MUSIM scheduling interval configuration can include the following information elements. Note that the values ​​used are empirical and the actual values ​​used may differ.

[0066] MUSIMSchedulingGapConfig :: = SEQUENCE {

[0067] SchedulingGapPeriodic SEQUENCE OF PeriodicGap of size M, SchedulingGapAperiodic SEQUENCE OF AperiodicGap of size N } PeriodicGap :: = SEQUENCE { PeriodicGapID gapId, / Unique value within this array of size M / SchedulingGapAdvance value {0 ms, 0.25 ms, 0.5 ms, …}, SchedulingGapLength value {1 ms, 2 ms, …} SchedulingGapPeriodicity value {320 ms, 640 ms, 1280 ms, 2560 ms.} } AperiodicGap :: = SEQUENCE { AperiodicGapID gapId, / Unique value within this array of size N / SchedulingGapAdvance value {0 ms, 0.25 ms, 0.5 ms, …}, SchedulingGapLength value {1 ms, 2 ms, …} } After configuring a set of SGs for the UE, while the UE is in an RRC connected state on the network, the UE determines a suitable gap from a set of available SGs (periodic and / or non-periodic) configured by the network based on its current use case on the NWB. The UE can activate the selected gap in at least two ways. In some implementations, the gap can be indicated as part of a UEAssistanceInformation message, in which the gap ID for the selected SG configuration is included. The network confirms to the UE the active current set of SG configuration as part of an RRCReconfiguration message. In other implementations, the gap can be indicated in an uplink (UL) media access control (MAC) control element (CE), in which the gap ID for the selected SG configuration is included. The network confirms to the UE the active current set of SG configuration in a downlink (DL) MAC CE. These exemplary UL MAC CEs and DL MAC CEs can be added to existing CE definitions, or new MAC CEs can be defined for this purpose.

[0068] Figure 6An exemplary signaling diagram 600 is shown, activated according to a scheduling gap (SG) of a first option. Similar to the previous method, signaling diagram 600 includes a multi-SIM UE 605 performing operations with a first network (NW A) 610 and a second network (NW B) 615. As described above, NW A 610 may refer to the UE 605 and its network having a subscription enabled by the first SIM (SIM A), and NW B 615 may refer to the UE 605 and its network having a subscription enabled by the second SIM (SIM B), wherein NW A 610 and NW B 615 may refer to the same network or different networks accessed by the UE 605.

[0069] In 620, similar to the previous method, UE 605 enters an RRC idle state or an RRC inactive state with NW B 615. In 625, UE 605 enters an RRC connected state with NW A 610 and is configured with a set of SG configurations, such as those described above relative to... Figure 5 One of the three options discussed.

[0070] In 630, UE 605 determines which SG(s) of a set of SG(s) to activate based on the current use case for NW B 615. Figure 6 In the example, UE 605 determines that a periodic gap with ID 1 should be activated, for example, to listen for paging messages, and an aperiodic gap with ID 2 should be activated, for example, for SI acquisition.

[0071] Box 635 illustrates a method for activating one or more SGs for UE 605 according to a first alternative scheme, wherein UE 605, in a connected state, requests the selected gap using RRC signaling, as described above. In 640, UE 605 sends the gap ID of the selected gap as part of a UEAssistanceInformation message to NWA 610. In 645, UE 605 receives the gap ID of the selected SG as part of an RRCReconfiguration message from NWA 610 as confirmation of the selected SG. In 650, UE 605 sends an RRCReconfigurationComplete message on the uplink resources allocated by NWA 610.

[0072] Box 655 represents a method for activating one or more SGs for UE 605 according to a second alternative scheme, wherein UE 605, in a connected state, uses a MAC CE to request a selected gap, as described above. In 660, UE 605 sends the gap ID of the selected gap as part of a UL MAC CE to NWA 610. In 665, UE 605 receives the gap ID of the selected SG as part of a DL MAC CE from NWA 610 as confirmation of the selected SG.

[0073] In 670, UE 605 and NWA 610 operate according to the active SG. For example, as described above, NWA 610 does not schedule any resources for UE 605 to transmit / receive data with NWA 610 during the active SG. Multi-SIM UE 605 leaves NWA 610 and tunes to NW B 615, but maintains its RRC connection state with NWA 610. UE 605 performs pre-scheduled protocol activities with NW B 615 during the SG.

[0074] According to other exemplary embodiments, the multi-SIM UE determines the desired SG mode based on its current use case on the NW B. In contrast to the exemplary embodiments described above, where the multi-SIM UE requests a scheduling gap and provides input parameters for calculating the scheduling gap on the NW A, in these exemplary embodiments, the multi-SIM UE determines the scheduling gap mode based on the idle / inactive DRX configuration of the NW B. It should be noted that these exemplary embodiments are applicable to UEs already in the RRC_CONNECTED state on the NW A.

[0075] According to the second implementation, the multi-SIM UE sends a UEAssistanceInformation message to the network (e.g., NW A) indicating a preferred scheduling gap based on the expected use case with the second network (e.g., NW B). The UE can provide the following information: SG type (e.g., periodic or aperiodic (one-off)), SG timing lead, SG length, or any other parameter used to characterize the SG. Additionally, when the SG is periodic, the periodicity of the SG can be indicated. The UE can indicate a set of gap configurations, each associated with a unique gap ID.

[0076] Similar to the first implementation, a timer is disabled to ensure the proper use of the scheduling gap request from the UE. The network can send an RRCReconfiguration message upon receiving a scheduling gap mode from the UE, indicating that it is acknowledging the scheduling gap mode from the MUSIM UE. Alternatively, the network can use a DL MAC CE to acknowledge the SG mode requested by the UE.

[0077] Figure 7 Signaling diagram 700 is shown, configured and activated according to the scheduling gap of the second option. Similar to the previous method, signaling diagram 700 includes a multi-SIM UE 705 performing operations with a first network (NW A) 710 and a second network (NW B) 715. In 720, similar to the previous method, UE 705 enters an RRC idle state or an RRC inactive state with NW B 715.

[0078] In 725, UE 705 enters the RRC connection state with NWA 710 and sends one or more SG configurations and associated gap IDs as part of the UEAssistanceInformation message to NWA 710.

[0079] Box 730 represents a first method for confirming the SG configuration requested by UE 705 according to the first option discussed above. In box 735, UE 705 receives the gap ID of the requested SG as part of an RRCReconfiguration message from NWA 710 as confirmation of the requested SG. In box 740, UE 705 sends an RRCReconfigurationComplete message on the uplink resources allocated by NWA 710 to activate the requested SG.

[0080] Box 745 represents a second method for confirming the SG configuration requested by UE 705 according to the second option discussed above. In 750, UE 705 transmits the gap ID of the requested SG to NWA 710 to activate the requested SG. In 755, UE 705 receives the gap ID of the requested SG from NWA 710 as part of the downlink MAC CE, as confirmation of the requested SG.

[0081] Regarding disabling timers, compared to the aforementioned implementation, the timer can first be configured by the network as part of any connection state configuration (e.g., RRCConnectionReconfiguration). This reconfig message can indicate a timer value, such as T_MUSIM_SG_PROHIBIT, with values ​​in seconds, such as 1 second, 2 seconds, 5 seconds, 30 seconds, 60 seconds, etc., where the specification can indicate a list of valid timer values, and the reconfig message indicates a value from that list.

[0082] As part of capability signaling, such as to NR or LTE, the MUSIM UE can advertise its MUSIM capabilities and SG request capabilities. The network can then indicate its support for SG request processing for MUSIM purposes by configuring a disable timer value. The presence of this timer value from the network to the UE means that the network allows the UE to request SG configuration as needed. The absence of this timer value from the network to the UE means that the network does not allow the UE to request MUSIM SG configuration.

[0083] During its RRC connection operation mode, the UE can determine the need to request a scheduling gap from the NW A based on some upcoming activities on the NW B. After the UE sends a request for the SG to the NW A (as a request for SG configuration according to the first exemplary embodiment or when sending SG configuration as in the second exemplary embodiment), the UE then initiates T_MUSIM_SG_PROHIBIT. When T_MUSIM_SG_PROHIBIT is running, the UE does not retransmit the previous SG request, but waits for the NW to provide SG configuration (first embodiment) or confirmation that the requested scheduling gap configuration is active (second embodiment).

[0084] In one scenario, once T_MUSIM_SG_PROHIBIT times out and the UE has not yet obtained SG configuration from the NWA, the UE is allowed to re-request the same MUSIM SG configuration or any different SG configuration and restart the T_MUSIM_SG_PROHIBIT timer. In another scenario, if the NWA has provided the requested SG configuration and if T_MUSIM_SG_PROHIBIT is running, the UE stops T_MUSIM_SG_PROHIBIT.

[0085] According to another implementation, while in an RRC connected state on NW A, the UE can request the cancellation of a previously requested SG when it is no longer needed. For example, when the UE loses service on NW B, the idle / inactive DRX monitoring periodic SG is no longer needed. While in an RRC connected state on NW A, NW A can reconfigure a set of available SGs. In such cases, the UE must delete the previously stored set of SGs and store a new set of SGs. It should be noted that regardless of the method used to configure / activate the SG, the described SGs can be used for deactivation, as described above in the first and second exemplary implementations.

[0086] Figure 8Signaling diagram 800 for deactivating scheduling gaps according to various exemplary embodiments described herein is illustrated. Similar to previous methods, signaling diagram 800 includes a multi-SIM UE 805 performing operations with a first network (NW A) 810 and a second network (NW B) 815.

[0087] In 820, similar to the previous method, UE 805 enters an RRC idle state or an RRC inactive state with NW B 815. In 825, UE 805 enters an RRC connected state with NW A 810 and is configured with a set of SG configurations, such as those described above relative to... Figure 5 One of the three options discussed.

[0088] In 830, UE 805 determines which (or which) of a set of active SG configurations to deactivate based on the current use case for NW B 815. Figure 8 In the example, UE 805 determines that the periodic gap with ID 1 should be deactivated, and the aperiodic gap with ID 2 should be deactivated. However, UE 805 may determine to deactivate a subgroup of configured SGs. For example, UE 805 may determine that the SG with ID 1 should be deactivated, but the SG with ID 2 should remain active.

[0089] Box 835 illustrates a method for deactivating one or more SGs for UE 805 according to a first alternative scheme, wherein the connected UE 805 uses RRC signaling to request the deactivation of the selected gap. In box 840, UE 805 sends the gap ID of the selected gap to be deactivated as part of a UEAssistanceInformation message to NWA 810. In box 845, UE 805 receives the gap ID of the selected SG as part of an RRCReconfiguration message from NWA 810 as confirmation of the deactivation of the selected SG. In box 850, UE 805 sends an RRCReconfigurationComplete message on the uplink resources allocated by NWA 810.

[0090] Box 855 represents a method for deactivating one or more SGs for UE 805 according to a second alternative scheme, wherein the connected UE 805 uses a MAC CE to request the deactivation of the selected gap, as described above. In 860, UE 805 sends the gap ID of the selected gap to be deactivated as part of a UL MAC CE to NWA 810. In 865, UE 805 receives the gap ID of the selected SG as part of a DL MAC CE from NWA 810 as confirmation of the deactivation of the selected SG.

[0091] In 870, UE 805 and NWA 810 operate based on the deactivated SG. For example, normal operation can be restored on NWA 810 without any SG.

[0092] Figure 9 A first exemplary method 900 for configuring and activating / deactivating scheduling gaps according to various exemplary embodiments described herein is illustrated.

[0093] In 905, a multi-SIM UE enters an RRC idle state or an RRC inactive state on a network (e.g., NW B). In 910, a UE enters an RRC connected state on a different network (e.g., NW A). During a transition to the RRC connected state or at any time prior to the current transition to the connected state, the UE indicates its multi-SIM capability to the NW A for implementing a scheduling gap (SG) as part of the UE capability signaling. The NW A may configure a timer disable for the UE if and when the UE transmits a scheduling gap request.

[0094] In 915, according to the first embodiment described above, the UE transmits a scheduling gap request to the NWA. As mentioned above, this SG request can be transmitted during the UE's transition to a connected state on the NWA, for example, in an RRCSetupRequest message (when the UE starts in an idle state on the NWA) or in an RRCResumeRequest message (when the UE starts in an inactive state on the NWA). If the UE is already in a connected state, the SG request can be transmitted in a UEAssistanceInformation message. The UE can start a disable timer after sending this request.

[0095] In 920, the NWA transmits a set of SG configurations to the UE. Each SG configuration includes information for the corresponding SG, including the SG type (periodic / aperiodic), SG timing advance, SG length, and the periodicity of the SG (only if the SG is periodic). Each SG configuration is associated with a unique SG identifier (ID). In exemplary method 900, it is assumed that the SG configuration is performed before the timer expires.

[0096] In 925, the UE selects the appropriate SG or more from a set of configured SGs based on the current use case for NW B operation. In 930, the UE indicates the selected SG configuration to the NW A using the appropriate SG ID, either as part of the UEAssistanceInformation message or in the MAC CE. In 935, the NW A confirms the currently active SG configuration, either as part of the RRCReconfiguration message or the DL MAC CE.

[0097] In 940, once one or more SGs are configured and activated, the UE and NWA operate accordingly. For example, the UE can periodically or non-periodically tune away from NWA during the duration of an SG to perform operations on NWA. At the end of the SG, the UE retunes to NWA and remains in RRC connected state on NWA.

[0098] In 945, the UE can request to deactivate one or more configured SGs. Similar to the activation process described above, the UE can determine which SGs to deactivate and transmit the deactivation request to the network in a UEAssistanceInformation message or MAC CE that includes the SG ID of the desired SG to be deactivated. The NWA can confirm the deactivation in an RRCReconfiguration message or DL ​​MAC CE.

[0099] Figure 10 A second exemplary method 1000 for configuring and activating / deactivating scheduling gaps according to various exemplary embodiments described herein is illustrated.

[0100] In scenario 1005, a multi-SIM UE enters an RRC idle state or an RRC inactive state on a network (e.g., NW B). In scenario 1010, a UE enters an RRC connected state on a different network (e.g., NW A). During the transition to the RRC connected state or at any time before entering the connected state, the UE indicates its multi-SIM capability for implementing a scheduling gap (SG) to the NW A as part of the UE capability signaling. If and when the UE transmits a scheduling gap request, the NW A can configure a timer to disable the UE. In this exemplary implementation, the UE can request one or more specific SG modes, rather than having the NW A configure a set of possible SG configurations.

[0101] In message 1015, as part of the UE Assistance Information, the UE indicates one or more preferred SG modes based on the intended use case with the NW B. In this message, the UE includes parameters for the SG, including the SG type (periodic / aperiodic), SG timing lead, SG length, and SG periodicity (only if the SG is periodic). Each SG mode indication in the SG mode indication is associated with a unique SG identifier (ID).

[0102] In 1020, the NWA confirms the SG mode indicated by the UE. The NWA can provide this confirmation by including the requested gap ID in the RRCReconfiguration message or the DL MAC CE.

[0103] In 1025, once one or more SGs are configured and activated, the UE and NWA operate accordingly. For example, the UE can periodically or non-periodically tune away from NWA during the duration of an SG to perform operations on NWA. At the end of the SG, the UE retunes to NWA and remains in RRC connected state on NWA.

[0104] In step 1030, the UE can request to deactivate one or more of the configured SGs. Similar to the activation process described above, the UE can determine which SGs to deactivate and transmit the deactivation request to the network in a UEAssistanceInformation message or MAC CE that includes the SG ID of the desired SG to be deactivated. The NWA can confirm the deactivation in an RRCReconfiguration message or DL ​​MAC CE.

[0105] In some exemplary implementations, the periodic SG can be configured by the network by default, i.e., without receiving an initial request from the UE. When the UE reports its SG capability to the network, the network can assume a need for the SG. After receiving the configuration, if the periodic SG is actually needed, the UE can (by default) activate it. Alternatively, if a multi-SIM UE is not currently using a second SIM on a second network, the UE can choose not to activate the configured SG.

[0106] In some scenarios, multi-SIM UEs may need to switch from NW A to NW B for a longer duration. Instead of keeping the RRC connected state on NW A for the entire duration, NW A can implement one or more implicit timers to transition from the RRC connected state to the RRC inactive state or the RRC idle state on NW A.

[0107] The NWA can configure a timer value for the UE that, if present, indicates to the UE that it may potentially transition to either an idle or inactive state if it does not receive a response to a long handover request from the NWA. For a more granular approach, the NWA can configure two timer values ​​(T1 and T2), where T1 indicates an implicit transition from RRC to RRC inactivity, and T2 indicates an implicit transition from RRC inactivity to RRC idle. If only one timer value (T) is configured, it means that the NWA does not support implicit transitions of the MUSIM UE to an RRC inactivity state and only allows the UE to enter an RRC idle state. The NWA can configure one or more timer values ​​as part of the whole-cell SI or on a per-RRC connection basis.

[0108] Example

[0109] In a first embodiment, a processor of a user equipment (UE) is configured to perform operations including: entering a Radio Resource Control (RRC) connection state on a first network using a first User Identity Module (SIM), and entering an RRC inactive state or an RRC idle state on a second network using a second SIM; transmitting to the first network an indication of the ability to perform a Scheduling Gap (SG) configuration, wherein the first network avoids scheduling resources for the UE during the duration of the SG; receiving from the first network an indication of the SG configuration to be used; tuning away from the first network to perform operations on the second network during the duration of the SG; and tuning back to the first network after the duration of the SG, wherein the RRC connection state was maintained on the first network during the duration of the SG.

[0110] In the second embodiment, the processor according to the first embodiment is used, wherein the SG is periodic and is configured by the first network by default.

[0111] In a third embodiment, a processor of a base station of a first network is configured to perform operations including: entering a Radio Resource Control (RRC) connection state with a user equipment, wherein the UE accesses the first network using a first User Identity Module (SIM), and wherein the UE also enters an RRC inactive state or an RRC idle state on a second network using a second SIM; receiving from the UE a request for a scheduling gap (SG) configuration, wherein during the duration of the SG, the first network avoids scheduling resources for the UE; transmitting to the UE an indication of the SG configuration to be used, wherein during the duration of the SG, the UE tunes away from the first network to perform operations on the second network; and maintaining the RRC connection state with the UE during the duration of the SG.

[0112] In the fourth embodiment, the processor according to the third embodiment further includes: transmitting to the UE a configuration for a set of SGs, wherein the UE selects one or more of the configured SGs to be used based on operations to be performed on the second network; and receiving from the UE an indication of the selected SG to activate the selected SG.

[0113] In the fifth embodiment, the processor according to the fourth embodiment is used, wherein the request transmitted by the UE is included in the RRCSetupRequest message, and the configuration transmitted by the first network is included in the RRCSetup message.

[0114] In the sixth embodiment, the processor according to the fourth embodiment is used, wherein the request transmitted by the UE is included in the RCResumeRequest message, and the configuration transmitted by the first network is included in the RCResume message.

[0115] In the seventh embodiment, according to the processor of the fourth embodiment, the request transmitted by the UE is included in the UEAssistanceInformation message, and the configuration transmitted by the first network is included in the RRCReconfiguration message.

[0116] In the eighth embodiment, the processor according to the fourth embodiment is provided, wherein the transmitted configuration for a set of SGs includes an SG identifier (ID) associated with each SG, wherein the SG ID of the selected SG is used to indicate the selected SG to the network.

[0117] In the ninth embodiment, according to the processor of the fourth embodiment, the activation of the selected SG is received in the UEAssistanceInformation message, and the first network confirms the activation of the selected SG in the RRCReconfiguration message.

[0118] In the tenth embodiment, the processor according to the fourth embodiment is wherein activation of the selected SG is received in the uplink media access control (MAC) control element (CE), and the first network confirms activation of the selected SG in the downlink MAC CE.

[0119] In the eleventh embodiment, the processor according to the third embodiment is provided, wherein the SG configuration includes an SG type, a timing advance of the SG, and a length of the SG, wherein the SG type includes either periodic or aperiodic.

[0120] In the twelfth embodiment, the processor according to the eleventh embodiment is further provided that the SG configuration includes the periodicity of the SG when the SG type is periodic.

[0121] In the thirteenth embodiment, the processor according to the third embodiment further includes: configuring a timer for the UE, wherein during the duration of the timer, the UE avoids transmitting additional requests to the SG.

[0122] In the fourteenth embodiment, the processor according to the thirteenth embodiment, wherein the indication of the SG configuration to be used received by the first network includes one or more SG IDs.

[0123] In the fifteenth embodiment, the processor according to the fourteenth embodiment is used, wherein the request is included in the UEAssistanceInformation message, and the indication transmitted by the first network is included in the RRCReconfiguration message.

[0124] In the sixteenth embodiment, the processor according to the fourteenth embodiment is provided, wherein the request is included in the UEAssistanceInformation message and the indication transmitted by the first network is included in the downlink media access control (MAC) control element (CE).

[0125] In the seventeenth embodiment, according to the processor of the thirteenth embodiment, the parameters of SG include SG type, SG timing advance and SG length, wherein the SG type includes either periodic or aperiodic.

[0126] In the eighteenth embodiment, the processor according to the seventeenth embodiment is further provided that when the SG type is periodic, the SG parameter also includes the periodicity of the SG.

[0127] In the nineteenth embodiment, the processor according to the thirteenth embodiment further includes: configuring a timer for the UE, wherein during the duration of the timer, the UE avoids transmitting additional requests to the SG.

[0128] In the twentieth embodiment, according to the processor of the third embodiment, the UE selects one or more configured SGs from a set of configured SGs to be deactivated based on an operation to be performed on the second network, the operation further comprising: receiving from the UE an indication of the selected SG to deactivate the selected SG.

[0129] In the twenty-first embodiment, according to the processor of the twenty-first embodiment, the deactivation of the selected SG is received in the UEAssistanceInformation message, and the first network confirms the deactivation of the selected SG in the RRCReconfiguration message.

[0130] In the twenty-second embodiment, the processor according to the twenty-first embodiment is wherein the deactivation of the selected SG is received in the uplink media access control (MAC) control element (CE), and the first network confirms the deactivation of the selected SG in the downlink MAC CE.

[0131] In a twenty-third embodiment, a processor of a base station of a first network is configured to perform operations including: entering a Radio Resource Control (RRC) connection state with a user equipment, wherein the UE accesses the first network using a first user identity module (SIM), wherein the UE also enters an RRC inactive state or an RRC idle state in a second network using a second SIM; receiving from the UE an indication of the ability to perform a scheduling gap (SG) configuration, wherein during the duration of the SG, the first network avoids scheduling resources for the UE; transmitting to the UE an indication of the SG configuration to be used, wherein during the duration of the SG, the UE tunes away from the first network to perform operations on the second network; and maintaining the RRC connection state with the UE during the duration of the SG.

[0132] In the twenty-fourth embodiment, the processor according to the twenty-third embodiment is used, wherein the SG is periodic and is configured by the first network by default.

[0133] In a twenty-fifth embodiment, a processor of a user equipment (UE) is configured to perform an operation including: entering a Radio Resource Control (RRC) connection state on a second network using a first user identity module (SIM), and entering an RRC inactive state or an RRC idle state on the second network using a second SIM; receiving from a first network a configuration for a first timer to be used when the UE tunes out of the first network; tuning out of the first network to perform the operation on the second network; and when the UE tunes out of the first network, starting the first timer, and if the first timer times out before the UE tunes back to the first network, entering an RRC inactive state or an RRC idle state on the first network when the UE tunes back to the first network.

[0134] In the twenty-sixth embodiment, the processor according to the twenty-fifth embodiment further includes: receiving from the first network a configuration for a second timer to be used when the UE tunes away from the first network, wherein the second timer has a shorter duration than the first timer; if the second timer times out before the UE tunes back to the first network and the first timer has not yet timed out, then when the UE tunes back to the first network, entering an RRC inactive state in the first network; and if the first timer times out before the UE tunes back to the first network, then when the UE tunes back to the first network, entering an RRC idle state on the first network.

[0135] In the twenty-seventh embodiment, the processor according to the twenty-fifth embodiment is configured to receive the first timer configuration in a system information (SI) broadcast or via RRC signaling.

[0136] In a twenty-eighth embodiment, a processor of a base station of a first network is configured to perform an operation including: entering a radio resource control (RRC) connection state with a user equipment, wherein the UE accesses the first network using a first user identity module (SIM), wherein the UE also enters an RRC inactive state or an RRC idle state on the second network using a second SIM; transmitting to the UE a configuration for a first timer to be used when the UE tunes away from the first network to perform the operation on the second network, wherein if the first timer times out before the UE tunes back to the first network, the UE enters an RRC inactive state or an RRC idle state on the first network when the UE tunes back to the first network.

[0137] In the twenty-ninth embodiment, the processor according to the twenty-eighth embodiment further includes: transmitting to the UE a configuration for a second timer to be used when the UE tunes away from the first network, wherein the second timer has a shorter duration than the first timer, wherein if the second timer times out before the UE tunes back to the first network and the first timer has not yet timed out, then when the UE tunes back to the first network, the UE enters an RRC inactive state on the first network, and if the first timer times out before the UE tunes back to the first network, then when the UE tunes back to the first network, the UE enters an RRC idle state on the first network.

[0138] In the thirtieth embodiment, the processor according to the twenty-eighth embodiment is configured such that the first timer is transmitted in the system information (SI) broadcast or via RRC signaling.

[0139] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0140] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0141] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0142] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. An apparatus comprising processing circuitry coupled to a memory, the processing circuitry being configured to: Using the first user identity module SIM to enter the Radio Resource Control (RRC) connected state on the first network, and using the second SIM to enter the RRC inactive or RRC idle state on the second network; A UEAssistanceInformation message is generated for transmission to the first network. The UEAssistanceInformation message includes scheduling gap (SG) configuration information, wherein... During the duration of the SG, the first network avoids scheduling resources for the UE; Based on signaling from the first network, a prohibition timer configuration is processed, wherein during the duration of the prohibition timer, the UE avoids transmitting additional UEAssistanceInformation messages including additional SG configuration information; Based on signaling from the first network, an indication of the SG configuration to be used is processed; During the duration of SG, tuning away from the first network to perform operations on the second network; and After the duration of SG, the signal is tuned back to the first network, wherein during the duration of SG, the RRC connection state is maintained on the first network.

2. The apparatus according to claim 1, wherein, The processor is also configured to: Based on signaling from the first network, the configuration for a set of SGs is processed; Based on the operation to be performed on the second network, select one or more of the configured SGs to be used; as well as Generate an indication for the selected SG to be transmitted to the first network, thereby activating the selected SG.

3. The apparatus according to claim 2, wherein, The indication of the SG configuration to be used is included in the RRCSetup message.

4. The apparatus according to claim 2, wherein, The indication of the SG configuration to be used is included in the RRCResume message.

5. The apparatus according to claim 2, wherein, The indication of the SG configuration to be used is included in the RRCReconfiguration message.

6. The apparatus according to claim 2, wherein, The UEAssistanceInformation includes instructions for the operations to be performed on the second network.

7. The apparatus according to claim 2, wherein, The received configuration for the set of SGs includes an SG identifier ID associated with each SG, wherein the SG ID of the selected SG is used to indicate the selected SG to the network.

8. The apparatus according to claim 2, wherein, Activation of the selected SG is transmitted in the UEAssistanceInformation message.

9. The apparatus according to claim 2, wherein, The activation of the selected SG is transmitted in the uplink Media Access Control (MAC) CE, and the first network confirms the activation of the selected SG in the downlink MAC CE.

10. The apparatus according to claim 1, wherein, The indication of the SG configuration to be used includes the SG type, the timing advance of the SG, and the length of the SG, wherein the SG type includes periodic or non-periodic.

11. The apparatus according to claim 10, wherein, When the SG type is periodic, the SG configuration also includes the periodicity of the SG.

12. The apparatus according to claim 1, wherein, The UEAssistanceInformation includes parameters for one or more SGs, wherein each SG is associated with an SG identifier ID.

13. The apparatus according to claim 12, wherein, The indication of the SG configuration to be used includes one or more SGIDs.

14. The apparatus according to claim 13, wherein, The indication of the SG configuration to be used is included in the RRCReconfiguration message.

15. The apparatus according to claim 13, wherein, The indication of the SG configuration to be used is included in the downlink media access control control element MAC CE.

16. The apparatus according to claim 12, wherein, The parameters of SG include SG type, SG timing lead, and SG length. SG type can be periodic or aperiodic.

17. The apparatus according to claim 16, wherein, When the SG type is periodic, the SG parameter also includes the periodicity of the SG.

18. A user equipment (UE), comprising: The first user identity module (SIM) associated with the first network; A second SIM associated with a second network; A transceiver configured to communicate with the first network using credentials associated with the first SIM and with the second network using credentials associated with the second SIM; as well as A processor, communicatively coupled to the transceiver and configured to: Entering the Radio Resource Control (RRC) connected state on the first network and entering the RRC inactive or RRC idle state on the second network; Generate a UEAssistanceInformation message for transmission to the first network, the UEAssistanceInformation message including scheduling gap (SG) configuration information, wherein, during the duration of the SG, the first network avoids scheduling resources for the UE; Based on signaling from the first network, a prohibition timer configuration is processed, wherein during the duration of the prohibition timer, the UE avoids transmitting additional UEAssistanceInformation messages including additional SG configuration information; Based on signaling from the first network, an indication of the SG configuration to be used is processed; During the duration of SG, tuning away from the first network to perform operations on the second network; and After the duration of SG, the signal is tuned back to the first network, wherein during the duration of SG, the RRC connection state is maintained on the first network.

19. The UE according to claim 18, wherein, The processor is also configured to: Based on signaling from the first network, the configuration for a set of SGs is processed; Based on the operation to be performed on the second network, select one or more of the configured SGs to be used; as well as Generate an indication for the selected SG to be transmitted to the first network, thereby activating the selected SG.

20. The UE according to claim 19, wherein, The indication of the SG configuration to be used is included in the RRCSetup message.

Images