Techniques for interference handling in dynamic time division duplex operations

Abstract

Aspects of the present disclosure relate to interference handling in dynamic time division duplex operations. An apparatus (400) includes at least one memory (404) and at least one processor (402) coupled to the at least one memory (404) and configured to cause the apparatus (400) to: receive a cross-link interference (CLI) measurement configuration including at least one CLI resource, where a CLI resource of the at least one CLI resource is configured with a dynamic indication, a dynamic indication of the CLI resource for the at least one CLI resource is monitored, and a measurement is performed on the CLI resource in response to the dynamic indication indicating that the CLI resource is available for the measurement.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to interference handling in dynamic time division duplex operations. Background Art

[0002] A wireless communication system may include one or more network communication devices, such as a base station, which may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)). Summary of the invention

[0003] The article "a" before an element is not limited and is understood to refer to "at least one" of these elements or "one or more" of these elements. The terms "one", "at least one", "one or more" and "at least one of one or more" are interchangeable. As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more" or "one or two") indicates a list of inclusions, so that, for example, a list of at least one of A, B or C represents A or B or C or AB or AC or BC or ABC (i.e. A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, the example steps described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0004] Some implementations of the methods and apparatus described herein may also include at least one memory and at least one processor coupled to the at least one memory. The at least one processor may be configured to cause the UE to: receive a cross-link interference (CLI) measurement configuration including at least one CLI resource, wherein the CLI resource of the at least one CLI resource is configured with a dynamic indication, monitor the dynamic indication of the CLI resource for the at least one CLI resource, and in response to the dynamic indication indicating that the CLI resource is available for measurement, perform measurement on the CLI resource.

[0005] In some implementations of the methods and apparatus described herein, at least one processor is coupled to at least one memory to cause a base station to: send a CLI measurement configuration to a UE, the CLI measurement configuration comprising at least one CLI resource, wherein a CLI resource of the at least one CLI resource is configured with a dynamic indication of validity of a CLI measurement occasion of the CLI resource, determine validity of the CLI measurement occasion of the CLI resource, and send the dynamic indication of validity of the CLI measurement occasion of the CLI resource to the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 An example of a wireless communication system according to aspects of the present disclosure is shown.

[0007] Figure 2 Example time division duplex (TDD) uplink (UL) / downlink (DL) configurations for three neighboring cells are shown in accordance with aspects of the present disclosure.

[0008] Figure 3 An example radio resource control (RRC) information element is shown for configuring a CLI measurement resource list according to aspects of the present disclosure.

[0009] Figure 4 An example of a UE 400 according to aspects of the present disclosure is shown.

[0010] Figure 5 An example of a processor 500 according to aspects of the present disclosure is shown.

[0011] Figure 6 An example of a network equipment (NE) 600 according to aspects of the present disclosure is shown.

[0012] Figure 7 A flow chart of a method performed by a UE according to aspects of the present disclosure is shown.

[0013] Figure 8 A flow chart of a method performed by a NE according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0014] In general, the present disclosure describes systems, methods, and devices for interference handling in dynamic time division duplex operation. In some embodiments, the method can be performed using computer code embedded on a computer readable medium. In some embodiments, the device or system may include a computer readable medium containing computer readable code, which, when executed by a processor, causes the device or system to perform at least a portion of the following solution.

[0015] In Release 16 of the 3rd Generation Partnership Project (3GPP) New Radio (NR), two types of CLI measurements are specified, Sounding Reference Signal (SRS) Reference Signal Received Power (SRS-RSRP) and CLI Reference Signal Strength Indicator (CLI-RSSI). According to 3GPP TS 38.215 (incorporated herein by reference), SRS-RSRP is defined as the linear average of the power contribution (in watts) of the resource units carrying the SRS. SRS-RSRP can be measured for the configured resource units within the considered measurement frequency bandwidth at the configured measurement time occasion. CLI-RSSI is defined as the linear average of the total received power (in watts) observed in the configured orthogonal frequency division multiplexing (OFDM) symbols of (multiple) configured measurement time resources, in the configured measurement bandwidth, from all sources, including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. For frequency range 1, the reference point for measurement should be the antenna connector of the UE. For frequency range 2, the measurement can be made based on the combined signal from the antenna elements corresponding to a given receiver branch. For frequency ranges 1 and 2, if receiver diversity is used by the UE, the reported measurement value shall not be lower than the corresponding measurement value of any single receiver branch.

[0016] In Release 16 of 3GPP NR, the SRS resources configured for SRS-RSRP measurement for CLI in a DL bandwidth part (BWP) include the same subcarrier spacing as the subcarrier spacing of the DL BWP. The UE is not expected to measure SRS-RSRP using SRS-RSRP measurement resources that are not completely confined within the DL BWP. The UE is not expected to measure more than 32 SRS resources, and the UE is not expected to receive more than 8 SRS resources in one slot.

[0017] In unpaired spectrum TDD, splitting radio resources between downlink and uplink in the time domain has been used to avoid interference (e.g., uplink and downlink interference within a network entity and intra-cell UE-to-UE interference). However, when different TDD DL and UL modes are used between neighboring cells, UL transmission in one cell may interfere with DL reception in another cell, which is called UE-to-UE CLI.

[0018] In 3GPP NR, DL and UL are allowed to be time-independent via downlink control information (DCI) signaling (i.e., dynamic TDD) to reduce latency and efficiently use radio resources in unpaired spectrum. In order to fully utilize the dynamic TDD feature in NR, effective interference management that considers dynamically changing interference levels may be necessary.

[0019] When cells in an unpaired spectrum operate using flexible symbols that are semi-statically configured, the presence and level of cross-link interference may depend on the dynamic use of the semi-statically configured flexible symbols. In one embodiment, the UE receives a CLI measurement configuration, wherein the CLI measurement configuration semi-statically configures potential one or more CLI measurement opportunities (e.g., multiple CLI measurement time slots) within a CLI measurement period. In addition, the UE receives a dynamic indication for a valid CLI measurement opportunity from one or more potential CLI measurement opportunities configured semi-statically, where the UE needs to perform measurements. The network entity determines and indicates the validity of the configured CLI measurement opportunity based on the dynamic use of the semi-statically configured flexible symbols within the configured CLI measurement opportunity. In one example, the validity of the configured CLI measurement opportunity is determined based on information about time domain resource utilization of neighboring cells. In another example, the network entity receives information about time domain resource utilization of neighboring cells from another network entity.

[0020] In NR Release 16, the UE assumes that CLI measurement resources are always valid / available and is expected to perform CLI measurements for all configured measurement occasions. When the communication direction of the flexible symbols changes dynamically and thus the presence of the dominant CLI changes dynamically, the UE may not be able to accurately measure the CLI level based on the semi-statically configured CLI measurement occasions.

[0021] However, in the proposed solution described herein, UE measurements can accurately reflect CLI levels even with dynamic TDD operation, because the UE can perform CLI measurements only when CLI exists based on dynamic indications from network entities. The present disclosure proposes a method for handling dynamic cross-link interference to improve TDD UL / DL configuration flexibility in unpaired spectrum.

[0022] Aspects of the disclosure are described in the context of wireless communication systems.

[0023] Figure 1An example of a wireless communication system 100 according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, an advanced 5G (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0024] One or more NEs 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more NEs 102 described herein may be or include or may be referred to as network nodes, base stations, network elements, network functions, network entities, radio access networks (RAN), NodeBs, eNodeBs (eNBs), next generation NodeBs (gNBs), or other suitable terms. NE 102 and UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NE 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0025] NE 102 can provide a geographic coverage area, and NE 102 can support services for one or more UE 104 within the geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NE 102.

[0026] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples.

[0027] The UE 104 may be able to directly support wireless communications with other UEs 104 via a communication link. For example, the UE 104 may directly support wireless communications with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a side link. For example, the UE 104 may directly support wireless communications with another UE 104 via a PC5 interface.

[0028] NE 102 can support communication with CN 106 or another NE 102 or both. For example, NE 102 can interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2 or network interface). In some implementations, NE 102 can communicate directly with each other. In some other implementations, NE 102 can communicate with each other or communicate indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). ANCs may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).

[0029] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0030] The CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N2 or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the CN 106 via the NE 102. The CN 106 may use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server. A PDU session may be an example of a logical connection between a UE 104 and a CN 106 (e.g., one or more network functions of the CN 106).

[0031] In the wireless communication system 100, the NE 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the NE 102 and the UE 104 may support different resource structures. For example, the NE 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the NE 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NE 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The NE 102 and the UE 104 may support various frame structures based on one or more parameter sets.

[0032] One or more parameter sets may be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, a first parameter set (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0033] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0034] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may use a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the normal cyclic prefix and the extended cyclic prefix may depend on the parameter set. It should be understood that references to a first parameter set (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0035] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc. based on frequency or wavelength. By way of example, the wireless communication system 100 can support one or more operating frequency bands, such as the frequency range designations FR1 (410 MHz–7.125 GHz), FR2 (24.25 GHz–52.6 GHz), FR3 (7.125 GHz–24.25 GHz), FR4 (52.6 GHz–114.25 GHz), FR4a or FR4-1 (52.6 GHz–71 GHz), and FR5 (114.25 GHz–300 GHz). In some implementations, the NE 102 and the UE 104 can perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 can be used by the NE 102 and the UE 104 and other devices or apparatuses for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by the NE 102 and the UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0036] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set (e.g., μ=0), the first parameter set including 15kHz subcarrier spacing; a second parameter set (e.g., μ=1), the second parameter set including 30kHz subcarrier spacing; and a third parameter set (e.g., v=2), the third parameter set including 60kHz subcarrier spacing. FR2 may be associated with one or more parameter sets (e.g., at least 2 configuration parameters). For example, FR2 may be associated with a third parameter set (e.g., μ=2), the third parameter set including 60kHz subcarrier spacing; and a fourth configuration parameter (e.g., μ=3), the fourth configuration parameter including 120kHz subcarrier spacing.

[0037] Regarding timeslot configuration, according to TS 38.213, if the UE also provides tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-ConfigurationDedicated only covers each timeslot flexible symbol in the timeslot number provided by tdd-UL-DL-ConfigurationCommon.

[0038] tdd-UL-DL-ConfigurationDedicated provides a set of slot configurations for each slot configuration from the slot configuration set via slotSpecificConfigurationsToAddModList, a slot index for the slot via slotIndex, and a set of symbols for the slot via symbols, where if symbols=allDownlink, all symbols in the slot are downlink; if symbols=allUplink, all symbols in the slot are uplink; and / or if symbols=explicit, nrofDownlinkSymbols provides the number of downlink first symbols in the slot, and nrofUplinkSymbols provides the number of uplink last symbols in the slot. If nrofDownlinkSymbols is not provided, there is no downlink first symbol in the slot, and if nrofUplinkSymbols is not provided, there is no uplink last symbol in the slot. The remaining symbols in the slot are flexible.

[0039] If the UE is not configured to monitor the Physical Downlink Control Channel (PDCCH) of DCI format 2_0, for the symbol set of a time slot indicated as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE, if the UE receives a corresponding indication through the DCI format, the UE receives a Physical Downlink Shared Channel (PDSCH) or a Channel State Information Reference Signal (CSI-RS) in the symbol set of the time slot, and if the UE receives a corresponding indication through the DCI format, a Random Access Response (RAR) UL grant, a fallbackRAR UL grant, or a successRAR, the UE sends a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or SRS in the symbol set of the time slot.

[0040] For symbol sets indicated to the UE as flexible timeslots by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), the UE does not expect to receive dedicated higher layer parameters transmitted from the UE in the symbol set of the configured timeslots and received by the UE in the symbol set of the configured timeslots.

[0041] With respect to the process used by the UE to determine the slot format, the Slot Format Indicator (SFI)-Index field value in DCI format 2_0 indicates to the UE the slot format used for each of a plurality of slots for each DL BWP or each UL BWP starting from the slot in which the UE detects DCI format 2_0. The number of slots is equal to or greater than the PDCCH monitoring period for DCI format 2_0. The SFI-index field includes bits, where maxSFIindex is the maximum of the values ​​provided by the corresponding slotFormatCombinationId. The slot formats are identified by the corresponding format index as provided in Table 11.1.1-1, where "D" represents downlink symbols, "U" represents uplink symbols, and "F" represents flexible symbols.

[0042] For the symbol set of the timeslot indicated as downlink / uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE does not expect to detect DCI format 2_0, whose SFI-index field value correspondingly indicates that the symbol set of the timeslot is uplink / downlink or flexible link.

[0043] For a set of symbols indicated to the UE as a flexible time slot by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE and if the UE detects that DCI format 2_0 uses a time slot format value other than 255 to provide a format for the time slot.

[0044] If one or more symbols from the symbol set are symbols in the control resource set (CORESET) configured to the UE for PDCCH monitoring, the UE shall receive PDCCH in the CORESET only if the SFI-index field value in DCI format 2_0 indicates that the one or more symbols are downlink symbols.

[0045] If the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is flexible, and the UE detects a DCI format indicating that the UE receives PDSCH or CSI-RS in the symbol set of the time slot, the UE receives PDSCH or CSI-RS in the symbol set of the time slot.

[0046] If the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is flexible, and the UE detects a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, indicating that the UE sends PUSCH, PUCCH, PRACH, or SRS in the symbol set of the time slot, the UE sends PUSCH, PUCCH, PRACH, or SRS in the symbol set of the time slot.

[0047] If the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is flexible, and the UE does not detect a DCI format indicating that the UE receives PDSCH or CSI-RS, or the UE does not detect a DCI format indicating that the UE sends PUSCH, PUCCH, PRACH or SRS in the symbol set of the time slot, RAR UL, fallbackRAR UL grant or successRAR grant, the UE does not transmit or receive in the symbol set of the time slot.

[0048] If the UE is configured by higher layers to receive PDSCH or CSI-RS in the symbol set of a timeslot, the UE shall receive PDSCH or CSI-RS in the symbol set of the timeslot only if the SFI-index field value in DCI format 2_0 indicates that the symbol set of the timeslot is downlink and, if applicable, the symbol set is within the remaining channel occupancy duration.

[0049] If the UE is configured by higher layers to receive a DL Positioning Reference Signal (PRS) in the symbol set of a time slot, the UE shall receive the DL PRS in the symbol set of the time slot only if the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is downlink or flexible link.

[0050] If the UE is configured by a higher layer to send PUCCH, PUSCH or PRACH in the symbol set of a time slot, the UE shall send PUCCH, PUSCH or PRACH in the time slot only if the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is uplink.

[0051] If the UE is configured by higher layers to send SRS in a symbol set of a slot, the UE sends SRS only in a subset of symbols from the symbol set of the slot that are indicated as uplink symbols by the SFI-index field value in DCI format 2_0.

[0052] The UE does not expect to detect the SFI-index field value in DCI format 2_0 (indicating that the symbol set of the timeslot is downlink) and detect DCI format, RAR UL grant, fallbackRAR UL grant or successRAR (indicating that the UE sends SRS, PUSCH, PUCCH or PRACH in one or more symbols in the symbol set from the timeslot).

[0053] If the symbol set of a time slot includes any repeated symbols corresponding to PUSCH transmissions activated by a UL type 2 grant PDCCH (as described in clause 10.2), the UE does not expect to detect the SFI-index field value in DCI format 2_0 that indicates that the symbol set of the time slot is downlink or flexible.

[0054] The UE does not expect to detect an SFI-index field value in DCI format 2_0 indicating that the symbol set of the time slot is uplink, nor does it expect to detect a DCI format indicating that the UE receives PDSCH or CSI-RS in one or more symbols in the symbol set of the time slot.

[0055] If the UE is configured by higher layers to receive CSI-RS or PDSCH in the symbol set of a time slot, and the UE detects a DCI format 2_0 with a time slot format value other than 255, which DCI format 2_0 indicates a subset of symbols from the symbol set as the uplink or flexible time slot format, or the UE detects a DCI format indicating that the UE sends PUSCH, PUCCH, SRS or PRACH in at least one symbol in the symbol set, the UE cancels CSI-RS reception in the symbol set of the time slot or cancels PDSCH reception in the time slot.

[0056] For operation with shared spectrum channel access, if the UE is configured by higher layers to receive CSI-RS and the UE is provided with CO-DurationsPerCell, then for the symbol sets of time slots indicated as downlink or flexible by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided, the UE cancels CSI-RS reception in the symbol sets of time slots that are not within the remaining channel occupancy duration.

[0057] If the UE is configured by higher layers to receive DL PRS in a symbol set of a time slot, and the UE detects a DCI format 2_0 with a time slot format value other than 255 indicating that the time slot format has a subset of symbols from the symbol set as uplink, or the UE detects a DCI format indicating that the UE sends PUSCH, PUCCH, SRS or PRACH in at least one symbol in the symbol set, the UE cancels DL PRS reception in the symbol set of the time slot.

[0058] If the UE is configured by higher layers to transmit SRS, PUCCH, PUSCH or PRACH in a symbol set of a slot, and the UE detects a DCI format 2_0 with a slot format value other than 255 indicating that the slot format has a subset of symbols from the symbol set as downlink or flexible, or the UE detects a DCI format indicating that the UE receives CSI-RS or PDSCH in a subset of symbols from the symbol set, the UE is not expected to cancel transmissions in symbols from the symbol set occurring relative to the last symbol of the CORESET in which the UE detected DCI format 2_0 or DCI format within a PUSCH preparation time T that is less than the corresponding PUSCH processing capability. proc，2 After the number of symbols, for example, according to TS 38.214, assuming d 2，1 =1 and μ corresponds to carrying DCI format 2_0 or DCI format and SRS, PUCCH, PUSCH or μ r SCS configuration, where if PRACH is 15kHz or higher, μ r Corresponding to the SCS configuration of PRACH; otherwise μ r =0, and / or the UE cancels the actual repetition of PUCCH, PUSCH or PUSCH, for example, according to TS 38.214, determined according to clauses 9 and 9.2.5 or clause 6.1 of TS 38.214, or PRACH transmissions from the remaining symbols in the symbol set, and cancels SRS transmissions from the remaining symbols in the symbol subset.

[0059] If the UE is configured by higher layers to receive CSI-RS, or detects DCI format 0_1 ​​indicating that the UE receives CSI-RS in one or more resource block (RB) sets and symbol sets of a time slot, and the UE detects DCI format 2_0 whose bitmap indicates that any of the one or more RB sets are not available for reception, the UE cancels CSI-RS reception in the symbol set of the time slot.

[0060] If the UE does not detect that the SFI-index field value in DCI format 2_0 indicates that the symbol set of the time slot is flexible or uplink, and the UE does not detect that the DCI format indicates that the UE sends SRS, PUSCH, PUCCH or PRACH in the symbol set, the UE assumes that the flexible symbols in the CORESET configured for PDCCH monitoring by the UE are downlink symbols.

[0061] For the symbol set of a flexible time slot indicated by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or when tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the UE and if the UE does not detect DCI format 2_0 providing the time slot format for the time slot, then if the UE receives a corresponding indication through the DCI format, the UE receives PDSCH or CSI-RS in the symbol set of the time slot, if the UE receives a corresponding indication through the DCI format, RAR UL grant, fallbackRAR UL grant or successRAR and / or the UE receives PDCCH, then the UE sends PUSCH, PUCCH, PRACH or SRS in the symbol set of the time slot.

[0062] If the UE is configured by higher layers to receive PDSCH in the symbol set of the time slot, the UE does not receive PDSCH in the symbol set of the time slot. If the UE is configured by higher layers to receive CSI-RS in the symbol set of the time slot, the UE does not receive CSI-RS in the symbol set of the time slot, unless when the UE is provided with CO-DurationsPerCell and the symbol set of the time slot is within the remaining channel occupancy duration. If the UE is configured by higher layers to receive DL PRS in the symbol set of the time slot, the UE receives DL PRS. If the UE is configured by higher layers to send SRS, or PUCCH, or PUSCH or PRACH in the symbol set of the time slot, and the UE is not provided with enableConfiguredUL, the UE does not send PUCCH, or PUSCH or PRACH in the time slot, nor does it send SRS (if any) in symbols from the symbol set in the time slot, starting from the PUSCH preparation time T for the corresponding PUSCH timing capability. proc，2 For example, according to TS 38.214, it is assumed that after the last symbol of CORESET 2，1 =1, where the UE is configured to monitor the PDCCH for DCI format 2_0, and μ corresponds to the SCS configuration of the PDCCH carrying DCI format 2_0 and SRS, PUCCH, PUSCH or μ r The smallest SCS configuration among the SCS configurations, where μ r Corresponds to the SCS configuration of PRACH (if it is 15kHz or higher); otherwise μ r= 0. The UE does not expect to cancel transmissions of SRS, or PUCCH, or PUSCH, or PRACH (if any) from symbols in the symbol set in the slot, from the PUSCH preparation time T for the corresponding PUSCH timing capability proc，2 For example, according to TS 38.214, assuming that the d after the last symbol of CORESET 2，1 =1, where the UE is configured to monitor the PDCCH for DCI format 2_0, and μ corresponds to the SCS configuration of the PDCCH carrying DCI format 2_0 and SRS, PUCCH, PUSCH or μ r The smallest SCS configuration among the SCS configurations, where μ r Corresponds to the SCS configuration of PRACH (if 15kHz or higher); otherwise μ r =0.

[0063] If the UE is configured by a higher layer to send SRS, or PUCCH, or PUSCH, or PRACH in the symbol set of the time slot, and the UE is provided with enableConfiguredUL, the UE may send SRS, or PUCCH, or PUSCH, or PRACH accordingly.

[0064] In one embodiment, the solution described herein is directed to dynamic indication of valid CLI measurement opportunities.In one embodiment, when cells in unpaired spectrum operate with semi-statically configured flexible symbols, the presence of cross-link interference may depend on the dynamic usage of the configured flexible symbols.

[0065] In one embodiment, the UE receives a CLI measurement configuration, wherein the CLI measurement configuration semi-statically configures potential one or more measurement time instances or measurement opportunities (e.g., multiple measurement time slots) within a measurement period. In addition, the UE receives a dynamic indication of valid measurement time instances or measurement opportunities from the semi-statically configured one or more potential measurement time instances or measurement opportunities, where the UE needs to perform measurements.

[0066] In some implementations, the measurement configuration includes at least one of one or more SRS resource configuration sets for CLI SRS-RSRP and one or more RSSI resource configuration sets for CLI-RSSI. The SRS resource configuration may specify the SRS resources (time-frequency resource units) within the configured frequency bandwidth and their periodic characteristics. The RSSI resource configuration may specify the CLI-RSSI resource, which includes the location of the OFDM symbol, the RB set, and the periodicity and slot offset time opportunity for the CLI-RSSI resource.

[0067] In some implementations, a CLI measurement time instance or measurement opportunity is considered valid if it completely overlaps with a downlink symbol, e.g., a semi-static downlink symbol and a flexible symbol that is indicated or assumed to be a downlink symbol. In some implementations, a dynamic indication of a valid CLI measurement time instance or measurement opportunity may be indicated or applied only for a measurement time instance or measurement opportunity that partially or completely overlaps with a flexible symbol. A CLI measurement time instance or measurement opportunity that completely overlaps with a semi-static downlink symbol is assumed to be valid.

[0068] In one implementation, the UE receives an explicit dynamic indication of valid CLI measurement opportunities via a DCI or a media access control (MAC) control element (CE). For example, a bit field in the DCI (e.g., a DCI with a DL assignment and / or a DCI with an UL grant) is configured to indicate the availability of one or more configured CLI measurement opportunities. For example, each bit in the DCI bit field indicates the availability of an associated set of CLI measurement opportunities (e.g., the set may include at least one CLI measurement opportunity). In addition, the UE may receive a validity duration for the explicit dynamic indication.

[0069] In another implementation, the UE receives an implicit dynamic indication of a valid CLI measurement occasion via an SFI in DCI format 2_0. In one example, if the SFI indicates that all configured measurement symbols of the CLI measurement occasion are downlink symbols, then the CLI measurement occasion is considered valid. In another example, if the SFI indicates that a configured or predefined number of symbols from the configured measurement symbols of the CLI measurement occasion are downlink symbols, then the CLI measurement occasion is considered valid. In addition, the UE performs CLI measurements on DL symbols from the configured measurement symbols of the CLI measurement occasion.

[0070] In one example, if the UE does not receive a dynamic indication sent in a semi-statically configured flexible symbol of a configured CLI measurement time slot, the UE performs CLI measurement in the configured CLI measurement time slot.

[0071] In another example, if the UE receives a dynamic indication received in a semi-statically configured flexible symbol of a configured CLI measurement time slot, the UE performs CLI measurement in the configured CLI measurement time slot.

[0072] In yet another implementation, the UE receives an indication that a subset of the configured one or more CLI measurement occasions are always valid CLI measurement occasions. In one example, the indication is included as part of the measurement occasion configuration.

[0073] In implementation, the UE is not expected to receive more than one indication (e.g., DCI) in a time window indicating different validity states / conditions for CLI measurement occasions. In one embodiment, the time window may be one slot or a predefined number of symbols / slots (e.g., depending on the SCS or depending on a processing timeline such as a PUSCH preparation time or a PDSCH processing time). In one embodiment, the time window starts at a time associated with the reception of the indication (e.g., the time when the DCI is received).

[0074] In an implementation, the UE receives a first indication (eg, via RRC, MAC CE, or DCI signaling). The first indication may enable / disable the UE to perform CLI measurements during a duration for which the UE has skipped PDCCH monitoring.

[0075] If the UE does not receive a dynamic indication sent in a semi-statically configured flexible symbol configuring a CLI measurement slot (or measurement opportunity), and if the UE has received a PDCCH skip indication indicating skipping of PDCCH monitoring for a duration including the CLI measurement slot, then if the UE has been instructed to perform CLI measurements under such conditions (e.g., via a first indication), the UE performs CLI measurements in the configured CLI measurement slot.

[0076] If the UE does not receive a PDCCH skip indication within "T" time units (eg, symbols) prior to the CLI measurement opportunity, the UE may be expected to perform CLI measurements in the configured CLI measurement slot.

[0077] In implementation, a CLI measurement opportunity is considered valid if the SFI indicates that a configured or predefined number of symbols in the configured measurement symbols from the CLI measurement opportunity are downlink symbols, and if the SFI is received at least "X" time units (time slots / symbols) before the CLI measurement opportunity.

[0078] In an implementation, if a dynamic unavailability indication is received / detected at least "X" time units (e.g., time slots, symbols) before the CLI measurement opportunity, then the CLI measurement opportunity for the UE is considered unavailable, where X is predefined or configured and may depend on the UE capabilities. Otherwise, the CLI measurement opportunity is considered available, and the UE performs CLI measurements on the CLI measurement opportunity. In an example, a value of "1" for a bit in the unavailability indication bitmap indicates unavailability of the associated CLI measurement opportunity, while a value of "0" indicates no change to the current assumption of availability or unavailability for the associated CLI measurement opportunity.

[0079] In one example, three neighboring cells have different semi-static UL / DL configurations, such as Figure 2As shown. UE 1 in cell 1 202 is configured with CLI measurement (e.g., CLI-RSSI or SRS-RSRP) in time slot (n+3) 204 with a period of 5 time slots. That is, the CLI measurement opportunity is configured for UE 1 in time slot (n+3) 204. If the network entity decides to use the cell-specific configured flexible symbols as DL symbols in time slot (n+3) 204, the network entity indicates to UE 1 via scheduling DCI or group common DCI that the CLI measurement opportunity in time slot (n+3) 204 is a valid CLI measurement opportunity. Since time slot (n+3) 204 includes the cell-specific configured flexible symbols, UE 1 determines whether to perform CLI measurement on time slot (n+3) 204 based on the scheduling DCI including the bit field for the availability of CLI measurement opportunity and / or the SFI in DCI format 2_0.

[0080] In with Figure 2 In another related example, UE 2 in cell 2 206 is configured with CLI measurement with a period of 5 time slots in time slot (m+1) 208 and time slot (m+2) 210. Since time slot (l+1) 214 in cell 3 212 is configured as a UL time slot, the network entity configures the CLI measurement opportunity in time slot (m+1) 208 of cell 2 206 as always valid / available for CLI measurement. On the other hand, CLI from cell 1 202 exists only when the flexible symbol in time slot (n+2) 216 of cell 1 202 is used as a UL symbol. Therefore, the network entity configures the CLI measurement opportunity in time slot (m+2) 210 of cell 2 206 as dynamically activated and deactivated, and UE 2 determines the validity / availability of the CLI measurement opportunity in time slot (m+2) 210 based on the dynamic indication via DCI.

[0081] Figure 3 An exemplary RRC information element (IE) MeasObjectCLI is provided, which configures the CLI measurement resource list (e.g., SRS resources, RSSI resources) and the DCI bit field size for dynamic availability indication. The CLI measurement resources can be configured with dynamic availability indication based on the parameter rssi-Resource-Dynamic-r18 304 or srs-Resource-Dynamic-r18 302 set to "true" and the parameter positionInDynamicIndicator-r18 306.

[0082] The following table describes the different units of the MeasObjectCLI IE:

[0083]

[0084]

[0085]

[0086]

[0087] Regarding coordination between next generation Node Bs (gNBs), in order to adopt the methods disclosed in this document, the base station may need to perform signaling for coordination before and / or during CLI management operations.

[0088] Regarding inter-gNB coordination on the Xn interface, in some embodiments, the first base station gNB1 may send a message / IE to the second base station gNB2, wherein the message / IE includes an indication of whether the flexible time slots / symbols in the gNB1 cell are to be used and / or whether the flexible time slots / symbols are to be used for uplink or downlink. The message / IE may be transmitted on the Xn interface or any direct backhaul link between the base stations.

[0089] In several embodiments, gNB2 may receive a TDD configuration from gNB1. The configuration may be the expected TDD UL-DL IE specified in TS 38.423 or a new IE dedicated to the implementation of the CLI management method disclosed herein.

[0090] In one embodiment, the message / IE may indicate that any or all slots / symbols configured as flexible may be used. This embodiment may be particularly useful when flexible slots / symbols may be used or not used at all due to variations in traffic load in the gNB1 cell.

[0091] In one example, the indication may be interpreted by gNB2 in a semi-static manner, i.e., the indication remains valid until it is overwritten by another indication from gNB1.

[0092] In another example, the indication may be dynamic, i.e., it may be associated with the flexible timeslot / symbol on a periodic basis (which may be signaled or configured by OAM (Operations, Administration and Maintenance)), until a timer expires, and so on.

[0093] In another embodiment, the message / IE may indicate that certain flexible slots / symbols may be used. This embodiment provides additional flexibility in case of varying traffic load on the gNB1 cell, but at the cost of additional overhead as the generated message / IE may be larger.

[0094] In one example, each flexible symbol may be assigned one bit in the bitmap field, where, for example, a value of "1" may indicate that the flexible symbol is to be used (or not guaranteed to be used). Then, a value of "0" in the bitmap field may indicate that the associated flexible symbol is expected (or guaranteed) to be unused. In this example, the bits in the bitmap field may be associated one by one and in the same order with the flexible symbols indicated by the expected TDD UL-DL IE, etc.

[0095] In another example, all flexible symbols in each time slot may be assigned one bit in the bitmap field, where, for example, a value of "1" may indicate that all flexible symbols in the associated time slot are to be used (or not guaranteed to be used). Then, a value of "0" in the bitmap field may indicate that all flexible symbols in the associated time slot are expected (or guaranteed) to be unused. In this example, the bits in the bitmap field may be associated one by one and in the same order with the time slots indicated by the expected TDD UL-DL IE, etc. The gNB2 may discard / ignore any bits in the bitmap field associated with time slots that do not include flexible symbols.

[0096] In yet another example, all flexible symbols in each time slot may be assigned one bit in the bitmap field, but time slots that do not include flexible symbols may not be assigned bits in the bitmap field. Here, similarly, for example, a value of "1" may indicate that all flexible symbols in the associated time slot will be used (or not guaranteed to be unused). Then, a value of "0" in the bitmap field may indicate that all flexible symbols in the associated time slot are expected (or guaranteed) to be unused. In this example, the bits in the bitmap field may be associated one by one and in the same order with the time slots indicated by the expected TDD UL-DL IE, etc., including at least one flexible symbol.

[0097] In several examples, the indication may be interpreted as semi-static, i.e. the information remains valid until overwritten by another indication from gNB1. Alternatively, the indication may be valid for a period (signaled or preconfigured), until a timer expires, etc.

[0098] In several embodiments, the bitmap field may additionally or alternatively indicate whether the flexible slots / symbols are to be used for downlink or uplink.

[0099] In one example, for example, a value of "1" or "0" may indicate that the associated flexible symbol, all flexible symbols in an associated slot, etc. may be used for the downlink or uplink, respectively.

[0100] In another example, for example, a value of "1" or "0" may indicate that the associated flexible symbol, all flexible symbols in an associated slot, etc. may be used for the downlink or not used, respectively.

[0101] In yet another example, for example, a value of "1" or "0" may indicate that the associated flexible symbol, all flexible symbols in an associated slot, etc. may be used for uplink or not used, respectively.

[0102] In another example, for example, one bit with a value of "1" or "0" can indicate that the associated flexible symbol, all flexible symbols in the associated time slot, etc. can be used or not used, respectively; and another bit with a value of "1" or "0" can indicate that the associated flexible symbol, all flexible symbols in the associated time slot, etc. can be used for downlink or uplink, respectively. If the first bit indicates that the associated flexible symbol, all flexible symbols in the associated time slot, etc. are not used, the second bit can be discarded / ignored. The two bits can be located in the same bitmap field or in different bitmap fields.

[0103] Regarding inter-gNB coordination over the NG interface, similar signaling may be employed for inter-gNB coordination where the gNBs are not directly connected via the Xn interface or where indirect signaling is preferred or available.

[0104] In several embodiments, the configuration may be provided by the core network, such as an access and mobility management function (AMF) in the core network.

[0105] In several embodiments, gNB1 may send a message / IE to AMF on the NG interface, and then AMF may forward the information of the message / IE to gNB2 on another NG interface. The content of the message / IE from gNB1 to AMF and / or from AMF to gNB2 may be similar to the content of the message / IE described above for coordination on the Xn interface.

[0106] In some embodiments, the AMF may receive messages / IEs from multiple source gNBs, combine the information, and send the information to one or more target gNBs. For example, the AMF may apply an AND or OR operation to the bitmap field included by the message / IE from the source gNB. In one example, if the value "1" indicates that the flexible symbol is to be used by the source gNB, the result of the OR operation may indicate to the target gNB that at least one other source gNB intends to use the flexible symbol (or does not guarantee that the flexible symbol is not used). Other similar operations (e.g., AND, addition, etc.) may provide other such information from a set of source gNBs to one or more target gNBs that adopt the CLI management method proposed in the present disclosure.

[0107] Figure 4An example of a UE 400 according to aspects of the present disclosure is shown. The UE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0108] The processor 402, memory 404, controller 406, or transceiver 408, or various combinations thereof or various components may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof that is configured or otherwise supports components for performing the functions described in the present disclosure.

[0109] The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to enable the UE 400 to perform various functions of the present disclosure.

[0110] The memory 404 may include volatile or non-volatile memory. The memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 402, cause the UE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 404 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media that can be accessed by a general or special purpose computer.

[0111] In some implementations, the processor 402 and the memory 404 coupled to the processor 402 may be configured to cause the UE 400 to perform one or more functions described herein (e.g., the processor 402 executes instructions stored in the memory 404). For example, the processor 402 may support wireless communications at the UE 400 according to the examples disclosed herein.

[0112] The UE 400 may be configured to support means for receiving a CLI measurement configuration, the CLI measurement configuration comprising at least one CLI resource, the CLI resource of the at least one CLI resource being configured with a dynamic indication. The UE 400 may be configured to support means for monitoring the dynamic indication of the CLI resource for the at least one CLI resource. The UE 400 may be configured to support means for performing measurements on the CLI resource in response to the dynamic indication not indicating that the CLI resource is not available for measurement.

[0113] The UE 400 may be configured to support means for performing measurements on the CLI resources by performing measurements on the CLI resources in response to not detecting the dynamic indication.

[0114] The UE 400 may be configured to support means for performing measurements on the CLI resource in response to a dynamic indication being detected a number of time units not earlier than a start symbol of a CLI opportunity of the CLI resource, regardless of the dynamic indication.

[0115] In one embodiment, the dynamic indication is a dynamic availability indication, and the UE 400 may be configured to support means for performing measurements on the CLI resources in response to the dynamic availability indication indicating that the CLI resources are available for measurement.

[0116] The UE 400 may be configured to support means for receiving a validity duration of a dynamic indication.The UE 400 may be configured to support means for receiving a dynamic indication in a DCI.

[0117] In one embodiment, the CLI measurement configuration further comprises a size of a bit field in the DCI for a dynamic indication set, the dynamic indication set corresponding to a CLI resource set of at least one CLI resource. In one embodiment, the CLI resource is further configured with a bit position within the bit field for dynamic indication.

[0118] UE 400 may be configured to support components for receiving semi-static DL and UL configurations including at least one semi-static flexible symbol, and wherein at least one processor is configured to cause the UE to: receive a dynamic indication in response to a CLI resource of semi-static flexible symbols including at least one semi-static flexible symbol.

[0119] The controller 406 may manage input and output signals for the UE 400. The controller 406 may also manage peripheral devices that are not integrated into the UE 400. In some implementations, the controller 406 may utilize an operating system, such as Or other operating systems. In some implementations, the controller 406 can be implemented as part of the processor 402.

[0120] In some implementations, the UE 400 may include at least one transceiver 408. In some other implementations, the UE 400 may have more than one transceiver 408. The transceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.

[0121] The receiver chain 410 may be configured to receive a signal (e.g., control information, data, packet) over a wireless medium. For example, the receiver chain 410 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiver chain 410 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0122] The transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or in a wireless medium.

[0123] Figure 5 An example of a processor 500 according to aspects of the present disclosure is shown. The processor 500 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 500 may include a controller 502 configured to perform various operations according to the examples described herein. The processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. In addition, or alternatively, the processor 500 may optionally include one or more arithmetic logic units (ALUs) 506. One or more of these components may be in electronic communication or otherwise coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0124] Processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, obtain, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory located locally in or included in the processor chipset (e.g., processor 500) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0125] The controller 502 may be configured to manage and coordinate various operations of the processor 500 (e.g., signal, receive, obtain, acquire, send, output, forward, store, determine, identify, access, write, read) so that the processor 500 supports various operations according to the examples described herein. For example, the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0126] The controller 502 may be configured to retrieve (e.g., obtain, acquire, receive) instructions from the memory 504 and determine the (multiple) subsequent instructions to be executed so that the processor 500 supports various operations according to the examples described herein. The controller 502 may be configured to track the memory addresses of instructions associated with the memory 504. The controller 502 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, the controller 502 may be configured to interpret instructions and determine control signals to be output to other components of the processor 500 so that the processor 500 supports various operations according to the examples described herein. Additionally or alternatively, the controller 502 may be configured to manage data flow within the processor 500. The controller 502 may be configured to control the transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 500.

[0127] The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500) or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 504 may reside within or on the processor chipset (e.g., local to the processor 500). In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote from the processor 500).

[0128] The memory 504 may store computer-readable, computer-executable code, including instructions, which, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. The controller 502 and / or the processor 500 may be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions. For example, the processor 500 and / or the controller 502 may be coupled to or coupled to the memory 504, and the processor 500, the controller 502, and the memory 504 may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors, and the memory 504 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 various functions described herein.

[0129] One or more ALUs 506 may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs 506 may be located in or on a processor chipset (e.g., processor 500). In some other implementations, one or more ALUs 506 may be located outside a processor chipset (e.g., processor 500). One or more ALUs 506 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 506 may receive input operands and an opcode that determines the operation to be performed. One or more ALUs 506 may be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to operations. Additionally or alternatively, one or more ALUs 506 may support logic operations, such as AND, OR, XOR (XOR), NOR (NOR), and NAND (NAND), so that one or more ALUs 506 can process conditional operations, comparisons, and bitwise operations.

[0130] The processor 500 may support wireless communications according to examples disclosed herein. The processor 500 may be configured or operable to support components for receiving a CLI measurement configuration, the CLI measurement configuration including at least one CLI resource, the CLI resource of the at least one CLI resource being configured with a dynamic indication. The processor 500 may be configured or operable to support components for monitoring a dynamic indication of a CLI resource for the at least one CLI resource. The processor 500 may be configured or operable to support components for performing measurements on a CLI resource in response to the dynamic indication not indicating that the CLI resource is not available for measurement.

[0131] The processor 500 may be configured or operable to support means for performing measurements on the CLI resource in response to failure to detect a dynamic indication.

[0132] The processor 500 may be configured or operable to support means for performing measurements on the CLI resource in response to a dynamic indication being detected a number of time units not earlier than a start symbol of a CLI opportunity of the CLI resource regardless of the dynamic indication.

[0133] In one embodiment, the dynamic indication is a dynamic availability indication, and the processor 500 may be configured or operable to support means for performing measurements on the CLI resource by performing measurements on the CLI resource in response to the dynamic availability indication indicating that the CLI resource is available for measurement.

[0134] The processor 500 may be configured or operable to support means for receiving a validity duration of a dynamic indication.The processor 500 may be configured or operable to support means for receiving a dynamic indication in a DCI.

[0135] In one embodiment, the CLI measurement configuration further comprises a size of a bit field in the DCI for a dynamic indication set corresponding to a CLI resource set of at least one CLI resource. In one embodiment, the CLI resource is further configured with a bit position within the bit field for dynamic indication.

[0136] The processor 500 may be configured or operable to support components for receiving a semi-static DL and UL configuration including at least one semi-static flexible symbol, and wherein at least one processor is configured to cause the UE to: receive a dynamic indication in response to a CLI resource including at least one semi-static flexible symbol.

[0137] Figure 6An example of a NE 600 according to aspects of the present disclosure is shown. The NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0138] The processor 602, memory 604, controller 606, or transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination of components configured or otherwise supported to perform the functions described in the present disclosure.

[0139] The processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to enable the NE 600 to perform various functions of the present disclosure.

[0140] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602, cause the NE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as the memory 604 or another type of memory. Computer-readable media include both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media that can be accessed by a general or special purpose computer.

[0141] In some implementations, the processor 602 and the memory 604 coupled to the processor 602 may be configured to cause the NE 600 to perform one or more functions described herein (e.g., the processor 602 executes instructions stored in the memory 604). For example, the processor 602 may support wireless communication at the NE 600 according to the examples disclosed herein. The NE 600 may be configured to support a component for sending a CLI measurement configuration to a UE, the CLI measurement configuration including at least one CLI resource, wherein the CLI resource of the at least one CLI resource is configured with a dynamic indication of the validity of the CLI measurement occasion of the CLI resource. The NE 600 may be configured to support a component for determining the validity of the CLI measurement occasion of the CLI resource. The NE 600 may be configured to support a component for sending a dynamic indication of the validity of the CLI measurement occasion of the CLI resource to the UE.

[0142] Controller 606 may manage input and output signals for NE 600. Controller 606 may also manage peripheral devices that are not integrated into NE 600. In some implementations, controller 606 may utilize an operating system, such as In some implementations, the controller 606 may be implemented as part of the processor 602 .

[0143] In some implementations, the NE 600 may include at least one transceiver 608. In some other implementations, the NE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.

[0144] The receiver chain 610 may be configured to receive a signal (e.g., control information, data, packet) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0145] The transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or in a wireless medium.

[0146] Figure 7 A flow chart of a method according to aspects of the present disclosure is shown. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions.

[0147] At 705, the method may include: receiving a CLI measurement configuration, the CLI measurement configuration including at least one CLI resource, the CLI resource in the at least one CLI resource being configured with a dynamic indication. The operations of 705 may be performed according to the examples described herein. In some implementations, aspects of the operations of 705 may be performed by a UE, such as with reference to Figure 7 described.

[0148] At 710, the method may include monitoring a dynamic indication of a CLI resource for at least one CLI resource. The operations of 710 may be performed according to examples described herein. In some implementations, aspects of the operations of 710 may be performed by a UE, such as with reference to Figure 7 described.

[0149] At 715, the method may include: in response to the dynamic indication not indicating that the CLI resources are not available for measurement, performing measurements on the CLI resources. The operations of 715 may be performed according to the examples described herein. In some implementations, aspects of the operations of 715 may be performed by the UE, such as with reference to Figure 7 described.

[0150] It should be noted that the methods described herein describe one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0151] Figure 8 A flow chart of a method according to aspects of the present disclosure is shown. The operations of the method may be implemented by the NE described herein. In some implementations, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0152] At 805, the method may include: sending a CLI measurement configuration to the UE, the CLI measurement configuration including at least one CLI resource, wherein a CLI resource of the at least one CLI resource is configured with a dynamic indication of the validity of the CLI measurement opportunity of the CLI resource. The operation of 805 may be performed according to the examples described herein. In some implementations, aspects of the operation of 805 may be performed by a NE, such as referring to Figure 8 described.

[0153] At 810, the method may include determining the validity of a CLI measurement opportunity for a CLI resource. The operations of 810 may be performed according to the examples described herein. In some implementations, aspects of the operations of 810 may be performed by a NE, such as with reference to Figure 8 described.

[0154] At 815, the method may include: sending a dynamic indication of the validity of the CLI measurement opportunity of the CLI resource to the UE. The operation of 815 may be performed according to the examples described herein. In some implementations, aspects of the operation of 815 may be performed by the NE, such as referring to Figure 8 described.

[0155] It should be noted that the methods described herein describe one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0156] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor, coupled to the at least one memory and configured to cause the UE to: receiving a cross-link interference (CLI) measurement configuration comprising at least one CLI resource, wherein the CLI resources of the at least one CLI resource are configured with a dynamic indication; monitoring the dynamic indication of the CLI resource for the at least one CLI resource; and In response to the dynamic indication indicating that the CLI resource is available for measurement, performing measurements on the CLI resource.

2. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: The measurements are performed on the CLI resource by performing the measurements on the CLI resource in response to not detecting the dynamic indication.

3. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: In response to the dynamic indication being detected a number of time units before a start symbol of a CLI opportunity of the CLI resource, performing the measurement on the CLI resource regardless of the dynamic indication.

4. The UE of claim 1 , wherein the dynamic indication is a dynamic availability indication, and wherein the at least one processor is configured to cause the UE to: The measurements are performed on the CLI resource by performing the measurements on the CLI resource in response to the dynamic availability indication indicating that the CLI resource is available for measurement.

5. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: A validity duration of the dynamic indication is received.

6. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: The dynamic indication is received in downlink control information (DCI).

7. The UE according to claim 6, wherein the CLI measurement configuration further comprises a size of a bit field for a dynamic indication set in the DCI, the dynamic indication set corresponding to a CLI resource set of the at least one CLI resource.

8. The UE of claim 7, wherein the CLI resource is further configured with a bit position within the bit field for the dynamic indication.

9. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: receiving a semi-static downlink (DL) and uplink (UL) configuration, the semi-static DL and UL configuration comprising at least one semi-static flexible symbol, and wherein the at least one processor is configured to cause the UE to: The dynamic indication is received in response to the CLI resource comprising a semi-static flexible symbol of the at least one semi-static flexible symbol.

10. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving a cross-link interference (CLI) measurement configuration comprising at least one CLI resource, wherein the CLI resources of the at least one CLI resource are configured with a dynamic indication; monitoring the dynamic indication of the CLI resource for the at least one CLI resource; and In response to the dynamic indication indicating that the CLI resource is available for measurement, performing measurements on the CLI resource.

11. The processor of claim 10, wherein the at least one controller is configured to cause the processor to: perform the measurement on the CLI resource by performing the measurement on the CLI resource in response to not detecting the dynamic indication.

12. The processor of claim 10, wherein the at least one controller is configured to cause the processor to: In response to the dynamic indication being detected a number of time units before a start symbol of a CLI opportunity of the CLI resource, performing the measurement on the CLI resource regardless of the dynamic indication.

13. The processor of claim 10, wherein the dynamic indication is a dynamic availability indication, and wherein the at least one processor is configured to cause the UE to: The measurements are performed on the CLI resource by performing the measurements on the CLI resource in response to the dynamic availability indication indicating that the CLI resource is available for measurement.

14. The processor of claim 10, wherein the at least one controller is configured to cause the processor to: A validity duration of the dynamic indication is received.

15. The processor of claim 10, wherein the at least one processor is configured to cause the UE to: The dynamic indication is received in downlink control information (DCI).

16. The processor of claim 15, wherein the CLI measurement configuration further comprises a size of a bit field in the DCI for a dynamic indication set, the dynamic indication set corresponding to a set of CLI resources of the at least one CLI resource.

17. The processor of claim 16, wherein the CLI resource is further configured with a bit position within the bit field for the dynamic indication.

18. The processor of claim 10, wherein the at least one processor is configured to cause the UE to: receiving a semi-static downlink (DL) and uplink (UL) configuration, the semi-static DL and UL configuration comprising at least one semi-static flexible symbol, and wherein the at least one processor is configured to cause the UE to: The dynamic indication is received in response to the CLI resource comprising a semi-static flexible symbol of the at least one semi-static flexible symbol.

19. A method performed by a user equipment (UE), the method comprising: receiving a cross-link interference (CLI) measurement configuration, the CLI measurement configuration comprising at least one CLI resource, a CLI resource of the at least one CLI resource being configured with a dynamic indication; monitoring the dynamic indication of the CLI resource for the at least one CLI resource; and In response to the dynamic indication not indicating that the CLI resource is unavailable for measurement, performing measurements on the CLI resource.

20. A base station for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the base station to: sending a cross-link interference (CLI) measurement configuration to a user equipment (UE), the CLI measurement configuration comprising at least one CLI resource, wherein a CLI resource of the at least one CLI resource is configured with a dynamic indication of validity of a CLI measurement opportunity of the CLI resource; determining the validity of the CLI measurement opportunity of the CLI resource; as well as sending the dynamic indication of the validity of the CLI measurement opportunity of the CLI resource to the UE.

Images