Methods, devices, and computer storage media for multi-sim ue capability indication and band conflict resolution

Abstract

The present disclosure relates to multi-SIM UE capability indication and band conflict resolution. Apparatuses and related methods for operating a dual-subscriber identity module (SIM) dual standby (DSDS) user equipment device (UE) configured with a first SIM and a second SIM. The UE transmits, using the first SIM, a connection request message to a base station over a first network, where the connection request message includes one or more capability indications of the UE. The UE receives a connection accept message from the base station, where the connection accept message contains one or more network capability indications corresponding to respective ones of the one or more UE capability indications. The UE performs communications with the base station in accordance with the one or more network capability indications.

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communications, and more particularly, to a user equipment (UE) having multiple subscriber identity modules (SIMs) and performing dual SIM dual standby (DSDS) operation. Background Art

[0002] The use of wireless communication systems is rapidly increasing. Furthermore, wireless communication technology has evolved from being solely for voice communication to also include the transmission of data, such as the internet and multimedia content. To enable a wireless device to access a wireless communication network (e.g., a cellular telecommunications network) in accordance with at least some wireless communication technologies and standards, a user may subscribe to a service provider ("carrier"), which in turn may provide such services to the user, for example, via the wireless communication network operated by the carrier. Such users in a wireless communication network are typically assigned user identity information, which may be stored in the user's wireless device, for example, as part of a subscriber identity module (SIM). For example, many wireless devices may be provided with a slot for a removable subscriber identity module (SIM) card. Providing such a slot enables users to select and / or change their subscriber identity independently of the wireless device, as users can switch from their current SIM card to a different SIM card at any given time as needed. More recently, UE devices may be equipped with an embedded SIM (eSIM), in which embedded memory in the UE stores the user's subscriber identity information.

[0003] Many UE devices today are designed as dual-SIM or multi-SIM phones, allowing the UE to store two or more sets of user identity information. This allows the UE to, for example, store a first set of user identity information for a user's home phone number and a second set of user identity information for a user's business phone number. Alternatively or additionally, one of the SIM cards can be used primarily for voice calls, while the other can be used primarily for data transmission.

[0004] One type of dual-SIM UE is called Dual-SIM Dual Active (DSDA) and may include multiple receiver (Rx) and / or transmitter (Tx) architectures. A DSDA UE is capable of using two SIMs and two radio components to maintain two sets of active data communications simultaneously. For example, the UE may use one SIM to make a voice call while performing data communications (e.g., internet browsing) on ​​the second SIM.

[0005] Another type of dual-SIM UE may have only a single Rx and / or Tx architecture (e.g., to save cost and reduce size requirements) and may be referred to as dual-SIM dual standby (DSDS). In a UE that includes only a single receiver, only one SIM may be active at any given time. Thus, when the UE is conducting a voice call using the first SIM, the second SIM will be idle. In some cases, when a SIM is currently in use and the UE detects the initiation of a higher-priority activity that requires the other SIM, the UE may suspend the activity on the first SIM in order to conduct the higher-priority activity on the other SIM. In a UE with multiple SIM devices and only one radio, the UE may experience network issues when the SIM suspends and then resumes the radio resource control (RRC) connection with the network.

[0006] In order to increase coverage and better serve the increasing demand and scope of intended uses of wireless communications, in addition to the above-mentioned communication standards, there are also wireless communication technologies being developed, including 3GPP fifth-generation (5G) New Radio (NR) communications. Therefore, improvements are expected in areas that support such development and design, particularly in terms of multi-user identity functionality. Summary of the Invention

[0007] In view of the above and other considerations, it is desirable to extend the functionality of wireless devices with respect to user identity. In particular, it is desirable to provide improved capability information exchange between wireless devices and networks in an energy-efficient manner. The present disclosure relates to such techniques for exchanging capability indications according to various embodiments.

[0008] Therefore, embodiments of the present disclosure may relate to a method for exchanging capability information in a multi-SIM device, a UE device configured to implement this method, and / or a non-transitory computer-accessible storage medium storing program instructions that can be executed by a processor to implement this method. The multi-SIM device can be of various types, including but not limited to a dual-SIM dual standby (DSDS) UE device, a single-receive DSDS (SR-DSDS) device, a dual-receive DSDS (DR-DSDS) device, a dual-SIM dual-pass (DSDA) device, or any type of device with more than two SIMs. The UE device may include a radio component for performing wireless communications (e.g., including one or more antennas and / or other radio components). The UE device may also include a processor configured to implement part or all of the method (e.g., by executing program instructions). The UE device may also include one or more user interface elements, such as a display. In addition, the UE device may include a non-transitory computer-accessible storage medium that can store program instructions that can be executed by the processor of the UE.

[0009] In some embodiments, a DSDS UE is configured with a first SIM and a second SIM, wherein each of the first SIM and the second SIM is coupled to a radio and configured for use with the radio of the UE for wireless communication.

[0010] In some embodiments, the UE is configured to send a connection request message to the base station via the first network, wherein the connection request message includes one or more capability indications of the UE. In various embodiments, the one or more UE capability indications may include an indication that the UE supports requesting a short or long network handover; an indication of whether the UE supports one or both of periodic and one-time short network handovers; and / or a preference for requesting a short or long network handover based on a duration of the network handover, a cause of the network handover, and / or a radio resource control (RRC) state preference for the network handover.

[0011] Alternatively or additionally, in some embodiments, the one or more UE capability indications include frequency band conflict information related to the first SIM and the second SIM, wherein the frequency band conflict information can be used by the first network to avoid frequency band conflicts between communications using the first SIM and the second SIM.

[0012] The UE is further configured to receive a message from the base station, wherein the message includes one or more network capability indications corresponding to respective UE capability indications in the one or more UE capability indications. The message received from the base station may be a connection accept message (e.g., an attach accept message (in LTE) or a registration accept message (in 5G)), or it may be an initial registration message received before establishing a connection between the UE and the network. The network capability indication may include an indication that the first network supports selective provision of short or long network handover, an indication that the first network allows one or both of periodic and one-time short network handover, an indication that the first network allows one or more handover attributes for requesting short or long network handover, and / or an indication that the base station supports providing a paging cause indicator together with a paging message.

[0013] The UE is further configured to perform communications with the base station in accordance with the one or more network capability indications.

[0014] Such techniques may be used individually or in any combination as desired. According to various embodiments, wireless devices implementing such techniques may improve communication performance in at least some cases.

[0015] It should be noted that the techniques described herein may be implemented in and / or used with several different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablets, wearable devices, and various other computing devices.

[0016] This summary is intended to provide a brief overview of some of the subject matter described in this document. Therefore, it should be understood that the above-described features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, accompanying drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] A better understanding of the presently disclosed subject matter may be obtained when the following detailed description of the preferred embodiments is considered in conjunction with the following drawings, in which:

[0018] Figures 1 to 2 An exemplary wireless communication system between a UE device and one or more networks via one or more base stations according to some embodiments is shown;

[0019] Figure 3 illustrates an exemplary cellular network system including an evolved packet core (EPC) according to some embodiments;

[0020] Figure 4 shows an example block diagram of a user equipment device according to some embodiments;

[0021] Figure 5 shows an exemplary block diagram of a base station according to some embodiments;

[0022] Figure 6 is a network communication flow diagram illustrating a method for providing reactive frequency band conflict indication according to some embodiments;

[0023] Figure 7 is a network communication flow diagram illustrating a method for providing proactive band conflict indication according to some embodiments;

[0024] Figure 8 is a network communication flow diagram illustrating a method for providing UE capability reporting to avoid frequency band conflicts according to some embodiments;

[0025] Figure 9 is a network communication flow diagram illustrating a method for exchanging multi-SIM capability information in a Fifth Generation New Radio (5G NR) network according to some embodiments;

[0026] Figure 10 is a network communication flow diagram illustrating a method for exchanging multi-SIM capability information in a Long Term Evolution (LTE) network according to some embodiments; and

[0027] Figure 11 is a flow chart illustrating a method for exchanging UE and network capability indications according to some embodiments.

[0028] While the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. However, it should be understood that the drawings and detailed description thereof are not intended to limit this disclosure to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0029] Acronyms

[0030] The following acronyms are used in this disclosure:

[0031] 3GPP: Third Generation Partnership Project

[0032] 3GPP2: Third Generation Partnership Project 2

[0033] GSM: Global System for Mobile Communications

[0034] UMTS: Universal Mobile Telecommunications System

[0035] LTE: Long Term Evolution

[0036] LTE-A: LTE Advanced

[0037] 5G NR: Fifth Generation New Radio

[0038] SIM: Subscriber Identity Module

[0039] eSIM: embedded SIM

[0040] IMSI: International Mobile Subscriber Identity

[0041] MCC: Mobile Country Code

[0042] MNC: Mobile Network Code

[0043] the term

[0044] The following is a glossary of terms used in this disclosure:

[0045] Storage Media—various types of memory devices or storage devices. The term "storage medium" is intended to include installation media, such as CD-ROMs, floppy disks, or tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media, such as hard drives or optical storage devices; registers, or other similar types of memory elements, etc. Storage media may also include other types of memory, or combinations thereof. Furthermore, a storage medium may be located in a first computer system executing a program, or in a different second computer system connected to the first computer system via a network, such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer system for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems connected via a network. A storage medium may store program instructions (e.g., represented as a computer program) that may be executed by one or more processors.

[0046] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic, or digital signals.

[0047] Programmable hardware elements—include various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can vary in size from fine-grained (combinatorial logic components or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "reconfigurable logic."

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

[0049] User Equipment (UE) (or "UE device") - any type of mobile or portable computer system device that performs wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhones TM , based on Android TMphones), wearable devices (e.g., smart watches, smart glasses), portable gaming devices (e.g., Nintendo DS TM PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, PDAs, portable internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to include any electronic device, computing device and / or telecommunication device (or combination of devices) that is easy for a user to transport and capable of wireless communication.

[0050] Base Station—The term “base station” has the full breadth of its ordinary meaning to include at least a wireless communication station installed at a fixed location for communicating as part of a wireless telephone system or radio communication system.

[0051] Processing Element—refers to various elements or combinations of elements. Processing elements include, for example, circuits such as ASICs (Application Specific Integrated Circuits), portions or circuits of individual processor cores, entire processor cores, individual processors, programmable hardware devices such as field programmable gate arrays (FPGAs), and / or larger portions of systems including multiple processors.

[0052] Automatic—refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without requiring user input to directly specify or execute the action or operation. Thus, the term "automatic" is in contrast to manual execution or specification of an action by a user, where the user provides input to directly execute the action. An automatic process may be initiated by input provided by a user, but the subsequent actions performed "automatically" are not specified by the user, i.e., they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting checkboxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user's actions. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without requiring any user input to specify the answers to the fields. As indicated above, a user may invoke automatic filling of a form without participating in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields, but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions that a user has taken.

[0053] Configured to—Various components may be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad statement that generally means “having the structure” to perform one or more tasks during operation. Thus, a component can be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some contexts, “configured to” may be a broad statement that generally means “having the circuitry” to perform one or more tasks during operation. Thus, the component can be configured to perform a task even when the component is not currently turned on. Generally, the circuitry that forms the structure corresponding to “configured to” may include hardware circuitry.

[0054] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to." Listing components configured to perform one or more tasks expressly does not invoke the interpretation of 35 U.S.C. §112, sixth paragraph, regarding components.

[0055] Figures 1 to 3 -Communication system

[0056] Figure 1 and Figure 2 An exemplary (simplified) wireless communication system is shown. Note that Figure 1 and Figure 2 The systems are merely examples of some possible systems, and embodiments may be implemented in any of a variety of systems as desired.

[0057] Figure 1 An exemplary wireless communication system includes a base station 102A that communicates with one or more user equipment (UE) devices 106A, 106B, etc., via a medium transmission. For example, via 106N. Each of the user equipment devices may be referred to herein as a "user equipment" (UE). Figure 2 In the exemplary wireless communication system of FIG, in addition to base station 102A, base station 102B also communicates (e.g., simultaneously or concurrently) with UE devices 106A, 106B, etc. via a transmission medium. For example, via 106N. If base station 102A is implemented in an LTE environment, it may also be referred to as an "eNodeB" or "eNB." If base station 102A is implemented in a 5G NR environment, it may also be referred to as a "gNodeB" or "gNB."

[0058] Base stations 102A and 102B may be base transceiver stations (BTS) or cell sites, and may include hardware that enables wireless communications with user devices 106A through 106N. Each base station 102 may also be equipped to communicate with a core network 100 (base station 102A may be coupled to core network 100A, while base station 102B may be coupled to core network 100B), which may be a core network of a cellular service provider. Each core network 100 may also be coupled to one or more external networks (such as external network 108), which may include the Internet, a public switched telephone network (PSTN), or any other network. Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100A; in Figure 2 In the exemplary system of FIG. 1 , base station 102B may also facilitate communications between user devices and / or between user devices and network 100B.

[0059] The base stations 102A and 102B and the user equipment may be configured to communicate over a transmission medium using any of a variety of radio communication access technologies (RATs), also known as radio communication technologies or telecommunication standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), 5G NR, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc.

[0060] For example, base station 102A and core network 100A may operate according to a first cellular communication standard (e.g., LTE), while base station 102B and core network 100B may operate according to a second (e.g., different) cellular communication standard (e.g., GSM, UMTS, and / or one or more CDMA2000 cellular communication standards). The two networks may be controlled by the same network operator (e.g., a cellular service provider or "carrier") or different network operators. In addition, the two networks may operate independently of each other (e.g., if they operate according to different cellular communication standards), or may operate in a somewhat coupled or tightly coupled manner.

[0061] Also note that, although Figure 2The exemplary network configuration shown may use two different networks to support two different cellular communication technologies, but other network configurations that implement multiple cellular communication technologies are also possible. As an example, base stations 102A and 102B may operate according to different cellular communication standards but be coupled to the same core network. As another example, a multi-mode base station capable of simultaneously supporting different cellular communication technologies (e.g., LTE and 5G NR, GSM and UMTS, or any other combination of cellular communication technologies) may be coupled to a core network that also supports different cellular communication technologies. Any other various network deployment scenarios are also possible.

[0062] As another possibility, base station 102A and base station 102B may operate according to the same wireless communication technology (or overlapping set of wireless communication technologies). For example, base station 102A and core network 100A may be operated by a cellular service provider that is independent of base station 102B and core network 100B, and base station 102B and core network 100B may be operated by different (e.g., competing) cellular service providers. Thus, in this case, despite utilizing similar and potentially compatible cellular communication technologies, UE devices 106A-106N may independently communicate with base stations 102A-102B, possibly by utilizing separate subscriber identities to communicate with the networks of different operators.

[0063] UE 106 is capable of communicating using multiple wireless communication standards. For example, UE 106 can be configured to communicate using either or both of a 3GPP cellular communication standard (such as LTE) and / or a 3GPP2 cellular communication standard (such as a cellular communication standard in the CDMA2000 family of cellular communication standards). As another example, UE 106 can be configured to communicate using different 3GPP cellular communication standards (e.g., two or more of GSM, UMTS, 5G NR, LTE, or LTE-A). Thus, as described above, UE 106 can be configured to communicate with base station 102A (and / or other base stations) according to a first cellular communication standard (e.g., LTE), and can also be configured to communicate according to a second cellular communication standard (e.g., one or more CDMA2000 cellular communication standards, UMTS, GSM, etc. (with base station 102B) and / or other base stations).

[0064] Thus, base stations 102A and 102B, as well as other base stations operating according to the same or different cellular communication standards, may be provided as one or more cell networks that may provide continuous or nearly continuous overlapping service to UEs 106a-106n and similar devices over a wide geographic area via one or more cellular communication standards.

[0065] The UE 106 may also or alternatively be configured to communicate using WLAN, Bluetooth, one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), etc. Other combinations of wireless communication standards, including more than two wireless communication standards, are also possible.

[0066] UE 106 may be a device with wireless network connectivity, such as a mobile phone, handheld device, computer or tablet, or substantially any type of wireless device.

[0067] The UE may include a processor configured to execute program instructions stored in a memory. The UE may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, the UE may include a programmable hardware element such as an FPGA (field programmable gate array) configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0068] The UE 106 can be configured to communicate using any of a number of wireless communication protocols. For example, the UE 106 can be configured to communicate using two or more of GSM, UMTS (W-DCMA, TD-SCDMA, etc.), CDMA2000 (1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), 5G NR, LTE, LTE-A, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0069] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols. The UE 106 may share one or more portions of a receive chain and / or a transmit chain between multiple wireless communication standards; for example, the UE 106 may be configured to communicate using one (or both) of GSM or LTE using a single shared radio. The shared radio may include a single antenna or may include multiple antennas for performing wireless communication (e.g., for MIMO).

[0070] Figure 3 -Exemplary cellular network

[0071] Figure 3 shows an exemplary cellular network

[0072] 1 is a simplified block diagram of a wireless communication system, which is particularly useful for implementing the various embodiments described herein. As shown, a UE 106 can communicate with a cellular network, wherein the cellular network can include a base station 102 (e.g., an eNB or gNB for LTE or 5G NR, respectively) and a core, such as an evolved packet core (EPC) in LTE or a 5G core (5GC) in 5G. The UE 106 can communicate with the base station 102 wirelessly. In turn, the base station 102 can be coupled to the core network, shown as EPC / 5GC 101 in the example embodiment. As shown, the EPC / 5GC 101 can include a mobility management entity (MME) (in LTE) or an access and mobility function (AMF) (in 5G) 322, a home subscriber server (HSS) (in LTE) or an authentication server function (AUSF) and a unified data manager (UDM) (in 5G) 324, and a serving gateway (SGW) (in LTE) or a user plane function (UPF) (in 5G) 326. The EPC / 5GC 100 may also include various other devices known to those skilled in the art.

[0073] The operations described herein performed by a cellular network (or NW) may be performed by Figure 3 The cellular network operations may be performed by one or more of the cellular network devices shown, such as the base station 102, MME / AMF 322, HSS 324, or SGW / UPF 326 in the EPC / 5GC 100, as well as other possible devices.

[0074] Figure 4 -Exemplary block diagram of UE

[0075] Figure 4 A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, the UE 106 may include a system on a chip (SOC) 300, which may include components for various purposes. For example, as shown, the SOC 300 may include a processor 302 that can execute program instructions for the UE 106 and a display circuit 304 that can perform graphics processing and provide display signals to a display 345. The processor 302 may also be coupled to a memory management unit (MMU) 340 and / or other circuits or devices (such as the display circuit 304, the radio component 330, the connector I / F 320, and / or the display 345). The MMU 340 may be configured to receive addresses from the processor 302 and convert those addresses into locations in a memory (e.g., the memory 306, the read-only memory (ROM) 350, the NAND flash memory 310). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0076] As shown, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), a connector interface 320 (e.g., for coupling to a computer system, docking station, charging station, etc.), a display 345, and wireless communication circuitry 330 (e.g., for LTE, LTE-A, NR, CDMA2000, Bluetooth, Wi-Fi, GPS, etc.). The UE device 106 may include at least one antenna (e.g., 335a) and may include multiple antennas (e.g., as shown by antennas 335a and 335b) for performing wireless communications with base stations and / or other devices. Antennas 335a and 335b are shown by way of example, and the UE device 106 may include fewer or more antennas. In general, one or more antennas are collectively referred to as antennas 335. For example, the UE device 106 may use antennas 335 with the aid of radio circuitry 330 to perform wireless communications. As described above, in some embodiments, the UE may be configured to perform wireless communications using multiple wireless communication standards.

[0077] As further described later herein, the UE 106 (and / or the base station 102) may include hardware and software components for implementing the implicit radio resource control state transition method for at least the UE 106 to perform in the cellular communication system. The processor 302 of the UE device 106 may be configured to implement part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or as an ASIC (application-specific integrated circuit). In addition, as Figure 3 As shown, one or more processors 302 can be coupled to other components and / or can interoperate with other components to perform implicit radio resource control state transitions in a cellular communication system according to various embodiments disclosed herein. The processor 302 can also implement various other applications and / or end-user applications running on the UE 106.

[0078] In some embodiments, radio 330 may include separate controllers dedicated to controlling communications for various corresponding RAT standards. Figure 3 As shown, the radio component 330 may include a Wi-Fi controller 332, a cellular controller (eg, an NR controller) 334, and a BLUETOOTH controller. TMController 336, and in at least some embodiments, one or more or all of these controllers may be implemented as respective integrated circuits (ICs or chips) that communicate with each other and with SOC 300 (more specifically, with one or more processors 302). For example, Wi-Fi controller 332 may communicate with cellular controller 334 via a cell-ISM link or WCI interface, and / or BLUETOOTH controller 336. TM Controller 336 may communicate with cellular controller 334 via a cell-ISM link, etc. Although three separate controllers are shown within radio 330 , other embodiments have fewer or more similar controllers for the various different RATs that may be implemented in UE device 106 .

[0079] As shown, UE 106 may also include two or more Subscriber Identity Modules (SIMs) 360 and 362. One or both of SIMs 360 and 362 may be implemented as embedded SIMs (eSIMs). In this case, SIMs 360 and / or 362 may be implemented in device hardware and / or software. For example, in some embodiments, UE 106 may include an embedded UICC (eUICC), e.g., a device that is built into UE 106 and non-removable. The eUICC may be programmable, allowing one or more eSIMs to be implemented on the eUICC. In other embodiments, the eSIM may be installed in UE 106 software, e.g., as program instructions stored on a storage medium (such as memory 306 or Flash 310) that is executed on a processor (such as processor 302) in UE 106. As an example, SIM 360 may be an application executing on a universal integrated circuit card (UICC). Alternatively or additionally, one or both of SIMs 360 and 362 may be implemented as removable SIM cards.

[0080] Each SIM 360 or 362 may include various types of information, including personalized information specific to a user and / or device (e.g., personalized information), and information not specific to a user and / or device (e.g., public information). This personalized information may include user / unit specific data, such as information identifying the user / unit to its carrier network, personalized authorization and / or security information, etc. Some or all of this personalized information may be used as a user identity for the UE 106, for example, to identify the UE 106 to the carrier's network and obtain cellular service from the carrier.

[0081] As an example, the personalized information may include one or more International Mobile Subscriber Identity (IMSI) codes. The IMSI identifies a user to their carrier's network. The IMSI may, for example, be a number that includes the user's "home" Mobile Country Code (MCC) and Mobile Network Code (MNC), as well as the user's unique Mobile Subscription Identity (MSIN). The personalized information may also or alternatively include a Personal Identification Number (PIN) (e.g., a code that a user can use to access their SIM card), a Personal Unlock Code and / or Personal Unlock Key (PUC / PUK), and one or more Authentication Keys (K / Ki). Any of a variety of other personalized information may also or alternatively be used, as desired.

[0082] Thus, each SIM 360 and 362 may contain subscriber identity information that can be used to identify the UE 106 to its subscriber's carrier cellular network. As described above, the UE 106 may utilize multiple subscriber identities. For example, a user may desirably obtain service from multiple carriers for any of a variety of reasons, including different coverage / service areas of different carriers, different service plans / pricing offered by different carriers, or different technologies employed. In some cases, it may be desirable to utilize multiple subscriber identities (whether from the same or different carriers) as a means of differentiating between types of interactions, such as work-related communications and personal communications.

[0083] As another possibility, situations may arise where it may be desirable for some operators implementing LTE networks to utilize multiple user identities in a single device. Specifically, in many cases, an LTE (e.g., as a packet-switched communication technology) network may be (at least initially) deployed for data communications (e.g., web browsing, email, and other networking applications, etc.), while a (e.g., pre-existing) GSM and / or UMTS (e.g., which may include circuit-switched communication technologies) network may be utilized for voice communications.

[0084] As further described below, the UE may implement various techniques that enable a particular SIM to perform suspend and resume operations with a cellular network while reducing interruptions due to RRC state mismatches. Accordingly, as further described later herein, the UE 106 may include hardware and software components for implementing methods for improving suspend / resume operations when transitioning between different SIMs.

[0085] The processor 302 of the UE device 106 may be configured to implement some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, the processor 302 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit).

[0086] Figure 5 - Example block diagram of a base station

[0087] Figure 5 An exemplary block diagram of a base station 102 is shown. Note that Figure 5 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processor 102 and convert these addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or to other circuits or devices.

[0088] The base station 102 may include at least one network port 470. The network port 470 may be configured to couple to a telephone network and provide access to the telephone network as described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0089] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0090] The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio 430. The antenna 434 communicates with the radio 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio 430 may be configured to communicate via various radio communication standards, including but not limited to LTE, WCDMA, CDMA2000, and the like.

[0091] The processor 404 of the base station 102 may be configured to implement part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit), or a combination thereof.

[0092] like Figure 3 The cellular network device shown may have a somewhat similar architecture to that described above, but typically does not include RF circuitry or antennas. Figure 3 Each of the cellular network devices shown will typically have a processing element and memory for performing its respective functions.

[0093] As used herein, a network or cellular network (e.g., NW1 and / or NW2 as described below) may refer to one or more physical entities included within the network infrastructure to perform the methods described. Figure 5 The gNB (or eNB) shown may receive instructions and messages directly from the UE and may relay these messages from the UE to the Access and Mobility Management Function (AMF) or Mobility Management Entity (MME) on the core network side. The MME (or AMF) may notify the eNB (or gNB) to retain the UE's RRC context (i.e., connection state and / or established EPS bearers / PDU sessions and QoS details), the MME (or AMF) may start a timer, and if the timer expires before the suspended SIM is resumed, the MME (or AMF) may notify the Serving Gateway (S-GW) or User Plane Function (UPF) to release the UE's bearer / PDN context, and notify the eNB (or gNB) to release the UE context (i.e., forget the C-RNTI and other state information of the UE and consider the UE to be idle). If the timer is running and the eNB (or gNB) receives an RRC resume request from the UE, the eNB (or gNB) may confirm that the C-RNTI exists and the UE context can be restored and may forward the resume request to the MME (or AMF), which may notify the S-GW (or UPF) to modify the radio bearers (e.g., if they had previously told the S-GW or UPF to freeze their context), stop the timer, and / or continue as if the UE were connected. In other words, the eNB-MME-SGW combination for LTE or the gNB-AMF-UPF combination for 5G NR may be understood as being interconnected to perform the embodiments described herein.

[0094] Radio Resource Control Status

[0095] Various cellular communication technologies include the use of a Radio Resource Control (RRC) protocol (e.g., which may facilitate connection establishment and release, radio bearer establishment, reconfiguration, and release) and / or various other possible signaling functions supporting the air interface between a wireless device and a cellular base station.

[0096] A wireless device (e.g., such as UE 106) can generally operate in one of a number of possible conditions (e.g., states or modes) with respect to RRC. For simplicity, the condition of a wireless device with respect to RRC may subsequently be referred to herein as its RRC state. For example, in LTE, a wireless device can operate in an RRC connected state (e.g., where the wireless device can perform continuous data transmission and where handovers between cells are managed by the network and access stratum context information is retained for the wireless device), or can operate in an RRC idle state (e.g., where the wireless device can operate in a battery-efficient state when not performing continuous data transmission, where the wireless device can handle its cell reselection activities, and where the network may not retain access stratum context information for the wireless device).

[0097] In addition to the RRC Connected state and the RRC Idle state, at least according to some embodiments, one or more other types of RRC states may be supported for wireless devices. For example, for 5G NR, an RRC Inactive state may be supported, in which the wireless device can operate in a relatively battery-efficient manner while the network retains at least some access stratum context information. At least according to some embodiments, this state may be based on wireless device mobility, for example, allowing the wireless device to move within a Radio Access Network Notification Area (RNA) without notifying the Next Generation (NG) Radio Access Network (RAN). While in this state, the wireless device may, for example, perform cell reselection and system information acquisition based at least in part on system information broadcast by potential candidate cells. Simultaneously, the last serving base station (e.g., gNB) may maintain the wireless device context and the NG connection with the 5G Core Network (CN) associated with the wireless device, for example, to facilitate easier transition back to the RRC Connected state. When paging the wireless device in the RRC Inactive state, the RAN may use RNA-specific parameters, including, for example, UE-specific discontinuous reception (DRX) and a UE identity index value (e.g., I-RNTI).

[0098] At least in some cases, using the RRC inactive state can help reduce network signaling overhead for wireless device connections. For example, for wireless devices with infrequent data transmission, using this RRC inactive state can reduce the amount of required mobility-related signaling (e.g., for handovers) compared to using the RRC connected state, for example, because the wireless device may be able to manage its own cell reselection process when moving between cells. For such wireless devices, using the RRC inactive state can also reduce the amount of required connection establishment-related signaling compared to using the RRC idle state, for example, because the network can retain at least some context information for the wireless device. This can directly reduce the signaling latency associated with transitioning to the RRC connected state.

[0099] As another potential benefit, such a state can reduce control plane latency for the wireless device compared to operating in the RRC Idle state. For example, it is possible that the access stratum connection establishment period and / or the non-access stratum connection establishment period can be shortened for the RRC Inactive state relative to the RRC Idle state. Thus, the time to transition from a battery-efficient state to the start of continuous data transmission can be reduced.

[0100] Additionally, such a state may improve power saving capabilities of the wireless device compared to operating in the RRC connected state, for example. For example, serving and / or neighbor cell measurements may be required more frequently when in the RRC connected state than when in the RRC inactive state, e.g., at least in accordance with a discontinuous reception (C-DRX) cycle of the wireless device's connection.

[0101] One use case that may be common (or becoming common) in cellular communication systems may include what may be referred to as a massive machine type communication (mMTC) scenario. For example, in an mMTC scenario, there is a high density of devices in the cellular network that tend to perform small, periodic data communication activities. For such devices, once data transmission is complete, the device's RRC connection may be released, at least as a possibility, after a predetermined connection activity period, via explicit RRC connection release signaling provided by the network. However, in at least some cases, for mMTC scenarios, such an explicit mechanism for releasing the RRC connection may result in a heavy signaling load on the network. Furthermore, using a predetermined connection inactivity period before RRC connection release may represent a potential waste of power, for example, because it may ensure that the wireless device can spend at least a certain amount of time in the RRC Connected state, but without performing any data activity before being released to the potentially more power-efficient RRC Idle or RRC Inactive state. This may be particularly costly for some machine type communication (MTC) devices that may be highly power-constrained (e.g., having a battery life expectancy of 5 to 10 years, among other possibilities, depending on various implementations).

[0102] Frequency band conflicts for multi-SIM devices

[0103] As described above, some UE devices may be able to contain multiple subscriber identity modules or SIMs. In some cases, these SIMs may be universal SIMs or USIMs. Some UE devices with multiple SIMs, i.e., dual SIM (e.g., dual SIM dual standby (DSDS) devices) and multi-SIM devices, including multi-USIM (or MUSIM) devices, may have any combination of single or multiple receivers and transmitters. In other words, different multi-SIM UEs may have a single receiver (Rx) system (shared between multiple SIMs) or a multi-Rx system (where each SIM has a dedicated receiver) to perform cellular communications for their multiple SIMs. Similarly, a multi-SIM UE may have one or more transmitters. For multi-SIM UEs that share a single receiver and / or transmitter between multiple SIMs, it may be necessary to time-share the receiver and / or transmitter by pausing activity on one SIM while performing another activity on another SIM to receive and / or transmit.

[0104] Some DSDS devices can operate as dual-SIM dual access (DSDA) devices, where a DSDA device is configured with two receivers and two transmitters, with each of the two SIM cards in the DSDA device having its own dedicated transmitter and receiver. These devices are capable of transmitting and receiving communications with both SIMs simultaneously. When the transmitters and / or receivers are tuned to specific frequency bands, simultaneous transmission and / or reception by multiple SIMs can introduce radio frequency (RF) band conflicts. According to some embodiments described herein, these RF band conflicts can be mitigated.

[0105] Some DSDS devices can operate as dual-receiver DSDS (DR-DSDS) devices, where the UE device has dual receivers but only a single transmitter. These devices may be able to receive communications from two SIMs simultaneously, but use a single shared transmitter to alternate their transmission activities. In the DR-DSDS mode of operation, radio frequency band conflicts may occur when both receivers are tuned to specific frequency bands. As an example, a first SIM (SIM1) may reside on a first frequency band, a second SIM (SIM2) may reside on a second frequency band, and both SIMs may be in idle mode. In this example, when the first and second frequency bands conflict during simultaneous reception (e.g., due to band overlap, intermodulation products, or interference between harmonic frequencies), one or both receivers may experience impaired reception for paging reception, system information block (SIB) decoding, or measurements.

[0106] Another example of RF band conflict may occur in a “connected-idle” scenario, where SIM1 is in RRC connected mode on a first band (e.g., band B1), SIM2 is in RRC idle mode on a second band (e.g., band B66), and SIM1 transmissions on the first band introduce direct interference to SIM2 reception on the second band (or some harmonics of the first band transmissions may interfere with reception on the second band). In general, DR-DSDS communications may experience band conflicts, which impairs the UE’s ability to operate in a DR-DSDS configuration. Similar challenges may exist in the DSDA mode of operation, although on a larger scale than DR-DSDS, as simultaneous transmissions on both bands increase interference to other co-located receivers tuned to the other band. Furthermore, these issues may be exacerbated as the number of SIMs in a MUSIM configuration increases.

[0107] Various communication scenarios may result in frequency band conflicts. As a first example, frequency band conflicts may arise in idle-idle (or inactive-inactive, idle-inactive, inactive-idle) configurations, where both SIMs of a dual-SIM device are in a combination of RRC idle and / or inactive states. In these configurations, frequency band conflicts may arise during cell selection, where the serving cell bands of the two SIMs in idle and / or inactive mode conflict with each other (i.e., simultaneous reception for all supported frequency band combinations is not possible or introduces undesirable interference). Additionally, frequency band conflicts may arise when an idle or inactive mode SIM reselects to another frequency band that conflicts with the idle or inactive mode serving band of another SIM.

[0108] As a second example, a band conflict may occur in a connected-idle (or connected-inactive) configuration, where one of the two SIMs is in a connected state and the other SIM is in an idle or inactive state. In these configurations, a band conflict may occur when the SIM in the connected state is measuring a frequency band that conflicts with the serving frequency of the SIM in the idle or inactive state. Additionally, a band conflict may occur when one SIM enters connected mode and transmissions cause interference to the idle or inactive mode SIM. Additionally, the connected mode SIM may be redirected or switched to another frequency band, which causes interference to the serving frequency of the idle or inactive mode SIM. Additionally, a new component carrier, dual connectivity (DC) connection, or multi-RAT dual connectivity (MR-DC) connection may be configured on the connected mode SIM, which conflicts with reception by the idle or inactive mode SIM. As another example, the idle or inactive mode SIM may reselect to another frequency band that creates a band conflict with the transmissions of the connected mode SIM.

[0109] In some embodiments, a dual-SIM UE can take mitigation steps when a frequency band conflict is detected. As a first example, the UE can perform autonomous mitigation (i.e., without first negotiating the mitigation steps with the network). For example, if both SIMs of the UE are in idle mode, one of the SIMs can autonomously reselect to a frequency band that does not conflict with the serving frequency of the other SIM.

[0110] In various embodiments, when performing frequency selection to mitigate frequency band conflicts, the UE may selectively or randomly determine which SIM should perform reselection to a non-conflicting frequency band. For example, the UE may selectively decide which SIM should remain on the current serving cell and which SIM to attempt reselection. The selective determination of which SIM to remain on the current serving frequency may be based on various factors, including but not limited to:

[0111] 1) the RAT used to communicate with each SIM (i.e., a SIM communicating on a newer RAT such as 5G NR may preferentially remain camped on the current frequency, while a SIM communicating with a legacy RAT such as LTE may perform inter-frequency reselection),

[0112] 2) the capabilities provided by each SIM's current serving cell,

[0113] 3) the communication signal strength on each SIM (e.g. a SIM with a weaker signal strength may be selected to perform frequency reselection),

[0114] 4) Data preferences for each SIM and other services mapped to each SIM (e.g., Multi-RAT Dual Connectivity (MR-DC), E-UTRAN New Radio Dual Connectivity (ENDC), Ultra-Reliable Low Latency Communication (URLLC), etc.),

[0115] 5) the probability of finding a non-conflicting frequency for each SIM based on neighboring cells configured in system information or via dedicated signaling, or

[0116] 6) UE mobility, and other possibilities.

[0117] In some embodiments, the data preferred SIM may prioritize maintaining frequency, while the non-data preferred SIM may perform inter-frequency reselection to avoid frequency band conflicts.

[0118] Alternatively, the UE may randomly determine which SIM should remain camped on the serving cell and which SIM should attempt to reselect to another frequency to mitigate the band conflict.

[0119] In some implementations, the UE can switch from DR-DSDS mode to single-receive DSDS (SR-DSDS) mode and stop concurrent reception on conflicting bands. In this mode, a single receiver is time-shared between the two SIMs, depending on the communication requirements of each SIM.

[0120] In some embodiments, the UE may use explicit reporting to the network to mitigate band conflicts rather than autonomously mitigating band conflicts. As a first example, Figure 6 As shown, when a SIM is in connected mode and a band conflict is detected, the UE can provide a reaction indication to the network. For example, the connected mode SIM can transmit a conflict indication to the network using an In-Device Coexistence (IDC) message, a measurement or event report message, or a UE Assistance Information message to indicate the presence of a band conflict and the conflicting frequency bands. Additionally or alternatively, the UE can also report non-conflicting adjacent frequency measurements to help the network decide which non-conflicting adjacent frequency band to perform a handover to the UE for use with the connected mode SIM.

[0121] Additionally, if Figure 7 As shown, the UE can provide active indication to the network before detecting a frequency band conflict. For example, the UE can report the serving cell frequency of the second SIM in idle mode to the network serving the first SIM while establishing a connected mode with the first SIM. Figure 11 As shown, in some embodiments, the proactive indication is provided as a UE capability indication within the connection request message.

[0122] like Figure 8 As shown, as a third possibility, the UE can perform capability reporting, whereby the UE reports the conflicting bands to the network via a UE capability information message (based on the UE configuration). The band conflict information can be grouped into idle-idle, connected-idle and connected-connected groups so that the network is aware of the limitations of the UE in different connection scenarios. The conflicting band combinations can be encoded in a bit mask to allow reporting of multiple band conflicts in the UE capability information message. Additionally, the UE can indicate that it requests band conflict avoidance on the bands that it indicates it supports, and the network can create a band conflict avoidance plan based on a predefined band conflict table. Similar to active reporting, the network can allocate bands to the UE for measurement, switching, redirection and carrier aggregation based on the indication provided by the UE (i.e., avoiding band conflicts).

[0123] In some embodiments, after the UE has sent a reactive or proactive report to the network and the band conflict due to dual receiver activity has been alleviated (e.g., because one of the SIMs is camped on a non-conflicting band), the UE may send a cancellation indication to the network indicating the cancellation of the previously sent band conflict indication to inform the network that the UE is no longer experiencing a band conflict or is at risk of experiencing a band conflict.

[0124] In some embodiments, the network sends a preference indication to the UE indicating a preference as to how the UE should handle band conflicts when in MUSIM mode of operation. In various embodiments, the network may alternatively indicate a) that it does not provide support for band conflict resolution (in which case the UE may then choose to autonomously mitigate band conflicts), or b) that it supports band conflict resolution (in which case the UE may use the various options described above to report band conflicts). The network may indicate support (or lack of support) for band conflict resolution via System Information Broadcast (SIB) messaging or via dedicated signaling (e.g., RRC reconfiguration, RRC establishment, RRC recovery, and / or RRC reestablishment messaging, etc.). As Figure 11 As shown, the preference indication may be provided as a network capability indication in a connect accept message.

[0125] In some embodiments, upon receiving a conflict indication of a frequency band conflict from the UE via a first SIM (e.g., via an IDC message, a UE Assistance Information (UAI) message, or a measurement report), the network may switch the connected mode (first) SIM to another frequency band that does not conflict with the idle mode frequency band of the UE's second SIM. The UE may provide information about conflict-free frequency band measurements in an IDC / UAI / measurement report indicating the frequency band conflict to the NW. Accordingly, or in addition, upon receiving the conflict indication, the network may remove or deactivate a primary cell group (MCG) secondary cell (SCELL) or a secondary cell group (SCG) primary secondary cell (PSCell) or scell from the cell group set of the first SIM to mitigate the frequency band conflict.

[0126] In the case of uplink carrier aggregation (CA) operation with multiple component carriers (CCs), upon receiving a contention indication, the network may allocate uplink physical resource block (PRB) resources on CCs where intermodulation distortion and harmonics do not fall within the frequency range of the system receiver that is in contention.

[0127] In some embodiments, upon receiving a conflict indication, the network may configure a supplementary uplink (SUL) without a paired downlink frequency for UE transmissions instead of a normal UL (i.e., a normal UL with a paired downlink frequency), where the SUL does not conflict with the Rx of the idle mode (second) SIM.

[0128] In some embodiments, when the UE proactively reports the frequency band of the idle mode SIM, the network may refrain from configuring measurements or component carriers on frequencies that conflict with the serving frequency band of the idle mode SIM until the UE reports a change in the serving frequency band of the idle mode SIM. Therefore or alternatively, the network may configure all frequency bands but may prioritize frequency bands that do not conflict for measurements and other dedicated procedures. In some scenarios, proactive reporting of frequency band conflicts by the UE may be preferred over reactive reporting, as reactive reporting may result in increased signaling load in the UL if multiple UEs simultaneously signal to the network to indicate frequency band conflicts (e.g., during mobility scenarios).

[0129] In some embodiments, the network may avoid redirecting, performing handover, adding CCs, or implementing dual connectivity for the first SIM on a frequency band that would conflict with the second SIM.

[0130] Capability indication of network handover and paging reasons

[0131] In some embodiments, a dual SIM UE is configured to provide a UE capability indication to the network to avoid paging conflicts (i.e., between pages to different SIMs of the UE), improve network handover performance, and / or enhance the UE's awareness of the cause of incoming pages.

[0132] In various embodiments, the dual SIMs of the UE may belong to the same or different operators, and they may be physical SIMs or embedded SIMs (eSIMs). Advantageously, the embodiments described herein for providing UE capability indications may be performed without operator (i.e., network) coordination, such that the described methods may operate in a variety of different communication environments served by different network operators and operator types.

[0133] In some embodiments, a UE in an RRC connected state with a first network (NW A) may need to be handed over to a second network (NW B) to conduct protocol activities with NW B (e.g., periodic signaling procedures, paging decoding, or voice calls, among other possibilities). For short signaling activities (e.g., periodic signaling procedures, tracking area updates (TAUs), radio area updates (RNAUs), or paging decoding, among other possibilities), it may be desirable for the UE to request a short handover procedure. Additionally, for long signaling activities or signaling activities with non-deterministic durations (e.g., voice calls), it may be desirable for the UE to request a long handover procedure.

[0134] The network may define a short handover procedure and a long handover procedure for a specific radio access technology (RAT) protocol. In a short handover procedure, NW A may retain some or all of the UE context while the UE is tuned to NW B, because NW A expects the UE to return after a relatively short period of time (e.g., seconds or milliseconds). In contrast, in a long handover procedure, NW A may not retain the UE context, or may not retain as many components of the UE context, because NW A expects the UE to be tuned to NW B for a longer or indeterminate period of time.

[0135] To address these and other issues, in some embodiments, capability information is exchanged between the UE and the network (NW) during initial connection establishment messaging. This capability information exchange can occur at Figure 9 During the registration process shown (e.g., in a 5G NR network), or it may occur as shown in Figure 10 During the attachment procedure shown (e.g., in an LTE network).

[0136] In some embodiments, as part of the initial registration or attachment process to the network, the UE may transmit a registration request message (e.g., Figure 9 as shown) or attach request message) as shown Figure 10 As shown). The UE capability indication may include an indication that the UE supports short handover and / or long handover. It may also indicate whether it supports the ability to request short handover or long handover based on specific handover attributes (e.g., handover duration, handover cause, and / or RRC state preference). In other words, the UE may request the ability to report the requested handover duration as a proxy for whether the requested handover should be a short handover or a long handover (e.g., a requested duration less than a predetermined threshold may correspond to a request for a short handover procedure). Similarly, different handover causes and / or RRC state preferences may correspond to short or long handover procedures.

[0137] The NW may respond to the UE with a Registration Accept or Attach Accept message containing NW capability information. The NW capability information may indicate whether the NW supports the distinction between short and long handovers (i.e., whether the NW can selectively perform either short or long handover in different handover scenarios). When the NW supports selective handover behavior, it may also indicate in the NW capability information which handover attributes requested by the UE are supported to trigger different handover types (i.e., long or short).

[0138] For each of short and long handovers, the UE and NW can agree on which attributes the UE is allowed to indicate when requesting a handover. Advantageously, this can allow different NW implementations to adapt the handover logic based on input attributes from the UE, and / or the UE can adapt the handover protocol based on what a particular NW implementation allows.

[0139] In addition to the indication that short handover is supported, the UE capability indication may indicate whether the short handover to be performed by the UE will be a periodic or one-time handover procedure. For example, periodic handover may be used for idle / inactive discontinuous reception (DRX) paging decoding or periodic TAU / RNAU of a SIM, where short-circuit handover is expected to occur multiple times periodically. Additionally, a single (one-time) handover may be used for a user-triggered manual public land mobile network (PLMN) search and / or an out-of-service (OOS) recovery search of a SIM, where only a single short handover is expected to occur. In these embodiments, the NW may respond with network capability information indicating whether the NW supports the distinction between periodic and one-shot short handovers. If such a distinction is supported, the NW may also indicate which handover attributes are allowed based on the received UE capability information.

[0140] In the event that a SIM of a dual or multi-SIM UE is removed or inserted (i.e., the UE switches from multi-SIM mode to single SIM mode or vice versa), the UE may send an updated UE capability indication to the NW indicating that it is capable of or no longer capable of using the MUSIM. This may indicate to the NW whether the UE's periodic / single switching capability is disabled / enabled.

[0141] Paging reason uncertainty

[0142] In some embodiments, a UE receiving a page may wish to determine whether the page is for an incoming voice call (e.g., VoLTE / VoNR). In some embodiments, the page from the network may include a paging cause indicator that informs the UE that the current incoming page is for a voice call. However, if the paging cause indicator is not present, in previous implementations, the UE may not be able to determine whether the absence is because a) the base station does not support providing a paging cause indicator, or b) the base station supports providing a paging cause indicator, but the paging message is not for a voice call.

[0143] To address these and other issues, in some embodiments, during the initial registration or attach process, the NW may specify whether it supports sending a paging cause indicator. This support indication may be sent as part of a Registration Accept or Radio Network Area (RNA) Update message (e.g., in a 5G NR network) or as part of an Attach Accept or Tracking Area Update (TAU) message (e.g., in an LTE network). For example, the NW may specify whether it supports sending a paging cause indicator in Figure 9 and 10 The registration accept message 910 or the attach accept message 1010 shown sends a paging cause indicator.

[0144] On the UE side, when the NW does not provide support for the paging cause indicator, the UE can determine that the UE will not apply any method of distinguishing between receiving voice and non-voice paging messages because the UE will not receive advance notification of whether the page is for a voice call. When the NW indicates during initial access that it does support providing the paging cause indicator, the lack of a paging cause indicator in a subsequent paging message will inform the UE that the incoming page is not for a VoLTE or VoNR voice call. Advantageously, the combination of the paging cause support indicator within the connection accept message and the paging cause indicator in the paging message enables the UE to distinguish between the following three cases: 1) the NW sends a page for a voice call, 2) the NW sends a page that is not for a voice call, and 3) the NW sends a page that it does not know is for a voice call.

[0145] Figure 11 - Flowchart for exchanging capability information with the network

[0146] Figure 11 is a flow chart illustrating a method for a multi-SIM wireless device (e.g., wireless user equipment (UE) device 106) to exchange capabilities and network capability indications with a network according to some embodiments. Figure 11 Various aspects of the method can be implemented by a wireless device, for example, in conjunction with a cellular base station, such as the UE 106 and BS 102 shown and described in various figures herein, or more generally, in conjunction with any computer system or device shown in the above figures and other devices. The UE may include a radio component having one or more antennas for performing wireless communications, and a processor operatively coupled to the radio component. The UE may also include first and second subscriber identity modules (SIMs), wherein each of the first and second SIMs is coupled to the radio component and is configured to be used with the radio component for wireless communications.

[0147] Note that although described in relation to the use of communication technologies and / or features associated with 5G NR and / or 3GPP specification documents, Figure 11 However, this description is not intended to limit the present disclosure, and as needed, Figure 11 The aspects of the method can be used in any suitable wireless communication system. In various embodiments, some of the method elements shown may be performed simultaneously in an order different from the order shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown in the figure, Figure 11The method can be operated as follows.

[0148] At 1102, the UE sends a connection request message to the base station via the first network using the first SIM. The connection request message includes one or more UE capability indications. The one or more UE capability indications may include information about Figure 7-10 Any capability indication described, i.e., the UE capability indication may include an indication of RF band conflict avoidance information for a second SIM of the UE, support for requesting a short / long switching procedure, support for one or more switching attributes acting as a proxy for a short / long switching procedure request, and / or support for requesting periodic and one-time short switching procedures.

[0149] At 1104, the UE receives a message from the base station. The message includes one or more network capability indications corresponding to respective UE capability indications in the one or more UE capability indications. The message received from the base station may be a connection accept message (e.g., an attach accept message (in LTE) or a registration accept message (in 5G)), or it may be an initial registration message received before establishing a connection between the UE and the network. The one or more network capability indications may include information about Figure 7-10 Any network capability indication described, i.e., the network capability indication may include NW support for providing RF band conflict avoidance assistance, support for providing paging cause indication, support for selective provision of short / long handover procedures, support for one or more handover attributes acting as a proxy for short / long handover procedure requests, and / or support for receiving indications requesting periodic and one-time short handover procedures.

[0150] At 1106, the UE performs communications with the base station based on the one or more network capability indications. In various embodiments, this may include requesting a long or short handover procedure, potentially using network-supported handover attributes to request a long or short handover procedure, and / or requesting a periodic or single short handover procedure.

[0151] Performing communications in accordance with the one or more network capability indications may additionally or alternatively include receiving a paging message including a paging cause indicator indicating whether the paging message is for a packet-handed voice call.

[0152] Performing communications in accordance with one or more network capability indications may additionally or alternatively include providing an indication of a potential or actual RF band conflict caused by simultaneous reception on the first and second SIMs of the UE. The NW may use the band conflict indication to avoid or resolve the band conflict (i.e., by retuning the first SIM to a non-conflicting frequency, instructing the UE to autonomously resolve the band conflict, and other possibilities as described above).

[0153] In some embodiments, the one or more UE capability indications include an indication that the UE supports requesting a short or long network handover, the one or more network capability indications include an indication that the first network supports selectively providing a short or long network handover, and performing communications with the base station in accordance with the one or more network capability indications includes performing a short or long network handover to the second network.

[0154] In some embodiments, the one or more UE capability indications further include an indication of whether the UE supports one or both of periodic and one-time short network switching, and the one or more network capability indications include an indication that the first network allows one or both of periodic and one-time short network switching.

[0155] In some embodiments, the one or more UE capability indications further include a preference for requesting a short or long network handover based on one or more handover attributes, wherein the one or more handover attributes include one or more of a duration of the network handover, a cause of the network handover, and a radio resource control (RRC) state preference for the network handover. In these embodiments, the one or more network capability indications may further include an indication of the one or more handover attributes that the first network allows to request a short or long network handover.

[0156] In some embodiments, the one or more network capability indications also include an indication that the base station supports providing a paging cause indicator together with a paging message, and performing communication with the base station based on the one or more network capability indications includes receiving, by the UE, from the base station a paging message including a paging cause indicator, the paging cause indicator indicating whether the paging is for a packet-switched voice call.

[0157] In some embodiments, the base station is a gNB, the first network is a fifth generation new radio (5G NR) network, the connection request message is a registration request message, and the connection accept message is a registration accept message. Alternatively, in some embodiments, the base station is an eNB, the first network is a long term evolution (LTE) network, the connection request message is an attach request message, and the connection accept message is an attach accept message.

[0158] In some embodiments, the one or more UE capability indications include frequency band conflict information associated with the first and second SIMs. The first network may use the frequency band conflict information to avoid frequency band conflicts between communications using the first and second SIMs. In other words, the base station may implement at least one frequency band conflict avoidance procedure based at least in part on the frequency band conflict information to avoid frequency band conflicts between communications using the first and second SIMs.

[0159] In some embodiments, at least one frequency band conflict avoidance process includes one or more of the following: switching the first SIM to a frequency band that does not conflict with communications on the second SIM; removing or deactivating a primary cell group (MCG) secondary cell (SCell), a secondary cell group (SCG) primary secondary cell (PSCell), or an SCG secondary SCell used for communicating with the UE; allocating physical resource block (PRB) resources for the UE on a component carrier whose intermodulation distortion and harmonics avoid the frequency band conflict; configuring a supplementary uplink instead of a normal uplink for the communication with the UE; or prioritizing a frequency band that avoids frequency band conflicts for communication with the UE.

[0160] In some embodiments, the UE is further configured to determine that the first SIM has switched to using a non-conflicting frequency band for communication. In response to determining that the first SIM has switched to using a non-conflicting frequency band for communication, the UE may be configured to transmit an updated capability indication to the base station, the capability indication indicating that the first SIM has switched to using a non-conflicting frequency band for communication. In response to receiving the updated capability indication, the base station may cease performing at least one frequency band conflict avoidance procedure.

[0161] In some embodiments, the frequency band conflict information includes specifications of a serving cell frequency used by the second SIM in idle mode.

[0162] In some embodiments, the band conflict information specifies potential band conflicts between the first and second SIMs when each of the first and second SIMs is in idle mode or connected mode. For example, the band conflict information may specify potential band conflicts for different combinations of RRC states of the first and second SIMs, respectively (e.g., SIM1=idle / SIM2=connected, SIM1=connected / SIM2=connected, SIM1=idle / SIM2=idle, SIM1=inactive / SIM2=connected, etc.).

[0163] In some embodiments, the band conflict information is mapped to a predefined band conflict table that can be used by the first network to allocate communication frequencies to the UE to avoid band conflicts between communications using the first and second SIMs. In other words, the base station can allocate communication frequencies to the UE based on the mapping to the predefined band conflict table to avoid band conflicts between communications using the first and second SIMs.

[0164] In some embodiments, the one or more network capability indications include an indication that the first network does not support frequency band conflict resolution, and performing communications with the base station in accordance with the one or more network capability indications includes autonomously avoiding potential frequency band conflicts by reselecting a frequency for receiving communications on the first SIM or the second SIM.

[0165] In some embodiments, the UE determines whether to reselect a frequency for receiving communications via the first or second SIM based at least in part on a comparison of one or more factors, including: 1) the radio access technology (RAT) used to communicate with the first and second SIMs, 2) the capabilities provided by the serving cells of the first and second SIMs, 3) the signal strength of communications via the first and second SIMs, 4) the data preferences of the first and second SIMs, or 5) the probability of finding non-conflicting frequencies for the first and second SIMs. Additionally or additionally, frequency reselection can be performed on the first or second SIM based on the mobility of the UE. In some embodiments, a SIM communicating using a legacy RAT is prioritized for reselecting its frequency for receiving communications over a SIM communicating using a newer RAT. In other embodiments, the determination of whether to reselect a frequency for receiving communications on the first or second SIM is random.

[0166] The following paragraphs describe additional embodiments.

[0167] In some embodiments, a user equipment (UE) device includes a radio comprising first and second receive (Rx) antennas and a transmit (Tx) antenna for performing wireless communications. The UE also includes a processor operatively coupled to the radio, a first subscriber identity module (SIM) configured to be used with the first Rx antenna and the Tx antenna for wireless communications, and a second SIM configured to be used with the second Rx antenna and the Tx antenna for wireless communications.

[0168] In some embodiments, the UE is configured to establish a first connection with a first network using a first SIM, establish a second connection with a second network using a second SIM, determine that a frequency band conflict has occurred between the first connection and the second connection, and provide a frequency band conflict indication to the first network.

[0169] In some embodiments, the frequency band conflict indication is provided within a UE assistance information message, a measurement report, or an in-device coexistence message.

[0170] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 stated to users.

[0171] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0172] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein the program instructions, if executed by a computer system, cause the computer system to perform a method, such as any one of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein or any combination of such subsets.

[0173] In some embodiments, the computer system may be configured to include a processor (or a group of processors) and a memory medium, wherein the memory medium stores program instructions, wherein the processor is configured to read and execute the program instructions from the memory medium, wherein the executable program instructions are to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any method embodiments described herein, or any combination of such subsets). The computer system can be implemented in any of various forms. For example, the computer system can be a personal computer (in any of its various implementations), a workstation, a computer on a card, a dedicated computer in a box, a server computer, a client computer, a handheld device, a user equipment (UE), a tablet computer, a wearable computer, etc.

[0174] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A user equipment (UE) device, the UE device comprising: a radio component comprising one or more antennas for performing wireless communications; a processor operatively coupled to the radio; and first and second subscriber identity modules (SIMs), wherein each of the first SIM and the second SIM is coupled to the radio and configured for use with the radio for the wireless communication; The UE device is configured to, using the first SIM card: Sending a registration request message to the first network via the base station, wherein the registration request message includes one or more UE capability indications; receiving a registration accept message from the base station, wherein the registration accept message includes one or more network capability indications corresponding to respective UE capability indications among the one or more UE capability indications, wherein the one or more network capability indications further include an indication that the network supports providing a paging cause indicator together with a paging message; Receiving, by the UE device, a paging message from the base station, the paging message including a paging cause indicator indicating whether the paging message is for a packet switched voice call; Receiving, by the UE device, a second paging message from the base station, wherein the second paging message does not include the paging cause indicator; as well as Based on the absence of the paging cause indicator in the second paging message and based on the registration accept message including the one or more network capability indications, it is determined that the second paging message is not for the packet switched voice call, the one or more network capability indications including an indication that the network supports providing a paging cause indicator together with a paging message.

2. The UE device according to claim 1, wherein the one or more UE capability indications include an indication that the UE device supports requesting a short or long network handover, and wherein the one or more network capability indications include an indication that the first network supports selectively providing short or long network handovers, and The UE device is further configured to perform a short or long network handover to a second network.

3. The UE device according to claim 2, wherein the one or more UE capability indications further include an indication of whether the UE device supports one or both of periodic and one-time short network switching, and The one or more network capability indications include an indication that the first network allows one or both of periodic and one-time short network switching.

4. The UE device according to claim 2, The one or more UE capability indications further include a preference for requesting a short or long network handover based on one or more handover attributes, wherein the one or more handover attributes include one or more of the following: Duration of network switching; The reason for the network switch; and The radio resource control (RRC) state preference for the network handover.

5. The UE device according to claim 4, The one or more network capability indications further include an indication of one or more of the handover attributes that the first network allows to request a short or long network handover.

6. The UE device according to claim 1, The combination of the paging cause support indicator in the registration accept message and the paging cause indicator in the paging message enables the UE device to distinguish between the following situations: 1) the network sends a paging for a voice call, 2) the network sends a paging that is not for a voice call, and 3) the network sends a paging that is not known to be for a voice call.

7. The UE device according to claim 1, wherein: The base station is a gNB, and the first network is a fifth generation new radio 5G NR network.

8. The UE device according to claim 1, wherein: The base station is an eNB, and the first network is a Long Term Evolution (LTE) network.

9. The UE device according to claim 1, wherein the one or more UE capability indications include frequency band conflict information associated with the first SIM and the second SIM, Wherein the band conflict information is usable by the first network to avoid band conflicts between communications using the first SIM and the second SIM.

10. The UE device according to claim 9, wherein the UE device is further configured to: determining that the first SIM has switched to communicating using a non-conflicting frequency band; and In response to determining that the first SIM has switched to communicating using the non-conflicting frequency band, an updated capability indication is sent to the base station, the updated capability indication indicating that the first SIM has switched to communicating using the non-conflicting frequency band.

11. The UE device according to claim 9, The frequency band conflict information includes specifications of a serving cell frequency used by the second SIM in idle mode.

12. The UE device according to claim 9, When each of the first SIM and the second SIM is in an idle mode or a connected mode, the frequency band conflict information indicates a potential frequency band conflict between the first SIM and the second SIM.

13. The UE device according to claim 9, Wherein the band conflict information is mapped to a predefined band conflict table, the predefined band conflict table being usable by the first network to allocate communication frequencies to the UE to avoid band conflicts between communications using the first SIM and the second SIM.

14. The UE device according to claim 9, wherein the one or more network capability indications include an indication that the first network does not support frequency band conflict resolution, and Wherein performing communications with the base station in accordance with the one or more network capability indications includes autonomously avoiding potential frequency band conflicts by reselecting a frequency for receiving communications on the first SIM or the second SIM.

15. The UE device according to claim 14, Wherein determining whether to reselect the frequency for receiving communications on the first SIM or the second SIM is based at least in part on a comparison of one or more of: a radio access technology (RAT) for communicating with the first SIM and the second SIM; capabilities provided by serving cells of the first SIM and the second SIM; signal strength of communications on the first SIM and the second SIM; data preferences of the first SIM and the second SIM; or A probability of finding non-conflicting frequencies for the first SIM and the second SIM.

16. The UE device according to claim 15, Wherein a SIM communicating using a legacy RAT may be prioritized over a SIM communicating using a newer RAT in reselecting the frequency on which it receives communications.

17. The UE device according to claim 14, Wherein whether to reselect the frequency for receiving communications on the first SIM or the second SIM is determined randomly.

18. A method for operating a UE device according to any one of claims 1 to 17.

19. A non-transitory computer-accessible storage medium comprising program instructions executable by a processor to operate a UE device according to any one of claims 1 to 17.

20. A base station, comprising: a radio component comprising one or more antennas for performing wireless communications; a processor operatively coupled to the radio component, wherein the base station is configured to: receiving a registration request message from a user equipment (UE) device using a first subscriber identity module (SIM) on a first network, wherein the registration request message includes one or more UE capability indications; Sending a registration accept message to the UE device, wherein the registration accept message includes one or more network capability indications corresponding to corresponding UE capability indications among the one or more UE capability indications, wherein the one or more network capability indications further include an indication that the network supports providing a paging cause indicator together with a paging message; Sending a paging message to the UE device, where the paging message includes a paging cause indicator indicating whether the paging message is for a packet switched voice call; as well as and sending a second paging message to the UE device, wherein the second paging message does not include the paging cause indicator, wherein sending the registration accept message including the one or more network capability indications and sending the second paging message without the paging cause indicator indicates that the second paging message is not for the packet switched voice call, the one or more network capability indications including an indication that the network supports providing the paging cause indicator together with the paging message.

21. The base station according to claim 20, wherein the one or more UE capability indications include an indication that the UE supports requesting a short or long network handover, and The one or more network capability indications include an indication that the first network supports selectively providing short or long network handover.

22. The base station according to claim 21, wherein the one or more UE capability indications further include an indication of whether the UE device supports one or both of periodic and one-time short network switching, and The one or more network capability indications include an indication that the first network allows one or both of periodic and one-time short network switching.

23. The base station according to claim 21, The one or more UE capability indications further include a preference for requesting a short or long network handover based on one or more handover attributes, wherein the one or more handover attributes include one or more of the following: Duration of network switching; The reason for the network switch; and The radio resource control (RRC) state preference for the network handover.

24. The base station according to claim 23, The one or more network capability indications further include an indication of one or more of the handover attributes that the first network allows to request a short or long network handover.

25. The base station according to claim 20, The combination of the paging cause support indicator in the registration accept message and the paging cause indicator in the paging message enables the UE device to distinguish between the following situations: 1) the network sends a paging for a voice call, 2) the network sends a paging that is not for a voice call, and 3) the network sends a paging that is not known to be for a voice call.

26. The base station according to claim 20, wherein: The base station is a gNB, and the first network is a fifth generation new radio 5G NR network.

27. The base station according to claim 20, wherein: The base station is an eNB, and the first network is a Long Term Evolution (LTE) network.

28. The base station according to claim 20, The one or more UE capability indications include frequency band conflict information related to the first SIM and the second SIM of the UE device, and the base station is further configured to: At least one band conflict avoidance procedure is implemented based at least in part on the band conflict information to avoid band conflicts between communications using the first SIM and the second SIM.

29. The base station according to claim 28, wherein the at least one frequency band conflict avoidance procedure comprises one or more of the following: switching the first SIM to a frequency band that does not conflict with communications on the second SIM; Remove or deactivate the primary cell group (MCG), secondary cell group (SCell), primary and secondary cell group (SCG), PSCell, or SCG SCell used for communicating with the UE device; Allocating physical resource blocks (PRBs) for the UE device on a component carrier, where intermodulation distortion and harmonics of the component carrier avoid frequency band conflicts; configuring a supplemental uplink instead of a normal uplink for the communication with the UE device; or Prioritizing frequency bands for the communication with the UE device that avoid the frequency band conflict.

30. The base station according to claim 28, wherein the base station is further configured to: receiving an updated capability indication from the UE device, the updated capability indication indicating that the first SIM has switched to communicating using a non-conflicting frequency band; and Based on responsive to receiving the updated capability indication, discontinuing implementation of the at least one frequency band conflict avoidance procedure.

31. The base station according to claim 28, The frequency band conflict information includes specifications of a serving cell frequency used by the second SIM in idle mode.

32. The base station according to claim 28, When each of the first SIM and the second SIM is in an idle mode or a connected mode, the frequency band conflict information indicates a potential frequency band conflict between the first SIM and the second SIM.

33. The base station according to claim 28, The frequency band conflict information is mapped to a predefined frequency band conflict table, and the base station is further configured to: A communication frequency is allocated to the UE device based on the mapping to the predefined frequency band conflict table to avoid frequency band conflicts between communications of the UE device using the first SIM and the second SIM.

34. A method for operating a base station according to any one of claims 20 to 33.

35. A non-transitory computer-accessible storage medium comprising program instructions executable by a processor to operate a base station according to any one of claims 20 to 33.

36. A computer program product comprising program instructions, the program instructions being executable by a processor to operate a UE device according to any one of claims 1 to 17 or a base station according to any one of claims 20 to 33.

37. An apparatus comprising a processor, wherein the processor is configured to cause a base station to: receiving a registration request message from a user equipment (UE) device using a first subscriber identity module (SIM) via a first network, wherein the registration request message includes one or more UE capability indications; Sending a registration accept message to the UE device, wherein the registration accept message includes one or more network capability indications corresponding to corresponding UE capability indications among the one or more UE capability indications, wherein the one or more network capability indications further include an indication that the network supports providing a paging cause indicator together with a paging message; Sending a paging message to the UE device, wherein the paging message includes a paging cause indicator indicating whether the paging message is for a packet switched voice call; as well as and sending a second paging message to the UE device, wherein the second paging message does not include the paging cause indicator, wherein sending the registration accept message including the one or more network capability indications and sending the second paging message without the paging cause indicator indicates that the second paging message is not for the packet switched voice call, the one or more network capability indications including an indication that the network supports providing the paging cause indicator together with the paging message.

38. The device according to claim 37, The combination of the paging cause support indicator in the registration accept message and the paging cause indicator in the paging message enables the UE device to distinguish between the following situations: 1) the network sends a paging for a voice call, 2) the network sends a paging that is not for a voice call, and 3) the network sends a paging that is not known to be for a voice call.

Images