Device for communication

Abstract

The present disclosure relates to obtaining caller ID on a second SIM of a multi-SIM user equipment. A user equipment (UE) configured to initiate a first voice call with a first network associated with a first subscriber identity module (SIM) of the UE, receive a paging request from a second network indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is in an active state, perform a radio resource control (RRC) connection setup with the second network, transmit an indication to the second network that the UE should be configured with a single component carrier (CC), and exchange session information protocol (SIP) messages with the second network to retrieve a caller identification (ID) of the incoming call.

Description

[0001] Priority declaration / incorporation by reference

[0002] This patent application claims priority to U.S. Provisional Application Serial No. 63 / 201,703, filed May 10, 2021, entitled “Obtaining a Caller ID on a Second SIM of a Multi-SIM User Equipment,” the entire contents of which are incorporated herein by reference. Background Technology

[0003] In 5G New Radio (NR) networks, User Equipment (UE) can be configured to have multiple common Subscriber Identity Modules (SIMs) (e.g., two SIMs). In some cases, the UE may include multiple receivers but only a single transmitter; in this case, the UE is classified as a Dual Receiver Dual SIM Dual Standby (DR-DSDS) UE. When the UE receives a call via the second SIM during an active call via the first SIM, the second SIM performs a Radio Resource Control (RRC) connection to obtain the caller ID of the incoming call. Summary of the Invention

[0004] Some exemplary embodiments relate to a processor configured to perform operations on a user equipment (UE). These operations include: initiating a first voice call using a first network associated with a first user identity module (SIM) of the UE; receiving a paging request from a second network indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is active; performing a radio resource control (RRC) connection establishment with the second network; transmitting to the second network an indication that the UE should be configured to have a single component carrier (CC); and exchanging Session Information Protocol (SIP) messages with the second network to retrieve the caller identifier (ID) of the incoming call.

[0005] Some exemplary embodiments relate to a processor of a base station configured to perform operations. These operations include: transmitting to a user equipment (UE) a paging request indicating an incoming voice call associated with a second user identity module (SIM) of the UE, wherein the UE receives the paging request while a first voice call associated with a first SIM of the UE is active; performing a radio resource control (RRC) connection establishment with the UE; receiving from the UE an indication that the UE should be configured to have a single component carrier (CC); suspending dual connectivity (DC) and carrier aggregation (CA); and exchanging Session Information Protocol (SIP) messages with the UE to provide the UE with the caller identifier (ID) of the incoming call.

[0006] A further exemplary embodiment relates to a processor configured to perform operations on a user equipment (UE). These operations include: initiating a first voice call using a first network associated with a first user identity module (SIM) of the UE; receiving a paging request from a second network indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is active; performing a Radio Resource Control (RRC) connection establishment with the second network; exchanging Session Information Protocol (SIP) messages with the second network to retrieve the caller identifier (ID) of the incoming call; and tuning the UE's transmitter to a frequency associated with the second network for one or more predetermined time periods during the RRC connection establishment and the SIP message exchange with the second network. Attached Figure Description

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

[0008] Figure 2 An exemplary multi-user User Identity Module (MUSIM) user equipment (UE) according to various exemplary embodiments is shown.

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

[0010] Figure 4A and Figure 4B A signaling diagram is shown, illustrating methods for providing the network with an indication, according to various exemplary embodiments, that a MUSIM UE should not be configured to have carrier aggregation (CA) or multiple radio access network (multiple RAN) dual connectivity (MR-DC).

[0011] Figure 5A and Figure 5B A signaling diagram is shown, illustrating methods for providing the network with an indication that the MUSIM UE should not be configured to have a CA or MR-DC, according to various exemplary embodiments.

[0012] Figure 6 A signaling diagram is shown, illustrating a method for transferring the UE's transmitter from the first SIM to the second SIM during a caller ID retrieval process on a second SIM, according to various exemplary embodiments.

[0013] Figures 7A to 7C A signaling diagram is shown, illustrating a method for procedurally transferring a UE's transmitter from a first SIM to a second SIM according to various exemplary embodiments.

[0014] Figure 8A signaling diagram is shown, illustrating a method for transferring a UE's transmitter from a first SIM to a second SIM based on a transport location, according to various exemplary embodiments.

[0015] Figure 9A An exemplary MUSIM UE with a single transmitter is shown according to various exemplary embodiments.

[0016] Figure 9B An exemplary MUSIM UE with multiple transmitters is shown according to various exemplary embodiments.

[0017] Figure 9C Exemplary transmission power diagrams related to power management of a multi-transmitter MUSIM UE are shown according to various exemplary embodiments. Detailed Implementation

[0018] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments describe a user equipment (UE) providing an instruction to a base station of a 5G New Radio (NR) network not to configure the UE with Carrier Aggregation (CA) and / or Multiple Radio Access Network (Multiple RAN) Dual Connectivity (MR-DC). The exemplary embodiments also describe the UE offloading its transmitter from a frequency of a first network corresponding to the first SIM to a frequency of a second network corresponding to the second SIM during an active call on a first SIM.

[0019] Exemplary implementations are described with reference to networks including 5G NR Radio Access Technology (RAT). However, the principles described herein can be used to implement exemplary implementations in other types of networks.

[0020] Throughout this specification, reference is made to the SIM, which performs functions such as communicating with a wireless network. However, those skilled in the art will understand that the SIM itself does not perform any functions or operations. Instead, the UE, or more precisely, the UE's processor, uses credentials and other information stored on the SIM to implement one or more protocol stacks, and then uses those protocol stacks to establish a connection with the network. Therefore, when references are made to SIM communicating with the network, this should be understood to include communication by the UE or the UE's processor via a connection associated with the SIM. Similarly, any other operations attributable to the SIM herein should be understood as operations performed by the processor using a protocol stack implemented with information provided by the SIM.

[0021] Exemplary embodiments are described with reference to the UE. However, the use of the UE is 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 that network. Therefore, the UE described herein is used to represent any electronic component.

[0022] When a Multi-User Identity Module (MUSIM) UE is in a Radio Resource Control (RRC) connection state with a first network via a first SIM (SIM1) and has an ongoing voice call, it can receive a paging request for the call (voice / data) from a second network via a second SIM (SIM2). In this case, the UE establishes an RRC connection with the second network via SIM2 to obtain the caller ID associated with the incoming call. Typically, all but one of the UE's multiple receivers (N-1 receivers) are assigned to SIM1 for the ongoing voice call, and that one receiver is assigned to SIM2, which is in an RRC idle state (or RRC inactive state), for receiving paging requests, maintaining idle mobility, etc. When SIM2 establishes an RRC connection with the second network to obtain the caller ID of the incoming call, the second network can configure the UE to have carrier aggregation (CA) and / or multiple radio access networks (multiple RANs) dual connectivity (MR-DC). However, because only one receiver in the UE's receivers is assigned to SIM2, the RRC configuration of SIM2 with CA and / or MR-DC will fail, and therefore the caller ID cannot be provided to the UE.

[0023] According to some exemplary implementations, when a MUSIM UE receives a paging request for a voice call on SIM2 while it has an ongoing call on SIM1, the UE may provide an indication to the second network that the dual connectivity (DC) CA should be suspended so that the second network can configure the UE to have only a single component carrier (CC) on SIM2.

[0024] Because a MUSIM UE can have multiple receivers and only one transmitter, the transmitter is shared between SIM1 and SIM2 when necessary. When there is an active voice call on SIM1, the UE primarily uses the transmitter for SIM1 voice calls. However, when a paging request for an incoming call is received from the second network while a voice call on SIM2 is still in progress on SIM1, the UE uses the transmitter to establish an RRC connection with the second network to obtain the caller ID of the incoming call. However, in this scenario, under the 3GPP standard, there is currently no transmitter sharing configuration between SIM1 and SIM2.

[0025] According to another exemplary embodiment, the UE is configured to switch the transmitter from the frequency associated with SIM1 to the frequency associated with SIM2 during one or more predetermined time periods during the caller ID retrieval process in such a way that the quality of the ongoing call on SIM1 is not degraded.

[0026] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is illustrated. The exemplary network arrangement 100 includes a UE 110. It should be noted that any number of UEs may be used in the network arrangement 100. Those skilled in the art will understand that the UE 110 may alternatively be any type of electronic component configured to communicate via a network, such as a mobile phone, tablet, desktop computer, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that a practical network arrangement may include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with a single UE 110 is provided.

[0027] UE 110 can be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 can wirelessly communicate are 5G New Radio (NR) Radio Access Network (5G NR-RAN) 120, LTE Radio Access Network (LTE-RAN) 122, and Wireless Local Area Network (WLAN) 124. However, it should be understood that UE 110 can also communicate with other types of networks, and UE 110 can also communicate with networks via wired connections. Therefore, UE 110 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124.

[0028] 5G NR-RAN 120 and LTE-RAN 122 may be portions of a cellular network that can be deployed by a cellular provider (e.g., Verizon, AT&T, T-Mobile, etc.). These networks 120, 122 may include, for example, cells or 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 124 may include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0029] UE 110 can connect to 5G NR-RAN 120 via next-generation Node B (gNB) 120A and / or gNB 120B. During operation, UE 110 can be within range of multiple gNBs. Therefore, simultaneously or alternatively, UE 110 can connect to 5G NR-RAN 120 via gNBs 120A and 120B. Additionally, UE 110 can communicate with eNB 122A of LTE-RAN 122 to transmit and receive control information for downlink and / or uplink synchronization relative to the 5G NR-RAN 120 connection.

[0030] Those skilled in the art will understand that any relevant procedures can be performed for UE 110 to connect to 5G NR-RAN 120. For example, as described above, 5G NR-RAN 120 can be associated with a specific cellular provider, where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 can transmit the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 can be associated with a specific base station (e.g., gNB 120A of 5G NR-RAN 120).

[0031] In addition to networks 120, 122, and 124, 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 (e.g., NR's 5GC) can be viewed as an interconnected collection 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.

[0032] IMS150 can generally be described as an architecture for delivering multimedia services to UE 110 using the IP protocol. IMS150 can communicate with cellular core network 130 and Internet 140 to provide multimedia services to UE 110. Network service backbone 160 communicates directly or indirectly with Internet 140 and cellular core network 130. 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 UE 110 to communicate with various networks.

[0033] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1The network arrangement 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory arrangement 210, display device 215, input / output (I / O) device 220, transceiver 225, other components 230, and a multi-purpose SIM (MUSIM) arrangement 240. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing a limited power source, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, one or more antenna panels, etc. For example, UE 110 may be coupled to industrial equipment via one or more ports. MUSIM arrangement 240 may include a first SIM (SIM1) 240a and a second SIM (SIM2) 240b, each of which may be coupled to different gNBs 120a, gNB 120b (or eNB 122A) of different networks.

[0034] Processor 205 may be configured to execute multiple engines of UE 110. For example, an engine may include MUSIM management engine 235. MUSIM management engine 235 may perform various operations related to managing the caller ID retrieval process and / or offloading transceiver 225 for predetermined time periods during the caller ID retrieval process, and may instruct network 100 during the caller ID retrieval process that dual connectivity (DC) carrier aggregation (CA) configuration should be suspended. An example of this process 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 may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to 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 may also be embodied as a single 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 arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. 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 5G NR-RAN 120, LTE-RAN 122, WLAN 124, etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous set of frequencies).

[0037] Figure 3 An exemplary network base station according to various exemplary embodiments is shown, in this example being gNB 120A. gNB 120A can represent any access node that UE 110 can use to establish a connection to a 5G NR network. Figure 3 The gNB 120A shown can also represent gNB 120B.

[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. These other components 330 may include, for example, a power supply, 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 RRC management engine 335 for performing operations including configuring RRC connections for one or more SIMs of MUSIM arrangement 240 for UE 110. An example of this process will be described in more detail below.

[0040] The engine described above, as an application (e.g., a program) executed by processor 305, is merely exemplary. The functionality associated with the engine 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 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 UEs 110 and 112. 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] Figure 4A and Figure 4B A signaling diagram is shown, illustrating methods for providing the network with an indication, according to various exemplary embodiments, that the MUSIM UE 110 should not be configured to have carrier aggregation (CA) or multiple radio access network (multiple RAN) dual connectivity (MR-DC). Figure 4A The procedure is illustrated when a user rejects an incoming call from SIM2 240b. At 402, SIM1 204a is in RRC connection mode with the first network (first gNB 120A) for active voice or data calls. It is assumed that SIM2 240b is in RRC idle mode (or RRC inactive mode). At 404, UE 110 disables Early Measurement Reporting (EMR) on SIM2 240b, which may have been configured by the second network (second gNB 120B) before SIM2 240b entered RRC idle mode (or RRC inactive mode).

[0043] At 406, SIM2 240b receives a paging request from the second network, which has a paging_reason field indicating whether the paging is for a voice call or a data call. Figure 4A The remaining description of the signaling diagram (and the remaining signaling diagram described below) assumes that the paging reason indicates that the paging request is for a voice call. However, if the paging reason is for a data call, then when SIM1 240a has an active call utilizing the first network, UE 110 ignores the paging request (and any subsequent retransmissions of the paging request) because the data call would require the use of an additional transmitter, which would degrade the call quality on SIM1 240a.

[0044] At 408, SIM2 240b transmits an RRC connection request to the second gNB 120B. At 410, the second gNB 120B transmits an RRC connection establishment message to SIM2 240b. At 412, SIM2 240b transmits an RRC connection establishment complete message to the second gNB 120B. In some implementations, the RRC complete message may include a request that a single component carrier (CC) to the second network be configured for SIM2. At 414, upon receiving the RRC connection establishment complete message, the second gNB 120B suspends dual connectivity (DC) carrier aggregation (CA).

[0045] At 416, the second gNB 120B transmits a security mode command message to SIM2 240b to configure UE 110 to activate access stratum (AS) security. At 418, SIM2 transmits a security mode completion message to the second gNB 120B. At 420, the second gNB 120B transmits an RRC reconfiguration message to SIM2 240b to configure the necessary data radio bearer (DRB). At 422, SIM2 240b transmits an RRC reconfiguration completion message to the second gNB 120B.

[0046] At position 424, the second gNB 120B transmits a Session Initiation Protocol (SIP) INVITE message to SIM2 240b via the default IMS bearer. This SIP INVITE message includes the caller ID associated with the incoming voice call. Therefore, UE 110 displays the caller ID and allows the user to decide whether to accept the incoming call (and hang up the active call on SIM1). As described above, Figure 4A Assume the user rejects the call. Therefore, at 426, SIM2 240b transmits a SIP call rejection message (e.g., SIP 486 message, SIP 603 message, etc.) to the second gNB 120B. Thus, the voice call on SIM1 continues, and the incoming call on SIM2 is rejected.

[0047] At 428, SIM2 240b transmits a UE Assistive Information (UAI) message to the second gNB 120B indicating that the RRC connection should be released. In some embodiments, this indication may be a PreferredRRCState field indicating an idle mode (PreferredRRCState = Idle or PreferredRRCState = Inactive). In some embodiments, this indication may alternatively include a new reason to the second gNB 120B indicating that SIM2 240b is requesting RRC release. At 430, the second gNB 120B releases the SIM2 RRC connection.

[0048] Figure 4BThis illustrates the process when a user accepts an incoming call from SIM2 240b. Due to 402 to 424 and... Figure 4A The corresponding steps are the same, so explanations of these operations are omitted here. After displaying the caller ID to the user, if the user wishes to accept an incoming call on SIM2, at 452, SIM1 240a transmits a SIP BYE message to the first gNB 120A indicating that the voice call on SIM1 240a should be terminated. At 454, the first gNB 120A transmits an acknowledgment (ACK) for the received SIP BYE message. At 458, SIM1 240a transmits a UAI message to the first gNB 120A indicating that the RRC connection for SIM1 240a should be released. In some embodiments, this indication may have a PreferredRRCState field indicating an idle mode (PreferredRRCState = idle) or an inactive mode (PreferredRRCState = inactive). In some embodiments, this indication may alternatively include a new reason indicating to the first gNB 120A that the UE is a MUSIM UE and is accepting a call on another SIM.

[0049] At 456, SIM2 240b transmits a SIP ringing message to the second gNB 120B, informing the caller that the phone is ringing. At 460, SIM2 240b transmits a SIP 200 OK message to the second gNB 120B. At 462, the second gNB 120B transmits an RRC reconfiguration message to SIM2 240b indicating the DRB for voice packets. At 464, the first gNB 120A transmits an RRC release message to SIM1 240a to release the SIM1 RRC connection. Therefore, SIM1 240a is now in RRC idle mode (or RRC inactive mode). At 466, SIM2 240b transmits an RRC reconfiguration complete message to the second gNB 120B indicating that DC-CA can now be resumed (because the user is accepting an incoming call from SIM2 240b, and all but one of the UE's receivers are now assigned to the SIM2 240b call). At 468, the second gNB 120B restores the DC-CA of SIM2240b. At 470, the second gNB 120B transmits an Activate Dedicated Evolved Packet System (EPS) Bearer Context message to SIM2 240b to configure SIM2 240a with a bearer context that will carry voice packets.

[0050] Figure 5A and Figure 5BA signaling diagram is shown, illustrating methods for providing the network with an indication that the MUSIM UE 110 should not be configured to have a CA or MR-DC, according to various exemplary embodiments. Figure 5A The procedure is illustrated when a user rejects an incoming call from SIM2 240b. At 502, SIM1 204a is in RRC connection mode with the first network (first gNB 120A) for active voice or data calls. It is assumed that SIM2 240b is in RRC idle mode (or RRC inactive mode). At 504, UE 110 disables EMR on SIM2 240b, which may have been configured by the second network (second gNB 120B) before SIM2 240b was in RRC idle mode (or RRC inactive mode).

[0051] At position 506, SIM2 240b receives a paging request from the second network, which has a paging_reason field indicating whether the paging is for a voice call or a data call. Figure 5A The remaining description of the signaling diagram assumes that the paging reason indicates the paging request is for a voice call. However, if the paging reason is for a data call, UE 110 ignores the paging request when SIM1 240a has an active call made on the first network, because the data call would require the use of an additional transmitter, which would degrade the call quality on SIM1 240a. Furthermore, from a service perspective, pure data services (e.g., internet browsing) have a lower priority than voice services (e.g., VoLTE, VoNR, etc.).

[0052] At 508, SIM2 240b transmits an RRC connection request to the second gNB 120B. At 510, the second gNB 120B transmits an RRC connection establishment message to SIM2 240b. At 512, SIM2 240b transmits an RRC connection establishment completion message to the second gNB 120B. At 514, the second gNB 120B transmits a security mode command message to SIM2 240b to configure UE 110 to activate AS security. At 516, SIM2 240b transmits a security mode completion message to the second gNB 120B.

[0053] At 518, SIM2 240b transmits a UAI message to the second gNB 120B, including an indication that DC-CA should be suspended. In some embodiments, this indication may be an implicit indication provided by using a maxAggrBW information element (IE) with a value of zero (maxAggrBW = 0). In some embodiments, this indication may alternatively be an explicit indication that SIM2 240b requests a single CC configuration for SIM2240b. At 520, upon receiving this UAI message, the second gNB 120B suspends dual connectivity (DC) carrier aggregation (CA). At 522, the second gNB 120B transmits an RRC reconfiguration to SIM2240b to configure the necessary DRB. At 524, SIM2 240b transmits an RRC reconfiguration complete message to the second gNB 120B.

[0054] At position 526, the second gNB 120B transmits a SIP INVITE message to SIM2 240b via the default IMS bearer. This SIP INVITE message includes the caller ID associated with the incoming voice call. Therefore, UE 110 displays the caller ID and allows the user to decide whether to accept the incoming call (and hang up the active call on SIM1). As described above, Figure 5A Assume the user rejects the call. Therefore, at 528, SIM2 240b transmits a SIP call rejection message (e.g., SIP486 message, SIP603 message, etc.) to the second gNB 120B. As a result, the voice call on SIM1 240a is restored, and the incoming call on SIM2 240b is rejected.

[0055] At 530, SIM2 240b transmits a UAI message to the second gNB 120B indicating that the RRC connection should be released. In some embodiments, this indication may be a PreferredRRCState field indicating either an idle mode (PreferredRRCState = idle) or an inactive mode (PreferredRRCState = inactive). In some embodiments, the indication may alternatively include a new reason to the second gNB 120B indicating that SIM2 240b is requesting RRC release. At 532, the second gNB 120B releases the SIM2 RRC connection.

[0056] Figure 5B This illustrates the process when a user accepts an incoming call from SIM2 240b. (Due to 502 to 526...) Figure 5AThe corresponding steps are the same, so explanations of these operations are omitted here. After displaying the caller ID to the user, if the user wishes to accept an incoming call on SIM2 240b, at 552, SIM1 240a transmits a SIP BYE message to the first gNB 120A indicating that the voice call on SIM1 240a should be terminated. At 554, the first gNB 120A transmits an acknowledgment (ACK) for the received SIP BYE message.

[0057] At position 556, SIM2 240b transmits a SIP ringing message to the second gNB 120B, informing the caller that the phone is ringing. At position 558, SIM2 240b transmits a SIP 200OK message to the second gNB 120B.

[0058] At position 560, SIM1 240a transmits a UAI message to the first gNB 120A indicating that the RRC connection for SIM1 240a should be released. In some embodiments, this indication may be a PreferredRRCState field indicating either an idle mode (PreferredRRCState = idle) or an inactive mode (PreferredRRCState = inactive). In some embodiments, the indication may alternatively include a new reason indicating to the first gNB 120A that the UE is a MUSIM UE and is accepting a call on another SIM.

[0059] At 562, SIM2 240b transmits a UAI message to the second gNB 120B indicating that DC-CA can now be resumed (because the user is accepting an incoming call from SIM2 240b, and all but one of the UE's receivers are now assigned to the SIM2 240b call). At 564, the first gNB 120A transmits an RRC release message to SIM1 240a, thereby releasing the SIM1 RRC connection. Therefore, SIM1 240a is now in idle or inactive mode.

[0060] At 566, the second gNB 120B restores the DC-CA of SIM2 240b. At 568, the second gNB 120B transmits an activation dedicated EPS bearer context message to SIM2 240b to configure SIM2 with a bearer context that will carry voice packets.

[0061] Figure 6A signaling diagram is shown, illustrating a method for transferring the transmitter 602 of UE 110 from a first SIM (SIM1 240a) to a second SIM (SIM2 240b) during a caller ID retrieval process on SIM2 240b, according to various exemplary embodiments. It should be noted that... Figure 6 The shaded box 690 (only one of the shaded boxes is marked) indicates which SIM controls the transmitter 602. Figure 6 In this process, the transmitter is tuned to the frequency of a second network that communicates with the SIM2 240b during the caller ID retrieval process. In some implementations, the duration of this tuning may be approximately 223 milliseconds (ms).

[0062] At points 605a and 605b, registration is performed on the Internet Protocol (IP) Multimedia Subsystem (IMS) Packet Data Network (PDN) associated with SIM1 240a and SIM2 240b (e.g., when UE 110 is powered on). At point 610, a voice call is established on SIM1 240a using the first network (first gNB 120A). Therefore, at point 615, SIM1 240a is in an RRC connected state. Therefore, at point 620, SIM2 240b is in an RRC idle state (or RRC inactive state).

[0063] At 625, SIM2 240b receives a paging request from the second network (second gNB 120B). This paging request includes a paging reason indicating whether the paging request is for a voice call or a data call. In some embodiments, the paging reason may explicitly indicate that the paging request is for a voice call. In such an embodiment, when UE 110 receives the paging reason, if the paging reason does not explicitly indicate that the paging is for a voice call, UE 110 may implicitly determine that the paging is for a data call. As mentioned above, it is assumed that the paging request is for a voice call. However, if the paging request is for a data call, UE 110 may ignore the paging request (and any subsequent retransmissions of the paging request) when SIM1 240a has an active call utilizing the first network. Because SIM1 240b has at least one assigned receiver, it can receive the paging request while a voice call is in progress on SIM1 240a.

[0064] At 630, UE 110 activates a radio frequency (RF) decoupling timer upon receiving a paging request (for a voice call). This timer expires at the end of a predetermined period based on the amount of time (e.g., 500ms, 300ms, 250ms, etc.) during which the transmitter can decouple from SIM1 without degrading the quality of active voice calls on SIM1 240a. Upon the expiration of this RF decoupling timer, regardless of what is happening on SIM2 240b, transmitter 602 is tuned back to the frequency associated with SIM1 240a.

[0065] At 635, UE 110 tunes transmitter 602 to the frequency associated with SIM2 240b. At 640, SIM2 performs the necessary signaling with the second network (second gNB 120B) to use the signaling as described above relative to... Figures 4A to 5B The caller ID of an incoming call is obtained using a similar method (connection establishment and SIP messaging). For example... Figure 6 As shown, from the moment the transmitter is tuned to the frequency of the second gNB 120B until the caller ID acquisition process ends, SIM2 240b controls transmitter 602.

[0066] At 645a, the RF de-call timer expires or the user rejects an incoming call on SIM2 240b. In either case, at 645b, UE 110 tunes the transmitter back to the frequency of the first gNB 120A. Although in Figure 6 Not shown, but it should be noted that if a call on SIM2 240b is accepted, the transmitter can only be tuned back to the frequency of the first gNB 120A if it is necessary to hang up the voice call on SIM1 240a. Subsequently, SIM2 240b will control transmitter 602 for the duration of the call on SIM2 240b.

[0067] Figures 7A to 7C A signaling diagram is shown, illustrating a method for procedurally transferring a UE's transmitter from a first SIM to a second SIM according to various exemplary embodiments. Figures 7A to 7C The method shown is the same as Figure 6 The difference in methods is that Figures 7A to 7CThe offloading of transmitter 602 is controlled by the RRC layer, Packet Transport Module (PTM) layer, Packet Data Convergence Protocol (PDCP) layer, RLC layer, and / or IMS stack. When a process associated with any of these layers needs to be performed, the transmitter is offloaded to the frequency of the network associated with the SIM performing the process. It should be noted that the shaded boxes 790 in Figure 7 (only one of them is marked) indicate which SIM controls transmitter 602. Each shaded box represents the offloading of transmitter 602 to the frequency of the corresponding network. In some embodiments, the longest duration for which transmitter 602 is offloaded from the first gNB 120A is less than 100 ms.

[0068] Figure 7A This describes a user rejecting an incoming call on SIM2 240b. At points 702a and 702b, registration is performed with the Internet and IMS PDN associated with SIM1 240a and SIM2 240b (e.g., when UE 110 is powered on). At point 704, a voice call is established on SIM1 240a using the first network (first gNB 120A). Therefore, at point 706, SIM1 240a is in an RRC connected state. Therefore, at point 708, SIM2 240b is in an RRC idle state (or RRC inactive state).

[0069] At 710, SIM2 240b receives a paging request from the second network (second gNB 120B). This paging request includes a paging reason indicating whether it is for a voice call or a data call. As mentioned above, it is assumed that the paging request is for a voice call. However, if the paging request is for a data call, UE 110 can ignore the paging request (and any subsequent retransmissions of the paging request) when SIM1 240a has an active call utilizing the first network. Because SIM1 240b has at least one assigned receiver, it can receive the paging request even when a voice call is in progress on SIM1 240a.

[0070] Since SIM2 240a now needs to establish an RRC connection, transmitter 602 is tuned to the frequency of the second gNB 120B (shown in the shaded box) that communicates with SIM2 240b. At 710, SIM2 240b transmits an RRC connection request message to the second network (second gNB 120B). At 712, second gNB 120B transmits an RRC connection establishment message to SIM2 240b. At 716, SIM2 240b transmits an RRC connection establishment complete message to second gNB 120B. At 718, second gNB 120B transmits a Radio Link Control (RLC) acknowledgment (ACK) to SIM2 240b. In some implementations, UE 110 is configured to tune transmitter 602 back to the frequency of the first gNB 120A once it receives the RLC ACK. If transmitter 602 is tuned away from SIM1 240a before receiving RLC ACK, it is possible that if an RLC negative ACK (NACK) is received, the transmitter will need to retune back to SIM2 240b, which means a retransmission will be required. When the transmitter is tuned back to the frequency of the first gNB 120A, SIM1 240 can transmit / receive any data pending when transmitter 602 was tuned to the frequency of SIM2 240b.

[0071] At 720, the second gNB 120B transmits a Security Mode Command message to configure UE 110 to activate AS security. At 722, SIM2 240b transmits a Security Mode Completion message to the second gNB 120B. Since this requires control of transmitter 602, the UE's RRC layer can tune the transmitter to the SIM2 240b frequency before the transmission at 720. At 724, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency (as indicated by the shaded box).

[0072] At 726, the second gNB 120B transmits an RRC reconfiguration message to SIM2 240b to configure the necessary DRB. At 728, SIM2 240b transmits an RRC reconfiguration complete message to the second gNB 120B. Since this requires control of transmitter 602, the UE's RRC layer can tune the transmitter to the SIM2 240b frequency before the transmission at 728. At 730, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0073] At 732, the second gNB 120B transmits a SIP INVITE message to SIM2 240b via the default IMS bearer. This SIP INVITE message includes the caller ID associated with the incoming voice call. Therefore, UE 110 displays the caller ID and allows the user to decide whether to accept the incoming call (and hang up the active call on SIM1 240a). At 734, SIM2 240b transmits a SIP 183 (Session Progress) message to the second gNB 120B. Since this requires control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 734. At 736, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0074] As mentioned above, Figure 7A Assume the user rejects the call. Therefore, at 738, SIM2 240b transmits a SIP call rejection message (e.g., SIP 486 message, SIP 603 message, etc.) to the second gNB 120B. This rejection may be an indication to the second network that a call on SIM1 240a is preferred. Since this requires control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 738. It should be noted that, although not shown, the call setup process may include other IMS messages (e.g., provisional response ACK (PRACK), PRACK-ACK, ringing, OK, message) between the RLC ACK at 736 and the call rejection at 738. At 740, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0075] At 742, the second gNB 120B transmits an ACK to SIM2 240b. At 744, SIM2 240b transmits an RLC ACK to the second gNB 120B. Since this requires control of transmitter 602, the UE's RLC layer can tune the transmitter to the SIM2 240b frequency before the transmission at 744. In some implementations, SIM2 240b may autonomously release its RRC connection at 746a. If SIM2 240b is a data-preferred SIM, it may force an RRC connection release to avoid further data exchange with the second network, which could unnecessarily cause transmitter 602 to de-frequency from SIM1 240a, thus degrading the quality of active voice calls on SIM1 240a. In some implementations, at 746b, SIM2 240b may alternatively wait for the second network to send an RRC release message. If SIM2 240b is not a data-preferred SIM, it may wait for the network to release the connection.

[0076] In some implementations, to ensure the existence of an RRC connection release protocol regarding the SIM2 240b and the second network, the SIM2 240b may transmit the protocol described above. Figure 5A Similar to the UAI discussed in 530, this UAI is used to indicate to the second network that SIM2 240b is requesting RRC release (preferredRRCState = idle or preferredRRCState = inactive). At 746b, in response, the second network may send an RRC release message to move SIM2 240b to RRC idle mode (or RRC inactive mode).

[0077] Figure 7B This describes how users ignore incoming calls on SIM2 240b. For clarity and brevity, descriptions of 702a to 736 and 746a, 746b are omitted here. Signaling for 712 to 730 is also included. Figure 7B This is categorized as "Call Setup". At 750, the second network (second gNB 120B) transmits a PRACK message to SIM2 240b in response to the SIP 183 message at 734. At 752, SIM2 240b transmits a SIP 200 OK message to the second gNB 120B. Since this requires control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 752. At 754, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0078] At 756, SIM2 240b transmits a SIP ringing message to the second gNB 120B. Since this requires control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 756. At 758, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once this RLC ACK is received, the transmitter is tuned back to the SIM1240a frequency.

[0079] As mentioned above, in Figure 7B In the above scenario, it is assumed that the user ignores the incoming call on SIM2 240b. Therefore, the call continues to ring until the call times out. At 760, once the call times out, the second gNB 120B transmits a SIP cancellation message. At 762, SIM2 240b transmits a SIP 200 OK message to the second gNB 120B. At 764, the second gNB 120B transmits an RLC ACK to SIM2 240b. At 766, SIM2 240b transmits a request to terminate message to the second gNB 120B. At 768, the second gNB 120B transmits an RLC ACK to SIM2 240b. Since the transmissions at 762 and 766 require control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 762. At 768, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once the RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0080] At 770, the second gNB 120B transmits an ACK message to SIM2 240b. At 772, SIM2 240b transmits an RLC ACK to the second gNB 120B. Since this requires control of transmitter 602, the UE's RLC layer can tune the transmitter to the SIM2 240b frequency before the transmission at 772. As described above, SIM2 240b can autonomously release its RRC connection at 746a, wait for the second network to send an RRC release message at 746b, or transmit a UAI to the second network to request RRC release.

[0081] Figure 7C This describes a user accepting an incoming call on SIM2 240b. For clarity and brevity, descriptions of 702a to 758 are omitted here. Signaling for 712 to 730 is also described in... Figure 7BThis is categorized as "Call Setup". At 774, SIM2 240b transmits a SIP 200 OK message to the second network (second gNB 120B) to indicate that the call has been accepted. Since this transmission requires control of transmitter 602, the UE's IMS layer can tune the transmitter to the SIM2 240b frequency before the transmission at 774. At 776, the second gNB 120B transmits an RLC ACK to SIM2 240b. Once the RLC ACK is received, the transmitter is tuned back to the SIM1 240a frequency.

[0082] At 778, since SIM1 240a controls the transmitter and the user decides to accept the incoming call on SIM2 240b, SIM1 240a transmits a SIP BYE message to the first network (first gNB 120A). First gNB 120A transmits a SIP 200 OK message to SIM1 240a. SIM1 240a transmits an RLC ACK to first gNB 120A. Once this RLC ACK is transmitted, transmitter 602 can be tuned back to the frequency of SIM2 240b, allowing the call on SIM2 to continue. At 784, when SIM1 terminates the voice call on SIM1, second gNB 120B transmits an ACK message to SIM2 240b.

[0083] Similar to the behavior of SIM2 240b when releasing its RRC connection, SIM1 240a can autonomously release its RRC connection at 746a, or wait for the second network to transmit an RRC release message at 746b, depending on whether SIM1 240a is the data-preferred SIM. Therefore, at 788, SIM1 240a is in RRC idle mode (or RRC inactive mode).

[0084] In some implementations, to ensure that a protocol for RRC connection release regarding the SIM1 240a and the first network exists, the SIM1 240a may transmit the protocol described above. Figure 5A Similar to the UAI discussed in 530, this UAI is used to indicate to the first network that SIM1 240a is requesting RRC release (preferredRRCState = idle or preferredRRCState = inactive). At 786b, in response, the first network may send an RRC release message to move SIM1 240a to RRC idle mode (or RRC inactive mode) at 788.

[0085] At 790, SIM2 240b transmits an RLC ACK to the second gNB 120B in response to the ACK received from the second gNB 120B at 784. At 792, a voice call is established on SIM2 240b. Therefore, at 794, SIM2 240a is now in RRC connection mode.

[0086] Figure 8 A signaling diagram is shown, illustrating a method for transferring a UE's transmitter from a first SIM to a second SIM based on a transport location, according to various exemplary embodiments. Figure 8 The method shown is the same as Figure 6 and Figures 7A to 7C The difference in methods is that Figure 8 The deactivation of transmitter 602 is controlled by the Media Access Control (MAC) layer or the L1 layer. When an uplink buffer exists at the MAC layer, the MAC layer reserves transmitter 602 for SIMs that need to perform Protocol Data Unit (PDU) transmissions. It should be noted that... Figure 8 The shaded boxes 890 (only one of them is marked) indicate which SIM controls transmitter 602. Each shaded box represents the frequency off-grid of transmitter 602 to the corresponding network (gNB).

[0087] Figure 8 This describes a user rejecting an incoming call on SIM2 240b. Descriptions of signaling in 802a to 846b are omitted here because this signaling is related to... Figure 7A The signaling is the same as that in 702a to 746b. Figure 8 The methods shown and Figure 7A The difference between the methods shown lies in the displacement of transmitter 602. As described above, in Figure 7A In this context, the transfer is based on process. However, in Figure 8 In this context, the switching is transmission-based. Therefore, whenever SIM2 240b needs to send a transmission to the second network (gNB 120B), transmitter 602 is tuned to the frequency of the second gNB 120B. Consequently, active voice calls on SIM1 240a are interrupted more frequently, but for significantly shorter durations (e.g., less than 1 ms each time). For brevity, a discussion of this transmission-based switching of transmitter 602 in cases where incoming calls to SIM2 240b are ignored or accepted is omitted here. However, it should be noted that the same transmission-based switching principle applies to those scenarios.

[0088] Figure 9A An exemplary MUSIM UE 110 with a single transmitter 906, as described in the above embodiment, is shown. Figure 9AAs shown, in some embodiments, UE 110 may include a first SIM (SIM1 901a) having an associated protocol stack (protocol stack 1 902a) and an associated receiver (Rx1 904a). Similarly, UE 110 may include a second SIM (SIM1 901b) having an associated protocol stack (protocol stack 2 902b) and an associated receiver (Rx2 904b). Both SIM1 901a and SIM2 901b share a single transmitter 906 as described above. SIM1 901a communicates with a first base station (base station 1 908a) of a first network (network 1 910a) via Rx1 904a and Tx 906. SIM2 901b communicates with a second base station (base station 2 908b) of a second network (network 2 910b) via Rx2 904b and Tx 906. Although Figure 9A Only two receivers (Rx1904a, Rx2904b) are shown in the diagram, but it should be noted that UE 110 may include multiple receivers.

[0089] Figure 9B An exemplary MUSIM UE 110 with multiple transmitters is shown according to various exemplary embodiments. Figure 9C It shows the relationship with Figure 9B An exemplary transmission power diagram related to power management in a multi-transmitter MUSIM UE. (See example...) Figure 9B As shown, in some embodiments, UE 110 may include a first SIM (SIM1 901a) having an associated protocol stack (protocol stack 1 902a), an associated receiver (Rx1 904a), and an associated transmitter (Tx1 906a). SIM1 901a communicates with a first base station (base station 1 908a) of a first network (network 1 908a) via Rx1 904a and Tx1 906a. Similarly, UE 110 may include a second SIM (SIM1 901b) having an associated protocol stack (protocol stack 2 902b), an associated receiver (Rx2 904b), and an associated transmitter (Tx2 906b). SIM2 901b communicates with a second base station (base station 2 908b) of a second network (network 2 908b) via Rx2 904b and Tx2 906b. Although Figure 9A Only two receivers (Rx1 904a, Rx2 904b) are shown in the diagram, but it should be noted that UE 110 may include multiple receivers.

[0090] exist Figure 9CIn the following description, it is assumed that SIM1 901a is in RRC connection mode and has an active voice call using Tx1 906a tuned to the frequency of base station 1 908a. When the caller ID retrieval process (as described above) begins (upon receiving a paging request indicating a voice call), Tx2 906b is tuned to the frequency of base station 2 908a. In some embodiments, when SIM2 901b needs to transmit messages to base station 2 908b for the caller ID retrieval process, the maximum Tx1 power is reduced to 0 (as indicated in 912a), and the maximum Tx2 power is set to a non-zero value (as indicated in 912b). Conversely, when SIM2 901b has completed these transmissions, the maximum Tx2 power is reduced to 0 (as indicated in 914b), and the maximum Tx1 power is set to a non-zero value (as indicated in 914a). The duty cycle can be controlled by protocol stacks 902a and 902b based on the transmission priority on the two SIMs 901a and 901b.

[0091] Example

[0092] In a first embodiment, the processor of a user equipment (UE) is configured to perform operations including: initiating a first voice call using a first network associated with a first user identity module (SIM) of the UE; receiving a paging request from a second network indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is active; performing a radio resource control (RRC) connection establishment with the second network; exchanging Session Information Protocol (SIP) messages with the second network to retrieve the caller identifier (ID) of the incoming call; and tuning the UE's transmitter to a frequency associated with the second network for one or more predetermined time periods during the RRC connection establishment and the SIP message exchange with the second network.

[0093] In the second embodiment, according to the processor of the first embodiment, the one or more predetermined time periods are a single time period spanning the entire RRC connection establishment and SIP message exchange with the second network.

[0094] In the third embodiment, according to the processor of the second embodiment, these operations further include: starting a radio frequency (RF) decoupling timer when a paging request is received, and tuning the UE's transmitter to a frequency associated with the first network when the RF decoupling timer expires, regardless of whether the RRC connection establishment and SIP message exchange are completed.

[0095] In the fourth embodiment, according to the processor of the first embodiment, the one or more predetermined time periods are determined by one or more upper layers of the UE based on when the one or more upper layers need to communicate with the second network.

[0096] In the fifth embodiment, the processor according to the fourth embodiment, wherein the one or more upper layers include one or more of the following: an RRC layer, a Packet Transport Module (PTM) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and / or an Internet Protocol (IP) Multimedia System (IMS) stack.

[0097] In the sixth embodiment, according to the processor of the fourth embodiment, when an incoming voice call is rejected or ignored and the second SIM is a voice-preferred SIM, these operations further include waiting to receive an RRC connection release message from the second network.

[0098] In the seventh embodiment, according to the processor of the fourth embodiment, when an incoming voice call is accepted, these operations further include tuning the transmitter to the frequency of the first network, terminating the first voice call, and tuning the transmitter back to the frequency of the second network.

[0099] In the eighth embodiment, the processor according to the seventh embodiment, wherein when the first SIM is a voice-preferred SIM, these operations further include waiting to receive an RRC connection release message from the second network.

[0100] In the ninth embodiment, the processor according to the seventh embodiment, wherein when the first SIM is a data preferred SIM, these operations further include performing an RRC connection release for the RRC connection with the first network.

[0101] In the tenth embodiment, according to the processor of the ninth embodiment, performing RRC connection release includes: transmitting a UE Assistance Information (UAI) message including an RRC connection release request to a first network, and receiving an RRC connection release from the first network.

[0102] In the eleventh embodiment, the processor according to the first embodiment is used, wherein the one or more predetermined time periods are determined by one or more lower layers of the UE, and based on when the one or more lower layers need to send transmissions to the second network.

[0103] In the twelfth embodiment, the processor according to the eleventh embodiment, wherein the one or more lower layers include one or more of a media access control (MAC) layer and a layer 2 (L2).

[0104] In the thirteenth embodiment, the processor according to the eleventh embodiment further includes waiting to receive an RRC connection release message from the second network when an incoming voice call is rejected or ignored and the second SIM is a voice-preferred SIM.

[0105] In the fourteenth embodiment, the processor according to the eleventh embodiment further includes performing an RRC connection release for the RRC connection with the second network when an incoming voice call is rejected and the second SIM is a data preferred SIM.

[0106] In the fifteenth embodiment, the processor according to the fourteenth embodiment, wherein performing RRC connection release includes: transmitting a UE Assistance Information (UAI) message including an RRC connection release request to a second network, and receiving an RRC connection release from the second network.

[0107] In the sixteenth embodiment, the processor according to the eleventh embodiment, wherein when an incoming voice call is accepted, these operations further include tuning the transmitter to the frequency of the first network, terminating the first voice call, and tuning the transmitter back to the frequency of the second network.

[0108] In the seventeenth embodiment, the processor according to the fifteenth embodiment, wherein when the first SIM is a voice-preferred SIM, these operations further include waiting to receive an RRC connection release message from the second network.

[0109] In the eighteenth embodiment, the processor according to the fifteenth embodiment, wherein when the first SIM is a data preferred SIM, these operations further include performing an RRC connection release for the RRC connection with the first network.

[0110] In the nineteenth embodiment, according to the processor of the eighteenth embodiment, performing RRC connection release includes: transmitting a UE Assistance Information (UAI) message including an RRC connection release request to a first network, and receiving an RRC connection release from the first network.

[0111] In a twentieth embodiment, according to the processor of the first embodiment, wherein the transmitter is associated with a second SIM, wherein the UE includes an additional transmitter associated with a first SIM, and wherein the operations further include: tuning the additional transmitter to a frequency of a first network; setting a first maximum transmission power of the additional transmitter to zero and a second maximum transmission power of the transmitter to a non-zero value when the transmitter needs to communicate with the second network; and setting the first maximum transmission power of the additional transmitter to a non-zero value and the second maximum transmission power of the transmitter to zero when the additional transmitter needs to communicate with the first network.

[0112] In the twenty-first embodiment, the user equipment (UE) includes a transceiver configured to communicate with a first network and a second network, and a processor communicatively coupled to the transceiver and configured to perform operations including: initiating a first voice call using the first network associated with a first user identity module (SIM) of the UE; receiving from the second network a paging request indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is active; performing a radio resource control (RRC) connection establishment with the second network; transmitting to the second network an indication that the UE should be configured to have a single component carrier (CC); and exchanging Session Information Protocol (SIP) messages with the second network to retrieve the caller identifier (ID) of the incoming call.

[0113] In the twenty-second embodiment, the base station includes a transceiver configured to communicate with a user equipment (UE) and a processor communicatively coupled to the transceiver and configured to perform operations including: transmitting to the UE a paging request indicating an incoming voice call associated with a second user identity module (SIM) of the UE, wherein the UE receives the paging request while a first voice call associated with a first SIM of the UE is active; performing a radio resource control (RRC) connection establishment with the UE; receiving from the UE an indication that the UE should be configured to have a single component carrier (CC); suspending dual connectivity (DC) and carrier aggregation (CA); and exchanging Session Information Protocol (SIP) messages with the UE to provide the UE with the caller identifier (ID) of the incoming call.

[0114] In the twenty-third embodiment, the user equipment (UE) includes a transceiver configured to communicate with a first network and a second network, and a processor communicatively coupled to the transceiver and configured to perform operations including: initiating a first voice call using the first network associated with a first user identity module (SIM) of the UE; receiving from the second network a paging request indicating an incoming voice call associated with a second SIM of the UE, wherein the paging request is received while the first voice call is active; performing a radio resource control (RRC) connection establishment with the second network; exchanging Session Information Protocol (SIP) messages with the second network to retrieve the caller identifier (ID) of the incoming call; and tuning the UE's transmitter to a frequency associated with the second network for one or more predetermined time periods during the RRC connection establishment and the SIP message exchange with the second network.

[0115] 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.

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

[0117] 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.

[0118] 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. A processor for a multi-user identity module (MUSIM) user equipment (UE), the processor being configured to perform operations including: Initiate a first voice call using a first network associated with the first user identity module (SIM) of the MUSIM UE; Receive a paging request from the second network indicating an incoming voice call associated with the second SIM of the MUSIM UE, wherein the paging request is received while the first voice call is active; Perform Radio Resource Control (RRC) connection establishment with the second network; The second network transmits an indication that the UE should be configured to have a single component carrier CC, wherein the indication is generated by a component carrier CC having a value of zero. maxAggrBW The information element IE provides an implicit instruction, and said instruction is configured to cause the second network to suspend dual-connectivity DC and carrier aggregation CA; and Exchange Session Information Protocol (SIP) messages with the second network to retrieve the caller ID of the incoming call; Perform one of the following actions: accept the incoming voice call or reject the incoming voice call; When the incoming voice call is rejected: Transmit a UE Assistance Information (UAI) message, including an RRC connection release request, to the second network; as well as Receive RRC connection release from the second network; as well as When the incoming voice call is accepted, the operation further includes: Transmit the UAI message, including the RRC connection release request, to the first network; as well as Receive the RRC connection release from the first network.

2. The processor of claim 1, wherein the indication is an explicit indication provided as part of an RRC connection establishment completion message sent by the MUSIM UE to the second network.

3. The processor according to claim 1, wherein the operation further comprises: A second indication is transmitted to the second network that dual-connection DC and carrier aggregation CA can be recovered.

4. The processor of claim 3, wherein the second indication is provided as part of an RRC reconfiguration completion message sent by the MUSIM UE to the second network.

5. The processor of claim 3, wherein the second indication is provided as part of a UE Assistance Information (UAI) message sent by the MUSIM UE to the second network.

6. A processor for a base station configured to perform operations, the operations including: Transmit a paging request to a multi-user identity module (MUSIM) user equipment (UE) indicating an incoming voice call associated with a second SIM of the MUSIM UE, wherein the MUSIM UE receives the paging request while a first voice call associated with a first SIM of the MUSIM UE is active; Perform Radio Resource Control (RRC) connection establishment with the MUSIM UE; The MUSIM UE receives an indication that it should be configured to have a single component carrier CC, wherein the indication is generated by a component carrier CC having a value of zero. maxAggrBW The information element IE provides an implicit instruction, and said instruction is configured to cause the base station to suspend dual connectivity DC and carrier aggregation CA; Suspend dual-connectivity DC and carrier aggregation CA; as well as Exchange Session Information Protocol (SIP) messages with the MUSIM UE to provide the MUSIM UE with the caller ID of the incoming call; In response to the MUSIM rejecting the voice call, a UE Assistance Information (UAI) message including an RRC connection release request is received from the MUSIM UE; as well as Transmit RRC connection release to the MUSIM UE.

7. The processor of claim 6, wherein the indication is an explicit indication provided as part of an RRC connection establishment complete message received from the UE.

8. The processor of claim 6, wherein when the incoming voice call is accepted, the operation further includes: Receive a second indication from the UE that DC-CA can be recovered; as well as Restore DC-CA.

9. The processor of claim 8, wherein the second indication is provided as part of an RRC reconfiguration completion message received from the UE.

10. The processor of claim 8, wherein the second indication is provided as part of a UE Assistance Information (UAI) message received from the UE.

Images