Systems, methods, and devices for UE capability design for multiple searcher based rrm

Abstract

The techniques described herein can include solutions for user equipment (UE) capability for multiple searcher based radio resource management (RRM). To perform RRM, network devices can use measurements of carriers performed by UEs. A UE can indicate a searcher capability, which indicates the number of carriers the UE can measure simultaneously. The searcher capability can be based on conditions and can be updated when conditions change. For example, the searcher capability can be based on band combinations, frequency ranges, or both. In some examples, the UE can update the searcher capability when a configuration changes. Configurations can include serving cell configurations and measurement object configurations. The UE can indicate the searcher capability to a network device.

Description

Attorney Docket No.: 106842257540 (P70733WO1)SYSTEMS, METHODS, AND DEVICES FOR UE CAPABILITY DESIGN FOR MULTIPLE SEARCHER BASED RRMCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 755,712, filed February 7, 2025, the content of which is herein incorporated by reference in its entirety for all purposes.FIELD

[0002] This disclosure relates to wireless communication networks and mobile device capabilities.BACKGROUND

[0003] Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fourth generation (4G), fifth generation (5G) or new radio (NR) technology. Such technology can include solutions for managing radio resources.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals can designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and can mean at least one, one or more, etc.

[0005] Figure 1 is a diagram of an example of an overview according to one or more implementations described herein.

[0006] Figure 2 is a diagram of an example network according to one or more implementations described herein.

[0007] Figure 3 is a diagram of an example process for user equipment (UE) capability design for multiple searcher based radio resource management (RRM) according to one or more implementations described herein.

[0008] Figure 4 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein.14905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)

[0009] Figure 5 is a diagram of an example sequence flow for UE capability design for multiple searcher based RRM according to one or more implementations described herein

[0010] Figure 6 is a diagram of an example of components of a device UE capability design for multiple searcher based RRM according to one or more implementations described herein.

[0011] Figure 7 is a diagram of example interfaces of baseband circuitry according to one or more implementations described herein.

[0012] Figure 8 is a block diagram illustrating components, according to one or more implementations described herein, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

[0013] Figure 9 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein.

[0014] Figure 10 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein.

[0015] Figure 11 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein.DETAILED DESCRIPTION

[0016] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.

[0017] Telecommunication networks can include user equipment (UEs) capable of communicating with base stations and / or other network access nodes. UEs and base stations can implement various techniques and communications standards for enabling UEs and base stations to discover one another, establish and maintain connectivity, and exchange information in an ongoing manner. Objectives of such techniques can include adaptive use of UE memory for different scenarios.

[0018] Devices in a radio network can perform radio resource management (RRM). RRM can include system level management of co-channel interference, channels, signals, resources, and other radio transmission characteristics. To perform RRM, network devices can use measurements of carriers performed by UEs. UEs can support multiple searchers, or can perform measurements of a multiple carriers simultaneously. However, memory restrictions, operation 24905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)modes, frequency range, frequency band, among other factors, can affect the capability of the UE to simultaneously perform measurements of multiple carriers. Thus, in different conditions, the UE can support different numbers of searchers (e.g., 2 searchers, 3 searchers).

[0019] Further, as conditions change, the number of searchers that the UE supports can also change. Configuring the UE with a lower number of searchers (e.g., 2 searchers), can prevent the memory and capability of the UE from being exceeded, but additional memory can be unused that could support additional searchers. Configuring the UE is with a higher number of searchers (e.g., 3 searchers), can result in utilizing the UE’s full capability, but in some examples, can exceed the memory and capabilities of the UE. Methods and techniques for determining UE searcher capability would be advantageous for optimal memory use and carrier measurements for RRM.

[0020] One or more of the techniques described herein address the foregoing deficiencies by providing solutions for UE capability design for multiple searcher based RRM. The searcher capability can be based on conditions and can be updated when conditions change. For example, the searcher capability can be based on band combinations, frequency ranges, or both. In some examples, the UE can update the searcher capability when a configuration changes.Configurations can include serving cell configurations and measurement object configurations. The UE can indicate the searcher capability to a network device. The UE can perform measurements accordingly and communicate the measurements to the network device for RRM.

[0021] By indicating the searcher capability based on conditions, and updating when configurations change, the searcher capability is adapted to current conditions. Techniques and methods described herein can result in optimal memory use, supporting RRM, and efficient carrier measurements, among other advantages.

[0022] Figure 1 is a diagram of an example of an overview 100 according to one or more implementations described herein. Overview 100 can be an example of UE 110 determining searcher capability and indicating the searcher capability to radio access node (RAN) 120. As shown, overview 100 can be performed by UE 110 and RAN 120. Operations described as being performed by UE 110 can be performed, at least in part, by baseband circuitry of UE 110. RAN 120 can be implemented by a base station or another type of network access point. Some or all of overview 100 can be performed by one or more other systems or devices, including one or more of the devices described herein.

[0023] UE 110 can communicate a searcher capability to RAN 120. RAN 120 can be an example of a network device (e.g., network entity, gNB, base station). RRM can include system level management of co-channel interference, channels, signals, resources, and other radio34905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)transmission characteristics. To support RRM, UE 110 can perform measurements of carriers, and indicate the measurements to RAN 120. Measurements of carriers can include reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference plus noise ratio (SINR), and reference signal measurements, among other measurements.

[0024] UE 110 can perform measurements of multiple carriers simultaneously, which can be called a searcher number. The searcher number can be described is a resource for measurement. The searcher number can be limited by the UE memory size of the baseband processing. For example, if the memory size can allow UE 110 to buffer X carriers bandwidth sequences, then UE 110 can claim that it can support X searchers for cell searching and measurement. Depending on the UE operation mode (e.g., carrier aggregation (CA), dual connectivity (DC)). For example, UE 110 can support 2 searchers. In such an example, UE 110 can search for and measure 2 carriers simultaneously, increasing measurement efficiency.

[0025] However, increasing the number of searchers also increases the memory demands. Different carriers can have different memory demands, such that UE 110 can support varying numbers of searchers based on carrier bandwidth sequences. For example, UE 110 can perform measurements without measurement gaps of different types of carriers, and those carriers can have different memory size requirements for buffering. For example, an FR1 carrier with 100MHz and 5ms searching window has much less memory demand than the FR2 carrier with 400MHz and 5ms searching window. Regarding LTE measurement, since LTE PSS / SSS is available every 5ms, and CRS is available on every slot. The LTE measurement can be performed in a TDM manner from NR measurement, to not complete against NR measurement for memory usage, however, it still necessary to check the time proximity between NR measurement occasion and LTE measurement occasion.

[0026] Thus, UE 110 can support different numbers of searchers in different scenarios. Scenarios include FR1, FR2, or combinations of FR1 and FR2. For example, in some scenarios, UE 110 can support 2 searchers, and in other scenarios, UE 110 can support 3 searchers.

[0027] To facilitate varying numbers of searchers based on conditions, UE 110 can transmit a searcher capability 115. The searcher capability 115 can be based on various factors. In some examples, when conditions change, UE 110 can update the searcher capability 115. For example, UE 110 can update capability based on serving cell change (at block 130). UE 110 can update capability based on measurement objects (MOs) configuration change (at block 140).

[0028] UE 110 can indicate searcher capability for band combinations (at block 150). In some examples, UE 110 can indicate different capabilities for different band combinations. For example, UE 110 can indicate a 2 searcher capability for a band combination in FR1+FR2, and a 44905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)3 searcher capability for a band combination in FR1.

[0029] UE 110 can indicate searcher capability for frequency ranges (at block 160). For example, UE can indicate different searcher capabilities for FR1, FR2, and combinations of FR1 and FR2. In some examples, after determining searcher capability, UE 110 can allocate searcher resources among target carriers for measurement.

[0030] Using multiple searchers, such as 3 searchers, can be used for carrier specific scaling factor (CSSF) reduction. A CSSF value is used to scale the measurement delay when UE 110 performs measurements. CSSF values can change based on mode, frequency range (e.g., FR1, FR2), measurement object, whether measurements are conducted inside a measurement gap or outside a measurement gap, among other factors. For example, for a carrier with a larger frequency range, the CSSF can be larger to account for the additional measurement delay when additional measurements are taken.

[0031] CSSF is applicable for many scenarios without measurement gaps. Each searcher can be associated with a scaling factor. In some examples, optimizing CSSF can reduce measurement delay (e.g., L3 measurements). By optimizing searcher capability and allocation, measurement delay can be reduced. Optimizing CSSF can apply to carrier aggregation (CA) and dual connectivity (DC) modes. Modes can further include evolved non-standalone DC (EN-DC) and E-UTRAN new radio DC (NE-DC) with varying frequency ranges (FR1, FR2), intra band CA, inter band CA, and cells.

[0032] Figure 2 is an example network 200 according to one or more implementations described herein. Example network 200 can include UEs 210, 210-2, etc. (referred to collectively as “UEs 210” and individually as “UE 210”), a radio access network (RAN) 220 (e.g., RAN node 220), a core network (CN) 230, application servers 240, and external networks 250.

[0033] The systems and devices of example network 200 can operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., long-term evolution (LTE)), and / or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example network 200 can operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards54905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)(e.g., wireless metropolitan area network (WMAN), worldwide interoperability for microwave access (WiMAX), etc.), and more.

[0034] As shown, UEs 210 can include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks). Additionally, or alternatively, UEs 210 can include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEs 210 can include internet of things (loT) devices (or loT UEs) that can comprise a network access layer designed for low-power loT applications utilizing short-lived UE connections. Additionally, or alternatively, an loT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximitybased service (ProSe) or device-to-device (D2D) communications, sensor networks, loT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an loT network can include interconnecting loT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, loT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the loT network.

[0035] UEs 210 can communicate and establish a connection with one or more other UEs 210 via one or more wireless channels 212, each of which can comprise a physical communications interface / layer. The connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc. The connection can involve a PC5 interface. In some implementations, UEs 210 can be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN node 222 or another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN node 222 or another type of network node.

[0036] UEs 210 can use one or more wireless channels 212 to communicate with one another. As described herein, UE 210 can communicate with RAN node 222 to request SL resources. RAN node 222 can respond to the request by providing UE 210 with a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can involve a grant based on a grant request from UE 210. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UE 210 can perform a clear channel assessment (CCA) procedure based on the 64905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UE 210 based on the SL resources. The UE 210 can communicate with RAN node 222 using a licensed frequency band and communicate with the other UE 210 using an unlicensed frequency band.

[0037] UEs 210 can communicate and establish a connection with (e.g., be communicatively coupled) with RAN 220, which can involve one or more wireless channels 214-1 and 214-2, each of which can comprise a physical communications interface / layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multiple receive and transmit (Rx / Tx) capable UE can use resources provided by different RAN network nodes (e.g., RAN network nodes 222-1 and 222-2) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G). In such a scenario, one network node can operate as a master node (MN) and the other as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN 230. Additionally, at least one of the MN or the SN can be operated with shared spectrum channel access, and functions specified for UE 210 can be used for an integrated access and backhaul mobile termination (IAB-MT). Similar for UE 210, the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) can be an example of network RAN network nodes.

[0038] As shown, UE 210 can also, or alternatively, connect to access point (AP) 216 via connection interface 218, which can include an air interface enabling UE 210 to communicatively couple with AP 216. AP 216 can comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connection 214 can comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 216 can comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in Fig. 2, AP 216 can be connected to another network (e.g., the Internet) without connecting to RAN 220 or CN 230. In some scenarios, UE 210, RAN 220, and AP 216 can be configured to utilize LTE- WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UE 210 in RRC CONNECTED being configured by RAN 220 to utilize radio resources of LTE and WLAN. LWIP can involve UE 210 using WLAN radio resources (e.g., connection interface 218) via IPsec protocol tunneling to 74905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface 218. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

[0039] RAN 220 can include one or more RAN nodes 222-1 andr-r(referred to collectively as RAN nodes 222, and individually as RAN node 222) that enable channels 214-1 and 214-2 to be established between UEs 210 and RAN 220. A RAN node 222 can be a base station and may be referred to herein as base station, and a base station may be an example of a RAN node 222. RAN nodes 222 can include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi®, etc.). As examples therefore, a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodes 222 can include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., terrestrial access points). In some scenarios, RAN node 222 can be a dedicated physical device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0040] Some or all of RAN nodes 222, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN / vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes 222; a media access control (MAC) / physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN / vBBUP and the PHY layer can be operated by individual RAN nodes 222; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN / vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes 222. This virtualized framework can allow freed-up processor cores of RAN nodes 222 to perform or execute other virtualized applications.

[0041] In some implementations, an individual RAN node 222 can represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual Fl or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads 84905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in RAN 220 or by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN / vBBUP. Additionally, or alternatively, one or more of RAN nodes 222 can be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs 210, and that can be connected to a 5G core network (5GC) 230 via an NG interface.

[0042] Any of the RAN nodes 222 can terminate an air interface protocol and can be the first point of contact for UEs 210. In some implementations, any of the RAN nodes 222 can fulfill various logical functions for the RAN 220 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 210 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 222 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0043] In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 222 to UEs 210, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a timefrequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest timefrequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block can comprise a collection of resource elements (REs); in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0044] Further, RAN nodes 222 can be configured to wirelessly communicate with UEs 210, and / or one another, over a licensed medium (also referred to as the “licensed spectrum” and / or 94905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)the “licensed band”), an unlicensed shared medium (also referred to as the “unlicensed spectrum” and / or the “unlicensed band”), or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity), whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc.) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.

[0045] The PDSCH can carry user data and higher layer signaling to UEs 210. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH can also inform UEs 210 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UE 210 within a cell) can be performed at any of the RAN nodes 222 based on channel quality information fed back from any of UEs 210. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs 210.

[0046] One or more of the techniques, described herein, can enable UE 210 to determine searcher capability, indicate searcher capability, and update searcher capability. Searcher capability indicates the number of carriers UE 210 can measure simultaneously. UE 210 can determine, update, and indicate searcher capability based on serving cell configuration changes, measurement object configuration changes, band combinations, frequency ranges, and other factors. For example, UE 210 can indicate a 2 searcher capability or a 3 searcher capability for varying scenarios and conditions. These and many other features and aspects of the techniques described herein are presented below with reference to remaining Figures.

[0047] The RAN nodes 222 can be configured to communicate with one another via interface 223. In implementations where the system is an LTE system, interface 223 can be an X2 interface. In NR systems, interface 223 can be an Xn interface. The X2 interface can be defined between two or more RAN nodes 222 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN 230, or between two eNBs connecting104905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)to an EPC. The RAN nodes 222 can be configured to communicate with the CN 230 via various interfaces, such as physical interfaces, including interface 224, interface 226, and interface 228.

[0048] As shown, RAN 220 can be connected (e.g., communicatively coupled) to CN 230. CN 230 can comprise a plurality of network elements 232, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 210) who are connected to the CN 230 via the RAN 220. In some implementations, CN 230 can include an evolved packet core (EPC), a 5G CN, and / or one or more additional or alternative types of CNs.

[0049] The components of the CN 230 can be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 230 can be referred to as a network slice, and a logical instantiation of a portion of the CN 230 can be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components / functions.

[0050] As shown, CN 230, application servers 240, and external networks 250 can be connected to one another via interfaces 234, 236, and 238, which can include IP network interfaces. Application servers 240 can include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN 230 (e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application servers 240 can also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VoIP) sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEs 210 via the CN 230. Similarly, external networks 250 can include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEs 210 of the network access to a variety of additional services, information, interconnectivity, and other network features.

[0051] Figure 3 is a diagram of an example of process 300 for UE capability design for multiple searcher based RRM according to one or more implementations described herein.114905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)Process 300 can be an example of UE 110 determining searcher capability and indicating the searcher capability to RAN 220. As shown, process 300 can be performed by UE 110 and RAN 220. Operations described as being performed by UE 110 can be performed, at least in part, by baseband circuitry of UE 110. RAN 220 (e.g., network entity, network device, gNB) can be implemented by base station or another type of network access point. Some or all of process 300 can be performed by one or more other systems or devices, including one or more of the devices of Figs. 1 and 2.

[0052] Additionally, process 300 can include one or more fewer, additional, differently ordered, and / or arranged operations than those shown in Fig. 3. Some, or all, of the operations of process 300 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 300. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in process 300.

[0053] As shown, process 300 can include transmitting, or otherwise indicating, one or more synchronization signal blocks (SSBs) (at 305). For example, UE 110 can receive, such as from RAN 220, SSBs associated with one or more cells.

[0054] Process 300 can also include determining searcher capability (at 310). For example, UE 110 can determine searcher capability (e.g., 2 searcher capability, 3 searcher capability). Searcher capability can indicate the number of carriers UE 110 can measure simultaneously. For example, 3 searcher capability can indicate that UE 110 supports simultaneous measurements on 3 carriers. In some examples, the measurements can be gapless measurements. UE 110 can determine searcher capability based on various factors, including serving cell configuration, measurement object (MO) configuration, frequency band combinations (e.g., band combinations), and frequency ranges (e.g., FR1, FR2).

[0055] UE 110 can determine different capabilities for different band combinations. Band combinations can include band combinations in FR1+FR2, band combinations in FR2+FR2, band combination in LTE + FR1+FR2, band combination in LTE + FR2+FR2, band combination in LTE + FR1+FR1, and band combinations in FR1. In some examples, band combinations can be a serving carrier band combinations or MO carrier combinations. UE 110 can determine a 3 searcher or 2 searcher capability for different band combinations. For example, for the band combination in FR1+FR2, or the band combination of FR2+FR2, UE 110 can support a 2 searcher capability (e.g., UE 110 does not support a 3 searcher capability). UE 110 can support 3 searcher capability for a band combination of FR1. That is, UE 110 can support 2 searcher capability for some band combinations and 3 searcher capability for other band combinations.124905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)UE 110 can also determine searcher capability per band, per band per band combination, or both.

[0056] In some examples, UE 110 can determine searcher capability based on frequency range (e.g., FR1 and FR2). UE 110 can indicate the capability as frequency specific (e.g., applying only to FR1 or FR2) or as frequency combination specific (e.g., applying to a combination of FR1 and FR2). For example, UE 110 can support a 3 searcher capability for FR1+FR1, FR1+FR2, orFR2.

[0057] In some examples, the absence of a 3 searcher capability indicates that UE 110 supports 2 searcher capabilities. For example, UE 110 can indicate 3 searcher capability support for FR1 and may not indicate 3 searcher support for FR2 and FR1+FR2. A 3 searcher capability support for FR1 indicates that UE 110 can measure 3 carriers with FR1 simultaneously. Not indicating 3 searcher capability for FR2 and FR1+FR2 can indicate that UE 110 supports 2 searcher capability for FR2 and FR1+FR2. Similarly, UE 110 can determine frequency range specific searcher capabilities for frequency ranges for serving carriers, frequency ranges for MOs, or both.

[0058] In some examples, UE 110 can be configured with LTE MO. In such examples, UE 110 can reference a periodicity threshold for NR S SB-based RRM measurement timing configuration (SMTC) or SSB periodicity. When the NR SMTC or SSB periodicity is smaller than the periodicity threshold, UE 110 can determine support of 2 searcher capability. For NR measurements, 3 searcher capability can be supported by the UE 110 when the NR SMTC or SSB periodicity is greater than the periodicity threshold. In such examples, LTE MO may not be counted in the CSSF for measurement. In some examples, when the NR SMTC or SSB periodicity is smaller than the periodicity threshold, UE 110 can determine support of 3 searcher capability. In such examples, LTE MO can be counted in the CSSF for measurement.

[0059] Process 300 can include indicating a searcher capability (at 315). For example, UE 110 can transmit a searcher capability to RAN 220. The searcher capability can indicate how many searchers UE 110 supports in various circumstances, and how many carriers UE 110 can measure simultaneously.

[0060] For example, UE 110 can indicate a searcher based gapless measurement capability (e.g., 3 searcher capability) for different band combinations. In such examples, UE 110 can simultaneously measure carriers for different band combinations. UE 110 can indicate a 2 searcher capability for some band combinations and a 3 -searcher capability for other band combinations. For example, UE 110 can indicate a 2-searcher capability for band combination in FR1+FR2 or band combination in FR2+FR2, and a 3 -searcher capability for band combination in FR1. The band combinations can be serving carrier band combinations or MO carrier band 134905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)combinations. Similarly, UE 110 can indicate searcher capability per band, per band per band combination, or a combination thereof.

[0061] In some examples, UE 110 can indicate searcher capability for frequency ranges (e.g., FR1+FR1, FR1+FR2, FR2), or may refrain from doing so. UE 110 can indicate the searcher capability as frequency range specific or as frequency range combination specific. The absence of a 3-searcher capability can indicate that UE 110 supports 2-searcher capabilities. For example, UE 110 can indicate 3-searcher capability support FR1, and may not indicate 2-searcher support for FR2 and FR1+FR2. Similarly, UE 110 can indicate frequency specific searcher capability for frequency range for serving carriers, frequency range for MOs, or a combination thereon.

[0062] Process 300 can include allocating resources (at 320). For example, RAN 220 can allocate resources for signaling based on the searcher capability (e.g., searcher capabilities) indicated by UE 110.

[0063] Process 300 can include indicating carrier signal(s) (at 325). For example, RAN 220 can transmit carrier signals to UE 110. The carrier signals can be transmitted in groups based on UE 110 searcher capability. For example, if UE 110 indicates a 3-searcher capability, RAN 220 can transmit 3 carrier signals.

[0064] Process 300 can include performing RRM measurement s) (at 330). For example, UE 110 can perform carrier measurements. Carrier measurements can include RRM measurements, such as RSRP, RSRQ, SINR, among other measurements.

[0065] Process 300 can include indicating a serving cell configuration (at 335). For example, RAN 220 can transmit a serving cell configuration to UE 110. In some examples, the serving cell configuration can change the serving cell configuration, such as by adding a new serving cell or by changing serving cell.

[0066] Process 300 can include indicating an updated searcher capability (at 340). For example, UE 110 can transmit an updated searcher capability to RAN 220 based on the serving cell configuration. In some examples, a change to the serving cell configuration can change the searcher capability of UE 110. For example, if FR1 carriers (e.g., for carrier aggregation or dual connectivity) are configured, UE 110 can indicate support for 3 searcher capability. If another FR2 serving cell is added, the memory demands can increase, and UE 110 may no longer support 3 searchers for the new configuration. In such an example, UE 110 can update the capability to be a 2-searcher capability.

[0067] Fig. 4 is a diagram of an example of process 400 for UE capability design for multiple searcher based RRM according to one or more implementations described herein.Process 400 can be an example of UE 110 determining searcher capability based on MO list 144905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)configuration and indicating the searcher capability to a RAN 220. In some examples, the MO list configuration can be updated, and UE 110 can update search capability accordingly. As shown, process 400 can be performed by UE 110 and RAN 220. Operations described as being performed by UE 110 can be performed, at least in part, by baseband circuitry of UE 110. RAN 220 can be implemented by base station or another type of network access point. Some or all of process 300 can be performed by one or more other systems or devices, including one or more of the devices of Figs. 1 and 2.

[0068] Additionally, process 400 can include one or more fewer, additional, differently ordered, and / or arranged operations than those shown in Fig. 4. Some or all of the operations of process 400 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 400. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Figure 4.

[0069] Process 400 can include indicating an MO list configuration (at 405). For example, RAN 220 can transmit MO list configuration to UE 110. MO list configuration can provide a list of objects for UE 110 to perform measurements. MOs can indicate frequency, time, and subcarrier spacings of signals to be measurements.

[0070] Process 400 can include determining which MOs are gapless-based (at 410). For example, UE 110 can determine which, if any, MOs of the configured list are gapless-based. In some examples, gapless-based MOs may be associated with FR1 carriers.

[0071] Process 400 can include determining memory capability (at 415). For example, UE 110 can determine how may searchers the memory of UE 110 can support for the identified gapless MOs. When the memory of UE 110 can support 3 searchers for the gapless MOs, UE 110 can support a 3 searcher capability. Similarly, when the memory of UE 110 may not support 3 searchers, UE 110 can support a 2 searcher capability.

[0072] Process 400 can include indicating searcher capability (at 420). For example, if UE 110 determines support for 3 searchers, UE 110 can indicate a 3 searcher capability to RAN 220. In such example, UE 110 memory can support for 3 searchers for simultaneous measurements.

[0073] Process 400 can include indicating an MO list reconfiguration (at 425). In some examples, RAN 220 can transmit an MO list reconfiguration to UE 110. For example, the reconfiguration can add MOs.

[0074] Process 400 can include re-checking searcher capability (at 430). For example, UE 110 re-check searcher capability based on the MO list reconfiguration. For example, if the MO154905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)list adds MOs, UE 110 may recheck for gapless based MOs (e.g., FR1 and FR2 gapless-based MOs) and the capability of UE 110 support additional MOs.

[0075] Process 400 can include indicating an updated searcher capability (at 435). For example, UE 110 can indicate to RAN 220 an update of searcher capability. For example, UE 110 can determine that additional MOs exceed the memory capability and indicate that UE 110 no longer supports a 3 searcher capability for measurements. In some examples, UE 110 can indicate that UE 110 does support a 2 searcher capability.

[0076] Fig. 5 is a diagram of an example of sequence flow 500 for UE capability design for multiple searcher based RRM according to one or more implementations described herein.Sequence flow 500 can be an example of UE (e.g., UE 110 as described with reference to FIG.2). determining allocation of searchers, such as 3 searchers. Sequence flow 500 can be performed by a UE, or another device. Operations described as being performed by the UE can be performed, at least in part, by baseband circuitry of the UE.

[0077] Additionally, sequence flow 500 can include one or more fewer, additional, differently ordered, and / or arranged operations than those shown in Fig. 4. Some or all of the operations of sequence flow 500 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of sequence flow 500. As such, the techniques described herein are not limited to the number, sequence, arrangement, timing, etc., of the operations or processes depicted in Figure 5.

[0078] In some examples, such as dual connectivity (DC), can include a master cell group (MCG) and a secondary cell group (SCG). The SCG can include primary cells (PCells), secondary cells (SCells), and primary secondary cells (PSCells) (e.g., special cells). UE can allocate searchers to configured cells based on cells configuration and scaling factors. An example of a scaling factor is a carrier specific scaling factor (CSSF).

[0079] The UE can support multiple searchers, such as 3 searchers. The UE can allocate searcher resources among target carriers for measurements. The PCell can have one allocated searcher. The scaling factor (e.g., CSSF) for primary component carrier (PCC) measurements can also be one (e.g., scaling factor = 1). For example, if the UE supports 3 searchers, the 1stsearcher is allocated to the PCell.

[0080] Next, the UE can determine whether the PSCell is configured and further allocate the searchers (at 510). When the PSCell is configured (510= YES), 1 searcher is allocated to the PSCell with a scaling factor of 1 for PCC measurements (at 515). For example, if the UE supports 3 searchers, the PSCell is allocated the 2ndsearcher.

[0081] The remaining 3rdsearcher is allocated based on secondary component carriers 164905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)(SCCs). In some examples, FR2 SCC measurements can be configured for a neighbor cell. The UE determines whether FR2 SCC measurements are configured for the neighbor cell (at 520, YES-Option 1). When configured, the FR2 SCC measurements are allocated 50% of the 3rdsearcher (at 525, 520= YES). The other SCCs are allocated the remaining 50% of the 3rdsearcher (at 530). When FR2 SCC measurements are not configured for the neighbor cell, all SCCs are assigned the 3rdsearcher (at 535, 520=NO).

[0082] In some examples, the UE can determine whether a high priority SCC is configured (at 540, YES-OPTION 2). When the high priority SCC is configured (540=YES), the SCC with high priority is allocated 50% of the 3rdsearcher, with a scaling factor of 2 multiplied by the high priority SCC (e.g., 2*high priority SCC). When the high priority SCC is not configured (540=NO), then the searchers are allocated based on the SCCs, including the configuration of the FR2 SCC measurement with the neighbor cell configuration (at 520).

[0083] In some examples, the PSCell is not configured (510=NO). There may be multiple ways the searchers may be allocation (e.g., NO-OPTION 1, NO-OPTION 2). For example, when the PSCell is not configured, searcher allocation cab be determined based on the FR2 SCC measurements with the neighbor cell configuration (at 550, 510=NO-OPTION 1). When the FR2 SCC measurements with the neighbor cell are configured, the FR2 SCC is allocated 1 searcher, which may be the 2ndsearcher. The scaling factor can be dependent on the FR2 SCC (scaling factor = FR2 SCC with neighbor for FR2 neighbor cell measurement) (at 555). All other SCCs can be allocated the 3rdsearcher (at 560). The other SCCs can include FR1 and FR2, and the scaling factor can be dependent on the number of SCCs (e.g., scaling factor = SCC number for other FR1 and FR2 SCC measurement).

[0084] When the FR2 SCC measurements with the neighbor cell are not configured (at 565, 550=NO), all the SCCs including FR2 are allocated 1 searcher and all the SCCs including FR1 are allocated 1 searcher, respectively (scaling factor = SCC number for all FR1 and FR2 SCC measurement). The searchers allocated to the FR1 and FR2 SCCs can be the 2ndand 3rdsearchers. The scaling factors are based on the SCC numbers (scaling factor for FR1 SCC= SCC number for all FR1 SCC measurement, scaling factor FR2 SCC= SCC number for all FR2 SCC measurement). In some examples, PCC, FR1 SCC, FR2 SCC can be measured simultaneously.

[0085] In some examples, when the PSCell is not configured, a high priority SCC can be configured (at 570, when 510-NO-OPTION 2). When a high priority SCC is configured by the network, the SCC with high priority can be allocated the 2ndsearcher, with a scaling factor of the high priory SCC number (scaling factor = high priority SCC number) (at 575, 750= YES). All other SCCs will use the 3rd searcher (at 580). When a high priority SCC is not configured by the 174905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)network, then the searcher allocation is determined by the SCC configuration of the FR2 SCCs and other SCCs (at 550, 570=NO).

[0086] Figure 6 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the device 600 can include application circuitry 602, baseband circuitry 604, RF circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. In some implementations, device 600 can include fewer elements (e.g., a RAN node may not utilize application circuitry 602, and can instead include a processor / controller to process data received from a core network. In some implementations, device600 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 600, etc.), or input / output (VO) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for cloud-RAN (C-RAN) implementations).

[0087] The application circuitry 602 can include one or more application processors. For example, the application circuitry 602 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 600. In some implementations, processors of application circuitry 602 can process data packets received from a core network.

[0088] The baseband circuitry 604 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 604 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 606 and to generate baseband signals for a transmit signal path of RF circuitry 606. Baseband circuitry 604 can interface with application circuitry 602 for generation and processing of the baseband signals and for controlling operations of RF circuitry 606. For example, in some implementations, baseband circuitry 604 can include a 3G baseband processor 604A, a 4G baseband processor 604B, a 5G baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, 7G, etc.). Baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) can handle various radio control functions that enable communication with 184905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)one or more radio networks via RF circuitry 606. In other implementations, some or all of the functionality of baseband processors 604 A-D can be included in modules stored in memory 804G and executed via a central processing unit (CPU) 804E. The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of baseband circuitry 604 can include Fast-Fourier Transform (FFT), precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of baseband circuitry 604 can include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.

[0089] In some implementations, memory 604G can receive and / or store information and instructions for enabling UE 210, and / or one or more components thereof, to support UE capability for multiple searchers. In some examples, UE 210 can measure carriers simultaneously. The number of carriers UE 210 can measure simultaneously can be indicated as a searcher capability. UE 210 can receive SSBs from a network device and determine and indicate a searcher capability. For example, the information and instructions can cause and / or enable UE 210 to indicate a searcher capability to the network device. The searcher capability can be based on serving cell configuration changes, measurement object configuration changes, band combinations, frequency ranges, and other factors. For example, UE 210 can indicate a 2 searcher capability or a 3 searcher capability. These and many other features and examples are described herein.

[0090] In some implementations, the baseband circuitry 604 can include one or more audio digital signal processor(s) (DSP) 604F. The audio DSPs 604F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 can be implemented together such as, for example, on a system on a chip (SOC).

[0091] In some implementations, the baseband circuitry 604 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 604 can support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks 194905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)(WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

[0092] RF circuitry 606 can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, RF circuitry 806 can include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 606 can include a receive signal path which can include circuitry to down-convert RF signals received from FEM circuitry 608 and provide baseband signals to baseband circuitry 604. RF circuitry 606 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by baseband circuitry 604 and provide RF output signals to FEM circuitry 608 for transmission.

[0093] In some implementations, the receive signal path of the RF circuitry 606 can include mixer circuitry 606A, amplifier circuitry 606B and filter circuitry 606C. In some implementations, the transmit signal path of RF circuitry 606 can include filter circuitry 606C and mixer circuitry 606 A. RF circuitry 606 can also include synthesizer circuitry 606D for synthesizing a frequency for use by mixer circuitry 606A of the receive signal path and the transmit signal path. In some implementations, mixer circuitry 606A of the receive signal path can be configured to down-convert RF signals received from FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606D. Amplifier circuitry 606B can be configured to amplify the down-converted signals and filter circuitry 606C can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to baseband circuitry 604 for further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this may not be a requirement. In some implementations, mixer circuitry 606A of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.

[0094] In some implementations, the mixer circuitry 606A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606D to generate RF output signals for the FEM circuitry 608. The baseband signals can be provided by the baseband circuitry 604 and can be filtered by filter circuitry 606C.

[0095] In some implementations, mixer circuitry 606A of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by 204905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)synthesizer circuitry 606D to generate RF output signals for FEM circuitry 608. The baseband signals can be provided by baseband circuitry 604 and can be filtered by filter circuitry 606C. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can include two or more mixers and can be arranged for image rejection. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, mixer circuitry 606A of the receive signal path and mixer circuitry 606A of the transmit signal path can be configured for super-heterodyne operation.

[0096] In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, RF circuitry 606 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and baseband circuitry 604 can include a digital baseband interface to communicate with RF circuitry 606.

[0097] In some dual-mode implementations, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect. In some implementations, the synthesizer circuitry 606D can be a fractional-N synthesizer or a fractional N / N+l synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitry 606D can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0098] Synthesizer circuitry 606D can be configured to synthesize an output frequency for use by mixer circuitry 606 A of RF circuitry 606 based on a frequency input and a divider control input. In some implementations, synthesizer circuitry 606D can be a fractional N / N+l synthesizer. In some implementations, frequency input can be provided by a voltage-controlled oscillator (VCO). Divider control input can be provided by either baseband circuitry 604 or the applications circuitry 602 depending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry 602.

[0099] Synthesizer circuitry 606D of RF circuitry 606 can include a divider, a delay-locked 214905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)loop (DLL), a multiplexer, and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD), and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0100] In some implementations, synthesizer circuitry 606D can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some implementations, RF circuitry 606 can include an in-phase / quadrature (I / Q) / polar converter.

[0101] FEM circuitry 608 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to RF circuitry 606 for further processing. FEM circuitry 608 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various implementations, the amplification through the transmit or receive signal paths can be done solely in RF circuitry 606, solely in FEM circuitry 608, or in both RF circuitry 606 and FEM circuitry 608.

[0102] In some implementations, the FEM circuitry 608 can include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[0103] In some implementations, the PMC 612 can manage power provided to the baseband circuitry 604. In particular, PMC 612 can control power-source selection, voltage scaling, battery 224905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)charging, or direct current (DC) to DC (DC-to-DC) conversion. PMC 612 can often be included when device 600 is capable of being powered by a battery, for example, when device 600 is included in a UE. PMC 612 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0104] While Fig. 6 shows PMC 612 coupled only with the baseband circuitry 604, in other implementations, PMC 612 can be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM circuitry 608.

[0105] In some implementations, the PMC 612 can control, or otherwise be part of, various power saving mechanisms of device 600. For example, if device 600 is in an RRC Connected state, where device 600 is still connected to the RAN node as device 600 expects to receive traffic shortly, then device 600 can enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, device 600 can power down for brief intervals of time and thus save power.

[0106] If there is no data traffic activity for an extended period of time, then device 600 can transition off to an RRC Idle state, where device 600 disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. Device 600 can go into a very low power state and device 600 can perform paging where again device 600 periodically can wake up to listen to the network and then power down again. Device 600 may not receive data in this state; in order to receive data, device 600 can transition back to RRC Connected state.

[0107] An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device 600 can be unreachable to the network and can power down completely. Any data sent during this time can incur a large delay and device 600 can assume the delay is acceptable.

[0108] Processors of application circuitry 602 and processors of baseband circuitry 604 can be used to execute elements of one or more instances of a protocol stack. For example, processors of baseband circuitry 604, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of baseband circuitry 604 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a radio resource control layer. As referred to herein, Layer 2 can comprise a medium access control layer, a radio link control layer, and a packet data convergence protocol layer, described in further detail below. As referred to herein, Layer 1 can 234905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)comprise a physical layer of a UE / RAN node.

[0109] Figure 7 is a diagram of example interfaces 700 of baseband circuitry according to one or more implementations described herein. One or more components or features of example interfaces 700 can correspond to one or more components or features described above or elsewhere. Baseband circuitry 704 can comprise processors 704A, 704B, 704C, 704D, and 704E and a memory 704G utilized by said processors. Each of the processors 704A, 704B, 704C, 704D, and 704E can include a memory interface, 706A, 706B, 706C, 706D, and 706E, respectively, to send / receive data to / from the memory 704G. Baseband circuitry can be a component of a UE and / or another type of device or system capable of transmitting and / or receiving wireless signals.

[0110] In some implementations, memory 704G can receive, store, and / or provide information and instructions for UE capability for multiple searcher based RRM. A UE can determine searcher capability, indicate searcher capability, and update searcher capability. A UE, or another device, can receive SSBs from a network device, and determine and indicate a searcher capability. The searcher capability can be based on serving cell configuration changes, measurement object configuration changes, band combinations, frequency ranges, and other factors. For example, UE 210 can indicate a 2 searcher capability or a 3 searcher capability. These and many other features and examples are described herein.[OHl] Baseband circuitry 704 can further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 712 (e.g., an interface to send / receive data to / from memory external to baseband circuitry 704), an application circuitry interface714 (e.g., an interface to send / receive data to / from the application circuitry as described herein), an RF circuitry interface 716, a wireless hardware connectivity interface 718 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send / receive power or control signals to / from a PMC)

[0112] Figure 8 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Fig. 8 shows a diagrammatic representation of hardware resources 800 including one or more processors 810 (or processor cores), one or more memory / storage devices 820, and one or more communication resources 830, each of which can be communicatively coupled via a bus 840. For implementations where node244905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)virtualization or network function virtualization is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices / sub-slices to utilize hardware resources 800. Hardware resources 800 can interact with hypervisor 802. For example, hypervisor 802 can schedule or otherwise manage hardware resource 800.

[0113] The processors 810 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processor 812 and a processor 814.

[0114] The memory / storage devices 820 can include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 820 can include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[0115] In some implementations, memory / storage devices 820 receive and / or store information and instructions 855 for UE capability design for multiple searchers for RRM. A UE, or another device, can receive SSBs from a network device, and determine and indicate a searcher capability. The searcher capability can be based on serving cell configuration changes, measurement object configuration changes, band combinations, frequency ranges, and other factors. For example, UE 210 can indicate a 2 searcher capability or a 3 searcher capability. These and many other features and examples are discussed herein.

[0116] Communication resources 830 can include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 via a network808. For example, communication resources 830 can include wired communication components (e.g., for coupling via a universal serial bus), cellular communication components, near field communication components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[0117] Instructions 850A, 850B, 850C, 850D, and / or 850E can comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of processors 810 to perform any one or more of the methodologies discussed herein. Instructions 850 can reside, completely or partially, within at least one of processors 810 (e.g., within a cache memory), memory / storage devices 820, or any suitable combination thereof. Furthermore, any 254905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)portion of instructions 850A-E can be transferred to hardware resources 800 from any combination of peripheral devices 804 or databases 806. Accordingly, memory of processors 810, memory / storage devices 820, peripheral devices 804, and databases 806 are examples of computer-readable and machine-readable media.

[0118] Figure 9 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein. Process 900 can be implemented by UE 210, baseband circuitry (e.g., baseband circuitry of UE 210), or both. In some implementations, some or all of process 900 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 900 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 9. In some implementations, some or all of the operations of process 900 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 900. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 9.

[0119] Process 900 can include receiving at least one SSB (block 910). Process 900 can include determining, based on the at least one SSB, a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for RRM (block 920). Process 900 can include transmitting a first searcher capability comprising an indication of the searcher number supported by the UE (block 930).

[0120] Figure 10 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein. Process 1000 can be implemented by base station (e.g., gNB, network device, etc.), baseband circuitry of the base station, or a UE 210. In some implementations, some or all of process 1000 can be performed by one or more other systems or devices, including one or more of the devices of Fig.2. Additionally, process 1000 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 10. In some implementations, some or all of the operations of process 1000 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1000. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 10.

[0121] Process 1000 can include transmitting, to a UE, at least one SSB (block 1010).Process 1000 can include receiving, from the UE and based on the at least one SSB, a first searcher capability indicating a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for RRM (block 264905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)1020).

[0122] Figure 11 is a diagram of an example process for UE capability design for multiple searcher based RRM according to one or more implementations described herein. Process 1100 can be implemented by baseband circuitry, such as baseband circuitry of UE 210. In some implementations, some or all of process 1100 can be performed by one or more other systems or devices, including one or more of the devices of Fig. 2. Additionally, process 1100 can include one or more fewer, additional, differently ordered and / or arranged operations than those shown in Fig. 11. In some implementations, some or all of the operations of process 1100 can be performed independently, successively, simultaneously, etc., of one or more of the other operations of process 1100. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in Fig. 11.

[0123] Process 1100 can include decoding at least one SSB (block 1110). Process 1100 can include determine, based on the at least one SSB, a searcher number supported by a user equipment (UE), the searcher number comprising a number of carriers the UE has is capable of measuring simultaneously for RRM (block 1120). Process 1100 can include outputting a first searcher capability comprising an indication of the searcher number supported by the UE (block 1130).

[0124] Examples and / or implementations herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor , etc.) with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.

[0125] In example 1, which can also include one or more of the examples described herein, a UE (e.g., UE 210) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UE 210 to: receive at least one synchronization signal block (SSB); determine, based on the at least one SSB, a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for radio resource management (RRM); and transmit a first searcher capability comprising an indication of the searcher number supported by the UE.

[0126] In example 2, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: receive a serving cell configuration comprising an indication of a serving cell to communicate with the UE; update the 274905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)first searcher capability to a second searcher capability according to the serving cell configuration, wherein the second searcher capability indicates a different number of carriers that is different than the number of carriers of the first searcher capability; and transmit the second searcher capability.

[0127] In example 3, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: receive a measurement object configuration comprising a measurement object list; and determine the first searcher capability according to the measurement object configuration.

[0128] In example 4, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: determine which measurement objects of the measurement object list are gapless-based measurement objects; determine that the memory is capable of supporting multiple searchers for the gapless-based measurement objects; and determine the first searcher capability according to the determination that the memory is capable of supporting multiple searchers.

[0129] In example 5, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: receive a reconfigured measurement object configuration that reconfigures the measurement object list; and determine whether the memory can support the first searcher capability for the reconfigured measurement object list.

[0130] In example 6, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: update, based on a determination that the memory cannot support the first searcher capability for the reconfigured measurement object list, the first searcher capability to a second searcher capability, wherein the first searcher capability indicates that the UE cannot support the reconfigured measurement object list; and transmit the second searcher capability.

[0131] In example 7, which can also include one or more of the examples described herein, wherein the first searcher capability comprises an indication of at least one supported band combination, at least one unsupported band combination, or both.

[0132] In example 8, which can also include one or more of the examples described herein, wherein the first searcher capability comprises an indication of at least one supported band, at least one unsupported band, or both.

[0133] In example 9, which can also include one or more of the examples described herein, wherein the first searcher capability comprises an indication of at least one supported frequency range, at least one unsupported frequency range, or both.284905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)

[0134] In example 10, which can also include one or more of the examples described herein, wherein the first searcher capability comprises an indication of at least one supported frequency range combination, at least one unsupported frequency range combination, or both.

[0135] In example 11, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: allocate a first searcher of the first searcher capability to a primary cell; allocate a second searcher of the first searcher capability to a primary secondary cell; and allocate a third searcher of the first searcher capability to at least one secondary component carrier.

[0136] In example 12, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UE 210 to: allocate a first searcher of the first searcher capability to a primary cell; and allocate a second searcher and a third searcher of the first searcher capability to at least one secondary component carrier.

[0137] In example 13, which can also include one or more of the examples described herein, wherein the number of carriers of the first searcher capability is based on a periodicity satisfying a periodicity threshold.

[0138] In example 14, which can also include one or more of the examples described herein, a base station (e.g., gNB, network entity, network device) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the base station to: transmit, to a user equipment (UE), at least one synchronization signal block (SSB); and receive, from the UE and based on the at least one SSB, a first searcher capability indicating a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for radio resource management (RRM).

[0139] In example 15, which can also include one or more of the examples described herein, the one or more processors are further configured to cause the base station to: transmit, to the UE, a serving cell configuration comprising an indication of a serving cell to communicate with the UE; and receive, from the UE and based on the serving cell configuration, a second searcher capability comprising an updated first searcher capability, wherein the second searcher capability indicates a different number of carriers that is different than the number of carriers of the first searcher capability.

[0140] In example 16, which can also include one or more of the examples described herein, the one or more processors are further configured to cause the base station to: transmit a measurement object configuration comprising a measurement object list; and receive the first searcher capability according to the measurement object configuration.

[0141] In example 17, which can also include one or more of the examples described herein,294905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)the one or more processors are further configured to cause the base station to: receive the first searcher capability according to a capability of a memory of the UE to support multiple searchers for gapless-based measurement objects of the measurement object list.

[0142] In example 18, which can also include one or more of the examples described herein, the one or more processors are further configured to cause the base station to: transmit a reconfigured measurement object configuration that reconfigures the measurement object list.

[0143] In example 19, which can also include one or more of the examples described herein, the one or more processors are further configured to cause the base station to: receive from the UE and based on the reconfigured measurement object configuration, a second searcher capability comprising an updated first searcher capability, wherein the first searcher capability indicates that the UE cannot support the reconfigured measurement object list.

[0144] In example 20, which can also include one or more of the examples described herein, baseband circuitry (e.g., baseband circuitry of a UE) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to: decode at least one synchronization signal block (SSB); determine, based on the at least one SSB, a searcher number supported by a user equipment (UE), the searcher number comprising a number of carriers the UE has is capable of measuring simultaneously for radio resource management (RRM); and output a first searcher capability comprising an indication of the searcher number supported by the UE.

[0145] The examples discussed above also extend to method, computer-readable medium, and means-plus-function claims and implementations, any of which can include one or more of the features or operations of any one or combination of the examples mentioned above.

[0146] The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.

[0147] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or 304905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

[0148] In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.

[0149] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.

[0150] 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 to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.314905-9995-6614, v. 2

Claims

Attorney Docket No.: 106842257540 (P70733WO1)CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising:a memory; andone or more processors configured to, when executing instructions stored in the memory, cause the UE to:receive at least one synchronization signal block (SSB);determine, based on the at least one SSB, a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for radio resource management (RRM); andtransmit a first searcher capability comprising an indication of the searcher number supported by the UE.

2. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:receive a serving cell configuration comprising an indication of a serving cell to communicate with the UE;update the first searcher capability to a second searcher capability according to the serving cell configuration, wherein the second searcher capability indicates a different number of carriers than the number of carriers of the first searcher capability; andtransmit the second searcher capability.

3. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:receive a measurement object configuration comprising a measurement object list; and determine the first searcher capability according to the measurement object configuration.

4. The UE of claim 3, wherein the one or more processors are further configured to cause the UE to:determine which measurement objects of the measurement object list are gapless-based measurement objects;determine that the memory is capable of supporting multiple searchers for the gapless-based measurement objects; and324905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)determine the first searcher capability according to the determination that the memory is capable of supporting multiple searchers.

5. The UE of claim 4, wherein the one or more processors are further configured to cause the UE to:receive a reconfigured measurement object configuration that reconfigures the measurement object list; anddetermine whether the memory can support the first searcher capability for the reconfigured measurement object list.

6. The UE of claim 5, wherein the one or more processors are further configured to cause the UE to:update, based on a determination that the memory cannot support the first searcher capability for the reconfigured measurement object list, the first searcher capability to a second searcher capability, wherein the first searcher capability indicates that the UE cannot support the reconfigured measurement object list; andtransmit the second searcher capability.

7. The UE of claim 1, wherein the first searcher capability comprises an indication of at least one supported band combination, at least one unsupported band combination, or both.

8. The UE of claim 1, wherein the first searcher capability comprises an indication of at least one supported band, at least one unsupported band, or both.

9. The UE of claim 1, wherein the first searcher capability comprises an indication of at least one supported frequency range, at least one unsupported frequency range, or both.

10. The UE of claim 1, wherein the first searcher capability comprises an indication of at least one supported frequency range combination, at least one unsupported frequency range combination, or both.

11. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:allocate a first searcher of the first searcher capability to a primary cell;334905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)allocate a second searcher of the first searcher capability to a primary secondary cell; and allocate a third searcher of the first searcher capability to at least one secondary component carrier.

12. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:allocate a first searcher of the first searcher capability to a primary cell; andallocate a second searcher and a third searcher of the first searcher capability to at least one secondary component carrier.

13. The UE of claim 1, wherein the number of carriers of the first searcher capability is based on a periodicity satisfying a periodicity threshold.

14. A base station, comprising:a memory; andone or more processors configured to, when executing instructions stored in the memory, cause the base station to:transmit, to a user equipment (UE), at least one synchronization signal block (SSB); and receive, from the UE and based on the at least one SSB, a first searcher capability indicating a searcher number supported by the UE, the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for radio resource management (RRM).

15. The base station of claim 14, wherein the one or more processors are further configured to cause the base station to:transmit, to the UE, a serving cell configuration comprising an indication of a serving cell to communicate with the UE; andreceive, from the UE and based on the serving cell configuration, a second searcher capability comprising an updated first searcher capability, wherein the second searcher capability indicates a different number of carriers than the number of carriers of the first searcher capability.

16. The base station of claim 15, wherein the one or more processors are further configured to cause the base station to:344905-9995-6614, v. 2Attorney Docket No.: 106842257540 (P70733WO1)transmit a measurement object configuration comprising a measurement object list; and receive the first searcher capability according to the measurement object configuration.

17. The base station of claim 16, wherein the one or more processors are further configured to cause the base station to:receive the first searcher capability according to a capability of a memory of the UE to support multiple searchers for gapless-based measurement objects of the measurement object list.

18. The base station of claim 17, wherein the one or more processors are further configured to cause the base station to:transmit a reconfigured measurement object configuration that reconfigures the measurement object list.

19. The base station of claim 18, wherein the one or more processors are further executable to cause the base station to:receive, from the UE and based on the reconfigured measurement object configuration, a second searcher capability comprising an updated first searcher capability, wherein the first searcher capability indicates that the UE cannot support the reconfigured measurement object list.

20. Baseband circuitry, comprising:a memory; andone or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to:decode at least one synchronization signal block (SSB);determine, based on the at least one SSB, a searcher number supported by a user equipment (UE), the searcher number comprising a number of carriers the UE is capable of measuring simultaneously for radio resource management (RRM); andoutput a first searcher capability comprising an indication of the searcher number supported by the UE.354905-9995-6614, v. 2

Images