Cross-link interference reporting for multiple types of transmit time intervals

Abstract

Methods, systems, and devices for wireless communication are described. A network entity may receive control information indicating parameter information for reporting cross-link interference (CLI). The parameter information may include first parameter information associated with a transmission time interval (TTI) of a first type in the control information, or the parameter information may include second parameter information associated with a TTI of a second type in the control information. The network entity may receive one or more CLI reference signals during one or more TTIs of the first type of TTI or the second type of TTI. The network entity may send a report including information indicating the CLI. The information indicating the CLI may be associated with one or more CLI reference signals.

Description

Cross-referencing

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 332,482, filed June 9, 2023, entitled “CROSS-LINK INTERFERENCE REPORTING FOR MULTIPLE TYPES OF TRANSMISSION TIME INTERVALS”, which has been assigned to the assignee of this application. Technical Field

[0002] The following discussion pertains to wireless communications, including reports of cross-link interference (CLI) for various types of transmission time intervals (TTIs). Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more network entities, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting cross-link interference (CLI) reporting for multiple types of Transmission Time Intervals (TTIs). For example, the described technology provides a framework for configuring a first network entity using parameters for measuring or reporting CLIs associated with one or more types of TTIs. In some examples, the first network entity may receive control information indicating parameter information for reporting CLIs. The parameter information may include first parameter information associated with a first type of TTI in the control information. For example, based on receiving the control information, the first network entity may receive one or more CLI reference signals during one or more TTIs of the first type of TTI. In some examples, the first network entity may send a report including information indicating CLIs. In such examples, the information indicating CLIs may be associated with one or more CLI reference signals.

[0005] A method for wireless communication performed by a first network entity is described. The method may include: receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of Time Interval (TTI) in the control information; receiving one or more CLI reference signals during one or more TTIs of the first type of TTI; and transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0006] A first network entity for wireless communication is described. The first network entity may include at least one communication interface and at least one processor coupled to the at least one communication interface. The first network entity may be configured to: receive control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI and wherein the first parameter information is associated with a first type of Time Interval (TTI) in the control information; receive one or more CLI reference signals during one or more TTIs of the first type of TTI; and transmit a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0007] Another first network entity for wireless communication is described. The first network entity may include: components for receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; components for receiving one or more CLI reference signals during one or more TTIs of the first type of TTI; and components for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0008] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network entity, the code enables the first network entity to: receive control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; receive one or more CLI reference signals during one or more TTIs of the first type of TTI; and transmit a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0009] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the parameter information includes second parameter information for reporting CLI, which may be associated with a second type of TTI in the control information, and the second type of TTI may be different from the first type of TTI.

[0010] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0011] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI reference signals may be received during at least one CLI reference signal of the first set of CLI resources.

[0012] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information indicating the CLI may be associated only with the first type of TTI.

[0013] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second or more CLI reference signals during one or more TTIs of the second type of TTI; and sending a second report including second information indicating the CLI, wherein the second information indicating the CLI may be associated only with the second or more CLI reference signals.

[0014] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information indicating the CLI may be associated with both the first type of TTI and the second type of TTI.

[0015] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing the averaging of CLI measurements across different TTI types, wherein the information indicating the CLI is based on the suppression to include first information associated with the first type of TTI and second information associated with the second type of TTI.

[0016] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first information includes a first CLI measurement that can be indicated as associated with the first type of TTI, and the second information includes a second CLI measurement that can be indicated as associated with the second type of TTI.

[0017] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first CLI measurement includes a first value of the CLI metric, and a second CLI measurement includes a second value of the CLI metric, and the first value may be associated with a first type of TTI, and the second value may be associated with a second type of TTI.

[0018] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first type of TTI includes a subband full-duplex (SBFD) TTI type, a non-SBFD TTI type, an unaligned dynamic time-division duplex (TDD) TTI type, an aligned dynamic time-division duplex (TDD) TTI type, or a non-SBFD unaligned dynamic TDD TTI type.

[0019] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for generating information indicative of the CLI based on one or more CLI reference signals.

[0020] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information via a CLI report configuration message or a CSI report configuration message.

[0021] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates the minimum number of TTIs between the report TTI and the reference TTI in which the report may be sent, and this minimum number of TTIs includes any type of TTI.

[0022] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates a minimum number of TTIs between the report TTI and the reference TTI in which the report may be sent, and the minimum number of TTIs includes only the TTIs of the first type.

[0023] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first type of TTI includes a type of time slot or a type of symbol.

[0024] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first network entity includes a user equipment (UE), the one or more CLI reference signals include UE-to-UE CLI reference signals, and the information indicating the CLI includes information indicating the UE-to-UE CLI.

[0025] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first parameter information can be used to report CLIs that can be associated with a half-duplex operating mode at the first network entity.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the first parameter information may be used to report a CLI that can be associated with a full-duplex operating mode at the second network entity.

[0027] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the first parameter information may be used to report a CLI that can be associated with the SBFD operating mode at the second network entity.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the first parameter information may be used to report a CLI that can be associated with a half-duplex operating mode in an unaligned TTI format at the second network entity.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the parameter information includes information indicating at least one parameter used to measure or report CLI.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the at least one parameter includes the type of CLI metric to be reported, one or more resources used to measure the CLI, or one or more resources used to report the CLI.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, this type of CLI metric includes the Reference Signal Received Power (RSRP) metric type or the Received Signal Strength Indicator (RSSI) metric type.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information includes an indication of the TTI for which the first parameter information is applicable to the first type of TTI.

[0033] A method for wireless communication performed by a first network entity is described. The method may include: receiving control information indicating resource allocation information for measuring CLI; receiving one or more CLI reference signals via one or more CLI resources according to the resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of discontinuous subbands allocated for downlink communication; and transmitting a report including information indicating the CLI, wherein the information indicating the CLI is associated with the one or more CLI reference signals.

[0034] A first network entity for wireless communication is described. The first network entity may include at least one communication interface and at least one processor coupled to the at least one communication interface. The first network entity may be configured to: receive control information indicating resource allocation information for measuring CLI; receive one or more CLI reference signals via one or more CLI resources according to the resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of discontinuous subbands allocated for downlink communication; and transmit a report including information indicating the CLI, wherein the information indicating the CLI is associated with the one or more CLI reference signals.

[0035] Another first network entity for wireless communication is described. The first network entity may include: components for receiving control information indicating resource allocation information for measuring CLI; components for receiving one or more CLI reference signals via one or more CLI resources according to the resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of discontinuous subbands allocated for downlink communication; and components for transmitting a report including information indicating the CLI, wherein the information indicating the CLI is associated with the one or more CLI reference signals.

[0036] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network entity, the code enables the first network entity to: receive control information indicating resource allocation information for measuring CLI; receive one or more CLI reference signals via one or more CLI resources according to the resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of discontinuous subbands allocated for downlink communication; and transmit a report including information indicating the CLI, wherein the information indicating the CLI is associated with the one or more CLI reference signals.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be located within one subband of the set of noncontiguous subbands allocated for downlink communication.

[0038] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include two CLI resources, and each of the two CLI resources may be located within a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0039] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be located in at least two subbands of the set of noncontiguous subbands allocated for downlink communication.

[0040] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information includes a bitmap indicating the distribution of the CLI resource across the set of noncontiguous subbands.

[0041] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates a set of multiple resource block sets including the CLI resource, and each of the multiple resource block sets may be associated with a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0042] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be within the set of non-contiguous subbands allocated for downlink communication, and the methods, network entities, and nontransitory computer-readable media may include additional operations, features, components, or instructions for measuring CLI within a portion of the CLI resources, wherein the portion may be based on semi-static configuration information for SBFD operations, wherein the semi-static configuration information may be available for one or more subbands in the set of non-contiguous subbands allocated for uplink communication and allocated for downlink communication, or the semi-static configuration information may be available for the subband allocated for uplink communication and one or more guard bands, wherein the information may indicate the measured CLI.

[0043] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving second control information that indicates the frequency position of the subband allocated for uplink communication or the corresponding frequency position of the one or more guard bands.

[0044] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates two CLI resource sets including the one or more CLI resources, and each of the two CLI resource sets may be associated with a corresponding subband in the set of non-contiguous subbands allocated for downlink communication.

[0045] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates a set of CLI resources that includes the one or more CLI resources, and the set of CLI resources may be associated with the set of non-contiguous subbands allocated for downlink communication.

[0046] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information includes a bitmap indicating the one or more CLI resources.

[0047] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates one or more resource block sets within the CLI resource set, the one or more resource block sets including the one or more CLI resources, and each resource block set may be associated with a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0048] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for measuring CLIs within one or more resource block sets within the CLI resource set, wherein the one or more resource block sets include the one or more CLI resources, wherein the one or more resource block sets may be based on semi-static configuration information for SBFD operations, wherein the semi-static configuration information may be used for one or more subbands in the set of non-contiguous subbands allocated for uplink communication and allocated for downlink communication, or the semi-static configuration information may be used for the subband and one or more guard bands allocated for uplink communication, and wherein the information may indicate the CLI being measured.

[0049] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the set of discontinuous subbands allocated for downlink communication may be within the TTI of SBFD operations allocated for a second network entity.

[0050] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first network entity includes a UE, and the second network entity includes a base station.

[0051] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI reference signals include UE-to-UE CLI reference signals, and the resource allocation information can be used to measure UE-to-UE CLI.

[0052] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information can be used to measure CLIs that can be associated with a half-duplex operating mode at the first network entity.

[0053] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the resource allocation information can be used to measure CLIs that can be associated with a full-duplex operating mode at the second network entity.

[0054] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the resource allocation information can be used to measure a CLI that can be associated with an SBFD operating mode at the second network entity.

[0055] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, receiving the control information may include operations, features, components, or instructions for receiving the control information from a second network entity, wherein the resource allocation information can be used to measure a CLI that can be associated with a half-duplex operating mode in an unaligned TTI format at the second network entity.

[0056] A method for wireless communication performed by a first network entity is described. The method may include: outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; and obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0057] A first network entity for wireless communication is described. The first network entity may include at least one communication interface and at least one processor coupled to the at least one communication interface. The first network entity may be configured to: output control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; and obtain a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0058] Another first network entity for wireless communication is described. The first network entity may include: components for outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; and components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0059] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network entity, the code enables the first network entity to: output control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; and obtain a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0060] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the parameter information includes second parameter information for reporting CLI, which may be associated with a second type of TTI in the control information, and the second type of TTI may be different from the first type of TTI.

[0061] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0062] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first set of CLI resources includes one or more CLI resources.

[0063] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information indicating the CLI may be associated only with the first type of TTI.

[0064] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining a second report including second information indicating a CLI, wherein the second information indicating the CLI may be associated only with a second or more CLI resources that may be within one or more TTIs of the second type of TTI.

[0065] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information indicating the CLI may be associated with both the first type of TTI and the second type of TTI.

[0066] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information indicating the CLI includes first information associated with the first type of TTI and second information associated with the second type of TTI.

[0067] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first information includes a first CLI measurement that can be indicated as associated with the first type of TTI, and the second information includes a second CLI measurement that can be indicated as associated with the second type of TTI.

[0068] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first CLI measurement includes a first value of the CLI metric, and a second CLI measurement includes a second value of the CLI metric, and the first value may be associated with a first type of TTI, and the second value may be associated with a second type of TTI.

[0069] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first type of TTI includes SBFD TTI type, non-SBFD TTI type, unaligned dynamic TDD TTI type, aligned dynamic TDD TTI type, or non-SBFD unaligned dynamic TDD TTI type.

[0070] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first type of TTI includes a type of time slot or a type of symbol.

[0071] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting the control information may include operations, features, components, or instructions for outputting the control information via CLI report configuration messages or CSI report configuration messages.

[0072] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates the minimum number of TTIs between the report TTI and the reference TTI in which the report may be sent, and this minimum number of TTIs includes any type of TTI.

[0073] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates a minimum number of TTIs between the report TTI and the reference TTI in which the report may be sent, and the minimum number of TTIs includes only the TTIs of the first type.

[0074] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first type of TTI includes a type of time slot or a type of symbol.

[0075] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the information indicating the CLI includes information indicating the UE to the UE CLI.

[0076] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting the control information may include operations, features, components, or instructions for outputting the control information to a second network entity, wherein the first parameter information may be used to report a CLI that can be associated with a half-duplex operating mode at the second network entity.

[0077] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first parameter information can be used to report CLIs that can be associated with the full-duplex operating mode at the first network entity.

[0078] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first parameter information can be used to report CLIs that can be associated with the SBFD operating mode at the first network entity.

[0079] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first parameter information can be used to report CLIs that can be associated with a half-duplex operation mode in an unaligned TTI format at the first network entity.

[0080] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting the control information may include operations, features, components, or instructions for outputting the control information to a second network entity, wherein the first parameter information may indicate at least one parameter for measuring or reporting CLI.

[0081] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the at least one parameter includes the type of CLI metric to be reported, one or more resources used to measure the CLI, or one or more resources used to report the CLI.

[0082] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, this type of CLI metric includes the RSRP metric type or the RSSI metric type.

[0083] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information includes an indication of the TTI for which the first parameter information is applicable to the first type of TTI.

[0084] A method for wireless communication performed by a first network entity is described. The method may include: outputting control information indicating resource allocation information for measuring CLI; and obtaining a report including information indicating the CLI, wherein the information indicating the CLI is associated with one or more CLI resources according to the resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0085] A first network entity for wireless communication is described. The first network entity may include at least one communication interface and at least one processor coupled to the at least one communication interface. The first network entity may be configured to: output control information indicating resource allocation information for measuring CLI; and obtain a report including information indicating the CLI, wherein the information indicating the CLI is associated with one or more CLI resources according to the resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0086] Another first network entity for wireless communication is described. The first network entity may include: components for outputting control information indicating resource allocation information for measuring CLI; and components for obtaining a report including information indicating the CLI, wherein the information indicating the CLI is associated with one or more CLI resources according to the resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0087] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a first network entity, the code enables the first network entity to: output control information indicating resource allocation information for measuring CLI, and obtain a report including information indicating the CLI, wherein the information indicating the CLI is associated with one or more CLI resources according to the resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0088] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be located within one subband of the set of noncontiguous subbands allocated for downlink communication.

[0089] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include two CLI resources, and each of the two CLI resources may be located within a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0090] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be located in at least two subbands of the set of noncontiguous subbands allocated for downlink communication.

[0091] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information includes a bitmap indicating the distribution of the CLI resource across the set of noncontiguous subbands.

[0092] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates a set of multiple resource block sets including the CLI resource, and each of the multiple resource block sets may be associated with a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0093] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the one or more CLI resources include CLI resources that may be allocated within the set of discontinuous subbands for downlink communication, the information indicating CLIs that may be measured within a portion of semi-static configuration information for SBFD operation, and the semi-static configuration information may be available for one or more subbands in the set of discontinuous subbands allocated for uplink communication and the set of discontinuous subbands allocated for downlink communication, or the semi-static configuration information may be available for the subband allocated for uplink communication and one or more guard bands.

[0094] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a second control information is output that indicates the frequency position of the subband or the corresponding frequency position of the one or more guard bands allocated for uplink communication.

[0095] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates two CLI resource sets including the one or more CLI resources, and each of the two CLI resource sets may be associated with a corresponding subband in the set of non-contiguous subbands allocated for downlink communication.

[0096] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates a set of CLI resources that includes the one or more CLI resources, and the set of CLI resources may be associated with the set of non-contiguous subbands allocated for downlink communication.

[0097] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information includes a bitmap indicating the one or more CLI resources.

[0098] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information indicates one or more resource block sets within the CLI resource set, the one or more resource block sets including the one or more CLI resources, and each resource block set may be associated with a corresponding subband in the set of noncontiguous subbands allocated for downlink communication.

[0099] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the information may indicate a CLI measured within one or more resource block sets within the CLI resource set, the one or more resource block sets comprising the one or more CLI resources, the one or more resource block sets being based on semi-static configuration information for SBFD operation, and the semi-static configuration information being available for one or more subbands in the set of non-contiguous subbands allocated for uplink communication and allocated for downlink communication, or the semi-static configuration information being available for the subband allocated for uplink communication and one or more guard bands.

[0100] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the set of discontinuous subbands allocated for downlink communication may be within the TTI of the SBFD operation allocated for the first network entity.

[0101] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the first network entity includes a base station.

[0102] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting the control information may include operations, features, components, or instructions for outputting the control information to a second network entity including the UE, wherein the resource allocation information may be used to measure UE to UE CLI.

[0103] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, outputting the control information may include operations, features, components, or instructions for outputting the control information to a second network entity, wherein the resource allocation information can be used to measure CLIs that can be associated with a half-duplex operating mode at the second network entity.

[0104] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information can be used to measure CLIs that can be associated with the full-duplex operation mode at the first network entity.

[0105] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information can be used to measure the CLI that can be associated with the SBFD operating mode at the first network entity.

[0106] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the resource allocation information can be used to measure CLIs that can be associated with a half-duplex operation mode in an unaligned TTI format at the first network entity. Attached Figure Description

[0107] Figure 1 and Figure 2 Examples of wireless communication systems supporting cross-link interference (CLI) reporting for various types of transmission time intervals (TTIs) are shown, each according to one or more aspects of this disclosure.

[0108] Figure 3 Examples of interference measurement graphs supporting CLI reports for various types of TTIs are shown, according to one or more aspects of this disclosure.

[0109] Figure 4 Examples of wireless communication systems supporting CLI reporting for various types of TTIs are shown, according to one or more aspects of this disclosure.

[0110] Figure 5 and Figure 6 Examples of process flows supporting CLI reporting for various types of TTIs are shown, each according to one or more aspects of this disclosure.

[0111] Figure 7 and Figure 8 A block diagram of a device supporting CLI reporting for various types of TTIs is shown, according to one or more aspects of this disclosure.

[0112] Figure 9 A block diagram is shown of a communication manager that supports CLI reporting for various types of TTIs, according to one or more aspects of this disclosure.

[0113] Figure 10 A diagram of a system including a device supporting CLI reporting for various types of TTIs, according to one or more aspects of this disclosure, is shown.

[0114] Figure 11 and Figure 12 A block diagram of a device supporting CLI reporting for various types of TTIs is shown, according to one or more aspects of this disclosure.

[0115] Figure 13 A block diagram is shown of a communication manager that supports CLI reporting for various types of TTIs, according to one or more aspects of this disclosure.

[0116] Figure 14 A diagram of a system including a device supporting CLI reporting for various types of TTIs, according to one or more aspects of this disclosure, is shown.

[0117] Figures 15 to 18 A flowchart illustrating a method for supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Detailed Implementation

[0118] Some wireless communication systems may include communication devices, such as user equipment (UEs) or network entities, that support wireless communication in half-duplex or full-duplex modes or combinations thereof. For example, in half-duplex mode, a communication device may transmit or receive communication during a time interval (such as a transmit time interval (TTI)) that may span one or more time resources (e.g., symbols, micro-slots, time slots). In full-duplex mode, a communication device may transmit and receive communication simultaneously or concurrently. For example, communication received by a communication device may overlap in the time domain with communication transmitted by the communication device. In other words, a TTI occupied or allocated for receiving signals may overlap with a TTI occupied or allocated for transmitting signals. In some examples, adjacent communication devices (e.g., network entities) may concurrently perform full-duplex or half-duplex time-division duplex (TDD) communication, such that downlink communication received by a first communication device may at least partially overlap in time with uplink communication transmitted from a second communication device (e.g., an adjacent communication device).

[0119] For example, adjacent network entities may concurrently perform dynamic TDD, whereby the format of TTI (e.g., time slots or symbols) may be misaligned across cells served by adjacent network entities. Consequently, a first communication device may receive downlink signals from a first network entity (e.g., via a cell served by the first network entity), while a second communication device may simultaneously transmit uplink signals to an adjacent second entity (e.g., via another cell served by the second network entity). In some other examples, the first network entity may perform full-duplex operation, such as subband full-duplex (SBFD) operation, in which the first network entity may transmit and receive simultaneously on a subband basis. For example, during a TTI, a first communication device may receive downlink signals from a first network entity using a subband allocated for downlink, while a second communication device may simultaneously transmit uplink signals to the first network entity using a subband allocated for uplink. Therefore, dynamic TDD operation or full-duplex operation, or both, may cause uplink communication transmitted from the second communication device to interfere with downlink communication received at the first communication device. This interference may be referred to as cross-link interference (CLI). In some examples, CLI may degrade wireless communication at the first communication device. To mitigate or reduce the impact of CLI, the first network entity may configure the first communication device to measure and report CLI. For example, the first network entity may configure the first communication device to perform CLI measurements on reference signals transmitted from a second communication device. However, in some cases, the degree of CLI experienced at the first communication device due to full-duplex operation may differ from the degree of CLI experienced at the first communication device due to dynamic TDD operation. In other words, the degree of CLI experienced at the first communication device during a TTI used for or allocated for dynamic TDD operation may differ from the degree of CLI experienced at the first communication device during a TTI used for or allocated for full-duplex operation.

[0120] Various aspects of this disclosure generally relate to techniques for CLI reporting for multiple types of TTIs, and more specifically, to a framework for configuring a communication device using CLI reporting parameters associated with one or more types of TTIs. For example, according to such techniques, a first network entity may configure a first communication device using parameters for reporting CLIs experienced at the first communication device during one or more types of TTIs. For example, the first network entity may configure the first communication device using parameters for reporting CLIs experienced at the first communication device during a TTI used for or allocated for dynamic TDD operation, or during a TTI used for or allocated for full-duplex operation, or both. In some examples, the first communication device may receive control information indicating first parameter information for reporting CLIs associated with a first type of TTI. In such an example, the first communication device may measure the CLI during a resource period occurring during the first type of TTI. For example, the first communication device may receive one or more CLI reference signals from a second communication device during one or more TTIs of the first type of TTI. In such an example, the first communication device may measure and report the CLI based on one or more CLI reference signals. For example, the first communication device may send a report including information indicating CLI associated with one or more CLI reference signals.

[0121] In some examples, such as during a TTI used for or allocated for SBFD operation, multiple non-contiguous subbands may be configured for downlink communication. In such examples, a first network may configure a first communication device using one or more sets of resources within the TTI that can be allocated for measuring CLI. For example, the first communication device may receive control information indicating resource allocation information for measuring CLI. In this example, the first communication device may receive one or more CLI signals from a second communication device via one or more CLI resources based on the resource allocation information. For example, one or more CLI resources may be within one or more subbands of multiple non-contiguous subbands configured for (e.g., allocated for) downlink communication. In this example, the first communication device may measure and report CLI based on one or more CLI reference signals. For example, the first communication device may send a report including information indicating CLI associated with one or more CLI reference signals.

[0122] Specific aspects of the subject matter described herein can be implemented to achieve one or more of the following potential benefits. For example, the technology employed by the described communication device can provide benefits and enhancements to the operation of the communication device, including enabling CLI reporting for multiple types of TTIs. In some examples, performing operations to enable reporting for multiple types of TTIs at one or more communication devices within the communication device can improve communication reliability and reduce latency within the wireless communication system, among other benefits.

[0123] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also described in the context of interference measurement diagrams and process flows. Furthermore, the aspects of this disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to CLI reporting for various types of TTI.

[0124] Figure 1 Examples of wireless communication systems 100 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure are shown. Wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0125] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0126] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0127] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of: a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As yet another example, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, or a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0128] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a first network node being configured to provide, transmit, output, communicate, or send information to a second network node. Similarly, in this example and consistent with this disclosure, disclosure regarding a first network node being configured to send information to a second network node includes disclosure regarding a second network node being configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0129] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0130] One or more of the network entities 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0131] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0132] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layer functions, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by CU 160. Alternatively or additionally, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0133] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0134] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support CLI reporting for various types of TTIs as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0135] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0136] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0137] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE can be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0138] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0139] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0140] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0141] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0142] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0143] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a TTI. In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0144] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0145] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0146] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0147] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0148] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0149] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0150] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0151] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0152] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0153] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0154] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0155] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0156] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0157] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0158] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0159] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0160] Various devices within the wireless communication system 100 may support one or more levels of full-duplex operation, depending on the deployment scenario, duplex mode (such as TDD only, FDD only, or both TDD and FDD), or interference management process or its association. In some aspects, wireless devices (UE 115, network entity 105, or IAB node 104) within the wireless communication system 100 may support half-duplex or full-duplex operation. For example, network entity 105 may support various types of MIMO communication, including: downlink multi-user MIMO (MU-MIMO), under which network entity 105 can simultaneously send downlink signaling to two different UEs 115; uplink MU-MIMO, under which network entity 105 can simultaneously receive uplink signaling from two different UEs 115; or downlink and uplink MU-MIMO (which may be referred to herein as full-duplex operation), under which network entity 105 can send downlink signaling to a first UE 115 while simultaneously receiving uplink signaling from a second UE 115. Network entity 105 may further support enhanced MIMO (eMIMO) or further enhanced MIMO (FeMIMO), which may be associated with an FeMIMO beam management session. Under full-duplex operation, the wireless device may be able to transmit and receive simultaneously. In other words, the wireless device may support simultaneous uplink and downlink transmissions (e.g., uplink and downlink transmissions that at least partially overlap in time). In some examples, simultaneous uplink and downlink transmissions at a wireless device may result in one or more types of interference at the wireless device, at adjacent wireless devices, or both. For example, simultaneous uplink and downlink transmissions at a wireless device may result in self-interference, CLI, interference caused by clutter (e.g., interference from objects such as buildings that reflect signaling), or any combination thereof.

[0161] In some respects, network entity 105 and UE 115 may support a variety of evaluation techniques and performance metrics associated with different deployment scenarios for full-duplex operation, such as for NR full-duplex. Furthermore, network entity 105 and UE 115 may support one or more techniques to support coexistence with other systems in any co-channel or adjacent channel for subband non-overlapping full-duplex operation, or for dynamic or flexible TDD, or for both. For example, network entity 105 and UE 115 may support techniques associated with the evolution of full-duplex operation for NR TDD across various spectrums, including unpaired spectrum. In such examples, network entity 105 may support full-duplex operation, UE 115 may support half-duplex operation, and network entity 105 and UE 115 may configure which frequency ranges are available or desire some relatively reduced constraints (reduced constraints or no constraints).

[0162] Such techniques may include various full-duplex types or schemes and corresponding metrics for evaluating the performance of such full-duplex types or schemes, inter-network entity (e.g., gNB-to-gNB) and inter-UE CLI mitigation techniques, intra-subband CLI and inter-subband CLI mitigation techniques (such as in specific implementations of non-overlapping subband full-duplex), or metric-based evaluation procedures for the impact of full-duplex operation on half-duplex operation (assuming coexistence in co-channel and adjacent channels). Alternatively or additionally, such techniques may include metric-based evaluation procedures for considering the impact on RF constraints when adjacent channels coexist, or for considering the impact on RF constraints when considering self-interference, inter-subband CLI and inter-carrier CLI at network entity 105, and inter-subband CLI and inter-carrier CLI at UE 115. Furthermore, such techniques may include antennas or RF and algorithmic designs for interference mitigation, including antenna isolation, transmit interference management suppression in the receiver portion, filtering, and digital interference suppression. Moreover, such techniques may comply with one or more management or network specifications associated with full-duplex operation in TDD unpaired spectrum.

[0163] In addition, some systems may support one or more technologies associated with dynamic or flexible TDD or subband full-duplex (SBFD) or both for UE-to-UE CLI processing (e.g., UE-to-UE CLI processing) or gNB-to-gNB CLI processing (gNB-to-gNB CLI processing), or both. Such technologies may include mechanisms related to UE-to-UE CLI measurement and reporting, coordinated scheduling, spatial domain design, receiver design, UE and network entity transmit and receive timing, power control-based design, or sensing-based mechanisms, as well as other example technologies associated with UE-to-UE CLI processing or gNB-to-gNB CLI processing. In some aspects, such technologies may be associated with whether the scheme or design includes over-the-air (OTA) or backhaul information exchange.

[0164] Various devices within the wireless communication system 100 can support inter-device CLI measurements. For example, one or more UEs 115 and network entity 105 can support techniques for measuring CLI experienced at UE 115 due to uplink transmissions from another UE 115. As described herein, a measurement of CLI experienced at UE 115 due to signaling from another UE 115 can be referred to as a UE-to-UE CLI measurement. Additionally, as described herein, a reference signal transmitted from UE 115 for CLI measurements (e.g., UE-to-UE CLI measurements) at another UE 115 can be referred to as a UE-to-UE CLI reference signal. In some cases, UE 115 may experience UE-to-UE CLI due to dynamic TDD operation or full-duplex operation (or both) at network entity 105 serving UE 115. In such cases, the degree of CLI experienced at UE 115 due to full-duplex operation may differ from the degree of CLI experienced at UE 115 due to dynamic TDD operation. In other words, the CLI level experienced by UE 115 during a TTI used at network entity 105 or allocated by that network entity for dynamic TDD operation may differ from the CLI level experienced by UE 115 during a TTI used at network entity 105 or allocated by that network entity for full-duplex operation. However, network entity 105 may lack a mechanism, let alone an effective one, for configuring UE 115 using multiple (e.g., different) parameters for measuring or reporting UE-to-UE CLI experienced by UE 115 during multiple (e.g., different) types of TTIs.

[0165] In some examples, UE 115 and network entity 105 may be configured to support one or more techniques for CLI reporting for multiple types of TTIs. For example, network entity 105 may support a framework for configuring UE 115 using CLI reporting parameters associated with one or more types of TTIs. In some examples, UE 115 may receive control information indicating first parameter information for reporting CLIs associated with a first type of TTI (e.g., a TTI assigned for dynamic TDD operation, a TTI configured for full-duplex operation). In this example, UE 115 may receive one or more CLI reference signals from another UE 115 during one or more TTIs of the first type of TTI. Therefore, UE 115 may send a report including information indicating CLIs associated with one or more CLI reference signals. In some examples, configuring UE 115 using CLI reporting parameters associated with the first type of TTI may improve communication reliability and reduce latency within the wireless communication system 100, among other potential benefits.

[0166] In some examples, during a TTI used for or allocated for full-duplex operation (e.g., SBFD operation), multiple non-contiguous subbands can be configured for downlink communication. In such examples, UE 115 can receive control information indicating resource allocation information for measuring CLI. Therefore, UE 115 can receive one or more CLI signals from another UE 115 via one or more CLI resources indicated by the resource allocation information. In some examples, one or more CLI resources can be located within one or more of the multiple non-contiguous subbands configured for downlink communication. Thus, UE 115 can measure and report CLI based on one or more CLI reference signals. For example, UE 115 can send a report including information indicating CLI associated with one or more CLI reference signals. In some examples, configuring UE 115 using CLI resources for measuring CLIs associated with non-contiguous subbands can improve communication reliability and reduce latency within the wireless communication system 100, among other potential benefits.

[0167] Figure 2 An example of a wireless communication system 200 supporting CLI reporting for multiple types of TTIs according to one or more aspects of this disclosure is shown. The wireless communication system 200 may be implemented or can be implemented to achieve or facilitate aspects of the wireless communication system 100. For example, the wireless communication system 200 may include UE 215-a and UE 215-b, as well as network entity 205-a and network entity 205-b. UE 215-a and UE 215-b may each be connected via… Figure 1 An example of UE 115 is illustrated and referenced in the diagram. Network entity 205-a and network entity 205-b can each be accessed via... Figure 1 An example of network entity 105 described in the diagram is shown and referenced. Figure 2 In the example, network entity 205-a may be associated with cell 210-a (e.g., serving that cell), and network entity 205-b may be associated with cell 210-b (e.g., serving that cell).

[0168] In some examples of the wireless communication system 200, network entity 205 may operate in a dynamic TDD mode, also known as a flexible TDD mode. Operating in dynamic TDD mode allows network entity 205 to flexibly adjust uplink and downlink resources, for example, based on traffic load (e.g., transient traffic load) within the wireless communication system 200. In some examples, dynamic TDD mode may include half-duplex operation (e.g., at network entity 205) with unaligned TTI formats (e.g., unaligned slot formats, unaligned symbol formats). Operating in dynamic TDD mode enables increased flexibility in asymmetric services, which can improve spectral efficiency within the wireless communication system 200, among other potential benefits.

[0169] However, in some examples, dynamic TDD operations at network entity 205 may cause interference between downlink and uplink communications within the wireless communication system 200. For example, dynamic TDD operations at network entity 205 may enable network entity 205-a to transmit downlink communications and enable network entity 205-b to concurrently (or temporally overlap) receive uplink communications, which may result in inter-NB CLI 220 at network entity 205-b. Therefore, UE 215-a may receive downlink communications from network entity 205-a, and UE 215-b may concurrently (or temporally overlap) transmit uplink communications to network entity 205-b, which may result in inter-UE CLI 225 experienced at UE 215-a. In other words, in some deployment scenarios, such as when UE 215-a and UE 215-b are relatively close to each other (e.g., but served by different cells), uplink signaling sent from UE 215-b (e.g., to network entity 205-b) may cause inter-UE CLI 225 (e.g., inter-cell UE interference) at UE 215-a. In some respects, the UE experiencing CLI (e.g., the UE receiving downlink signals, such as UE 215-a) may be referred to as the victim UE, and the UE causing CLI (e.g., the UE sending uplink signals, such as UE 215-b) may be referred to as the attacker UE.

[0170] In some specific implementations, one or more of network entities 205 and one or more of UEs 215 may support technologies associated with UE-to-UE CLI mitigation for deployments involving dynamic TDD scenarios, such as those that can be used for... Figure 2The examples illustrate this. For instance, one or both of network entities 205 and one or both of UE 215 may support UE-to-UE CLI reporting. In some examples, to support CLI reporting, one or both of UE 215 may support UE-to-UE CLI measurements. In some examples, to reduce inter-cell CLI and improve decoding of downlink signals at UE 215-a, network entity 205-a may configure UE 215-a to perform one or more CLI measurements (e.g., RSRP or RSSI measurements) on reference signals transmitted from UE 215-b.

[0171] Figure 3 An example of an interference measurement diagram 300 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. The interference measurement diagram 300 can be implemented or may be implemented to achieve or facilitate aspects of wireless communication system 100 or wireless communication system 200. For example, the interference measurement diagram 300 illustrates interference or potential interference (and corresponding interference measurements) between various wireless communication devices (including UE 315-a, UE 315-b, UE 315-c, and UE 315-d, and network entities 305-a and 305-b). UE 315-a, UE 315-b, UE 315-c, and UE 315-d can each be achieved through… Figure 1 and Figure 2 Examples of UEs are illustrated and referred to in these figures. Network entity 305-a and network entity 305-b can each be accessed via... Figure 1 and Figure 2 Examples of network entities described in these diagrams are shown and referenced.

[0172] exist Figure 3 In the example, network entity 305-a may be associated with cell 310-a, and network entity 305-b may be associated with cell 310-b. Within cell 310-a, UE 315-a may send signaling (e.g., uplink signaling) to network entity 305-a, which may result in intra-cell CLI 330-a at UE 315-b. Similarly, within cell 310-b, UE 315-c may send signaling (e.g., uplink signaling) to network entity 305-b, which may result in intra-cell CLI 330-b at UE 315-d. In some aspects, the UE experiencing the CLI (e.g., a UE receiving downlink signals, such as UE 315-b or UE 315-d) may be referred to as the victim UE, and the UE causing the CLI (e.g., a UE sending uplink signals, such as UE 315-a or UE 315-c) may be referred to as the attacker UE.

[0173] In some deployment scenarios, such as when UE 315-b and UE 315-c are relatively close to each other (e.g., but served by different cells), signaling sent from UE 315-c (e.g., to network entity 305-b) may result in an inter-cell CLI 325 at UE 315-b. The inter-cell CLI 325 can be achieved through... Figure 2 Example and reference to the UE-to-UE CLI described in the figure. For instance, in a scenario where network entities 305-a and 305-b support dynamic TDD operation, UE 315-b may experience inter-cell CLI 325 from UE 315-c. Thus, UE 315-b may experience intra-cell CLI 330-a or inter-cell CLI 325, or both. Furthermore, in some deployment scenarios, network entity 305-a may send signaling that could trigger gNB-to-gNB CLI 320 (such as downlink signaling to UE 315-b). gNB-to-gNB CLI 320 can be via... Figure 2 An example of a gNB-to-cLI described in this figure is shown and referenced.

[0174] In the example, network entity 305 (e.g., network entity 305-a and network entity 305-b) can support SBFD (e.g., full-duplex communication using resources configured for SBFD). That is, network entity 305 can support simultaneous transmission of downlink signals and reception of uplink signals on a subband basis. In this example, network entity 305 (e.g., a full-duplex gNB) can support simultaneous transmission of downlink signals and reception of uplink signals in the same time slot. In some examples, SBFD can provide an increase in the uplink duty cycle, which can reduce latency. For example, SBFD operation can enable the transmission of uplink signals in time slots allocated for downlink signaling or the reception of downlink signals in time slots allocated for uplink signaling, which can improve (e.g., reduce) communication latency. Furthermore, SBFD can enhance system capabilities, resource utilization, and spectral efficiency, and enable flexible and dynamic uplink and downlink resource adaptation in a relatively robust manner according to uplink and downlink traffic.

[0175] In some examples, such as in cases where network entity 305 supports SBFD, intra-cell CLI 330-a, intra-cell CLI 330-b, inter-cell CLI 325, and inter-gNB CLI 320 may include inter-subband CLI. For example, during a time slot configured for SBFD at network entity 305-a, UE 315-a may transmit uplink signals to network entity 305-a using one or more uplink subbands within that time slot, while network entity 305-a may simultaneously transmit downlink signals to UE 315-b using downlink subbands. Thus, the uplink signal transmitted from UE 315-a may result in intra-cell CLI 330-a at UE 315-b. Alternatively, during the time slot configured for SBFD at network entities 305-a and 305-b, UE 315-c may use one or more uplink subbands within that time slot to transmit uplink signals to network entity 305-b, while network entity 305-a may simultaneously use downlink subbands to transmit downlink signals to UE 315-b. Thus, the uplink signal transmitted from UE 315-c may result in inter-cell CLI 325 at UE 315-b.

[0176] Alternatively or additionally, in some examples, network entities 305-a and 305-b may support fully or partially overlapping full-duplex communication. In such examples, intra-cell CLI 330-a, intra-cell CLI 330-b, inter-cell CLI 325, and inter-gNB CLI 320 may include intra-subband CLIs. Therefore, in some example deployments, such as those where network entities 305-a and 305-b can communicate and schedule communications according to network-side SBFD modes, UE 315-b may experience inter-subband, intra-cell, and inter-UE CLIs (such as intra-cell CLI 330-a) from UE 315-a and inter-subband, inter-cell, and inter-UE CLIs (such as inter-cell CLI 325) from UE 315-c.

[0177] In some deployments, network entities 305-a and 305-b may each experience a certain amount of inter-subband or intra-subband, gNB-to-gNB CLI (e.g., gNB-to-gNB CLI 320). For example, network entity 305-a may send downlink signaling via one or more downlink subbands, and this downlink signaling may result in gNB-to-gNB CLI 320 in one or more uplink subbands (in addition to one or more downlink subbands) at network entity 305-b. Similarly, network entity 305-b may send downlink signaling via one or more downlink subbands, and this downlink signaling may result in gNB-to-gNB CLI 320 in one or more uplink subbands (in addition to one or more downlink subbands) at network entity 305-a.

[0178] In some specific implementations, one or more of network entities 305 and one or more of UEs 315 may support techniques associated with inter-UE CLI mitigation for deployments involving non-overlapping subband full-duplex scenarios, deployments involving partially or fully overlapping full-duplex scenarios, deployments involving dynamic TDD scenarios, or any combination thereof. For example, one or more of network entities 305 may support a framework for configuring one or more of UEs 315 to measure and report CLIs that can be associated with one or more types of TTIs, such as TTIs associated with non-overlapping subband full-duplex scenarios (e.g., SBFD TTIs), TTIs associated with partially or fully overlapping full-duplex scenarios (e.g., non-SBFD TTIs), or TTIs associated with dynamic TDD scenarios (e.g., aligned or unaligned dynamic TDD TTIs). Alternatively or additionally, one or more network entities 305 may support a framework for configuring one or more of the UEs 315 to measure and report CLIs that can be associated with (e.g., included in the SBFD TTI) non-contiguous subbands. In some examples, such a framework can improve the accuracy of CLI measurements, among other benefits.

[0179] Figure 4 An example of a wireless communication system 400 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. The wireless communication system 400 may be implemented or can be implemented to achieve or facilitate aspects of wireless communication system 100, wireless communication system 200, and interference measurement diagram 300. For example, the wireless communication system 400 includes UE 415-a and UE 415-b, which may be via... Figure 1 and Figure 2 Examples of UEs are illustrated and referred to in these figures. Additionally, the wireless communication system 400 includes network entities 405-a and 405-b, which can be... Figure 1 and Figure 2 Examples of network entities described in these figures are illustrated and referenced. Network entity 405 may communicate with one or more of UEs 415 via one or more communication links. For example, network entity 405-a may communicate with UE 415-a via uplink 410-a. Additionally, network entity 405-a may communicate with UE 415-b via uplink 410-c and downlink 420. Network entity 405-b may communicate with UE 415-a via uplink 410-b. In some examples, uplink 410 and downlink 420 may each be via... Figure 1 An example of a communication link 125 (e.g., a Uu interface) described in the figure is illustrated and referenced.

[0180] In some examples of the wireless communication system 400, one or both of the network entities 405 may support full-duplex operation (e.g., SBFD operation) or dynamic TDD operation, in which one of the network entities 405 may simultaneously or concurrently transmit downlink signals and receive uplink signals. For example, UE 415-a may transmit uplink signaling to network entity 405-a, while UE 415-b simultaneously receives downlink signaling from network entity 405-a. In some other examples, UE 415-a may transmit uplink signaling to network entity 405-b, while UE 415-b receives downlink signaling from network entity 405-a. Uplink signaling transmitted from UE 415-a (e.g., an attacking UE) may result in CLI 425 at UE 415-b. CLI 425 may be transmitted via… Figure 3 Examples of inter-cell CLIs or intra-cell CLIs described in this figure are illustrated and referenced.

[0181] For example, CLI 425 may be associated with a subband non-overlapping full-duplex scenario, a partially or fully overlapped full-duplex scenario, or a dynamic TDD scenario, or any combination thereof. That is, a CLI may occur during one or more TTIs associated with subband non-overlapping full-duplex operation, partially or fully overlapped full-duplex operation, or dynamic TDD operation (e.g., allocated for, or used for, subband non-overlapping full-duplex operation, partially or fully overlapped full-duplex operation, or dynamic TDD operation). As described herein, a TTI associated with SBFD operation (e.g., allocated for SBFD operation) may include a TTI during which one or both of network entities 405 can simultaneously transmit and receive on a subband basis. Therefore, a TTI associated with subband non-overlapping full-duplex operation may be referred to as an SBFD TTI (e.g., an SBFD symbol or time slot). As described herein, a TTI associated with partially or fully overlapped full-duplex operation (e.g., allocated for partially or fully overlapped full-duplex operation) may include a TTI (or a portion of a TTI) during which network entity 405 may simultaneously (or concurrently) send and receive communications according to full-duplex mode. That is, the format of a TTI (or a portion of a TTI) may be misaligned across network entity 405. For example, a TTI (or a portion of a TTI) may be allocated for downlink at network entity 405-a and for uplink at network entity 405-b, such that UE 415-a can send uplink signaling to network entity 405-b, while UE 415-b receives downlink signaling from network entity 405-a. Therefore, a TTI associated with partially or fully overlapped full-duplex operation may be referred to as a non-SBFD TTI (e.g., a non-SBFD symbol or time slot). As described herein, a TTI associated with dynamic TDD operation (e.g., allocated for dynamic TDD operation) may include a TTI during which network entity 405 can simultaneously (or concurrently) transmit and receive communications according to a half-duplex mode. For example, a TTI (or a portion of a TTI) may be allocated for downlink communication at network entity 405-a and uplink communication at network entity 405-b, such that network entity 405-a can transmit downlink communication while network entity 405-b receives uplink communication. In this example, the format of the TTI may be unaligned between network entities 405 (e.g., across corresponding cells served by network entity 405). An unaligned TTI associated with dynamic TDD operation may be referred to as an unaligned dynamic TDD TTI (e.g., an unaligned dynamic TDD symbol or time slot). In some other examples, TTI can be assigned for downlink or uplink communication at network entity 405-a and network entity 405-b, such that network entity 405-a and network entity 405-b can simultaneously (or concurrently) send downlink communication or receive uplink communication.In this example, the format of the TTI may be aligned between network entities 405 (e.g., across corresponding cells served by network entity 405). The aligned TTI associated with dynamic TDD operation may be referred to as an aligned dynamic TDD TTI (e.g., an aligned dynamic TDD symbol or slot). In some examples, the likelihood of one or both UEs 415 experiencing a CLI during an aligned dynamic TDD TTI may be relatively low compared to the likelihood of one or both UEs 415 experiencing a CLI during an unaligned dynamic TDD TTI, SBFD TTI, or a non-SBFD TTI.

[0182] To reduce or mitigate CLI 425 and improve the decoding of downlink signals at UE 415-b, network entity 405-a may configure UE 415-b to perform one or more CLI measurements (e.g., one or more RSRP measurements or one or more RSSI measurements) using one or more reference signals transmitted from UE 415-a (e.g., to network entity 405-a or network entity 405-b). In this example, network entity 405-a may send control signaling (e.g., reporting configuration) to configure UE 415-b to perform one or more CLI measurements (e.g., one or more UE-to-UE CLI measurements). For example, network entity 405-a may send reporting configuration (e.g., downlink control information (DCI), RRC message, MAC control element (MAC-CE)) indicating one or more parameters for the measurement or reporting of CLI experienced at UE 415-b, for example, due to signaling from UE 415-a. In other words, the reporting configuration may include parameter information that indicates one or more parameters used to measure or report CLI 425. One or more parameters may include the type of CLI metric to be reported (e.g., whether UE 415-b reports the value of an RSSI metric or an RSRP metric), one or more resources that UE 415-b may use to measure CLI during its operation (e.g., one or more CLI measurement resources), or one or more resources that UE 415-b may use to transmit reports including information indicating CLI during its operation (e.g., one or more CLI reporting resources), and other examples of parameters that can be used to interfere with the measurement or reporting. That is, the reporting configuration (e.g., control information) may include information indicating the type of CLI metric to be reported, information indicating the allocation of one or more resources (e.g., one or more CLI measurement resources) for CLI measurements, or information indicating the allocation of one or more resources (e.g., one or more CLI reporting resources) allocated for CLI reporting. In some examples, CLI measurement resources used for (or allocated for) RSSI measurements may be referred to as CLI-RSSI resources, and CLI measurement resources used for (or allocated for) RSRP measurements may be referred to as CLI-RSRP resources. Additionally, in some examples, resources used for (or allocated for) CLI measurements experienced at a UE due to signaling from another UE may be referred to as UE-to-UE CLI measurement resources.

[0183] like Figure 4As illustrated in the example, network entity 405-a may send control information 430-a (e.g., report configuration) to UE 415-b, which may indicate one or more CLI resources (e.g., CLI-RSRP resources, CLI-RSSI resources) available to UE 415-b for measuring CLI (e.g., for measuring CLI 425) experienced at UE 415-b due to signaling from UE 415-a. In this example, one or more CLI resources may include time-frequency resources that UE 415-a may use (or may be scheduled to use) to send uplink reference signals (e.g., CLI reference signal 435, such as a sounding reference signal (SRS)) to network entity 405-a or network entity 405-b. In other words, control information 430-a may indicate CLI measurement resources (e.g., UE-to-UE CLI measurement resources) corresponding to (or associated with) the CLI reference signal resources occupied (or allocated for) CLI reference signal 435. Control information 430-a may indicate one or more other parameters for measurement or reporting of CLI 425. The degree of CLI experienced at UE 415-b due to full-duplex operation (e.g., during SBFD TTI or non-SBFD TTI) may differ from the degree of CLI experienced at UE 415-b due to dynamic TDD operation (e.g., during aligned TDD TTI or unaligned dynamic TDD TTI). Therefore, one or more parameters for measurement or reporting of CLI associated with full-duplex operation may differ from one or more parameters for measurement or reporting of CLI associated with dynamic TDD operation. In other words, one or more parameters for measurement or reporting of CLI on SBFD TTI, non-SBFD TTI, aligned TDD TTI, and unaligned dynamic TDD TTI (e.g., CLI experienced during SBFD TTI, non-SBFD TTI, aligned TDD TTI, and unaligned dynamic TDD TTI) may be different. However, in some examples, network entity 405-a may lack a mechanism, let alone an effective one, for indicating multiple (e.g., different) parameters for measurement or reporting of CLIs associated with multiple (e.g., different) types of TTIs.

[0184] In some other examples, one or both of network entities 405 may support a framework for configuring UE 415-a (or UE 415-b) to measure and report CLIs over multiple types of TTIs. For example, one or both of network entities 405 and one or both of UE 415 may support one or more reporting configurations for inter-UE CLIs over multiple types of TTIs (e.g., two or more types of symbols or time slots). Figure 4As illustrated in the example, network entity 405-a may send control information 430-a (e.g., report configuration) to UE 415-b. In some examples, control information 430-a may indicate parameter information for reporting CLI 425. That is, control information 430-a may include information indicating at least one parameter for measurement or reporting of CLI 425.

[0185] In some examples, one or both of network entities 405 and one or both of UE 415 may support multiple (e.g., separate) reporting configuration CLIs for multiple types of TTI. In other words, one or both of network entities 405 and one or both of UE 415 may support multiple reporting configurations for two (or more) types of symbols or time slots. In some examples, multiple reporting configurations may be available for two types of symbols or time slots. In such examples, the two types of time slots or symbols may be SBFD symbols or time slots and non-SBFD symbols or time slots. Alternatively or concurrently, the two types of symbols or time slots may be aligned dynamic TDD and unaligned dynamic TDD symbols or time slots. In some other examples, multiple reporting configurations may be available for more than two types of time slots or symbols. In such examples, the more than two types of symbols or time slots may be SBFD symbols or time slots, non-SBFD symbols or time slots, or unaligned dynamic TDD symbols or time slots. As an illustrative example, (e.g., included in control information 430-a) parameter information may include first parameter information associated with a first type of TTI (e.g., in control information 430-a), which may include an SBFD TTI type, a non-SBFDTTI type, an unaligned dynamic TDD TTI type, an aligned dynamic TDD TTI type, or a non-SBFD unaligned dynamic TDDDTTI. In some examples, control information 430-a may include an indication of the TTI to which the first parameter information applies for the first type of TTI. In some other examples, UE 415-b may autonomously determine the TTI to which the first parameter information applies for the first type of TTI.

[0186] Control information 430-a can configure UE 415-b to report CLIs on a first type of TTI. That is, control information 430-a can configure UE 415-b to measure or report CLIs experienced (e.g., detected or measured at the UE) during one or more TTIs of the first type. For example, UE 415-b may receive a CLI reference signal 435 during one or more TTIs of the first type, which may result in CLI 425. Therefore, UE 415-b may measure (and report) CLI 425 during one or more TTIs. In some examples, UE 415-b may send a report 440 that may include information indicating CLI 425 (e.g., indicating CLIs measured at UE 415-b during one or more TTIs). The information indicating CLI 425 may be associated with (e.g., based on) the CLI reference signal 435. For example, UE 415 may generate information indicating CLI 425 based on CLI reference signal 435 (e.g., one or more CLI measurements based on CLI reference signal 435).

[0187] In some examples, UE 415-a can be configured to measure and report CLIs for multiple types of TTIs. For example, UE 415-b can receive control information 430-b (e.g., in addition to control information 430-a), which may include second parameter information associated with a second type of TTI or a third type of TTI (e.g., within control information 430-b). As an illustrative example, the first type of TTI may include an SBFD TTI type, the second type of TTI may include a non-SBFD TTI type, and the third type of TTI may include an unaligned dynamic TDD TTI type. In this example, control information 430-a may correspond to a single reporting configuration (e.g., a single CLI reporting configuration, or a single CLI information element (IE) within a Channel State Information (CSI) reporting configuration) for the first type of TTI (e.g., for an SBFD TTI). That is, control information 430-a may configure UE 415-b (e.g., only) to report CLIs on SBFD symbols or time slots. In other words, the first parameter information included in control information 430-a can be used to report CLIs associated with the SBFD operating mode at network entity 405-a. Therefore, control information 430-a (e.g., first CSI reporting configuration, first CLI reporting configuration) can configure UE 415-b to measure CLIs that can be associated with resources (e.g., CLI resources) within an SBFD symbol or time slot. In some examples, CLI resources may include periodic CLI resources, semi-periodic CLI resources, or aperiodic CLI resources. In other words, control information 430-a can configure UE 415-b to measure (and report) CLIs associated with periodic CLI resources, semi-periodic CLI resources, or aperiodic CLI resources within one or more SBFD symbols or time slots.

[0188] In some examples, control information 430-b may correspond to a single reporting configuration (e.g., a single CLI reporting configuration, or a single CLI IE within a CSI reporting configuration) for a second type of TTI (e.g., for a non-SBFD TTI) or for a third type of TTI (e.g., for an unaligned dynamic TDD TTI). That is, control information 430-b may configure (e.g., configure only) UE 415-b to report CLIs on non-SBFD symbols or slots or on unaligned dynamic TDD symbols or slots. In other words, the second parameter information may be used to report CLIs associated with a full-duplex operating mode at network entity 405-a or a dynamic TDD operating mode at network entity 405-a (e.g., a half-duplex operating mode at network entity 405-a with an unaligned TTI format). Therefore, control information 430-b (e.g., a second CSI or CLI report configuration) can configure UE 415-b to measure CLIs associated with CLI resources within non-SBFD symbols or slots (e.g., measuring one or more periodic CLI resources, semi-periodic CLI resources, or aperiodic CLI resources within non-SBFD symbols or slots). Alternatively, control information 430-b (e.g., a second CSI or CLI report configuration) can configure UE 415-b to measure CLIs associated with CLI resources within unaligned dynamic TDD symbols or slots (e.g., measuring one or more periodic CLI resources, semi-periodic CLI resources, or aperiodic CLI resources within one or more unaligned dynamic TDD symbols or slots). In some examples, for instance, if the format of a non-SBFD symbol or time slot is not aligned between network entity 405-a and network entity 405-b (e.g., if a non-SBFD symbol or time slot is allocated for downlink at network entity 405-a and uplink at network entity 405-b), network entity 405-a may configure UE 415-b to measure CLIs associated with CLI resources within the non-SBFD symbol or time slot. That is, non-SBFD symbols or time slots may be misaligned between neighboring cells (e.g., cells served via network entity 405), which may affect (e.g., cause, result in) CLI 425. Therefore, network entity 405-a may configure UE 415-b to measure CLIs associated with CLI resources within non-SBFD symbols or time slots (e.g., non-SBFD misaligned dynamic TDD TTI).

[0189] In some examples, control information 430-a and control information 430-b may be associated with one or more CLI resources. That is, multiple (e.g., individual) reporting configurations (such as control information 430-a and control information 430-b) may be linked to one or more of the same CLI resources or one or more different CLI resources. In other words, control information 430-a may indicate a first set of one or more CLI resources associated with a first type of TTI (e.g., SBFD TTI), and control information 430-b may indicate a second set of CLI resources associated with a second type of TTI (e.g., non-SBFD TTI) or a third type of TTI (e.g., unaligned dynamic TDD TTI). In some examples, the first set and the second set of CLI resources may include different CLI resources. In some other examples, the first set and the second set of CLI resources may include one or more CLI resources within the same CLI resource (e.g., one or more CLI resources may be common to both the first and second sets of CLI resources). In some examples, control information 430-a may include both first parameter information and second parameter information. For example, control information 430-a could be an example of a CSI reporting configuration that includes one or more first IEs or fields (e.g., first parameter information) associated with a CLI on a first type of TTI and one or more second IEs or fields (e.g., second parameter information) associated with a CLI on a second or third type of TTI. In some other examples, control information 430-a could be an example of a single reporting configuration (e.g., a CLI reporting configuration) that may include one or more first IEs or fields (e.g., first parameter information) associated with a CLI on a first type of TTI and one or more second IEs or fields (e.g., second parameter information) associated with a CLI on a second or third type of TTI. In such examples, control information 430-a could indicate both a first set of CLI resources associated with a first type of TTI and a second set of CLI resources associated with a second or third type of TTI.

[0190] In some examples, control information 430-a may instruct one or more CLI reporting resources. For example, control information 430-a may include instruction parameters ( Information regarding the CLI reporting resource. In this example, UE 415-b can determine that the CLI reporting resource has been in use for at least [time period missing] since the corresponding CLI measurement resource (e.g., the CLI resource occupied by CLI reference signal 435). Within a TTI. That is, the CLI resources to be used to send report 440 (which may include information indicating CLI 425) may have been used by UE 415-b at least after the TTI of CLI 425 has been measured during its period (e.g., including the TTI of CLI reference signal resources used to send CLI reference signal 435). Within a TTI. In other words, the CLI report resource to be used to send report 440 can be at the end relative to the corresponding CLI measurement resource (e.g., CLI reference signal resource). Within a symbol or time slot's TTI. In some examples, The value can include various types of TTI. That is to say, It can be defined as the next A symbol or time slot, regardless of the symbol or time slot type. In other words, control information 430a may indicate the reporting TTI in which report 440 is to be transmitted and the reference TTI (e.g., CLI resources occupied by CLI reference signals). One TTI (e.g., a minimum number or other suitable number of TTIs), and The value can include various types of TTIs (e.g., any type). In some examples, UE415-b may determine that the size of report 440 exceeds the reporting TTI (e.g., cannot be adapted within the reporting TTI). In such examples, UE415-b may search (e.g., continue searching) for the next TTI (e.g., the next adapted symbol or slot) that can accommodate the size of report 440. In some examples, the CLI reporting resource can be an example of a resource allocated to the Physical Uplink Control Channel (PUCCH). That is, the CLI reporting resource can be a PUCCH resource.

[0191] In some other examples, The value can include a single type of TTI. That is, It can be counted on a single type of TTI (e.g., only on a single type of TTI), such as SBFD TTI, non-SBFD TTI, unaligned dynamic TDD TTI, or aligned dynamic TDD TTI. In some examples, with parameters The type of the associated TTI can be based on the type of the TTI that includes the corresponding CLI resource (e.g., the corresponding CLI measurement resource, the corresponding CLI reference signal resource). For example, the reference TTI (e.g., the CLI resource during which CLI 425 was measured, the CLI resource occupied by CLI reference signal 435) can be a first type of TTI. Therefore, control information 430a can indicate the time between the reporting TTI (e.g., the TTI in which report 440 is to be sent) and the reference TTI. One TTI (e.g., a minimum number or other suitable number of TTIs), and The value may include the TTI of the first type (e.g., only the first type). In other words, UE 415-b may be used after the CLI resource of CLI reference signal 435 is occupied (e.g., after the corresponding CLI resource indicated via control information 430-a). SFBD symbol or time slot transmission report 440. In some examples, UE 415-b may transmit another report for CLI reference signals received during the TTI of a Type II or Type III TTI. For example, UE 415-b may transmit a report after the corresponding CLI resource indicated via control information 430-b. TTI (e.g., A non-SBFD time slot or symbol, Send another report (for each misaligned dynamic TDD slot or symbol).

[0192] In some examples, control information 430-a may indicate parameter information for multiple types of TTI. For example, one or both of network entities 405 and one or both of UE 415 may support a single (e.g., the same) CLI reporting configuration for multiple types of TTI. In other words, one or both of network entities 405 and one or both of UE 415 may support a single reporting configuration for two (or more) types of symbols or time slots. In some examples, the reporting configuration may be associated with two types of symbols or time slots. In such examples, the two types of time slots or symbols may be SBFD symbols or time slots and non-SBFD symbols or time slots. Therefore, control information 430-a may configure UE 415-b to report CLI on both SBFD symbols or time slots and non-SBFD symbols or time slots. In some other examples, the two types of symbols or time slots may be aligned dynamic TDD and unaligned dynamic TDD symbols or time slots. In such examples, control information 430-a can configure UE 415-b to report CLIs on both aligned and unaligned dynamic TDD symbols or slots. In some examples, the reporting configuration can be associated with more than two types of symbols or slots. In such examples, the more than two types of symbols or slots can be SBFD symbols or slots, non-SBFD symbols or slots, and unaligned dynamic TDD symbols or slots. In this example, control information 430-a can configure UE 415-b to report CLIs on SBFD slots or symbols, non-SBFD slots or symbols, and unaligned dynamic TDD symbols or slots.

[0193] For example, control information 430-a may indicate first parameter information associated with a first TTI type and second parameter information associated with a second or third TTI type. In such examples, UE behavior may be constrained (e.g., restricted) to disable averaging CLI measurement results across multiple (e.g., different) TTI types. That is, UE 415-b may suppress averaging CLI measurement values ​​across one or more TTIs of the first type and one or more TTIs of the second (or third) type. In some examples, UE 415-b may disable (or may be configured to disable) one or more UE capabilities at UE 415-b that can be associated with averaging CLI measurement values ​​across multiple TTI types (e.g., averaging CLI measurement values ​​across multiple TTI types may be supported). In such examples, UE 415-b may suppress averaging CLI measurement values ​​across one or more TTIs of the first type and one or more TTIs of the second (or third) type in response to disabling one or more UE capabilities. In some examples, such as based on this suppression, report 440 may indicate one or more CLI measurements associated with a first TTI type and one or more CLI measurements associated with a second (or third) TTI type. In some other examples, report 440 may indicate one or more CLI measurements associated with a first TTI type, and UE 415-b may send a second report indicating one or more CLI measurements associated with a second TTI type. Network entity 405-a may determine the TTI type associated with report 440 (or the corresponding TTI type associated with each CLI measurement indicated via report 440). That is, network entity 405-a may know whether report 440 is a CLI timing mapped to an SBFD symbol (e.g., associated with the first type), a CLI timing in a non-SBFD symbol (e.g., associated with the second type), or a CLI timing in an unaligned dynamic TDD TTI (e.g., associated with the third type). In some examples, network entity 405-a may apply report 440 based on the type of TTI associated with report 440 (e.g., information included in report 440, such as information indicating CLI 425). That is, network entity 405-b may know the type of symbol or time slot associated with the CLI report, and thus may use the CLI report accordingly on different symbol or time slot types.

[0194] In some examples, control information 430-a may indicate resource allocation information for measuring CLI 425. For example, control information 430-a may correspond to a reporting configuration for an SBFD TTI in which network entity 405-a may transmit and receive on a subband basis. In this example, network entity 405-a may be configured to transmit CLI resources on a set of non-contiguous subbands that can be allocated for downlink communication in the SBFD TTI (e.g., on two or more non-contiguous downlink subbands of the SBFD TTI) (e.g., via control information 430-a). For example, UE 415-a may receive CLI reference signal 435 via one or more CLI resources according to resource allocation information (e.g., included in control information 430-a). In this example, one or more CLI resources may be within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0195] In some examples, CLI 425 may span multiple relatively similar (e.g., symmetrical) subbands included in a set of discontinuous subbands allocated for downlink communication (e.g., multiple discontinuous downlink subbands). In such examples, UE 415-b may measure the CLI associated with a single downlink subband in a set of discontinuous subbands allocated for downlink communication (e.g., one downlink subband among multiple discontinuous downlink subbands of SBFD TTI). For example, network entity 405-a (e.g., gNB) may configure a single CLI resource (e.g., a CLI-RSSI or CLI-RSRP resource) for CLI measurement on one of multiple discontinuous downlink subbands for SBFD TTI. In other words, CLI reference signal 435 may occupy a single CLI resource within one subband in a set of discontinuous subbands allocated for downlink communication.

[0196] In some other examples, UE 415-b can measure CLIs associated with multiple non-contiguous downlink subbands. That is, UE 415-b can be configured to measure CLIs associated with two or more downlink subbands in a set of non-contiguous subbands allocated for downlink communication (e.g., two or more downlink subbands in a set of non-contiguous downlink subbands for SBFD TTI). For example, network entity 405-a (e.g., gNB) can be configured to measure two or more CLI resources (e.g., two or more CLI-RSSI or CLI-RSRP resources) on two or more downlink subbands in a set of non-contiguous downlink subbands for SBFD TTI. In other words, CLI reference signal 435 can occupy two or more CLI resources within two or more subbands in a set of non-contiguous subbands allocated for downlink communication. In some examples, each CLI resource can be within a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0197] In some other examples, network entity 405-a (e.g., gNB) may be configured to measure a single CLI resource (e.g., a CLI-RSSI or CLI-RSRP resource) on two or more downlink subbands in a plurality of non-contiguous downlink subbands for SBFD TTI. In other words, CLI reference signal 435 may occupy CLI resources within two or more subbands in a set of non-contiguous subbands allocated for downlink communication. In some examples, resource allocation information (e.g., indicated via control information 430-a) may include a bitmap indicating the distribution (e.g., frequency location) of CLI resources occupied by CLI reference signal 435 across a set of non-contiguous subbands allocated for downlink communication. In some other examples, resource allocation information (e.g., indicated via control information 430-a) may indicate a plurality of resource block sets including CLI resources. In such examples, one resource block set (e.g., each resource block set) in the plurality of resource block sets may be associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication. In other words, a network entity 405-a (e.g., gNB) may configure CLI resources (e.g., a CLI-RSSI or CLI-RSRP resource) for CLI measurements on two or more downlink subbands of multiple non-contiguous downlink subbands for SBFD TTI via a bitmap or via multiple sets of non-contiguous downlink resource blocks (e.g., explicitly).

[0198] In some other examples, network entity 405-a (e.g., gNB) may configure CLI resources for CLI measurements on two or more non-contiguous downlink subbands of an SBFD TTI symbol. In other words, network entity 405-a may (e.g., implicitly) configure a CLI-RSSI or CLI-RSRP resource for CLI measurements on two or more non-contiguous downlink subbands of an SBFD TTI symbol. That is, UE 415-a may (e.g., implicitly) determine CLI resources for CLI measurements on two or more downlink subbands of a plurality of non-contiguous downlink subbands for SBFD TTI. In some examples, UE 415-b may determine CLI resources based on (e.g., within a set of frequency resources) an SBFD configuration that is semi-statically configured with uplink subband frequency positions and one or more guard bands or uplink and downlink subband frequency positions. In other words, UE 415-b can receive a semi-static SBFD configuration (e.g., control information) that indicates the uplink subband frequency location and corresponding frequency location of one or more guard bands for an SBFD TTI, or indicates the uplink subband and corresponding frequency location of one or more downlink subbands for an SBFD TTI. In this example, UE 415-b can determine (e.g., implicitly) the distribution of CLI resources within discontinuous downlink subbands (e.g., within the frequency resource set) based on the semi-statically configured SBFD configuration (e.g., and the frequency resource set).

[0199] In other words, CLI resources can be examples of non-contiguous CLI resources within two or more downlink subbands in a plurality of non-contiguous downlink subbands of the SBFD TTI, and UE 415-b can determine two or more downlink subbands (e.g., the frequency positions of two or more downlink subbands) based on a semi-statically configured SBFD frequency configuration. In such an example, the semi-statically configured SBFD frequency configuration can indicate the corresponding frequency positions of the uplink subband and one or more guard bands. Alternatively, the semi-statically configured SBFD frequency configuration can (e.g., explicitly) indicate the corresponding frequency positions of the uplink subband and the downlink subband. In other words, CLI resources occupied by CLI reference signal 435 can be within two or more subbands in a set of non-contiguous subbands allocated for downlink communication, and UE 415-b can measure CLI within a portion of the CLI resources. This portion of the CLI resource may be based on semi-static configuration information for SBFD operation (e.g., a semi-statically configured SBFD configuration), and this semi-static configuration information may be used for subbands allocated for uplink communication (e.g., uplink subbands of an SBFD TTI) and one or more subbands in a set of non-contiguous subbands allocated for downlink communication (e.g., one or more downlink subbands of an SBFD TTI). Alternatively, the semi-static configuration information may be used for subbands allocated for uplink communication (e.g., uplink subbands of an SBFD TTI) and one or more guard bands. In such examples, report 440 may indicate information that indicates the measured CLI. In some examples, UE 415-b may receive second control information (e.g., semi-static configuration information, a semi-statically configured SBFD frequency configuration) indicating the frequency position of a subband allocated for uplink communication or the corresponding frequency position of one or more guard bands.

[0200] In some examples, one or both of network entities 405 and one or both of UE 415 may support non-contiguous CLI resource configurations for measuring CLIs in multiple non-contiguous downlink subbands for SBFD TTI. That is, one or both of network entities 405 and one or both of UE 415 may support non-contiguous CLI resource configurations for measuring CLIs in two or more non-contiguous downlink subbands within an SBFD symbol or slot. In such examples, control information 430-a (e.g., reporting configuration) may be linked to multiple CLI resources or resource sets (e.g., two different CLI resources or resource sets). That is, resource allocation information (e.g., included in control information 430-a) may indicate two CLI resource sets including one or more CLI resources occupied by CLI reference signal 435. In such examples, one CLI resource set from the two CLI resource sets (e.g., each CLI resource set) may be associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0201] In some other examples, control information 430-a (e.g., report configuration) may be linked to a single CLI resource or resource set. In such examples, resource allocation information (e.g., included in control information 430-a) enables non-contiguous CLI resource configuration at UE 415-b. That is, a single CLI resource or resource set may correspond to a CLI resource or CLI resource set within a non-contiguous downlink subband of the SBFD TTI. In some examples, a CLI resource or CLI resource set may be indicated via one or more resource block sets. For example, resource allocation information may indicate a first (e.g., start) resource block of a CLI resource set and a second (e.g., end, last) resource block of one or more CLI resource sets. In some examples, resource allocation information may indicate a corresponding pair of first and second resource blocks for multiple subbands. That is, resource allocation information may indicate a corresponding start and end resource block for multiple subbands (e.g., each subband) allocated for downlink communication in a set of non-contiguous subbands. Additionally or alternatively, resource allocation information may indicate the number of resource blocks for one or more subbands. For example, resource allocation information can indicate the corresponding number of resource blocks for each subband in a set of non-contiguous subbands allocated for downlink communication.

[0202] In other words, a CLI resource set may include one or more resource block sets, which include one or more CLI resources occupied by CLI reference signal 435. Additionally, one or more resource block sets (e.g., CLI resource sets) may be associated with a set of non-contiguous subbands allocated for downlink communication. In this example, resource allocation information may indicate one or more resource block sets or one or more CLI resources within a resource block set, or both. For example, resource allocation information may include (e.g., explicitly) one or more bitmaps indicating one or more resource block sets. That is, resource allocation information may indicate start and end resource blocks, or a corresponding number of resource blocks in each subband of the set of non-contiguous subbands allocated for downlink communication, via one or more bitmaps. In other words, resource allocation information may include a bitmap indicating a CLI resource set, or a bitmap indicating one or more CLI resources within a CLI resource set, or both. Alternatively or additionally, resource allocation information may indicate one or more resource block sets within a CLI resource set (e.g., via start and end resource blocks or via a certain number of resource blocks in each downlink subband). In this example, one or more resource block sets comprise one or more CLI resources occupied via CLI reference signal 435. Additionally, in this example, each resource block set may be associated with a corresponding subband in a set of discontinuous subbands allocated for downlink communication.

[0203] In some other examples, network entity 405-a (e.g., gNB) may (e.g., implicitly) configure one or more resource block sets for CLI measurements on two or more non-contiguous downlink subbands for SBFDTTI symbols. For example, network entity 405-a may use a contiguous (e.g., relatively wideband) CLI resource configuration. That is, network entity 405-a may (e.g., via control information 430-a) indicate a contiguous CLI resource configuration to UE 415-a. In this example, UE 415-a may determine CLI resources based on the contiguous CLI resource configuration (e.g., implicitly). For example, UE 415-a may apply the contiguous (e.g., relatively wideband) CLI resource configuration based on (e.g., based on) (e.g., within a set of frequency resources) uplink subband frequency positions and one or more guard bands, or a semi-statically configured SBFD configuration of uplink subband frequency positions and downlink subband frequency positions. In some examples, UE 115 can be configured using rules to exclude CLI resources that may be within uplink subbands and guard bands, or to exclude resource blocks outside downlink subbands. In other words, UE 415-b can measure CLIs within one or more resource block sets included in a CLI resource set, and the one or more resource block sets may include one or more CLI resources occupied by CLI reference signal 435. In this example, the one or more resource block sets may be based on semi-static configuration information for SBFD operation. Alternatively, in this example, the semi-static configuration information may be used for one or more subbands in a set of subbands allocated for uplink communication and non-contiguous subbands allocated for downlink communication, or the semi-static configuration information may be used for subbands allocated for uplink communication and one or more guard bands. In such examples, the information included in report 440 may indicate the measured CLIs. In some examples, sending control information 430-a (or control information 430-b) to UE 415-b enables CLI reporting for various types of TTIs, which can improve communication reliability and reduce latency within the wireless communication system 400, among other benefits.

[0204] Figure 5 An example of a process flow 500 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Process flow 500 may be implemented or can be implemented to facilitate or achieve one or more aspects of wireless communication system 100, wireless communication system 200, interference measurement diagram 300, and wireless communication system 400. For example, process flow 500 may be implemented at UE 515-a and UE 515-b, and they may be implemented via... Figures 1 to 4 Examples of UEs described in these figures are illustrated and referenced. Additionally, process flow 500 may be implemented at network entity 505, which may be through... Figures 1 to 4 Examples of network entities described in these figures are illustrated and referenced. Operations performed at UE 515 (e.g., UE 515-a, UE 515-b) and network entity 505 can support improvements in communication between UE 515 and network entity 505, as well as other benefits. In the following description of process flow 500, operations performed at UE 515 and network entity 505 may be performed in a different order than the examples shown. Additionally, operations performed at UE 515 and network entity 505 may be performed at different times. Some operations may be combined, and some may be omitted. In some examples, UE 515 and network entity 505 may support a framework for UE-to-UE CLI measurement and reporting over various types of TTIs.

[0205] At point 520, UE 515-b can receive control information from network entity 505. The control information can be received via... Figures 1 to 4 Examples of control information (e.g., reporting configuration) described in these figures are illustrated and referenced. For example, control information may indicate parameter information used for reporting CLI. In some examples, the parameter information may include first parameter information for reporting CLI, which may be associated in the control information with a first type of TTI (e.g., it may be associated with one of the SBFD TTI type, a non-SBFD TTI type, or an unaligned dynamic TDD TTI type).

[0206] At position 525, UE 515-b can receive one or more UE-to-UE CLI reference signals from UE 515-a. The first or more UE-to-UE CLI reference signals can each be received via... Figures 1 to 4 Examples of CLI reference signals (e.g., UE-to-UE CLI reference signals) described in these figures are illustrated and referenced. For example, the first or more UE-to-UE CLI reference signals may each be examples of uplink reference signals (such as SRS). UE 515-b may receive the first or more UE-to-UE CLI reference signals during one or more TTIs of the first type of TTI.

[0207] In some examples, the parameter information (e.g., indicated via control information received at 520) may include second parameter information for reporting CLI. The second parameter information may be associated with a second type of TTI in the control information. The second type of TTI may be different from the first type of TTI (e.g., it may be a different one of SBFD TTI type, non-SBFD TTI type, or unaligned dynamic TDD TTI type).

[0208] In such an example, at 530, UE 515-b can receive a second or more UE-to-UE CLI reference signals from UE 515-b. The second or more UE-to-UE CLI reference signals can each be received via... Figures 1 to 4 Examples of CLI reference signals (e.g., UE-to-UE CLI reference signals) described in these figures are illustrated and referenced. For example, a second or more UE-to-UE CLI reference signals may each be examples of uplink reference signals (such as SRS). UE 515-b may receive a second or more UE-to-UE CLI reference signals during one or more TTIs of the second type of TTI.

[0209] In some examples, at 535, UE 515-b may measure UE-UE CLI based on (e.g., using) a first or more UE-UE CLI reference signals or a second or more UE-UE CLI reference signals, or both. For example, UE 515-b may generate information indicating the CLI (e.g., UE-UE CLI) experienced at UE 515-b due to the first or more UE-UE CLI reference signals or the second or more UE-UE CLI reference signals, or both. In some examples, the information indicating the CLI may be based on an RSSI measurement or RSRP measurement performed on the first or more UE-UE CLI reference signals or the second or more UE-UE CLI reference signals, or both. That is, the information indicating the CLI may indicate one or more CLI measurement values, which may include one or more values ​​of an RSSI measurement or one or more values ​​of an RSRP measurement.

[0210] At 545, UE 515-b may send a first report including information indicating CLI (e.g., the measured CLI). The information indicating CLI may be associated with a first or more CLI reference signals or a second or more CLI reference signals, or both. For example, (e.g., included in the first report) the information indicating CLI may be associated with a first type TTI, a second type TTI, or both a first type TTI and a second type TTI.

[0211] In some examples, at 540, UE 515-b may suppress the averaging of CLI measurements across multiple (e.g., different) TTI types. Therefore, information indicating CLI (e.g., information included in the first report sent at 545) may, based on this suppression, include first information associated with a first type of TTI and second information associated with a second type of TTI. The first information may include a first CLI measurement that can be indicated as associated with a first type of TTI, and the second information may include a second CLI measurement that can be indicated as associated with a second type of TTI. That is, the first report may include multiple IEs or fields that indicate to network entity 505 that the first CLI measurement is associated with a first type of TTI and the second CLI measurement is associated with a second type of TTI. In some examples, the first CLI measurement may include a first value of a CLI metric, and the second CLI measurement may include a second value of a CLI metric (or another CLI metric). In this example, the first value may be associated with a first type of TTI, and the second value may be associated with a second type of TTI. In some other examples, based on this suppression, UE 415-b may send multiple reports. For example, the first report may include (e.g., only) information indicating CLI that can be associated with the first type of TTI (e.g., the first report may only include first information associated with the first type of TTI).

[0212] In such examples, at 550, UE 515-b may send a second report including second information indicating CLI that can be associated with a second type of TTI (e.g., the second report may only include the second information associated with the second type of TTI). In some examples, the second information indicating CLI (e.g., included in the second report) may be associated with a second or more UE-to-UE CLI reference signals (e.g., only with a second or more UE-to-UE CLI reference signals). In some examples, the first report or the second report, or both, may enable CLI reporting for multiple types of TTIs, which can improve communication reliability and reduce latency, among other benefits.

[0213] Figure 6 An example of a process flow 600 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Process flow 600 may be implemented or can be implemented to facilitate or achieve one or more aspects of wireless communication system 100, wireless communication system 200, interference measurement map 300, wireless communication system 400, and process flow 500. For example, process flow 600 may be implemented at UE 615-a and UE 615-b, which may be via... Figures 1 to 5Examples of UEs described in these figures are illustrated and referenced. Additionally, process flow 600 may be implemented at network entity 605, which may be implemented via... Figures 1 to 5 Examples of network entities described in these figures are illustrated and referenced. Operations performed at UE 615 (e.g., UE 615-a, UE 615-b) and network entity 605 can support improvements in communication between UE 615 and network entity 605, as well as other benefits. In the following description of process flow 600, operations performed at UE 615 and network entity 605 may be performed in a different order than the examples shown. Additionally, operations performed at UE 615 and network entity 605 may be performed at different times. Some operations may be combined, and some may be omitted. In some examples, UE 615 and network entity 605 may support a framework for UE-to-UE CLI measurement and reporting over various types of TTIs.

[0214] At 620, UE 615-b can receive control information from network entity 605. The control information can be received via... Figures 1 to 5 Examples of control information (e.g., reporting configuration) described in these figures are illustrated and referenced. For example, control information may indicate resource allocation information used for measuring CLI. In some examples, resource allocation information may include a bitmap indicating one or more CLI resources allocated within a set of non-contiguous subbands for downlink communication. Alternatively or concurrently, resource allocation information may include a bitmap indicating the distribution of one or more CLI resources across a set of non-contiguous subbands.

[0215] In some other examples, resource allocation information may include information indicating one or more resource block sets, which comprise one or more CLI resources across a set of non-contiguous subbands. For example, each resource block set may be associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication. In some examples, resource allocation information may indicate one or more resource block sets within a CLI resource set. In such examples, one or more resource block sets may include one or more CLI resources.

[0216] At 625, UE 615-b can receive one or more UE-to-UE CLI reference signals from UE 615-a via one or more CLI resources, based on resource allocation information. For example, the one or more CLI resources may be located within one or more subbands in a set of discontinuous subbands allocated for downlink communication. The one or more UE-to-UE CLI reference signals may each be received via… Figures 1 to 5Examples of CLI reference signals (e.g., UE-to-UE CLI reference signals) described in these figures are illustrated and referenced. For example, one or more UE-to-UE CLI reference signals may each be an example of an uplink reference signal (such as an SRS).

[0217] In some examples, at 630, UE 615-b may measure UE-UE CLI based on (e.g., using) one or more UE-UE CLI reference signals. For example, UE 515-b may generate information indicating the CLI (e.g., UE-to-UE CLI) experienced at UE 615-b due to one or more UE-UE CLI reference signals. In some examples, the information indicating the CLI may be based on an RSSI measurement or RSRP measurement performed on one or more UE-UE CLI reference signals. That is, the information indicating the CLI may indicate the CLI measured at 630. For example, the information indicating the CLI may indicate one or more CLI measurement values, which may include one or more values ​​of an RSSI measurement or one or more values ​​of an RSRP measurement.

[0218] In some examples, UE 615-b may (e.g., at 630) measure (e.g., by one or more UE-to-UE CLI reference signals) a portion of CLI resources. In such examples, this portion may be based on semi-static configuration information for SBFD operation. For example, semi-static configuration information may be used for one or more subbands in a set of discontinuous subbands allocated for uplink communication and allocated for downlink communication. In some other examples, semi-static configuration information may be used for subbands allocated for uplink communication and one or more guard bands.

[0219] In some other examples, UE 615-b may (e.g., at 630) measure CLI within one or more resource block sets of a CLI resource set. In such examples, one or more resource block sets may include (e.g., occupied by one or more UE-to-UE CLI reference signals) one or more CLI resources. UE 615-b may determine one or more resource block sets based on semi-static configuration information for SBFD operation. That is, UE 615-b may determine one or more resource block sets based on semi-state configuration information for one or more subbands in a set of non-contiguous subbands allocated for uplink communication and allocated for downlink communication, or based on semi-static configuration information for subbands allocated for uplink communication and one or more guard bands.

[0220] At 635, UE 615-b can send a report including information indicating CLI (e.g., the measured CLI). The report can be transmitted via... Figures 1 to 5 Examples of reports described in these figures are illustrated and referenced. For instance, information indicating CLI that can be included in a report may be associated with one or more CLI reference signals. In some examples, the report may implement CLI reporting for non-contiguous subbands of the SBFD TTI, which can improve communication reliability and reduce latency, among other benefits.

[0221] Figure 7 A block diagram 700 illustrates a device 705 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure. Device 705 may be an example of aspects of UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0222] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with CLI reports for various types of TTIs). The information may be delivered to other components of device 705. Receiver 710 may utilize a single antenna or a collection of antennas.

[0223] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with CLI reports for various types of TTIs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0224] The communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of CLI reporting for various types of TTI as described herein. For example, the communication manager 720, receiver 710, transmitter 715, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0225] In some examples, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0226] Alternatively or concurrently, the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 720, receiver 710, transmitter 715, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0227] In some examples, the communication manager 720 may be configured to use or otherwise cooperate with the receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 720 may receive information from the receiver 710, transmit information to the transmitter 715, or be integrated with the receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0228] According to the examples disclosed herein, the communication manager 720 may support wireless communication at a first network entity (e.g., device 705). For example, the communication manager 720 is capable of, configured to, or operable to support components for receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The communication manager 720 is capable of, configured to, or operable to support components for receiving one or more CLI reference signals during one or more TTIs of the first type of TTI. The communication manager 720 is capable of, configured to, or operable to support components for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0229] Alternatively or additionally, according to the examples disclosed herein, the communication manager 720 may support wireless communication at a first network entity (e.g., device 705). For example, the communication manager 720 may be capable of, configured to, or operable to support components for receiving control information indicating resource allocation information for measuring CLI. The communication manager 720 may be capable of, configured to, or operable to support components for receiving one or more CLI reference signals via one or more CLI resources based on resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. The communication manager 720 may be capable of, configured to, or operable to support components for transmitting reports including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0230] By including or configuring a communication manager 720 according to an example as described herein, device 705 (e.g., controlling receiver 710, transmitter 715, communication manager 720 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0231] Figure 8 A block diagram 800 of a device 805 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Device 805 may be an example of aspects of device 705 or UE 115 as described herein. Device 805 may include a receiver 810, a transmitter 815, and a communication manager 820. Device 805, or one or more components of device 805 (e.g., receiver 810, transmitter 815, and communication manager 820), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0232] Receiver 810 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with CLI reports for various types of TTIs). The information may be delivered to other components of device 805. Receiver 810 may utilize a single antenna or a collection of antennas.

[0233] Transmitter 815 may provide components for transmitting signals generated by other components of device 805. For example, transmitter 815 may transmit information associated with various information channels (e.g., control channels, data channels, information channels associated with CLI reports for various types of TTIs), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 815 may be co-located with receiver 810 in a transceiver module. Transmitter 815 may utilize a single antenna or a collection of multiple antennas.

[0234] Device 805 or its various components may be examples of parts for performing various aspects of CLI reporting for various types of TTI as described herein. For example, communication manager 820 may include control information component 825, CLI reference signal component 830, reporting component 835, or any combination thereof. Communication manager 820 may be examples of aspects of communication manager 720 as described herein. In some examples, communication manager 820 or its various components may be configured to use or otherwise cooperate with receiver 810, transmitter 815, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 820 may receive information from receiver 810, transmit information to transmitter 815, or be integrated in combination with receiver 810, transmitter 815, or both to acquire information, output information, or perform various other operations as described herein.

[0235] According to the examples disclosed herein, the communication manager 820 may support wireless communication at a first network entity (e.g., device 805). The control information component 825 is capable of, configured to, or operable to support means for receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The CLI reference signal component 830 is capable of, configured to, or operable to support means for receiving one or more CLI reference signals during one or more TTIs of the first type of TTI. The reporting component 835 is capable of, configured to, or operable to support means for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0236] Alternatively or additionally, according to the examples disclosed herein, the communication manager 820 may support wireless communication at a first network entity (e.g., device 805). The control information component 825 is capable of, configured to, or operable to support means for receiving control information indicating resource allocation information for measuring CLI. The CLI reference signal component 830 is capable of, configured to, or operable to support means for receiving one or more CLI reference signals via one or more CLI resources based on resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. The reporting component 835 is capable of, configured to, or operable to support means for transmitting reports including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0237] Figure 9 A block diagram 900 is shown of a communication manager 920 supporting CLI reporting for multiple types of TTIs according to one or more aspects of this disclosure. The communication manager 920 may be an example of a communication manager 720, a communication manager 820, or aspects thereof as described herein. The communication manager 920 or its various components may be examples of parts for performing various aspects of CLI reporting for multiple types of TTIs as described herein. For example, the communication manager 920 may include a control information component 925, a CLI reference signal component 930, a reporting component 935, a CLI information component 940, a CLI measurement component 945, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0238] According to the examples disclosed herein, the communication manager 920 may support wireless communication at a first network entity. The control information component 925 is capable of, configured to, or operable to support means for receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The CLI reference signal component 930 is capable of, configured to, or operable to support means for receiving one or more CLI reference signals during one or more TTIs of the first type of TTI. The reporting component 935 is capable of, configured to, or operable to support means for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0239] In some examples, the parameter information includes second parameter information for reporting CLI. In some examples, the second parameter information is associated with a second type of TTI in the control information. In some examples, the second type of TTI differs from the first type of TTI. In some examples, the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0240] In some examples, one or more CLI reference signals are received during at least one CLI reference signal of a first set of CLI resources. In some examples, the information indicating the CLI is associated only with a first type of TTI.

[0241] In some examples, CLI reference signal component 930 is capable of, configured to, or operable to support components for receiving a second or more CLI reference signals during one or more TTIs of the second type of TTI. In some examples, reporting component 935 is capable of, configured to, or operable to support components for transmitting a second report including second information indicating CLI, wherein the second information indicating CLI is associated only with the second or more CLI reference signals. In some examples, the information indicating CLI is associated with both the first type of TTI and the second type of TTI.

[0242] In some examples, CLI information component 940 is capable of, configured to, or operable to support components for suppressing the averaging of CLI measurements across different TTI types, wherein information indicating CLI is based on this suppression to include first information associated with a first type of TTI and second information associated with a second type of TTI.

[0243] In some examples, the first information includes a first CLI measurement value indicated as associated with a first type of TTI. In some examples, the second information includes a second CLI measurement value indicated as associated with a second type of TTI. In some examples, the first CLI measurement value includes a first value of a CLI metric, and the second CLI measurement value includes a second value of a CLI metric. In some examples, the first value is associated with a first type of TTI, and the second value is associated with a second type of TTI.

[0244] In some examples, the first type of TTI includes SBFD TTI type, non-SBFD TTI type, unaligned dynamic TDD TTI type, aligned dynamic TDD TTI type, or non-SBFD unaligned dynamic TDD TTI type. In some examples, CLI information component 940 is capable of, configured to, or operable to support components for generating information indicating CLI based on one or more CLI reference signals.

[0245] In some examples, to support the reception of control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information via CLI report configuration messages or CSI report configuration messages. In some examples, the control information indicates a minimum number of TTIs between the report TTI and the reference TTI in which a report is to be sent. In some examples, the minimum number of TTIs includes any type of TTI. In some examples, the control information indicates a minimum number of TTIs between the report TTI and the reference TTI in which a report is to be sent. In some examples, the minimum number of TTIs includes only the first type of TTI.

[0246] In some examples, the first type of TTI includes a type of time slot or a type of symbol. In some examples, the first network entity includes the UE. In some examples, one or more CLI reference signals include UE-to-UE CLI reference signals. In some examples, the information indicating the CLI includes information indicating the UE-to-UE CLI. In some examples, the first parameter information is used to report the CLI associated with the half-duplex operation mode at the first network entity.

[0247] In some examples, in order to support receiving control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein the first parameter information is used to report CLI associated with a full-duplex operating mode at the second network entity.

[0248] In some examples, in order to support receiving control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein the first parameter information is used to report CLI associated with the sub-band full-duplex operation mode at the second network entity.

[0249] In some examples, in order to support the reception of control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein the first parameter information is used to report a CLI associated with a half-duplex operation mode at the second network entity and having an unaligned TTI format.

[0250] In some examples, the parameter information includes information indicating at least one parameter used to measure or report CLI. In some examples, at least one parameter includes the type of CLI metric to be reported, one or more resources used to measure the CLI, or one or more resources used to report the CLI. In some examples, the type of CLI metric includes an RSRP metric type or an RSSI metric type. In some examples, the control information includes a first parameter information indicating the TTI for a first type of TTI.

[0251] Alternatively or additionally, according to the examples disclosed herein, the communication manager 920 may support wireless communication at a first network entity. In some examples, the control information component 925 is capable of, configured to, or operable to support means for receiving control information indicating resource allocation information for measuring CLI. In some examples, the CLI reference signal component 930 is capable of, configured to, or operable to support means for receiving one or more CLI reference signals via one or more CLI resources based on resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. In some examples, the reporting component 935 is capable of, configured to, or operable to support means for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0252] In some examples, one or more CLI resources comprise CLI resources within a subband of a set of non-contiguous subbands allocated for downlink communication. In some examples, one or more CLI resources comprise two CLI resources. In some examples, each of the two CLI resources is within a corresponding subband of a set of non-contiguous subbands allocated for downlink communication.

[0253] In some examples, one or more CLI resources include CLI resources within at least two subbands in a set of non-contiguous subbands allocated for downlink communication. In some examples, resource allocation information includes a bitmap indicating the distribution of CLI resources across the set of non-contiguous subbands.

[0254] In some examples, resource allocation information indicates a set of multiple resource block sets that include CLI resources. In some examples, each resource block set in the set of multiple resource block sets is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0255] In some examples, one or more CLI resources are included within a set of non-contiguous subbands allocated for downlink communication, and the CLI measurement component 945 is capable of, configured to, or operable to support components for measuring a portion of the CLI resources, wherein this portion is based on semi-static configuration information for SBFD operation, wherein the semi-static configuration information is for subbands allocated for uplink communication and one or more subbands in a set of non-contiguous subbands allocated for downlink communication, or the semi-static configuration information is for subbands allocated for uplink communication and one or more guard bands, and wherein the information indicates the CLI being measured.

[0256] In some examples, the control information component 925 is capable of, configured to, or operable to support components for receiving second control information indicating the frequency position of a subband allocated for uplink communication or the corresponding frequency position of one or more guard bands.

[0257] In some examples, the resource allocation information indicates two CLI resource sets, each including one or more CLI resources. In some examples, each CLI resource set is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0258] In some examples, resource allocation information indicates a set of CLI resources that includes one or more CLI resources. In some examples, the CLI resource set is associated with a set of non-contiguous subbands allocated for downlink communication. In some examples, resource allocation information includes a bitmap indicating one or more CLI resources.

[0259] In some examples, resource allocation information indicates one or more resource block sets within a CLI resource set. In some examples, one or more resource block sets include one or more CLI resources. In some examples, each resource block set is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0260] In some examples, CLI measurement component 945 is capable of, configured to, or operable to support components for measuring CLIs within one or more resource block sets within a CLI resource set, wherein the one or more resource block sets include one or more CLI resources, wherein the one or more resource block sets are based on semi-static configuration information for SBFD operation, wherein the semi-static configuration information is used for one or more subbands in a set of subbands allocated for uplink communication and non-contiguous subbands allocated for downlink communication, or the semi-static configuration information is used for subbands allocated for uplink communication and one or more guard bands, and wherein the information indicates the CLI being measured.

[0261] In some examples, the set of discontinuous subbands allocated for downlink communication is within the TTI allocated for SBFD operation at the second network entity. In some examples, the first network entity includes the UE, and the second network entity includes the base station.

[0262] In some examples, one or more CLI reference signals include a UE-to-UE CLI reference signal. In some examples, resource allocation information is used to measure the UE-to-UE CLI. In some examples, resource allocation information is used to measure the CLI associated with a half-duplex operating mode at a first network entity.

[0263] In some examples, in order to support the reception of control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein resource allocation information is used to measure the CLI associated with the full-duplex operation mode at the second network entity.

[0264] In some examples, in order to support the reception of control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein resource allocation information is used to measure the CLI associated with the SBFD operating mode at the second network entity.

[0265] In some examples, in order to support the reception of control information, the control information component 925 is capable of, configured to, or operable to support components for receiving control information from a second network entity, wherein resource allocation information is used to measure CLI associated with a half-duplex operation mode at the second network entity and having an unaligned TTI format.

[0266] Figure 10A diagram of a system 1000 including a device 1005 supporting CLI reporting for multiple types of TTIs, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or may include components thereof. Device 1005 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1020, an input / output (I / O) controller 1010, a transceiver 1015, an antenna 1025, at least one memory 1030, code 1035, and at least one processor 1040. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1045).

[0267] I / O controller 1010 manages the input and output signals of device 1005. I / O controller 1010 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1010 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1010 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 1010 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 1010 may be implemented as part of one or more processors, such as at least one processor 1040. In some cases, a user may interact with the device 1005 via the I / O controller 1010 or via hardware components controlled by the I / O controller 1010.

[0268] In some cases, device 1005 may include a single antenna 1025. However, in other cases, device 1005 may have more than one antenna 1025, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1015 may communicate bidirectionally via one or more antennas 1025 as described herein, or via a wired or wireless link. For example, transceiver 1015 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1015 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1025 for transmission; and demodulating packets received from one or more antennas 1025. Transceiver 1015, or transceiver 1015 and one or more antennas 1025, may be an example of transmitter 715, transmitter 815, receiver 710, receiver 810, or any combination thereof or components thereof as described herein.

[0269] At least one memory 1030 may include random access memory (RAM) and read-only memory (ROM). At least one memory 1030 may store computer-readable, computer-executable code 1035, including instructions that, when executed by at least one processor 1040, cause device 1005 to perform the various functions described herein. Code 1035 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1035 may not be directly executable by at least one processor 1040, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0270] At least one processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 1040 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 1040. At least one processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 1030) to cause device 1005 to perform various functions (e.g., various functions or tasks supporting CLI reporting for various types of TTI). For example, device 1005 or components of device 1005 may include at least one processor 1040 and at least one memory 1030 coupled to or coupled to at least one processor 1040, at least one processor 1040 and at least one memory 1030 configured to perform the various functions described herein. In some examples, at least one processor 1040 may include multiple processors, and at least one memory 1030 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein.

[0271] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at a first network entity. For example, the communication manager 1020 is capable of, configured to, or operable to support components for receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The communication manager 1020 is capable of, configured to, or operable to support components for receiving one or more CLI reference signals during one or more TTIs of the first type of TTI. The communication manager 1020 is capable of, configured to, or operable to support components for transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0272] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1020 may support wireless communication at a first network entity. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for receiving control information indicating resource allocation information for measuring CLI. The communication manager 1020 may be capable of, configured to, or operable to support components for receiving one or more CLI reference signals via one or more CLI resources based on resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. The communication manager 1020 may be capable of, configured to, or operable to support components for transmitting reports including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals.

[0273] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 can support techniques for improving communication reliability, reducing latency, and utilizing communication resources more efficiently.

[0274] In some examples, the communication manager 1020 may be configured to cooperate with transceiver 1015, one or more antennas 1025, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1020 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1020 may be supported by or executed by at least one processor 1040, at least one memory 1030, code 1035, or any combination thereof. For example, code 1035 may include instructions that may be executed by at least one processor 1040 to cause device 1005 to perform various aspects of CLI reporting for various types of TTI as described herein, or at least one processor 1040 and at least one memory 1030 may be otherwise configured to perform or support such operations individually or jointly.

[0275] Figure 11 A block diagram 1100 of a device 1105 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0276] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0277] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Alternatively or concurrently, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0278] The communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of CLI reporting for various types of TTI as described herein. For example, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0279] In some examples, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0280] Alternatively or concurrently, the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1120, receiver 1110, transmitter 1115, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or collectively to support components for performing the functions described in this disclosure).

[0281] In some examples, the communication manager 1120 may be configured to use or otherwise cooperate with the receiver 1110, the transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1120 may receive information from the receiver 1110, transmit information to the transmitter 1115, or be integrated with the receiver 1110, the transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0282] According to the examples disclosed herein, communication manager 1120 may support wireless communication at a first network entity (e.g., device 1105). For example, communication manager 1120 may be capable of, configured to, or operable to support components for outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. Communication manager 1120 may be capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0283] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1120 may support wireless communication at a first network entity (e.g., device 1105). For example, the communication manager 1120 may be capable of, configured to, or operable to support components for outputting control information indicating resource allocation information for measuring CLI. The communication manager 1120 may be capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources based on resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0284] By including or configuring a communication manager 1120 according to an example as described herein, device 1105 (e.g., controlling receiver 1110, transmitter 1115, communication manager 1120, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0285] Figure 12 A block diagram 1200 of a device 1205 supporting CLI reporting for various types of TTIs according to one or more aspects of this disclosure is shown. Device 1205 may be an example of aspects of device 1105 or network entity 105 as described herein. Device 1205 may include receiver 1210, transmitter 1215, and communication manager 1220. Device 1205, or one or more components of device 1205 (e.g., receiver 1210, transmitter 1215, and communication manager 1220), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0286] Receiver 1210 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be delivered to other components of device 1205. In some examples, receiver 1210 may support acquiring information by receiving signals via one or more antennas. Alternatively or concurrently, receiver 1210 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0287] Transmitter 1215 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1205. For example, transmitter 1215 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Alternatively or additionally, transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1215 and receiver 1210 may be co-located in a transceiver, which may include or be coupled to a modem.

[0288] Device 1205 or its various components may be examples of parts for performing various aspects of CLI reporting for various types of TTIs as described herein. For example, communication manager 1220 may include parameter information component 1225, CLI instruction component 1230, resource allocation information component 1235, or any combination thereof. Communication manager 1220 may be examples of aspects of communication manager 1120 as described herein. In some examples, communication manager 1220 or its various components may be configured to use or otherwise cooperate with receiver 1210, transmitter 1215, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1220 may receive information from receiver 1210, transmit information to transmitter 1215, or be integrated in combination with receiver 1210, transmitter 1215, or both to acquire information, output information, or perform various other operations as described herein.

[0289] According to the examples disclosed herein, the communication manager 1220 may support wireless communication at a first network entity (e.g., device 1205). The parameter information component 1225 is capable of, configured to, or operable to support components for outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The CLI indication component 1230 is capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0290] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1220 may support wireless communication at a first network entity (e.g., device 1205). The resource allocation information component 1235 is capable of, configured to, or operable to support components for outputting control information indicating resource allocation information for measuring CLI. The CLI indication component 1230 is capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources based on resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0291] Figure 13 A block diagram 1300 is shown of a communication manager 1320 supporting CLI reporting for multiple types of TTIs according to one or more aspects of this disclosure. The communication manager 1320 may be an example of a communication manager 1120, a communication manager 1220, or aspects of both as described herein. The communication manager 1320 or its various components may be examples of parts for performing various aspects of CLI reporting for multiple types of TTIs as described herein. For example, the communication manager 1320 may include a parameter information component 1325, a CLI instruction component 1330, a resource allocation information component 1335, a report configuration message component 1340, a frequency location component 1345, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0292] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a first network entity. The parameter information component 1325 is capable of, configured to, or operable to support components for outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The CLI indication component 1330 is capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0293] In some examples, the parameter information includes second parameter information for reporting CLI. In some examples, the second parameter information is associated with a second type of TTI in the control information. In some examples, the second type of TTI differs from the first type of TTI. In some examples, the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0294] In some examples, the first set of CLI resources includes one or more CLI resources. In some examples, the information indicating the CLI is associated only with the first type of TTI.

[0295] In some examples, CLI instruction component 1330 is capable of, configured to, or operable to support components for obtaining a second report including second information indicating CLI, wherein the second information indicating CLI is associated only with a second or more CLI resources within one or more TTIs of a second type of TTI.

[0296] In some examples, the information indicating the CLI is associated with both a first type of TTI and a second type of TTI. In some examples, the information indicating the CLI includes first information associated with the first type of TTI and second information associated with the second type of TTI.

[0297] In some examples, the first information includes a first CLI measurement indicated as associated with a first type of TTI. In some examples, the second information includes a second CLI measurement indicated as associated with a second type of TTI.

[0298] In some examples, the first CLI measurement includes a first value of the CLI metric, and the second CLI measurement includes a second value of the CLI metric. In some examples, the first value is associated with a first type of TTI, and the second value is associated with a second type of TTI.

[0299] In some examples, the first type of TTI includes SBFD TTI type, non-SBFD TTI type, unaligned dynamic TDD TTI type, aligned dynamic TDD TTI type, or non-SBFD unaligned dynamic TDD TTI type. In some examples, the first type of TTI includes a type of slot or a type of symbol.

[0300] In some examples, to support the output of control information, the report configuration message component 1340 can be configured or operable to support components for outputting control information via CLI report configuration messages or CSI report configuration messages.

[0301] In some examples, the control information indicates the minimum number of TTIs between the reporting TTI and the reference TTI in which the report is to be sent. In some examples, the minimum number of TTIs includes any type of TTI.

[0302] In some examples, the control information indicates the minimum number of TTIs between the reporting TTI and the reference TTI in which the report is to be sent. In some examples, the minimum number of TTIs includes only the first type of TTI. In some examples, the first type of TTI includes either a type of time slot or a type of symbol. In some examples, the information indicating the CLI includes information indicating the UE to the UE CLI.

[0303] In some examples, in order to support output control information, parameter information component 1325 can be, configured, or operable to support components for outputting control information to a second network entity, wherein the first parameter information is used to report CLI associated with a half-duplex operation mode at the second network entity.

[0304] In some examples, the first parameter information is used to report the CLI associated with a full-duplex operation mode at the first network entity. In some examples, the first parameter information is used to report the CLI associated with an SBFD operation mode at the first network entity. In some examples, the first parameter information is used to report the CLI associated with a half-duplex operation mode at the first network entity and having an unaligned TTI format.

[0305] In some examples, in order to support output control information, parameter information component 1325 is capable of, configured to, or operable to support components for outputting control information to a second network entity, wherein the first parameter information indicates at least one parameter for measuring or reporting CLI.

[0306] In some examples, at least one parameter includes the type of CLI metric to be reported, one or more resources used to measure the CLI, or one or more resources used to report the CLI. In some examples, the type of CLI metric includes an RSRP metric type or an RSSI metric type. In some examples, the control information includes an indication of the TTI for which the first parameter information applies.

[0307] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1320 may support wireless communication at a first network entity. The resource allocation information component 1335 is capable of, configured to, or operable to support components for outputting control information indicating resource allocation information for measuring CLI. In some examples, the CLI indication component 1330 is capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources based on resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0308] In some examples, one or more CLI resources include CLI resources within one subband of a set of non-contiguous subbands allocated for downlink communication. In some examples, one or more CLI resources include two CLI resources. In some examples, each of the two CLI resources is within a corresponding subband of a set of non-contiguous subbands allocated for downlink communication. In some examples, one or more CLI resources include CLI resources within at least two subbands of a set of non-contiguous subbands allocated for downlink communication.

[0309] In some examples, resource allocation information includes a bitmap indicating the distribution of CLI resources across a set of non-contiguous subbands. In some examples, resource allocation information indicates a set of multiple resource block sets that include CLI resources. In some examples, each resource block set in the set of multiple resource block sets is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0310] In some examples, one or more CLI resources are included within a set of non-contiguous subbands allocated for downlink communication. In some examples, the information indicates the CLI measured within a portion of semi-static configuration information for SBFD operation. In some examples, the semi-static configuration information is used for subbands allocated for uplink communication and one or more subbands in a set of non-contiguous subbands allocated for downlink communication, or the semi-static configuration information is used for subbands allocated for uplink communication and one or more guard bands.

[0311] In some examples, the frequency location component 1345 is capable of, configured to, or operable to support components for outputting second control information indicating the frequency location of a subband allocated for uplink communication or the corresponding frequency location of one or more guard bands.

[0312] In some examples, the resource allocation information indicates two CLI resource sets, each including one or more CLI resources. In some examples, each CLI resource set is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0313] In some examples, resource allocation information indicates a CLI resource set that includes one or more CLI resources. In some examples, a CLI resource set is associated with a set of non-contiguous subbands allocated for downlink communication.

[0314] In some examples, resource allocation information includes a bitmap indicating one or more CLI resources. In some examples, resource allocation information indicates one or more resource block sets within a CLI resource set. In some examples, one or more resource block sets include one or more CLI resources. In some examples, each resource block set is associated with a corresponding subband in a set of non-contiguous subbands allocated for downlink communication.

[0315] In some examples, the information indicates CLI measured within one or more resource block sets within a CLI resource set. In some examples, one or more resource block sets comprise one or more CLI resources. In some examples, one or more resource block sets are based on semi-static configuration information for SBFD operation. In some examples, the semi-static configuration information is used for subbands allocated for uplink communication and one or more subbands in a set of discontinuous subbands allocated for downlink communication, or the semi-static configuration information is used for subbands allocated for uplink communication and one or more guard bands.

[0316] In some examples, the set of discontinuous subbands allocated for downlink communication is within the TTI allocated for SBFD operation at a first network entity. In some examples, the first network entity includes a base station.

[0317] In some examples, to support output control information, the resource allocation information component 1335 is capable of, configured to, or operable to support components for outputting control information to a second network entity including the UE, wherein the resource allocation information is used to measure UE to UE CLI.

[0318] In some examples, to support output control information, the resource allocation information component 1335 is capable of, configured to, or operable to support components for outputting control information to a second network entity, wherein the resource allocation information is used to measure the CLI associated with a half-duplex operating mode at the second network entity. In some examples, the resource allocation information is used to measure the CLI associated with a full-duplex operating mode at the first network entity.

[0319] In some examples, resource allocation information is used to measure the CLI associated with the SBFD operating mode at the first network entity. In some examples, resource allocation information is used to measure the CLI associated with a half-duplex operating mode at the first network entity and having an unaligned TTI format.

[0320] Figure 14 A diagram of a system 1400 including a device 1405 supporting CLI reporting for multiple types of TTIs, according to one or more aspects of this disclosure, is shown. Device 1405 may be an example of device 1105, device 1205, or network entity 105 as described herein, or may include components thereof. Device 1405 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1405 may include components supporting output and enabling communication, such as a communication manager 1420, a transceiver 1410, an antenna 1415, at least one memory 1425, code 1430, and at least one processor 1435. These components may communicate electronically or otherwise (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1440).

[0321] Transceiver 1410 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1410 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Alternatively, in some examples, transceiver 1410 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1405 may include one or more antennas 1415 that are capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1410 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1415, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1415, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1410 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1415 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1415 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1410 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1410, or transceiver 1410 and one or more antennas 1415, or transceiver 1410 and one or more antennas 1415 and one or more processors or one or more memory components (e.g., at least one processor 1435, at least one memory 1425, or both) may be included in a chip or chip assembly mounted in device 1405. In some examples, transceiver 1410 is operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0322] At least one memory 1425 may include RAM, ROM, or any combination thereof. At least one memory 1425 may store computer-readable, computer-executable code 1430 including instructions that, when executed by one or more of at least one processor 1435, cause device 1405 to perform the various functions described herein. Code 1430 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1430 may not be directly executable by one of the at least one processor 1435, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1425 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1435 may include multiple processors, and at least one memory 1425 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0323] At least one processor 1435 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1435 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1435. At least one processor 1435 may be configured to execute computer-readable instructions stored in memory (e.g., one or more of at least one memory 1425) to cause device 1405 to perform various functions (e.g., various functions or tasks supporting CLI reporting for various types of TTI). For example, device 1405 or components of device 1405 may include at least one processor 1435 and at least one memory 1425 coupled to one or more of the at least one processor 1435, wherein at least one processor 1435 and at least one memory 1425 are configured to perform the various functions described herein. At least one processor 1435 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1430) host functions for performing the functions of device 1405. At least one processor 1435 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1405 (such as within one or more memories of at least one memory 1425). In some implementations, at least one processor 1435 may be a component of a processing system. A processing system can generally refer to a system or series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components of, for example, device 1405). For example, the processing system of device 1405 may refer to a system that includes various other components or sub-components of device 1405 (such as at least one processor 1435, transceiver 1410, communication manager 1420, or other components or combinations of components of device 1405). The processing system of device 1405 can interface with other components of device 1405 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1405 may include a processing system and one or more interfaces for outputting information or for acquiring information, or both. These one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to both output and acquire information, and other specific implementations.In some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1405 to send information output from the chip or modem. Alternatively, in some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1405 to receive information or signal input, and such information can be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0324] In some examples, bus 1440 may support communication at protocol layers of the protocol stack (e.g., within a protocol layer). In some examples, bus 1440 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1405, or communication performed between different components of device 1405 that are co-addressable or may be located in different locations (e.g., where device 1405 may refer to a system in which one or more of communication manager 1420, transceiver 1410, at least one memory 1425, code 1430 and at least one processor 1435 may be located in one component of different components or partitioned between different components).

[0325] In some examples, the communication manager 1420 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1420 can manage the transfer of data communication between client devices (such as one or more UEs 115). In some examples, the communication manager 1420 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating other network entities 105 to control communication with UE 115. In some examples, the communication manager 1420 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0326] According to the examples disclosed herein, the communication manager 1420 may support wireless communication at a first network entity (e.g., device 1405). For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The communication manager 1420 may be capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0327] Alternatively or additionally, according to the examples disclosed herein, the communication manager 1420 may support wireless communication at a first network entity (e.g., device 1405). For example, the communication manager 1420 may be capable of, configured to, or operable to support components for outputting control information indicating resource allocation information for measuring CLI. The communication manager 1420 may be capable of, configured to, or operable to support components for obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources based on resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0328] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 can support techniques for improving communication reliability, reducing latency, and utilizing communication resources more efficiently.

[0329] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the transceiver 1410, one or more antennas 1415 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1420 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1420 may be supported or performed by the transceiver 1410, one or more processors in at least one processor 1435, one or more memories in at least one memory 1425, code 1430, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1435, at least one memory 1425, code 1430, or any combination thereof). For example, code 1430 may include instructions that can be executed by one or more of at least one processor 1435 to cause device 1405 to perform various aspects of CLI reporting for various types of TTI as described herein, or at least one processor 1435 and at least one memory 1425 may be otherwise configured to perform or support such operations individually or jointly.

[0330] Figure 15 A flowchart illustrating a method 1500 for supporting CLI reporting for various types of TTIs according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be performed by, as referenced... Figures 1 to 10The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0331] At 1505, the method may include receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. Operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1505 may be provided by reference to [reference needed]. Figure 9 The described control information component 925 is executed.

[0332] At 1510, the method may include receiving one or more CLI reference signals during one or more TTIs of the first type of TTI. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be determined by references... Figure 9 The CLI reference signal component 930 described herein is executed.

[0333] At 1515, the method may include sending a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be provided by reference to... Figure 9 The described reporting component 935 is executed.

[0334] Figure 16 A flowchart illustrating method 1600 for supporting CLI reporting for various types of TTIs according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed by, as referenced... Figures 1 to 10 The UE 115 described herein performs the following: In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0335] At 1605, the method may include receiving control information indicating resource allocation information for measuring the CLI. The operation of block 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 9 The described control information component 925 is executed.

[0336] At 1610, the method may include receiving one or more CLI reference signals via one or more CLI resources based on resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to... Figure 9 The CLI reference signal component 930 described herein is executed.

[0337] At 1615, the method may include sending a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI reference signals. Operation of block 1615 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1615 may be provided by reference to... Figure 9 The described reporting component 935 is executed.

[0338] Figure 17 A flowchart illustrating method 1700 for supporting CLI reporting for various types of TTIs according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a network entity or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0339] At 1705, the method may include outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information. The operation of block 1705 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to [reference needed]. Figure 13 The parameter information component 1325 described is executed.

[0340] At 1710, the method may include obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI. Operation of box 1710 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1710 may be provided by reference to [reference needed]. Figure 13 The described CLI instruction component 1330 is executed.

[0341] Figure 18A flowchart illustrating method 1800 for supporting CLI reporting for various types of TTIs according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a network entity or its components as described herein. For example, operation of method 1800 can be implemented by, as referenced... Figures 1 to 6 as well as Figures 11 to 14 The described network entity performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0342] At 1805, the method may include outputting control information indicating resource allocation information for measuring the CLI. The operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be provided by reference to [reference needed]. Figure 13 The resource allocation information component 1335 described is executed.

[0343] At 1810, the method may include obtaining a report including information indicating a CLI, wherein the information indicating a CLI is associated with one or more CLI resources based on resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to [reference]. Figure 13 The described CLI instruction component 1330 is executed.

[0344] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method of wireless communication performed by a first network entity, the method comprising: receiving control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; receiving one or more CLI reference signals during one or more TTIs of the first type of TTI; and transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0345] Aspect 2: According to the method of aspect 1, the parameter information includes second parameter information for reporting CLI, the second parameter information being associated with a second type of TTI in the control information, and the second type of TTI being different from the first type of TTI.

[0346] Aspect 3: The method according to aspect 2, wherein the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0347] Aspect 4: According to the method of aspect 3, wherein the one or more CLI reference signals are received during at least one CLI reference signal of the first set of CLI resources.

[0348] Aspect 5: The method according to any one of Aspects 2 to 4, wherein the information indicating the CLI is associated only with the first type of TTI.

[0349] Aspect 6: The method according to aspect 5 further includes: receiving a second or more CLI reference signals during one or more TTIs of the second type of TTI; and sending a second report including second information indicating CLI, wherein the second information indicating CLI is associated only with the second or more CLI reference signals.

[0350] Aspect 7: The method according to aspect 2, wherein the information indicating the CLI is associated with both the first type of TTI and the second type of TTI.

[0351] Aspect 8: According to the method of aspect 7, the method further includes: suppressing the averaging of CLI measurements across different TTI types, wherein the information indicating the CLI includes, based on the suppression, first information associated with the first type of TTI and second information associated with the second type of TTI.

[0352] Aspect 9: According to the method of aspect 8, wherein the first information includes a first CLI measurement value indicated as associated with the first type of TTI, and the second information includes a second CLI measurement value indicated as associated with the second type of TTI.

[0353] Aspect 10: According to the method of aspect 9, wherein the first CLI measurement includes a first value of the CLI metric, and the second CLI measurement includes a second value of the CLI metric, and the first value is associated with a TTI of the first type, and the second value is associated with a TTI of the second type.

[0354] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first type of TTI includes SBFDTTI type, non-SBFD TTI type, unaligned dynamic TDD TTI type, aligned dynamic TDD TTI type or non-SBFD unaligned dynamic TDD TTI type.

[0355] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: generating the information indicating the CLI based on the one or more CLI reference signals.

[0356] Aspect 13: The method according to any one of Aspects 1 to 12, wherein receiving the control information includes: receiving the control information via a CLI report configuration message or a CSI report configuration message.

[0357] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the control information indicates a minimum number of TTIs between a report TTI and a reference TTI in which the report is to be sent, and the minimum number of TTIs includes any type of TTI.

[0358] Aspect 15: The method according to any one of Aspects 1 to 13, wherein the control information indicates a minimum number of TTIs between a report TTI and a reference TTI in which the report is to be sent, the minimum number of TTIs including only the first type of TTIs.

[0359] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the first type of TTI includes a type of time slot or a type of symbol.

[0360] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the first network entity includes a UE, the one or more CLI reference signals include UE-to-UE CLI reference signals, and the information indicating CLI includes information indicating UE-to-UE CLI.

[0361] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the first parameter information is used to report the CLI associated with the half-duplex operation mode at the first network entity.

[0362] Aspect 19: The method according to any one of Aspects 1 to 17, wherein receiving the control information includes: receiving the control information from a second network entity, wherein the first parameter information is used to report a CLI associated with a full-duplex operation mode at the second network entity.

[0363] Aspect 20: The method according to any one of Aspects 1 to 17, wherein receiving the control information includes: receiving the control information from a second network entity, wherein the first parameter information is used to report a CLI associated with an SBFD operation mode at the second network entity.

[0364] Aspect 21: The method according to any one of Aspects 1 to 17, wherein receiving the control information comprises: receiving the control information from a second network entity, wherein the first parameter information is used to report a CLI associated with a half-duplex operation mode at the second network entity and having an unaligned TTI format.

[0365] Aspect 22: The method according to any one of aspects 1 to 21, wherein the parameter information includes information indicating at least one parameter for measuring or reporting CLI.

[0366] Aspect 23: According to the method of aspect 22, the at least one parameter includes the type of CLI metric to be reported, one or more resources for measuring CLI, or one or more resources for reporting CLI.

[0367] Aspect 24: The method according to any one of Aspects 22 to 23, wherein the type of CLI metric includes an RSRP metric type or an RSSI metric type.

[0368] Aspect 25: The method according to any one of Aspects 1 to 24, wherein the control information includes an indication of the first parameter information for a TTI of the first type.

[0369] Aspect 26: A method of wireless communication performed by a first network entity, the method comprising: receiving control information indicating resource allocation information for measuring CLI; receiving one or more CLI reference signals via one or more CLI resources according to the resource allocation information, wherein the one or more CLI resources are within one or more subbands in a set of discontinuous subbands allocated for downlink communication; and transmitting a report including information indicating CLI, wherein the information indicating CLI is associated with the one or more CLI reference signals.

[0370] Aspect 27: According to the method of aspect 26, wherein the one or more CLI resources include CLI resources within a subband of the set of discontinuous subbands allocated for downlink communication.

[0371] Aspect 28: According to the method of aspect 26, wherein the one or more CLI resources comprise two CLI resources, and each of the two CLI resources is within a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0372] Aspect 29: According to the method of aspect 26, wherein the one or more CLI resources include CLI resources in at least two subbands of the set of non-contiguous subbands allocated for downlink communication.

[0373] Aspect 30: The method according to aspect 29, wherein the resource allocation information includes a bitmap indicating the distribution of the CLI resources across the set of non-contiguous subbands.

[0374] Aspect 31: The method according to aspect 29, wherein the resource allocation information indicates a plurality of resource block sets including the CLI resources, and each of the plurality of resource block sets is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0375] Aspect 32: The method according to any one of Aspects 26 to 31, wherein the one or more CLI resources include CLI resources within the set of discontinuous subbands allocated for downlink communication, and wherein the method further comprises: measuring CLI within a portion of the CLI resources, wherein the portion is based on semi-static configuration information for SBFD operation, wherein the semi-static configuration information is for subbands allocated for uplink communication and one or more subbands in the set of discontinuous subbands allocated for downlink communication, or the semi-static configuration information is for subbands allocated for uplink communication and one or more guard bands, and wherein the information indicates the measured CLI.

[0376] Aspect 33: According to the method of aspect 32, the method further includes: receiving second control information, the second control information indicating the frequency position of the sub-band allocated for uplink communication or the corresponding frequency position of the one or more guard bands.

[0377] Aspect 34: The method according to any one of Aspects 26 to 33, wherein the resource allocation information indicates two CLI resource sets including the one or more CLI resources, and each CLI resource set in the two CLI resource sets is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0378] Aspect 35: The method according to any one of Aspects 26 to 33, wherein the resource allocation information indicates a CLI resource set including the one or more CLI resources, and the CLI resource set is associated with the set of discontinuous subbands allocated for downlink communication.

[0379] Aspect 36: According to the method of aspect 35, the resource allocation information includes a bitmap indicating the one or more CLI resources.

[0380] Aspect 37: According to the method of aspect 35, wherein the resource allocation information indicates one or more resource block sets within the CLI resource set, the one or more resource block sets including the one or more CLI resources, and each resource block set is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0381] Aspect 38: The method according to any one of Aspects 35 to 37, the method further comprising: measuring CLIs within one or more resource block sets within the CLI resource set, wherein the one or more resource block sets include the one or more CLI resources, wherein the one or more resource block sets are based on semi-static configuration information for SBFD operation, wherein the semi-static configuration information is used to allocate one or more subbands from the set of discontinuous subbands for uplink communication and for downlink communication, or the semi-static configuration information is used to allocate the subbands for uplink communication and one or more guard bands, and wherein the information indicates the measured CLIs.

[0382] Aspect 39: The method according to any one of Aspects 26 to 38, wherein the set of discontinuous subbands allocated for downlink communication is within the TTI of the SBFD operation allocated for the second network entity.

[0383] Aspect 40: The method according to aspect 39, wherein the first network entity includes a UE and the second network entity includes a base station.

[0384] Aspect 41: According to the method of aspect 40, wherein the one or more CLI reference signals include UE-to-UE CLI reference signals, and the resource allocation information is used to measure UE-to-UE CLI.

[0385] Aspect 42: The method according to any one of Aspects 26 to 41, wherein the resource allocation information is used to measure the CLI associated with the half-duplex operation mode at the first network entity.

[0386] Aspect 43: The method according to any one of Aspects 26 to 41, wherein receiving the control information comprises: receiving the control information from a second network entity, wherein the resource allocation information is used to measure the CLI associated with a full-duplex operation mode at the second network entity.

[0387] Aspect 44: The method according to any one of Aspects 26 to 41, wherein receiving the control information comprises: receiving the control information from a second network entity, wherein the resource allocation information is used to measure the CLI associated with the SBFD operating mode at the second network entity.

[0388] Aspect 45: The method according to any one of Aspects 26 to 41, wherein receiving the control information comprises: receiving the control information from a second network entity, wherein the resource allocation information is used to measure the CLI associated with a half-duplex operation mode having an unaligned TTI format at the second network entity.

[0389] Aspect 46: A method of wireless communication performed by a first network entity, the method comprising: outputting control information indicating parameter information for reporting CLI, wherein the parameter information includes first parameter information for reporting CLI, and wherein the first parameter information is associated with a first type of TTI in the control information; and obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources within one or more TTIs of the first type of TTI.

[0390] Aspect 47: According to the method of aspect 46, the parameter information includes second parameter information for reporting CLI, the second parameter information being associated with a second type of TTI in the control information, and the second type of TTI being different from the first type of TTI.

[0391] Aspect 48: The method according to aspect 47, wherein the control information indicates a first set of CLI resources associated with the first type of TTI and a second set of CLI resources associated with the second type of TTI.

[0392] Aspect 49: The method according to aspect 48, wherein the first set of CLI resources includes the one or more CLI resources.

[0393] Aspect 50: The method according to any one of aspects 47 to 49, wherein the information indicating the CLI is associated only with the first type of TTI.

[0394] Aspect 51: The method according to aspect 50 further includes: obtaining a second report including second information indicating CLI, wherein the second information indicating CLI is associated only with a second or more CLI resources within one or more TTIs of the second type of TTI.

[0395] Aspect 52: The method according to any one of aspects 47 to 49, wherein the information indicating the CLI is associated with both the first type of TTI and the second type of TTI.

[0396] Aspect 53: According to the method of aspect 52, the information indicating the CLI includes first information associated with the first type of TTI and second information associated with the second type of TTI.

[0397] Aspect 54: The method according to aspect 53, wherein the first information includes a first CLI measurement value indicated as associated with the first type of TTI, and the second information includes a second CLI measurement value indicated as associated with the second type of TTI.

[0398] Aspect 55: The method according to aspect 54, wherein the first CLI measurement includes a first value of the CLI metric, and the second CLI measurement includes a second value of the CLI metric, and the first value is associated with a TTI of the first type, and the second value is associated with a TTI of the second type.

[0399] Aspect 56: The method according to any one of Aspects 46 to 55, wherein the first type of TTI includes SBFDTTI type, non-SBFD TTI type, unaligned dynamic TDD TTI type, aligned dynamic TDD TTI type or non-SBFD unaligned dynamic TDD TTI type.

[0400] Aspect 57: The method according to any one of Aspects 46 to 56, wherein the first type of TTI includes a type of time slot or a type of symbol.

[0401] Aspect 58: The method according to any one of Aspects 46 to 57, wherein outputting the control information includes: outputting the control information via a CLI report configuration message or a CSI report configuration message.

[0402] Aspect 59: The method according to any one of Aspects 46 to 58, wherein the control information indicates a minimum number of TTIs between a report TTI and a reference TTI in which the report is to be sent, and the minimum number of TTIs includes any type of TTI.

[0403] Aspect 60: The method according to any one of Aspects 46 to 58, wherein the control information indicates a minimum number of TTIs between a report TTI and a reference TTI in which the report is to be sent, the minimum number of TTIs including only the first type of TTIs.

[0404] Aspect 61: The method according to any one of aspects 46 to 60, wherein the first type of TTI includes a type of time slot or a type of symbol.

[0405] Aspect 62: The method according to any one of aspects 46 to 61, wherein the information instructing the CLI includes information instructing the UE to the UE CLI.

[0406] Aspect 63: The method according to any one of Aspects 46 to 62, wherein outputting the control information comprises: outputting the control information to a second network entity, wherein the first parameter information is used to report a CLI associated with a half-duplex operation mode at the second network entity.

[0407] Aspect 64: The method according to any one of Aspects 46 to 62, wherein the first parameter information is used to report the CLI associated with the full-duplex operation mode at the first network entity.

[0408] Aspect 65: The method according to any one of Aspects 46 to 62, wherein the first parameter information is used to report the CLI associated with the SBFD operation mode at the first network entity.

[0409] Aspect 66: The method according to any one of Aspects 46 to 62, wherein the first parameter information is used to report the CLI associated with a half-duplex operation mode at the first network entity and having an unaligned TTI format.

[0410] Aspect 67: The method according to any one of Aspects 46 to 66, wherein outputting the control information comprises: outputting the control information to a second network entity, wherein the first parameter information indicates at least one parameter for measuring or reporting CLI.

[0411] Aspect 68: According to the method of aspect 67, the at least one parameter includes the type of CLI metric to be reported, one or more resources for measuring CLI, or one or more resources for reporting CLI.

[0412] Aspect 69: The method according to any one of Aspects 67 to 68, wherein the type of CLI metric includes an RSRP metric type or an RSSI metric type.

[0413] Aspect 70: The method according to any one of Aspects 46 to 69, wherein the control information includes an indication of the first parameter information for a TTI of the first type.

[0414] Aspect 71: A method of wireless communication performed by a first network entity, the method comprising: outputting control information indicating resource allocation information for measuring CLI; and obtaining a report including information indicating CLI, wherein the information indicating CLI is associated with one or more CLI resources according to the resource allocation information, and wherein the one or more CLI resources are within one or more subbands in a set of non-contiguous subbands allocated for downlink communication.

[0415] Aspect 72: According to the method of aspect 71, wherein the one or more CLI resources include CLI resources within a subband of the set of discontinuous subbands allocated for downlink communication.

[0416] Aspect 73: According to the method of aspect 71, wherein the one or more CLI resources comprise two CLI resources, and each of the two CLI resources is within a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0417] Aspect 74: According to the method of aspect 71, wherein the one or more CLI resources include CLI resources in at least two subbands of the set of non-contiguous subbands allocated for downlink communication.

[0418] Aspect 75: The method according to aspect 74, wherein the resource allocation information includes a bitmap indicating the distribution of the CLI resources across the set of non-contiguous subbands.

[0419] Aspect 76: According to the method of aspect 74, wherein the resource allocation information indicates a plurality of resource block sets including the CLI resources, and each of the plurality of resource block sets is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0420] Aspect 77: The method according to any one of Aspects 71 to 76, wherein the one or more CLI resources include CLI resources within the set of discontinuous subbands allocated for downlink communication, and the information indicates a CLI measured within a portion of semi-static configuration information for SBFD operation of the CLI resources, the semi-static configuration information being used for subbands allocated for uplink communication and one or more subbands in the set of discontinuous subbands allocated for downlink communication, or the semi-static configuration information being used for subbands allocated for uplink communication and one or more guard bands.

[0421] Aspect 78: According to the method of aspect 77, the method further includes: outputting second control information, the second control information indicating the frequency position of the sub-band allocated for uplink communication or the corresponding frequency position of the one or more guard bands.

[0422] Aspect 79: The method according to any one of Aspects 71 to 78, wherein the resource allocation information indicates two CLI resource sets including the one or more CLI resources, and each CLI resource set in the two CLI resource sets is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0423] Aspect 80: The method according to any one of Aspects 71 to 78, wherein the resource allocation information indicates a CLI resource set including the one or more CLI resources, and the CLI resource set is associated with the set of discontinuous subbands allocated for downlink communication.

[0424] Aspect 81: According to the method of aspect 80, the resource allocation information includes a bitmap indicating the one or more CLI resources.

[0425] Aspect 82: According to the method of aspect 80, wherein the resource allocation information indicates one or more resource block sets within the CLI resource set, the one or more resource block sets including the one or more CLI resources, and each resource block set is associated with a corresponding subband in the set of discontinuous subbands allocated for downlink communication.

[0426] Aspect 83: The method according to any one of Aspects 80 to 82, wherein the information indicates a CLI measured within one or more resource block sets within the CLI resource set, the one or more resource block sets comprising the one or more CLI resources, and the one or more resource block sets are based on semi-static configuration information for SBFD operation, the semi-static configuration information being used to allocate one or more subbands from the set of discontinuous subbands for uplink communication and allocated for downlink communication, or the semi-static configuration information being used to allocate the subbands for uplink communication and one or more guard bands.

[0427] Aspect 84: The method according to any one of aspects 71 to 83, wherein the set of discontinuous subbands allocated for downlink communication is within the TTI of the SBFD operation allocated for the first network entity.

[0428] Aspect 85: The method according to any one of Aspects 71 to 84, wherein the first network entity includes a base station.

[0429] Aspect 86: The method according to any one of Aspects 71 to 85, wherein outputting the control information comprises: outputting the control information to a second network entity including a UE, wherein the resource allocation information is used to measure UE to UE CLI.

[0430] Aspect 87: The method according to any one of Aspects 71 to 86, wherein outputting the control information comprises: outputting the control information to a second network entity, wherein the resource allocation information is used to measure the CLI associated with a half-duplex operation mode at the second network entity.

[0431] Aspect 88: The method according to any one of Aspects 71 to 86, wherein the resource allocation information is used to measure the CLI associated with the full-duplex operation mode at the first network entity.

[0432] Aspect 89: The method according to any one of Aspects 71 to 86, wherein the resource allocation information is used to measure the CLI associated with the SBFD operation mode at the first network entity.

[0433] Aspect 90: The method according to any one of Aspects 71 to 86, wherein the resource allocation information is used to measure the CLI associated with a half-duplex operation mode at the first network entity and having an unaligned TTI format.

[0434] Aspect 91: A first network entity for wireless communication, the first network entity comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to perform a method according to any one of aspects 1 to 25.

[0435] Aspect 92: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 1 to 25.

[0436] Aspect 93: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the first network entity to perform the method according to any one of aspects 1 to 25 when executed by the first network entity.

[0437] Aspect 94: A first network entity for wireless communication, the first network entity comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to perform a method according to any one of aspects 26 to 45.

[0438] Aspect 95: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 26 to 45.

[0439] Aspect 96: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the first network entity to perform the method according to any one of aspects 26 to 45 when executed by the first network entity.

[0440] Aspect 97: A first network entity for wireless communication, the first network entity comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to perform a method according to any one of aspects 46 to 70.

[0441] Aspect 98: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 46 to 70.

[0442] Aspect 99: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the first network entity to perform the method according to any one of aspects 46 to 70 when executed by the first network entity.

[0443] Aspect 100: A first network entity for wireless communication, the first network entity comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to perform a method according to any one of aspects 71 to 90.

[0444] Aspect 101: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 71 to 90.

[0445] Aspect 102: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the first network entity to perform the method according to any one of aspects 71 to 90 when executed by the first network entity.

[0446] The methods described herein outline possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0447] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0448] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0449] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0450] The functionality described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.

[0451] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0452] As used herein, the term "or" is inclusive unless restrictive language is used relative to the listed alternatives. For example, a reference to "X is based on A or B" should be interpreted as including, within its scope, X is based on A, X is based on B, and X is based on both A and B. In this respect, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B," because "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be interpreted as including, within its scope, X is based on A, X is based on B, X is based on C, X is based on both A and B, X is based on both A and C, X is based on both B and C, and X is based on both A, B, and C. In this respect, a reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C," because "or" is inclusive. As an example of restrictive language, the reference to "X is based on either A or B" should be interpreted as including, within its scope, both X based on A and X based on B, but excluding X based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based on at least A," unless specifically stated differently. Similarly, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be understood in the same way as "one or more" or "at least one."

[0453] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0454] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0455] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0456] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all examples that can be implemented or that are within the scope of the claims. The terms "aspect" or "example" as used herein mean "serving as an aspect, example, instance, or illustration," and not "preferred" or "advantageous over other aspects." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0457] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network entity for wireless communication, the first network entity comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to: receive control information indicating parameter information for reporting cross-link interference, wherein the parameter information includes first parameter information for reporting cross-link interference, and wherein the first parameter information is associated with a first type of transmission time interval in the control information; receive one or more cross-link interference reference signals during one or more transmission time intervals of the first type of transmission time interval; and transmit a report including information indicating cross-link interference, wherein the information indicating the cross-link interference is associated with the one or more cross-link interference reference signals.

2. The first network entity of claim 1, wherein the parameter information includes second parameter information for reporting cross-link interference, wherein the second parameter information is associated with a second type of transmission time interval in the control information, and wherein the second type of transmission time interval is different than the first type of transmission time interval.

3. The first network entity of claim 2, wherein the control information indicates a first set of cross-link interference resources associated with the first type of transmission time interval and a second set of cross-link interference resources associated with the second type of transmission time interval.

4. The first network entity of claim 3, wherein the one or more cross-link interference reference signals are received during at least one cross-link interference reference signal of the first set of cross-link interference resources.

5. The first network entity of claim 2, wherein the information indicating the cross-link interference is associated with only the first type of transmission time interval.

6. The first network entity of claim 5, wherein the first network entity is configured to: receive a second one or more cross-link interference reference signals during one or more transmission time intervals of the second type of transmission time interval; and transmit a second report including second information indicating cross-link interference, wherein the second information indicating the cross-link interference is associated with only the second one or more cross-link interference reference signals.

7. The first network entity of claim 2, wherein the information indicating the cross-link interference is associated with both the first type of transmission time interval and the second type of transmission time interval.

8. The first network entity of claim 7, wherein the first network entity is configured to: refrain from averaging cross-link interference measurements across different transmission time interval types, and wherein the information indicating the cross-link interference includes first information associated with the first type of transmission time interval and second information associated with the second type of transmission time interval based on the refraining.

9. The first network entity of claim 8, wherein the first information comprises a first cross-link interference measurement value indicated as being associated with the first type of transmission time interval, and wherein the second information comprises a second cross-link interference measurement value indicated as being associated with the second type of transmission time interval.

10. The first network entity of claim 9, wherein a first cross-link interference measurement value comprises a first value of a cross-link interference metric, and the second cross-link interference measurement value comprises a second value of the cross-link interference metric, and wherein the first value is associated with the first type of transmission time interval and the second value is associated with the second type of transmission time interval.

11. The first network entity of claim 1, wherein the first type of transmission time interval comprises a sub-band full duplex transmission time interval type, a non-sub-band full duplex transmission time interval type, an unaligned dynamic time division duplex transmission time interval type, an aligned dynamic time division duplex transmission time interval type, or a non-sub-band full duplex unaligned dynamic time division duplex transmission time interval type.

12. The first network entity of claim 1, wherein the first network entity is configured to: generate the information indicating the cross-link interference based on the one or more cross-link interference reference signals.

13. The first network entity of claim 1, wherein to receive the control information, the first network entity is configured to: receive the control information via a cross-link interference report configuration message or a channel state information report configuration message.

14. The first network entity of claim 1, wherein the control information indicates a minimum number of transmission time intervals between a reporting transmission time interval in which the report is to be transmitted and a reference transmission time interval, and wherein the minimum number of transmission time intervals comprises any type of transmission time interval.

15. The first network entity of claim 1, wherein the control information indicates a minimum number of transmission time intervals between a reporting transmission time interval in which the report is to be transmitted and a reference transmission time interval, wherein the minimum number of transmission time intervals comprises only the first type of transmission time interval.

16. The first network entity of claim 1, wherein the first type of transmission time interval comprises one type of slot or one type of symbol.

17. The first network entity of claim 1, wherein the first network entity comprises a user equipment (UE), wherein the one or more cross-link interference reference signals comprise a UE-to-UE cross-link interference reference signal, and wherein the information indicating cross-link interference comprises information indicating UE-to-UE cross-link interference.

18. The first network entity of claim 1, wherein the first parameter information is for reporting cross-link interference associated with a half duplex mode of operation at the first network entity.

19. The first network entity of claim 1, wherein to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the first parameter information is for reporting cross-link interference associated with a full duplex mode of operation at the second network entity.

20. The first network entity of claim 1, wherein to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the first parameter information is for reporting cross-link interference associated with a sub-band full duplex mode of operation at the second network entity.

21. The first network entity of claim 1, wherein to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the first parameter information is for reporting cross-link interference associated with a half duplex mode of operation at the second network entity and having a misaligned transmission time interval format.

22. The first network entity of claim 1, wherein the parameter information comprises information indicating at least one parameter for measuring or reporting cross-link interference.

23. The first network entity of claim 22, wherein the at least one parameter comprises a type of cross-link interference metric to report, one or more resources for measuring cross-link interference, or one or more resources for reporting cross-link interference.

24. The first network entity of claim 22, wherein the type of cross-link interference metric comprises a reference signal received power metric type or a received signal strength indicator metric type.

25. The first network entity of claim 1, wherein the control information comprises an indication of a transmission time interval for which the first parameter information is applicable.

26. A first network entity for wireless communication, comprising: at least one communication interface; and at least one processor coupled to the at least one communication interface, wherein the first network entity is configured to: receive control information indicating resource allocation information for measuring cross-link interference; receive, in accordance with the resource allocation information, one or more cross-link interference reference signals via one or more cross-link interference resources, wherein the one or more cross-link interference resources are within one or more sub-bands of a set of non-contiguous sub-bands allocated for downlink communications; and transmit a report comprising information indicating cross-link interference, wherein the information indicating the cross-link interference is associated with the one or more cross-link interference reference signals.

27. The first network entity of claim 26, wherein the one or more cross-link interference resources comprise a cross-link interference resource within one sub-band of the set of non-contiguous sub-bands allocated for downlink communications.

28. The first network entity of claim 26, wherein the one or more cross-link interference resources comprise two cross-link interference resources, and wherein each of the two cross-link interference resources is within a respective sub-band of the set of non-contiguous sub-bands allocated for downlink communications.

29. The first network entity of claim 26, wherein the one or more cross-link interference resources comprise a cross-link interference resource within at least two sub-bands of the set of non-contiguous sub-bands allocated for downlink communications.

30. The first network entity of claim 29, wherein the resource allocation information comprises a bitmap indicating a distribution of the cross-link interference resource across the set of non-contiguous sub-bands.

31. The first network entity of claim 29, wherein the resource allocation information indicates a plurality of sets of resource blocks comprising the cross-link interference resource, and wherein each set of resource blocks of the plurality of sets of resource blocks is associated with a respective sub-band of the set of non-contiguous sub-bands allocated for downlink communications.

32. The first network entity of claim 26, wherein the one or more cross-link interference resources comprise a cross-link interference resource within the set of non-contiguous sub-bands allocated for downlink communications, and wherein the first network entity is configured to: measure cross-link interference within a portion of the cross-link interference resource, wherein the portion is based on semi-static configuration information for sub-band full duplex operation, wherein the semi-static configuration information is for a sub-band allocated for uplink communications and one or more sub-bands of the set of non-contiguous sub-bands allocated for downlink communications, or the semi-static configuration information is for the sub-band allocated for uplink communications and one or more guard bands, and wherein the information indicates the measured cross-link interference.

33. The first network entity of claim 32, wherein the first network entity is configured to: receive second control information indicating a frequency location of the sub-band allocated for uplink communications or a respective frequency location of the one or more guard bands.

34. The first network entity of claim 26, wherein the resource allocation information indicates two sets of cross-link interference resources comprising the one or more cross-link interference resources, and wherein each set of cross-link interference resources of the two sets of cross-link interference resources is associated with a respective sub-band of the set of non-contiguous sub-bands allocated for downlink communications.

35. The first network entity of claim 26, wherein the resource allocation information indicates a set of cross-link interference resources comprising the one or more cross-link interference resources, and wherein the set of cross-link interference resources is associated with the set of non-contiguous sub-bands allocated for downlink communications.

36. The first network entity of claim 35, wherein the resource allocation information comprises a bitmap indicating the one or more cross-link interference resources.

37. The first network entity of claim 35, wherein the resource allocation information indicates one or more sets of resource blocks within the set of cross-link interference resources, wherein the one or more sets of resource blocks include the one or more cross-link interference resources, and wherein each set of resource blocks is associated with a respective sub-band of the set of non-consecutive sub-bands allocated for downlink communication.

38. The first network entity of claim 35, wherein the first network entity is configured to: measure cross-link interference within one or more sets of resource blocks within the set of cross-link interference resources, wherein the one or more sets of resource blocks include the one or more cross-link interference resources, wherein the one or more sets of resource blocks are based on semi-static configuration information for sub-band full duplex operation, wherein the semi-static configuration information is for one or more of a sub-band allocated for uplink communication and the set of non-consecutive sub-bands allocated for downlink communication, or the semi-static configuration information is for the sub-band allocated for uplink communication and one or more guard bands, and wherein the information indicates the measured cross-link interference.

39. The first network entity of claim 26, wherein the set of non-consecutive sub-bands allocated for downlink communication is within a transmission time interval allocated for sub-band full duplex operation at a second network entity.

40. The first network entity of claim 39, wherein the first network entity comprises a user equipment (UE) and the second network entity comprises a base station.

41. The first network entity of claim 40, wherein the one or more cross-link interference reference signals comprise a UE-to-UE cross-link interference reference signal, and wherein the resource allocation information is for measuring UE-to-UE cross-link interference.

42. The first network entity of claim 26, wherein the resource allocation information is for measuring cross-link interference associated with a half duplex mode of operation at the first network entity.

43. The first network entity of claim 26, wherein to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the resource allocation information is for measuring cross-link interference associated with a full duplex mode of operation at the second network entity.

44. The first network entity of claim 26, wherein to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the resource allocation information is for measuring cross-link interference associated with a sub-band full duplex mode of operation at the second network entity.

45. The first network entity of claim 26, wherein, to receive the control information, the first network entity is configured to receive the control information from a second network entity, and wherein the resource allocation information is for measuring cross-link interference associated with a half duplex mode of operation at the second network entity and having unaligned transmission time interval formats.

Images