Tracking reference signal in full duplex operation

Abstract

Methods, systems, and devices for wireless communication are described. Techniques described herein relate to a scheme for managing overlap of at least a portion of a tracking reference signal (TRS) with an uplink subband or guard band in a subband full duplex (SBFD) slot or symbol. In some examples, if a user equipment (UE) and / or a network entity determines that at least a portion of a TRS is scheduled for reception in an uplink subband or guard band of an SBFD timeslot or symbol, the UE and / or the network entity may: discard the TRS, punctured the portion of the TRS that overlaps the uplink subband or guard band; alternatively, the frequency position of the TRS may be shifted such that the TRS is scheduled within the downlink subband of the SBFD slot or symbol.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 956,588, entitled “TRACKING REFERENCE SIGNALS IN FULL DUPLEX OPERATION,” filed by Ibrahim et al. on September 29, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates to wireless communications including the use of tracking reference signals in full-duplex operation. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be able to 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, advanced LTE (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 techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each of which supports wireless communications for communication devices, which may be referred to as user equipment (UE). Summary of the invention

[0005] The described technology relates to improved methods, systems, devices and apparatuses for supporting tracking reference signals (TRS) in full-duplex operation. For example, the described technology provides for managing the overlap of at least a portion of a TRS with an uplink subband or guard band in a sub-band full-duplex (SBFD) time slot or symbol. If a user equipment (UE) and / or a network entity determines that a portion of a TRS is scheduled for reception in an uplink subband or guard band of a SBFD time slot or symbol, the UE and / or the network entity may discard the TRS, puncture the portion of the TRS that overlaps the uplink subband or the guard band, or shift the frequency position of the TRS so that the TRS is scheduled within the downlink subband of the SBFD time slot or symbol.

[0006] A method for wireless communication at a UE is described. The method may include: receiving control signaling from a network entity to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband; and adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive control signaling from a network entity for scheduling a group of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjust monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: means for receiving control signaling from a network entity for scheduling a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband; and means for adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0009] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to perform the following operations: receiving control signaling from a network entity to schedule a group of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0010] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing monitoring for the TRS based on the portion of the TRS overlapping at least one of the guard band or the uplink subband.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for refraining from monitoring the portion of the TRS and receiving the TRS via a second portion of the TRS that overlaps the downlink subband.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the TRS via the second portion may include operations, features, components, or instructions for receiving the TRS based on the second portion satisfying a threshold bandwidth.

[0013] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving the TRS via a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband may not be adjacent to the downlink subband in frequency.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the TRS via the second portion and the third portion may include operations, features, components, or instructions for the following actions: receiving the TRS based on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the TRS via the second portion and the third portion may include operations, features, components, or instructions for the following actions: receiving the TRS based on the second portion and the third portion each satisfying a threshold bandwidth.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing monitoring of a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband may not be adjacent to the downlink subband in frequency.

[0017] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, suppressing monitoring of the third portion may include operations, features, components, or instructions for suppressing monitoring of the third portion based on the second portion including more TRS resources than the third portion.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, suppressing monitoring of the third portion may include operations, features, components, or instructions for suppressing monitoring of the third portion based on the third portion failing to satisfy a threshold bandwidth.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, adjusting monitoring of the TRS may include operations, features, components, or instructions for the following actions: shifting the monitored resources for the TRS in frequency so that the monitored resources for the TRS can be within a downlink subband.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second TRS from a set of scheduled TRSs in a half-duplex symbol of the time slot, wherein the TRS may be scheduled in a SBFD symbol of the time slot.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the time slot comprises a SBFD time slot.

[0022] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving the control signaling may include operations, features, components, or instructions for the following actions: receiving an indication of a frequency hopping pattern to be applied to a TRS in an SBFD time slot and a half-duplex time slot, wherein adjusting monitoring of the TRS includes applying the frequency hopping pattern to the TRS so that the TRS can be within a downlink subband based on the time slot being a SBFD time slot.

[0023] A method for wireless communication at a network entity is described. The method may include: sending control signaling to a UE to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband; and adjusting the transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0024] An apparatus for wireless communication at a network entity is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: send control signaling to a UE for scheduling a group of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjust the transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0025] Another apparatus for wireless communication at a network entity is described. The apparatus may include: means for sending control signaling to a UE that schedules a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband; and means for adjusting the sending of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a network entity is described. The code may include instructions executable by a processor to perform the following operations: send control signaling to a UE to schedule a group of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjust the transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing transmission of the TRS based on the portion of the TRS overlapping at least one of the guard band or the uplink subband.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing transmission of the portion of the TRS and transmitting the TRS via a second portion of the TRS that overlaps a downlink subband.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the TRS via the second portion may include operations, features, components, or instructions for sending the TRS based on the second portion satisfying a threshold bandwidth.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting the TRS via a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband may not be adjacent to the downlink subband in frequency.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the TRS via the second portion and the third portion may include operations, features, components, or instructions for the following actions: sending the TRS based on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the TRS via the second portion and the third portion may include operations, features, components, or instructions for the following actions: sending the TRS based on the second portion and the third portion each satisfying a threshold bandwidth.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for suppressing transmission of a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband may not be adjacent to the downlink subband in frequency.

[0034] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, suppressing transmission of the third portion may include operations, features, components, or instructions for suppressing transmission of the third portion based on that the second portion includes more TRS resources than the third portion.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, suppressing transmission of the third portion may include operations, features, components, or instructions for suppressing transmission of the third portion based on the third portion failing to meet a threshold bandwidth.

[0036] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, adjusting the transmission of the TRS may include operations, features, components, or instructions for: shifting the TRS in frequency so that the TRS may be within a downlink subband.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second TRS of a scheduled set of TRSs in a half-duplex symbol of the time slot, wherein the TRS may be scheduled in a SBFD symbol of the time slot.

[0038] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the time slot comprises a SBFD time slot.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the control signaling may include operations, features, components, or instructions for the following actions: sending an indication of a frequency hopping pattern to be applied to a TRS in an SBFD time slot and a half-duplex time slot, wherein adjusting the transmission of the TRS includes applying the frequency hopping pattern to the TRS so that the TRS can be within a downlink subband based on the time slot being a SBFD time slot. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 An example of a wireless communication system supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0041] Figure 2 An example of a resource map supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0042] Figure 3 An example of a wireless communication system supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0043] Figure 4 An example of a time slot format supporting a tracking reference signal in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0044] Figure 5 An example of a timing diagram supporting a tracking reference signal in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0045] Figure 6 An example of a resource map supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0046] Figure 7 An example of a resource map supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0047] Figure 8An example of a resource map format supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0048] Fig. 9 An example of a process flow for supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is illustrated.

[0049] Fig.10 and Fig.11 A block diagram of a device supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is shown.

[0050] Fig.12 A block diagram of a communications manager supporting tracking reference signals in full-duplex operation is shown in accordance with one or more aspects of the present disclosure.

[0051] Fig.13 A diagram of a system including a device supporting tracking reference signals in full-duplex operation is shown in accordance with one or more aspects of the present disclosure.

[0052] Fig.14 and Fig.15 A block diagram of a device supporting tracking reference signals in full-duplex operation according to one or more aspects of the present disclosure is shown.

[0053] Fig.16 A block diagram of a communications manager supporting tracking reference signals in full-duplex operation is shown in accordance with one or more aspects of the present disclosure.

[0054] Fig.17 A diagram of a system including a device supporting tracking reference signals in full-duplex operation is shown in accordance with one or more aspects of the present disclosure.

[0055] Figures 18 to 21 A flow chart illustrating a method of supporting a tracking reference signal in full-duplex operation according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0056] Some wireless communication systems may implement sub-band full-duplex (SBFD) communication. In SBFD communication, a user equipment (UE) and a network entity may simultaneously communicate uplink transmissions and downlink transmissions. For example, an SBFD time slot may include at least one uplink subband, at least one downlink subband, and a guard band separating the at least one uplink subband from the at least one downlink subband. The network entity may schedule a semi-static or periodic tracking reference signal (TRS) for transmission to the UE, which the UE may use for time or frequency tracking and / or estimation of delay or Doppler spread. In some cases, the UE and the network entity may switch between half-duplex communication and SBFD communication. In an SBFD time slot or symbol, at least a portion of the TRS scheduled semi-statically or periodically may be scheduled in an uplink subband or a guard band. The UE may not receive a signal in an uplink subband or in a guard band. Therefore, the UE may not be able to receive a TRS that at least partially overlaps an uplink subband or a guard band.

[0057] Various aspects of the present disclosure relate to managing TRS transmission and reception in full-duplex operation. For example, some aspects relate to a scheme for managing the overlap of at least a portion of a TRS with an uplink subband or guard band in an SBFD time slot or symbol. If a UE and / or a network entity determines that a portion of a TRS is scheduled for reception in an uplink subband or guard band of an SBFD time slot or symbol, the UE and / or the network entity may discard the TRS, may puncture the portion of the TRS that overlaps the uplink subband or guard band, or may shift the frequency position of the TRS so that the TRS is scheduled in a downlink subband of the SBFD time slot or symbol. Puncturing may refer to discarding the portion of the TRS that overlaps the uplink subband or guard band, and receiving the TRS via the remaining portion of the TRS included in the downlink subband. For example, when puncturing a portion of the TRS, the UE may omit monitoring the TRS in the punctured communication resources, and the network entity may suppress sending the TRS in the punctured communication resources. In some examples, the UE and network entities may determine whether to puncture or drop the TRS based on the bandwidth of the TRS within the downlink subband. In some cases, the network may define a frequency hopping scheme for half-duplex time slots or symbols and SBFD or symbols so that regardless of whether a given time slot / symbol is configured for half-duplex communication or SBFD communication, the TRS is scheduled for reception in the downlink resources of the time slot / symbol.

[0058] Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects of the present disclosure are additionally illustrated and described with reference to resource diagrams, timing diagrams, time slot formats, and process flows. Aspects of the present disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flow diagrams related to TRS in full-duplex operation.

[0059] Figure 1 An example of a wireless communication system 100 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is illustrated. The 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, the 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 according to other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0060] The network entities 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may include devices in different forms or with different capabilities. In various examples, the network entities 105 may be referred to as network elements, mobility elements, radio access network (RAN) nodes, or network equipment, among other nomenclature. In some examples, the network entities 105 and the UE 115 may communicate wirelessly via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, the network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) within which the UE 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area within which the network entity 105 and the UE 115 may support signal communications according to one or more radio access technologies (RATs).

[0061] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or both stationary and mobile at different times. The UEs 115 may be devices in different forms or with different capabilities. Figure 1 Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communication with various types of devices, such as Figure 1 Communicate with other UEs 115 or network entities 105) as shown.

[0062] As described herein, a node of the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, the node may be a UE 115. As another example, the node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different relative to these examples. Similarly, references to UE 115, network entity 105, apparatus, device, computing system, etc. may include disclosure of UE 115, network entity 105, apparatus, device, computing system, etc. as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that the first node is configured to receive information from a second node.

[0063] In some examples, the network entities 105 may communicate with the core network 130 or with each other, or both. For example, the network entities 105 may communicate with the 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, the network entities 105 may communicate with each other directly (e.g., directly between the network entities 105) or indirectly (e.g., via the core network 130) via the backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, the network entities 105 may communicate with each other via midhaul communication links 162 (e.g., according to a midhaul interface protocol) or fronthaul communication links 168 (e.g., according to a fronthaul interface protocol) or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., electrical links, optical fiber links), one or more wireless links (e.g., radio links, wireless optical links), etc. or various combinations thereof. UE 115 may communicate with core network 130 via communication link 155 .

[0064] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a transceiver base station, a radio base station, an NR base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a gigabit Node B (any of which may be referred to as a gNB), a 5G NB, a next-generation eNB (ng-eNB), a home Node B, a home evolved Node B, or other suitable terminology). In some examples, the network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, stand-alone) base station architecture, which 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 a base station 140).

[0065] In some examples, the network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that may be configured to utilize a protocol stack that is physically or logically distributed between 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, the 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 (near RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) 180 system, or any combination thereof. The RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 105 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The functional split between CU 160, DU 165, and RU 170 is flexible and may support different functionalities 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 functional split of a protocol stack may be employed between CU 160 and DU 165 such that CU 160 may support one or more layers of a protocol stack and DU 165 may support one or more different layers of a protocol stack. In some examples, CU 160 may host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between the DU 165 and the RU 170, such that the DU 165 may support one or more layers of the protocol stack, and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or more different cells (e.g., via one or more RUs 170). In some cases, the functional split between CU 160 and DU 165 or between DU 165 and RU 170 may be within a protocol layer (e.g., some functions of a protocol layer may be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer are performed by different ones of CU 160, DU 165, or RU 170). CU 160 may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 may be connected to one or more DUs 165 via midhaul communication links 162 (e.g., F1, F1-c, F1-u), and DU 165 may be connected to one or more RUs 170 via fronthaul communication links 168 (e.g., an open fronthaul (FH) interface). In some examples, midhaul communication link 162 or fronthaul communication link 168 may be implemented based on interfaces (eg, channels) between layers of a protocol stack supported by respective network entities 105 that communicate via those communication links.

[0067] In some wireless communication systems (e.g., wireless communication system 100), infrastructure and spectrum resources for radio access may 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 nodes 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 DUs 165 or one or more RUs 170 may be controlled in part by one or more CUs 160 associated with a donor network entity 105 (e.g., a 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 nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120). The IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a coupled IAB donor's DU 165. The IAB-MT may include an independent set of antennas for relaying communications with the UE 115, or may share the same antennas of the IAB node 104 (e.g., of the RU 170) for access via the DU 165 of the IAB node 104 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, the 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 the IAB node 104) may be configured to operate according to the techniques described herein.

[0068] For example, an access network (AN) or RAN may include an access node (e.g., an IAB donor), communications between an IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, the IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and the IAB node 104 may communicate via an F1 interface according to a protocol defining signaling messages (e.g., an F1AP protocol). Additionally or alternatively, CU 160 may communicate with the core network via an interface (which may be an example of a portion of a backhaul link) and may communicate with other CUs 160 (e.g., CUs 160 associated with alternative IAB donors) via an Xn-C interface (which may be an example of a portion of a backhaul link).

[0069] The IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, wireless self-backhaul capability, etc.). The DU 165 may act as a distributed scheduling node toward a child node associated with the IAB node 104, and the IAB-MT may act as a scheduled node toward a parent node associated with the IAB node 104. That is, the IAB donor may be referred to as a parent node that communicates with one or more child nodes (e.g., the IAB donor may relay the transmission of the UE through one or more other IAB nodes 104). Additionally or alternatively, the IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of the IAB node 104 may provide a Uu interface for the child IAB node 104 to receive signaling from the parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for the parent IAB node 104 to signal to the child IAB node 104 or the UE 115.

[0070] For example, the IAB node 104 may be referred to as a parent node supporting communications for a child IAB node or as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 having a wired or wireless connection (e.g., backhaul communication link 120) to the core network 130, and may act as a parent node of the IAB node 104. For example, the DU 165 of the IAB donor may relay the transmission to the UE 115 through the IAB node 104, or may directly signal the transmission to the UE 115, or both. The CU 160 of the IAB donor may signal the IAB node 104 via the F1 interface that the communication link is established, and the IAB node 104 may schedule the transmission (e.g., the transmission relayed from the IAB donor to the UE 115) through the DU 165. That is, data may be relayed to and from the IAB node 104 via the NR Uu interface of the MT to the IAB node 104 via signaling. Communications with the IAB node 104 may be scheduled by the DU 165 of the IAB donor, and communications with the IAB node 104 may be scheduled by the DU 165 of the IAB node 104 .

[0071] Where the techniques described herein are applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support TRS in full-duplex operation as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally or alternatively be performed by one or more components of the disaggregated RAN architecture (e.g., an IAB node 104, a DU 165, a CU 160, a RU 170, a RIC 175, a SMO 180).

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

[0073] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as network entities 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 shown.

[0074] The UE 115 and the network entity 105 may 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" may refer to a collection of RF spectrum resources having a physical layer structure defined for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of an RF spectrum band (e.g., a bandwidth portion (BWP)) that operates 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 for coordinating carrier operations, user data, or other signaling. The wireless communication system 100 may support communications with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between the network entity 105 and other devices may refer to communication between these devices and any portion (e.g., entity, sub-entity) of the network entity 105. For example, the terms "send," "receive," or "communicate" when referring to the network entity 105 may refer to any portion of a network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105).

[0075] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

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

[0078] The signal waveform transmitted via the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system using MCM techniques, a resource element may refer to a symbol period (e.g., the duration of a modulation symbol) and a resource of a subcarrier, in which case the symbol period and the 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 coding rate of the modulation scheme, or both), so that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high order modulation scheme may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, time 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.

[0079] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

[0080] The time interval for the network entity 105 or the UE 115 may be expressed in multiples of a basic time unit, which may be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the supported subcarrier spacing, and N f The supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0081] 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, the frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a certain 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 certain number of symbol periods (e.g., depending on the length of the cyclic prefix appended in front of each symbol period). In some wireless communication systems 100, the time slot may be further divided into a plurality of 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., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0082] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0083] Physical channels may be multiplexed according to various techniques in order to communicate using a carrier. For example, physical control channels and physical data channels may be multiplexed using one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique to signal via a downlink carrier. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a set of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs in UE 115 may monitor or search a control region to obtain control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may 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 sets may include a common search space set configured for transmitting control information to multiple UEs 115 , and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0084] The network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with the network entity 105 (e.g., using a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) on which the logical communication entity operates. Depending on various factors such as the capabilities of the network entity 105, such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include a building, a subset of a building, or an external space between or overlapping coverage areas 110, and the like.

[0085] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 with service subscriptions with a network provider that supports the macro cell. A small cell may be associated with a lower power network entity 105 (e.g., a lower power base station 140) (compared to a macro cell), and the small cell may operate using the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription with a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a home or office). A network entity 105 may support one or more cells, and may also use one or more component carriers to support communications via one or more cells.

[0086] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0087] In some examples, the network entities 105 (e.g., base stations 140, RUs 170) may be mobile and thus provide communication coverage for 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 provide coverage for various coverage areas 110 using the same or different radio access technologies.

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

[0089] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

[0090] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the 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 communication 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 commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

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

[0092] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The 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), an 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), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a network entity 105 (e.g., a base station 140) associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of one or more network operators. IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0093] The wireless communication system 100 may operate using one or more frequency bands that may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from about 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 may be sufficient to penetrate structures so that macro cells provide services to UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) than communications using the lower frequencies and longer wavelengths of the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0094] The wireless communication system 100 may utilize both licensed RF spectrum bands and unlicensed RF spectrum bands. For example, the wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for conflict detection and avoidance. In some examples, operations performed using unlicensed bands may be based on carrier aggregation configuration (e.g., LAA) in conjunction with component carriers operating using licensed bands. Operations performed using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and the like.

[0095] The 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 technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the network entity 105 or UE 115 may be located in one or more antenna arrays or antenna panels, which may support MIMO operations 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, antennas or antenna arrays associated with the network entity 105 may be located at different geographical locations. The network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that the network entity 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals sent via the antenna ports.

[0096] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

[0097] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining signals conveyed via antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals conveyed via antenna elements may include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each of these antenna elements may be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device or relative to some other direction).

[0098] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the 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 sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions 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)) beam directions for later transmission or reception by the network entity 105.

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

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

[0101] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive 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).

[0102] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0103] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0104] In some examples, the wireless communication system 100 may implement SBFD communication. In SBFD communication, the UE 115 and the network entity 105 may simultaneously communicate uplink transmissions and downlink transmissions. For example, an SBFD time slot may include at least one uplink subband, at least one downlink subband (e.g., within the same carrier as the at least one uplink subband), and a guard band separating the at least one uplink subband from the at least one downlink subband. The network entity 105 may schedule semi-static or periodic TRS for transmission to the UE 115, which the UE 115 may use, for example, for time or frequency tracking and estimation of delay or Doppler spread. In some cases, the UE 115 and the network entity 105 may switch between half-duplex communication and SBFD communication. In an SBFD time slot or symbol, at least a portion of the semi-statically or periodically scheduled TRS may be scheduled in an uplink subband or a guard band. The UE 115 may not receive a signal in an uplink subband or in a guard band. Therefore, UE 115 may not be able to receive a TRS that at least partially overlaps with an uplink subband or a guard band.

[0105] If the UE 115 and / or the network entity 105 determine that a portion of the TRS is scheduled for reception in an uplink subband or guard band of an SBFD time slot or symbol, the UE 115 and / or the network entity 105 may discard the TRS, may puncture the portion of the TRS that overlaps the uplink subband or guard band, or may shift the frequency position of the TRS so that the TRS is scheduled within the downlink subband of the SBFD time slot or symbol. Puncturing refers to discarding the portion of the TRS that overlaps the uplink subband or guard band, and receiving the TRS via the remaining portion of the TRS included in the downlink subband. In some examples, the UE 115 and the network entity 105 may determine whether to puncture or discard the TRS based on the bandwidth of the TRS within the downlink subband. In some cases, the network entity 105 may define a frequency hopping scheme for half-duplex slots or symbols and SBFD symbols such that TRSs are scheduled for reception in the downlink resources of a given slot / symbol regardless of whether the slot / symbol is configured for half-duplex or SBFD communication.

[0106] Figure 2 An example of a resource map 200 supporting TRS in a full-duplex network according to one or more aspects of the present disclosure is illustrated. The resource map 200 can implement aspects of the wireless communication system 100. As described herein, some wireless communication systems 100 can implement full-duplex communication. The full-duplex communication can be in-band full-duplex (IBFD) communication or sub-band FDD communication (e.g., flexible duplex).

[0107] The first example 205-a illustrates an IBFD example. In IBFD, a wireless device (e.g., a network entity 105 or a UE 115) may transmit and receive on the same frequency resource at the same time. For example, downlink resources 210-a and uplink resources 215-a may overlap completely or partially (e.g., downlink resources 210-a and uplink resources 215-a may share the same IBFD time and / or time resources).

[0108] The second example 205-b illustrates a sub-band FDD example. In sub-band FDD, a wireless device (e.g., a network entity 105 or a UE 115) may transmit and receive simultaneously but on different frequency resources. For example, uplink resources 210-b may be separated from downlink resources 215-b in the frequency domain (e.g., via a guard band 220).

[0109] Figure 3Examples of wireless communication systems 300-a, 300-b, and 300-c that support TRS in a full-duplex network according to one or more aspects of the present disclosure are illustrated. The wireless communication systems 300-a, 300-b, and 300-c may implement aspects of the wireless communication system 100. For example, the wireless communication system 300-a may include a first UE 115-a and a second UE 115-b, the wireless communication system 300-b may include a first UE 115-c and a second UE 115-d, and the wireless communication system 300-c may include a first UE 115-e and a second UE 115-f, which may be examples of UE 115 as described herein. The wireless communication system 300-a may include network entity 105-a and network entity 105-b, the wireless communication system 300-b may include network entity 105-c and network entity 105-d, and the wireless communication system 300-c may include network entity 105-e, which may be examples of network entity 105 as described herein.

[0110] The wireless communication system 300-a illustrates an example in which the network entity 105-a operates in full duplex and each of the first UE 115-a and the second UE 115-b operates in half duplex. For example, the network entity 105-a may use downlink resources (e.g., downlink resources 335-a or downlink resources 335-b) to send a downlink signal 320-a to the second UE 115-b, and the first UE 115-a may use downlink resources 340-a to send an uplink signal 325-a to the network entity 105-a. The uplink resources 340-a may not overlap with the downlink resources 335-a and the downlink resources 335-b. The uplink signal 325-a sent by the first UE 115-a may cause cross-link interference 315-b at the second UE 115-b. The transmission of the network entity 105-b may cause cross-link interference 315-a at the network entity 105-a. The transmission of the downlink signal 320 - a by the network entity 105 - a may cause self-interference 330 - a at the network entity 105 - a relative to the reception of the uplink signal 325 - a .

[0111] The wireless communication system 300-b illustrates an example in which the network entity 105-c operates in full-duplex and the first UE 115-c operates in full-duplex. For example, the network entity 105-c may use downlink resources 335-c to send a downlink signal 320-b to the first UE 115-c, and the first UE 115-c may use uplink resources 340-b to send an uplink signal 325-b to the network entity 105-c. The network entity 105-c may also send a downlink signal 320-c to the second UE 115-d. The uplink resources 340-b may overlap (e.g., partially or completely overlap) with the downlink resources 335-c. The uplink signal 325-b sent by the first UE 115-c may cause cross-link interference 315-d at the second UE 115-d. The transmission of the network entity 105-d may cause cross-link interference 315-c at the network entity 105-c. The transmission of the downlink signal 320-b or the downlink signal 320-c by the network entity 105-c may cause self-interference 330-b at the network entity 105-a relative to the reception of the uplink signal 325-b. The transmission of the uplink signal 325-b by the first UE 115-c may cause self-interference 330-c at the first UE 115-c relative to the reception of the downlink signal 320-b.

[0112] The wireless communication system 300-c illustrates an example in which the network entity includes multiple TRPs (e.g., a first TRP 310-a and a second TRP 310-b) and operates in full-duplex and the first UE 115-e operates in full-duplex. For example, the first UE 115-e may support SBFD operation. For example, the second TRP 310-b may use downlink resources 335-d to send a downlink signal 320-d to the first UE 115-e, and the second TRP 310-b may use downlink resources 335-d to send a downlink signal 320-e to the second UE 115-f. The first UE 115-e may use uplink resources 340-c to send an uplink signal 325-c to the first TRP 310-a. The uplink resources 340-c may overlap (e.g., partially or completely overlap) with the downlink resources 335-d. The transmission of downlink signal 320-d and downlink signal 320-e by the second TRP 310-b may cause cross-link interference 315-e at the first TRP 310-a. The uplink signal 325-c transmitted by the first UE 115-e may cause cross-link interference 315-f at the second UE 115-f. The transmission of uplink signal 325-c by the first UE 115-e may cause self-interference 330-d at the first UE 115-e relative to the reception of downlink signal 320-d.

[0113] Some wireless communication systems may include only TDD frequency bands. Some wireless communication systems (e.g., wireless communication system 300-a) may include full-duplex operation at the network and half-duplex operation at the UE. Some wireless communication systems may support SBFD (e.g., full-duplex within a carrier, but no overlap between downlink resources and uplink resources).

[0114] Figure 4 An example of a slot format 400 supporting TRS in a full-duplex network according to one or more aspects of the present disclosure is illustrated. The slot format 400 may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c.

[0115] The time slot format 400 illustrates an example half-duplex downlink time slot 405, SBFD time slot 410, and half-duplex uplink time slot 415 for a carrier bandwidth 430. The half-duplex downlink time slot 405 includes a downlink control region 435-a (e.g., resources for downlink control) and a downlink data region 440-a (e.g., resources for downlink data). The half-duplex uplink time slot 415 includes an uplink data region 450-b (e.g., resources for a physical uplink shared channel (PUSCH)) and an uplink control region 445-b (e.g., resources for uplink control).

[0116] The SBFD timeslot 410 includes a downlink BWP that includes a first downlink subband 420-a and a second downlink subband 420-b. In a "D+U" timeslot, such as in the SBFD timeslot 410, the carrier bandwidth 430 may be used for both uplink transmissions and downlink transmissions. Figure 4As illustrated, the SBFD time slot 410 includes an uplink BWP that includes an uplink subband 425. A guard band may separate a first downlink subband 420-a and a second downlink subband 420-b from the uplink subband 425. The first downlink subband 420-a includes a downlink control region 435-b and a downlink data region 440-b. The second downlink subband 420-b includes a downlink control region 435-c and a downlink data region 440-c. The uplink subband 425 includes a PUSCH region 450-a and an uplink control region 445-a. In some examples, in a "D+U" time slot, downlink transmissions and uplink transmissions may occur in overlapping frequency bands (e.g., IBFD operation). In some examples, in a "D+U" time slot, as shown in the SBFD time slot 410, downlink transmissions and uplink transmissions may occur in adjacent, non-overlapping frequency bands. When scheduling with a "D+U" time slot, a half-duplex UE 115 may transmit in an uplink frequency band (e.g., uplink subband 425) or receive in a downlink frequency band (e.g., first downlink subband 420-a and second downlink subband 420-b). When scheduling with a "D+U" time slot, a full-duplex UE 115 (e.g., a UE 115 supporting simultaneous transmission and reception) may transmit in an uplink frequency band (e.g., uplink subband 425) and / or receive in a downlink frequency band (e.g., first downlink subband 420-a and second downlink subband 420-b). A "D+U" time slot may include downlink-only symbols, uplink-only symbols, or full-duplex symbols.

[0117] Figure 5 An example of a timing diagram 500 for supporting TRS in a full-duplex network according to one or more aspects of the present disclosure is illustrated. In some examples, the timing diagram 500 may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c. Figure 5 In the example of FIG. 5 , a time period 505 corresponding to a first time slot 510 and a second time slot 515 is illustrated. In this example, a TRS resource 520 may be configured in the first time slot 510 and the second time slot 515 (indexed as time slot n and time slot n+1, respectively).

[0118] In some examples, the TRS resources 520 may include two or four periodic CSI-RS resources with a periodicity of P*2^μ slots, where P=10, 20, 40, or 80, and μ represents a subcarrier spacing (SCS) (e.g., for 15, 30, ..., μ=0, 1, ...). All four resources (e.g., the TRS resource in the fourth index symbol in the first slot 510, the TRS resource in the eighth index symbol in the first slot 510, the TRS resource in the second slot 515, and the TRS resource in the eighth index symbol in the second slot 515) may be associated with a single port, where the density is three (e.g., the TRS in the TRS resources 520 uses three resource elements per symbol per resource block and uses one antenna port to transmit). The first pair of TRS resources in the TRS resources 520 may be transmitted in one slot (e.g., the first slot 510), and the second pair of resources in the TRS resources 520 (if configured) may be transmitted in the next adjacent slot (e.g., the second slot 515). The minimum bandwidth may be equal to min{52 physical resource blocks (PRBs), the bandwidth of the active BWP}. In some examples, for P=10, the bandwidth may not exceed 52 PRBs. Figure 5 In the example of , the TRS resources 520 include two pairs of resources using three resource elements per symbol per resource block in the first time slot 510 and include two pairs of resources using three resource elements per symbol per resource block in the second time slot 515.

[0119] In some examples, TRS resources 520 may be used for time / frequency tracking for a particular bandwidth or BWP and / or for measuring delay spread or Doppler spread. To estimate delay spread, TRS resources 520 may have a dense pattern in frequency (e.g., D=3) and sufficient resource blocks. To estimate Doppler spread, each TRS in TRS resources 520 may include two symbols spaced four symbols apart. Figure 5 In the example of , each TRS in TRS resource 520 has a density of three and includes two symbols separated by 4 symbols.

[0120] Figure 6 An example of a slot format 600-a and an example of a slot format 600-b supporting TRS in full-duplex operation according to one or more aspects of the present disclosure are illustrated. The slot formats 600-a and 600-b may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c.

[0121] Slot formats 600-a and 600-b illustrate example half-duplex downlink time slots (e.g., half-duplex downlink time slots 605-a and half-duplex downlink time slots 605-b) and SBFD time slots (e.g., SBFD time slots 610-a and SBFD time slots 610-b) for active BWPs (e.g., BWP 640-a and BWP 640-b) for UE 115. The half-duplex downlink time slots (half-duplex downlink time slots 605-a and half-duplex downlink time slots 605-b) include downlink regions (downlink regions 615-a and downlink regions 615-b) (e.g., resources used for downlink transmissions). SBFD time slot 610-a includes downlink subband 620-a and downlink subband 620-b. SBFD time slot 610-b includes downlink subband 620-c and downlink subband 620-d. In "D+U" time slots, such as in SBFD time slots (eg, SBFD time slot 610-a and SBFD time slot 610-b), active BWPs (eg, BWP 640-a and BWP 640-b) may be used for both uplink and downlink transmissions.

[0122] As illustrated in slot format 600-a, SBFD slot 610-a includes uplink subband 625-a. Guard band 630-a and guard band 630-b may separate downlink subband 620-a and downlink subband 620-b from uplink subband 625-a. As illustrated in slot format 600-b, SBFD slot 610-b includes uplink subband 625-b. Guard bands 630-c and 630-d may separate downlink subband 620-c and downlink subband 620-d from uplink subband 625-b.

[0123] As shown in time slot format 600-a, in some examples, UE 115 may be scheduled with TRS opportunities in half-duplex downlink time slot 605-a and SBFD time slot 610-a. TRS 650-a and TRS 650-b may be scheduled in downlink region 615-a of half-duplex downlink time slot 605-a, and UE 115 may receive TRS 650-a and TRS 650-b. TRS 650-c and TRS 650-d may be scheduled in SBFD time slot 610-a. For example, the network may schedule periodic TRS in each time slot. In the SBFD time slot 610-a, the first part of TRS 650-c and the first part of TRS 650-d overlap with the downlink subband 620-a, the second part of TRS 650-c and the second part of TRS 650-d overlap with the downlink subband 620-b, and the third part of TRS 650-c and the third part of TRS 650-d overlap with the guard band (guard band 630-a and guard band 630-b) and the uplink subband 625-a.

[0124] As shown in time slot format 600-b, in some examples, UE 115 may be scheduled with TRS opportunities in half-duplex downlink time slot 605-b and SBFD time slot 610-b. TRS 650-e and TRS 650-f may be scheduled in downlink region 615-b of half-duplex downlink time slot 605-b, and UE 115 may receive TRS 650-e and TRS 650-f. TRS 650-g and TRS 650-g may be scheduled in SBFD time slot 610-b. For example, the network may schedule periodic TRS in each time slot. In the SBFD time slot 610-b, the first part of TRS 650-g and the first part of TRS 650-h overlap with the downlink subband 620-d, and the second part of TRS 650-g and the second part of TRS 650-h overlap with the guard band 630-d and the uplink subband 625-b.

[0125] like Figure 6As shown, in SBFD time slots (e.g., SBFD time slots 610-a and SBFD time slots 610-b), the frequency resources available for downlink may be less than the frequency resources used for half-duplex downlink time slots (e.g., half-duplex downlink time slots 605-a and half-duplex downlink time slots 605-b). For full-duplex aware UEs, TRS opportunities may occur in full-duplex time slots (e.g., SBFD time slots 610-a and SBFD time slots 610-b). In some cases, TRSs that overlap with uplink subbands or guard bands in SBFD time slots may be punctured. Puncturing may result in non-adjacent downlink resources (e.g., downlink subbands 620-a and downlink subbands 620-b) being used for TRSs (e.g., TRS 650-c or TRS 650-d), which may involve special processing on the UE side. In some cases, UE 115 may process TRS resources in two downlink subbands (e.g., downlink subband 620-a and downlink subband 620-b) separately, which may result in a loss of coherence across the downlink subbands. In some cases, UE 115 and / or network entity 105 may ensure that there are sufficient frequency domain resources in the TRS after puncturing to achieve accurate delay spread estimation.

[0126] In some examples, if UE 115 is configured with a set of TRSs (e.g., TRS 650-a, TRS 650-b, TRS 650-c, and TRS 650-d), then the TRSs in the set of TRSs (e.g., TRS 650-c and TRS 650-d) that overlap with the guard band (guard band 630-a or guard band 630-b) or the uplink subband 625-a may be considered as an error condition and may not be scheduled by the network entity 105.

[0127] In some examples, UE 115 may not process TRS opportunities (e.g., TRS 650-c and TRS 650-d) that overlap with a guard band (guard band 630-a or guard band 630-b) or an uplink subband 625-a (e.g., UE 115 may discard or refrain from monitoring TRS 650-c and TRS 650-d). In some examples, network entity 105 may discard TRS opportunities (e.g., TRS 650-c and TRS 650-d) that overlap with a guard band (guard band 630-a or guard band 630-b) or an uplink subband 625-a (e.g., network entity 105 may not send TRS 650-c and TRS 650-d).

[0128] In some examples, UE 115 and / or network entity 105 may puncture TRS opportunities (e.g., TRS 650-c and TRS 650-d) that overlap with a guard band (guard band 630-a or guard band 630-b) or uplink subband 625-a (e.g., UE 115 may discard or refrain from monitoring TRS 650-c and TRS 650-d). In some cases, the TRS may be punctured to be included in downlink subband 620-a and downlink subband 620-b. For example, portions of TRS 650-c and TRS 650-d that overlap with the guard bands (guard bands 630-a and 630-b) and uplink subband 625-a may be punctured, and UE 115 may receive TRS 650-c and TRS 650-d on non-adjacent frequency domain resources (e.g., downlink subband 620-a and downlink subband 620-b). In some cases, the TRS may be punctured to be included in downlink subband 620-a and downlink subband 620-b. For example, portions of TRS 650-c and TRS 650-d that overlap with a guard band (guard band 630-a and guard band 630-b), uplink subband 625-a, and a downlink subband (downlink subband 620-a or downlink subband 620-b) may be punctured, and UE 115 may receive TRS 650-c and TRS 650-d on another downlink subband (e.g., one of downlink subband 620-a and downlink subband 620-b). In some cases, the TRS may be punctured so that the TRS is received on downlink subband 620-b (e.g., a downlink subband having a lower frequency range). In some cases, the TRS may be punctured so that the TRS is received on a downlink subband that contains more TRS resources (e.g., downlink subband 620-b has more TRS resources for TRS 650-c and TRS 650-d (e.g., larger bandwidth 655-a) than downlink subband 620-a (e.g., bandwidth 655-b)).

[0129] In some examples, if the TRS (TRS 650-c and / or TRS 650-d) is punctured, the threshold TRS bandwidth may not be configured, which in some cases may result in fewer frequency domain resources for a particular TRS. For TRSs with small bandwidths, the delay spread estimation accuracy may be lower.

[0130] In some examples, if the TRS (TRS 650-c and / or TRS 650-d) is punctured, the UE 115 may monitor and / or the network entity 105 may send the TRS if the remaining aggregate bandwidth (across both downlink subband 620-a and downlink subband 620-b) meets a threshold. For example, the threshold may be configured in RRC signaling. For example, if the cumulative bandwidth of bandwidth 655-a and bandwidth 655-b meets a threshold, the UE 115 may monitor and / or the network entity 105 may send TRS 650-c and / or TRS 650-d.

[0131] In some examples, if a TRS (TRS 650-c and / or TRS 650-d) is punctured, the UE 115 may monitor the TRS in a given downlink subband (e.g., downlink subband 620-a and downlink subband 620-b) and / or the network entity 105 may send the TRS in the given downlink subband if the bandwidth (e.g., bandwidth 655-a and bandwidth 655-b) meets the configured threshold. In some cases, if the bandwidth 655-b used for a TRS (e.g., TRS 650-c and / or TRS 650-d) in one downlink subband (e.g., downlink subband 620-b) meets a threshold, but the bandwidth 655-a used for the TRS in another downlink subband 620-a does not meet the threshold, the UE 115 may monitor the TRS in the downlink subband 620-b, and / or the network entity 105 may send the TRS in the downlink subband.

[0132] In some cases, if either the bandwidth 655-a used for a TRS (e.g., TRS 650-c and / or TRS 650-d) in the downlink subband 620-a or the bandwidth 655-b used for the TRS in the downlink subband 620-b does not meet a threshold (e.g., the frequency domain resources used for the TRS in both downlink subbands must meet a threshold in order for the TRS to be sent / received), the UE 115 and / or the network entity 105 may discard the TRS.

[0133] Figure 7 An example of a slot format 700-a and a slot format 700-b supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is illustrated. The slot formats 700-a and 700-b may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c.

[0134] In some examples, different frequency domain resources for TRS 650 may be defined differently in a full-duplex time slot to avoid losing full-duplex resources and maintain the accuracy of measuring delay spread. For example, time slot format 700-a includes a half-duplex downlink time slot 605-c and a SBFD time slot 610-c for a BWP 640-c of a UE. The half-duplex downlink time slot 605-c includes a downlink region 615-c. The SBFD time slot 610-c includes a downlink subband 620-e and an uplink subband 625-c. TRS 650-i and TRS 650-j may be scheduled in the half-duplex downlink time slot 605-c, and TRS 650-k and TRS 650-l may be scheduled in the SBFD time slot 610-c.

[0135] In some examples, if UE 115 is scheduled with a TRS opportunity that overlaps with a guard band or an uplink subband (e.g., uplink subband 625-c), UE 115 and / or network entity 105 may interpret the resources of the scheduled TRS opportunity according to the slot type. For example, the starting resource blocks of TRS 650-k and TRS 650-1 may be interpreted differently in SBFD slot 610-c than TRS 650-i and TRS 650-j in half-duplex downlink slot 605-c (e.g., the starting resource blocks may be shifted so that TRS 650-k and TRS 650-1 are in downlink subband 620-e).

[0136] The time slot format 700-b includes an SBFD time slot 610-d and an SBFD time slot 610-e for the BWP 640-d of the UE. The SBFD time slot 610-d includes a downlink subband 620-f and an uplink subband 625-d. The SBFD time slot 610-e includes a downlink subband 620-g and an uplink subband 625-e. The positions of the downlink subbands (downlink subband 620-f and downlink subband 620-g) and the uplink subbands (uplink subband 625-d and uplink subband 625-e) can be swapped between the SBFD time slot 610-d and the SBFD time slot 610-e. TRS 650 - m and TRS 650 - n may be scheduled in SBFD time slot 610 - d , and TRS 650 - o and TRS 650 - p may be scheduled in SBFD time slot 610 - e .

[0137] In some cases, UE 115 and network entity 105 may apply a defined frequency hopping pattern across half-duplex and SBFD time slots, e.g., as shown in time slot format 700-a, such that a TRS is scheduled in the downlink resources of the time slot. In some examples, UE 115 and network entity 105 may apply a defined frequency hopping pattern across different types of SBFD time slots, e.g., as shown in time slot format 700-b, such that a TRS is scheduled in the downlink subband of a SBFD time slot.

[0138] Figure 8 An example of a slot format 800 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is illustrated. The slot format 800 may implement aspects of the wireless communication system 100, the wireless communication system 300-a, the wireless communication system 300-b, or the wireless communication system 300-c.

[0139] The time slot 805 may include a half-duplex symbol 820 and a SBFD symbol 825 (e.g., a D+U symbol) for the BWP 640-e of the UE 115. The SBFD symbol 825 may include a downlink subband 620-h, a downlink subband 620-i, an uplink subband 625-f, and a guard band (a guard band 630-e and a guard band 630-f). Within the time slot 805, a TRS 650-q may be scheduled in the half-duplex symbol 820 (e.g., in the downlink symbol), and a TRS 650-r may be scheduled in the SBFD symbol 825. The TRS 650-r may be scheduled in the uplink subband 625-f and / or the guard band (the guard band 630-e and / or the guard band 630-f), which may affect the accuracy of the estimation of the Doppler spread.

[0140] As described with reference to TRS scheduled across half-duplex timeslots and SBFD timeslots, in some examples, the network entity 105 may not configure the TRS 650-r to overlap with the uplink subband 625-f and / or the guard bands (guard bands 630-e and guard bands 630-f) (e.g., such overlap is an error condition). As described with reference to TRS scheduled across half-duplex timeslots and SBFD timeslots, in some examples, the UE 115 and / or the network entity 105 may discard the TRS 650-r based on the TRS 650-r overlapping with the uplink subband 625-f and / or the guard bands (guard bands 630-e and guard bands 630-f). As described with reference to TRS scheduled across half-duplex timeslots and SBFD timeslots, in some examples, UE 115 and / or network entity 105 may puncture TRS 650-r so that TRS 650-r is received in one or both of downlink subband 620-h or downlink subband 620-i.

[0141] Fig. 9An example of a process flow 900 for supporting TRS in a full-duplex network according to one or more aspects of the present disclosure is illustrated. The process flow 900 may include a UE 115-g, which may be an example of a UE 115 as described herein. The process flow 900 may include a network entity 105-f, which may be an example of a network entity 105 as described herein. In the following description of the process flow 900, operations between the network entity 105-f and the UE 115-g may be sent in an order different from the example order shown, or operations performed by the network entity 105-f and the UE 115-g may be performed in a different order or at a different time. Some operations may also be omitted from the process flow 900, and other operations may be added to the process flow 900.

[0142] At 905, the UE 115-g may receive control signaling from the network entity 105-f that schedules a set of TRSs in a time slot. The time slot may include an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband. A portion of the TRSs in the set of TRSs may overlap with at least one of the uplink subband or the guard band.

[0143] At 910, the UE 115-g may adjust monitoring of the TRS based on the portion of the TRS overlapping with at least one of a guard band or an uplink subband.

[0144] At 915 , the network entity 105 - f may adjust the transmission of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband.

[0145] In some examples, at 920 , the network entity 105 - f may send the TRS according to the adjustment at 915 , and the UE 115 - g may receive the TRS according to the adjusted monitoring at 910 .

[0146] In some examples, UE 115-g may refrain from monitoring the TRS based on the portion of the TRS overlapping with an uplink subband or a guard band.

[0147] In some examples, the network entity 105 - f may suppress transmission of the TRS based on the portion of the TRS overlapping with at least one of a guard band or an uplink subband.

[0148] In some examples, UE 115-g may suppress monitoring of the portion of the TRS, and may receive the TRS via a second portion of the TRS that overlaps with a downlink subband. In some examples, UE 115-g may receive the TRS via the second portion based on the second portion satisfying a threshold bandwidth. In some examples, UE 115-g may receive the TRS via a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency (e.g., in the frequency domain). In some cases, UE 115-g may receive the TRS via the second portion and the third portion based on the second portion and the third portion satisfying a cumulative threshold bandwidth. In some cases, UE 115-g may receive the TRS via the second portion and the third portion based on the second portion and the third portion each satisfying a threshold bandwidth. In some examples, UE 115-g may refrain from monitoring a third portion of the TRS that overlaps with a second downlink subband of the timeslot, wherein the second downlink subband is not contiguous in frequency to the downlink subband. In some cases, refraining from monitoring the third portion includes refraining from monitoring the third portion based on the second portion including more TRS resources than the third portion. In some cases, refraining from monitoring the third portion includes refraining from monitoring the third portion based on the third portion failing to meet a threshold bandwidth.

[0149] In some examples, the network entity 105-f may suppress transmission of the portion of the TRS and transmit the TRS via a second portion of the TRS that overlaps the downlink subband. In some examples, the network entity 105-f may transmit the TRS via the second portion based on the second portion satisfying a threshold bandwidth. In some examples, the network entity 105-f may transmit the TRS via a third portion of the TRS that overlaps a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency. In some cases, the network entity 105-f may transmit the TRS via the second portion and the third portion based on the second portion and the third portion satisfying a cumulative threshold bandwidth. In some cases, the network entity 105-f may transmit the TRS via the second portion and the third portion based on the second portion and the third portion each satisfying a threshold bandwidth. In some examples, the network entity 105-f may suppress transmission of a third portion of the TRS that overlaps with a second downlink subband of the time slot, wherein the second downlink subband is not contiguous in frequency to the downlink subband. In some cases, suppressing transmission of the third portion includes suppressing transmission of the third portion based on the second portion including more TRS resources than the third portion. In some cases, suppressing transmission of the third portion includes suppressing transmission of the third portion based on the third portion failing to meet a threshold bandwidth.

[0150] In some cases, adjusting monitoring of the TRS includes shifting the monitored resources for the TRS in frequency so that the monitored resources for the TRS are within a downlink subband. In some cases, adjusting the transmission of the TRS includes shifting the monitored resources for the TRS in frequency so that the monitored resources for the TRS are within a downlink subband.

[0151] In some examples, UE 115 - g may receive and network entity 105 - f may send a second TRS from a set of scheduled TRSs in a half-duplex symbol of the time slot, and the TRS is scheduled in a SBFD symbol of the time slot.

[0152] In some examples, the time slot is a SBFD time slot. In some examples, the control signaling at 905 may include an indication of a frequency hopping pattern to be applied to TRS in the SBFD time slot and the half-duplex time slot. Adjusting the monitoring TRS and adjusting the transmission of the TRS may include applying the frequency hopping pattern to the TRS based on the time slot being a SBFD time slot so that the TRS is within the downlink subband.

[0153] Fig.10 A block diagram 1000 of a device 1005 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1005 may be an example of aspects of a UE 115 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0154] The receiver 1010 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to TRS in full-duplex operation), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1005. The receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0155] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to TRS in full-duplex operation), user data, control information, or any combination thereof. In some examples, the transmitter 1015 may be co-located with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0156] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of TRS in full-duplex operation as described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0157] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof that is configured to or otherwise supports components for performing the functions described in the present disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0158] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations thereof, or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0159] In some examples, communication manager 1020 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with receiver 1010, transmitter 1015, or both. For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in conjunction with receiver 1010, transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0160] The communication manager 1020 may support wireless communication at a UE according to examples as disclosed herein. For example, the communication manager 1020 may be configured to or otherwise support components for receiving control signaling from a network entity for scheduling a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The communication manager 1020 may be configured to or otherwise support components for adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0161] By including or configuring a communication manager 1020 according to examples as described herein, a device 1005 (e.g., a processor controlling or otherwise coupled to a receiver 1010, a transmitter 1015, a communication manager 1020, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0162] Fig.11 A block diagram 1100 of a device 1105 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1105 may be an example of aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0163] The receiver 1110 may provide means for receiving information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to TRS in full-duplex operation), user data, control information, or any combination thereof. The information may be communicated to other components of the device 1105. The receiver 1110 may utilize a single antenna or a collection of multiple antennas.

[0164] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels related to TRS in full-duplex operation), user data, control information, or any combination thereof. In some examples, the transmitter 1115 may be co-located with the receiver 1110 in a transceiver module. The transmitter 1115 may utilize a single antenna or a collection of multiple antennas.

[0165] Device 1105 or its various components may be examples of components for performing various aspects of TRS in full-duplex operation as described herein. For example, communication manager 1120 may include TRS scheduling manager 1125, TRS monitoring adjustment manager 1130, or any combination thereof. Communication manager 1120 may be an example of various aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 1110, transmitter 1115, or both. For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or integrate with receiver 1110, transmitter 1115, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0166] The communication manager 1120 may support wireless communications at a UE according to examples as disclosed herein. The TRS scheduling manager 1125 may be configured to or otherwise support components for receiving control signaling from a network entity for scheduling a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The TRS monitoring adjustment manager 1130 may be configured to or otherwise support components for adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0167] Fig.12 A block diagram 1200 of a communication manager 1220 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The communication manager 1220 can be an example of aspects of the communication manager 1020, the communication manager 1120, or both as described herein. The communication manager 1220 or its various components can be examples of components for performing various aspects of TRS in full-duplex operation as described herein. For example, the communication manager 1220 may include a TRS scheduling manager 1225, a TRS monitoring adjustment manager 1230, a TRS suppression manager 1235, a downlink overlap manager 1240, a shift manager 1245, a threshold bandwidth manager 1250, a non-contiguous downlink sub-band manager 1255, a frequency hopping manager 1260, or any combination thereof. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0168] The communication manager 1220 may support wireless communications at a UE according to examples as disclosed herein. The TRS scheduling manager 1225 may be configured to or otherwise support components for receiving control signaling from a network entity for scheduling a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The TRS monitoring adjustment manager 1230 may be configured to or otherwise support components for adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0169] In some examples, the TRS suppression manager 1235 can be configured or otherwise support components for suppressing monitoring for the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband.

[0170] In some examples, TRS suppression manager 1235 may be configured or otherwise support components for suppressing monitoring for the portion of the TRS. In some examples, downlink overlap manager 1240 may be configured or otherwise support components for receiving the TRS via a second portion of the TRS that overlaps with a downlink subband.

[0171] In some examples, to support receiving the TRS via the second portion, the threshold bandwidth manager 1250 may be configured or otherwise support components for receiving the TRS based on the second portion satisfying a threshold bandwidth.

[0172] In some examples, the non-contiguous downlink sub-band manager 1255 may be configured or otherwise support components for receiving the TRS via a third portion of the TRS that overlaps with a second downlink sub-band of the time slot, where the second downlink sub-band is not contiguous in frequency to the downlink sub-band.

[0173] In some examples, to support receiving the TRS via the second portion and the third portion, the threshold bandwidth manager 1250 may be configured or otherwise support components for receiving the TRS based on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0174] In some examples, to support receiving the TRS via the second portion and the third portion, the threshold bandwidth manager 1250 may be configured or otherwise support components for receiving the TRS based on the second portion and the third portion each satisfying a threshold bandwidth.

[0175] In some examples, the non-contiguous downlink sub-band manager 1255 may be configured or otherwise support components for refraining from monitoring a third portion of the TRS that overlaps with a second downlink sub-band of the time slot, where the second downlink sub-band is not contiguous in frequency to the downlink sub-band.

[0176] In some examples, to support refraining from monitoring the third portion, the TRS suppression manager 1235 may be configured or otherwise support components for refraining from monitoring the third portion based on the second portion including more TRS resources than the third portion.

[0177] In some examples, to support refraining from monitoring the third portion, threshold bandwidth manager 1250 may be configured or otherwise support components for refraining from monitoring the third portion based on the third portion failing to meet a threshold bandwidth.

[0178] In some examples, to support adjusting monitoring of the TRS, the shift manager 1245 may be configured or otherwise support components for shifting the monitored resources for the TRS in frequency so that the monitored resources for the TRS are within the downlink subband.

[0179] In some examples, the TRS scheduling manager 1225 may be configured to or support components for receiving a second TRS of a scheduled set of TRSs in a half-duplex symbol of the time slot, wherein the TRS is scheduled in a SBFD symbol of the time slot.

[0180] In some examples, the time slot comprises a SBFD time slot.

[0181] In some examples, to support receiving the control signaling, the frequency hopping manager 1260 may be configured as or otherwise support components for receiving an indication of a frequency hopping pattern to be applied to a TRS in an SBFD time slot and a half-duplex time slot, wherein adjusting monitoring of the TRS includes applying the frequency hopping pattern to the TRS so that the TRS is within a downlink subband based on the time slot being a SBFD time slot.

[0182] Fig.13A diagram of a system 1300 including a device 1305 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein, or include components thereof. The device 1305 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 1305 may include components for two-way voice and data communications, including components for sending and receiving communications, such as a communication manager 1320, an input / output (I / O) controller 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, and a processor 1340. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1345).

[0183] I / O controller 1310 can manage input and output signals for device 1305. I / O controller 1310 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1310 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1310 can utilize an operating system, such as or another known operating system. Additionally or alternatively, I / O controller 1310 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1310 may be implemented as part of a processor, such as processor 1340. In some cases, a user may interact with device 1305 via I / O controller 1310 or via hardware components controlled by I / O controller 1310.

[0184] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, a wired or wireless link, as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1325 for transmission; and demodulating packets received from one or more antennas 1325. The transceiver 1315 or the transceiver 1315 and one or more antennas 1325 may be examples of transmitters 1015, transmitters 1115, receivers 1010, receivers 1110, or any combination thereof or components thereof as described herein.

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

[0186] The processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) so that the device 1305 performs various functions (e.g., various functions or tasks of supporting TRS in full-duplex operation). For example, the device 1305 or a component of the device 1305 may include a processor 1340 and a memory 1330 coupled to or coupled to the processor 1340, and the processor 1340 and the memory 1330 are configured to perform the various functions described herein.

[0187] The communication manager 1320 may support wireless communications at a UE according to examples as disclosed herein. For example, the communication manager 1320 may be configured to or otherwise support components for receiving control signaling from a network entity for scheduling a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The communication manager 1320 may be configured to or otherwise support components for adjusting monitoring of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0188] By including or configuring a communication manager 1320 according to examples as described herein, the device 1305 can support techniques for reducing power consumption, more efficiently utilizing communication resources, and improving utilization of processing capabilities.

[0189] In some examples, the communication manager 1320 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the transceiver 1315, one or more antennas 1325, or any combination thereof. Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the processor 1340, the memory 1330, the code 1335, or any combination thereof. For example, the code 1335 may include instructions executable by the processor 1340 to cause the device 1305 to perform various aspects of TRS in full-duplex operation as described herein, or the processor 1340 and the memory 1330 may be otherwise configured to perform or support such operations.

[0190] Fig.14 A block diagram 1400 of a device 1405 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1405 may be an example of aspects of the network entity 105 as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. The device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] Receiver 1410 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of device 1405. In some examples, receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0192] The transmitter 1415 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1405. For example, the transmitter 1415 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, the transmitter 1415 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1415 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0193] The communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of TRS in full-duplex operation as described herein. For example, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0194] In some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic components, discrete hardware components, or any combination thereof configured as or otherwise supporting components for performing the functions described in the present disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory by the processor).

[0195] Additionally or alternatively, in some examples, the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1420, the receiver 1410, the transmitter 1415, or various combinations thereof, or components thereof may be performed by a general purpose processor (e.g., configured as or otherwise supporting components for performing the functions described in the present disclosure), a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices.

[0196] In some examples, communication manager 1420 may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1410, transmitter 1415, or both. For example, communication manager 1420 may receive information from receiver 1410, transmit information to transmitter 1415, or be integrated in conjunction with receiver 1410, transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0197] The communication manager 1420 may support wireless communications at a network entity according to examples as disclosed herein. For example, the communication manager 1420 may be configured to or otherwise support components for sending control signaling to a UE that schedules a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The communication manager 1420 may be configured to or otherwise support components for adjusting the sending of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0198] By including or configuring a communication manager 1420 according to examples as described herein, a device 1405 (e.g., a processor controlling or otherwise coupled to a receiver 1410, a transmitter 1415, a communication manager 1420, or a combination thereof) may support techniques for more efficiently utilizing communication resources.

[0199] Fig.15 A block diagram 1500 of a device 1505 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1505 may be an example of aspects of the device 1405 or the network entity 105 as described herein. The device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. The device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0200] Receiver 1510 may provide means for obtaining (e.g., receiving, determining, identifying) 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). The information may be passed to other components of device 1505. In some examples, receiver 1510 may support obtaining information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1510 may support obtaining information by receiving signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof.

[0201] The transmitter 1515 may provide a means for outputting (e.g., sending, providing, conveying, transmitting) information generated by other components of the device 1505. For example, the transmitter 1515 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, the transmitter 1515 may support outputting information by sending signals via one or more antennas. Additionally or alternatively, the transmitter 1515 may support outputting information by sending signals via one or more wired (e.g., electrical, optical) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1515 and the receiver 1510 may be co-located in a transceiver, which may include a modem or be coupled to a modem.

[0202] Device 1505 or its various components may be examples of components for performing various aspects of TRS in full-duplex operation as described herein. For example, communication manager 1520 may include TRS scheduling manager 1525, TRS transmission adjustment manager 1530, or any combination thereof. Communication manager 1520 may be an example of various aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise cooperating with receiver 1510, transmitter 1515, or both. For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or integrate with receiver 1510, transmitter 1515, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0203] The communication manager 1520 may support wireless communication at a network entity according to examples as disclosed herein. The TRS scheduling manager 1525 may be configured to or otherwise support components for sending control signaling to a UE for a set of TRSs in a scheduled time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The TRS transmission adjustment manager 1530 may be configured to or otherwise support components for adjusting transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0204] Fig.16A block diagram 1600 of a communication manager 1620 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The communication manager 1620 can be an example of aspects of the communication manager 1420, the communication manager 1520, or both as described herein. The communication manager 1620 or its various components can be examples of components for performing various aspects of TRS in full-duplex operation as described herein. For example, the communication manager 1620 may include a TRS scheduling manager 1625, a TRS transmission adjustment manager 1630, a TRS suppression manager 1635, a downlink overlap manager 1640, a shift manager 1645, a frequency hopping manager 1650, a threshold manager 1655, a non-contiguous downlink sub-band manager 1660, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), which communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with the network entity 105, between devices, components, or virtualized components associated with the network entity 105), or any combination thereof.

[0205] The communication manager 1620 may support wireless communications at a network entity according to examples as disclosed herein. The TRS scheduling manager 1625 may be configured to or otherwise support components for sending control signaling to a UE for a set of TRSs in a scheduled time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The TRS transmission adjustment manager 1630 may be configured to or otherwise support components for adjusting transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0206] In some examples, the TRS suppression manager 1635 may be configured or otherwise support components for suppressing transmission of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband.

[0207] In some examples, TRS suppression manager 1635 may be configured or otherwise support means for suppressing transmission of the portion of the TRS. In some examples, downlink overlap manager 1640 may be configured or otherwise support means for transmitting the TRS via a second portion of the TRS that overlaps with a downlink subband.

[0208] In some examples, to support sending the TRS via the second portion, the threshold manager 1655 may be configured or otherwise support components for sending the TRS based on the second portion satisfying a threshold bandwidth.

[0209] In some examples, the non-contiguous downlink sub-band manager 1660 may be configured or otherwise support components for transmitting the TRS via a third portion of the TRS that overlaps with a second downlink sub-band of the time slot, where the second downlink sub-band is not contiguous in frequency to the downlink sub-band.

[0210] In some examples, to support sending the TRS via the second portion and the third portion, the threshold manager 1655 may be configured or otherwise support components for sending the TRS based on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0211] In some examples, to support sending the TRS via the second portion and the third portion, the threshold manager 1655 may be configured or otherwise support components for sending the TRS based on the second portion and the third portion each satisfying a threshold bandwidth.

[0212] In some examples, the non-contiguous downlink subband manager 1660 may be configured to or otherwise support components for suppressing transmission of a third portion of the TRS that overlaps with a second downlink subband of the time slot, where the second downlink subband is not contiguous in frequency to the downlink subband.

[0213] In some examples, to support suppressing transmission of the third portion, the TRS suppression manager 1635 may be configured or otherwise support components for suppressing transmission of the third portion based on the second portion including more TRS resources than the third portion.

[0214] In some examples, to support suppressing transmission of the third portion, threshold manager 1655 may be configured or otherwise support components for suppressing transmission of the third portion based on the third portion failing to meet a threshold bandwidth.

[0215] In some examples, to support adjusting the transmission of the TRS, the shift manager 1645 may be configured or otherwise support components for shifting the TRS in frequency so that the TRS is within the downlink subband.

[0216] In some examples, the TRS scheduling manager 1625 may be configured to or support components for transmitting a second TRS of a scheduled set of TRSs in a half-duplex symbol of the time slot, where the TRS is scheduled in a SBFD symbol of the time slot.

[0217] In some examples, the time slot comprises a SBFD time slot.

[0218] In some examples, to support sending control signaling, the frequency hopping manager 1650 may be configured to or otherwise support components for sending an indication of a frequency hopping pattern to be applied to a TRS in an SBFD time slot and a half-duplex time slot, wherein adjusting transmission of the TRS includes applying the frequency hopping pattern to the TRS so that the TRS is within a downlink subband based on the time slot being a SBFD time slot.

[0219] Fig.17 A diagram of a system 1700 including a device 1705 supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The device 1705 may be an example of a device 1405, a device 1505, or a network entity 105 as described herein, or include components thereof. The device 1705 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication through one or more wired interfaces, through one or more wireless interfaces, or any combination thereof. The device 1705 may include components that support output and acquisition of communications, such as a communication manager 1720, a transceiver 1710, an antenna 1715, a memory 1725, a code 1730, and a processor 1735. These components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1740).

[0220] The transceiver 1710 may support bidirectional communication via a wired link, a wireless link, or both as described herein. In some examples, the transceiver 1710 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, the transceiver 1710 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1705 may include one or more antennas 1715, which may be capable of (e.g., concurrently) sending or receiving wireless transmissions. The transceiver 1710 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1715, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1715, from a wired receiver); and demodulating the signal. In some implementations, the transceiver 1710 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1715 configured to support various receiving or obtaining operations, or one or more interfaces coupled to one or more antennas 1715 configured to support various sending or outputting operations, or a combination thereof. In some implementations, the transceiver 1710 may include or be configured to be coupled to one or more processors or memory components, which are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some implementations, the transceiver 1710, or the transceiver 1710 and one or more antennas 1715, or the transceiver 1710 and one or more antennas 1715 and one or more processors or memory components (e.g., processor 1735 or memory 1725 or both) may be included in a chip or chip assembly installed in the device 1705. In some examples, the transceiver may be operable to support communications via one or more communication links (eg, communication link 125, backhaul communication link 120, midhaul communication link 162, fronthaul communication link 168).

[0221] Memory 1725 may include RAM and ROM. Memory 1725 may store computer-readable, computer-executable code 1730 including instructions that, when executed by processor 1735, cause device 1705 to perform various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by processor 1735, but may (e.g., when compiled and executed) cause a computer to perform the functions described herein. In some cases, memory 1725 may also include, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0222] The processor 1735 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1735 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into the processor 1735. The processor 1735 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1725) so that the device 1705 performs various functions (e.g., various functions or tasks of supporting TRS in full-duplex operation). For example, the device 1705 or a component of the device 1705 may include a processor 1735 and a memory 1725 coupled to the processor 1735, and the processor 1735 and the memory 1725 are configured to perform the various functions described herein. The processor 1735 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, a virtual machine, or a container instance) that may host functions for performing the functions of the device 1705 (e.g., by executing code 1730). The processor 1735 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1705 (such as in the memory 1725). In some specific implementations, the processor 1735 may be a component of a processing system. A processing system may generally refer to a system or a series of machines or components that receive inputs and process these inputs to produce a set of outputs (which may be delivered to, for example, other systems or components of the device 1705). For example, the processing system of the device 1705 may refer to a system including various other components or subcomponents of the device 1705 (such as the processor 1735, or the transceiver 1710, or the communication manager 1720, or other components or combinations of components of the device 1705). The processing system of device 1705 can be docked with other components of device 1705, and can process information (such as input or signal) received from other components or output information to other components. For example, a chip or modem of device 1705 may include a processing system and one or more interfaces for outputting information or for obtaining information or both. One or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information or the same interface configured to output information and obtain information, as well as other specific implementations. In some specific implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a transmitter, so that device 1705 can send information output from the chip or modem.Additionally or alternatively, in some implementations, one or more interfaces may refer to an interface between a processing system of a chip or modem and a receiver, such that the device 1705 may obtain information or signal input, and the information may be passed to the processing system. One of ordinary skill in the art will readily recognize that a first interface may also obtain information or signal input, and a second interface may also output information or signal output.

[0223] In some examples, bus 1740 may support communications of a protocol layer (e.g., within a protocol layer) of a protocol stack. In some examples, bus 1740 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of device 1705, or communications performed between different components of device 1705 that may be co-located or may be located in different locations (e.g., where device 1705 may refer to a system in which one or more of communication manager 1720, transceiver 1710, memory 1725, code 1730, and processor 1735 may be located in one of the different components or divided between the different components).

[0224] In some examples, communication manager 1720 may manage aspects of communications with core network 130 (e.g., via one or more wired or wireless backhaul links). For example, communication manager 1720 may manage delivery of data communications for client devices such as one or more UEs 115. In some examples, communication manager 1720 may manage communications with other network entities 105 and may include a controller or scheduler for controlling communications with UE 115 in coordination with other network entities 105. In some examples, communication manager 1720 may support an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between network entities 105.

[0225] The communication manager 1720 may support wireless communications at a network entity according to examples as disclosed herein. For example, the communication manager 1720 may be configured to or otherwise support components for sending control signaling to a UE that schedules a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of a TRS in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The communication manager 1720 may be configured to or otherwise support components for adjusting the transmission of the TRS based on the portion of the TRS overlapping with at least one of the guard band or the uplink subband.

[0226] By including or configuring a communication manager 1720 according to examples as described herein, the device 1705 can support techniques for reducing power consumption, more efficiently utilizing communication resources, and improving utilization of processing capabilities.

[0227] In some examples, the communication manager 1720 may be configured to perform various operations (e.g., receive, obtain, monitor, output, transmit) using or otherwise cooperating with the transceiver 1710, one or more antennas 1715 (e.g., where applicable), or any combination thereof. Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by the transceiver 1710, the processor 1735, the memory 1725, the code 1730, or any combination thereof. For example, the code 1730 may include instructions that can be executed by the processor 1735 to cause the device 1705 to perform various aspects of TRS in full-duplex operation as described herein, or the processor 1735 and the memory 1725 may be otherwise configured to perform or support such operations.

[0228] Fig.18 A flow chart illustrating a method 1800 for supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0229] At 1805, the method may include receiving control signaling from a network entity to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The operations of 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Fig.12 The TRS schedule manager 1225 described here performs.

[0230] At 1810, the method may include adjusting monitoring of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband. The operations of 1810 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed as described in reference to Fig.12 The TRS monitoring adjustment manager 1230 described performs.

[0231] Fig.19 A flowchart illustrating a method 1900 for supporting TRS in full-duplex operation according to one or more aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE or a component thereof as described in reference to Figures 1 to 13 The described UE 115 performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the described functions.

[0232] At 1905, the method may include receiving control signaling from a network entity to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The operations of 1905 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Fig.12 The TRS schedule manager 1225 described here performs.

[0233] At 1910, the method may include adjusting monitoring of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband. The operations of 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Fig.12 The TRS monitoring adjustment manager 1230 described performs.

[0234] At 1915, the method may include refraining from monitoring the portion of the TRS. The operations of 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Fig.12 The described TRS suppression manager 1235 performs.

[0235] At 1920, the method may include receiving the TRS via a second portion of the TRS that overlaps the downlink subband. The operations of 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Fig.12 The described downlink overlay manager 1240 performs.

[0236] Fig. 202000 is a flowchart illustrating a method 2000 for supporting TRS in full-duplex operation according to one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2000 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 9 as well as Figures 14 to 17 The described network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0237] At 2005, the method may include sending control signaling to the UE to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The operations of 2005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Fig.16 The TRS schedule manager 1625 described here performs.

[0238] At 2010, the method may include adjusting the transmission of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband. The operations of 2010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Fig.16 The TRS transmission adjustment manager 1630 described performs.

[0239] Fig.21 2100 is a flowchart illustrating a method 2100 for supporting TRS in full-duplex operation according to one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a network entity or a component thereof as described herein. For example, the operations of the method 2100 may be implemented by a network entity or a component thereof as described in reference to Figures 1 to 9 as well as Figures 14 to 17 The described network entity performs. In some examples, the network entity may execute an instruction set to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform various aspects of the described functions.

[0240] At 2105, the method may include sending control signaling to the UE to schedule a set of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled set of TRSs overlaps with at least one of the guard band or the uplink subband. The operations of 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed as described in reference to Fig.16 The TRS schedule manager 1625 described here performs.

[0241] At 2110, the method may include adjusting the transmission of the TRS based on the portion of the TRS overlapping at least one of a guard band or an uplink subband. The operations of 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Fig.16 The TRS transmission adjustment manager 1630 described performs.

[0242] At 2115, the method may include suppressing transmission of the portion of the TRS. The operations of 2115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Fig.16 The described TRS suppression manager 1635 executes.

[0243] At 2120, the method may include transmitting the TRS via a second portion of the TRS that overlaps the downlink subband. The operations of 2120 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Fig.16 The described downlink overlay manager 1640 performs.

[0244] The following provides an overview of various aspects of the disclosure:

[0245] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control signaling from a network entity for scheduling a group of TRSs in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjusting monitoring of the TRS based at least in part on the overlap of the portion of the TRS with at least one of the guard band or the uplink subband.

[0246] Aspect 2: The method of aspect 1, further comprising: refraining from monitoring the TRS based at least in part on the portion of the TRS overlapping at least one of the guard band or the uplink subband.

[0247] Aspect 3: The method according to aspect 1, further comprising: refraining from monitoring the portion of the TRS; and receiving the TRS via a second portion of the TRS overlapping with the downlink subband.

[0248] Aspect 4: The method of aspect 3, wherein receiving the TRS via the second portion comprises receiving the TRS based at least in part on the second portion satisfying a threshold bandwidth.

[0249] Aspect 5: The method according to any one of aspects 3 to 4 further comprises: receiving the TRS via a third portion of the TRS overlapping with a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency.

[0250] Aspect 6: The method of aspect 5, wherein receiving the TRS via the second portion and the third portion comprises receiving the TRS based at least in part on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0251] Aspect 7: The method of aspect 5, wherein receiving the TRS via the second portion and the third portion comprises receiving the TRS based at least in part on the second portion and the third portion each satisfying a threshold bandwidth.

[0252] Aspect 8: The method according to any one of aspects 3 to 4, further comprising: suppressing monitoring of a third portion of the TRS overlapping with a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency.

[0253] Aspect 9: The method of aspect 8, wherein refraining from monitoring the third portion comprises refraining from monitoring the third portion based at least in part on the second portion including more TRS resources than the third portion.

[0254] Aspect 10: The method according to any one of aspects 8 to 9, wherein refraining from monitoring the third portion comprises refraining from monitoring the third portion based at least in part on a failure of the third portion to satisfy a threshold bandwidth.

[0255] Aspect 11: The method according to aspect 1, wherein adjusting the monitoring of the TRS comprises: shifting the monitored resources for the TRS in frequency so that the monitored resources for the TRS are within the downlink sub-band.

[0256] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: receiving a second TRS in a scheduled set of TRSs in a half-duplex symbol of the time slot, wherein the TRS is scheduled in a SBFD symbol of the time slot.

[0257] Aspect 13: The method according to any one of aspects 1 to 12, wherein the time slot comprises a SBFD time slot.

[0258] Aspect 14: A method according to Aspect 13, wherein receiving the control signaling includes: receiving an indication of a frequency hopping pattern to be applied to TRS in SBFD time slots and half-duplex time slots, wherein adjusting the monitoring of the TRS includes: applying the frequency hopping pattern to the TRS so that the TRS is within the downlink subband based at least in part on the fact that the time slot is a SBFD time slot.

[0259] Aspect 15: A method for wireless communication at a network entity, the method comprising: sending control signaling of a group of TRSs in a scheduled time slot to a UE, wherein the time slot includes an uplink subband, a downlink subband, and a guard band located between the uplink subband and the downlink subband, wherein a portion of the TRSs in the scheduled group of TRSs overlaps with at least one of the guard band or the uplink subband; and adjusting the sending of the TRSs at least partially based on the overlap of the portion of the TRSs with at least one of the guard band or the uplink subband.

[0260] Aspect 16: The method of aspect 15, further comprising: suppressing transmission of the TRS based at least in part on the portion of the TRS overlapping at least one of the guard band or the uplink subband.

[0261] Aspect 17: The method according to aspect 15, further comprising: suppressing transmission of the portion of the TRS; and transmitting the TRS via a second portion of the TRS overlapping with the downlink subband.

[0262] Aspect 18: The method of aspect 17, wherein sending the TRS via the second portion comprises sending the TRS based at least in part on the second portion satisfying a threshold bandwidth.

[0263] Aspect 19: The method according to any one of Aspects 17 to 18, further comprising: sending the TRS via a third portion of the TRS overlapping with a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency.

[0264] Aspect 20: The method of aspect 19, wherein sending the TRS via the second portion and the third portion comprises sending the TRS based at least in part on the second portion and the third portion satisfying a cumulative threshold bandwidth.

[0265] Aspect 21: The method of aspect 19, wherein sending the TRS via the second portion and the third portion comprises sending the TRS based at least in part on the second portion and the third portion each satisfying a threshold bandwidth.

[0266] Aspect 22: The method according to any one of aspects 17 to 18, further comprising: suppressing the transmission of a third portion of the TRS overlapping with a second downlink subband of the time slot, wherein the second downlink subband is not adjacent to the downlink subband in frequency.

[0267] Aspect 23: The method according to aspect 22, wherein suppressing the transmission of the third part includes suppressing the transmission of the third part based at least in part on the fact that the second part includes more TRS resources than the third part.

[0268] Aspect 24: The method according to any one of aspects 22 to 23, wherein suppressing the transmission of the third part comprises suppressing the transmission of the third part based at least in part on failure of the third part to meet a threshold bandwidth.

[0269] Aspect 25: The method according to aspect 15, wherein adjusting the transmission of the TRS includes: shifting the TRS in frequency so that the TRS is within the downlink sub-band.

[0270] Aspect 26: The method according to any one of aspects 15 to 25, the method further comprising: sending a second TRS of the scheduled set of TRSs in a half-duplex symbol of the time slot, wherein the TRS is scheduled in a SBFD symbol of the time slot.

[0271] Aspect 27: The method according to any one of aspects 15 to 26, wherein the time slot comprises a SBFD time slot.

[0272] Aspect 28: A method according to any one of Aspects 15 to 27, wherein sending the control signaling includes: sending an indication of a frequency hopping pattern to be applied to TRS in SBFD time slots and half-duplex time slots, wherein adjusting the sending of the TRS includes: applying the frequency hopping pattern to the TRS so that the TRS is within the downlink subband based at least in part on the fact that the time slot is a SBFD time slot.

[0273] Aspect 29: An apparatus for performing wireless communications at a UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 14.

[0274] Aspect 30: An apparatus for wireless communication at a UE, the apparatus comprising at least one component for performing the method according to any one of aspects 1 to 14.

[0275] Aspect 31: A non-transitory computer-readable medium storing a code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 14.

[0276] Aspect 32: An apparatus for performing wireless communications at a network entity, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 15 to 28.

[0277] Aspect 33: An apparatus for wireless communication at a network entity, the apparatus comprising at least one component for performing the method according to any one of aspects 15 to 28.

[0278] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to perform the method according to any one of aspects 15 to 28.

[0279] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. In addition, aspects from two or more methods may be combined.

[0280] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0281] The information and signals described herein may 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 specification may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0282] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The 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 in conjunction with a DSP core, or any other such configuration).

[0283] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as one or more instructions or codes of a computer-readable medium, or sent using one or more instructions or codes of a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these items. Features that implement the functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0284] Computer-readable medium includes both non-transient computer storage medium and communication medium, and the communication medium includes any medium that promotes the transfer of computer programs from one location to another location.Non-transient storage medium can be any available medium that can be accessed by a general or special computer.By way of example and not limitation, non-transient computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage device, disk storage device or other magnetic storage device, or can be used for carrying or storing desired program code components and any other non-transient medium that can be accessed by a general or special computer or a general or special processor in the form of an instruction or data structure.Moreover, any connection is appropriately referred to as computer-readable medium.For example, if software is sent 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 in the definition of computer-readable medium. As used herein, disks and optical disks include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks. Disks can reproduce data magnetically, and optical disks can reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0285] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items introduced by a phrase such as "at least one of..." or "one or more of...") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means 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, an example step 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 "based at least in part on".

[0286] The term "determine" or "determining" encompasses a wide variety of actions, and thus, "determining" may include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, database or other data structure), ascertaining, etc. Furthermore, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data stored in a memory), etc. Furthermore, "determining" may include parsing, obtaining, selecting, choosing, establishing, and other such similar actions.

[0287] In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label to distinguish between similar components. If only the first reference label is used in the specification, the description may apply to any of the similar components having the same first reference label, regardless of the second or other subsequent reference labels.

[0288] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples." The specific implementation includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0289] The description herein is provided to enable one of ordinary skill in the art to implement 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 may be applied to other variations without departing from the scope of the present disclosure. Thus, the present 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 method for wireless communication at a user equipment (UE), the method comprising: receiving control signaling from a network entity to schedule a set of tracking reference signals in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of tracking reference signals in the set of scheduled tracking reference signals overlaps with at least one of the guard band or the uplink subband; as well as Monitoring of the tracking reference signal is adjusted based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

2. The method according to claim 1, further comprising: Monitoring the tracking reference signal is refrained from based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

3. The method according to claim 1, further comprising: refraining from monitoring the portion of the tracking reference signal; as well as The tracking reference signal is received via a second portion of the tracking reference signal that overlaps with the downlink subband.

4. The method of claim 3, wherein receiving the tracking reference signal via the second portion comprises: The tracking reference signal is received based at least in part on the second portion satisfying a threshold bandwidth.

5. The method according to claim 3, further comprising: The tracking reference signal is received via a third portion of the tracking reference signal that overlaps with a second downlink subband of the time slot, wherein the second downlink subband is non-contiguous in frequency to the downlink subband.

6. The method of claim 5, wherein receiving the tracking reference signal via the second portion and the third portion comprises: The tracking reference signal is received based at least in part on the second portion and the third portion satisfying a cumulative threshold bandwidth.

7. The method of claim 5, wherein receiving the tracking reference signal via the second portion and the third portion comprises: The tracking reference signal is received based at least in part on the second portion and the third portion each satisfying a threshold bandwidth.

8. The method according to claim 3, further comprising: Monitoring a third portion of the tracking reference signal that overlaps with a second downlink subband of the time slot is refrained from, wherein the second downlink subband is non-contiguous in frequency to the downlink subband.

9. The method of claim 8, wherein inhibiting monitoring the third portion comprises: Monitoring the third portion is refrained from based at least in part on the second portion including more tracking reference signal resources than the third portion.

10. The method of claim 8, wherein inhibiting monitoring the third portion comprises: Monitoring of the third portion is refrained based at least in part on a failure of the third portion to satisfy a threshold bandwidth.

11. The method of claim 1 , wherein adjusting monitoring the tracking reference signal comprises: Monitored resources for the tracking reference signal are shifted in frequency so that the monitored resources for the tracking reference signal are within the downlink subband.

12. The method according to claim 1, further comprising: A second tracking reference signal of a set of scheduled tracking reference signals is received in a half-duplex symbol of the time slot, wherein the tracking reference signals are scheduled in a sub-band full-duplex symbol of the time slot.

13. The method of claim 1, wherein the time slot comprises a sub-band full-duplex time slot.

14. The method of claim 13, wherein receiving the control signaling comprises: Receiving an indication of a frequency hopping pattern to be applied to a tracking reference signal in a sub-band full-duplex time slot and a half-duplex time slot, wherein adjusting monitoring of the tracking reference signal comprises: applying the frequency hopping pattern to the tracking reference signal so that the tracking reference signal is within the downlink sub-band based at least in part on the time slot being a sub-band full-duplex time slot.

15. A method for wireless communication at a network entity, the method comprising: sending control signaling to a user equipment (UE) to schedule a set of tracking reference signals in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of tracking reference signals in the set of scheduled tracking reference signals overlaps with at least one of the guard band or the uplink subband; as well as The sending of the tracking reference signal is adjusted based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

16. The method according to claim 15, further comprising: Transmission of the tracking reference signal is suppressed based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

17. The method according to claim 15, further comprising: suppressing transmission of the portion of the tracking reference signal; as well as The tracking reference signal is sent via a second portion of the tracking reference signal overlapping with the downlink subband.

18. The method of claim 17, wherein sending the tracking reference signal via the second portion comprises: The tracking reference signal is sent based at least in part on the second portion satisfying a threshold bandwidth.

19. The method according to claim 17, further comprising: The tracking reference signal is sent via a third portion of the tracking reference signal that overlaps with a second downlink subband of the time slot, wherein the second downlink subband is non-contiguous in frequency to the downlink subband.

20. The method of claim 19, wherein sending the tracking reference signal via the second portion and the third portion comprises: The tracking reference signal is transmitted based at least in part on the second portion and the third portion satisfying a cumulative threshold bandwidth.

21. The method of claim 19, wherein sending the tracking reference signal via the second portion and the third portion comprises: The tracking reference signal is sent based at least in part on the second portion and the third portion each satisfying a threshold bandwidth.

22. The method according to claim 17, further comprising: Transmission of a third portion of the tracking reference signal that overlaps with a second downlink subband of the time slot is suppressed, wherein the second downlink subband is non-contiguous in frequency to the downlink subband.

23. The method of claim 22, wherein suppressing transmission of the third portion comprises: Transmission of the third portion is suppressed based at least in part on the second portion including more tracking reference signal resources than the third portion.

24. The method of claim 22, wherein suppressing transmission of the third portion comprises: Transmission of the third portion is suppressed based at least in part on a failure of the third portion to satisfy a threshold bandwidth.

25. The method of claim 15, wherein adjusting the sending of the tracking reference signal comprises: The tracking reference signal is shifted in frequency so that the tracking reference signal is within the downlink sub-band.

26. The method according to claim 15, further comprising: A second tracking reference signal of a set of scheduled tracking reference signals is transmitted in a half-duplex symbol of the time slot, wherein the tracking reference signals are scheduled in a sub-band full-duplex symbol of the time slot.

27. The method of claim 15, wherein the time slot comprises a sub-band full-duplex time slot.

28. The method of claim 15, wherein sending the control signaling comprises: An indication of a frequency hopping pattern to be applied to a tracking reference signal in a sub-band full-duplex time slot and a half-duplex time slot is sent, wherein adjusting the sending of the tracking reference signal comprises: applying the frequency hopping pattern to the tracking reference signal so that the tracking reference signal is within the downlink sub-band based at least in part on the time slot being a sub-band full-duplex time slot.

29. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: receiving control signaling from a network entity to schedule a set of tracking reference signals in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of tracking reference signals in the set of scheduled tracking reference signals overlaps with at least one of the guard band or the uplink subband; as well as Monitoring of the tracking reference signal is adjusted based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

30. An apparatus for wireless communication at a network entity, the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: sending control signaling to a user equipment (UE) to schedule a set of tracking reference signals in a time slot, wherein the time slot includes an uplink subband, a downlink subband, and a guard band between the uplink subband and the downlink subband, wherein a portion of tracking reference signals in the set of scheduled tracking reference signals overlaps with at least one of the guard band or the uplink subband; as well as The sending of the tracking reference signal is adjusted based at least in part on the portion of the tracking reference signal overlapping at least one of the guard band or the uplink subband.

Images