Cross-link interference reporting and resource configuration

By increasing the CLI measurement reporting rate using Layer 1 and Layer 2 signaling in subband full-duplex mode, the UE receives CLI measurement configuration and reports cross-link interference, solving the problem of slow CLI measurement reporting speed and improving the spectrum utilization efficiency of the communication system.

CN123057987APending Publication Date: 2026-11-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090184.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-03-28
Publication Date
2026-11-06

AI Technical Summary

Technical Problem

In subband full-duplex mode, the cross-link interference (CLI) measurement reporting speed between network equipment and user equipment is slow, especially in dynamic environments where it is difficult to respond quickly, affecting communication efficiency.

Method used

By using Layer 1 and/or Layer 2 signaling, the CLI measurement reporting rate is increased, the UE receives CLI measurement configuration and reports cross-link interference, and resource configuration and measurement are performed using Channel State Information (CSI) reporting, thereby mitigating CLI.

Benefits of technology

It improves the speed and accuracy of CLI measurements and reporting, helps network devices dynamically schedule resources, reduces interference between UEs, and improves the spectrum utilization efficiency of wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123057987A_ABST
    Figure CN123057987A_ABST
Patent Text Reader

Abstract

A UE, a baseband processor, and a network device are described. The UE or baseband processor can receive an indication of the configuration for a Subband Full-Duplex (SBFD) serving cell. The configuration can identify one or more subcarriers for downlink resources of the SBFD serving cell, which are frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell. The UE or baseband processor can then receive a CLI measurement configuration indicating a set of resources for cross-link interference (CLI) measurements for the SBFD serving cell. The UE or baseband processor then performs CLI measurements using at least a portion of the downlink resources according to the CLI measurement configuration and sends a report to the network device serving the SBFD serving cell based at least in part on the performed CLI measurements.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates in general to wireless communication systems, including systems, apparatus, and methods for cross-link interference (CLI) reporting and resource allocation. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between network devices (e.g., base stations, radio heads, etc.) and wireless communication devices. Wireless communication system standards and protocols may include, for example, 3GPP Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs) (often referred to as Wi-Fi within industry organizations). ® ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between RAN network equipment (sometimes also commonly referred to as RAN nodes, network nodes, or simply nodes) and wireless communication equipment called UEs. 3GPP RANs can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more Radio Access Technologies (RATs) for communication between network devices and UEs. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements the NR RAT (sometimes referred to herein as the 5G RAT, 5G NR RAT, or simply NR). In some deployments, E-UTRAN may also implement the NR RAT. In some deployments, NG-RAN may also implement the LTE RAT.

[0005] The network equipment used in a RAN can correspond to that RAN. An example of E-UTRAN network equipment is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB). An example of NG-RAN network equipment is a Next Generation Node B (sometimes also called gNodeB or gNB).

[0006] The RAN provides communication services to external entities through its connection with the core network (CN). For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC). Attached Figure Description

[0007] To facilitate the identification of any particular element or action in the discussion, one or more of the most significant digits in the figure reference numerals refer to the figure number in which the element was first introduced.

[0008] Figure 1 An example wireless communication system is shown according to one or more aspects described herein.

[0009] Figure 2 An example wireless communication system for deploying subband full-duplex (SBFD) according to one or more aspects described herein is shown.

[0010] Figure 3 An example signal flow is shown based on one or more aspects described herein.

[0011] Figure 4A An example media access control (MAC) control element is shown according to one or more aspects described herein.

[0012] Figure 4B An example of Cross-Link Interference (CLI) resource signaling is shown according to one or more aspects described herein.

[0013] Figure 4C Another example of CLI resource signaling based on one or more aspects described herein is shown.

[0014] Figure 5 Example methods based on one or more aspects described herein are shown.

[0015] Figure 6 Another example method is shown based on one or more aspects described herein.

[0016] Figure 7 An example architecture of a wireless communication system according to the implementation scheme described herein is illustrated.

[0017] Figure 8 An example system for performing signaling between a wireless device and a network device according to the implementation described herein is illustrated. Detailed Implementation

[0018] Various embodiments are described with respect to processors (e.g., baseband processors), wireless devices (e.g., user equipment (UE)), or network devices. However, references to processors, wireless devices, or network devices are provided for illustrative purposes only. The example embodiments can be used with any electronic component or device capable of establishing a wireless connection and configured with hardware, software, and / or firmware for exchanging information and data via the wireless connection. Therefore, the processors, wireless devices, and network devices described herein are used to represent any suitable electronic component or device.

[0019] The radio frequency spectrum bands used by network devices to serve UEs typically operate in one of two modes: Frequency Domain Duplex (FDD) or Time Domain Duplex (TDD). In FDD mode, each frequency band is dedicated to either the uplink or downlink. Generally, network devices serving under an FDD configuration can be faster and experience less interference with neighboring network devices. However, in situations with asymmetrical uplink and downlink traffic, FDD may result in wasted spectrum due to its relative inflexibility. In TDD mode, frequency bands switch between uplink and downlink at different times. Generally, network devices serving under a TDD configuration may be relatively slower and experience more interference with neighboring network devices compared to FDD. However, TDD is more flexible to changing network conditions, for example, by dynamically allocating more or less resources between uplink and downlink as needed, and therefore utilizes spectrum more efficiently.

[0020] In some cases, FDD can be complex and relatively inflexible to deploy, while TDD may provide insufficient throughput for the uplink. There is a growing expectation that network devices will operate in full-duplex mode within the same frequency band. As further described herein, operation in Subband Full-Duplex (SBFD) mode may therefore be desired. In SBFD, network devices operate in full-duplex mode within a frequency band, while UEs typically operate in half-duplex mode (although full-duplex operation is also possible). One or more guard bands separating the uplink and downlink can be used to reduce interference.

[0021] Cross-link interference (CLI) between different combinations of network devices and UEs is becoming increasingly problematic for SBFD. For example, a network device may operate in full-duplex mode, transmitting to some UEs while simultaneously receiving from other UEs in the same service area. Therefore, a victim UE attempting to receive in a frequency band may experience CLI from a nearby aggressor UE that is transmitting. UEs can therefore measure CLI and report it to the network device, allowing the network device to take steps to help mitigate CLI, such as allocating resources for UEs to reduce CLI between UEs. However, current methods use relatively slow CLI measurement and reporting, such as Layer 3 measurement and reporting. Therefore, an increased measurement and reporting rate may be desired, for example in dynamic environments, including in serving cells where UEs move relatively quickly.

[0022] As further described herein, techniques for CLI reporting and resource configuration are described. Such techniques can result in an increased CLI measurement reporting rate, for example, by using Layer 1 and / or Layer 2 signaling. The UE can be configured by the network device to operate in an SBFD serving cell. The UE can then be configured using a CLI measurement configuration that indicates the set of resources in the SBFD serving cell used for CLI measurements. The UE performs CLI measurements on the downlink resources of the SBFD serving cell according to the CLI measurement configuration. The UE then transmits a CLI measurement report to the network device. According to some aspects described herein, the CLI report may use aspects of a Channel State Information (CSI) report or otherwise associate it with the CSI report.

[0023] This document describes various aspects of CLI reporting and resource configuration using a communication system employing SBFD communication, including a description of different interferences involving CLI within the context of SBFD communication. Signaling diagrams for providing CLI configuration, measurement, and reporting are then described. Finally, processes, systems, and apparatuses supporting CLI reporting and resource configuration as further described herein are presented.

[0024] Figure 1An example wireless communication system 100 is illustrated according to one or more aspects described herein. In one or more embodiments, the wireless communication system 100 supports one or more aspects of CLI reporting and resource configuration, as further described herein. The wireless communication system 100 includes one or more UEs 102, which may be served by a network device 104 via a communication link 106 (e.g., having a Radio Resource Control (RRC) connection established with the network device). Coverage area 108 is a service area (e.g., a cell or serving cell, which may include multiple cells) of an RF spectrum band utilized by the network device 104 serving the UE 102. Although shown as a mobile device or smartphone, the UE 102 may include any mobile or non-mobile computing device configured for wireless communication, such as a watch or extended reality (XR) device, including virtual reality (VR) or augmented reality (AR) devices. In some cases, the UE 102 may be a system that operates as a component of the UE 102.

[0025] Network device 104 may utilize SBFD configuration to provide (serve) one or more serving cells. Wireless communication system 100 illustrates an example SBFD configuration for component carrier 110 (which may also be referred to as a frequency band, frequency band, or serving cell), which includes a number of subcarriers, such as OFDM subcarriers. The SBFD configuration includes a set of time slots 112, which includes SBFD time slots having both downlink resources 114 and uplink resources 116. In some embodiments, a guard band 118 may be provided to mitigate interference between downlink and uplink signals (e.g., CLI). In some embodiments, time slot 112 may be organized into frames (e.g., radio frames). Each SBFD time slot 134 may span a number of OFDM symbols 122 (e.g., fourteen symbol periods) and consists of a set of resource blocks 120 (e.g., physical resource blocks) spanning the frequency domain of component carrier 110, where each resource block includes a number of subcarriers (e.g., 12 OFDM subcarriers per resource block). In one example, downlink resource 114 spans eight resource blocks 124, which are in two frequency groups of four. Uplink resource 116 spans two resource blocks 126 and is separated from downlink resource 114 by two guard bands in guard bands 118, each spanning one resource block 128.

[0026] In some embodiments, component carrier 110 may include SBFD slot 134 and one or more non-SBFD slots, such as downlink slot 132 or uplink slot 136, or both. In other embodiments, component carrier 110 includes only SBFD slot 134. In some embodiments, the relative number of downlink resources 114 and uplink resources 116 may be varied via configuration. Although shown as uplink resource 116 having downlink resources 114 adjacent to each other at both higher and lower frequencies, other configurations or arrangements of resources consistent with the techniques described herein are possible. For example, a single set of downlink resources in consecutive subcarriers and a single set of uplink resources in consecutive subcarriers may be configured.

[0027] As further discussed herein, UE 102 may receive configuration for the SBFD serving cell (e.g., component carrier 110) of network device 104, wherein one or more subcarriers for downlink resources are frequency-domain multiplexed with one or more subcarriers for uplink resources (FDM).

[0028] Figure 2 An example wireless communication system 200 deploying SBFD according to one or more aspects described herein is illustrated. In one or more embodiments, the wireless communication system 200 supports one or more aspects of CLI reporting and resource configuration as further described herein, and various types of interference are illustrated in systems using SBFD.

[0029] Wireless communication system 200 includes network device 104, which uses an SBFD serving cell with coverage area 212 to serve UE 102 and one or more additional UEs 206. The SBFD serving cell of network device 104 uses one or more time slots as SBFD time slot 202. Wireless communication system 200 also includes network device 210, which uses an SBFD serving cell with coverage area 214 to serve one or more UEs 208. The SBFD serving cell of network device 210 uses one or more time slots as SBFD time slot 204.

[0030] For SBFD slot 202, UE 102 can be served by network device 104 on downlink 216. For SBFD slot 202, another UE (e.g., UE 206) in the same serving cell as UE 102 can be served by network device 104 on uplink 218. Therefore, UE 102 attempting to receive on downlink 216 may experience CLI 224 due to UE 206's transmission on uplink 218. CLI 224 may also be referred to as intra-cell UE-to-UE co-channel subband CLI, or intra-cell UE-to-UE co-channel subband CLI, for example, interference at the receiving UE from UEs transmitting on non-overlapping frequency resources (e.g., subcarriers) in the same cell.

[0031] In addition to CLI 224, UE 102 may also experience CLI 226. For SBFD slot 204, a UE in a different serving cell than UE 102 (e.g., UE 208) may be served by network device 210 on downlink 234 and / or uplink 232. In some examples, SBFD slots 202 and 204 may occur during overlapping time periods, but using different sets of frequency resources (e.g., different frequency bands, different component carriers). For example, for SBFD slot 204, UE 208 may transmit on uplink 232 during the same time period that UE 102 attempts to receive on downlink 216. Therefore, UE 102 may experience CLI 226 due to UE 208's transmission on uplink 232. CLI 226 may also be referred to as inter-cell UE-to-UE co-channel subband CLI or inter-cell UE-to-UE co-channel subband CLI, for example, interference at the receiving UE from a UE transmitting on non-overlapping frequency resources (e.g., subcarriers) in a neighboring cell.

[0032] In addition to CLI, UE 102 may also experience co-channel interference. For example, a neighboring network device (network device 210) may transmit to UE 208 on downlink 234. UE 102 receiving data from network device 104 on downlink 216 may experience interference 230.

[0033] Other forms of interference and CLI may also exist in the wireless communication system 200 using SBFD. In the first example, network device 104 may experience network device self-interference 220. In the second example, network device 104 may experience network device-to-network device co-channel subband CLI 222 from a neighboring network device (network device 210). In the third example, network device 104 may experience inter-network cell UE-to-network device interference 228 (e.g., UE-to-network device UL co-channel interference) due to UE 208's transmission on uplink 232.

[0034] As further described herein, UE 102 may receive from network device 104 a CLI measurement configuration indicating a set of resources for CLI measurements of the SBFD serving cell of network device 104. Based on this CLI measurement configuration, UE 102 may then perform CLI measurements using at least a portion of downlink resources, such as downlink resources of SBFD slot 202. As further described herein, in some embodiments, the measurement may be a Received Signal Strength Indicator (RSSI) measurement (RSSI CLI measurement). In other embodiments, the measurement may be a Sounding Reference Signal (SRS) measurement (SRS CLI measurement). UE 102 may then send a report to network device 104 based at least in part on the performed CLI measurements. This report may be sent on uplink 232. As further described herein, the report may be a Layer 1 or Layer 2 report. That is, the report may use Layer 1 or Layer 2 resources to report CLI measurement results.

[0035] Figure 3 An example signal flow 300 is illustrated according to one or more aspects described herein. In one or more embodiments, signal flow 300 supports one or more aspects of CLI reporting and resource configuration, as further described herein. Signal flow 300 includes signaling and actions performed by UE 102, network device 104, and one or more UEs 302, and between these UEs and the network device. In some examples, one or more UEs 302 may be examples of the UEs described herein, including UE 206 and / or UE 208.

[0036] At 310, UE 102 receives an indication of the SBFD configuration used by network device 104 (e.g., the SBFD serving cell served by network device 104). In some embodiments, the SBFD serving cell configuration identifier or otherwise indicates one or more subcarriers for downlink resources and one or more subcarriers for uplink resources, for example, as further described with reference to wireless communication system 100. For example, UE 102 may receive one or more control messages, such as system information (e.g., one or more master information blocks or system information blocks) and RRC signaling (e.g., RRC establishment signaling), which identify the SBFD configuration for the serving cell for UE 102.

[0037] At 312, UE 102 may send UE capability signaling to network device 104. In one or more examples, the UE capability signaling may be RRC signaling. In some implementations, the UE capability signaling may optionally identify the UE capability configured using RSSI resources for CLI measurements. The UE capability signaling may also identify the maximum number of values ​​that the UE can report for RSSI CLI measurements (e.g., MaxnrofReportedCLI-RSSI).

[0038] In other embodiments, UE capability signaling may identify UE capabilities configured using SRS resources for CLI measurements. In still other embodiments, signaling may indicate UE capabilities configured using both RSSI resources and SRS resources. UE capability signaling may identify the maximum number of values ​​the UE can report for SRS CLI measurements (e.g., MaxnrofReportedSRS-RSRP). For example, when both RSSI CLI and SRS-RSRP values ​​are reported in the same report, the maximum number of values ​​the UE can report for RSSI CLI may be the same as or different from the maximum number of values ​​the UE can report for SRS-RSRP.

[0039] In some implementations, UE capability signaling may identify a UE capability to send a single report based at least in part on both the performed CLI measurement and CSI measurement (e.g., UE capability signaling may specify the number or number n of reports in a single report). For example, the CSI measurement may be a CSI measurement for link adaptation, beam management, or both.

[0040] At 314, UE 102 may receive configuration signaling from network device 104 indicating configurations for UE 102 to use for CLI measurements and reporting. The configuration signaling indicates configurations for UE 102 to use for measuring CLI resources on the SBFD serving cell. The configuration signaling may also provide reporting configurations for UE 102 to use for reporting CLI measurements, as further discussed herein, including CLI measurement reporting with reference to 324.

[0041] In one or more examples, the configuration signaling includes an indication of CLI measurement resources (e.g., cli-ResourceForCrossLInkInterference). In some embodiments, the indication of CLI measurement resources may be in CSI report configuration signaling (e.g., CSI-ReportConfig). In some embodiments, the CLI measurement configuration is associated with a CSI report configuration identifier (e.g., CSI-ResourceConfigId) of a CSI resource configuration that identifies a list of CLI reference signal resources. For example, the corresponding identifier (e.g., CSI-ResourceConfigId) is associated with a CLI resource list (e.g., CLI-RS-ResourceList), which may also be referred to as a CLI reference signal resource list.

[0042] In one or more embodiments, the CLI reference signal resource list may include one or more SRS resources and one or more RSSI resources for CLI measurements. For example, the CLI reference signal resource list (e.g., CLI-RS-ResourceList) may include one or more SRS resources (e.g., SRS-ResourceConfigCLI) and one or more RSSI resources (e.g., RSSIResourceConfigCLI) for CLI measurements.

[0043] In one or more embodiments, the CLI measurement configuration includes a CLI reference signal resource list (e.g., CLI-RS-ResourceList), and each CLI reference signal resource in the CLI reference signal resource list is associated with the same serving cell index (e.g., ServCellIndex) as every other CLI reference signal resource in that CLI reference signal resource list. In some embodiments, additionally or alternatively, the CLI measurement configuration includes a CLI reference signal resource list (e.g., CLI-RS-ResourceList), and each CLI reference signal resource in the CLI reference signal resource list is associated with the same bandwidth portion (BWP) identifier (e.g., BWP-Id) as every other CLI reference signal resource in that CLI reference signal resource list. In some embodiments, the UE ignores carriers in the CSI reporting configuration (e.g., CSI-ReportConfig), ignores BWP identifiers (e.g., bwp-Id) in the CSI resource configuration (e.g., CSI-ResourceConfig), or both. In some implementations, if configured, the UE ignores the reference serving cell index (e.g., refServCellIndex) and reference BWP (e.g., ref-BWP) in the SRS resource configuration (e.g., SRS-ResourceConfigCLI) used for CLI. Additionally or alternatively, if configured, the UE ignores the reference serving cell index (e.g., refServCellIndex) and reference BWP (e.g., ref-BWP) in the SRS resource configuration (e.g., SRS-ResourceConfigCLI) used for CLI. Additionally or alternatively, if configured, the UE ignores the reference serving cell index (e.g., refServCellIndex) in the RSSI resource configuration (e.g., RSSI-ResourceConfigCLI).

[0044] In one or more implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the SRS resources identified by the CLI reference signal resource list are within the uplink resources of the SBFD serving cell. In one example, if the CLI reference signal resource list (e.g., CLI-RS-ResourceList) includes SRS resources (e.g., SRS-ResourceConfigCLI) resources, then the SRS resources are configured within the uplink subband configuration, such as the uplink resources configured for the SBFD serving cell.

[0045] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and RSSI resources identified by the CLI reference signal resource list are within a downlink BWP that spans at least a portion of both one or more subcarriers for downlink resources and one or more subcarriers for uplink resources. In some implementations, RSSI resources identified by the CLI reference signal resource list are within a portion of one or more subcarriers for downlink resources. In some implementations, RSSI resources identified by the CLI reference signal resource list are within a portion of one or more subcarriers for uplink resources, and SRS resources are identified by the CLI reference signal resource list. In one or more implementations, RSSI resources being within a downlink BWP, within a portion of downlink resources, or within a portion of uplink resources means that the starting physical resource block (PRB) (e.g., startPRB) and the number of PRBs (e.g., nrofPRBs) for each resource are respectively within a downlink BWP, within a portion of downlink resources, or within a portion of uplink resources.

[0046] In one or more embodiments, the CSI resource configuration identifier associated with the CLI measurement configuration indicates a resource type in a set of resource types for resources in a CLI reference signal resource list (e.g., CLI-RS-ResourceList). CLI measurements can be performed based on the resource type. The resource type can be one of aperiodic, semi-persistent, or periodic resources. In some embodiments, UE 102 determines (identifies) the resource type used for the CSI resource configuration identifier.

[0047] In one or more embodiments, if the CLI reference signal resource list (e.g., CLI-RS-ResourceList) includes SRS resources or RSSI resources for CLI (e.g., SRS-ResourceConfigCLI or RSSI-ResourceConfigCLI), the temporal behavior of each SRS resource is given by an indicator of the resource type in the configuration for the SRS or RSSI resource, respectively. In some embodiments, for RSSI resources for CLI, the information element RSSI-ResourceConfigCLI may be updated to indicate resourceType = one of aperiodic, semi-persistent, or periodic. In some cases, for the present art, only periodic resource types for SRS or RSSI CLI are allowed to be configured, rather than any of aperiodic, semi-persistent, or periodic as described with respect to some embodiments herein. In one or more embodiments, when the CLI reference signal resource list includes RSSI resources for CLI measurements, the RSSI resource configuration for CLI indicates the slot offset for aperiodic resources, or the period and offset for semi-persistent resources.

[0048] In one or more embodiments, at 314, UE 102 may receive RRC signaling indicating the number of SRS reports (e.g., nrofReportedSRS-RSRP) of different CLI RSSI reports to be set for each report in a single report. In some examples, the number of SRS reports (e.g., nrofReportedSRS-RSRP) is constrained (limited) to not exceed the maximum number of reports indicated in the UE capability signaling (e.g., MaxnrofReportedCLI-RSSI). In one or more embodiments, the configuration indicates that the report should include the resource index of the SRS CLI resource (e.g., SRS-ResourceConfigCLI) in the corresponding resource list (e.g., CLI-RS-ResourceList). In some embodiments, UE 102 may be configured to report a certain number (e.g., nrofReportedCLI-RSSI) of the worst (e.g., SRS-ResourceConfigCLI) resources. In other embodiments, the number of best resources is reported. Reporting for the first resource of SRS-RSRP measurements for CLI can be absolute (e.g., 7 bits representing the absolute measurement), but for other resources it can be differential (e.g., 4 bits representing the measurement relative to the absolute value), as further specified herein. Reporting for CLI applicable to CLI-RSSI-RI, CLI-RSSI, and differential CLI-RSSI can be similar.

[0049] At 316, UE 102 can participate in communication with network device 104 via at least the SBFD serving cell, including data and control.

[0050] At 318, UE 102 receives a CLI control message. In some embodiments, the CLI control message is a MAC CE, for example, as described with reference to MAC CE 401. In one or more embodiments, the MAC CE instructs UE 102 to activate a set of resources for CLI measurements and identifies the SBFD serving cell. In some embodiments, the MAC CE includes an identifier for a semi-persistent resource indicating a list of CLI reference signal resources.

[0051] In other embodiments, the CLI control message is a DCI message, for example, as described with reference to CLI resource signaling 402 and / or CLI resource signaling 403. In some embodiments, candidate time slots for CLI measurements are based at least in part on time slot offset values, wherein CLI measurements are performed in SBFD time slots following the candidate time slots, based on the candidate time slots being non-SBFD time slots. UE 102 may determine the candidate time slots. In some embodiments, the time slot is the first SBFD time slot following the candidate time slot.

[0052] At 320, UE 102 may optionally provide acknowledgment of received CLI control messages (e.g., received MAC CE (e.g., MAC CE 401)). In some embodiments, UE 102 determines candidate time slots for CLI measurements based on the number of SBFD time slots following the time slot in which acknowledgment is sent and received. In some embodiments, the number of time slots may be determined in cases where the CLI-RS resource is a semi-persistently configured resource.

[0053] At 322, UE 102 uses at least a portion of the downlink resources of the SBFD serving cell to perform CLI measurements. UE 102 listens for and receives CLI signals (e.g., SRS or signals used for RSSI measurements) based on the CLI measurement configuration at 314 and the CLI control message at 318. Such CLI signals may be transmitted by one or more UEs 302.

[0054] At position 324, UE 102 sends a report including CLI measurement results to network device 104. In some embodiments, the report is sent by UE 102 using Layer 1 resources according to the CLI report field configuration. In other embodiments, the report is sent by UE 102 using Layer 2 resources according to the CLI report field configuration.

[0055] In one or more implementations, the CLI reporting field for reporting at position 324 may be specified by Table 1, which specifies the bit width for CSI-RS Resource Indicator (CRI), SRS-RSRP, CLI-RSSI, Differential RSRP, and Differential RSSI:

[0056]

[0057] Table 1: Bit width used for CLI report fields

[0058] in This refers to the number of SRS resources (e.g., SRS-ResourceConfigCLI resources) used for CLI in the corresponding CLI resource list (e.g., CLI-RS-ResourceList), and This is the number of RSSI resources (e.g., RSSI-ResourceConfigCLI resources) used for CLI in the corresponding CLI resource list (e.g., CLI-RS-ResourceList). Although Table 1 shows a specific number and order of bits in the CLI report, other orderings or numbers consistent with the description provided herein may be used.

[0059] In one or more implementations, the mapping order of CLI fields for a specific report (e.g., #n) used for reporting at position 324 can be specified by Table 2:

[0060]

[0061] Table 2: Mapping order of CLI report fields for a report for CLI-RSSI and / or SRS-RSRP reports

[0062] In Table 2, for each row, the bit width is given by the corresponding field provided in Table 1. As further discussed herein, for example, referring to the UE capability signaling at 312, UE 102 can be configured using one or both of the SRS resource set (e.g., SRS-ResourceListConfigCLI) or the RSSI resource set (e.g., RSSI-ResourceListConfigCLI). Although Table 2 shows a specific number and order of fields in the CLI report, other orderings or numbers consistent with the description provided herein can be used.

[0063] In one or more embodiments, the maximum number (quantity) of reported CLI measurements for RSSI (e.g., MaxnrofReportedCLI-RSSI) or the maximum number (quantity) of reported CLI measurements for SRS resources (e.g., MaxnrofReportedCLI-SRS), or both, may be available to UE 102. In some embodiments, the maximum number of RSSI and / or SRS may be subject to UE capabilities, such as those reported by UE 102 at 312. In some embodiments, the maximum number of RSSI is the same as the maximum number of SRS. In other embodiments, the maximum number of RSSI differs from the maximum number of SRS. In some embodiments, these reported maximum values ​​may differ from the maximum values ​​when the UE instructs its UE capabilities to report both CLI-RSSI and SRS-RSRP in a single report. In some examples, the corresponding reporting quantities (e.g., reportQuantity) in the CSI reporting configuration (e.g., CSI-ReportConfig) will be CLI-RSSI and SRS-RSRP, respectively.

[0064] In one or more embodiments, CLI measurement report 324 may be a report for both CLI-RSSI and SRS-RSRP, or include such a report. In some embodiments, UE 102 may be configured to provide a single report including both CLI-RSSI and SRS-RSRP. In some examples, two or more relative priority levels may be defined, such as priority 0 being defined as a higher priority than priority 1. In some embodiments, priority 0 may include SRS-RSRP-RI #1, SRS-RSRP-RI #2, SRS-RSRP, and differential SRS-RSRP; and priority 1 may include CLI-RSSI-RI #1, CLI-RSSI-RI #2, CLI-RSSI, and differential CLI-RSSI. In another embodiment, priority 0 may include SRS-RSRP-RI #1, SRS-RSRP, CLI-RSSI-RI #1, and CLI-RSSI; and priority 1 may include SRS-RSRP-RI #2, differential SRS-RSRP, CLI-RSSI-RI #2, and differential CLI-RSSI. In another implementation, all CLI reports with a certain report (e.g., report #n) have the same priority level, and in some examples, all CLI reports may be discarded together (e.g., if needed).

[0065] In one or more embodiments, CLI measurement report 324 may be a CSI report, include a CSI report, or be included in a CSI report. In one or more embodiments, the configuration of CLI measurement report 324 or a report including CLI measurement report 324 may be based on the UE's ability to include both CLI and CSI reports in a single report. In one or more embodiments, the priority of CLI reports may be determined relative to CSI reports. In some embodiments, CLI measurement reports are given a higher priority than CSI reports. In other embodiments, CLI reports are given a lower priority than CSI reports if the CSI report carries Layer 1 RSRP information (e.g., L1-RSRP) and / or Layer 1 SINR information (e.g., L1-SINR), and a higher priority if the CSI report carries measurement information other than L1-RSRP and / or L1-SINR. In still other embodiments, CLI reports are given a lower priority than CSI reports.

[0066] Figure 4A An example MAC CE 401 is shown according to one or more aspects described herein. In one or more implementations, the MAC CE 401 supports one or more aspects of CLI reporting and resource configuration, as further described herein.

[0067] In one or more implementations, CLI resources can be semi-persistently scheduled. For example, CLI resources in a resource list for CLI reference signals (e.g., CLI-RS-ResourceList) can be configured using a resource type (e.g., resourceType) for CLI resources, which is set to semi-persistent. MAC CE 401 can then be used to activate or deactivate the semi-persistently scheduled CLI resources.

[0068] MAC CE 401 includes a CLI-RS-ResourceList cell ID field 412, an SP CLI-RS-ResourceListID field 414, an activation / deactivation (A / D) field 416, and one or more reserved (R) bits. The CLI-RS-ResourceList cell ID field 412 indicates the identifier of the serving cell (e.g., an SBFD serving cell) that contains the activated / deactivated SP CLI-RS-ResourceList. The SP CLI-RS-ResourceList ID field 414 indicates the identifier of the SP CLI-RS-ResourceList identified by a CLI measurement configuration (e.g., csi-ResourceConfigId) that will be activated or deactivated by MAC CE 401. In some embodiments, the SP CLI-RS-ResourceListID field 414 is 7 bits long. The A / D field 416 indicates whether the indicated SP CLI-RS-ResourceList is activated or deactivated. In some embodiments, this field is set to 1 to indicate activation, otherwise it indicates deactivation (e.g., when set to 0).

[0069] In one or more implementations, not all time slots of the serving cell are available for CLI measurements. For example, one or more time slots of the serving cell may be configured for communication other than using SBFD. In other words, in some examples, not all time slots are SBFD time slots. Therefore, for CLI resources configured as periodic or semi-persistent (e.g., where the higher-layer parameter resourceType is set to periodic or semi-persistent), the candidate time slots for which the configured CLI-RS can be used for CLI measurements include SBFD time slots that satisfy the following equation:

[0070]

[0071] (For example, it could be the number of time slots in a frame used for SCS). (For example, it could be a frame number). These are parameters for higher-level configurations of period (in time slots) and time slot offset, respectively. It is the subcarrier spacing (SCS) of the BWP in the subband of the SBFD time slot. It is used for SCS configuration. The time slot number within the frame.

[0072] For CLI-RS resources configured as semi-persistent (e.g., where the higher-level parameter resourceType is set to semi-persistent), the slot number ( () is a time slot The subsequent SBFD time slot, in which This refers to the time slot in which the UE will send a PUCCH with HARQ-ACK information, which corresponds to a PDSCH carrying a MAC CE activation command for semi-persistent CLI. It is PUCCH's SCS.

[0073] Figure 4B An example of CLI resource signaling 402 is shown, which is based on one or more aspects described herein. Figure 4C Another example of CLI resource signaling 403 according to one or more aspects described herein is shown. In one or more embodiments, CLI resource signaling 402 and CLI resource signaling 403 support one or more aspects of CLI reporting and resource configuration, as further described herein.

[0074] In one or more implementations, CLI resources can be scheduled non-periodically. For example, CLI resources in a resource list for CLI reference signals (e.g., CLI-RS-ResourceList) can be configured using a resource type (e.g., resourceType) for CLI resources, which is set to periodic. Downlink Control Information (DCI) message 422 can then be used to trigger (schedule) CSI RS resources available for CLI measurements.

[0075] For CLI-RS resources configured as aperiodic (e.g., where the higher-level parameter resourceType is set to aperiodic), the candidate time slots for CLI measurements triggered by the CLI RS resource are no earlier than […]. The first SBFD time slot, in which It is the time slot that receives the trigger DCI, and It is the slotOffset parameter configured at a higher level (e.g., RRC).

[0076] As illustrated with reference to CLI resource signaling 402, DCI message 422 is received in time slot 426, and time slot 428 is an SBFD time slot. DCI message 422 indicates a CLI resource that can be used by the UE for CLI measurements. In one or more embodiments, k indicates time slot 428 for aperiodic CLI reference signaling resource 424 (e.g., two time slots after time slot 426 in which DCI message 422 is received). In the example of CLI resource signaling 402, because time slot 428 is an SBFD time slot, CLI measurements can be performed by the UE in time slot 428.

[0077] As illustrated with reference to CLI resource signaling 403, DCI message 432 is received in time slot 436. Time slot 438 is not an SBFD time slot, but time slot 440 is an SBFD time slot. DCI message 432 indicates CLI resources that can be used by the UE for CLI measurements. In one or more embodiments, k indicates time slot 438 following time slot 436 in which DCI message 432 is received, for aperiodic CLI reference signal resource 444. In the example of CLI resource signaling 403, because time slot 438 is not an SBFD time slot, CLI measurements may not be performed by the UE in time slot 438. In this example, the next SBFD time slot after time slot 438 is the subsequent time slot, i.e., time slot 440. Therefore, CLI measurements can be performed by the UE in time slot 440 in response to DCI message 432.

[0078] Figure 5 An example method 500 for wireless communication performed by a UE is illustrated. In some cases, the UE may be a wireless device 802 or a UE 102. In some cases, method 500 may be executed by a baseband processor of the UE. In some embodiments, the baseband processor may include one or more processor cores and memory coupled to the processor cores. The memory may store instructions that, when executed by the processor cores, cause the baseband processor to perform the operations of method 500. While the baseband processor is performing the operations of method 500, the baseband processor may also cause other components of the UE to perform or interrupt various operations.

[0079] At 502, method 500 includes: receiving SBFD configuration for the SBFD serving cell. In some embodiments, method 500 includes: receiving an indication of configuration for the SBFD serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell.

[0080] At 504, method 500 includes receiving a CLI measurement configuration. In some embodiments, method 500 receives a CLI measurement configuration indicating a set of resources for CLI measurements of the SBFD serving cell.

[0081] At 506, method 500 includes processing CLI measurements. In some embodiments, method 500 processes CLI measurements obtained using at least a portion of downlink resources based on CLI measurement configuration.

[0082] At 508, method 500 includes: sending a CLI measurement report. In some embodiments, method 500 sends the report based at least in part on the CLI measurement performed.

[0083] In one or more embodiments, the method further includes receiving a CSI report configuration indicating a CLI measurement configuration. In some embodiments, the CLI measurement configuration is associated with a CSI report configuration identifier for a CSI resource configuration that identifies a list of CLI reference signal resources.

[0084] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, each CLI reference signal resource in the list being associated with the same serving cell index and BWP identifier as every other CLI reference signal resource in the list.

[0085] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the SRS resources identified by the CLI reference signal resource list are within the uplink resources of the SBFD serving cell.

[0086] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are within a downlink BWP that spans at least a portion of both one or more subcarriers for downlink resources and one or more subcarriers for uplink resources.

[0087] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are located within a portion of one or more subcarriers used for downlink resources.

[0088] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are within a portion of one or more subcarriers used for uplink resources, and the SRS resources are identified by the CLI reference signal resource list.

[0089] In one or more embodiments, the method further includes: determining a resource type among multiple resource types for resources in a CLI reference signal resource list, for a CSI resource configuration identifier associated with a CLI measurement configuration, wherein the CLI measurement is processed according to the resource type, and the resource type includes one of aperiodic resources, semi-persistent resources, or periodic resources. In some embodiments, the CLI reference signal resource list includes RSSI resources for CLI measurements, and the RSSI resource configuration for CLI indicates a slot offset for aperiodic resources or a period and offset for semi-persistent resources.

[0090] In one or more embodiments, the method further includes: receiving a MAC CE indicating activation of a set of resources for CLI measurements, the MAC CE identifying the SBFD serving cell and an identifier of a semi-persistent resource indicating a CLI reference signal resource list.

[0091] In one or more embodiments, the method further includes: receiving a MAC CE indicating activation of a set of resources for CLI measurements; sending an acknowledgment of the received MAC CE in a time slot; and determining candidate time slots for CLI measurements based at least in part on a number of SBFD time slots following the time slot in which the acknowledgment is sent.

[0092] In one or more embodiments, the method further includes: receiving a DCI message that schedules at least a portion of downlink resources for CLI measurements; and determining candidate time slots for CLI measurements based at least in part on time slot offset values, wherein the CLI measurements are obtained from measurements in SBFD time slots following the candidate time slots based at least in part on the candidate time slots being non-SBFD time slots.

[0093] In one or more embodiments, the method further includes: identifying a Layer 1 or Layer 2 resource used to send a report based on a CLI report field configuration, the report being sent using a Layer 1 or Layer 2 resource. In one or more embodiments, the method further includes: sending capability signaling that identifies a UE capability configured using one or more of an RSSI resource or an SRS resource for CLI measurements.

[0094] In one or more embodiments, the method further includes: sending capability signaling that identifies one or both of the following: the maximum number of values ​​that the UE can report for RSSI CLI measurements or the maximum number of values ​​that the UE can report for SRS CLI measurements.

[0095] In one or more embodiments, the method further includes: sending capability signaling that identifies a UE capability to send a single report based at least in part on both the processed CLI measurement and the CSI measurement. In one or more embodiments, the method further includes: obtaining the CSI measurement; and determining a relative priority between reporting the processed CLI measurement and the obtained CSI measurement, wherein the report is sent according to the relative priority.

[0096] Method 500 can be embodied, extended, or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0097] Figure 6 An example method 600 for wireless communication performed by a network device is illustrated. In one or more embodiments, method 600 supports one or more aspects of CLI reporting and resource configuration, as further described herein. In some cases, the network device may be one of network device 104, network device 820, or other network devices described herein. Method 600 may be performed using a processor, transceiver (e.g., main radio component), or other components of the network device.

[0098] At 602, method 600 includes: transmitting an SBFD configuration for the SBFD serving cell, including both downlink resources and uplink resources. In some embodiments, method 600 includes: transmitting an indication of a configuration for the SBFD serving cell, the configuration identifying one or more subcarriers for the downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for the uplink resources of the SBFD serving cell.

[0099] At 604, method 600 includes: sending CLI measurement configuration. In some embodiments, method 600 includes: sending to the UE a CLI measurement configuration indicating a set of resources for CLI measurements of the SBFD serving cell.

[0100] At 606, method 600 includes: receiving a CLI measurement report. In some embodiments, method 600 includes: receiving a report from a UE, the report being at least partially based on CLI measurements performed by the UE using at least a portion of downlink resources according to a CLI measurement configuration.

[0101] In one or more embodiments, the method further includes sending a CSI report configuration indicating a CLI measurement configuration. In some embodiments, the CLI measurement configuration is associated with a CSI report configuration identifier for a CSI resource configuration that identifies a list of CLI reference signal resources.

[0102] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, each CLI reference signal resource in the list being associated with the same serving cell index and BWP identifier as every other CLI reference signal resource in the list.

[0103] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the SRS resources identified by the CLI reference signal resource list are within the uplink resources of the SBFD serving cell.

[0104] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are within a downlink BWP that spans at least a portion of both one or more subcarriers for downlink resources and one or more subcarriers for uplink resources.

[0105] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are located within a portion of one or more subcarriers used for downlink resources.

[0106] In some implementations, the CLI measurement configuration includes a CLI reference signal resource list, and the RSSI resources identified by the CLI reference signal resource list are within a portion of one or more subcarriers used for uplink resources, and the SRS resources are identified by the CLI reference signal resource list.

[0107] In one or more embodiments, the method further includes: determining a resource type among multiple resource types for resources in a CLI reference signal resource list for a CSI resource configuration identifier associated with a CLI measurement configuration, wherein the CLI measurement is performed by the UE according to the resource type, and the resource type includes one of aperiodic resources, semi-persistent resources, or periodic resources. In some embodiments, the CLI reference signal resource list includes RSSI resources for CLI measurements, and the RSSI resource configuration for CLI indicates a slot offset for aperiodic resources or a period and offset for semi-persistent resources.

[0108] In one or more embodiments, the method further includes sending a MAC CE to the UE indicating activation of a set of resources for CLI measurements, the MAC CE identifying the SBFD serving cell and an identifier of a semi-persistent resource indicating a CLI reference signal resource list.

[0109] In one or more embodiments, the method further includes: sending a MAC CE to the UE indicating activation of a resource set for CLI measurements; receiving an acknowledgment of the received MAC CE from the UE in a time slot; and determining candidate time slots for CLI measurements based at least in part on a certain number of SBFD time slots following the time slot in which the acknowledgment is received.

[0110] In one or more embodiments, the method further includes: sending a DCI message to the UE scheduling at least a portion of downlink resources for CLI measurements; determining candidate time slots for CLI measurements based at least in part on time slot offset values, wherein the CLI measurements are performed by the UE in an SBFD time slot following the candidate time slot based at least in part on the candidate time slot being a non-SBFD time slot.

[0111] In one or more embodiments, the method further includes: identifying a Layer 1 or Layer 2 resource used to send a report based on a CLI report field configuration, the report being sent using a Layer 1 or Layer 2 resource. In one or more embodiments, the method further includes: receiving capability signaling from the UE, the capability signaling identifying a UE capability configured using one or more of an RSSI resource or an SRS resource for CLI measurements.

[0112] In one or more embodiments, the method further includes: receiving capability signaling from the UE, the capability signaling identifying one or both of the following: the maximum number of values ​​that the UE can report for RSSI CLI measurements or the maximum number of values ​​that the UE can report for SRS CLI measurements.

[0113] In one or more embodiments, the method further includes: receiving capability signaling from the UE, the capability signaling identifying a UE capability to send a single report based at least in part on both CLI measurements and CSI measurements. In one or more embodiments, the method further includes: determining a relative priority between reporting CLI measurements and CSI measurements, wherein the report is received according to the relative priority.

[0114] Method 600 may be embodied, extended or modified in various ways, as described in the following paragraphs and elsewhere in this description.

[0115] The embodiments contemplated herein include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 500 or 600. In the context of method 500, the non-transitory computer-readable medium may be, for example, the memory of a UE (such as memory 806 of a wireless device 802 as a UE, as described herein) or the memory of a processor. In the context of method 600, the non-transitory computer-readable medium may be, for example, the memory of a network device (such as memory 824 of a network device 820, as described herein).

[0116] The embodiments contemplated herein include an apparatus having logic components, modules, or circuitry for performing one or more elements of method 500 or 600. In the context of method 500, the apparatus may be, for example, a UE (such as wireless device 802 as a UE). In the context of method 600, the apparatus may be, for example, a network device (such as network device 820, as described herein).

[0117] The embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media that use or store instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 500 or 600. In the context of method 500, the apparatus may be, for example, a UE (such as wireless device 802 as a UE, as described herein). In the context of method 600, the apparatus may be, for example, a network device (such as network device 820, as described herein).

[0118] The implementation schemes envisioned herein include signals as described or associated with one or more elements of method 500 or 600.

[0119] The embodiments contemplated herein include a computer program or computer program product having instructions, wherein a processor executes the program to cause the processor to perform one or more elements of method 500 or 600. In the context of method 500, the processor may be a processor of a UE (such as processor 804 of wireless device 802 as a UE, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the UE (such as memory 806 of wireless device 802 as a UE, as described herein). In the context of method 600, the processor may be a processor of a network device (such as processor 822 of network device 820, as described herein), and the instructions may be located, for example, in the processor and / or in the memory of the network device (such as memory 824 of network device 820, as described herein).

[0120] Figure 7 An example architecture of a wireless communication system according to the implementation scheme described herein is illustrated. The following description is provided for example wireless communication system 700, which operates in conjunction with LTE system standards or specifications and / or 5G or NR system standards or specifications as provided by 3GPP technical specifications.

[0121] As shown in the figure, the wireless communication system 700 includes UE 702 and UE 704 (but any number of UEs may be used). In this example, UE 702 and UE 704 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0122] UE 702 and UE 704 can be configured to communicatively couple with RAN 706. In implementations, RAN 706 can be NG-RAN, E-UTRAN, etc. UE 702 and UE 704 utilize connections (or channels) with RAN 706 (shown as connection 708 and connection 710, respectively), each of these connections including a physical communication interface. RAN 706 may include one or more network devices (such as base station 712 and base station 714) implementing connection 708 and connection 710.

[0123] In this example, Connection 708 and Connection 710 are air interfaces that enable this type of communication coupling and are compliant with the RAT used by RAN 706, such as LTE and / or NR, for example.

[0124] In some implementations, UE 702 and UE 704 may also exchange communication data directly via sidelink interface 716. UE 704 is shown configured to access an access point (shown as AP 718) via connection 720. By way of example, connection 720 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, while AP 718 may include Wi-Fi. ® Router. In this example, AP 718 may connect to another network (e.g., the Internet) without using CN 724.

[0125] In the implementation, UE 702 and UE 704 may be configured to communicate with each other or with base station 712 and / or base station 714 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication)); however, the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0126] In some implementations, all or some of the base stations in base station 712 or base station 714 may be implemented as one or more software entities running on a server computer as part of a virtual network. Furthermore, or in other implementations, base station 712 or base station 714 may be configured to communicate with each other via interface 722. In implementations where the wireless communication system 700 is an LTE system (e.g., when CN 724 is an EPC), interface 722 may be an X2 interface. This X2 interface may be defined between two or more network devices (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In implementations where the wireless communication system 700 is an NR system (e.g., when CN 724 is a 5GC), interface 722 may be an Xn interface. The Xn interface may be defined between two or more network devices (e.g., two or more gNBs, etc.) connected to the 5GC, between base station 712 (e.g., gNB) and eNB connected to the 5GC, and / or between two eNBs connected to the 5GC (e.g., CN 724).

[0127] RAN 706 is shown communicatively coupled to CN 724. CN 724 may include one or more network elements 726 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 702 and UE 704) connected to CN 724 via RAN 706. Components of CN 724 may be implemented in a single physical device or a separate physical device including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media).

[0128] In the implementation scheme, CN 724 may be an EPC, and RAN 706 may be connected to CN 724 via S1 interface 728. In the implementation scheme, S1 interface 728 may be divided into two parts: an S1 user plane (S1-U) interface, which carries service data between base station 712 or base station 714 and service gateway (S-GW); and an S1-MME interface, which is the signaling interface between base station 712 or base station 714 and mobility management entity (MME).

[0129] In the implementation scheme, CN 724 may be a 5GC, and RAN 706 may be connected to CN 724 via NG interface 728. In the implementation scheme, NG interface 728 may be divided into two parts: NG user plane (NG-U) interface, which carries service data between base station 712 or base station 714 and user plane function (UPF); and S1 control plane (NG-C) interface, which is the signaling interface between base station 712 or base station 714 and access and mobility management function (AMF).

[0130] Generally, application server 730 can be a component that provides applications (e.g., packet-switched data services) that use Internet Protocol (IP) bearer resources with CN 724. Application server 730 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 702 and UE 704 via CN 724. Application server 730 can communicate with CN 724 via IP communication interface 732.

[0131] Figure 8 An example system 800 for performing signaling 838 between a wireless device 802 and a network device 820 according to an embodiment described herein is illustrated. System 800 may be part of a wireless communication system as described herein. Wireless device 802 may be, for example, a UE of a wireless communication system. Network device 820 may be, for example, a base station (e.g., an eNB or gNB) or a radio headend of a wireless communication system.

[0132] Wireless device 802 may include one or more processors 804. Processor 804 is executable instructions that cause various operations of wireless device 802 to be performed as described herein. Processor 804 may include one or more baseband processors, which are implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0133] Wireless device 802 may include memory 806. Memory 806 may be a non-transitory computer-readable storage medium that stores instructions 808, which may include, for example, instructions executed by processor 804. Instructions 808 may also be referred to as program code or a computer program. Memory 806 may also store data used by processor 804 and results calculated by the processor.

[0134] Wireless device 802 may include one or more transceivers 810 (also collectively referred to as transceivers 810), which may include radio frequency (RF) transmitter and / or receiver circuitry that uses antenna 812 of wireless device 802 to facilitate to-and-for and / or signaling from wireless device 802 to other devices (e.g., network device 820) and / or from wireless device 802 in accordance with corresponding RATs (e.g., signaling 838).

[0135] Wireless device 802 may include one or more (e.g., one, two, four, eight or more) antennas 812. In embodiments with multiple antennas 812, wireless device 802 may fully utilize the spatial diversity of such multiple antennas 812 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, MIMO behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by wireless device 802 may be implemented according to pre-decoding (or digital beamforming) applied to wireless device 802, which multiplexes the data streams among antennas 812 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some embodiments may use a single-user MIMO (SU-MIMO) method (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) method (where individual data streams may be directed to individual (different) receivers at different locations in the spatial domain).

[0136] In some implementations with multiple antennas, wireless device 802 can implement analog beamforming technology, whereby the phase of the signal transmitted by antenna 812 is relatively adjusted so that the (joint) transmission of antenna 812 can be directed (this is sometimes referred to as beam control).

[0137] Wireless device 802 may include one or more interfaces 814. Interfaces 814 can be used to provide input to or output to wireless device 802. For example, wireless device 802 as a UE may include interfaces 814, such as microphones, speakers, touchscreens, buttons, etc., to allow input and / or output from a user of the UE to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 810 / antenna 812 already described), allowing communication between the UE and other devices, and can be configured according to known protocols (e.g., Wi-Fi). ® ,Bluetooth ® (etc.) to perform the operation.

[0138] Wireless device 802 may include CLI measurement manager 816. CLI measurement manager 816 may be implemented via hardware, software, or a combination thereof. For example, CLI measurement manager 816 may be implemented as a processor, circuitry, and / or instructions 808 stored in memory 806 and executed by processor 804. In some examples, CLI measurement manager 816 may be integrated within processor 804 and / or transceiver 810. For example, CLI measurement manager 816 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 804 or transceiver 810.

[0139] From the perspective of a wireless device or UE, the CLI measurement manager 816 can be used in various aspects of this disclosure, for example, Figures 1 to 8 The CLI measurement manager 816 can be configured to, for example, perform: receiving an indication of a configuration for the SBFD serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell; receiving or obtaining a CLI measurement configuration indicating a set of resources for CLI measurements for the SBFD serving cell; processing CLI measurements obtained using at least a portion of the downlink resources according to the CLI measurement configuration; and sending a report at least in part based on the performed CLI measurements.

[0140] Network device 820 may include one or more processors 822. Processor 822 may execute instructions to perform various operations of network device 820 as described herein. Processor 822 may include one or more baseband processors, which may be implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0141] Network device 820 may include memory 824. Memory 824 may be a non-transitory computer-readable storage medium that stores instructions 826, which may include, for example, instructions executed by processor 822. Instructions 826 may also be referred to as program code or a computer program. Memory 824 may also store data used by processor 822 and results calculated by the processor.

[0142] Network device 820 may include one or more transceivers 828 (also collectively referred to as transceiver 828), which may include RF transmitter and / or receiver circuitry that uses the antenna 830 of network device 820 to facilitate to-and-for and / or signaling from network device 820 (e.g., signaling 838) in accordance with the corresponding RAT.

[0143] Network device 820 may include one or more antennas 830 (e.g., one, two, four or more). In embodiments having multiple antennas 830, network device 820 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described.

[0144] Network device 820 may include one or more interfaces 832. Interface 832 can be used to provide input to or output to network device 820. For example, RAN network device 820 (e.g., base station, radio head, etc.) may include interfaces 832 consisting of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 828 / antenna 830 already described), which enable network device 820 to communicate with other equipment in the network and / or enable network device 820 to communicate with external networks, computers, databases, etc., for the purpose of operating, managing, and maintaining network device 820 or other equipment operatively connected to it.

[0145] Network device 820 may include at least one CLI measurement manager 834. The CLI measurement manager 834 may be implemented via hardware, software, or a combination thereof. For example, the CLI measurement manager 834 may be implemented as a processor, circuitry, and / or instructions 826 stored in memory 824 and executed by processor 822. In some examples, the CLI measurement manager 834 may be integrated within processor 822 and / or transceiver 828. For example, the CLI measurement manager 834 may be implemented via a combination of software components (e.g., executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 822 or transceiver 828.

[0146] From a network device perspective, the CLI Measurement Manager 834 can be used in various aspects of this disclosure, for example... Figures 1 to 8 The CLI measurement manager 834 can be configured to, for example, perform: sending an indication of a configuration for the SBFD serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell; sending a CLI measurement configuration to the UE, the CLI measurement configuration indicating a set of resources for CLI measurements for the SBFD serving cell; and receiving a report from the UE, the report being at least in part based on CLI measurements performed by the UE using at least a portion of the downlink resources according to the CLI measurement configuration.

[0147] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor (or processor) as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein. Similarly, circuitry associated with a UE, network device, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein.

[0148] Unless otherwise explicitly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustrative and descriptive purposes, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form described. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from the practice of various embodiments.

[0149] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0150] The systems described herein relate to specific implementations but are provided as examples. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be understood that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0151] Although the foregoing has been described in considerable detail for clarity, it will be apparent that changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this description is not limited to the details given herein, but can be modified within the scope and equivalents of the appended claims.

Claims

1. A baseband processor, the baseband processor including a memory and configured to: Receive an instruction for the configuration of a Subband Full-Duplex (SBFD) serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell; Receive CLI measurement configuration indicating the resource set for cross-link interference (CLI) measurement of the SBFD serving cell; Process the CLI measurements obtained using at least a portion of the downlink resources according to the CLI measurement configuration; and Send reports that are at least partially based on the CLI measurements performed.

2. The baseband processor of claim 1, wherein the baseband processor configured to receive the CLI measurement configuration includes a baseband processor configured to perform the following operations: Receive Channel State Information (CSI) report configuration indicating the CLI measurement configuration.

3. The baseband processor of claim 2, wherein the CLI measurement configuration is associated with a CSI report configuration identifier of a CSI resource configuration, the CSI resource configuration identifying a CLI reference signal resource list.

4. The baseband processor of claim 1, wherein the CLI measurement configuration includes a CLI reference signal resource list, each CLI reference signal resource in the CLI reference signal resource list being associated with the same serving cell index and bandwidth portion identifier as each other CLI reference signal resource in the CLI reference signal resource list.

5. The baseband processor of claim 1, wherein the CLI measurement configuration includes a CLI reference signal resource list, and the probe reference signal (SRS) resources identified by the CLI reference signal resource list are within the uplink resources of the SBFD serving cell.

6. The baseband processor of claim 1, wherein the CLI measurement configuration includes a CLI reference signal resource list, and the received signal strength indicator resource is identified by the CLI reference signal resource list: Within a portion of the downlink bandwidth spanning at least a portion of both the one or more subcarriers used for the downlink resources and the one or more subcarriers used for the uplink resources; Within a portion of the one or more subcarriers used for the downlink resources; or Within a portion of the one or more subcarriers used for the uplink resources, and the probe reference signal resources are identified by the CLI reference signal resource list.

7. The baseband processor according to claim 1, wherein the baseband processor is further configured to: For the CSI resource configuration identifier associated with the CLI measurement configuration, a resource type is determined from among a variety of resource types for resources in the CLI reference signal resource list, wherein the CLI measurement is processed according to the resource type, and the resource type includes one of aperiodic resources, semi-persistent resources, or periodic resources.

8. The baseband processor of claim 7, wherein the CLI reference signal resource list includes Received Signal Strength Indicator (RSSI) resources for the CLI measurement, and the RSSI resource configuration for the CLI indicates a slot offset for the aperiodic resources or a period and offset for the semi-persistent resources.

9. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The system receives an instruction to activate a Media Access Control (MAC) control element for the resource set used in the CLI measurement, the MAC control element identifying the SBFD serving cell and an identifier of a semi-persistent resource indicating a CLI reference signal resource list.

10. The baseband processor of claim 1, wherein semi-persistent resources are used for the CLI measurement, and the baseband processor is further configured to: The system receives an instruction to activate the Media Access Control (MAC) control element for the resource set used for the CLI measurement; Send an acknowledgment of the received MAC control element in the time slot; and Candidate time slots for the CLI measurement are determined at least in part based on the number of SBFD time slots following the time slot in which the confirmation is sent.

11. The baseband processor of claim 1, wherein periodic resources are used for the CLI measurement, and the baseband processor is further configured to: Receive downlink control information (DCI) messages for scheduling at least a portion of the downlink resources used for the CLI measurement; Candidate time slots for the CLI measurements are determined at least in part based on time slot offset values, wherein the CLI measurements are obtained from measurements in SBFD time slots following the candidate time slots, based at least in part on the fact that the candidate time slots are non-SBFD time slots.

12. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The CLI report field configuration identifies the Layer 1 or Layer 2 resource to be used to send the report, which is sent using the Layer 1 or Layer 2 resource.

13. The baseband processor according to claim 12, wherein the baseband processor is further configured to: Send capability signaling, the capability signaling identifying UE capabilities configured using one or more of the Received Signal Strength Indicator (RSSI) resource or the Sounding Reference Signal (SRS) resource used for the CLI measurement.

14. The baseband processor according to claim 1, wherein the baseband processor is further configured to: Send capability signaling, which identifies one or both of the following: the maximum number of values ​​that the UE can receive for Signal Strength Indicator (RSSI) CLI measurement reports or the maximum number of values ​​that the UE can receive for Probe Reference Signal (SRS) CLI measurement reports.

15. The baseband processor according to claim 1, wherein the baseband processor is further configured to: The capability signaling identifies the UE capability to be sent in a single report based at least in part on both the processed CLI measurements and Channel State Information (CSI) measurements.

16. The baseband processor of claim 15, further configured to: Obtain CSI measurements; and Determine the relative priority between the CLI measurements processed in the report and the obtained CSI measurements, wherein the report is sent according to the relative priority.

17. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive an instruction for the configuration of a Subband Full-Duplex (SBFD) serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell; Receive CLI measurement configuration indicating the resource set for cross-link interference (CLI) measurement of the SBFD serving cell; According to the CLI measurement configuration, at least a portion of the downlink resources are used to process the CLI measurement; and Reports are sent based at least in part on the CLI measurements processed.

18. The method according to claim 17, further comprising: Receive Channel State Information (CSI) report configuration indicating the CLI measurement configuration.

19. The method of claim 17, further comprising: Send capability signaling identifying one or more of the following: UE capabilities configured using one or more of the Received Signal Strength Indicator (RSSI) resource or the Sounding Reference Signal (SRS) resource used for the CLI measurement; The maximum number of values ​​that the UE can report for RSSI CLI measurement; The maximum number of values ​​that the UE can report for SRS CLI measurements; or The UE's ability to send a single report based at least in part on both the processed CLI measurements and Channel State Information (CSI) measurements.

20. A method for wireless communication at a network device, the method comprising: Send an indication of the configuration for a Subband Full-Duplex (SBFD) serving cell, the configuration identifying one or more subcarriers for downlink resources of the SBFD serving cell, the one or more subcarriers being frequency-domain multiplexed with one or more subcarriers for uplink resources of the SBFD serving cell; Send a CLI measurement configuration to the user equipment (UE) indicating the set of resources for cross-link interference (CLI) measurement for the SBFD serving cell; as well as The UE receives a report, which is at least in part based on CLI measurements performed by the UE using at least a portion of the downlink resources in accordance with the CLI measurement configuration.