Inter-RAT LTE measurement without measurement gap

Abstract

An apparatus of a user equipment (UE) configured to decode a high priority flag received from a network, the high priority flag indicating to prioritize measurements of one or more LTE component carriers (LTE CCs) over measurements of new radio (NR) secondary component carriers (NR SCCs); allocate a first searcher resource for measurements of a new radio primary component carrier (NR PCC); allocate a first portion of a second searcher resource for measurements of the LTE CCs and a second portion of the second searcher resource for measurements of one or more NR SCCs based on the high priority flag, wherein the first portion is greater than or equal to the second portion; perform measurements of the LTE CCs using the first portion of the second searcher resource without using a measurement gap; and perform measurements of the NR SCCs using the second portion of the second searcher resource.

Description

Technical Field

[0001] Embodiments of the present invention relate to wireless communication, including apparatus, systems, and methods for performing Long Term Evolution (LTE) measurements between Radio Access Technologies (RATs) without measurement gaps by a User Equipment (UE) in a cellular communication network. Background Technology

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices, such as smartphones and tablets, have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now offer access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these functionalities.

[0003] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their subscriber base. LTE was first proposed in 2004 and standardized for the first time in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand from wireless network operators to support higher capacity for a higher density of mobile broadband users has also increased. Research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.

[0004] 5G-NR (also known as NR for short) offers higher capacity for higher density mobile broadband users compared to LTE, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Additionally, NR allows for more flexible UE scheduling compared to current LTE. Therefore, ongoing development of 5G-NR is underway to take advantage of the potentially higher throughput at higher frequencies. Summary of the Invention

[0005] The implementation relates to wireless communication, and more specifically to an apparatus, system, and method for a user equipment (UE) including one or more processors coupled to a memory, the one or more processors being configured to: decode a high-priority flag received from a network, the high-priority flag indicating priority for measuring one or more LTE component carriers (LTE CCs) relative to measurements of one or more New Radio (NR) Secondary Component Carriers (NR SCCs); allocate a first searcher resource for measurements of one or more New Radio Primary Component Carriers (NR PCCs); allocate a first portion of a second searcher resource for measurements of one or more LTE CCs and a second portion of the second searcher resource for measurements of one or more NR SCCs based on the high-priority flag, wherein the first portion is greater than or equal to the second portion; perform measurements of one or more LTE CCs using the first portion of the second searcher resource without using measurement gaps; and perform measurements of one or more NR SCCs using the second portion of the second searcher resource.

[0006] Other embodiments relate to an apparatus for a base station (e.g., a base station) including one or more processors coupled to a memory, the one or more processors being configured to: determine, for a user equipment (UE), prioritize measurements of one or more Long Term Evolution (LTE) component carriers (LTE CCs) relative to measurements of one or more New Radio (NR) secondary component carriers (NR SCCs); encode a high-priority flag to transmit to the UE, the high-priority flag indicating that measurements of one or more LTE CCs are prioritized relative to measurements of one or more NR SCCs; and encode configuration information for measurements of one or more LTE CCs and measurements of one or more NR SCCs to transmit to the UE, wherein the configuration information includes: an indication of a first searcher resource for measurements of one or more New Radio Primary Component Carriers (NR PCCs), and an indication of a second searcher resource for measurements of one or more LTE CCs and measurements of one or more NR SCCs, wherein based on the high-priority flag, a first portion of the second searcher resource is allocated for measurements of one or more LTE CCs and a second portion of the second searcher resource is allocated for measurements of one or more NR SCCs, and wherein the first portion is greater than or equal to the second portion.

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

[0008] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the features described above are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0009] A better understanding of the subject matter can be obtained by considering the following detailed description of various embodiments in conjunction with the accompanying drawings, in which: Figure 1A Example wireless communication systems according to some implementation schemes are illustrated.

[0010] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are illustrated.

[0011] Figure 2 Example block diagrams of base stations according to some implementation schemes are shown.

[0012] Figure 3 Example block diagrams of servers according to some implementation schemes are shown.

[0013] Figure 4 Exemplary block diagrams of a UE according to some implementation schemes are shown.

[0014] Figure 5 Exemplary block diagrams of cellular communication circuits according to some implementation schemes are shown.

[0015] Figure 6 Examples of baseband processor architectures for UEs according to some implementation schemes are illustrated.

[0016] Figure 7 Example block diagrams illustrating the interface of a baseband circuit according to some implementation schemes are shown.

[0017] Figure 8 Example block diagrams illustrate the UE-initiated beam reporting (UIBR) process using configured uplink permission (UL) according to some implementation schemes.

[0018] Figure 9An example timing diagram illustrating the signaling exchange between a user equipment (UE) and a base station for a UE-initiated beam reporting (UIBR) process using configured permission (UL) according to some implementation schemes.

[0019] Figure 10 An example illustration is shown of a UE-initiated beam report (UIBR) procedure retransmission according to some implementation schemes.

[0020] Figure 11 An example illustration is shown of how searcher resources are allocated to LTE and NR measurements based on high-priority flags according to some implementation schemes.

[0021] Figure 12 Example tables are provided illustrating CSSF (Carrier Specific Scaling Factor) values ​​for different scenarios and frequency ranges according to some implementation schemes.

[0022] Figure 13 Another example illustration illustrates the allocation of searcher resources for LTE and NR measurements based on high-priority flags according to some implementation schemes.

[0023] Figure 14 Another example table illustrates CSSF (carrier-specific scaling factor) values ​​for different scenarios and frequency ranges according to some implementation schemes.

[0024] Figure 15 An example of the abstract syntax mark-1 (ASN.1) code for the measurement configuration (MeasConfig) information element is shown according to some implementation schemes.

[0025] Figure 16 Example illustrations are provided of the allocation of searcher resources for LTE and NR measurements according to some implementation schemes, including a dedicated searcher for LTE measurements.

[0026] Figure 17 Example tables illustrate CSSF (Carrier Specific Scaling Factor) values ​​for dedicated searchers used for LTE measurements in different scenarios and frequency ranges, based on considerations of some implementation schemes.

[0027] Figure 18 A flowchart illustrating a method for performing Long Term Evolution (LTE) measurements between Radio Access Technologies (RATs) without measurement gaps, according to some implementation schemes, is provided.

[0028] Although the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit one to the specific forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0029] the term The following is a glossary of terms used in this disclosure: Memory media—any of various types of nontransitory memory devices or storage devices. The term "memory media" is intended to include mounting media, such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory; magnetic media, such as hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter example, the second computer system may provide program instructions to the first computer for execution. The term "memory media" may include two or more memory media residing in different locations in different computer systems connected via, for example, a network. Memory media may store program instructions (e.g., embodied in a computer program) that can be executed by one or more processors.

[0030] Carrier media—such as memory media as described above, and physical transmission media such as buses, networks, and / or other physical transmission media that transmit signals such as electrical signals, electromagnetic signals, or digital signals.

[0031] Programmable hardware elements encompass a variety of hardware devices, which include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can range from fine-grained (combinational logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "reconfigurable logic units."

[0032] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0033] User equipment (UE) (or “UE device”) — any of various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). ™ Based on Android ™ Telephones), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ ), laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or combination of devices) that is easily transportable by the user and capable of wireless communication.

[0034] Base station—The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

[0035] A processing element (or processor) is a component or combination of components capable of performing the functions of a device such as a user equipment or cellular network device. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0036] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on the wireless protocol, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, channel bandwidth can be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, for example, different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0037] Frequency band—The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0038] Automatic—means that an action or operation is performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct specification or execution of the action or operation through user input. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system will update the form in response to the user's actions. The form can be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0039] Approximately—means a value close to the correct or precise value. For example, approximately could mean a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can be application-dependent. For example, in some implementations, “approximately” may mean within 0.1% of a specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or settings of the specific application.

[0040] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0041] The legacy system—the 3rd Generation Partnership Project (3GPP) develops specifications that define 3GPP technologies. 3GPP specifications cover cellular telecommunications technologies, including radio access, core network, and service capabilities, providing a complete system description for mobile telecommunications. 3GPP uses a system of parallel “releases,” which provide developers with a stable platform for implementing features at a given point and then allow for the addition of new functionality in subsequent releases. Release 17 was released in 2022. At the time of this disclosure, Release 18 (Rel-18) is forthcoming, as its specifications are largely finalized. Therefore, specific implementations and concepts compatible with Rel-18 or earlier releases are sometimes referred to herein as “legacy.” One or more implementations of this disclosure may be adopted in future releases (e.g., Release 19).

[0042] rN — As used herein, when used in conjunction with an Information Element (IE), rN refers to a UE that supports 3GPP version N. For example, r18 indicates a UE that supports 3GPP version 18. UEs that support versions greater than N may also support 3GPP version N. UEs that do not support 3GPP version N may not support IEs including rN.

[0043] Various components can be described as being "configured" to perform one or more tasks. In this context, "configured" is a broad expression that generally means "having a structure" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can be a broad expression that generally means "having a circuit" that performs one or more tasks during operation. Therefore, a component can be configured to perform a task even when it is not currently switched on. Generally, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0044] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0045] The example implementation can be further understood by referring to the following description and related figures, in which the same elements have the same reference numerals. The example implementation involves a UE-initiated beam reporting (UIBR) performed by a user equipment (UE) for frequency range two (FR2) using configured authorized (UL) resources.

[0046] Example implementations are described regarding communication between a base station (e.g., a next-generation Node B (gNB)) and a user equipment (UE). However, references to gNB or UE are provided for illustrative purposes only. The example implementations can be used with any electronic component that establishes a connection to the network and is configured with hardware, software, and / or firmware to provide and support inter-Radio Access Technology (RAT) Long Term Evolution (LTE) measurements performed by the user equipment (UE) without measurement gaps. Therefore, gNB or UE as described herein is used to refer to any suitable type of electronic component.

[0047] An example implementation is also described with reference to a fifth-generation (5G) new radio (NR) network that can configure the UE to perform inter-RAT LTE measurements without measurement gaps. However, the reference to the 5G NR network is provided for illustrative purposes only. The example implementation can be used with any suitable type of network.

[0048] Throughout this description, various information elements (IEs) are referred to by specific names. It should be understood that these names are merely examples, and the IEs carrying the information referenced throughout this description may be referenced by various entities under other names.

[0049] Figure 1A and Figure 1B Communication system Figure 1A A simplified example wireless communication system according to some implementation schemes is illustrated. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0050] As shown in the figure, the example wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N, etc., via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0051] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0052] The communication area (or coverage area) of a base station may be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in the context of LTE (also known as Evolved Universal Terrestrial Radio Access Network (E-UTRAN), its alternative location may be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in the context of 5G NR, its alternative location may be referred to as a "gNodeB" or "gNB".

[0053] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various telecommunications capabilities, such as voice, SMS, and / or data services.

[0054] Base station 102A and other similar base stations (such as base stations 102B, ..., 102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-106N and similar devices over a geographical area via one or more cellular communication standards.

[0055] Therefore, although base station 102A can act as such Figure 1A The illustrated UEs 106A-106N are "serving cells," but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells." Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing a service area size. For example, Figure 1A The illustrated base stations 102A-102B may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0056] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0057] It should be noted that UE 106 may be able to communicate using multiple wireless communication standards. For example, UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) other than at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.)). If desired, UE 106 may also be configured, or alternatively, to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H) and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0058] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is illustrated. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet computer, or virtually any type of wireless device.

[0059] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any method implementation of the method implementations described herein by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to perform any of the method implementations described herein or any portion thereof.

[0060] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR using a single shared radio component and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Generally, the radio component may include any combination of baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among multiple wireless communication technologies (such as those discussed above).

[0061] In some implementations, UE 106 may include independent transmit and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0062] Figure 2 Block diagram of a base station Figure 2 Example block diagrams of base station 102 according to some implementation schemes are shown. It should be noted that... Figure 2 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 204, which executes program instructions for base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250) or into other circuitry or devices.

[0063] Base station 102 may include at least one network port 270. Network port 270 may be configured to couple to a telephone network and provide access to multiple devices, such as UE device 106, as described above in Figure 1 and... Figure 2 Access to the telephone network described in the text.

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

[0065] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0066] Base station 102 may include at least one antenna 234, and may include multiple antennas. At least one antenna 234 may be configured to operate as a wireless transceiver and may also be configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0067] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some instances, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0068] As further described herein, BS 102 may include hardware and software components for implementing or supporting specific implementations of the features described herein. The processor 204 of base station 102 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of BS 102 may be configured to implement or support some or all of the features described herein.

[0069] Furthermore, as described herein, processor 204 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 204. Therefore, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 204.

[0070] Furthermore, as described herein, radio component 230 may comprise one or more processing elements. In other words, one or more processing elements may be included in radio component 230. Therefore, radio component 230 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 230. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio component 230.

[0071] In some implementations, the base station or gNB 102 and / or its processor 204 are capable of and configured to: encode configuration information for allocating configured Granted Physical Uplink Shared Channel (CG-PUSCH) resources to transmit to the User Equipment (UE) using Radio Resource Control signaling to notify that the UIBR process has been triggered at the UE, enabling the UE to: select a Reference Signal (RS) resource to be monitored at the UE to identify whether the UIBR has been triggered at the UE; monitor the signal quality of the selected RS resource by the UE; determine by the UE that the signal quality is less than a signal quality threshold; and measure a Channel State Information Reference Signal (RS) resource set based on the determination that the signal quality is less than the signal quality threshold; and decode a beam management report from the UE using the CG-PUSCH resource based on the measurement based on the CSI resource set to notify that the UIBR process has been triggered.

[0072] Figure 3 Server block diagram Figure 3 Example block diagrams of server 104 according to some implementation schemes are shown. Note that... Figure 3 The server shown is merely one example of a possible server. As illustrated, server 104 may include processor 344 capable of executing program instructions for server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or into other circuitry or devices.

[0073] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102 and UE device 106, for example, as further described herein.

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

[0075] As described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. The processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 354, 364, and / or 374, the processor 344 of server 104 may be configured to implement or support some or all of the features described herein.

[0076] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.

[0077] Figure 4 User Equipment Block Diagram Figure 4 A simplified block diagram of a communication device 106 according to some implementation schemes is shown. Note that... Figure 4 The block diagram of the communication device is merely one example of possible communication devices. According to implementations, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. As shown, communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 400 may be implemented as individual components or groups of components for various purposes. The set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of communication device 106.

[0078] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 460 that may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). ™ (and WLAN circuitry). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0079] Cellular communication circuitry 430 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, short-to-medium-range wireless communication circuitry 429 may be coupled (e.g., communicatively; directly or indirectly) to antennas 435 and 436 in addition to or instead of being coupled to antennas 437 and 438. Short-to-medium-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0080] In some embodiments, as further described below, the cellular communication circuit 430 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuit 430 may include a single transmit chain that can be switched between radio components dedicated to a specific RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and may communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and may communicate with a dedicated receive chain and a shared transmit chain.

[0081] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 460 (which may be a touch screen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to the user and / or receiving or interpreting user input.

[0082] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC (Universal Integrated Circuit Card) cards 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functionality, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.

[0083] As noted above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other specific implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to standby awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.

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

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

[0086] Furthermore, as described herein, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0087] Additionally, as described herein, the cellular communication circuit 430 and the short-to-medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-to-medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 429.

[0088] Figure 5 Block diagram of cellular communication circuit Figure 5 Exemplary simplified block diagrams of cellular communication circuits according to some implementation schemes are shown. It should be noted that... Figure 5The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As noted above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

[0089] The cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a-b and 436 are shown in the diagram. In some embodiments, cellular communication circuitry 530 may include dedicated receive chains for various RATs (including and / or coupled to (e.g., communicatively ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0090] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 535. RF front end 535 may include circuitry for transmitting and receiving radio signals. For example, RF front end 535 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0091] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0092] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0093] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSANR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), processor 512 may be configured to implement some or all of the features described herein by combining one or more of other components 530, 532, 534, 535, 550, 570, 572, 335a, 335b, and 336.

[0094] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0095] For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), processor 522 may be configured to implement some or all of the features described herein. Alternatively (or in addition), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336, processor 522 may be configured to implement some or all of the features described herein.

[0096] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0097] In some implementations, processors 512, 522 may be configured to perform inter-RAT LTE measurements without measurement gaps, as further described herein.

[0098] Figure 6 Block diagram of the baseband processor architecture for UE Figure 6 Example components of device 600 according to some implementation schemes are illustrated. It should be noted that... Figure 6 The device described is merely one example of a possible system, and the features of this disclosure can be implemented in any type of UE as needed.

[0099] In some embodiments, device 600 may include application circuitry 602, baseband circuitry 604, radio frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 (at least coupled together as shown). Components of the illustrated device 600 may be included in UE 106 or RAN node 102A. In some embodiments, device 600 may include fewer components (e.g., the RAN node may not utilize application circuitry 602, but instead include a processor / controller to process IP data received from the EPC). In some embodiments, device 600 may include additional components such as, for example, memory / storage devices, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device (e.g., the circuitry may be individually included in more than one device for a cloud-RAN (C-RAN) specific implementation).

[0100] Application circuitry 602 may include one or more application processors. For example, application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). These processors may be coupled to or may include memory / storage devices and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on device 600. In some embodiments, the processor of application circuitry 602 may process IP data packets received from the EPC.

[0101] Baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 604 may include one or more baseband processors or control logic components to process baseband signals received from the receive signal path of RF circuitry 606 and generate baseband signals for the transmit signal path of RF circuitry 606. Baseband processing circuitry 604 may interact with application circuitry 602 to generate and process baseband signals and control the operation of RF circuitry 606. For example, in some embodiments, baseband circuitry 604 may include a third-generation (3G) baseband processor 604A, a fourth-generation (4G) baseband processor 604B, a fifth-generation (5G) baseband processor 604C, or other existing, under development, or future generations of baseband processors 604D (e.g., second-generation (2G), sixth-generation (6G), etc.). Baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may process various radio control functions that enable communication with one or more radio networks via RF circuitry 606. In other embodiments, some or all of the functionality of the baseband processors 604A-D may be included in modules stored in memory 604G and executed via a central processing unit (CPU) 604E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, and radio frequency shifting. In some embodiments, the modulation / demodulation circuitry of the baseband circuitry 604 may include Fast Fourier Transform (FFT), pre-decoding, or constellation mapping / demapping functionality. In some embodiments, the encoding / decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity-check (LDPC) encoder / decoder functionality. Implementations of the modulation / demodulation and encoder / decoder functionality are not limited to these examples, and other suitable functionalities may be included in other embodiments.

[0102] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processors (“DSPs”) 604F. The audio DSP 604F may include elements for compression / decompression and echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the components of the baseband circuitry 604 and the application circuitry 602 may be implemented together, for example, on a system-on-a-chip (SOC).

[0103] In some implementations, baseband circuit 604 can provide communication compatible with one or more radio technologies. For example, in some implementations, baseband circuit 604 can support communication with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), or Wireless Personal Area Networks (WPAN). Implementations in which baseband circuit 604 is configured to support radio communication with more than one radio protocol may be referred to as multimode baseband circuits.

[0104] RF circuit 606 enables communication with a wireless network via a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 606 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. RF circuit 606 may include a receive signal path that includes circuitry for down-converting the RF signal received from FEM circuit 608 and providing a baseband signal to baseband circuit 604. RF circuit 606 may also include a transmit signal path that includes circuitry for up-converting the baseband signal provided by baseband circuit 604 and providing an RF output signal for transmission to FEM circuit 608.

[0105] In some embodiments, the receive signal path of RF circuit 606 may include mixer circuit 606a, amplifier circuit 606b, and filter circuit 606c. In some embodiments, the transmit signal path of RF circuit 606 may include filter circuit 606c and mixer circuit 606a. RF circuit 606 may also include synthesizer circuit 606d for synthesizing frequencies used by mixer circuit 606a in both the receive and transmit signal paths. In some embodiments, mixer circuit 606a in the receive signal path may be configured to down-convert the RF signal received from FEM circuit 608 based on the synthesized frequency provided by synthesizer circuit 606d. Amplifier circuit 606b may be configured to amplify the down-converted signal, and filter circuit 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 604 for further processing. In some implementations, these output baseband signals may be zero-frequency baseband signals, but this is not necessary. In some implementations, the mixer circuit 606a in the receiving signal path may include a passive mixer, but the scope of the implementations is not limited in this respect.

[0106] In some implementations, the mixer circuit 606a of the transmit signal path may be configured to up-convert the input baseband signal based on the synthesis frequency provided by the synthesizer circuit 606d to generate an RF output signal for the FEM circuit 608. The baseband signal may be provided by the baseband circuit 604 and may be filtered by the filter circuit 606c.

[0107] In some embodiments, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and quadrature upconversion, respectively. In some embodiments, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit 606a for the receive signal path and the mixer circuit 606a for the transmit signal path may be configured for superheterodyne operation.

[0108] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuit 604 may include a digital baseband interface for communicating with RF circuit 606.

[0109] In some dual-mode implementations, separate radio IC circuits may be provided to process signals for each spectrum, but the scope of the implementation is not limited in this respect.

[0110] In some implementations, synthesizer circuit 606d may be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, but the scope of implementations is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 606d may be a Δ-∑ synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0111] Synthesizer circuit 606d can be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 606a of RF circuit 606. In some embodiments, synthesizer circuit 606d may be a fractional N / N+1 synthesizer.

[0112] In some implementations, the frequency input may be provided by a voltage-controlled oscillator (VCO), but this is not necessary. The divider control input may be provided by the baseband circuitry 604 or the application processor 602 according to the desired output frequency. In some implementations, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application processor 602.

[0113] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a phase detector, a charge pump, a D-type flip-flop, and a set of cascaded adjustable delay elements. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase groups, 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.

[0114] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may 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 frequency divider circuitry to generate multiple signals having multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, RF circuitry 606 may include an IQ / polarity converter.

[0115] FEM circuit 608 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals, and provide an amplified version of the received signals to RF circuit 606 for further processing. FEM circuit 608 may also include a transmit signal path, which may include circuitry configured to amplify transmit signals provided by RF circuit 606 for transmission by one or more of the one or more antennas 610. In various embodiments, amplification via the transmit or receive signal path may be performed only in RF circuit 606, only in FEM 608, or in both RF circuit 606 and FEM 608.

[0116] In some embodiments, FEM circuit 608 may include a TX / RX switch for switching between transmit and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include an LNA for amplifying the received RF signal and providing the amplified received RF signal as an output (e.g., provided to RF circuit 606). The transmit signal path of FEM circuit 608 may include a power amplifier (PA) for amplifying (e.g., provided by RF circuit 606) the input RF signal; and one or more filters for generating an RF signal for subsequent transmission (e.g., through one or more antennas in one or more antennas 610).

[0117] In some implementations, the PMC 612 can manage the power supplied to the baseband circuitry 604. Specifically, the PMC 612 can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 612 is typically included when the device 600 can be powered by a battery, for example, when the device is included in a UE. The PMC 612 can improve power conversion efficiency while providing the desired implementation size and thermal characteristics.

[0118] Although Figure 6A PMC 612 is shown coupled only to the baseband circuit 604, but in other embodiments, the PMC 612 may be coupled additionally or alternatively to other components such as, but not limited to, the application circuit 602, the RF circuit 606, or the FEM 608, and perform similar power management operations for these other components.

[0119] In some implementations, the PMC 612 may control or otherwise become part of various power-saving mechanisms of the device 600. For example, if the device 600 is in the Radio Resource Control_Connected (RRC_Connected) state, where the device is still connected to the RAN node because it expects to receive traffic immediately, it may enter a state called Discontinuous Receive Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for short intervals, thereby saving power.

[0120] If there is no data traffic activity during the extended period, device 600 can transition to the RRC_Idle state, in which the device disconnects from the network and does not perform operations such as channel quality feedback or handover. Device 600 enters a very low power state and performs paging, in which the device periodically wakes up again to listen to the network and then powers off again. Device 600 may be unable to receive data in this state, and to receive data, it will transition back to the RRC_Connected state.

[0121] An additional power-saving mode renders the device unusable for a period exceeding the paging interval (from seconds to hours). During this time, the device is completely unconnected to the network and may be completely powered off. Any data transmitted during this period will incur significant latency, which is assumed to be acceptable.

[0122] The processor of application circuit 602 and the processor of baseband circuit 604 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 604 can be used individually or in combination to execute layer 3, layer 2, or layer 1 functionality, while the processor of application circuit 604 can utilize data received from these layers (e.g., packet data) and further execute layer 4 functionality (e.g., transmit communication protocol (TCP) and user datagram protocol (UDP) layers). As mentioned herein, layer 3 (L3) may include the Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 (L2) may include the Media Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 (L1) may include the physical (PHY) layer of the UE / RAN node, which will be described in further detail below. Therefore, baseband circuit 604 can be used to encode messages for transmission between the UE and gNB, or to decode messages received between the UE and gNB.

[0123] For example, baseband circuitry 604 can be used to decode a high-priority flag received from the network, indicating that measurements of one or more LTE component carriers (LTE CCs) should be prioritized relative to measurements of New Radio (NR) secondary component carriers (NR SCCs). The UE can allocate a first searcher resource for measurements of New Radio Primary Component Carriers (NR PCCs). The UE can allocate a first portion of a second searcher resource for LTE CC measurements and a second portion of the second searcher resource for measurements of one or more NR SCCs based on the high-priority flag, wherein the first portion is greater than or equal to the second portion. The UE can use the first portion of the second searcher resource to perform LTE CC measurements without using measurement gaps. The UE can use the second portion of the second searcher resource to perform NR SCC measurements. The baseband circuitry can be used as previously described.

[0124] Figure 7 Block diagram of the baseband circuit interface Figure 7 Example interfaces of baseband circuits according to some implementation schemes are illustrated. Note that... Figure 7 The baseband circuit is merely one example of a possible circuit, and the features of this disclosure can be implemented in any of various systems as needed.

[0125] As discussed above, Figure 6The baseband circuit 604 may include processors 604A-604E and a memory 604G utilized by the processors. Each of the processors 604A-604E may respectively include a memory interface 704A-704E for transferring / receiving data to / from the memory 604G.

[0126] The baseband circuit 604 may further include: one or more interfaces for communicatively coupling to other circuits / devices, such as a memory interface 712 (e.g., an interface for transferring / receiving data to / from a memory external to the baseband circuit 604); and an application circuit interface 714 (e.g., for transferring / receiving data to / from a memory external to the baseband circuit 604); Figure 6 Application circuit 602 is an interface for transmitting / receiving data; RF circuit interface 716 (e.g., for sending / receiving data to / from...). Figure 6 RF circuit 606 is an interface for transmitting / receiving data; wireless hardware connectivity interface 718 (e.g., for transmitting / receiving data to / from near field communication (NFC) components, Bluetooth). ® Components (e.g., Bluetooth) ® Low power consumption, Wi-Fi ® Interfaces for transmitting / receiving data to / from components and other communication components); and power management interface 720 (e.g., an interface for transmitting / receiving power or control signals to / from the PMC612).

[0127] Figure 8 Control plane protocol stack Figure 8 This is an example of a control plane protocol stack according to some implementation schemes. In this implementation scheme, control plane 800 is shown as a communication protocol stack between UE 106a (or alternatively, UE 106b), RAN node 102A (or alternatively, RAN node 102B) and Mobility Management Entity (MME) 621.

[0128] PHY layer 801 can transmit or receive information used by MAC layer 802 through one or more air interfaces. PHY layer 801 can further perform link adaptive or adaptive modulation and decoding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers (such as RRC layer 805). PHY layer 801 can also further perform: error detection of the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, modulation / demodulation of the physical channel, interleaving, rate matching, mapping to the physical channel, and multiple-input multiple-output (MIMO) antenna processing.

[0129] MAC layer 802 can perform the following: mapping between logical channels and transport channels, multiplexing MAC service data units (SDUs) from one or more logical channels onto a transport block (TB) to be delivered to the PHY via the transport channel, demultiplexing MAC SDUs from a transport block (TB) delivered from the PHY via the transport channel onto one or more logical channels, multiplexing MAC SDUs onto a TB, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), and logical channel prioritization.

[0130] RLC layer 803 can operate in multiple modes, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC layer 803 can perform the transmission of higher-layer protocol data units (PDUs), error correction via Automatic Repeat Request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC layer 803 can also re-segment RLC data PDUs used for AM data transmission, reorder RLC data PDUs used for UM and AM data transmission, detect duplicate data used for UM and AM data transmission, discard RLC SDUs used for UM and AM data transmission, detect protocol errors used for AM data transmission, and perform RLC re-establishment.

[0131] PDCP layer 804 can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform sequential delivery of upper-layer PDUs during lower-layer re-establishment, eliminate duplication of lower-layer SDUs during lower-layer re-establishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of control plane data, control timer-based data discarding, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0132] The main services and functions of RRC layer 805 may include broadcasting system information (e.g., included in the Master Information Block (MIB) or System Information Block (SIB) related to the Non-Access Stratum (NAS), broadcasting system information related to the Access Stratum (AS), paging, establishment, maintenance, and release of RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, mobility between Radio Access Technologies (RATs), and measurement configuration for UE measurement reporting. The MIB and SIB may include one or more Information Elements (IEs), each of which may include a separate data field or data structure.

[0133] UE 601 and RAN node 102A can use the Uu interface (e.g., the LTE-Uu interface) to exchange control plane data via a protocol stack including PHY layer 801, MAC layer 802, RLC layer 803, PDCP layer 804 and RRC layer 805.

[0134] The Non-Access Stratum (NAS) protocol 806 forms the highest layer of the control plane between UE 601 and MME 621. NAS protocol 806 supports the mobility and session management procedures of UE 601 to establish and maintain IP connectivity between UE 601 and P-GW 623.

[0135] The S1 Application Protocol (S1-AP) layer 815 supports the functions of the S1 interface and includes the Basic Procedure (EP). The EP is the interaction unit between RAN node 102A and CN 1020. S1-AP layer services can include two sets: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration delivery.

[0136] The Flow Control Transmission Protocol (SCTP) layer (optionally referred to as the SCTP / IP layer) 814 may be based in part on the IP protocol supported by the IP layer 813 to ensure reliable delivery of signaling messages between the RAN node 102A and the MME 621. The L2 layer 812 and the L1 layer 811 may refer to the communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0137] RAN node 102A and MME 621 can use the S1-MME interface to exchange control plane data through a protocol stack including L1 layer 811, L2 layer 812, IP layer 813, SCTP layer 814 and S1-AP layer 815.

[0138] Figure 9 User plane protocol stack Figure 9 This is an example of a user plane protocol stack according to some implementation schemes. In this implementation, user plane 900 is shown as a communication protocol stack between UE 106A (or alternatively, UE 106B or 106N), RAN node 102A (or alternatively, RAN node 102B), S-GW 622, and P-GW 623. User plane 900 may utilize at least some of the same protocol layers as control plane 800. For example, UE 601 and RAN node 102A may use a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack including PHY layer 801, MAC layer 802, RLC layer 803, and PDCP layer 804.

[0139] The General Packet Radio Service (GPRS) tunneling protocol for the user plane (GTP-U) layer 904 can be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data can be packets in any of the IPv4, IPv6, or PPP formats. The UDP and IP Security (UDP / IP) layer 903 provides checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. RAN node 102A and S-GW 622 can exchange user plane data using the S1-U interface via a protocol stack including L1 layer 811, L2 layer 812, UDP / IP layer 903, and GTP-U layer 904. S-GW 622 and P-GW 623 can exchange user plane data using the S5 / S8a interface via a protocol stack including L1 layer 811, L2 layer 812, UDP / IP layer 903, and GTP-U layer 904. (As described above...) Figure 8 The NAS protocol discussed here supports the mobility and session management process of UE 106 to establish and maintain IP 913 connectivity between UE 106 and P-GW 623.

[0140] Figure 10 Core network Figure 10 Example architectures of system 1000, including core network (CN) 1020, are illustrated according to various implementation schemes. CN 1020 may be the core network of a 5G system (which may be referred to as 5GC). System 1000 is shown to include UE 1001, which may be the same as or similar to UE 106A, 106B, or 106N previously discussed; (R)AN 1010, which may be the same as or similar to BS 102A or 102N previously discussed; and data network (DN) 1003, which may be, for example, operator services, Internet access, or third-party services; and CN 1020. CN 1020 may include multiple network functions, including Authentication Server Function (AUSF) 1022; Access and Mobility Management Function (AMF) 1021; Session Management Function (SMF) 1024; Network Exposure Function (NEF) 1023; Policy Control Function (PCF) 1026; Network Repository Function (NRF) 1025; Unified Data Management (UDM) 1027; Application Function (AF) 1028; User Plane Function (UPF) 1002; and Network Slice Selection Function (NSSF) 1029. In some cases, these network functions may be implemented as virtualization software-based functions / services.

[0141] UPF 1002 can act as an anchor point for mobility within and between RATs, an external Packet Data Unit (PDU) session point interconnected with DN 1003, and a branch point supporting multihomed PDU sessions. A PDU session is a logical connection between the UE and the DN. UPF 1002 can also perform packet routing and forwarding, packet inspection, user plane portion of policy rules, lawful packet interception (user plane (UP) collection), traffic usage reporting, quality of service (QoS) processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 1002 may include an uplink classifier to support traffic flow routing to the data network. DN 1003 may represent various network operator services, Internet access, or third-party services. DN 1003 may include or be similar to the previously discussed application server 104. UPF 1002 can interact with SMF1024 via the N4 reference point between SMF 1024 and UPF 1002.

[0142] AUSF 1022 can store authentication data for UE 1001 and handle authentication-related functionality. AUSF 1022 can facilitate a common authentication framework for various access types. AUSF 1022 can communicate with AMF 1021 via the N12 reference point between AMF 1021 and AUSF 1022; and can communicate with UDM 1027 via the N13 reference point between UDM 1027 and AUSF 1022. Additionally, AUSF 1022 can present an interface based on Nausf services.

[0143] AMF 1021 is responsible for registration management (e.g., registering UE 1001, etc.), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. AMF 1021 can be the termination point of the N11 reference point between AMF 1021 and SMF 1024. AMF 1021 provides transmission of SM messages between UE 1001 and SMF 1024 and acts as a transparent proxy for routing SM messages. AMF 1021 can also be used between UE 1001 and SMSF (… Figure 10AMF 1021 provides transmission of Short Message Service (SMS) messages between (not shown). AMF 1021 can act as a Security Anchor Function (SEAF), which may include interaction with AUSF 1022 and UE 1001, and reception of an intermediate key established due to the UE 1001 authentication process. In the case of authentication using the Universal Subscriber Identity Module (USIM), AMF 1021 may retrieve security material from AUSF 1022. AMF 1021 may also include a Security Context Management (SCM) function, which receives a key from the SEAF for deriving a network-specific access key. Furthermore, AMF 1021 may be the termination point of the RAN Control Plane (CP) interface, which may include or may be the N2 reference point between (R)AN 1010 and AMF 1021; and AMF 1021 may be the termination point of NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0144] AMF 1021 can also support NAS signaling with UE 1001 via a Non-3GPP Interoperability Function (N3IWF) interface. N3IWF can be used to provide access to untrusted entities. N3IWF can be the termination point for the N2 interface between (R)AN 1010 and AMF 1021 for the control plane, and can be the termination point for the N3 reference point between (R)AN 1010 and UPF 1002 for the user plane. Therefore, AMF 1021 can process N2 signaling for PDU sessions from SMF 1024 and AMF 1021, encapsulate / decapsulate packets for IPSec and N3 tunneling, mark N3 user plane packets in the uplink, and perform QoS corresponding to the N3 packet markings, while taking into account the QoS requirements associated with such markings received via N2. The N3IWF can also relay uplink and downlink control plane non-access stratum (NAS) signaling between UE 1001 and AMF 1021 via the N1 reference point between UE 1001 and AMF 1021, and relay uplink and downlink user plane packets between UE 1001 and UPF 1002. The N3IWF also provides a mechanism for establishing an Internet Protocol Security (IPsec) tunnel using UE 1001. AMF 1021 can present an interface based on Namf services and can be the N14 reference point between two AMF 1021s, as well as the AMF 1021 and the 5G Equipment Identity Register (5G-EIR). Figure 10 The endpoint of the N17 reference point (not shown).

[0145] UE 1001 may need to register with AMF 1021 to receive network services. Registration Management (RM) is used to register UE 1001 with or deregister it from the network (e.g., AMF 1021) and to establish a UE context in the network (e.g., AMF 1021). UE 1001 can operate in RM-REGISTERED or RM-DEREGISTERED states. In RM-DEREGISTERED state, UE 1001 does not register with the network, and the UE context in AMF 1021 does not maintain valid location or routing information for UE 1001; therefore, AMF 1021 cannot reach UE 1001. In RM-REGISTERED state, UE 1001 registers with the network, and the UE context in AMF 1021 can maintain valid location or routing information for UE 1001; therefore, AMF 1021 can reach UE 1001. In RM-REGISTERED state, UE 1001 can perform mobility registration update procedures, periodic registration update procedures triggered by the expiration of periodic update timers (e.g., notifying the network that UE 1001 is still active), and registration update procedures to update UE capability information or renegotiate protocol parameters with the network, etc.

[0146] The AMF 1021 can store one or more RM contexts for UE 1001, where each RM context is associated with a specific access to the network. The RM context can be a data structure, database object, etc., indicating or storing registration status and periodic update timers, particularly for each access type. The AMF 1021 can also store 5GC Mobility Management (MM) contexts that are the same as or similar to the Evolved Packet Services (EPS) Mobility Management (E) MM contexts discussed earlier. In various implementations, the AMF 1021 can store UE 1001's CE Mode B restriction parameters in the associated MM context or Registration Management (RM) context. The AMF 1021 can also derive values ​​from UE usage setting parameters already stored in the UE context (and / or MM / RM context) when needed.

[0147] Connection Management (CM) can be used to establish and release signaling connections between UE 1001 and AMF 1021 via the N1 interface. Signaling connections are used to enable NAS signaling exchange between UE 1001 and CN 1020, and include signaling connections between the UE and AN (e.g., RRC connections for non-3GPP access or UE-N3IWF connections) and N2 connections between the AN (e.g., AN 1010) and AMF 1021 for UE 1001. UE 1001 can operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When UE 1001 operates in CM-IDLE state / mode, UE 1001 may not have a NAS signaling connection established with AMF 1021 via the N1 interface, and (R)AN 1010 signaling connections (e.g., N2 and / or N3 connections) may exist for UE 1001. When UE 1001 operates in CM-CONNECTED state / mode, UE 1001 may have a NAS signaling connection established with AMF 1021 via the N1 interface, and may have (R)AN 1010 signaling connections (e.g., N2 and / or N3 connections) for UE 1001. Establishing an N2 connection between (R)AN 1010 and AMF 1021 enables UE 1001 to transition from CM-IDLE mode to CM-CONNECTED mode, and UE 1001 can transition from CM-CONNECTED mode to CM-IDLE mode when the N2 signaling between (R)AN 1010 and AMF 1021 is released.

[0148] SMF 1024 is responsible for Session Management (SM), session establishment, modification, and publication (including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of UPF traffic redirection to route traffic to the correct destination; termination of interfaces toward policy control functions; policy enforcement and QoS control portions; lawful interception (for SM events and interfaces with the LI system); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information transmitted to the AN via N2 through AMF; and determination of the SSC mode of the session. SM may refer to the management of PDU sessions, and a PDU session or "session" may refer to the PDU connectivity service that provides or enables PDU exchange between UE 1001, identified by the Data Network Name (DNN), and Data Network (DN) 1003. A PDU session can be established upon request from UE 1001, modified upon request from both UE 1001 and CN 1020, and released upon request from both UE 1001 and CN 1020 using NAS SM signaling exchanged via the N1 reference point between UE 1001 and SMF1024. Upon request from the application server, CN 1020 can trigger a specific application within UE 1001. In response to receiving a trigger message, UE 1001 can pass the trigger message (or relevant portions / information of the trigger message) to one or more identified applications within UE 1001. The identified application within UE 1001 can establish a PDU session to a specific data network name (DNN). SMF 1024 can check whether the UE 1001 request matches the user subscription information associated with UE 1001. In this regard, SMF 1024 can retrieve and / or request to receive update notifications regarding SMF1024 level subscription data from UDM 1027.

[0149] The SMF 1024 may include the following roaming functionalities: handling local execution to apply QoS SLAB Virtual Public Land Mobile Network (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interfaces with the LI system, in the VPLMN); and support for interaction with external DNs to transmit signaling for PDU session authorization / authentication via external DNs. In roaming scenarios, an N16 reference point between two SMF 1024s may be included in System 1000, which may be located between another SMF 1024 in the visited network and an SMF 1024 in the home network. Additionally, the SMF 1024 may present an interface based on NSMF services.

[0150] The NEF 1023 provides components for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 1028), edge computing, or fog computing systems. In such implementations, the NEF 1023 can authenticate, authorize, and / or restrict AFS. The NEF 1023 can also translate information exchanged with AF 1028 and information exchanged with internal network functions. For example, the NEF 1023 can translate between AF service identifiers and internal SCC information. The NEF 1023 can also receive information from other network functions (NFs) based on their exposure capabilities. This information can be stored as structured data at the NEF 1023 or stored at a data storage NF using a standardized interface. The stored information can then be re-exposed by the NEF 1023 to other NFs and AFs, and / or used for other purposes such as analysis. Additionally, the NEF 1023 can present an interface based on Nnef services.

[0151] The NRF 1025 supports service discovery, receiving NF discovery requests from NF instances and providing information about discovered NF instances to them. The NRF 1025 also maintains information about available NF instances and the services they support. As used herein, terms such as "instantiation" can refer to the creation of an instance, and "instance" can refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. Additionally, the NRF 1025 can present an interface based on Nnrf services.

[0152] The PCF 1026 can provide policy rules to control plane functions for enforcement and supports a unified policy framework to manage network behavior. The PCF 1026 can also implement a front-end (FE) to access subscription information related to policy decisions in the UDR of the UDM 1027. The PCF 1026 can communicate with the AMF 1021 via an N15 reference point, which can include the PCF 1026 in the visited network and the AMF 1021 in roaming scenarios. PCF 1026 can communicate with AF 1028 via the NS reference point between PCF 1026 and AF 1028; and communicate with SMF 1024 via the N7 reference point between PCF 1026 and SMF 1024. System 1000 and / or CN 1020 may also include an N24 reference point between PCF 1026 (in the home network) and PCF 1026 in the visited network. In addition, PCF 1026 may present an interface based on NPCF services.

[0153] UDM 1027 can process subscription-related information to support network entities in handling communication sessions and can store subscription data for UE 1001. For example, subscription data can be communicated between UDM 1027 and AMF 1021 via an NS reference point between UDM 1027 and AMF. UDM 1027 may include two parts: Application FE and UDR ( Figure 10 (FE and UDR are not shown). The UDR may store subscription data and policy data of UDM 1027 and PCF 1026, and / or structured data for exposure of NEF 1023, as well as application data (including PFD for application detection, application request information of multiple UE 1001s). An interface based on the Nadr service may be presented by UDR 221 to allow UDM 1027, PCF 1026, and NEF 1023 to access a specific set of stored data, and to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. Several different front-ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR may interact with SMF 1024 via the N10 reference point between UDM 1027 and SMF 1024. The UDM 1027 also supports SMS management, with SMS-FE implementing similar application logic as previously discussed. Additionally, the UDM 1027 can present an interface based on Nudm services.

[0154] AF 1028 can provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE can be a mechanism allowing CN 1020 and AF 1028 to provide information to each other via NEF 1023, which can be used in edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 1001 access point to achieve efficient service delivery through reduced end-to-end latency and load on the transport network. For edge computing implementations, 5GC can select UPF 1002 near UE 1001 and perform traffic redirection from UPF 1002 to DN 1003 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 1028. In this way, AF 1028 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1028 is considered a trusted entity, the network operator can allow AF 1028 to interact directly with the relevant NF. In addition, the AF 1028 can present an interface based on Naf services.

[0155] NSSF 1029 can select a set of network slice instances to serve UE 1001. If needed, NSSF 1029 can also determine the allowed network slice selection assistance information (NSSAI) and the mapping to the subscribed individual NSSAI (S-NSSAI). NSSF 1029 can also determine the set of AMFs, or a list of candidate AMFs 1021, for serving UE 1001 based on appropriate configuration and possibly by querying NRF 1025. The selection of a set of network slice instances for UE 1001 can be triggered by AMF 1021 registered with UE 1001 interacting with NSSF 1029, which can result in a change to AMF 1021. NSSF 1029 can interact with AMF 1021 via the N22 reference point between AMF 1021 and NSSF 1029; and via the N31 reference point (…). Figure 10 (Not shown) communicates with another NSSF 1029 in the visited network. Additionally, the NSSF 1029 can present an interface based on the Nnssf service.

[0156] As previously discussed, CN 1020 may include a Short Message Service Function (SMSF), which is responsible for SMS subscription checks and verification, as well as relaying SM messages to and / or from UE 1001 or other entities such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 1021 and UDM 1027 to notify UE 1001 of its availability for SMS delivery (e.g., setting a UE unreachable flag and notifying UDM 1027 when UE 1001 is available for SMS).

[0157] CN 1020 may also include Figure 10 Other elements not shown include data storage systems / architecture, 5G-EIR, Secure Edge Protection Agent (SEPP), etc. Data storage systems may include Structured Data Storage Network Function (SDSF), Unstructured Data Storage Function (UDSF), etc. Any network function (NF) can be transmitted via any NF and UDSF ( Figure 10 The N18 reference point (not shown) is used to store unstructured data in or retrieve unstructured data from the UDSF (e.g., UE context). Individual NFs can share a UDSF to store their respective unstructured data, or each NF can have its own UDSF located at or near its location. Additionally, the UDSF can present an interface based on Nudsf services (…). Figure 10(Not shown). 5G-EIR can be an NF that checks the status of a Permanent Equipment Identifier (PEI) to determine whether a specific piece of equipment / entity should be blacklisted from the network; and SEPP can be a non-transparent agent that performs topology hiding, message filtering, and policing on the control plane interface between PLMNs.

[0158] Furthermore, there can be more reference points and / or service-based interfaces between NF services; however, for clarity, Figure 10 These interfaces and reference points are omitted. In one example, CN 1020 may include an Nx interface, which is an inter-CN interface between the Mobility Management Entity (MME) and AMF 1021 to enable interoperability between CN 1020 and CNs in the 4G system. Other example interfaces / reference points may include an interface based on N5G-EIR services presented by 5G-EIR, reference point N27 between the NRF in the visited network and the NRF in the home network; and reference point N31 between the NSSF in the visited network and the NSSF in the home network.

[0159] Figure 11 Allocation of searcher resources for LTE and NR measurements Prior to 3GPP Release 18 (R18), all radio access technology (RAT) measurements from NR to LTE were performed within measurement gaps. Currently, there is a need to provide gapless RAT-to-LTE measurements so that gapless LTE measurements can have the same priority as gapless secondary component carriers (SCCs).

[0160] Therefore, as described herein, the mechanism of the illustrated implementation provides an example for performing inter-Radio Access Technology (RAT) Long Term Evolution (LTE) measurements without measurement gaps. For example, a UE can be configured to decode a high-priority flag received from the network indicating that measurements of one or more LTE component carriers (LTE CCs) should be prioritized relative to measurements of New Radio (NR) Secondary Component Carriers (NR SCCs). The UE can allocate a first searcher resource for measurements of New Radio Primary Component Carriers (NR PCCs). It should be noted that the searcher or “search resource” can include various hardware and software components that can be used for cell search and Radio Resource Management (RRM) measurements. The UE can allocate a first portion of a second searcher resource for measurements of LTE CCs and a second portion of the second searcher resource for measurements of one or more NR SCCs based on the high-priority flag, where the first portion is greater than or equal to the second portion. The UE can use the first portion of the second searcher resource to perform LTE CC measurements without using measurement gaps. The UE can use the second portion of the second searcher resource to perform NR SCC measurements.

[0161] To further explain, Figure 11 The primary component carrier (PCC) and SCC are associated with a measurement timing configuration (SMTC) timing based on a synchronization signal block (SSB), which can be configured by the network. Figure 11 An example is provided of the allocation of searcher resources for the primary component carrier (PCC), secondary component carrier 1 (SCC1), secondary component carrier 2 (SCC2), and LTE component carrier 1 (LTE CC1) without gaps, along with an exemplary option for allocating searcher resources based on a high priority flag.

[0162] Gapless LTE CC1 measurements can be associated with an Effective Measurement Window (EMW) timing, which can also be configured by the network. Searcher 1 can be dedicated to PCC measurements, while searcher 2 is shared between SCC and LTE CC1 measurements. Currently, 3GPP standards (such as 3GPP Technical Specification (TS) 38.133 V18.4.0 (January 2024)) treat gapless LTE measurements with the same priority as NRSCC measurements. For example, in Figure 11 In this scenario, searcher 2 will spend 1 / 3 of its time on NR SCC1, 1 / 3 on SCC2, and 1 / 3 on LTE CC1. Therefore, when multiple NR SCCs exist, searcher 2 will spend less than half the time (i.e., 1 / 3 or less) on LTE CC1. However, in certain scenarios, such as handover or load balancing, the time spent by the LTE carrier relative to searcher 2 on all NR SCCs should not be de-prioritized. To address this issue, the illustrated implementation mechanism provides a high-priority flag to prioritize LTE CC measurements over NR SCC measurements.

[0163] In one example, Seeker 1 can be dedicated to NR PCC measurements. Seeker 2 can be shared between LTE CC1 and NR SCC measurements. The allocation of Seeker 2 resources depends on the high priority flag.

[0164] In the first option, when the high priority flag is set, a first portion (e.g., 50%) of the searcher 2 resources can be allocated for LTE CC1 measurements, and a second portion (e.g., 50%) can be allocated for NR SCC measurements, as... Figure 11 As shown. This ensures that LTE measurements are given the same priority as NR SCC measurements.

[0165] By dynamically allocating searcher resources (e.g., searcher 2 resources) based on high priority flags, the UE can prioritize LTE measurements over NR SCC measurements when necessary (such as during handover or load balancing scenarios), thereby ensuring reliable and timely LTE measurements without relying on measurement gaps.

[0166] Figure 12 CSSF values ​​for different scenarios and frequency ranges Figure 12 Example tables illustrating CSSF (Carrier-Specific Scaling Factor) values ​​for different scenarios and frequency ranges according to various implementation schemes are provided. The tables present CSSF values ​​for various combinations of carriers in frequency range 1 (FR1) and frequency range 2 (FR2), as well as different types of measurements, such as inter-frequency and inter-RAT measurements. The values ​​illustrated in the table can be used to provide measurement cycles for LTE CC measurements, where a first portion (e.g., 50%) of the searcher 2 resources can be allocated for LTE CC1 measurements, and a second portion (e.g., 50%) can be allocated for NR SCC measurements, such as... Figure 11 As shown.

[0167] The CSSF value is determined based on several factors, including the number of secondary cells (SCells) with a configuration of Layer 3 (L3) measurements based on Synchronization Block (SSB) or Channel State Information Reference Signal (CSI-RS), the number of inter-frequency measurement objects (MOs) without measurement gaps (MG), and the number of inter-E-UTRA RAT MOs without MG.

[0168] Figure 12 The tables also consider specific scenarios, such as FR1 carrier aggregation (CA) only, FR2 intra-band CA only, FR2 inter-band CA only, and FR1+FR2 CA with FR1 or FR2 primary cells (PCells). For each scenario, CSSF values ​​are provided for the primary component carrier (PCC), secondary component carrier (SCC), and various measurement configurations.

[0169] therefore, Figure 12 The table in the document describes both columns and rows. The columns list various carrier aggregation and measurement scenarios, such as, for example, FR1 CA only, FR2 intra-band CA only, FR2 inter-band CA only, and FR1+FR2 CA with FR1 or FR2 PCell.

[0170] The "CSSF outside_gap,i for FR1 PCC" column provides the CSSF value for the primary component carrier (PCC) in frequency range 1 (FR1) when measurements are performed outside the gap. The "CSSF outside_gap,i for FR1 SCC" column provides the CSSF value for the secondary component carrier (SCC) in FR1 when measurements are performed outside the gap.

[0171] The "CSSF outside_gap,i for FR2 PCC" column provides the CSSF value for the PCC in frequency range 2 (FR2) when measurements are performed outside the gap. The "CSSF outside_gap,i for FR2 SCC where neighbor cell measurements are required" column provides the CSSF value for the SCC in FR2 with neighbor cell measurements configured.

[0172] The column “CSSFoutside_gap,i for FR2 SCCs where neighboring cell measurements are not required” provides the CSSF value for SCCs in FR2s where neighboring cell measurements are not configured. The column “CSSFoutside_gap,i for inter-frequency MOs without measurement gaps” provides the CSSF value for inter-frequency measurement objects (MOs) without measurement gaps, and the column “CSSFoutside_gap,i for inter-E-UTRA RAT MOs without measurement gaps” is designed to provide the CSSF value for inter-E-UTRA RAT MOs without measurement gaps.

[0173] The row headings list specific carrier aggregation and frequency range scenarios, including FR1 CA only, FR2 intra-band CA only, FR2 inter-band CA only, and FR1+FR2 CA with FR1 or FR2 PCells. The CSSF values ​​in the table are determined based on a combination of scenario (rows) and measurement configuration (columns), and they are calculated using the number of SCells in the configuration, the number of MOs, and other factors as specified.

[0174] In addition, one or more conditions can be defined to set the CSSFoutside_gap,i value, the number of SCells in a configuration with a specific measurement configuration, and the number of MOs in SCells with Received Signal Strength Indicator (RSSI) or Channel Occupancy (CO) measurements in a configuration without MG. These conditions provide additional context and definitions for the parameters used in the CSSF calculation. For example, these conditions and definitions can be defined as: 1) for inter-band CA of FR1 and FR2 (FR1+FR2), only one frequency range one (FR1) operating band and one FR2 operating band are included, and for inter-band carrier aggregation (CA) of FR2, only two NRs are included. FR2 operating frequency band, 2) Select the SCC in FR2 that requires neighboring cell measurement; 3) If only one SCell is configured and there is no gapless inter-frequency MO and only SSB-based Layer 3 (L3) measurement is configured on the SCC, then CSSFoutside_gap,i equals one (1), or if only one SCell is configured and there is no gapless inter-frequency MO and L3 based on both SSB and Channel State Information Reference Signal (CSI-RS) or only CSI-RS based L3 measurement is configured on the SCC, then CSSFoutside_gap,i equals two (2); 4) Y is the number of configured inter-frequency measurement objects (MOs) outside the MG without MG, or Y is 0; 5) If the main component carrier (PCC) is configured with L3 measurement based on both SSB and CSI-RS or only CSI-RS based L3 measurement, then the number of main cells configured in the new radio (NR) (N) is... PCC6) The Channel State Information Reference Signal (NPCC_CSIRS) is equal to one (1), or the NPCC_CSIRS is equal to zero (0); 7) The NSCC_SSB is one or more new radio-assisted cells (SCells) that are only configured with SSB-based Layer 3 (L3) measurements and are measured without measurement gaps (MG); NSCC_Channel State Information Reference Signal (NSCC_CSIRS) is one or more SCells configured with L3 measurements based on both SSB and Channel State Information Reference Signal (CSI-RS), or only L3 measurements based on CSI-RS; 8) NSCC_CCA_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) (NSCC_CCA_RSSI / CO) is the number of measurement objects (MOs) of one or more SCells configured with RSSI or CO measurements but without MG when the Remaining Minimum System Information (RMSI) Measurement Timing Configuration (RMTC) and the SSB-based Measurement Timing Configuration (SMTC) overlap; 9) If the SCC is located in FR2 where neighbor cell measurements are required and is configured with both SSB and CSI-RS or only CSI-RS measurements, then NSCC_CSIRS_Frequency Range Two (FR2)_NCM (NSCC_CSIRS_FR2_NCM) equals one (1), or NSCC_CSIRS_FR2_NCM equals zero (0); and 10) Z is the number of Evolved Universal Terrestrial Radio Access (E-UTRA) RATs between MOs in the absence of MG, or Z equals zero (0).

[0175] Figure 13 Allocation of searcher resources for LTE and NR measurements Figure 13 Another example illustration illustrates the allocation of searcher resources for LTE and NR measurements based on high-priority flags according to some implementation schemes. Figure 11 similar, Figure 13 The allocation of searcher resources for the primary component carrier (PCC), secondary component carrier 1 (SCC1), secondary component carrier 2 (SCC2), gapless LTE component carrier 1 (LTE CC1), and gapless LTE component carrier 2 (LTE CC2) is described. PCC, SCC1, and SCC2 are associated with Measurement Timing Configuration (SMTC) timing based on Synchronization Signal Block (SSB), which can be configured by the network. Gapless LTE CC1 and LTE CC2 are associated with Effective Measurement Window (EMW) timing, which can also be configured by the network.

[0176] In this example, the Seeker 1 resource is dedicated to PCC measurements, while the Seeker 2 resource is shared among SCC1, SCC2, LTE CC1, and LTE CC2 measurements. The allocation of the Seeker 2 resource is based on a high-priority flag, which is introduced to prioritize LTE measurements over NR SCC measurements.

[0177] and Figure 11 Compared to the allocation in the example, Figure 13 Alternative options for allocating resources for Searcher 2 are illustrated. Therefore, Figure 11 The allocation of search resources can be referred to as Option 1, while Figure 13 The allocation of search resources can be referred to as Option 2.

[0178] In this option (e.g., Option 2), when the high priority flag is set, a first portion of the searcher 2 resources (e.g., 2 / 3 of the searcher 2 resources) can be allocated for LTE CC1 and LTE CC2 measurements, and a second portion of the searcher 2 resources (e.g., 1 / 3 of the searcher 2 resources) can be allocated for NR SCC measurements. That is, the first portion of the searcher 2 resources allocated for LTE CC1 and LTE CC2 measurements is at least 2 / 3 of the searcher 2 resources, and the second portion is the remaining 1 / 3 of the searcher 2 resources allocated for NR SCC1 and SCC2 measurements. This allocation gives higher priority to LTE CC measurements compared to NR SCC measurements.

[0179] In addition, such as Figure 13 The depicted 2 / 3 allocation for LTE CC measurements can be further divided between LTE CC1 and LTE CC2. Figure 13 In the example shown, LTE CC1 and LTE CC2 each receive an equal share of the allocated Searcher 2 resources for LTE measurements. However, the allocation between LTE CC1 and LTE CC2 can vary depending on specific needs and network conditions.

[0180] Figure 14 CSSF values ​​for different scenarios and frequency ranges Figure 14 Another example table illustrates CSSF (Carrier-Specific Scaling Factor) values ​​for different scenarios and frequency ranges according to some implementation schemes. Figure 12 Similar to the tables in the text, Figure 14 The table presents CSSF values ​​for various combinations of carriers in frequency range 1 (FR1) and frequency range 2 (FR2), as well as different types of measurements, such as inter-frequency and inter-RAT measurements. Figure 14The values ​​illustrated in the table can be used to provide measurement cycles for LTE CC measurements, where the first portion (e.g., 2 / 3) of the searcher 2 resources can be allocated for LTE CC1 and LTE CC2 measurements, while the second portion (e.g., 1 / 3) can be allocated for NR SCC measurements, as shown below. Figure 13 As shown.

[0181] and Figure 12 Similar to the tables in the text, Figure 14 The CSSF value is determined based on several factors, including the number of secondary cells (SCells) with a configuration of Layer 3 (L3) measurements based on Synchronization Signal Block (SSB) or Channel State Information Reference Signal (CSI-RS), the number of inter-frequency measurement objects (MOs) without measurement gaps (MG), and the number of inter-E-UTRARAT MOs without MG.

[0182] This table takes into account... Figure 12 The same scenarios are included, such as FR1 carrier aggregation (CA) only, FR2 intra-band CA only, FR2 inter-band CA only, and FR1+FR2 CA with FR1 or FR2 primary cells (PCells). For each scenario, CSSF values ​​are provided for the primary component carrier (PCC), secondary component carrier (SCC), and various measurement configurations.

[0183] However, due to such Figure 13 The different allocations of searcher resources described in the text Figure 14 The CSSF value in (Option 2) is the same as Figure 12 The CSSF values ​​in (Option 1) are different. For example, in the "FR1 CA only" scenario, the CSSF value for FR1 SCC is "3×(NSCC_SSB+Y+2xNSCC_CSIRS+NSCC_CCA_RSSI / CO)", which is higher than... Figure 12 The corresponding value in [the table / reference]. This increase reflects the allocation of 2 / 3 of the Searcher 2 resources to LTE measurements in Option 2. Similarly, with [other values / references]... Figure 12 In comparison, Figure 14 In this context, the CSSF values ​​for frequency-interval MOs without measurement gaps and E-UTRA RAT-interval MOs without measurement gaps also differ. For frequency-interval MOs, the CSSF value is typically higher, while for E-UTRA RAT-interval MOs, the CSSF value is calculated using the formula "ceil(1.5×Z)" (where "ceil" means rounding up), where Z is the number of E-UTRA RAT-interval MOs configured without MGs.

[0184] Figure 14 The conditions and definitions in the table provide parameters used in CSSF calculations that are consistent with... Figure 12The same additional context and definitions are provided. These conditions and definitions help clarify the various terms and conditions used in CSSF formulas. For the sake of brevity, Figure 12 The conditions and definitions described in [the document] apply to [the following]. Figure 14 .

[0185] therefore, Figure 14 The CSSF values ​​in the code are applicable to Figure 13 The searcher resource allocation proposed in Option 2, as described in the document, prioritizes LTE measurements over NR SCC measurements by allocating 2 / 3 of the searcher 2 resources to LTE and 1 / 3 to NR SCC. By adapting the CSSF value based on this allocation, the UE can efficiently utilize its searcher resources when necessary and ensure reliable LTE measurements.

[0186] Figure 15 Measurement configuration information element (MeasConfig) Figure 15 An example of the abstract syntax markup 1 (ASN.1) code for the Measurement Configuration (MeasConfig) information element according to some implementation schemes is shown. The MeasConfig information element can be used to configure various measurement-related parameters in a wireless communication system. The MeasConfig information element consists of several fields, each responsible for configuring a specific aspect of the measurement process. These fields may include, but are not limited to: 1) measObjectToRemoveList: a list of measurement objects to be removed from the UE's configuration; 2) measObjectToAddModList: a list of measurement objects to be added to or modified in the UE's configuration; 3) reportConfigToRemoveList: a list of report configurations to be removed from the UE's configuration; 4) reportConfigToAddModList: a list of report configurations to be added to or modified in the UE's configuration; 5) measIdToRemoveList: a list of measurement identifiers to be removed from the UE's configuration; 6) measIdToAddModList: a list of measurement identifiers to be added to or modified in the UE's configuration; 7) s-MeasureConfig: the selection between the Synchronization Block Reference Signal Received Power (SSB-RSRP) and the CSI Reference Signal Received Power (CSI-RSRP) for the serving cell measurement configuration; 8) quantityConfig: the configuration for the quantity-related parameters of the measurement; 9) measGapConfig: the configuration of the measurement gap; and 10) measGapSharingConfig: the configuration for sharing the measurement gap among multiple measurement objects.

[0187] In addition to these fields, Figure 15The MeasConfig information element can also include a field called "LTEMeasureOutsideGap". The "LTEMeasureOutsideGap" field allows the network to configure the UE with one of the options for prioritizing LTE measurements over NR secondary component carrier (SCC) measurements, such as... Figure 11 and Figure 13 The “LTEMeasureOutsideGap” field can be a table such as that described herein (e.g., ...). Figure 12 and Figure 14 The values ​​described in the table (or other options). These values ​​may correspond to, for example, the values ​​described in the table (see below). Figure 11 and Figure 13 The different searcher resource allocation options discussed herein. For example, "Option 1" could refer to a 50 / 50 split between LTE CC measurements and NR SCC measurements, while "Option 2" could refer to a 2 / 3 and a 1 / 3 split for LTE CC and NR SCC measurements, respectively.

[0188] In an additional example, the field in the MeasConfig information element can also be “interFrequencyConfig-NoGap-r16”. When set to “true”, the “interFrequencyConfig-NoGap-r16” field instructs the UE to perform inter-frequency measurements without using measurement gaps, as specified in version 16 (r16) of the 3GPP specification. The addition of the “LTEMeasureOutsideGap” and “interFrequencyConfig-NoGap-r16” fields to the MeasConfig information element prioritizes LTE measurements over NR SCC measurements.

[0189] Figure 16 Allocation of searcher resources for LTE and NR measurements Figure 16 Example illustrations are provided of the allocation of searcher resources for LTE and NR measurements according to some implementation schemes, including a dedicated searcher for LTE measurements.

[0190] and Figure 11 and Figure 13 similar, Figure 16The allocation of searcher resources for the primary component carrier (PCC), secondary component carrier 1 (SCC1), secondary component carrier 2 (SCC2), gapless LTE component carrier 1 (LTE CC1), and gapless LTE component carrier 2 (LTE CC2) is described. PCC, SCC1, and SCC2 are associated with Measurement Timing Configuration (SMTC) timing based on Synchronization Signal Block (SSB), which can be configured by the network. Gapless LTE CC1 and LTE CC2 are associated with Effective Measurement Window (EMW) timing, which can also be configured by the network.

[0191] However, in Figure 16 The system provides a new UE capability to indicate support for a dedicated searcher for LTE measurements (e.g., searcher 3 in the searcher resource). This dedicated searcher, which can be designed as a searcher resource, can be assigned to both LTE CC1 and LTE CC2 measurements. By having a separate searcher for LTE measurements, the UE can ensure reliable and timely LTE measurements without relying on measurement gaps or sharing resources with NR measurements.

[0192] For example, in Figure 16 In this configuration, Seeker 1 and Seeker 2 of the Seeker resource can be allocated for NR measurements. Seeker 1 can be dedicated to PCC measurements, while Seeker 2 can be shared between SCC1 and SCC2 measurements. The allocation of Seeker 2 resources between SCC1 and SCC2 can vary depending on network configuration and measurement requirements.

[0193] Dedicated LTE searchers (such as, for example, searcher 3) can be specifically designed for LTE CC1 and LTE CC2 measurements. Figure 16 In the example shown, the searcher resource 3 is equally divided between LTE CC1 and LTE CC2. However, the allocation of searcher 3 resources between LTE CC1 and LTE CC2 can be adjusted based on the specific needs of the network and the UE.

[0194] By introducing a dedicated searcher for LTE measurements, the dedicated searcher ensures that LTE measurements are not compromised by the presence of NR measurements. The UE can perform LTE measurements independently without measurement gaps or sharing resources with NR measurements. This approach is particularly beneficial in scenarios where reliable and timely LTE measurements are critical, such as during handover or load balancing. Therefore, as... Figure 16 As shown, using a dedicated LTE searcher provides improved efficiency for performing LTE and NR measurements simultaneously, while also allowing the UE to prioritize LTE measurements when necessary, while maintaining the performance of NR measurements using searcher 1 and searcher 2.

[0195] Figure 17 CSSF values ​​for different scenarios and frequency ranges Figure 17 Example tables illustrate CSSF (Carrier Specific Scaling Factor) values ​​for different scenarios and frequency ranges considering a dedicated searcher used for LTE measurements.

[0196] exist Figure 17 In, with Figure 12 and Figure 14 Similarly, this table considers the relationship with Figure 12 and Figure 14 The same scenarios are included, such as FR1 carrier aggregation (CA) only, FR2 intra-band CA only, FR2 inter-band CA only, and FR1+FR2 CA with FR1 or FR2 primary cells (PCells). For each scenario, CSSF values ​​are provided for the primary component carrier (PCC), secondary component carrier (SCC), and various measurement configurations.

[0197] However, due to the existence of a dedicated LTE searcher (searcher 3). Figure 17 CSSF values ​​and Figure 12 and Figure 14 The CSSF values ​​differ. In the case where Seeker 3, with its dedicated Seeker resources, handles LTE CC measurements, the CSSF values ​​for NR measurements (performed by Seeker 1 and Seeker 2) are lower compared to the previous table. This reduction reflects the fact that NR measurements no longer need to share resources with LTE CC measurements.

[0198] exist Figure 17 The CSSF values ​​for inter-frequency MO without a measurement gap and inter-frequency MO without a measurement gap in E-UTRA RAT were also adjusted. For inter-frequency MO, the CSSF value is typically lower than [value missing]. Figure 12 and Figure 14 The CSSF value reflects the reduced resource sharing between NR SCC and LTECC measurements. For E-UTRA RAT inter-MO, the CSSF value is simply “Z”, where Z is the number of E-UTRA RAT inter-MOs in a configuration without measurement gaps (MG).

[0199] Figure 18 Flowchart of a method for inter-RAT LTE measurements without measurement gaps Figure 18 A flowchart illustrating a method for performing Long Term Evolution (LTE) measurements between Radio Access Technologies (RATs) without measurement gaps, according to some implementation schemes, is provided. Figure 18 The methods shown can also be used in conjunction with any of the systems, methods, or apparatuses illustrated in the figures, as well as other devices. In various embodiments, some of the method elements shown may be performed concurrently in a different order than those shown, or may be omitted. Additional method elements may also be performed as needed.

[0200] According to the implementation scheme, method 1800 can decode a high priority flag received from the network that indicates priority for measuring one or more LTE component carriers (LTE CCs) relative to the measurement of one or more new radio (NR) secondary component carriers (NR SCCs), as in box 1810.

[0201] Method 1800 may further include allocating a first searcher resource for measurements of one or more new radio main component carriers (NR PCCs), as in box 1820. Method 1800 may further include allocating a first portion of a second searcher resource for measurements of one or more LTE CCs based on a high priority flag and allocating a second portion of the second searcher resource for measurements of one or more NR SCCs, wherein the first portion is greater than or equal to the second portion, as in box 1830.

[0202] Method 1800 may further include performing measurements of one or more LTE CCs using a first portion of the second searcher resources without using measurement gaps, as in box 1840. Method 1800 may further include performing measurements of one or more NR SCCs using a second portion of the second searcher resources, as in box 1850.

[0203] In some implementations, the first portion is fifty percent (50%) of the second searcher resources, and the second portion is fifty percent (50%) of the second searcher resources. In some implementations, the first portion is two-thirds (2 / 3) of the second searcher resources, and the second portion is one-third (1 / 3) of the second searcher resources.

[0204] In some implementations, the first portion of the second searcher resource and the second portion of the second searcher resource are allocated according to a predetermined ratio.

[0205] In some implementations, the high priority flag is indicated by setting the interFrequencyConfig-NoGap-r16 setting in the measurement configuration to true.

[0206] In some implementations, one or more NR PCC measurements are performed during an SSB-based Measurement Timing Configuration (SMTC) window.

[0207] In some implementations, one or more NR SCC measurements are performed during an SSB-based Measurement Timing Configuration (SMTC) window.

[0208] In some implementations, measurements of one or more LTE CCs are performed during the Effective Measurement Window (EMW).

[0209] In some implementations, method 1800 may also include performing measurements of one or more LTE CCs based on a carrier-specific scaling factor (CSSF).

[0210] In some implementations, the CSSF is the CSSFoutside_gap,i for frequency range one (FR1) SCC, which includes: 2×(NSCC_Synchronization Block (SSB) + Y + 2×NSCC_Channel State Information Reference Signal (CSIRS) + NSCC_Clear Channel Assessment (CCA)_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) for FR1-only carrier aggregation (CA); and 4×(NSCC_SSB + Y + 2×NSCC_SSB + Y + 2×NSCC_Channel State Information Reference Signal (CSIRS) + NSCC_Clear Channel Assessment (CCA)_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) for FR1 and FR2 CA. NSCC_CSIRS -1-NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)), where the primary cell (Pcell) is located in FR1; and 2×(NSCC_SSB +Y+2x NSCC_CSIRS) for FR1 and FR2 CA, where the Pcell is located in FR2.

[0211] In some implementations, the CSSF is a CSSFoutside_gap,i for frequency range two (FR2) SCCs where neighboring cell measurements are required, which includes: 4×(1+NSCC_Channel State Information Reference Signal (CSIRS)_FR2_Neighboring Cell Measurement (NCM)) for frequency range two (FR2) inter-band carrier aggregation (CA) only; and 4×(1+NSCC_CSIRS_FR2_NCM) for FR1 and FR2 CAs, where the primary cell (Pcell) is located in FR1.

[0212] In some implementations, the CSSF is a CSSFoutside_gap,i for frequency range two (FR2) SCCs where measurements of neighboring cells are not required. The CSSFoutside_gap,i includes: 2×(NSCC_SSB +Y + 2x NSCC_Channel State Information Reference Signal (CSIRS)) for frequency range two (FR2) intra-band carrier aggregation (CA) only; 4×(NSCC_SSB +Y + 2x NSCC_CSIRS - 1 - NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)) for FR2 inter-band CA only; 4×(NSCC_SSB +Y + 2x NSCC_CSIRS - 1 - NSCC_CSIRS_FR2_NCM) for FR1 and FR2 CAs, where the primary cell (Pcell) is located in FR1; and 2×(NSCC_SSB +Y + 2x NSCC_CSIRS) for FR1 and FR2 CAs, where the Pcell is located in FR2.

[0213] In some implementations, the CSSF is a CSSFoutside_gap,i for inter-frequency measurement objects (MOs) without measurement gaps, which includes: 2×(NSCC_SSB +Y + 2x NSCC_Channel State Information Reference Signal (CSIRS)) for carrier aggregation (CA) only in frequency range one (FR1); 2×(NSCC_SSB +Y + 2x NSCC_CSIRS) for intra-band carrier aggregation (CA) only in frequency range two (FR2); 4×(NSCC_SSB +Y + 2x NSCC_CSIRS -1 - NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)) for inter-band carrier aggregation (CA) only in FR2; 4×(NSCC_SSB +Y + 2x NSCC_CSIRS -1 - NSCC_CSIRS_FR2_NCM) for CA in both FR1 and FR2, where the primary cell (Pcell) is located in FR1; and for both FR1 and FR2... CA is 2×(NSCC_SSB +Y+Z+2x NSCC_CSIRS), where Pcell is located in FR2.

[0214] In some implementations, the CSSF is a CSSFoutside_gap,i for Evolved Universal Terrestrial Radio Access (E-UTRA) RAT inter-measurement objects (MOs), which includes: 2×Z for carrier aggregation (CA) only in frequency range one (FR1); 2×Z for intra-band carrier aggregation (CA) only in frequency range two (FR2); 2×Z for inter-band carrier aggregation (CA) only in FR2; 2×Z for FR1 and FR2 CA, where the primary cell (Pcell) is located in FR1; and 2×Z for FR1 and FR2 CA, where the Pcell is located in FR2.

[0215] In some implementations, the CSSF is the CSSFoutside_gap,i for frequency range one (FR1) SCC, which includes: 3×(NSCC_Synchronization Block (SSB) + Y + 2×NSCC_Channel State Information Reference Signal (CSIRS) + NSCC_Clear Channel Assessment (CCA)_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) for FR1-only carrier aggregation (CA); and 6×(NSCC_SSB + Y + 2×NSCC_SSB + Y + 2×NSCC_Channel State Information Reference Signal (CSIRS) + NSCC_Clear Channel Assessment (CCA)_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) for FR1 and FR2 CA. NSCC_CSIRS -1-NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)), where the primary cell (Pcell) is located in FR1; and 2x(NSCC_SSB +Y+2x NSCC_CSIRS) for FR1 and FR2 CA, where the Pcell is located in FR2.

[0216] In some implementations, the CSSF is a CSSFoutside_gap,i for frequency range two (FR2) SCCs where neighboring cell measurements are required, which includes: 6×(1+NSCC_Channel State Information Reference Signal (CSIRS)_FR2_Neighboring Cell Measurement (NCM)) for frequency range two (FR2) inter-band carrier aggregation (CA) only; and 6×(1+NSCC_CSIRS_FR2_NCM) for FR1 and FR2 CAs, where the primary cell (Pcell) is located in FR1.

[0217] In some implementations, the CSSF is the CSSFoutside_gap,i for frequency range two (FR2) SCCs where measurements of neighboring cells are not required. The CSSFoutside_gap,i includes: 3×(NSCC_SSB +Y+2x NSCC_Channel State Information Reference Signal (CSIRS)) for frequency range two (FR2) intra-band carrier aggregation (CA) only; 6×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)) for FR2 inter-band CA only; 6×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_NCM) for FR1 and FR2 CAs, where the primary cell (Pcell) is located in FR1; and 3×(NSCC_SSB +Y+2x NSCC_CSIRS) for FR1 and FR2 CAs, where the Pcell is located in FR2.

[0218] In some implementations, the CSSF is a CSSFoutside_gap,i for inter-frequency measurement objects (MOs) without measurement gaps, which includes: 3×(NSCC_SSB +Y + 2x NSCC_Channel State Information Reference Signal (CSIRS)) for carrier aggregation (CA) only in frequency range one (FR1); 3×(NSCC_SSB +Y + 2x NSCC_CSIRS) for intra-band carrier aggregation (CA) only in frequency range two (FR2); 6×(NSCC_SSB +Y + 2x NSCC_CSIRS - 1 - NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)) for inter-band carrier aggregation (CA) only in FR2; 6×(NSCC_SSB +Y + 2x NSCC_CSIRS - 1 - NSCC_CSIRS_FR2_NCM) for CA in both FR1 and FR2, where the primary cell (Pcell) is located in FR1; and for both FR1 and FR2... CA is 3×(NSCC_SSB +Y+Z+2x NSCC_CSIRS), where Pcell is located in FR2.

[0219] In some implementations, the CSSF is a CSSFoutside_gap,i for Evolved Universal Terrestrial Radio Access (E-UTRA) RAT inter-measurement objects (MOs), which includes: a cell (1.5×Z) for frequency range one (FR1) carrier aggregation (CA) only; a cell (1.5×Z) for frequency range two (FR2) intra-band carrier aggregation (CA) only; a cell (1.5×Z) for FR2 inter-band carrier aggregation (CA) only; a cell (1.5×Z) for FR1 and FR2 CA, wherein the primary cell (Pcell) is located in FR1; and a cell (1.5×Z) for FR1 and FR2 CA, wherein the Pcell is located in FR2.

[0220] In some implementations, method 1800 may further include performing measurements of one or more LTE CCs according to CSSF, wherein: for inter-band CA of FR1 and FR2 (FR1+FR2), only one frequency range one (FR1) operating band and one FR2 operating band are included, and for inter-band carrier aggregation (CA) of FR2, only two NR FR2 operating bands are included; the SCC in FR2 from which neighboring cell measurements are required is selected; if only one SCell is configured and there is no gapless inter-frequency MO and only SSB-based Layer 3 (L3) measurements are configured on the SCC, then CSSFoutside_gap,i equals one (1), or if only one SCell is configured and there is no gapless inter-frequency MO and L3 measurements based on both SSB and Channel State Information Reference Signal (CSI-RS) are configured on the SCC or only CSI-RS-based L3 measurements are configured, then CSSFoutside_gap,i equals two (2); Y is The number of inter-frequency measurement objects (MOs) configured for measurement outside the MG without MG, or Y is 0; if the primary component carrier (PCC) is configured with L3 measurements based on both SSB and CSI-RS or L3 measurements based only on CSI-RS, then the number of primary component carriers (NPCC)_channel state information reference signal (NPCC_CSIRS) is equal to one (1), or NPCC_CSIRS is equal to zero (0); NSCC_SSB is one or more secondary cells (SCells) configured with only SSB-based L3 measurements and measured without measurement gaps (MG). ; NSCC_Channel State Information Reference Signal (NSCC_CSIRS) is one or more SCells configured with both SSB-based and Channel State Information Reference Signal (CSI-RS) L3 measurements, or only CSI-RS-based L3 measurements; NSCC_CCA_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) (NSCC_CCA_RSSI / CO) is a SCell configured with RSSI or CO measurements but without MG when the Residual Minimum System Information (RMSI) Measurement Timing Configuration (RMTC) and SSB-based Measurement Timing Configuration (SMTC) overlap. The number of measurement objects (MOs) of one or more SCells; if the SCC is located in an FR2 in which neighboring cell measurements are required and is configured with both SSB and CSI-RS or only CSI-RS measurements, then NSCC_CSIRS_Frequency Range II (FR2)_NCM(NSCC_CSIRS_FR2_NCM) equals one (1), or NSCC_CSIRS_FR2_NCM equals zero (0); and Z is the number of MOs between Evolved Universal Terrestrial Radio Access (E-UTRA) RATs configured to be measured outside the MG without the MG, or Z equals zero (0).

[0221] In some implementations, method 1800 may further include encoding UE capability information for transmission to the network, the UE capability information indicating the support of a dedicated searcher for measurements of one or more LTE CCs.

[0222] In some implementations, method 1800 may further include allocating a third portion of the second searcher resources for measurements of one or more LTE CCs of a dedicated searcher.

[0223] In some implementations, method 1800 may also include performing measurements of one or more LTE CCs based on a carrier-specific scaling factor (CSSF).

[0224] In some implementations, CSSF is CSSFoutside_gap,i for E-UTRA RAT inter-measurement objects (MOs), which includes: Z for frequency range one (FR1) carrier aggregation (CA) only; Z for frequency range two (FR2) intra-band carrier aggregation (CA) only; Z for FR2 inter-band carrier aggregation (CA) only; Z for FR1 and FR2 CAs, where the primary cell (Pcell) is located in FR1; and Z for FR1 and FR2 CAs, where the Pcell is located in FR2, where Z is the number of configured E-UTRA RAT inter-measurement objects (MOs) measured outside the MG without the MG, or Z equals zero (0).

[0225] In some embodiments, an apparatus is disclosed that is configured to cause a user equipment (UE) to perform any operation of method 1800.

[0226] In some embodiments, an apparatus is disclosed that is configured to cause a base station to perform any operation of method 1800.

[0227] In some embodiments, an apparatus is disclosed that is configured to cause a user equipment (UE) to perform any operation of method 1800 and / or the operation of method 1800.

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

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

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

[0231] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X sent by the base station, and interpreting each message / signal Y sent by the UE in the uplink as a message / signal Y received by the base station, any of the methods described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.

[0232] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. A method for performing Long Term Evolution (LTE) measurements between Radio Access Technologies (RATs) without measurement gaps by a User Equipment (UE), the method comprising: Decode the high priority flag received from the network, which indicates that the measurement of one or more LTE component carriers (LTE CCs) should be prioritized over the measurement of one or more New Radio (NR) Secondary Component Carriers (NR SCCs); Allocate the first searcher resources for measurements of one or more new radio main component carriers (NR PCCs); The first portion of the second searcher resources is allocated for the measurement of the one or more LTECCs based on the high priority flag, and the second portion of the second searcher resources is allocated for the measurement of the one or more NR SCCs, wherein the first portion is greater than or equal to the second portion; The measurements of the one or more LTE CCs are performed using the first portion of the second searcher resources without using the measurement gap; as well as The measurement of the one or more NR SCCs is performed using the second portion of the second searcher resource.

2. The method of claim 1, wherein the first portion is fifty percent (50%) of the second searcher resources, and the second portion is fifty percent (50%) of the second searcher resources.

3. The method of claim 1, wherein the first portion is two-thirds (2 / 3) of the second searcher resource, and the second portion is one-third (1 / 3) of the second searcher resource.

4. The method of claim 1, wherein the first portion of the second searcher resource and the second portion of the second searcher resource are allocated according to a predetermined ratio.

5. The method of claim 1, wherein the high priority flag is indicated by setting the interFrequencyConfig-NoGap-r16 of the measurement configuration to true.

6. The method of claim 1, wherein the measurement of the one or more NR PCCs is performed during an SSB-based Measurement Timing Configuration (SMTC) window.

7. The method of claim 1, wherein the measurement of the one or more NR SCCs is performed during an SSB-based Measurement Timing Configuration (SMTC) window.

8. The method of claim 1, wherein the measurement of the one or more LTE CCs is performed during an effective measurement window (EMW).

9. The method of claim 1, further comprising performing the measurement of the one or more LTE CCs according to a carrier-specific scaling factor (CSSF).

10. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range of one (FR1) SCC, the CSSFoutside_gap,i comprising: For FR1 carrier aggregation (CA) only, 2×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2xNSCC - Channel State Information Reference Signal (CSIRS) + NSCC - Idle Channel Assessment (CCA) - Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO); For FR1 and FR2 CA, 4×(NSCC_SSB +Y+2) NSCC_CSIRS -1-NSCC_CSIRS_Frequency Range 2 (FR2)_Neighboring Cell Measurement (NCM)), wherein the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 2×(NSCC_SSB +Y+2x NSCC_CSIRS), where the Pcell is located in FR2.

11. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range two (FR2) SCC in which measurements of neighboring cells are required, the CSSFoutside_gap,i comprising: For frequency range two (FR2) inter-band carrier aggregation (CA) only, the number of SCells configured in the 4×(1+) configuration (N) SCC Channel State Information Reference Signal (CSIRS) FR2 Neighboring Cell Measurement (NCM)); and For FR1 and FR2 CA, 4x(1+NSCC_CSIRS_FR2_NCM) is used, where the primary cell (Pcell) is located in FR1.

12. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range two (FR2) SCC in which measurements of neighboring cells are not required, the CSSFoutside_gap,i comprising: For frequency range two (FR2) in-band carrier aggregation (CA) only, 2×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2x NSCC Channel State Information Reference Signal (CSIRS) For FR2 inter-band CA only, 4×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_Neighboring cell measurement (NCM)); For FR1 and FR2 CA, 4×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_NCM), where the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 2×(NSCC_SSB +Y+2x NSCC_CSIRS), where the Pcell is located in FR2.

13. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for an inter-frequency measurement object (MO) without a measurement gap, the CSSFoutside_gap,i comprising: For frequency range only (FR1) carrier aggregation (CA) 2×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2x NSCC Channel State Information Reference Signal (CSIRS) For in-band carrier aggregation (CA) only in frequency range 2 (FR2), 2×(NSCC_SSB +Y+2x NSCC_CSIRS); For FR2 inter-band carrier aggregation (CA) only, 4×(NSCC_SSB +Y+2x NSCC_CSIRS -1- NSCC_CSIRS_FR2_Neighboring cell measurement (NCM)); For FR1 and FR2 CA, 4×(NSCC_SSB +Y+2x NSCC_CSIRS -1- NSCC_CSIRS_ FR2_NCM), where the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 2×(NSCC_SSB +Y+Z+2x NSCC_CSIRS), where the Pcell is located in FR2.

14. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for an Evolved Universal Terrestrial Radio Access (E-UTRA) RAT inter-measurement object (MO), the CSSFoutside_gap,i comprising: For 2×Z of carrier aggregation (CA) with only frequency range one (FR1); For 2×Z only in-band carrier aggregation (CA) within frequency range two (FR2); For 2×Z only FR2 inter-band carrier aggregation (CA); For 2×Z of FR1 and FR2 CA, where the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA 2×Z, wherein the Pcell is located in FR2.

15. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range of one (FR1) SCC, the CSSFoutside_gap,i comprising: For FR1 carrier aggregation (CA) only, 3×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2xNSCC - Channel State Information Reference Signal (CSIRS) + NSCC - Idle Channel Assessment (CCA) - Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO); For FR1 and FR2 CA, 6×(NSCC_SSB +Y+2) NSCC_CSIRS-1-NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)), wherein the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 2×(NSCC_SSB +Y+2x NSCC_CSIRS), where the Pcell is located in FR2.

16. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range two (FR2) SCC in which measurements of neighboring cells are required, the CSSFoutside_gap,i comprising: For frequency range two (FR2) inter-band carrier aggregation (CA) only, the number of SCells configured in the 6×(1+) configuration (N) SCC Channel State Information Reference Signal (CSIRS) FR2 Neighboring Cell Measurement (NCM)); and For FR1 and FR2 CA, 6x(1+NSCC_CSIRS_FR2_NCM) are used, where the primary cell (Pcell) is located in FR1.

17. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for a frequency range two (FR2) SCC in which measurements of neighboring cells are not required, the CSSFoutside_gap,i comprising: For frequency range two (FR2) in-band carrier aggregation (CA) only, 3×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2x NSCC Channel State Information Reference Signal (CSIRS) For FR2 inter-band CA only, 6×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_Neighboring Cell Measurement (NCM)); For FR1 and FR2 CA, 6×(NSCC_SSB +Y+2x NSCC_CSIRS - 1-NSCC_CSIRS_FR2_NCM), where the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 3×(NSCC_SSB +Y+2x NSCC_CSIRS), where the Pcell is located in FR2.

18. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for an inter-frequency measurement object (MO) without a measurement gap, the CSSFoutside_gap,i comprising: For frequency range only (FR1) carrier aggregation (CA) 3×(number of configured SCells (N) SCC Synchronization Signal Block (SSB) + Y + 2x NSCC Channel State Information Reference Signal (CSIRS) For in-band carrier aggregation (CA) only in frequency range 2 (FR2), 3×(NSCC_SSB +Y+2x NSCC_CSIRS); For FR2 inter-band carrier aggregation (CA) only, 6×(NSCC_SSB +Y+2x NSCC_CSIRS -1- NSCC_CSIRS_FR2_Neighboring cell measurement (NCM)); For FR1 and FR2 CA, 6×(NSCC_SSB +Y+2x NSCC_CSIRS -1- NSCC_CSIRS_ FR2_NCM), where the primary cell (Pcell) is located in FR1; and For FR1 and FR2 CA, 3×(NSCC_SSB +Y+Z+2x NSCC_CSIRS), where the Pcell is located in FR2.

19. The method of claim 9, wherein the CSSF is a CSSFoutside_gap,i for an Evolved Universal Terrestrial Radio Access (E-UTRA) RAT inter-measurement object (MO), the CSSFoutside_gap,i comprising: For cell (1.5×Z) with only frequency range one (FR1) carrier aggregation (CA); For cell (1.5×Z) with in-band carrier aggregation (CA) only in frequency range two (FR2); For cells (1.5×Z) with only FR2 inter-band carrier aggregation (CA); For cells (1.5×Z) of FR1 and FR2 CA, where the primary cell (Pcell) is located in FR1; and For cells (1.5×Z) of FR1 and FR2 CA, wherein the P cell is located in FR2.

20. The method of claim 9, further comprising performing the measurement of the one or more LTE CCs according to the CSSF, wherein: For inter-band CA of FR1 and FR2 (FR1+FR2), only one frequency range one (FR1) operating frequency band and one FR2 operating frequency band are included, and for inter-band carrier aggregation (CA) of FR2, only two NR FR2 operating frequency bands are included; Select the secondary component carrier (SCC) in the FR2 that requires neighboring cell measurements. If only one SCell is configured and there is no gapless inter-frequency MO and only SSB-based Layer 3 (L3) measurement is configured on the SCC, then CSSFoutside_gap,i equals one (1), or if only one SCell is configured and there is no gapless inter-frequency MO and L3 based on both SSB and Channel State Information Reference Signal (CSI-RS) is configured on the SCC or only CSI-RS-based L3 measurement is configured, then CSSFoutside_gap,i equals two (2). Y is the number of measurement objects (MOs) between frequencies of the configuration measured outside the MG in the absence of the MG, or Y is 0; If the primary component carrier (PCC) is configured with L3 measurements based on both SSB and CSI-RS, or L3 measurements based solely on CSI-RS, then the number of primary cells configured (N) PCC Channel State Information Reference Signal (N) PCC _CSIRS) equals one (1), or the N PCC _CSIRS equals zero (0); The number of secondary component carriers (NSCC) - Synchronization signal block (SSB) is one or more secondary cells (SCells) that are only configured with SSB-based layer 3 (L3) measurements and are measured without measurement gaps (MG). N SCC The Channel State Information Reference Signal (NSCC_CSIRS) is one or more SCells configured with L3 measurements based on both SSB and Channel State Information Reference Signal (CSI-RS) or only L3 measurements based on CSI-RS. The NSCC_CCA_Received Signal Strength Indicator (RSSI) / Channel Occupancy (CO) (NSCC_CCA_RSSI / CO) is the number of measurement objects (MOs) of one or more SCells that are configured with RSSI or CO measurements but do not have MG when the Remaining Minimum System Information (RMSI) Measurement Timing Configuration (RMTC) and the SSB-based Measurement Timing Configuration (SMTC) overlap. If the SCC is located in the FR2 in which neighboring cell measurements are required and is configured with both the SSB and the CSI-RS or only CSI-RS measurements, then NSCC_CSIRS_Frequency Range II (FR2)_NCM(NSCC_CSIRS_FR2_NCM) equals one (1), or NSCC_CSIRS_FR2_NCM equals zero (0); and Z is the number of MOs between Evolved Universal Terrestrial Radio Access (E-UTRA) RATs in the absence of MGs, or Z equals zero (0).

21. The method of claim 1, further comprising encoding UE capability information for transmission to the network, the UE capability information indicating support of a dedicated searcher for the measurement of the one or more LTE CCs.

22. The method of claim 21, further comprising allocating a third portion of the second searcher resources for the measurement of the one or more LTE CCs of the dedicated searcher.

23. The method of claim 22, further comprising performing the measurement of the one or more LTE CCs according to a carrier-specific scaling factor (CSSF).

24. The method of claim 23, wherein the CSSF is a CSSFoutside_gap,i for an E-UTRA RAT inter-measurement object (MO), the CSSFoutside_gap,i comprising: For Z-band carrier aggregation (CA) with only frequency range one (FR1); For Z-band carrier aggregation (CA) within frequency range two (FR2) only; Z is for FR2 inter-band carrier aggregation (CA) only; Z for FR1 and FR2 CA, where the primary cell (Pcell) is located in FR1; and For Z in FR1 and FR2 CA, where the Pcell is located in FR2, Z is the number of objects (Mo) measured between E-UTRA RATs in the configuration without MG, or Z equals zero (0).

25. A user equipment (UE), the user equipment (UE) comprising: One or more processors coupled to memory, the one or more processors being configured to perform one or more methods according to claims 1 to 24.

26. A baseband processor configured to perform one or more of the methods according to claims 1 to 24.

27. A user equipment (UE), the user equipment (UE) comprising: One or more processors, said one or more processors coupled to memory, said one or more processors being configured to: Decode the high priority flag received from the network, which indicates that the measurement of one or more LTE component carriers (LTE CCs) should be prioritized over the measurement of one or more New Radio (NR) Secondary Component Carriers (NR SCCs); Allocate the first searcher resources for measurements of one or more new radio main component carriers (NR PCCs); The first portion of the second searcher resources is allocated for the measurement of the one or more LTECCs based on the high priority flag, and the second portion of the second searcher resources is allocated for the measurement of the one or more NR SCCs, wherein the first portion is greater than or equal to the second portion; The measurements of the one or more LTE CCs are performed using the first portion of the second searcher resources without using the measurement gap; as well as The measurement of the one or more NR SCCs is performed using the second portion of the second searcher resource.

28. An apparatus for a base station, the apparatus comprising: One or more processors, said one or more processors coupled to memory, said one or more processors being configured to: For user equipment (UE), prioritize measurements of one or more Long Term Evolution (LTE) component carriers (LTE CCs) relative to measurements of one or more New Radio (NR) secondary component carriers (NR SCCs); A high-priority flag is encoded and sent to the UE, the high-priority flag indicating that the measurement of the one or more LTE CCs is given priority over the measurement of the one or more NR SCCs; as well as Configuration information for the measurements of the one or more LTE CCs and the one or more NR SCCs is encoded and transmitted to the UE, wherein the configuration information includes: Indication of the first searcher resource for measurements of one or more new radio main component carriers (NR PCCs), and Indication of a second searcher resource for the measurement of the one or more LTE CCs and the measurement of the one or more NR SCCs, wherein, based on the high priority flag, a first portion of the second searcher resource is allocated for the measurement of the one or more LTE CCs and a second portion of the second searcher resource is allocated for the measurement of the one or more NR SCCs, and wherein the first portion is greater than or equal to the second portion.

29. A user equipment (UE) configured to perform any of the operations described herein.

30. A base station configured to perform any of the operations described herein.

31. A computer program product comprising computer instructions that, when executed by one or more processors, perform any of the operations described herein.

Images