Single search in multi-SIM ue

Abstract

Apparatuses, systems, and methods for a single search in multiple SIM UEs, e.g., in 5G NR systems and beyond. A UE may include a plurality of SIM instances and a first SIM instance may detect a service interruption while camped on a first cell of a network. The first SIM instance may notify a second SIM instance of the plurality of SIM instances that the first SIM detected the service interruption and retrieve, upon expiry of a public land mobile network (PLMN) search timer (PST) initiated by the first SIM instance, first last registered PLMN (RPLMN) information from a database hosted by the UE upon failure of an immediate recovery of service. The first SIM instance may initiate a PLMN search based, at least in part, on the first RPLMN information retrieved from the database and share, upon receiving a service interruption indication from at least the second SIM instance, search information from the PLMN search with at least the second SIM instance.

Description

SINGLE SEARCH IN MULTLSIM UEFIELD

[0001] The invention relates to wireless communications, and more particularly to apparatuses, systems, and methods for a single search in multiple SIM UEs, e.g., in cellular systems, such as 5G New Radio (NR) systems and beyond.DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones, wearable devices or accessory devices), and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS), and are capable of operating sophisticated applications that utilize these functionalities.

[0003] Long Term Evolution (LTE) is currently the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. Thus, in 2015 study of a new radio access technology began and, in 2017, a first release of Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultrareliable, and massive machine type communications with lower latency and / or lower battery consumption. Further, NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.SUMMARY

[0005] Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for a single search in multiple SIM UEs, e.g., in 5G NR systems, LTE systems, WiFi systems and beyond.

[0006] For example, in some embodiments, a UE may include a plurality of Subscriber Identity Module (SIM) instances and a first SIM instance of the plurality of SIM instances may be configured to detect a service interruption while camped on a first cell of a network. A connection to the first cell may support communication via at least the first SIM instance. The service interruption may be an out-of-service (OOS) condition and / or a low / limited service condition. Further, the first SIM instance may be configured to notify at least a second SIM instance of the plurality of SIM instances that the first SIM detected the service interruption and retrieve, upon expiry of a public land mobile network (PLMN) search timer (PST) initiated by the first SIM instance, first last registered PLMN (RPLMN) information from a database hosted by the UE upon failure of an immediate recovery of service. The database may include, for each of the plurality of SIM instances of the UE, one or more of a state variable, an RPLMN equivalent list, an equivalent HPLMN (eHPLMN) list, and / or or a preferred PLMN list. The state variable may be maintained with critical selection for detecting service interruption start and end. The first SIM instance may be configured to initiate a PLMN search based, at least in part, on the first RPLMN information retrieved from the database and share, upon receiving a service interruption indication from at least the second SIM instance, search information from the PLMN search with at least the second SIM instance. The search information may include one or more of a search process type, a search counter, a found PLMN list, and / or a search type array. The search type array may include one or more of an indication of data validity, a task PLMN list, a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information.

[0007] The techniques described herein may be implemented in and / or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), a UTM server, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

[0008] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow 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, Figures, and Claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0010] Figure 1A illustrates an example wireless communication system according to some embodiments.

[0011] Figure IB illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.

[0012] Figure 2 illustrates an example block diagram of a base station, according to some embodiments.

[0013] Figure 3 illustrates an example block diagram of a server according to some embodiments.

[0014] Figure 4 illustrates an example block diagram of a UE according to some embodiments.

[0015] Figure 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.

[0016] Figure 6A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments.

[0017] Figure 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments.

[0018] Figure 7 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.

[0019] Figures 8A, 8B, 8C, 8D, 8E, 8F, 8G, 8H, and 9 illustrate examples of signaling for a shared cell search in a multi-SIM UE, according to some embodiments.

[0020] Figure 10 illustrates a block diagram of an example of a method for a shared cell search algorithm in a multi-SIM UE, according to some embodiments.

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

[0022] Various acronyms are used throughout the present disclosure. Definitions of the most prominently used acronyms that may appear throughout the present disclosure are provided below:• 3GPP: Third Generation Partnership Project• UE: User Equipment• RE: Radio Frequency• DL: Downlink• UL: Uplink• LTE: Long Term Evolution• NR: New Radio• 5GS: 5G System• 5GMM: 5GS Mobility Management• 5GC / 5GCN: 5G Core Network• IE: Information Element• CE: Control Element• MAC: Medium Access Control• SSB: Synchronization Signal Block• CSI: Channel State Information• PDCCH: Physical Downlink Control Channel• PDSCH: Physical Downlink Shared Channel• RRC: Radio Resource Control• RRM: Radio Resource Management• CORESET : Control Resource Set• TCI: Transmission Configuration Information• DCI: Downlink Control InformationTerms

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

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

[0025] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0026] Programmable Hardware Element - includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as “reconfigurable logic”.

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

[0028] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0029] Base Station - The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

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

[0031] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. In contrast, WLAN channels may be 22MHz wide whileBluetooth channels may be IMhz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0032] Band - The term “band” has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0033] Wi-Fi - The term “Wi-Fi” (or WiFi) has the full breadth of its ordinary meaning, and at least includes a wireless communication network or RAT that is serviced by wireless LAN (WLAN) access points and which provides connectivity through these access points to the Internet. Most modem Wi-Fi networks (or WLAN networks) are based on IEEE 802.11 standards and are marketed under the name “Wi-Fi”. A Wi-Fi (WLAN) network is different from a cellular network.

[0034] 3GPP Access - refers to accesses (e.g., radio access technologies) that are specified by 3 GPP standards. These accesses include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. In general, 3GPP access refers to various types of cellular access technologies.

[0035] Non-3GPP Access - refers any accesses (e.g., radio access technologies) that are not specified by 3 GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP accesses may be split into two categories, “trusted” and “untrusted”: Trusted non-3GPP accesses can interact directly with an evolved packet core (EPC) and / or a 5G core (5GC) whereas untrusted non-3GPP accesses interwork with the EPC / 5GC via a network entity, such as an Evolved Packet Data Gateway and / or a 5G NR gateway. In general, non-3GPP access refers to various types on non-cellular access technologies.

[0036] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term “automatically” is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifyinginformation (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system must update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed), though the user may choose to revoke or revise the automatically filled form for accuracy or certain optimization. The present specification provides various examples of operations being automatically performed in response to actions the user has taken.

[0037] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as required by the particular application.

[0038] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0039] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may 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 recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task evenwhen the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.

[0040] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.Figures 1A and IB: Communication Systems

[0041] Figure 1 A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of Figure 1A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0042] As shown, the example wireless communication system includes a base station 102 A which communicates over a transmission medium with one or more wireless devices, such as user devices 106A, 106B, etc., through 106N, as well as accessory devices, such as user devices 107A, 107B. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices 106 and 107 are referred to as UEs or UE devices.

[0043] The base station (BS) 102 A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106 A through 106N as well as UEs 107 A and 107B.

[0044] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102 A and the UEs 106 / 107 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as, LTE, LTE- Advanced (LTE- A), 5G new radio (5G NR), etc. Note that if the base station 102A is implemented in the context of LTE, it may alternately be referred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0045] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and / or between the user devices and the network 100. In particular, the cellular base station 102A mayprovide UEs 106 / 107 with various telecommunication capabilities, such as voice, SMS and / or data services.

[0046] Base station 102 A and other similar base stations (such as base stations 102B. . . 102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0047] Thus, while base station 102A may act as a “serving cell” for UEs 106 / 107 as illustrated in Figure 1, each UE 106 / 107 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and / or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in Figure 1 might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.

[0048] In some embodiments, base station 102 A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0049] Note that a UE 106 / 107 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 / 107 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., LTE, LTE-A, 5G NR, etc.). The UE 106 / 107 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC- M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0050] Note that accessory devices 107A / B may include cellular communication capability and hence are able to directly communicate with cellular base station 102A via a cellular RAT. However, since the accessory devices 107A / B are possibly one or more of communication, output power, and / or battery limited, the accessory devices 107A / B may in some instances selectively utilize the UEs 106A / B as a proxy for communication purposes with the base station 102Aand hence to the network 100. In other words, the accessory devices 107A / B may selectively use the cellular communication capabilities of its companion device (e.g., UEs 106A / B) to conduct cellular communications. The limitation on communication abilities of the accessory devices 107A / B may be permanent, e.g., due to limitations in output power or the RATs supported, or temporary, e.g., due to conditions such as current battery status, inability to access a network, or poor reception.

[0051] Figure IB illustrates user equipment 106 (e.g., one of the devices 106A through 106N) and accessory device (or user equipment) 107 (e.g., one of the devices 107A or 107B) in communication with a base station 102 and an access point 112 as well as one another, according to some embodiments. The UEs 106 / 107 may be devices with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a wearable device, a hand-held device, a computer or a tablet, or virtually any type of wireless device. The accessory device 107 may be a wearable device such as a smart watch. The accessory device 107 may comprise cellular communication capability and be capable of directly communicating with the base station 102 as shown. Note that when the accessory device 107 is configured to directly communicate with the base station, the accessory device may be said to be in “autonomous mode.” In addition, the accessory device 107 may also be capable of communicating with another device (e.g., UE 106), referred to as a proxy device, intermediate device, or companion device, using a short-range communications protocol; for example, the accessory device 107 may according to some embodiments be “paired” with the UE 106, which may include establishing a communication channel and / or a trusted communication relationship with the UE 106. Under some circumstances, the accessory device 107 may use the cellular functionality of this proxy device for communicating cellular voice and / or data with the base station 102. In other words, the accessory device 107 may provide voice and / or data packets intended for the base station 102 over the short-range link to the UE 106, and the UE 106 may use its cellular functionality to transmit (or relay) this voice and / or data to the base station on behalf of the accessory device107. Similarly, the voice and / or data packets transmitted by the base station and intended for the accessory device 107 may be received by the cellular functionality of the UE 106 and then may be relayed over the short-range link to the accessory device. As noted above, the UE 106 may be a mobile phone, a tablet, or any other type of hand-held device, a media player, a computer, a laptop or virtually any type of wireless device. Note that when the accessory device 107 is configured to indirectly communicate with the base station 102 using the cellular functionality of an intermediate or proxy device, the accessory device may be said to be in “relay mode.”

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

[0053] The UE 106 / 107 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, LTE / LTE-Advanced or 5G NR using a single shared radio and / or LTE, LTE- Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 / 107 may share one or more parts of a receive and / or transmit chain between multiple wireless communication technologies, such as those discussed above.

[0054] In some embodiments, the UE 106 / 107 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 / 107 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 / 107 might include a shared radiofor communicating using either of LTE or 5G NR (or LTE), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.Figure 2: Block Diagram of a Base Station

[0055] Figure 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of Figure 3 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.

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

[0057] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and / or other services to a plurality of devices, such as UE devices 106. In some cases, the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).

[0058] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0059] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, Wi-Fi, etc.

[0060] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, etc.).

[0061] As described further subsequently herein, the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 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. Alternatively (or in addition) the processor 204 of the BS 102, in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.

[0062] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.

[0063] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.Figure 3: Block Diagram of a Server

[0064] Figure 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of Figure 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.

[0065] The server 104 may be configured to provide a plurality of devices, such as base station 102, UE devices 106, and / or UTM 108, access to network functions, e.g., as further described herein.

[0066] In some embodiments, the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server 104 may be connected to a legacy evolved packet core (EPC) network and / or to a NR core (NRC) network.

[0067] As described further subsequently herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 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. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 may be configured to implement or support implementation of part or all of the features described herein.

[0068] In addition, as described herein, processor(s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.Figure 4: Block Diagram of a UE

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

[0070] For example, the communication device 106 / 107 may include various types of memory (e.g., including NAND flash 410), an input / output interface such as connector I / F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 106 / 107, and wireless communication circuitry 430. The wireless communication circuitry 430 may include a cellular modem 434 such as for 5G NR, LTE, LTE-A, etc., and short to medium range wireless communication logic 436 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 106 / 107 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0071] The wireless communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a, 435b, and 435c (e.g., 435a-c) as shown. The wireless communication circuitry 430 may include local area network (LAN) logic 432, the cellular modem 434, and / or short-range communication logic 436. The LAN logic 432 may be for enabling the UE device 106 / 107 to perform LAN communications, such as Wi-Fi communications on an 802.11 network, and / or other WLAN communications. The short-range communication logic 436 may be for enabling the UE device 106 / 107 to perform communications according to a short-range RAT, such as Bluetooth or UWB communications. In some scenarios, the cellular modem 434 may be a lower power cellularmodem capable of performing cellular communication according to one or more cellular communication technologies.

[0072] In some embodiments, as further described below, cellular modem 434 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5GNR). In addition, in some embodiments, cellular modem 434 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5GNR, and may be in communication with a dedicated receive chain and the shared transmit chain.

[0073] The communication device 106 / 107 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.

[0074] The communication device 106 / 107 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUICCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE 106 / 107 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106 / 107, or each SIM 410 may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and / or the SIMs 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUICC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of theSIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 / 107 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality), as desired. For example, the UE 106 / 107 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

[0075] As noted above, in some embodiments, the UE 106 / 107 may include two or more SIMs. The inclusion of two or more SIMs in the UE 106 / 107 may allow the UE 106 / 107 to support two different telephone numbers and may allow the UE 106 / 107 to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM 410 support a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the UE 106 / 107 comprises two SIMs, the UE 106 / 107 may support Dual SIM Dual Active (DSD A) functionality. The DSDA functionality may allow the UE 106 / 107 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE 106 / 107 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 / 107 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 / 107 to be on standby waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and / or RATs.

[0076] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 106 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and / or to other circuitsor devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[0077] As noted above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuitry. The communication device 106 may be configured to perform methods for a single search in multiple SIM UEs, e.g., in 5GNR systems and beyond, as further described herein.

[0078] As described herein, the communication device 106 / 107may include hardware and software components for implementing the above features for a communication device 106 / 107to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 106 / 107may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 106, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.

[0079] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.

[0080] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wirelesscommunication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.Figure 5: Block Diagram of Cellular Communication Circuitry

[0081] Figure 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of Figure 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 530, which may be cellular modem circuitry 434, may be included in a communication device, such as communication device 106 / 107described above. As noted above, communication device 106 / 107may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, a wearable device, and / or a combination of devices, among other devices.

[0082] The cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 535a-c (which may be antennas 435a- c of Figure 4). In some embodiments, cellular communication circuitry 530 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in Figure 5, cellular communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE- A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

[0083] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 535a.

[0084] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 535b.

[0085] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 535c. Thus, when cellular communication circuitry 530 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0086] In some embodiments, the cellular communication circuitry 530 may be configured to perform methods for a single search in multiple SIM UEs, e.g., in 5G NR systems and beyond, as further described herein.

[0087] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NS A NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 535a-c may be configured to implement part or all of the features described herein.

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

[0089] As described herein, the modem 520 may include hardware and software components for implementing the above features for a single search in multiple SIM UEs, e.g., in 5G NR systems and beyond, as well as the various other techniques described herein. The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer- readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 535a-c may be configured to implement part or all of the features described herein.

[0090] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.Figures 6 A, 6B and 7: 5G Core Network Architecture - Interworking with Wi-Fi

[0091] In some embodiments, the 5G core network (CN) may be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as Wi-Fi connection). Figure 6A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE 106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB 604, which may be a base station 102) and an access point, such as AP 612. The AP 612 may include a connection to the Internet 600 as well as a connection to a non-3GPP inter-working function (N3IWF) 603 network entity. The N3IWF may include a connection to a core access and mobility management function (AMF) 605 of the 5G CN. The AMF 605 may include an instance of a 5G mobility management (5G MM) function associated with the UE 106 / 107. In addition, the RAN (e.g., gNB 604) may also have a connection to the AMF 605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registrationfor UE 106 / 107 access via both gNB 604 and AP 612. As shown, the AMF 605 may be in communication with a location management function (LMF) 609 via a networking interface, such as an NLs interface. The LMF 609 may receive measurements and assistance information from the RAN (e.g., gNB 604) and the UE (e.g., UE 106) via the AMF 605. The LMF 609 may be a server (e.g., server 104) and / or a functional entity executing on a server. Further, based on the measurements and / or assistance information received from the RAN and the UE, the LMF may determine a location of the UE. In addition, the AMF 605 may include one or more functional entities associated with the 5G CN (e.g., network slice selection function (NSSF) 620, short message service function (SMSF) 622, application function (AF) 624, unified data management (UDM) 626, policy control function (PCF) 628, and / or authentication server function (AUSF) 630). Note that these functional entities may also be supported by a session management function (SMF) 606a and an SMF 606b of the 5G CN. The AMF 605 may be connected to (or in communication with) the SMF 606a. Further, the gNB 604 may in communication with (or connected to) a user plane function (UPF) 608a that may also be communication with the SMF 606a. Similarly, the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and / or the Internet 600 and Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) core network 610.

[0092] Figure 6B illustrates an example of a 5G network architecture that incorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access to the 5G CN, according to some embodiments. As shown, a user equipment device (e.g., such as UE 106) may access the 5G CN through both a radio access network (RAN, e.g., such as gNB 604 or eNB 602, which may be a base station 102) and an access point, such as AP 612. The AP 612 may include a connection to the Internet 600 as well as a connection to the N3IWF 603 network entity. The N3IWF may include a connection to the AMF 605 of the 5G CN. The AMF 605 may include an instance of the 5GMM function associated with the UE 106 / 107. In addition, the RAN (e.g., gNB 604) may also have a connection to the AMF 605. Thus, the 5G CN may support unified authentication over both connections as well as allow simultaneous registration for UE 106 / 107 access via both gNB 604 and AP 612. In addition, the 5G CN may support dual -registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). As shown, the eNB 602 may have connections to a mobility management entity (MME) 642 and a serving gateway (SGW) 644. The MME 642 may have connections to both the SGW644 and the AMF 605. In addition, the SGW 644 may have connections to both the SMF 606a and the UPF 608a. As shown, the AMF 605 may be in communication with an LMF 609 via a networking interface, such as an NLs interface, e.g., as described above, and may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). Note that UDM 626 may also include a home subscriber server (HSS) function and the PCF may also include a policy and charging rules function (PCRF). Note further that these functional entities may also be supported by the SMF606a and the SMF 606b of the 5G CN. The AMF 606 may be connected to (or in communication with) the SMF 606a. Further, the gNB 604 may in communication with (or connected to) the UPF 608a that may also be communication with the SMF 606a. Similarly, the N3IWF 603 may be communicating with a UPF 608b that may also be communicating with the SMF 606b. Both UPFs may be communicating with the data network (e.g., DN 610a and 610b) and / or the Internet 600 and IMS core network 610.

[0093] Note that in various embodiments, one or more of the above-described network entities may be configured to perform methods for a single search in multiple SIM UEs, e.g., in 5GNR systems and beyond, e.g., as further described herein.

[0094] Figure 7 illustrates an example of a baseband processor architecture for a UE (e.g., such as UE 106), according to some embodiments. The baseband processor architecture 700 described in Figure 7 may be implemented on one or more radios (e.g., radios 429 and / or 430 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum (NAS) 710 may include a 5GNAS 720 and a legacy NAS 750. The legacy NAS 750 may include a communication connection with a legacy access stratum (AS) 770. The 5G NAS 720 may include communication connections with both a 5G AS 740 and a non- 3GPP AS 730 and Wi-Fi AS 732. The 5GNAS 720 may include functional entities associated with both access stratums. Thus, the 5G NAS 720 may include multiple 5G MM entities 726 and 728 and 5G session management (SM) entities 722 and 724. The legacy NAS 750 may include functional entities such as short message service (SMS) entity 752, evolved packet system (EPS) session management (ESM) entity 754, session management (SM) entity 756, EPS mobility management (EMM) entity 758, and mobility management (MM) / GPRS mobility management (GMM) entity 760. In addition, the legacy AS 770 may include functional entities such as LTE AS 772, UMTS AS 774, and / or GSM / GPRS AS 776.

[0095] Thus, the baseband processor architecture 700 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that as shown, the 5G MM maymaintain individual connection management and registration management state machines for each connection. Additionally, a device (e.g., UE 106) may register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. Further, it may be possible for the device to be in a connected state in one access and an idle state in another access and vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, de-regi strati on, identification, authentication, as so forth) for both accesses.

[0096] Note that in various embodiments, one or more of the above-described functional entities of the 5GNAS and / or 5G AS may be configured to perform methods for a single search in multiple SIM UEs, e.g., in 5GNR systems and beyond, e.g., as further described herein.Single Search in Multiple SIM UEs

[0097] In current implementations, in multiple SIM (MSIM) mode of operation, in an out-off- service (OOS) scenario recovery, each instance of the MSIM may perform search tasks without taking into consideration respective instance states (e.g., whether other instances of the MSIM are in an OOS scenario recover). This may lead to multiple collisions and arbitrations, which may delay recovery time from OOS and may consume more power and million instructions per second (MIPS). Further, with operators sharing base stations, the possibility of multiple instances moving to OOS at the same time is rather high. Such a condition may lead to multiple arbitrations / conflicts between radio frequency (RF) resources. Therefore, improvements are desired.

[0098] Embodiments described herein provided systems, methods, and mechanisms for a single cell search in multiple SIM UEs, including systems, methods and mechanisms for a multi-SIM (MSIM) UE to, based on last registered public land mobile network (PLMN), home PLMN (HPLMN) and other priority PLMN data of each instance of the MSIM, one instance may choose not to perform a cell search or a PLMN search and may rely on search scheduling by an other instance of the MSIM and corresponding results shared by the other instance of the MSIM in case of an out-of-service (OOS) scenario and / or a limited service scenario. In some instances, a decentralized architecture of information sharing between multiple instances of network access stratum (NAS) mobility management (NAS_MM) may be utilized such that a NAS_MM of one instance may share information (e.g., cell search and / or PLMN search results and / or scheduling) to other instances, e.g., by sending a kicker or trigger signal to activate other NAS MM instances to access a shared database based on a scenario. For example, when multiple modem instances (e.g., multiple MSIM instances) in a UE are OOS and / or in LimitedService (LS), the UE may per perform only a single search on behalf of all MSIM instances and results may be shared between all the instances of the MSIM in OOS / LS for further PLMN Selection. The single search algorithm described herein may avoid conflicts between RF resources, lead to lower power consumption and MIPS, limit possibility of band search in cell selection, and introduce symmetry between MSIM instances.

[0099] In some instances, the database may include a state variable, a last registered PLMN (RPLMN) equivalent list, an equivalent HPLMN (eHPLMN) list, and / or a preferred PLMN list. The state variable may be maintained with critical selection for detecting OOS / LS scenario start / end. The RPLMN equivalent list, eHPLMN list, and / or preferred PLMN list may include entries from each instance of the MSIM and may be used for cross instance sharing.

[0100] In some instances, search information may include a search process type, a search counter, PLMN information such as a found PLMN list, and / or a search type array. The search type array may include an indication of data validity, a task PLMN list, a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information.

[0101] In some instances, a single search algorithm may include one or more stages, such as an immediate recovery stage (e.g., stage-0), a PLMN search timer start and expiry stage (e.g., stage-1), a PLMN search and data sharing stage (e.g., stage-2), and / or an actions based on PLMN search results and priority framework stage (e.g., stage-3). Note that the PLMN search timer may be a timer which provides a trigger for a recovery search from OOS / LS. The PLMN search timer may be started once a network access stratum (NAS) layer finishes its search and moves to an idle state while remaining is an OOS / LS condition.

[0102] In some instances, a parameter that may include a list of secondary equivalent PLMNs (e.g., secondary _equiv_plmns) may be added to a search. For example, in some instances, bands corresponding to frequencies in the list of secondary equivalent PLMNs may be scanned after bands corresponding to frequencies in a list of equivalent PLMNs.

[0103] In some instances, an immediate recover stage (e.g., stage-0) may correspond to a point when multiple instances of an MSIM go out of coverage and start a cell selection. For example, when a first instance of the MSIM experiences an OOS condition, the first instance may notify other instances of the MSIM of a start of an “immediate” cell selection. Then, if and / or when another instance of the MSIM, e.g., a second instance, also experiences an OOS condition, the second instance may notify the first instances of the OOS condition. Then, based on the indication, the first instance may begin sharing cell search results with the second instance. Inaddition, the second instance may only perform a search on found frequencies of corresponding PLMNs, e.g., if PLMN A is found on frequency 1, the search will only be for frequency 1, and wait for cell search results shared by the first instance before choosing and / or determining to perform a band search for cell selection. In some instance, the shared search results may be shared as the list of secondary equivalent PLMNs. Further, based on the shared search results, the second instances may choose to perform cell selection.

[0104] In some instances, a PLMN search timer start and expiry stage (e.g., stage- 1) may corresponds to the point where when a first instance of an MSIM experiences an OOS condition and initiates (starts) a PLMN Search Timer after immediate recovery failure (e.g., failure to find service at stage-0). The first instance may indicate to other instances of the MSIM a start of the PLMN Search Timer (PST) and a corresponding process for with the PST has been started. Then, if and / or when another instance of the MSIM, e.g., a second instance, also experiences an OOS condition, the second instance may notify the first instances of the OOS condition. Then, based on the indication, the first instance may begin sharing cell search results with the second instance. Additionally, upon expiry of the PST, the first instance may indicate the expiry of the PST to the second instance.

[0105] In some instances, a PLMN search and data sharing stage (e.g., stage-2) may corresponds to the point where a first instances of an MSIM initiates a PLMN search after PST expiry. For example, upon expiry of the PST, in addition to notifying other instances of the MSIM of the expiry of the PST, the first instance may, before starting a PLMN Search, check an RPLMN equivalent PLMN List of one or more other instances of the MSIM. In some instances, when the RPLMN equivalent PLMN List of one or more other instances of the MSIM matches an RPLMN equivalent PLMN List of the first instance, the first instance may only include its RPLMN equivalent PLMN List in its cell (e.g., PLMN) search. Otherwise, the first instance may add any differing PLMNs into its task equivalent PLMN List for cell (e.g., PLMN) search. Further, as the first instance collects search results, the first instance may send updated search result information to the other instances of the MSIM that have reported an OOS / LS condition as well as update a shared cell selection database with search information and / or search result information as search results are determined, e.g., as the first instance determines whether a cell and / or set of cells within a searched list is found or not found. In some instances, if and / or when an other instance, e.g., a second instance, of the MSIM experiences an OOS condition while the first instance is performing the cell search, the other instance may notify the first instance of the OOS condition. Upon receipt of the notification,the first instance may begin to share search results with the other instance as the search results are received and / or determined, e.g., without delay. In some instances, if and / or when an other instance, e.g., a second instance, of the MSIM experiences an OOS condition while the first instance is performing the cell search and the other instance has a different RPLMN equivalent PLMN list than the first instance, when the first instance is on an search on an only found frequencies of corresponding PLMNs step of the cell search, the first instance may share already received search result upon receipt of an OOS indication from the other instance and then search only differing PLMNs from the RPLMN equivalent list for the other instance. In some instances, if and / or when an other instance, e.g., a second instance, of the MSIM experiences an OOS condition while the first instance is performing the cell search and the other instance has a different RPLMN equivalent PLMN list than the first instance, when the first instance is on any cell search step of the cell search, the first instance may share already received search result upon receipt of an OOS indication from the other instance, pause a current band scan and create a PLMN task list with only differing PLMNs and insert missed PLMNs from an RPLMN equivalent list of the other instance.

[0106] In some instances, an actions based on PLMN search results and priority framework stage (e.g., stage-3) may correspond to a point in time where a first instance of an MSIM either stops a cell (e.g., PLMN) search due to finding an interested PLMN or the cell search completes with no PLMN or lower priority / non-allowable PLMNs detected. In such instances, a priority framework may be used when multiple instances (e.g., a first instance and a second instance) of an MSIM detect an interested PLMN and want to trigger cell selection. In such a scenario, using the priority framework, a priority may be assigned to each pending task and each instance may update their respective task priority. For example, each instance may update its task priority in a shared cell selection database and, upon determining to trigger cell selection, each instance may first check task priority of other instances prior to triggering cell selection. In this manner, cell selection may be triggered in order of higher priority to lowest priority.

[0107] Figures 8A, 8B, 8C, 8D, 8E, 8F, 8G, 8H, and 9 illustrate examples of signaling for a shared cell search in a multi-SIM UE, according to some embodiments. The signaling shown in Figures 8A-G and 9 may be used in conjunction with one another as well any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired. As shown, this signaling may flow as follows.

[0108] Note that Figures 8A-H and 9 describe internal signaling of a UE, such as UE 106, that is attached to at least one cell of a network via two or more connections supported by two or more SIMs and / or two or more instances of a SIM. As shown in Figures 8A-G and 9, the UE may include two or more network access stratum (NAS) mobility management (NAS_MM) entities, such as NAS_MMs 845a-n and may further host a database, such as database 804. The NAS_MMs may be in communication with one another, e.g., via a system bus, and in communication with the database. Note further that each NAS MM may correspond to a SIM and / or instances of a SIM, thus the UE may be considered a multi-SIM UE. Further, each SIM may have a unique identifier. In some instances, multiple SIMS of the UE may be serviced by a common carrier, thus, when one SIM experiences an out-of-service (OOS) and / or low / limited service (LS) event, it is likely that other SIMS on the UE are or will also experience the OOS / LS event. Thus, the signaling described herein in reference to Figures 8A-G and 9 may allow the UE to efficiently recover from such events by limiting a search for coverage (e.g., cell search and / or PLMN search) to a single SIM and share results of the search for coverage between SIMs.

[0109] Turning to Figure 8A, the signaling shown in Figure 8A corresponds to an immediate coverage stage (e.g., stage 0) in which the UE detects an OOS event and attempts to re-establish a lost connection with a current serving cell. As shown, this signaling may flow as follows.

[0110] The NAS_MMs 845a-n may each send a message 808a-c including a corresponding current PLMN equivalent list to the database 804 to update the database. Each respective message may include an index identifying a respective NAS_MM. In addition, the message may include a state variable, a last registered PLMN (RPLMN) equivalent list, an equivalent HPLMN (eHPLMN) list, and / or a preferred PLMN list. The state variable may be maintained to indicate various stages of search, e.g., such as OOS start, OOS end, PLMN Search Timer (PST) start, PST end, and so forth. The RPLMN equivalent list, eHPLMN list, and / or preferred PLMN list may be used for cross instance sharing. At 810, the NAS_MM 845a may detect an OOS condition. Based on the detection of the OOS condition, the NAS MM 845a may notify other NAS MM instances of the OOS condition via OOS notifications 812. The OOS notifications 812 may indicate that NAS MM 845a has experienced an OOS condition and is attempting cell selection 814 to immediately resume a connection to the network.[OHl] In some instances, NAS MM 845b may also detect an OOS condition at 816. In response, NAS_MM 845b may notify NAS_MM 845a of the OOS condition via OOS notification 818. In response, NAS_MM 845a may share any cell search results since detectingthe OOS condition at 810 via message 820, e.g., such as interested PLMNs, allowable PLMNs, and so forth. In some instances, e.g., if NAS_MM 845a was successful with resuming the connection to the network, NAS_MM 845b may attempt cell selection 822, e.g., based on the search results received via message 820. Note that at least in some instances, NAS MM 845b may not experience an OOS condition at this point.

[0112] Similarly, in some instances, NAS_MM 845n may also detect an OOS condition at 824. In response, NAS_MM 845n may notify NAS_MM 845a of the OOS condition via OOS notification 826. In response, NAS_MM 845a may share any cell search results since detecting the OOS condition at 810 via message 828, such as interested PLMNs, allowable PLMNs, and so forth. In some instances, e.g., if NAS_MM 845a was successful with resuming the connection to the network, NAS_MM 845n may attempt cell selection 830, e.g., based on the search results received via message 828. Note that at least in some instances, NAS MM 845n may not experience an OOS condition at this point.

[0113] Turning to Figure 8B, the signaling shown in Figure 8B corresponds to a PLMN search timer start and expiry stage (e.g., stage-1), e.g., to the point where when a first instance of an MSIM (e.g., NAS MM 845a) experiences an OOS condition, moves to an OOS state, and initiates (starts) a PLMN Search Timer (PST) after immediate recovery failure (e.g., failure to find service at stage-0). As shown, this signaling may flow as follows.

[0114] At 832, after failure to find service via an immediate recovery process (e.g., as described above in reference to Figure 8A), NAS MM 845a may move to an OOS state and start a PST. Upon starting the PST, NAS MM 845a may send PST start notifications 834 to NAS_MMs 845b-n. In addition, the NAS_MM 845a may send a state variable update 836 to database 804. The state variable update 836 may indicate that NAS MM 845a has moved to the OOS state and initiated the PST. At 850, the PST may expire and NAS MM 845a may, upon expiry of the PST, send a state variable update 852 to database 804. The state variable update 852 may indicate that the expiry of the PST. In addition, NAS MM 845a may send PST expiry notifications 854 to NAS_MMs 845b-n.

[0115] In some instances, during a duration of the PST initiated by NAS_MM 845a, NAS_MM 845b may move to an OOS state at 838 and may send a search information update 840 to database 804. The search information update 840 may include a state variable, a last registered PLMN (RPLMN) equivalent list, an equivalent HPLMN (eHPLMN) list, and / or a preferred PLMN list. The state variable may be maintained with critical selection for detecting OOS / LS scenario start / end. The RPLMN equivalent list, eHPLMN list, and / or preferred PLMN list mayinclude entries from each instance of the MSIM and may be used for cross instance sharing. Note that, based on receiving PST start notification 834, NAS_MM 845b may not initiate a PST. Instead, NAS_MM 845b may send a state notification 842 to NAS_MM 845a indicating the move to the OOS state. Note that at least in some instances, NAS MM 845b may not experience an OOS condition at this point.

[0116] In some instances, during a duration of the PST initiated by NAS_MM 845a, NAS_MM 845n may move to an OOS state at 844 and may send a search information update 846 to database 804. The search information update 846 may include a state variable, a last registered PLMN (RPLMN) equivalent list, an equivalent HPLMN (eHPLMN) list, and / or a preferred PLMN list. The state variable may be maintained with critical selection for detecting OOS / LS scenario start / end. The RPLMN equivalent list, eHPLMN list, and / or preferred PLMN list may include entries from each instance of the MSIM and may be used for cross instance sharing. Note that, based on receiving PST start notification 834, NAS_MM 845n may not initiate a PST. Instead, NAS_MM 845n may send a state notification 848 to NAS_MM 845 indicating the move to the OOS state. Note that at least in some instances, NAS MM 845n may not experience an OOS condition at this point.

[0117] Turning to Figure 8C, the signaling shown in Figure 8C corresponds to a PLMN search and data sharing stage (e.g., stage-2), e.g., a point where a first instances of an MSIM (e.g., NAS_MM 845a) initiates a PLMN search after PST expiry. As shown, this signaling may flow as follows.

[0118] After transmitting PST expiry notifications 854 (e.g., at the end of the PLMN search timer start and expiry stage), NAS_MM 845a may retrieve RPLMN information 856 from database 804. The RPLMN information 856 may be associated with NAS_MMs 845b-n. At 858, NAS_MM 845a may perform a PLMN search. In some instances, prior to initiating the PLMN search, NAS_MM 845a may compare RPLMNs associated with NAS_MMs 845b-n with RPLMNs associated with NAS_MM 845a and add RPLMNs not associated with NAS MM 845a. In other words, RPLMNs retrieved from the database that are not include in a RPLMN search list of NAS_MM 845a may be added to the RPLMN search list. After the search, NAS_MM 845a may update search information / search results at database 804 via message 860. Further NAS_MM 845a may share search data (e.g., results) with NAS_MMs 845b-n via messages 862. Message 860 may include search result information such as a search process type, a search counter, PLMN information such as a found PLMN list, and / or a search type array. The search type array may include an indication of data validity, a task PLMN list,a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information.

[0119] Turning to Figures 8D-H, the signaling shown in Figures 8D-H correspond to an actions based on PLMN search results stage (e.g., stage-3), e.g., a point in time where a first instance of an MSIM (e.g., NAS_MM 845a) either stops a cell (e.g., PLMN) search due to finding an interested PLMN or the cell search completes with no PLMN or lower priority / non-allowable PLMNs detected. As shown, this signaling may flow as follows.

[0120] Turning to Figure 8D, As discussed above, after transmitting PST expiry notifications 854 (e.g., at the end of the PLMN search timer start and expiry stage), NAS_MM 845a may retrieve RPLMN information 856 from database 804. The RPLMN information 856 may be associated with NAS_MMs 845b-n. At 864, NAS_MM 845b may move to an OOS state and send OOS notification 866 to NAS_MM 845a. In response, NAS_MM 845a may retrieve RPLMN information associated with NAS_MM 845b from database 804. At 870, NAS_MM 845a may compare an RPLMN list associated with NAS_MM 845a to the retrieved RPLMN information and add any RPLMNs from the retrieved RPLMN information to the RPLMN list associated with NAS_MM 845a to generate an updated RPLMN list. At 872, NAS_MM 845a may perform a PLMN search based on the update RPLMN list. Upon discovering an interested PLMN, NAS_MM 845a may send a search result update 874 to database 804 and share search data via message 876 with NAS_MMs 845b-n. Message 874 may include search result information such as a search process type, a search counter, PLMN information such as a found PLMN list, and / or a search type array. The search type array may include an indication of data validity, a task PLMN list, a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information.

[0121] Turing to Figure 8E, after sharing search data via message 876, in some instances, NAS_MM 845a may initiate cell selection. Upon selecting the interested PLMN, NAS_MM 845a may send a state variable update 880 to database 804 indicating cell selection is ongoing. In addition, NAS_MM 845a may send a cell selection notification 882 to NAS_MM 845b indicating the selection of the interested PLMN.

[0122] At 884, in at least some instances, NAS_MM 845b may determine that the interested PLMN is an allowable PLMN for NAS_MM 845b. At 886, based on the determination, NAS_MM 845b may initiate cell selection.

[0123] Turning to Figure 8F, after sharing search data via message 876, in some instances, NAS_MM 845a may initiate cell selection. Upon selecting the interested PLMN, NAS_MM845a may send a state variable update 880 to database 804 indicating cell selection is ongoing. In addition, NAS_MM 845a may send a cell selection notification 882 to NAS_MM 845b indicating the selection of the interested PLMN.

[0124] At 888, in at least some instances, NAS_MM 845b may determine that the interested PLMN is not an allowable PLMN for NAS_MM 845b. Thus, at 890, based on the determination, NAS_MM 845b may initiate a cell search based on previously shared search data, e.g., such as search data shared via message 876, e.g., as described above in reference to Figure 8D.

[0125] Turning to Figure 8G, after sharing search data via message 876, in some instances, NAS_MM 845a may determine that PLMNs other than an RPLMN / HPLMN has been found. In such instances, NAS_MM 845a may include the PLMNs other than the RPLMN / HPLMN in cell selection notification 882. Then, based on the cell selection notification 882, NAS MM 845a and NAS_MM 845b may initiate cell selections at 892a and 892b, respectively.

[0126] Turning to Figure 8H, after sharing search data via message 876, in some instances, NAS_MM 845a may determine that no PLMNs have been found. In such instances, NAS_MM 845a may include an indication that no PLMNs have been found in cell selection notification 882. Further, at 894, NAS_MM 845a may initiate a PST, e.g., thereby returning NAS_MM 845a to the PLMN search timer start and expiry stage (e.g., stage-1). Upon starting the PST, NAS_MM 845a may send PST start notification 896 to NAS_MM 845b. In addition, the NAS MM 845a may send a state variable update 898 to database 804. The state variable update 898 may indicate that NAS MM 845a remains in the OOS state and initiated an other PST.

[0127] Turning to Figure 9, the signaling shown in Figure 9 corresponds to a priority framework executed upon discovery of an interested PLMN. As shown, this signaling may flow as follows.

[0128] Prior to experiencing an OOS condition, each NAS_MM, e.g., NAS_MMs 845a-n of a UE, e.g., UE 106, may send a priority indication to database 804. Thus NAS_MMs 845a-n may send priority indications 902, 904, and 906, respectively, to database 804. The priority may be assigned according to a priority framework based on a pending task at each NAS MM and each NAS_MM may use the priority framework to assign a priority value to the pending task. Note that a higher priority task may be an indication that an NAS_MM associated with the higher priority task should camp on a cell (e.g., select a cell) prior to other NAS_MMs with tasks of lower priority than the higher priority task.

[0129] Thus, as shown, assuming NAS MM 845a has experienced an OOS condition and failed to immediately recover, NAS_MMs 845a-n may progress through various stages of cell search and selection, e.g., as described above. Thus, NAS_MMs may progress through stage- 1 at 908 (e.g., corresponding to a PLMN search timer start and expiry stage as described above) and stage-2 at 910 (e.g., corresponding to a PLMN search and data sharing stage as described above). Further, at 912, NAS_MM 845a may determine that an allowable PLMN has been found and send a search result update via message 914 to database 804. Message 914 may include search result information such as a search process type, a search counter, PLMN information such as a found PLMN list, and / or a search type array. The search type array may include an indication of data validity, a task PLMN list, a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information. Additionally, NAS_MM 845a may perform a priority check 916 to determine whether or not a pending task for NAS_MM 845a has a higher priority than pending tasks for NAS_MMs 845b- n. Note that when the pending task for NAS_MM 845a has a higher priority than pending tasks for NAS_MMs 845b-n, NAS_MM 845a may proceed with cell selection (e.g., attempting to camp on the allowable PLMN). Otherwise, NAS_MM 845a may wait for an indication from other NAS_MMs with higher priority tasks prior to proceeding with cell selection. After performing the priority check at 916, NAS_MM 845a may send search selection notifications 918 to NAS_MMs 845b-n. Upon receipt of a search selection notification, each NAS MM may perform a priority check. Thus, NAS_MM 845b may perform priority check 920 and NAS_MM 845n may perform priority check 922. In this manner, the NAS_MMs 845a-n may proceed with cell selection in a priority order based on a priority of a pending task.

[0130] Figure 10 illustrates a block diagram of an example of a method for a shared cell search algorithm in a multi-SIM UE, according to some embodiments. The method shown in Figure 10 may be used in conjunction with any of the systems, methods, or devices shown in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired. As shown, this method may operate as follows.

[0131] At 1002, a UE, such as UE 106, that includes a plurality of Subscriber Identity Module (SIM) instances, may detect, at a first SIM instance of the plurality of SIM instances, a service interruption while camped on a first cell of a network. A connection to the first cell may supportcommunication via at least the first SIM instance. The service interruption may be an out-of- service (OOS) condition and / or a low / limited service condition.

[0132] At 1004, the first SIM instance may notify at least a second SIM instance of the plurality of SIM instances that the first SIM detected the service interruption.

[0133] At 1006, the first SIM instance may retrieve, upon expiry of a public land mobile network (PLMN) search timer (PST) initiated by the first SIM instance, first last registered PLMN (RPLMN) information from a database hosted by the UE upon failure of an immediate recovery of service. In some instances, the database may include, for each of the plurality of SIM instances of the UE, one or more of a state variable, an RPLMN equivalent list, an equivalent HPLMN (eHPLMN) list, and / or or a preferred PLMN list. The state variable may be maintained with critical selection for detecting service interruption start and end.

[0134] At 1008, the first SIM instance may initiate a PLMN search based, at least in part, on the first RPLMN information retrieved from the database.

[0135] At 1010, the first SIM instance may share, upon and / or in response to receiving a service interruption indication form at least a second SIM instance, search information from the PLMN search with the second SIM instance. In other words, when the first SIM receives an indication from an other SIM instance that the other SIM instance has also experienced a service interruption and / or has moved to an OOS state, the first SIM instance may begin sharing search results with the other SIM instance. In some instances, the search information may include one or more of a search process type, a search counter, a found PLMN list, and / or a search type array. The search type array may include one or more of an indication of data validity, a task PLMN list, a Mobile Country Code (MCC) array, a search complete indication, a found PLMN list, and / or frequency band information.

[0136] In some instances, prior to detecting the service interruption, the first SIM instance may camp on the first cell and send, to the database, a PLMN equivalent list.

[0137] In some instances, the first SIM instance may attempt, after detecting the service interruption and prior to initiating the PST, cell selection via a cell search as part of an immediate recovery process for recovery from the service interruption. Further, the first SIM instance may receive, from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption and upon successfully completing a PLMN and / or cell search (e.g., discovering, finding, and / or determining there is an allowable PLMN / cell to camp on) and / or re-establishing service (e.g., camping on a cell), share search results with the second SIM instance.

[0138] In some instances, the first SIM instance may, upon failing to immediately recover from the service interruption, move to an OOS state and initiate the PST. Additionally, the first SIM instance may send an indication of the initiation of the PST to at least the second SIM instance. Further, the first SIM instance may send a first state variable update to the database. The first state variable update may indicate that the first SIM instance has entered an OOS state. In addition, upon expiry of the PST, the first SIM instance may send a second state variable update to the database. The second state variable update may indicate that the first SIM instance is moving to a cell search state. In some instances, the first SIM instance may, upon expiry of the PST, send an indication of the expiry of the PST to at least the second SIM instance. Note that in some instances, prior to expiry of the PST, the first SIM instance may receive, from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption.

[0139] In some instances, the first SIM instance may, prior to initiating the PLMN search, receive from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption. The first SIM instance may retrieve second RPLMN information associated with the second SIM instance from the database and compare the first RPLMN information to the second RPLMN information. The first SIM instance may add PLMNs from the second RPLMN information that are not in the first RPLMN information to a PLMN search list. In such instances, the PLMN search may be also (and / or further) based, at least in part, on the PLMN search list.

[0140] In some instances, the first SIM instance may send search results to the database.

[0141] In some instances, the first SIM instance may, after unsuccessfully searching for a PLMN to camp on, send a cell selection notification to at least the second SIM instance and reinitiate the PST. Further, the first SIM instance may send, to at least the second SIM instance, an indication of the re-initiation of the PST and send, to the database, a state variable update indicating re-initiation of the PST.

[0142] In some instances, prior to detecting the service interruption, the first SIM instance may camp on the first cell and send a priority of a task associated with a connection supported by the first SIM instance. In some instances, the first SIM instance may receive, from at least the second SIM instance, an indication that the second SIM instance is in an OOS state and, upon successfully finding an interested PLMN, query, from the database, priority information associated tasks supported by at least the second SIM instance. The first SIM instance may, prior to attempting to camp on the interested PLMN, compare the priority of the task associatedwith the connection supported by the first SIM instance to a priority of a task associated with a connection supported by the second SIM instance. In some instances, when the priority of the task associated with the connection supported by the second SIM instance is higher than the priority of the task associated with the connection supported by the first SIM instance, the first SIM instance may a search selection notification indicating the interested PLMN and delay camping on the interested PLMN until receiving, from the second SIM instance, an indication that the second SIM instance has successfully established a connection.

[0143] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0144] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer- readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[0145] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any 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.

[0146] In some embodiments, a device (e.g., a UE 106) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodimentsdescribed herein, or, any combination of such subsets). The device may be realized in any of various forms.

[0147] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as message / signal X transmitted by the base station, and each message / signal Y transmitted in the uplink by the UE as a message / signal Y received by the base station.

[0148] Although the embodiments above 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 embrace all such variations and modifications.

Claims

CLAIMSWhat is claimed is:

1. A method for a shared cell search, comprising: detecting, at a first Subscriber Identity Module (SIM) instance of a plurality of SIM instances of a user equipment device (UE), a service interruption while camped on a first cell of a network, wherein a connection to the first cell supports communication via at least the first SIM instance; notifying at least a second SIM instance of the plurality of SIM instances that the first SIM detected the service interruption; retrieving, by the first SIM instance and upon expiry of a public land mobile network (PLMN) search timer (PST) initiated by the first SIM instance, last registered PLMN (RPLMN) information; initiating, by the first SIM instance, a PLMN search based, at least in part, on the first RPLMN information; and sharing, upon receiving a service interruption indication from at least the second SIM instance, search information from the PLMN search with at least the second SIM instance.

2. The method of claim 1, wherein the service interruption comprises at least one of: an out-of-service (OOS) condition; or a low or limited service condition.

3. The method of claim 1, comprising: prior to detecting the service interruption: camping on the first cell; and sending, to a database hosted by the UE, a PLMN equivalent list.

4. The method of claim 1, comprising: attempting, after detecting the service interruption and prior to initiating the PST, cell selection via a cell search as part of an immediate recovery process for recovery from the service interruption.

5. The method of claim 4, comprising: receiving, from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption; and upon successfully re-establishing service, sharing search results with the second SIM instance.

6. The method of claim 1, comprising: upon failing to recover from the service interruption, moving to an out-of-service (00 S) state; initiating the PST; sending, by the first SIM instance, an indication of the initiation of the PST to at least the second SIM instance.

7. The method of claim 6, comprising: sending, by the first SIM instance, a first state variable update to a database hosted by the UE, wherein the first state variable update indicates that the first SIM instance has entered an OOS state.

8. The method of claim 7, comprising: upon expiry of the PST, sending, by the first SIM instance, a second state variable update to the database, wherein the second state variable update indicates that the first SIM instance is moving to a cell search state.

9. The method of claim 6, comprising: upon expiry of the PST, sending, by the first SIM instance, an indication of the expiry of the PST to at least the second SIM instance.

10. The method of claim 6, comprising: prior to expiry of the PST, receiving, from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption.

11. The method of claim 1, comprising:prior to initiating, by the first SIM instance, the PLMN search, receiving from at least the second SIM instance, an indication that the second SIM instance has experienced a service interruption; retrieving, by the first SIM instance, second RPLMN information associated with the second SIM instance from a database hosted by the UE; comparing the first RPLMN information to the second RPLMN information; and adding PLMNs from the second RPLMN information that are not in the first RPLMN information to a PLMN search list; and wherein the PLMN search is also based, at least in part, on the PLMN search list.

12. The method of claim 1, comprising: sending, by the first SIM instance, search results to a database hosted by the UE.

13. The method of claim 1, comprising: after unsuccessfully searching for a PLMN to camp on, sending, by the first SIM instance, a cell selection notification to at least the second SIM instance; and re-initiating, by the first SIM instance, the PST.

14. The method of claim 13, sending, to at least the second SIM instance, an indication of the re-initiation of the PST; and sending, to a database hosted by the UE, a state variable update indicating re-initiation of the PST.

15. The method of claim 1, wherein the UE hosts a database comprising , for each of the plurality of SIM instances of the UE, one or more of: a state variable; an RPLMN equivalent list; an equivalent HPLMN (eHPLMN) list; or a preferred PLMN list.

16. The method of claim 1,prior to detecting the service interruption: camping on the first cell; and sending, by the first SIM instance, a priority of a task associated with a connection supported by the first SIM instance.

17. The method of claim 16, receiving, from at least the second SIM instance, an indication that the second SIM instance is in an out-of-service (OOS) state; upon successfully finding an interested PLMN, querying, from a database hosted by the UE, priority information associated tasks supported by at least the second SIM instance; and prior to attempting to camp on the interested PLMN, comparing the priority of the task associated with the connection supported by the first SIM instance to a priority of a task associated with a connection supported by the second SIM instance.

18. The method of claim 17, wherein, when the priority of the task associated with the connection supported by the second SIM instance is higher than the priority of the task associated with the connection supported by the first SIM instance, sending, by the first SIM instance, a search selection notification indicating the interested PLMN; and delaying camping on the interested PLMN until receiving, from the second SIM instance, an indication that the second SIM instance has successfully established a connection.

19. A baseband processor, comprising: a memory; and processing circuitry in communication with the memory and configured to perform a method according to any of claims 1 to 18.

20. A non-transitory computer readable memory medium storing program instructions executable by a processor operably coupled to the memory medium to perform a method according to any of claims 1 to 18.

Images