Managing downlink traffic reception and cross-link interference

Abstract

In wireless devices configured to perform methods and apparatuses for managing downlink traffic reception and cross-link interference (CLI), a wireless device can receive physical downlink control channel (PDCCH) traffic from a base station using a first receive (Rx) resource tuning of an Rx resource, determine whether a time period between an end of the PDCCH traffic and a beginning of a CLI measurement occasion exceeds a threshold duration for tuning the Rx resource to a second Rx resource tuning, and can receive downlink traffic using the first Rx resource tuning in response to determining that the time period between the end of the PDCCH traffic and the beginning of the CLI measurement occasion is less than or equal to the threshold duration.

Description

Background Technology

[0001] Cross-link interference (CLI) can occur when a first wireless device (sometimes referred to as the "interference source") transmits an uplink signal while a nearby second wireless device (sometimes referred to as the "victim") attempts to receive a downlink signal, if the uplink signal symbol of the first wireless device conflicts with at least one downlink signal symbol of the second wireless device. CLI can occur between wireless devices communicating in the same cell or different cells. The base station can schedule resources for the victim wireless device to measure the CLI from the interference source wireless device and provide reports to the base station regarding the measured CLI. Typically, the interference source wireless device does not transmit special signals to facilitate CLI measurement, and the interference source wireless device is typically unaware that its uplink transmission is being measured by the victim wireless device. Summary of the Invention

[0002] The aspects include a method performed by a wireless device configured to perform management of downlink traffic reception and cross-link interference. The aspects may include: receiving physical downlink control channel (PDCCH) traffic from a base station using a first Rx resource tuner with receive (Rx) resources; determining whether a time period between the end of the PDCCH traffic and the beginning of a CLI measurement timing exceeds a threshold duration for tuning the Rx resources to a second Rx resource tuner; and receiving downlink traffic using the first Rx resource tuner in response to determining that the time period between the end of the PDCCH traffic and the beginning of the CLI measurement timing is less than or equal to the threshold duration.

[0003] In some aspects, the downlink service may include Physical Downlink Shared Channel (PDSCH) service or Channel State Information Reference Signal (CSI-RS). Some aspects may include: determining whether the CLI measurement timing overlaps with the downlink service in response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration; and receiving the downlink service using the first Rx resource tuning in response to determining that the CLI measurement timing overlaps with the downlink service. Some aspects may include: performing CLI measurements using the second Rx resource tuning during the CLI measurement timing in response to determining that the CLI measurement timing does not overlap with the downlink service. Some aspects may include: performing CLI measurements using the second Rx resource tuning during a subsequent CLI measurement timing that does not conflict with subsequent downlink service.

[0004] In some aspects, receiving the downlink service using the first Rx resource tuning in response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing is less than or equal to the threshold duration may include: using the second Rx resource tuning to begin the CLI measurement; determining, based on the decoded PDCCH service, whether a second time period from the end of the PDCCH service to the beginning of the downlink service exceeds a second threshold duration; and receiving the downlink service using the first Rx resource tuning before completing the CLI measurement in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration. Some aspects may include: using the second Rx resource tuning to complete the CLI measurement in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration.

[0005] A further aspect includes a wireless device having a processor configured to perform one or more operations of any of the methods summarized above. A further aspect includes a processing device for use in a wireless device configured to have processor-executable instructions for performing operations of any of the methods summarized above. A further aspect includes a non-transitory processor-readable storage medium having processor-executable instructions stored thereon configured to cause the processor of the wireless device to perform operations of any of the methods summarized above. A further aspect includes a wireless device having units with functionality for performing any of the methods summarized above.

[0006] The aspects include methods performed by a base station configured to perform management of downlink traffic reception and cross-link interference. The aspects may include receiving a capability report from a radio device indicating that the radio device is configured to determine whether a time period between the end of a Physical Downlink Control Channel (PDCCH) service and the beginning of a Cross-Link Interference (CLI) measurement timing exceeds a threshold duration, and, in response to determining that the radio device is not configured to determine whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, scheduling downlink services for the radio device that do not overlap with the CLI measurement timing.

[0007] In some aspects, the capability report may indicate whether the wireless device is configured to determine whether to switch to the second Rx resource and perform CLI measurements by determining whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration. In some aspects, the downlink service may include Physical Downlink Shared Channel (PDSCH) service or Channel State Information Reference Signal (CSI-RS). Some aspects may include: in response to determining that the wireless device is configured to determine whether the time period between the end of the PDCCH service and the CLI measurement timing exceeds the threshold duration, scheduling the PDCCH service and the CLI measurement timing to be at least separated by the threshold duration.

[0008] In some aspects, the capability report indicates whether the wireless device is configured to determine whether a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to a second threshold duration. Such an aspect may further include scheduling the downlink service for at least the second threshold duration after the end of the PDCCH service in response to determining that the wireless device is configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

[0009] Some aspects may also include scheduling the downlink service to avoid overlapping with the CLI measurement timing in response to determining that the wireless device is not configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration. In some aspects, the capability report may indicate whether the wireless device is configured to abort the CLI measurement in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

[0010] A further aspect includes a base station having a processor configured to perform one or more operations of any of the methods summarized above. A further aspect includes a processing device for use in a base station configured to have processor-executable instructions for performing operations of any of the methods summarized above. A further aspect includes a non-transitory processor-readable storage medium having processor-executable instructions stored thereon configured to cause the base station's processor to perform operations of any of the methods summarized above. A further aspect includes a base station having units with functionality for performing any of the methods summarized above. Attached Figure Description

[0011] Figure 1 This is a system block diagram illustrating an example communication system suitable for implementing various embodiments.

[0012] Figure 2 This is a component block diagram illustrating an example computing and wireless modem system suitable for implementing various embodiments.

[0013] Figure 3 This is a component block diagram illustrating the software architecture of a radio protocol stack for the user plane and control plane, which is suitable for implementing various embodiments of wireless communication.

[0014] Figure 4A and Figure 4B This is a component block diagram illustrating an example system 400 suitable for implementing various embodiments.

[0015] Figure 5A , Figure 5B and Figure 5C This is a conceptual diagram illustrating various aspects of the operation 500a-500c of the method for managing downlink service reception and CLI according to various embodiments.

[0016] Figure 6A This is a flowchart illustrating a method executed by a processor of a wireless device, according to various embodiments, for enhancing coverage for managing downlink traffic reception and CLI.

[0017] Figure 6B and Figure 6C This is a process flowchart illustrating operations that can be executed by a processor of a wireless device as part of a method for enhancing coverage for managing downlink traffic reception and CLI, according to various embodiments.

[0018] Figure 7A This is a flowchart illustrating a method executed by a base station processor according to various embodiments for enhancing coverage for managing downlink service reception and CLI.

[0019] Figure 7B This is a flowchart illustrating the process of operations that can be executed by the processor of a base station as part of a method for managing downlink service reception and CLI, according to various embodiments.

[0020] Figure 8 This is a component block diagram of a base station computing device suitable for use with various embodiments.

[0021] Figure 9 This is a component block diagram suitable for use with various embodiments of a wireless device. Detailed Implementation

[0022] Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0023] Various embodiments include methods for managing downlink traffic reception and cross-link interference (CLI), and wireless devices and base stations configured to perform said methods. These embodiments enable the wireless devices and base stations to dynamically manage reception of downlink traffic (such as Physical Downlink Shared Channel (PDSCH) data or messages or Channel State Information (CSI) Reference Signals (CSI-RS)) and CLI measurements performed by the wireless devices. These embodiments prioritize downlink traffic reception over CLI measurements and dynamically manage reception of such downlink traffic to enable the wireless devices to improve downlink traffic throughput and perform CLI measurements.

[0024] The term "wireless device" as used herein refers to one or more of the following: wireless router devices, wireless appliances, cellular phones, smartphones, portable computing devices, personal or mobile multimedia players, laptops, tablets, smartbooks, ultrabooks, PDAs, wireless email receivers, internet-enabled multimedia cellular phones, medical devices and equipment, biometric sensors / devices, wearable devices (including smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings and smart bracelets)), entertainment devices (e.g., wireless game controllers, music and video players, satellite radio units, etc.), and other types of user equipment (UE), as well as Internet of Things (IoT) devices that support wireless networks (including smart meters / sensors, industrial manufacturing equipment, large and small machinery and appliances for home or business use), wireless communication units within automated and semi-automated vehicles, wireless devices attached to or integrated into various mobile platforms, GPS devices, and similar electronic devices including memory, wireless communication components, and programmable processors.

[0025] The term "System-on-a-Chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip containing multiple resources or processors integrated on a single substrate. A single SOC can contain circuitry for digital, analog, mixed-signal, and radio frequency functions. A single SOC can also include any number of general-purpose or special-purpose processors (digital signal processors, modem processors, video processors, etc.), memory blocks (such as ROM, RAM, flash memory, etc.), and resources (such as timers, regulators, oscillators, etc.). A SOC can also include resources and processors for controlling the integration, as well as software for controlling peripheral devices.

[0026] The term "system-in-package" (SIP) may be used herein to refer to a single module or package that contains multiple resources, computing units, cores, or processors on two or more IC chips, substrates, or SoCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged onto a uniform substrate. A SIP may also include multiple independent SoCs coupled together and packaged close to each other via high-speed communication circuitry (e.g., on a single motherboard or in a single wireless device). Proximity of SoCs facilitates high-speed communication and the sharing of memory and resources.

[0027] As used herein, the terms “network,” “system,” “wireless network,” “cellular network,” and “wireless communication network” can be used interchangeably to refer to part or all of a wireless network associated with a wireless device and / or a carrier customized on the wireless device. The techniques described herein can be used in a variety of wireless communication networks, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), FDMA, Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Long Term Evolution (LTE), 5G, New Radio (NR), and others. Typically, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support at least one radio access technology, which can operate on one or more frequencies or frequency ranges. For example, a CDMA network can implement Universal Terrestrial Radio Access (UTRA) (including the Wideband Code Division Multiple Access (WCDMA) standard), CDMA2000 (including the IS-2000, IS-95, and / or IS-856 standards), etc. In another example, a TDMA network can implement GSM Enhanced Data Rate (EDGE) for GSM evolution. In another example, OFDMA networks can implement evolved UTRA (E-UTRA) (including the LTE standard), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, and flash. Etc. Reference can be made to wireless networks using the LTE standard; therefore, the terms "Evolved Universal Terrestrial Radio Access," "E-UTRAN," and "eNodeB" ("Evolved Node B") may be used interchangeably herein to refer to wireless networks. However, such references are provided by way of example only and are not intended to exclude wireless networks using other communication standards. For example, while various third-generation (3G), fourth-generation (4G), and fifth-generation (5G) systems are discussed herein, those systems are cited only as examples, and future generations of systems (e.g., sixth-generation (6G) or higher) may be used as alternatives in the various examples.

[0028] In LTE, 5G, NR, and other communication technologies, CLI (Collision Limitation Event) can occur when an aggressor radio device transmits uplink signals while a nearby victim radio device attempts to receive downlink traffic. One or more uplink symbols from the aggressor radio device's uplink signaling may collide with at least one downlink signal symbol from the victim radio device (i.e., during the overlap period). CLI can occur between radio devices communicating in the same cell or in different cells.

[0029] The base station can schedule resources for the victim wireless device (generally referred to herein as the second wireless device) to measure CLI from the interfering wireless device (generally referred to herein as the first wireless device), and to provide reports on the measured CLI to the base station. Typically, the interfering wireless device does not send special signals to facilitate CLI measurement, and the interfering wireless device is typically unaware that its uplink transmissions are being measured by the victim wireless device.

[0030] By convention, for example in 3GPP Release 16, radio devices are statically configured to prioritize CLI measurements over receiving downlink traffic directed at the radio device (such as Physical Downlink Control Channel (PDCCH) traffic, PDSCH messages or data, or CSI-RS). Reception of PDCCH traffic is typically less affected by the radio device prioritizing CLI measurements because the control area (where PDCCH traffic resides) typically occurs at the beginning of a time slot. CLI measurements typically measure the source radio device's transmission of Sounding Reference Signals (SRS) and / or uplink signaling, which does not occur at the beginning of a time slot and has a greater chance of conflicting with the victim radio device's reception of PDSCH traffic and / or CSI-RS in the downlink.

[0031] As used herein, the receive (Rx) chain circuitry system of a wireless device is referred to as an "Rx resource". As used herein, the configuration of an Rx resource used to receive downlink traffic or measure CLI is referred to as "Rx resource tuning". As used herein, the term "traffic" generally refers to signals, messages, data, and / or other information.

[0032] Wireless devices typically perform CLI measurements on resources (e.g., frequencies and channels) that are different from those used for downlink traffic reception. For a wireless device with a single Rx resource, measuring CLI and receiving downlink traffic requires the wireless device to tune its Rx chain circuitry to different tuning configurations, and for such a wireless device, it is not possible to simultaneously measure CLI and receive downlink traffic. If a conflict arises between CLI measurement timing and downlink signal reception timing, conventional wireless devices prioritize CLI measurement at the expense of downlink signal reception, which degrades downlink traffic reception performance and throughput.

[0033] Various embodiments include methods for managing the reception of downlink traffic (e.g., PDSCH messages or data and CSI-RS) and performing and reporting CLI measurements, and wireless devices and base stations configured to perform said methods. In some embodiments, the wireless device may be configured to dynamically prioritize downlink signaling reception over performing CLI measurements.

[0034] In various embodiments, the wireless device may receive PDCCH services from the base station using a first Rx resource tuning of its Rx resources. The wireless device may determine whether the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds a threshold duration for tuning the Rx resources to a second Rx tuning. In response to determining that the time period between the end of the PDCCH service and the next CLI measurement opportunity does not exceed (i.e., is less than or equal to) the threshold duration, the wireless device may use the first Rx resource tuning to receive downlink services. In some embodiments, in response to determining that the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds the threshold duration, the wireless device may tune its Rx resources to a second Rx resource tuning and perform a CLI measurement during the CLI measurement opportunity.

[0035] In some embodiments, the duration of the first threshold reflects the time required for the wireless device to decode PDCCH traffic (e.g., one or more samples of PDCCH or one or more PDCCH candidates) and switch the tuning of the wireless device's Rx resources from a first Rx resource tuning to a second Rx resource tuning. In some embodiments, the wireless device may use the first Rx resource tuning to receive PDCCH traffic and downlink traffic (e.g., PDSCH messages or data and / or CSI-RS). In some embodiments, the wireless device may use the second Rx resource tuning to perform CLI measurements of SRS against, for example, nearby interfering wireless devices.

[0036] In some embodiments, in response to determining that the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds a threshold duration, the wireless device may determine whether the next CLI measurement opportunity overlaps with the next downlink service. The wireless device may use a first Rx resource tuning to receive the downlink service in response to determining that the next CLI measurement opportunity overlaps with the next downlink service. In response to determining that the next CLI measurement opportunity does not overlap with the next downlink service, the wireless device may use a second Rx resource tuning to perform the CLI measurement during the next CLI measurement opportunity. In some embodiments, the wireless device may perform the CLI measurement during the next CSI measurement opportunity that does not conflict with (e.g., overlap or conflict with) the downlink service. In some embodiments, the wireless device may use a second Rx resource tuning to perform the CLI measurement during a subsequent CLI measurement opportunity that does not conflict with any downlink service.

[0037] In some embodiments, the wireless device may be configured to dynamically prioritize downlink service reception over performing CLI measurements, tune Rx resources to a second Rx resource to perform CLI measurements, and tune Rx resources to a first Rx resource to receive downlink services, using a first threshold duration and a second threshold duration that reflect the time required for the wireless device to decode PDCCH services.

[0038] In some embodiments, the wireless device may use a second Rx resource tuning to initiate CLI measurements. In some embodiments, the wireless device may continue decoding PDCCH traffic (e.g., buffered or stored in the wireless device's memory) while performing CLI measurements. In some embodiments, when the wireless device has decoded a sufficient number of PDCCH traffic, the wireless device may (based on the decoded PDCCH traffic) determine whether a second time period from the end of the PDCCH signaling to the beginning of the downlink traffic exceeds a second threshold duration. In some embodiments, the wireless device may, in response to determining that the second time period from the end of the PDCCH traffic to the beginning of the downlink traffic does not exceed (i.e., is less than or equal to) the second threshold duration, use a first Rx resource tuning to receive downlink traffic before completing CLI measurements. In some embodiments, the wireless device may, in response to determining that the second time period from the end of the PDCCH traffic to the beginning of the downlink traffic does not exceed (i.e., is less than or equal to) the second threshold duration, abort CLI measurements. In some embodiments, the wireless device may use a second Rx resource tuning to perform CLI measurement in response to determining that a second time period from the end of the PDCCH service to the beginning of the downlink service exceeds a second threshold duration.

[0039] In various embodiments, the base station may be configured to schedule or adjust the scheduling of downlink traffic and / or CLI measurement resources that a wireless device can use to measure CLI. In various embodiments, the base station may receive capability reports from the wireless device indicating whether the wireless device is configured to determine whether the time period between the end of a PDCCH service and the next CLI measurement opportunity exceeds a threshold duration. In response to determining that the wireless device is not configured to determine whether the time period between the end of a PDCCH service and the next CLI measurement opportunity exceeds a threshold duration, the base station may schedule downlink traffic for the wireless device that does not overlap with the next or subsequent CLI measurement opportunity. In response to determining that the wireless device is configured to determine whether the time period between the end of a PDCCH service and the next CLI measurement opportunity exceeds a threshold duration, the base station may schedule the PDCCH service and the next CLI measurement opportunity at least (e.g., relative to each other) a threshold duration apart. In some embodiments, the base station may determine or adjust the timing or scheduling of the PDCCH service and / or the next CLI measurement opportunity. In some embodiments, the capability report may indicate whether the wireless device is configured to determine whether to switch to a second Rx resource and perform a CLI measurement by determining whether the time period between the end of PDCCH service and the next cross-link interference (CLI) measurement timing exceeds a threshold duration.

[0040] In some embodiments, a capability report from a wireless device may indicate whether the wireless device is configured to determine whether a second time period from the end of a PDCCH service to the beginning of a downlink service is less than or equal to a second threshold duration. In response to determining that the wireless device is configured to determine whether the second time period from the end of a PDCCH service to the beginning of a downlink service is less than or equal to the second threshold duration, the base station may schedule the downlink service for at least the second threshold duration following the end of the PDCCH service. In some embodiments, the base station may schedule the downlink service in response to determining that the wireless device is not configured to determine whether the second time period from the end of a PDCCH service to the beginning of a downlink service is less than or equal to the second threshold duration, so as not to overlap with the next CLI measurement timing. In some embodiments, a capability report may indicate whether the wireless device is configured to abort CLI measurements in response to determining that the second time period from the end of a PDCCH service to the beginning of a downlink service is less than the second threshold duration.

[0041] Figure 1 This is a system block diagram illustrating an example communication system 100 suitable for implementing various embodiments. Communication system 100 may be a 5G New Radio (NR) network, or any other suitable network such as a Long Term Evolution (LTE) network. Although Figure 1 The description illustrates a 5G network, but subsequent generations of networks may include the same or similar elements. Therefore, references to 5G networks and 5G network elements in the following description are for illustrative purposes and are not intended to be limiting.

[0042] Communication system 100 may include a heterogeneous network architecture, which includes a core network 140 and various wireless devices. Figure 1 The wireless devices 120a-120e are shown in the diagram. The communication system 100 may also include a number of base stations (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. Base stations are entities that communicate with the wireless devices and may also be referred to as Node Bs, LTE Evolved Node Bs (eNodeBs or eNBs), Access Points (APs), Radio Headends, Transmit / Receive Points (TRPs), New Radio Base Stations (NR BSs), 5G Node Bs (NBs), Next Generation Node Bs (gNodeBs or gNBs), etc. Each base station can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a base station, a base station subsystem serving that coverage area, or a combination thereof, depending on the context in which the term is used. The core network 140 can be any type of core network, such as an LTE core network (e.g., an evolved packet core (EPC) network), a 5G core network, etc.

[0043] Base stations 110a-110d can provide communication coverage for macro cells, pico cells, femtocells, another type of cell, or a combination thereof. Macro cells can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UEs with service subscriptions. Pico cells can cover a relatively small geographic area and can allow unrestricted access by UEs with service subscriptions. Femtocells can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by radio devices associated with the femtocell (e.g., radio devices in a Closed User Group (CSG)). A base station used for a macro cell can be called a macro BS. A base station used for a pico cell can be called a pico BS. A base station used for a femtocell can be called a femtocell BS or a home BS. Figure 1 In the example shown, base station 110a can be a macro BS for macro cell 102a, base station 110b can be a pico BS for pico cell 102b, and base station 110c can be a femto BS for femto cell 102c. Base stations 110a-110d can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5GNB,” and “cell” may be used interchangeably herein.

[0044] In some examples, the cell may not necessarily be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station. In some examples, base stations 110a-110d may interconnect with each other and with one or more other base stations or network nodes (not shown) in communication system 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof).

[0045] Base stations 110a-110d can communicate with the core network 140 via wired or wireless communication link 126. Wireless devices 120a-120e can communicate with base stations 110a-110d via wireless communication link 122.

[0046] The wired communication link 126 can use various wired networks (such as Ethernet, TV cable, telephone, fiber optic and other forms of physical network connection), and the wired network can use one or more wired communication protocols, such as Ethernet, point-to-point protocol, advanced data link control (HDLC), improved data communication control protocol (ADCCP) and transmission control protocol / Internet protocol (TCP / IP).

[0047] The communication system 100 may also include relay stations (such as relay BS110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station or wireless device) and send data transmissions to a downstream station (e.g., a wireless device or base station). A relay station can also be a wireless device that can relay transmissions for other wireless devices. Figure 1 In the example shown, relay station 110d can communicate with macro base station 110a and wireless device 120d to facilitate communication between base station 110a and wireless device 120d. A relay station can also be referred to as a relay base station, relay base station, repeater, etc.

[0048] The communication system 100 may be a heterogeneous network comprising different types of base stations (e.g., macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations may have different transmit power levels, different coverage areas, and different effects on interference in the communication system 100. For example, macro base stations may have high transmit power levels (e.g., 5 to 40 watts), while pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0049] Network controller 130 can be coupled to a group of base stations and can provide coordination and control for these base stations. Network controller 130 can communicate with the base stations via backhaul. Base stations can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0050] Wireless devices 120a, 120b, and 120c can be distributed throughout the communication system 100, and each wireless device can be stationary or mobile. Wireless devices can also be referred to as access terminals, terminals, mobile stations, user units, stations, user equipment (UE), etc.

[0051] Macro base station 110a can communicate with core network 140 via wired or wireless communication link 126. Wireless devices 120a, 120b, and 120c can communicate with base stations 110a-110d via wireless communication link 122.

[0052] Wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. Wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that can be used in wireless communication links include 3GPP LTE, 3G, 4G, 5G (such as NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global Microwave Access Interoperability (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Further examples of RATs that can be used in one or more wireless communication links within the communication system 100 include mid-range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, and MuLTEfire, and relatively short-range RATs such as ZigBee, Bluetooth, and Bluetooth Low Energy (LE).

[0053] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, often referred to as tones, frequency bands, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz, and the minimum resource allocation (called a "resource block") could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size could be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0054] While some implementation descriptions may use terminology and examples associated with LTE technology, some implementations are applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR can utilize OFDM with a cyclic prefix (CP) on both the uplink (UL) and downlink (DL), and includes support for half-duplex operation using Time Division Duplex (TDD). A single-component carrier bandwidth of 100 MHz can be supported. An NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75 kHz for a duration of 0.1 milliseconds (ms). Each radio frame can include 50 subframes with a length of 10 ms. Therefore, each time slot can have a length of 0.2 ms. Each subframe can indicate the link direction for data transmission (e.g., DL or UL), and the link direction for each subframe can be dynamically switched. Each subframe can include DL / UL data and DL / UL control data. Beamforming can be supported, and beam direction can be dynamically configured. Precoded multiple-input multiple-output (MIMO) transmission can also be supported. The MIMO configuration in DL can support up to eight transmit antennas, with up to eight streams and up to two streams per wireless device in multilayer DL transmission. Multilayer transmission with up to two streams per wireless device can also be supported.

[0055] In cases with up to eight serving cells, aggregation of multiple cells can be supported. Alternatively, in addition to the OFDM-based air interface, NR can support different air interfaces.

[0056] Some wireless devices can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) wireless devices. MTC and eMTC wireless devices include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., capable of communicating with a base station, another device (e.g., a remote device), or some other entity. Wireless computing platforms can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links, for example. Some wireless devices can be considered Internet of Things (IoT) devices, or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Wireless devices 120a-120e can be included within a housing that houses components of wireless devices 120a-120e, such as processor components, memory components, similar components, or combinations thereof.

[0057] Typically, any number of communication systems and wireless networks can be deployed in a given geographical area. Each communication system and wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency in a given geographical area can support a single RAT to avoid interference between communication systems using different RATs. In some cases, 4G / LTE and / or 5G / NR RAT networks can be deployed. For example, a 5G Non-Standalone (NSA) network can utilize both a 4G / LTE RAT on the 4G / LTE RAN side of a 5G NSA network and a 5G / NR RAT on the 5G / NR RAN side of a 5G NSA network. The 4G / LTE RAN and 5G / NR RAN can be interconnected within the 5G NSA network and connected to both the 4G / LTE core network (e.g., an evolved packet core (EPC) network). Other example network configurations can include a 5G Standalone (SA) network, in which the 5G / NR RAN is connected to the 5G core network.

[0058] In some implementations, two or more wireless devices (e.g., shown as wireless devices 120a and 120e) can communicate directly using one or more sidelink channels (e.g., without using base stations 110a-d as intermediaries). For example, wireless devices 120a-e can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks, or similar networks, or combinations thereof. In this case, wireless devices 120a-120e can perform scheduling operations, resource selection operations, and other operations described elsewhere herein as performed by base stations 110a-110d.

[0059] Figure 2 This is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing various embodiments. The various embodiments may be implemented on a number of single-processor and multi-processor computer systems, including system-on-a-chip (SoC) or system-in-package (SIP).

[0060] refer to Figure 1 and Figure 2The illustrated example computing system 200 (which may be a SIP in some embodiments) includes two SOCs 202 and 204 coupled to a clock 206, a voltage regulator 208, and a wireless transceiver 266. The wireless transceiver 266 is configured to transmit wireless communication to / receive wireless communication from a wireless device (such as base station 110a) via an antenna (not shown). In some implementations, the first SOC 202 may operate as a central processing unit (CPU) of the wireless device that implements instructions by performing arithmetic, logic, control, and input / output (I / O) operations specified by instructions from a software application. In some implementations, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (such as 5Gbps) or very high frequency short-wavelength (such as 28GHz millimeter-wave spectrum) communications.

[0061] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor 216, one or more coprocessors 218 (such as vector coprocessors) connected to one or more processors, memory 220, a custom circuit system 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power envelope (TPE) component 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple millimeter-wave transceivers 256, memory 258, and various additional processors 260, such as application processors, packet processors, etc.

[0062] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independently of other processors / cores. For example, the first SOC 202 may include a processor running a first type of operating system (such as FreeBSD, LINUX, OS X, etc.) and a processor running a second type of operating system (such as MICROSOFT WINDOWS 10). Furthermore, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (such as a synchronous processor cluster architecture, an asynchronous or heterogeneous processor cluster architecture, etc.).

[0063] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and performing other specialized operations, such as decoding packets and processing encoded audio and video signals for presentation in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting processors and software clients running on wireless devices. System components and resources 224 or custom circuitry 222 may also include circuitry for interfacing with peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc.

[0064] The first SOC 202 and the second SOC 204 can communicate via interconnect / bus module 250. Individual processors 210, 212, 214, 216, and 218 can be interconnected via interconnect / bus module 226 to one or more memory elements 220, system components and resources 224, custom circuitry 222, and thermal management unit 232. Similarly, processor 252 can be interconnected via interconnect / bus module 264 to power management unit 254, millimeter-wave transceiver 256, memory 258, and various additional processors 260. Interconnect / bus modules 226, 250, and 264 can include reconfigurable logic gate arrays or implement bus architectures (such as CoreConnect, AMBA, etc.). Communication can be provided via improved interconnects (such as high-performance on-chip networks (NoC)).

[0065] The first SOC 202 or the second SOC 204 may also include input / output modules (not shown) for communicating with resources outside the SOC, such as clock 206 and voltage regulator 208. The resources outside the SOC (such as clock 206 and voltage regulator 208) may be shared by two or more of the internal SOC processors / cores.

[0066] In addition to the example SIP 200 discussed above, some implementations can be implemented in a wide variety of computing systems, which may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0067] Figure 3 This is a component block diagram illustrating a software architecture 300 including radio protocol stacks for the user plane and control plane suitable for implementing various embodiments of wireless communication. (Refer to...) Figures 1-3Wireless device 320 may implement software architecture 300 to facilitate communication between wireless device 320 (e.g., wireless devices 120a-120e, 200) and base station 350 (e.g., base station 110a-110d) in a communication system (e.g., 100). In various embodiments, layers in software architecture 300 may form logical connections with corresponding layers in the software of base station 350. Software architecture 300 may be distributed across one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although illustrated with respect to a single radio protocol stack, in a multi-SIM (Subscriber Identity Module) wireless device, software architecture 300 may include multiple protocol stacks, each of which may be associated with a different SIM (e.g., in a dual-SIM wireless communication device, the two protocol stacks are associated with two SIMs respectively). Although described below with reference to the LTE communication layer, the software architecture 300 may support any of the various standards and protocols used for wireless communication, and / or may include additional protocol stacks that support any of the various standards and protocols used for wireless communication.

[0068] Software architecture 300 may also include a Non-Access Stratum (NAS) 302 and an Access Stratum (AS) 304. NAS 302 may include functions and protocols for supporting packet filtering, security management, mobility control, session management, and services and signaling between a SIM (such as SIM 204) of a radio device and its core network 140. AS 304 may include functions and protocols for supporting communication between the SIM (such as SIM 204) and entities of the supported access network (such as base stations). In particular, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may contain various sublayers.

[0069] In the user plane and control plane, Layer 1 (L1) of AS 304 can be Physical Layer (PHY) 306, which can supervise the functions implemented for transmission or reception over the air interface via a wireless transceiver (e.g., 266). Examples of such Physical Layer 306 functions may include Cyclic Redundancy Check (CRC) appending, coded blocks, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The Physical Layer may include various logical channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH).

[0070] In the user plane and control plane, Layer 2 (L2) of AS 304 can be responsible for the link between wireless device 320 and base station 350 via physical layer 306. In some implementations, Layer 2 may include a Media Access Control (MAC) sublayer 308, a Radio Link Control (RLC) sublayer 310, and a Packet Data Convergence Protocol (PDCP) sublayer 312, each of which forms a logical connection that terminates at base station 350.

[0071] In the control plane, Layer 3 (L3) of AS 304 may include a Radio Resource Control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional Layer 3 sublayers and various upper layers above Layer 3. In some implementations, RRC sublayer 313 may provide functions including broadcasting system information, paging, and establishing and releasing RRC signaling connections between radio device 320 and base station 350.

[0072] In some implementations, PDCP sublayer 312 can provide uplink functions, including multiplexing between different radio bearers and logical channels, sequence number increment, handover data processing, integrity protection, encryption, and header compression. In the downlink, PDCP sublayer 312 can provide functions including in-order delivery of packets, duplicate data packet detection, integrity verification, decryption, and header decompression.

[0073] In the uplink, RLC sublayer 310 can provide segmentation and concatenation of upper-layer data packets, retransmission of lost data packets, and Automatic Repeat Request (ARQ). In the downlink, RLC sublayer 310 functions may include reordering data packets to compensate for out-of-order reception, reassembly of upper-layer data packets, and ARQ.

[0074] In the uplink, MAC sublayer 308 can provide functions including multiplexing between logical and transport channels, random access procedures, logical channel prioritization, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions can include channel mapping within the cell, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0075] While the software architecture 300 can provide functionality for transmitting data over a physical medium, it may also include at least one host layer 314 to provide data transfer services to various applications within the wireless device 320. In some implementations, application-specific functionality provided by at least one host layer 314 can provide an interface between the software architecture and the general-purpose processor 206.

[0076] In other implementations, software architecture 300 may include one or more higher logical layers (such as transport, session, presentation, and application layers) that provide host layer functionality. For example, in some implementations, software architecture 300 may include a network layer (such as the Internet Protocol (IP) layer), where logical connections terminate at a Packet Data Network (PDN) gateway (PGW). In some implementations, software architecture 300 may include an application layer, where logical connections terminate at another device (such as an end-user device, server, etc.). In some implementations, software architecture 300 may also include a hardware interface 316 in AS 304 between physical layer 306 and communication hardware (such as one or more radio frequency (RF) transceivers).

[0077] Figure 4A and Figure 4B This is a component block diagram illustrating an example system 400 suitable for implementing various embodiments. (Refer to...) Figures 1-4B System 400 may include base station 402 and wireless device 404 (e.g., 110a-110d, 120a-120e, 200, 320, 350). Base station 402 and wireless device 404 exchange wireless communications to establish wireless communication links 122, 124, 126.

[0078] Base station 402 and wireless device 404 may include one or more processors 428, 432 coupled to electronic storage 426, 430 and a wireless transceiver (e.g., 266). In base station 402 and wireless device 404, wireless transceiver 266 may be configured to receive messages transmitted in transit and to pass such messages to processors 428, 432 for processing. Similarly, processors 428, 432 may be configured to send messages for transmission to wireless transceiver 266 for transmission.

[0079] Referring to base station 402, processor 428 can be configured via machine-readable instructions 406. Machine-readable instructions 406 may include one or more instruction modules. Instruction modules may include computer program modules. Instruction modules may include one or more of the following: capability report receiving module 408, scheduling module 410, or other instruction modules.

[0080] Capability report receiving module 408 can be configured to receive a capability report from a wireless device (e.g., 404) indicating whether the wireless device is configured to determine whether the time period between the end of a Physical Downlink Control Channel (PDCCH) service and the next Cross-Link Interference (CLI) measurement timing exceeds a threshold duration. In some embodiments, additionally or alternatively, the capability report may indicate whether the wireless device is configured to determine whether a second time period from the end of a PDCCH service to the beginning of a downlink service is less than or equal to a second threshold duration.

[0081] Scheduling module 410 can be configured to schedule CLI measurement resources that do not overlap with the next downlink service (such as a Physical Downlink Shared Channel (PDSCH) service or the next Channel State Information Reference Signal (CSI-RS)) for the wireless device in response to determining whether the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds a threshold duration. Scheduling module 410 can also be configured to schedule the PDCCH service and the next CLI measurement opportunity at least a threshold duration apart in response to determining whether the wireless device is configured to determine whether the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds a threshold duration. Alternatively, scheduling module 410 can be configured to schedule downlink services for at least the second threshold duration after the end of the PDCCH service in response to determining whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to a second threshold duration.

[0082] Referring to wireless device 404, processor 432 can be configured via machine-readable instructions 434. Machine-readable instructions 406 may include one or more instruction modules. Instruction modules may include computer program modules. Instruction modules may include one or more of the following: PDCCH receiving module 436, time period determination module 438, downlink service receiving module 440, CLI measurement module 442, or other instruction modules.

[0083] PDCCH receiving module 436 can be configured to receive PDCCH services from the base station using the first Rx resource tuning of Rx resources.

[0084] The time period determination module 438 can be configured to determine whether the time period between the end of the PDCCH service and the next CLI measurement opportunity exceeds the threshold duration for tuning the Rx resource to the second Rx resource.

[0085] The downlink service receiving module 440 can be configured to receive downlink services using the first Rx resource tuning in response to determining that the time period between the end of the PDCCH service and the next CLI measurement opportunity does not exceed a threshold duration.

[0086] CLI measurement module 442 can be configured to perform CLI measurements using a second Rx resource tuned during CLI measurement timing.

[0087] In some embodiments, base station 402 and wireless device 404 may be operatively linked via one or more electronic communication links (e.g., wireless communication links 122, 124, 126). It will be understood that this is not intended to be limiting, and the scope of this disclosure includes embodiments in which base station 402 and wireless device 404 may be operatively linked via some other communication medium.

[0088] Electronic storage devices 426 and 430 may include non-transitory storage media that store information electronically. The electronic storage media of electronic storage devices 426 and 430 may include one or both of system storage (which is provided integrally with base station 402 and wireless device 404 (i.e., substantially non-removable)) and / or removable storage (which is removably connected to base station 402 and wireless device 404 via, for example, a port (e.g., a Universal Serial Bus (USB) port, a FireWire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage devices 426 and 430 may include one or more of optically readable storage media (e.g., optical discs, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard disk drives, floppy disk drives, etc.), charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drives, etc.) and / or other electronically readable storage media. Electronic storage devices 426 and 430 may include one or more virtual storage resources (e.g., cloud storage, virtual private networks, and / or other virtual storage resources). Electronic storage devices 426 and 430 may store software algorithms, information determined by processors 428 and 432, information received from base station 402 and wireless device 404, or other information that enables base station 402 and wireless device 404 to operate as described herein.

[0089] Processors 428 and 432 can be configured to provide information processing capabilities in base station 402 and wireless device 404. Therefore, processors 428 and 432 may include one or more of a digital processor, an analog processor, digital circuitry designed to process information, analog circuitry designed to process information, a state machine, and / or other mechanisms for electronically processing information. Although processors 428 and 432 are shown as a single entity, this is for illustrative purposes only. In some embodiments, processors 428 and 432 may include multiple processing units and / or processor cores. Processing units may be physically located within the same device, or processors 428 and 432 may represent the processing functions of multiple devices operating collaboratively. Processors 428 and 432 can be configured to execute modules 408-414 and modules 436-446 and / or other modules via software; hardware; firmware; a combination of software, hardware, and / or firmware; and / or other mechanisms for configuring processing capabilities on processors 428 and 432. As used herein, the term "module" can refer to any component or collection of components that performs the functionality attributed to that module. This can include one or more physical processors, processor-readable instructions, circuitry, hardware, storage media, or any other components during the execution of processor-readable instructions.

[0090] The descriptions of the functions provided by the various modules 408-414 and 436-446 described below are for illustrative purposes and are not intended to be limiting, as any module 408-414 and 436-446 may provide more or fewer functions than described. For example, one or more modules 408-414 and 436-446 may be removed, and some or all of their functions may be provided by other modules 408-414 and 436-446. As another example, processors 428 and 432 may be configured to execute one or more additional modules that can perform some or all of the functions of one of the modules categorized below as belonging to modules 408-414 and 436-446.

[0091] Figure 5A , Figure 5B and Figure 5C This is a conceptual diagram illustrating various aspects of the operation 500a-500c of the methods for managing downlink signal reception and CLI according to various embodiments. (Refer to...) Figures 1-5C Operations of 500a-500c can be performed by the processors (e.g., 210, 212, 214, 216, 218, 252, 260, 428, 432) of wireless devices (e.g., 120a-120e, 200, 320, 404) and / or base stations (e.g., 110a-110d, 200, 350, 402).

[0092] Reference Figure 5A The wireless device can use a first Rx resource tuned to receive PDCCH service 502 from the base station. The wireless device can determine whether the time period 508 between the end of the PDCCH service and the beginning of the next CLI measurement opportunity 504 exceeds a threshold duration TH1 that the wireless device might need to tune its Rx resources from the first Rx resource to the second Rx resource tuned. In some embodiments, the wireless device can be configured to prioritize receiving downlink services (e.g., PDSCH service or CSI-RS) over performing CLI measurements. In some embodiments, in response to determining that the time period 508 does not exceed (i.e., is less than or equal to) the threshold duration TH1, the wireless device can use the first Rx resource tuned to receive downlink service 506. In some embodiments, in response to determining that the time period 508 exceeds the threshold duration TH1, the wireless device can tune its Rx resources to the second Rx resource tuned and perform CLI measurements during CLI measurement opportunity 504.

[0093] Reference Figure 5B In some embodiments, in response to determining that the time period between the end of a PDCCH service and the beginning of the next CLI measurement opportunity exceeds a threshold duration, the wireless device can determine whether the next CLI measurement opportunity overlaps with the next downlink service 516. For example, the wireless device can determine that the time period 514 between the end of a PDCCH service 502 and the beginning of the next CLI measurement opportunity 510 exceeds a threshold duration TH1. In such embodiments, in response to determining that the next CLI measurement opportunity overlaps with the next downlink service 512 516, the wireless device can use a first Rx resource tuned to receive the downlink service 512 (e.g., a PDSCH service or CSI-RS). In some embodiments, the wireless device can maintain its Rx resource tuned to the first Rx resource tuned and may not tune its Rx resource to the second Rx resource tuned. In some embodiments, at a future time, the wireless device can use the second Rx resource tuned to perform CLI measurements during a subsequent CLI measurement opportunity (not shown) that does not conflict with the downlink service 512.

[0094] In response to determining that the next RI measurement opportunity 510 does not overlap with downlink traffic 512, the wireless device can tune the Rx resource to a second Rx resource tuned and perform a CLI measurement during the CLI measurement opportunity 510.

[0095] Reference Figure 5CIn some embodiments, the wireless device may determine whether there is sufficient time to use the second Rx resource tuning to perform CLI measurements, and then tune the Rx resource to the first Rx resource operation, and receive downlink traffic. In some embodiments, in response to determining that the time period 514 between the end of PDCCH service 502 and the beginning of the next CLI measurement opportunity 518 has not exceeded a threshold duration TH1, the wireless device may tune the Rx resource to the second Rx resource tuning, and begin performing CLI measurements during CLI measurement opportunity 518.

[0096] In some embodiments, the wireless device may continue decoding the buffered PDCCH service 502 while performing CLI measurements. In some embodiments, the wireless device may determine, based on the decoded PDCCH service, whether a second time period 520 from the end of the PDCCH service 502 to the beginning of the downlink service 522 (e.g., PDSCH service or CSI-RS) exceeds a second threshold duration TH2. In some embodiments, the second threshold duration TH2 may represent the amount of time required for the wireless device to decode the PDCCH service, tune the Rx resource to a second Rx resource, perform CLI measurements, and tune the Rx resource to a first Rx resource to receive the downlink service 522.

[0097] In some embodiments, in response to determining that the second time period 520 has not exceeded the second threshold duration TH2, the wireless device may use a first Rx resource tune to receive downlink service 522 before completing CLI measurement. In some embodiments, the wireless device may abort the execution of CLI measurement and tune the Rx resource to the first Rx resource tune. For example, before the wireless device has completed decoding of PDCCH service, the wireless device may tune the Rx resource to the second Rx resource tune and perform CLI measurement during CLI measurement timing 518. After starting CLI measurement, the wireless device may decode a sufficient number of PDCCH services to determine the scheduling of upcoming downlink service 518. The wireless device may determine that the second time period 520 from the end of PDCCH service to the beginning of downlink service 518 has not exceeded the second threshold duration TH2, and in response, the wireless device may tune the Rx resource to the first Rx resource tune and receive downlink service 518. In some embodiments, the wireless device may measure CLI during a subsequent CLI measurement opportunity (not shown) that does not conflict with or overlap with the downlink service or subsequent downlink service.

[0098] In some embodiments, the base station may receive a capability report from a radio device indicating whether the radio device is configured to determine whether a time period (e.g., 508, 514) between the end of a PDCCH service and the beginning of the next CLI measurement opportunity exceeds a threshold duration (e.g., TH1). In some embodiments, the capability report may indicate whether the radio device is configured to determine whether to switch to a second Rx resource and perform a CLI measurement by determining whether the time period between the end of a PDCCH service and the beginning of the next CLI measurement opportunity exceeds a threshold duration. In some embodiments, the capability report sent by the radio device may include one or more thresholds (e.g., TH1, TH2).

[0099] In some embodiments, the base station may schedule CLI measurement resources that do not overlap with upcoming downlink traffic (e.g., 506, 518) for the radio device in response to determining that the radio device is not configured to determine whether the time period between the end of the PDCCH service and the beginning of the next CLI measurement opportunity (e.g., 508, 514) exceeds a threshold duration (e.g., TH1). In some embodiments, the base station may schedule the PDCCH service and the next CLI measurement opportunity to be at least (i.e., temporally) separated by a threshold duration in response to determining that the radio device is configured to determine whether CLI measurement can be performed (e.g., whether the radio device has sufficient time to perform CLI measurement) by determining whether the time period between the end of the PDCCH service and the beginning of the next CLI measurement opportunity exceeds a threshold duration.

[0100] In some embodiments, the wireless device may send a capability report including an indication of whether the wireless device is configured to determine whether a second time period (e.g., 520) from the end of a PDCCH service (e.g., 502) to the beginning of a downlink service 518 is less than or equal to a second threshold duration (e.g., TH2). In some embodiments, the capability report may indicate whether the wireless device is configured to suspend CLI measurements in response to determining that the second time period from the end of a PDCCH service (e.g., 502) to the beginning of a downlink service 518 is less than or equal to the second threshold duration. In response to determining that the wireless device is configured to determine whether the second time period from the end of a PDCCH service (e.g., 502) to the beginning of a downlink service 518 is less than or equal to the second threshold duration, the base station may schedule downlink services (e.g., PDSCH service or CSI-RS) for at least the second threshold duration (e.g., TH2) after the end of the PDCCH service. In some embodiments, the base station may schedule downlink traffic in response to determining that the radio device is not configured to determine whether the second time period from the end of the PDCCH traffic to the beginning of the downlink traffic is less than or equal to the duration of the second threshold, so as not to overlap with the next CLI measurement timing.

[0101] Figure 6A This is a process flowchart illustrating a method 600a executed by a processor of a wireless device to enhance coverage for managing downlink traffic reception and CLI, according to various embodiments. (Refer to...) Figures 1-6A Method 600a can be executed by the processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428, 432) of a wireless device (e.g., 120a-120e, 200, 320, 404).

[0102] In box 602, the processor can use the first Rx resource of the receive (Rx) resource to tune the reception of physical downlink control channel (PDCCH) services from the base station (e.g., 110a-110d, 402).

[0103] In determination box 604, the processor can determine whether the time period between the end of the PDCCH service and the start of the next CLI measurement opportunity exceeds the threshold duration for tuning the Rx resource to the second Rx resource.

[0104] In response to determining that the time interval between the end of the PDCCH service and the beginning of the next CLI measurement opportunity is less than or equal to the threshold duration for tuning the Rx resource to the second Rx resource (i.e., determining block 604 = "No"), the processor may use the first Rx resource tuning to receive downlink service in block 606. In some embodiments, the downlink service may include Physical Downlink Shared Channel (PDSCH) service or Channel State Information Reference Signal (CSI-RS).

[0105] In response to determining that the time period between the end of the PDCCH service and the beginning of the next CLI measurement opportunity exceeds the threshold duration for tuning the Rx resource to the second Rx resource (i.e., determining box 604 = "Yes"), the processor may use the second Rx resource tuning to perform the CLI measurement in box 608.

[0106] After performing the operation of box 606 or box 608, the processor may again perform the operation of box 602 as described.

[0107] Figure 6B and Figure 6C This is a process flowchart illustrating operations 600b and 600c, which, according to various embodiments, can be executed by a processor of a wireless device as part of a method 600a for enhancing coverage for managing downlink traffic reception and CLI. (Refer to...) Figures 1-6C Operations 600b and 600c can be performed by the processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428, 432) of a wireless device (e.g., 120a-120e, 200, 320, 404).

[0108] Reference Figure 6B In some embodiments, in response to determining that the time period between the end of the PDCCH data and the next CLI measurement timing exceeds a threshold duration (i.e., determination box 604 = "Yes"), the processor may determine in determination box 610 whether the next CLI measurement timing overlaps with the next PDSCH data or CSI-RS.

[0109] In response to determining that the next CLI measurement timing overlaps with the next downlink service (i.e., determining box 610 = "Yes"), the processor can use the first Rx resource to tune in box 612 to receive the downlink service.

[0110] In optional block 616, the processor can perform CLI measurements using a second Rx resource tuning during a subsequent CLI measurement opportunity that does not conflict with downlink traffic. In some embodiments, after receiving downlink traffic, the processor can receive resource allocation or scheduling information from the base station indicating that another CLI measurement opportunity will be available. In such embodiments, the processor can perform CLI measurements during the upcoming CLI measurement opportunity as long as the upcoming CLI measurement opportunity does not conflict with downlink traffic (e.g., does not overlap with downlink traffic).

[0111] In response to determining that the next CLI measurement timing does not overlap with the next downlink traffic (i.e., determining box 610 = "No"), the processor may use the second Rx resource tuning to perform the CLI measurement during the next CLI measurement timing in box 614.

[0112] After performing the operation of box 614, box 612, or optional box 616, the processor can again perform the operation of box 602 as described. Figure 6A ) operation.

[0113] Reference Figure 6C In some embodiments, in response to determining that the timing of the next CLI measurement does not overlap with the next downlink traffic (i.e., determining block 610 = "No"), the processor may begin CLI measurement using a second Rx resource tuner in block 620. In some embodiments, the processor may decode received PDCCH traffic while performing CLI measurement.

[0114] In determination box 622, the processor can determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration based on the decoded PDCCH service.

[0115] In response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service does not exceed (i.e., less than or equal to) the second threshold duration (i.e., determining box 622 = "No"), the processor may use the first Rx resource to receive the downlink service in box 624 before completing the measurement of CLI.

[0116] In response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration (i.e., determining box 622 = "Yes"), the processor can use the second Rx resource tuning in box 626 to complete the measurement of CLI.

[0117] In box 628, the processor can use the first Rx resource to tune to receive downlink traffic.

[0118] After performing the operation of box 624 or box 628, the processor can again perform the operation of box 602 as described. Figure 6A ) operation.

[0119] Figure 7A This is a process flowchart illustrating a method 700a executed by a base station processor according to various embodiments for enhancing coverage for managing downlink service reception and CLI. (Refer to...) Figures 1-7A Method 600a can be executed by the processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428, 432) of the base station (e.g., 110a-110d, 200, 350, 402).

[0120] In block 702, the processor may receive a capability report from the wireless device indicating whether the wireless device is configured to determine whether the time period between the end of a PDCCH service and the start of the next CLI measurement opportunity exceeds a threshold duration. In some embodiments, the capability report may indicate whether the wireless device is configured to determine whether to switch to a second Rx resource tuning and perform a CLI measurement by determining whether the time period between the end of a Physical Downlink Control Channel (PDCCH) service and the start of the next Cross-Link Interference (CLI) measurement opportunity exceeds a threshold duration. In some embodiments, the capability report may indicate whether the wireless device is configured to determine whether there is sufficient time to use a first Rx resource tuning to decode the PDCCH service and then tune its Rx resources to a second Rx resource tuning to perform a CLI measurement.

[0121] In determination block 704, the processor may determine whether the wireless device is configured to determine whether the time period between the end of the PDCCH signaling and the beginning of the next CLI measurement opportunity exceeds a threshold duration (e.g., based on a capability report). In some embodiments, the processor may determine whether the wireless device is configured to determine whether to perform a CLI measurement by determining whether the time period between the end of the PDCCH signaling and the beginning of the next CLI measurement opportunity exceeds a threshold duration.

[0122] In response to determining that the wireless device is configured to determine whether the time period between the end of the PDCCH signaling and the beginning of the next CLI measurement opportunity exceeds a threshold duration (i.e., determination box 704 = "Yes"), the processor may schedule the PDCCH service and the next CLI measurement opportunity to be separated by at least the threshold duration in box 706. For example, determining that the wireless device is configured to determine whether the time period between the end of the PDCCH signaling and the next CLI measurement opportunity exceeds a threshold duration may instruct the wireless device to require the PDCCH service and the next CLI measurement to be separated from each other in time by at least the threshold duration for occurrence (or to be scheduled). In some embodiments, the threshold duration may indicate the duration during which the wireless device can perform the CLI measurement. In some embodiments, the base station may schedule the PDCCH service and the next CLI measurement opportunity to be separated by at least the threshold duration to provide the wireless device with sufficient time to decode the PDCCH service and then tune the receive (Rx) resources from a first Rx resource tuned to enable the wireless device to receive the PDCCH service to a second Rx resource tuned to perform the CLI measurement.

[0123] In response to determining that the wireless device is not configured to determine whether the time period between the end of the PDCCH signaling and the beginning of the next CLI measurement opportunity exceeds a threshold duration (i.e., determination box 704 = "No"), the processor may schedule downlink traffic in box 708 so as not to overlap with the next CLI measurement opportunity. For example, the processor may schedule downlink traffic after the CLI measurement opportunity by allowing the wireless device to tune its receive (Rx) resources from a second Rx resource frequency that enables the wireless device to perform CLI measurements to a first Rx resource frequency for receiving downlink traffic for a sufficiently long period of time. In some embodiments, downlink traffic may include Physical Downlink Shared Channel (PDSCH) traffic or Channel State Information Reference Signaling (CSI-RS).

[0124] Figure 7B This is a flowchart illustrating operation 700b, as part of a method 700a for managing downlink service reception and CLI, which can be executed by a base station processor according to various embodiments. (Refer to...) Figures 1-7B Operation 700b can be performed by the processor (e.g., 210, 212, 214, 216, 218, 252, 260, 428, 432) of the base station (e.g., 110a-110d, 200, 350, 402).

[0125] In block 720, the processor may receive a capability report from a wireless device indicating whether the wireless device is configured to determine whether a second time period from the end of a PDCCH service to the beginning of a downlink service (e.g., a PDSCH service or CSI-RS) exceeds a second threshold duration. In some embodiments, the capability report may indicate whether the wireless device is configured to determine whether there is sufficient time to tune its Rx resources to a second Rx resource frequency to perform CLI measurements, and then tune its Rx resources back to a first Rx resource frequency to receive downlink services. As described, in some embodiments, the wireless device may be configured to abort or cancel the execution of CLI measurements and tune its Rx resources to receive downlink services. In some embodiments, the capability report may indicate whether the wireless device is configured to make such a determination. In some embodiments, the capability report may be merged with other capability reports from the wireless device (e.g., the capability report in block 702), may be sent together, or may be a separate capability report.

[0126] In determination block 722, the processor may determine whether the wireless device is configured to determine whether a second time period from the end of PDCCH signaling to the start of downlink service exceeds a second threshold duration (e.g., based on capability reports). In some embodiments, the processor may determine whether the wireless device is configured to determine whether there is sufficient time to tune its Rx resources to a second Rx resource frequency to perform CLI measurements, and then tune its Rx resources back to a first Rx resource frequency to receive downlink service.

[0127] In response to determining whether the wireless device is configured to determine whether a second time period from the end of PDCCH signaling to the beginning of PDSCH signaling or CSI-RS exceeds a second threshold duration (i.e., determination box 722 = "Yes"), the processor may schedule PDSCH signaling or CSI-RS for at least the second threshold duration after the end of PDCCH signaling in box 724.

[0128] In response to determining that the radio device is not configured to determine whether the second time period from the end of PDCCH signaling to the beginning of PDSCH signaling or CSI-RS exceeds a second threshold duration (i.e., determination box 722 = "No"), the processor may schedule downlink traffic in box 726 so as not to overlap with CLI measurement timing. For example, in response to determining that the radio device is not configured to determine whether there is sufficient time to tune its Rx resources to a second Rx resource to perform CLI measurements, and then tune its Rx resources back to a first Rx resource to receive downlink traffic, the base station may schedule CLI measurement timing and downlink traffic so as not to overlap.

[0129] Figure 8 This is a component block diagram of a base station computing device suitable for use with the various embodiments. Such a base station computing device (e.g., base stations 110a-110d, 350, 402) may include at least Figure 8 The components shown. (Refer to...) Figures 1-8 The base station computing device 800 may typically include a processor 801 coupled to volatile memory 802 and mass non-volatile memory (such as a disk drive 808). The base station computing device 800 may also include peripheral memory access devices 806, such as floppy disk drives, optical disc (CD) or digital video disc (DVD) drives coupled to the processor 801. The base station computing device 800 may also include a network access port 804 (or interface) coupled to the processor 801 for establishing a data connection to a network (such as the Internet or a local area network coupled to other system computers and servers). The base station computing device 800 may include one or more antennas 807 that can be connected to a wireless communication link for transmitting and receiving electromagnetic radiation. The base station computing device 800 may include additional access ports for coupling to peripheral devices, external memory, or other devices, such as USB, FireWire, Thunderbolt, etc.

[0130] Figure 9 This is a component block diagram of a wireless device 900 suitable for use with various embodiments. (Refer to...) Figures 1-9 The various embodiments can be implemented on various wireless devices 900 (e.g., wireless devices 120a-120e, 200, 320, 404), examples of which are... Figure 9 The wireless device 900 is illustrated in the form of a smartphone. It may include a first SOC 202 (e.g., an SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to internal memory 916, a display 912, and a speaker 914. Furthermore, the wireless device 900 may include an antenna 904 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless transceiver 266 coupled to one or more processors in the first SOC 202 and / or the second SOC 204. The wireless device 900 may include a menu selection button or a rocker switch 920 for receiving user input.

[0131] Wireless device 900 may include a voice encoding / decoding (CODEC) circuitry 910, which digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes the received voice data packets to generate an analog signal provided to a speaker to produce sound. One or more processors in the first SOC 202, the second SOC 204, the wireless transceiver 266, and the CODEC 910 may include digital signal processor (DSP) circuitry (not shown separately).

[0132] The processors of the base station computing device 800 and the wireless device 900 can be any programmable microprocessor, microcomputer, or multiprocessor chip, which can be configured via software instructions (applications) to perform various functions, including some of the functions described below. In some wireless devices, multiple processors may be provided, such as one processor within SOC 204 dedicated to wireless communication functions, and one processor in SOC 202 dedicated to running other applications. Software applications may be stored in memories 702, 916 before being accessed and loaded into the processor. The processor may include internal memory sufficient to store application software instructions.

[0133] As used in this application, the terms "component," "module," "system," etc., are intended to include computer-related entities such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software being executed, configured to perform specific operations or functions. For example, a component can be, but is not limited to, a process, processor, object, executable file, execution thread, program, or computer running on a processor. By way of illustration, both an application running on a wireless device and the wireless device can be referred to as a component. One or more components may reside within a process or execution thread, and components may reside on a single processor or core or be distributed across two or more processors or cores. Furthermore, these components can be executed from various non-transitory computer-readable media having various instructions or data structures stored thereon. Components can communicate via local and / or remote processes, function or procedure calls, electronic signals, data packets, memory read / write, and other known network, computer, processor, or process-related communication methods.

[0134] Many different cellular and mobile communication services and standards are available or anticipated in the future, all of which can be implemented and benefit from various implementations. Such services and standards include, for example, the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) systems, 3rd Generation Wireless (3G), 4th Generation Wireless (4G), 5th Generation Wireless (5G) and later 3GPP technologies, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, Universal Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), Enhanced Data Rate for GSM Evolution (EDGE), Improved Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA), Evolved Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Global Microwave Access Interoperability (WiMAX), Wireless Local Area Network (WLAN), Wi-Fi Protected Access I and II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). Each of these technologies relates to, for example, the transmission and reception of voice, data, signaling, and / or content messages. It should be understood that any references to terms and / or technical details relating to individual telecommunications standards or technologies are for illustrative purposes only and are not intended to limit the scope of the claims to a particular communication system or technology, unless specifically stated in the language of the claims.

[0135] The various embodiments shown and described are provided by way of example only to illustrate the features of the claims. However, the features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. Furthermore, the claims are not intended to be limited to any of the exemplary embodiments. For example, one or more of methods and operations 600a, 600b, 600c, 700a, and 700b may be replaced by one or more operations of methods and operations 600a, 600b, 600c, 700a, and 700b, or combined with one or more operations of methods and operations 600a, 600b, 600c, 700a, and 700b.

[0136] Examples of implementations are described in the following paragraphs. While some of the examples of implementations below are described from the perspective of example methods, further example implementations may include: example methods implemented by a wireless device or base station, as discussed in the following paragraphs, the wireless device or base station including a processor configured to have processor-executable instructions to perform the operations of the methods of the examples of the following implementations; example methods implemented by a wireless device or base station, as discussed in the following paragraphs, the wireless device or base station including units for performing the functions of the methods of the examples of the following implementations; and example methods discussed in the following paragraphs may be implemented as having a non-transitory processor-readable storage medium having processor-executable instructions stored thereon configured to cause the processor of the wireless device or base station to perform the operations of the methods of the examples of the following implementations.

[0137] Example 1. A method for managing downlink traffic reception and cross-link interference (CLI), executed by a processor of a wireless device, comprising: receiving physical downlink control channel (PDCCH) traffic from a base station using a first Rx resource tuned with receive (Rx) resources; determining whether a time period between the end of the PDCCH traffic and the beginning of a CLI measurement timing exceeds a threshold duration for tuning the Rx resources to a second Rx resource tuned; and receiving the downlink traffic using the first Rx resource tuned in response to determining that the time period between the end of the PDCCH traffic and the beginning of the CLI measurement timing is less than or equal to the threshold duration.

[0138] Example 2. The method according to claim 1, wherein the downlink service includes Physical Downlink Shared Channel (PDSCH) service or Channel State Information Reference Signal (CSI-RS).

[0139] Example 3. The method according to any of Examples 1 and 2 further includes: in response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, determining whether the CLI measurement timing overlaps with a downlink service; and in response to determining that the next CLI measurement timing overlaps with the downlink service, using the first Rx resource tuning to receive the downlink service.

[0140] Example 4. According to the method of Example 3, it further includes performing CLI measurements using the second Rx resource tuning during the CLI measurement period in response to determining that the CLI measurement timing does not overlap with the downlink service.

[0141] Example 5. The method of Example 3 further includes performing CLI measurements using the second Rx resource tuning during a subsequent CLI measurement opportunity that does not conflict with subsequent downlink traffic.

[0142] Example 6. A method according to any of Examples 1-5, wherein receiving the downlink service using the first Rx resource tuning in response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing is less than or equal to the threshold duration includes: using the second Rx resource tuning to begin the measurement of the CLI; determining, based on the decoded PDCCH service, whether a second time period from the end of the PDCCH service to the beginning of the downlink service exceeds a second threshold duration; and receiving the downlink service using the first Rx resource tuning before completing the measurement of the CLI in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

[0143] Example 7. According to the method of Example 6, the measurement of the CLI is further included in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration, using the second Rx resource tuning.

[0144] Example 8. A method for managing downlink traffic reception and cross-link interference, executed by a processor of a base station, comprising: receiving a capability report from a radio device, the capability report indicating whether the radio device is configured to determine whether a time period between the end of a physical downlink control channel (PDCCH) service and the beginning of a cross-link interference (CLI) measurement timing exceeds a threshold duration; and, in response to determining that the radio device is not configured to determine whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, scheduling downlink traffic for the radio device that does not overlap with the CLI measurement timing.

[0145] Example 9. According to the method of Example 8, wherein the capability report indicates whether the wireless device is configured to determine whether to switch to the second Rx resource and perform CLI measurement by determining whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration.

[0146] Example 10. The method according to any of the examples in Examples 8 and 9, wherein the downlink service includes Physical Downlink Shared Channel (PDSCH) service or Channel State Information Reference Signal (CSI-RS).

[0147] Example 11. The method according to any of Examples 8-10 further includes, in response to determining that the wireless device is configured to determine whether the time period between the end of the PDCCH service and the CLI measurement timing exceeds the threshold duration, scheduling the PDCCH service and the CLI measurement timing to be at least separated by the threshold duration.

[0148] Example 12. A method according to any of Examples 8-10, wherein the capability report indicates whether the wireless device is configured to determine whether a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to a second threshold duration, the method further includes scheduling the downlink service for at least the second threshold duration after the end of the PDCCH service in response to determining that the wireless device is configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

[0149] Example 13. The method according to Example 12 further includes scheduling the downlink service in response to determining that the wireless device is not configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration, so as not to overlap with the CLI measurement timing.

[0150] Example 14. According to the method of Example 12, wherein the capability report indicates whether the wireless device is configured to suspend CLI measurement in response to determining that a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the duration of the second threshold.

[0151] The foregoing method descriptions and process flowcharts are provided as illustrative examples only and are not intended to require or imply that the operations of the various embodiments must be performed in the given order. As those skilled in the art will appreciate, the operations in the foregoing embodiments can be performed in any order. Words such as “afterward,” “then,” “next,” etc., are not intended to limit the order of operations; these words are used to guide the reader through the description of the method. Furthermore, the use of articles such as “a,” “an,” or “the” to refer to claim elements in the singular should not be construed as limiting the elements to the singular.

[0152] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and operations have been generally described above in accordance with their functions. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in alternative ways for each specific application; however, such embodiments should not be construed as causing a departure from the scope of the claims.

[0153] The hardware used to implement the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver intelligent objects, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Alternatively, some methods or operations may be performed by a circuit system specific to a given function.

[0154] In one or more embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. The operation of the methods or algorithms disclosed herein may be embodied in processor-executable software modules or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium accessible by a computer or processor. By way of example, and not limitation, such a non-transitory computer-readable or processor-readable storage medium may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disc storage, disk storage or other magnetic storage smart objects, or any other medium that may be used to store desired program code in the form of instructions or data structures and accessible by a computer. As used herein, "disk" and "optical disc" include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while optical discs optically copy data using lasers. The above combinations are also included within the scope of non-transitory computer-readable and processor-readable media. Furthermore, the operation of a method or algorithm may reside as one or any combination or set of code and / or instructions on a non-transitory processor-readable and / or computer-readable storage medium, which may be incorporated into a computer program product.

[0155] The foregoing description of the disclosed embodiments is provided to enable any person skilled in the art to implement or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the appended claims and principles and novel features disclosed herein.

Claims

1. A method for managing downlink traffic reception and cross-link interference (CLI), executed by a processor of a wireless device, comprising: The first Rx resource of the receive (Rx) resource is used to tune the reception of physical downlink control channel (PDCCH) services from the base station; Determine whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration for tuning the Rx resource to the second Rx resource. as well as In response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing is less than or equal to the threshold duration, the first Rx resource tuning is used to receive downlink services.

2. The method according to claim 1, wherein, The downlink services include Physical Downlink Shared Channel (PDSCH) services or Channel State Information Reference Signal (CSI-RS).

3. The method according to claim 1, further comprising: In response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, it is determined whether the CLI measurement timing overlaps with downlink service; as well as In response to determining that the CLI measurement timing overlaps with the downlink service, the first Rx resource is used for tuning to receive the downlink service.

4. The method of claim 3, further comprising, in response to determining that the CLI measurement timing does not overlap with the downlink service, using the second Rx resource tuning to perform the CLI measurement during the CLI measurement timing.

5. The method of claim 3, further comprising performing CLI measurements using the second Rx resource tuning during a subsequent CLI measurement opportunity that does not conflict with subsequent downlink traffic.

6. The method according to claim 1, wherein, In response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing is less than or equal to the threshold duration, receiving the downlink service using the first Rx resource tuning includes: Use the second Rx resource to tune in order to begin the measurement of the CLI; Based on the decoded PDCCH service, determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds a second threshold duration; and In response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration, the downlink service is received using the first Rx resource tuning before the measurement of the CLI is completed.

7. The method according to claim 6, further comprising: In response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration, the measurement of the CLI is completed using the second Rx resource tuning.

8. A wireless device, comprising: A processor configured to have processor-executable instructions for performing the following operations: The first Rx resource of the receive (Rx) resource is used to tune the reception of physical downlink control channel (PDCCH) services from the base station; Determine whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration for tuning the Rx resource to the second Rx resource. as well as In response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing is less than or equal to the threshold duration, the first Rx resource tuning is used to receive downlink services.

9. The wireless device according to claim 8, wherein, The processor is also configured to have processor-executable instructions such that the downlink service includes physical downlink shared channel (PDSCH) service or channel state information reference signal (CSI-RS).

10. The wireless device according to claim 8, wherein, The processor is also configured to have processor-executable instructions for performing the following operations: In response to determining that the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, it is determined whether the CLI measurement timing overlaps with downlink service; as well as In response to determining that the CLI measurement timing overlaps with the downlink service, the first Rx resource is used for tuning to receive the downlink service.

11. The wireless device according to claim 10, wherein, The processor is also configured to have processor-executable instructions for performing the following operations: in response to determining that the CLI measurement timing does not overlap with the downlink service, performing CLI measurements using the second Rx resource tuning during the CLI measurement timing.

12. The wireless device according to claim 10, wherein, The processor is also configured to have processor-executable instructions for performing CLI measurements using the second Rx resource tuning during a subsequent CLI measurement opportunity that does not conflict with subsequent downlink traffic.

13. The wireless device according to claim 8, wherein, The processor is also configured to have processor-executable instructions for performing the following operations: Use the second Rx resource to tune in order to begin the measurement of the CLI; Based on the decoded PDCCH service, determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration; as well as In response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration, the downlink service is received using the first Rx resource tuning before the measurement of the CLI is completed.

14. The wireless device according to claim 13, wherein, The processor is also configured to have processor-executable instructions for performing the measurement of the CLI using the second Rx resource tuning in response to determining that the second time period from the end of the PDCCH service to the beginning of the downlink service exceeds the second threshold duration.

15. A method executed by a processor of a base station for managing downlink service reception and cross-link interference, comprising: The wireless device receives a capability report indicating whether it is configured to determine whether the time period between the end of a Physical Downlink Control Channel (PDCCH) service and the beginning of a Cross-Link Interference (CLI) measurement exceeds a threshold duration. as well as In response to determining that the wireless device is not configured to determine whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration, the wireless device schedules downlink services that do not overlap with the CLI measurement timing.

16. The method according to claim 15, wherein, The capability report indicates whether the wireless device is configured to determine whether to switch to a second Rx resource and perform a CLI measurement by determining whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration.

17. The method according to claim 15, wherein, The downlink services include Physical Downlink Shared Channel (PDSCH) services or Channel State Information Reference Signal (CSI-RS).

18. The method of claim 15, further comprising: In response to determining that the wireless device is configured to determine whether the time period between the end of the PDCCH service and the CLI measurement timing exceeds the threshold duration, the PDCCH service and the CLI measurement timing are scheduled to be separated from the threshold duration by at least.

19. The method according to claim 15, wherein, The capability report indicates whether the wireless device is configured to determine whether a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to a second threshold duration. The method further includes scheduling the downlink service for at least the second threshold duration after the end of the PDCCH service in response to determining that the wireless device is configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

20. The method of claim 19, further comprising scheduling the downlink service in response to determining that the wireless device is not configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration, so as not to overlap with the CLI measurement timing.

21. The method according to claim 19, wherein, The capability report indicates Is the wireless device configured to suspend CLI measurement in response to determining that a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the duration of the second threshold? 22. A base station, comprising: A processor configured to have processor-executable instructions for performing the following operations: The wireless device receives a capability report indicating whether it is configured to determine whether the time period between the end of a Physical Downlink Control Channel (PDCCH) service and the beginning of a Cross-Link Interference (CLI) measurement exceeds a threshold duration. as well as In response to determining that the wireless device is not configured to determine whether the time period between the end of the PDCCH service and the CLI measurement timing exceeds the threshold duration, a downlink service that does not overlap with the CLI measurement timing is scheduled for the wireless device.

23. The base station according to claim 22, wherein, The processor is also configured to have processor-executable instructions that cause the capability report to indicate whether the wireless device is configured to determine whether to switch to a second Rx resource and perform a CLI measurement by determining whether the time period between the end of the PDCCH service and the beginning of the CLI measurement timing exceeds the threshold duration.

24. The base station according to claim 22, wherein, The processor is also configured to have processor-executable instructions such that the downlink service includes physical downlink shared channel (PDSCH) service or channel state information reference signal (CSI-RS).

25. The base station according to claim 22, wherein, The processor is also configured to have processor-executable instructions for performing the following operations: In response to determining that the wireless device is configured to determine whether the time period between the end of the PDCCH service and the CLI measurement timing exceeds the threshold duration, the PDCCH service and the CLI measurement timing are scheduled to be separated from the threshold duration by at least.

26. The base station according to claim 22, wherein, The capability report indicates whether the wireless device is configured to determine whether a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to a second threshold duration. Furthermore, the processor is also configured to have processor-executable instructions for: scheduling the downlink service for at least the second threshold duration after the end of the PDCCH service in response to determining whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration.

27. The base station according to claim 26, wherein, The processor is also configured to have processor-executable instructions for performing the following: in response to determining that the wireless device is not configured to determine whether the second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the second threshold duration, to schedule the downlink service so as not to overlap with the CLI measurement timing.

28. The base station according to claim 26, wherein, The processor is also configured to have processor-executable instructions that cause the capability report to indicate whether the wireless device is configured to suspend CLI measurements in response to determining that a second time period from the end of the PDCCH service to the beginning of the downlink service is less than or equal to the duration of the second threshold.

Images