Handling uplink resource muting patterns overlapping with phase tracking reference signals in sub-band full duplex operation

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a configuration associated with an uplink phase tracking reference signal (PTRS). The UE may receive an indication of an uplink resource muting pattern, wherein the uplink resource muting pattern overlaps with a Physical Uplink Shared Channel (PUSCH) carrying an uplink PTRS in a sub-band full duplex operation. The UE may perform handling of an uplink resource muting mode overlapping with the PUSCH carrying the uplink PTRS. Numerous other aspects are described.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 495,342, filed October 26, 2023, entitled “Handling an Uplink Resource Muting Pattern That Overlaps with a Phase Tracking Reference Signal in a Subband Full-Duplex Operation”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and specifically to techniques, apparatus, and methods for handling uplink resource silence modes that overlap with the phase tracking reference signal (PTRS) in subband full-duplex (SBFD) operation. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] In some specific implementations, an apparatus for wireless communication at a user equipment (UE) includes: a memory; and one or more processors coupled to the memory and configured to cause the UE to: receive a configuration associated with an uplink phase tracking reference signal (PTRS); receive an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex (SBFD) operation; and perform disposal of the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0006] In some specific implementations, an apparatus for wireless communication at a network node includes: a memory; and one or more processors coupled to the memory and configured to cause the network node to: transmit a configuration associated with an uplink PTRS; transmit an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in SBFD operation; and receive the uplink PTRS at least in part based on the handling of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS.

[0007] In some specific implementations, a wireless communication method performed by a UE includes: receiving a configuration associated with an uplink PTRS; receiving an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and performing a disposition on the uplink resource silence mode that overlaps with the PUSCH carrying the uplink PTRS.

[0008] In some specific implementations, a method of wireless communication performed by a network node includes: transmitting a configuration associated with an uplink PTRS; transmitting an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and receiving the uplink PTRS based at least in part on the disposal of the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0009] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration associated with an uplink PTRS; receive an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and perform a disposition on the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0010] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: send a configuration associated with an uplink PTRS; send an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in SBFD operation; and receive the uplink PTRS at least in part based on the disposal of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS.

[0011] In some specific implementations, an apparatus for wireless communication includes: components for receiving a configuration associated with an uplink PTRS; components for receiving an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and components for performing disposal on the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0012] In some specific implementations, an apparatus for wireless communication includes: means for transmitting a configuration associated with an uplink PTRS; means for transmitting an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and means for receiving the uplink PTRS at least in part based on the handling of the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0013] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0014] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0015] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0016] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0017] Figure 2 This is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0018] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0019] Figure 4 This is a diagram illustrating an example of full-duplex (FD) communication according to this disclosure.

[0020] Figure 5 This is a diagram illustrating an example of FD communication according to this disclosure.

[0021] Figure 6This is a diagram illustrating an example of a phase tracking reference signal (PTRS) mode according to the present disclosure.

[0022] Figure 7 This is a diagram illustrating an example of PTRS insertion according to this disclosure.

[0023] Figure 8 This is a diagram illustrating an example of an uplink resource silent mode that overlaps with a Physical Uplink Shared Channel (PUSCH) carrying PTRS according to this disclosure.

[0024] Figures 9 to 10 This is a diagram illustrating an example of an uplink resource silent mode that overlaps with PTRS in subband full-duplex (SBFD) operation, according to this disclosure.

[0025] Figure 11 This is a flowchart illustrating an example procedure performed by a UE according to this disclosure.

[0026] Figure 12 This is a flowchart illustrating an example process performed by a network node according to this disclosure.

[0027] Figures 13 to 14 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0028] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0029] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0030] Full-duplex (FD) operation can involve in-band full-duplex (IBFD) operation, where transmission and reception can occur on the same time and frequency resources. Based at least in part on full or partial overlap, the downlink and uplink directions can share the same IBFD time / frequency resources. Alternatively, FD operation can involve sub-band full-duplex (SBFD) (or flexible duplex) operation, where transmission and reception can occur simultaneously but on different frequency resources. Downlink resources can be separated from uplink resources in the frequency domain. In SBFD operation, downlink and uplink frequency overlap may not occur.

[0031] Uplink resource silencing can be used to support cross-link interference (CLI) measurements between network nodes. Different uplink empty / silent resources can be used to measure the spatial characteristics of network node-to-network node CLI caused by various downlink signals and to avoid cross-link interference. The uplink resource silencing mode can be different for various downlink channels and / or downlink signals.

[0032] A phase tracking reference signal (PTRS) can be used to track the phase of the local oscillator at both the receiver and transmitter. Phase tracking enables the suppression of phase noise and common phase error, which can be useful at high carrier frequencies such as millimeter waves. Due to the properties of phase noise, PTRS can have relatively low density in the frequency domain but relatively high density in the time domain.

[0033] The user equipment (UE) can be configured using an uplink resource silence mode, which may overlap with a Physical Uplink Shared Channel (PUSCH) carrying PTRS signals. The uplink resource silence mode and the PUSCH carrying PTRS signals may overlap in uplink resources, which may be associated with SBFD time slots. SBFD time slots may include, in the frequency domain, a first downlink resource, a second downlink resource, and uplink resources between the first and second downlink resources, wherein the uplink resources are associated with an uplink resource silence mode overlapping with the PUSCH carrying PTRS signals.

[0034] The UE may not be configured to handle such overlapping scenarios. Specifically, the UE may not be configured to handle situations where it is configured to use uplink resources in silent mode that overlap with a PUSCH carrying PTRS signals. Due to the uplink resource silent mode, some uplink resources may be silent, and these resources may overlap with PUSCHs carrying PTRS signals, thus preventing PTRS signal transmission. Furthermore, PTRS can be used for phase error tracking, so the UE may not consider the performance impact when handling overlapping scenarios. Because of the inability to handle overlapping scenarios, the UE may suffer from phase error tracking degradation, negatively impacting the overall performance of the UE.

[0035] The various aspects generally relate to handling uplink resource quiescent modes that overlap with PTRS. Some aspects more specifically relate to handling uplink resource quiescent modes that overlap with PUSCH carrying uplink PTRS during SBFD operations. In some aspects, the UE may receive configuration associated with uplink PTRS from a network node. The UE may receive an indication of uplink resource quiescent mode from a network node. The uplink resource quiescent mode may overlap with PUSCH carrying uplink PTRS (e.g., in time and / or frequency) during SBFD operations. The network node may be associated with FD operations. The UE may perform handling of uplink resource quiescent modes that overlap with PUSCH carrying uplink PTRS. For example, the UE may prioritize uplink resource quiescent mode over uplink PTRS. Alternatively, the UE may prioritize uplink PTRS over uplink resource quiescent mode. According to this procedure, the UE may, at least in part, transmit uplink PTRS to the network node via PUSCH based on the uplink PTRS priority over uplink resource silencing mode. Alternatively, the UE may, according to this procedure, use uplink resource silencing mode to silence uplink resources based at least in part on the uplink resource silencing mode priority over uplink PTRS.

[0036] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by configuring the UE to handle overlapping scenarios where the uplink resource silencing mode overlaps with a PUSCH carrying uplink PTRS, the described techniques can be used to allow the UE to transmit uplink PTRS and / or silence uplink resources using the uplink resource silencing mode in the presence of overlap. Based at least in part on this handling, uplink PTRS can reside on separate symbols and / or separate REs on the same symbol instead of conflicting with each other, which improves the overall performance of the UE. In some cases, the UE can handle overlapping scenarios according to uplink PTRS priority relative to the uplink resource silencing mode priority. Furthermore, in some cases, the UE can still transmit uplink PTRS based at least in part on this handling, which improves the UE's phase error tracking.

[0037] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0038] With increasing demand for broadband access and the technological evolution supported by wireless communication networks, further technological improvements can be adopted or implemented in 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication and adapt to a variety of existing and new use cases and applications. Such technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or environmental IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative maneuvering, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0039] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0040] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific radio access technology (RAT) (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RAT, 5G / NR RAT, and / or 6G RAT, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0041] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0043] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0044] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographical locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations conforming to O-RAN Alliance standards), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0045] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0046] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0047] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell can cover a relatively large geographic area (e.g., with a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A picocell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femtocell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macrocell may be referred to as a macro network node. Network node 110 used for a pico cell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may be mobile based on the location of the associated mobile network node 110 (e.g., a train, satellite base station, unmanned aerial vehicle, or non-terrestrial network (NTN) network node).

[0048] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Various types of network nodes 110 can typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100 compared to other types of network nodes 110. For example, macro network nodes can have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0049] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more PUSCH. The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0050] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks (RBs), and / or resource elements (REs)), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources (e.g., a contiguous block of RBs) allocated to one or more UEs 120. UE 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0051] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. For example, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0052] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0053] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an extended reality (XR) device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0054] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.

[0055] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0056] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles or drones, remote devices, sensors, meters, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0057] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR-Lite UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0058] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0059] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0060] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO technology typically utilizes multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) can employ advanced MIMO techniques such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0061] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may: receive configuration associated with an uplink PTRS; receive an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and perform disposal of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0062] In some aspects, a network node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may: send configuration associated with the uplink PTRS; send an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in SBFD operation; and receive the uplink PTRS at least in part based on the disposal of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0063] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0064] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.

[0065] like Figure 2As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0066] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “processor,” “controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0067] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be from the same set of processors or can be from different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0068] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) based on the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0069] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a set of corresponding antennas 234.

[0070] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0071] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0072] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0073] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0074] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling transmission, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0075] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0076] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110 and can provide a set of received downlink signals (e.g., R received signals) to a set of modems 254. For example, each received signal can be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use the corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from the set of modems 254, can perform MIMO detection on the received symbols where applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue and / or an application executed on the UE 120), and provide the decoded control information and system information to the controller / processor 280.

[0077] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a Channel Quality Indicator (CQI) parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0078] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink SRS, and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded (where applicable) by TX MIMO processor 266 and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (where applicable) and can provide an assembly of output symbol streams (e.g., U output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0079] Modems 254a to 254u can transmit a set of uplink signals (e.g., R uplink signals or U uplink symbols) via a set of corresponding antennas 252. Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0080] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0081] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit the cross-polarized signal. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0082] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0083] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0084] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0085] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.

[0086] Figure 3 This is an illustration of an example disaggregated base station architecture 300 according to the present disclosure. One or more components of the example disaggregated base station architecture 300 may be one or more network nodes (such as one or more network nodes 110), may include, or may be included in one or more network nodes. The disaggregated base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more disaggregated control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120 via a corresponding RF access link. In some deployments, UE 120 can be served by multiple RU 340s simultaneously.

[0087] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0088] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0089] The SMO framework 360 supports RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0090] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0091] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and may be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may tune RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may perform corrective actions using AI / ML models created via the SMO framework 360 (such as reconfiguration via the O1 interface) or via RAN management policies (such as A1 interface policies).

[0092] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more techniques associated with handling uplink resource silent modes overlapping with PTRS in SBFD operations, or perform one or more operations associated with handling uplink resource silent modes overlapping with PTRS in SBFD operations, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more techniques associated with handling uplink resource silent modes overlapping with PTRS in SBFD operations, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 11 Process 1100 Figure 12The operation of process 1200 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 11 Process 1100 Figure 12 The process 1200 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0093] In some aspects, the UE (e.g., UE 120) includes: components for receiving configuration associated with an uplink PTRS; components for receiving an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation; and / or components for performing disposal of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS. Components for the UE to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0094] In some aspects, a network node (e.g., network node 110) includes: components for transmitting configuration associated with the uplink PTRS; components for transmitting an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in subband full-duplex operation; and / or components for receiving the uplink PTRS at least in part based on the disposition of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS. Components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0095] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0096] FD operation may involve IBFD operation, where transmission and reception can occur on the same time and frequency resources. Based at least in part on full or partial overlap, the downlink and uplink directions can share the same IBFD time / frequency resources. Alternatively, FD operation may involve SBFD (or Flexible Duplex) operation, where transmission and reception can occur simultaneously but on different frequency resources. Downlink resources can be separated from uplink resources in the frequency domain. In SBFD operation, downlink and uplink frequency overlap may not occur.

[0097] Figure 4 This is a diagram illustrating example 400 of FD communication according to this disclosure.

[0098] As shown by reference numeral 402, downlink resource 404 and uplink resource 406 may share the same IBDF time / frequency resource, at least partially based on complete overlap. As shown by reference numeral 408, downlink resource 410 and uplink resource 412 may share the same IBDF time / frequency resource, at least partially based on partial overlap. As shown by reference numeral 414, downlink resource 416 and uplink resource 420 may be associated with the same time but different frequencies. Downlink resource 416 and uplink resource 420 may be separated by a guard band 418.

[0099] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0100] Figure 5This is a diagram illustrating example 500 of FD communication according to this disclosure.

[0101] As shown by reference numeral 502 in the attached figure, an FD network node (e.g., network node 110a) can communicate with a half-duplex (HD) UE. The FD network node may experience cross-link interference (CLI) from another FD network node (e.g., network node 110d). The CLI from the other FD network node can be inter-node CLI. The FD network node may experience self-interference (SI). The FD network node can receive uplink transmissions from a first HD UE (e.g., UE 120a) and can send downlink transmissions to a second HD UE (e.g., UE 120e). The FD network node can receive uplink transmissions and send downlink transmissions in the same time slot (e.g., simultaneous receive / transmit). The second HD UE may experience CLI from the first HD UE (e.g., inter-UE CLI).

[0102] As shown by reference numeral 504 in the attached figure, an FD network node (e.g., network node 110a) can communicate with an FD UE. The FD network node may experience CLIs from another FD network node (e.g., network node 110d). The FD network node may experience SIs. The FD network node can send downlink transmissions to a first FD UE (e.g., UE 120a), and the FD network node can receive uplink transmissions from the first FD UE at the same time as the downlink transmissions. The FD network node can send downlink transmissions to a second FD UE (e.g., UE 120e). The second HD UE can experience CLIs from the first HD UE. The first UE may experience SIs.

[0103] As shown by reference numeral 506 in the accompanying drawings, a first FD network node (e.g., network node 110a) that can be associated with multiple Transmit / Receive Points (TRPs) can communicate with an SBFD UE. The first FD network node may experience CLIs from a second FD network node (e.g., network node 110d). The first FD network node can receive uplink transmissions from a first SBFD UE (e.g., UE 120a). The second FD network node can send downlink transmissions to both the first SBFD UE and the second SBFD UE (e.g., UE 120e). The second SBFD UE may experience CLIs from the first SBFD UE. The first SBFD UE may experience SIs.

[0104] As shown by reference numeral 508 in the attached figure, SBFD time slots can be associated with non-overlapping uplink / downlink subbands. SBFD time slots can be associated with simultaneous downlink / uplink transmission / reception on a subband basis. Within the component carrier bandwidth, uplink resource 512 can be located in the frequency domain between the first downlink resource 510 and the second downlink resource 514. The first downlink resource 510, the second downlink resource 514, and the uplink resource 512 can all be associated with the same time.

[0105] SBFD operation can increase the uplink duty cycle, which can reduce latency (e.g., downlink signals can be received in uplink-only slots, resulting in latency savings) and improve uplink coverage. SBFD operation can improve system capability, resource utilization, and / or spectral efficiency. SBFD operation can robustly achieve flexible and dynamic uplink / downlink resource adaptation based on uplink / downlink traffic.

[0106] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0107] For network node-to-network node co-channel CLI measurements and / or channel measurements (e.g., gNB-to-gNB co-channel CLI measurements and / or channel measurements), uplink resource silencing can be based at least in part on transparent uplink resource silencing or non-transparent uplink resource silencing. Transparent uplink resource silencing avoids the scheduling of measurement resources. Non-transparent uplink resource silencing can utilize one or more RE or RB silencing modes to define the uplink resource silencing mode.

[0108] Uplink resource silencing for network node-to-network node co-channel CLI measurements and / or channel measurements can be used to measure network node-to-network node (e.g., gNB-to-gNB) CLI levels with less interference from uplink resources. Uplink resource silencing can also be used to measure network node-to-network node channels with less interference from uplink resources. Furthermore, uplink resource silencing can be used to measure the network node-to-network node CLI interference covariance matrix with less interference from uplink resources. Transparent uplink resource silencing can be supported using network node scheduling. Uplink resource silencing may result in uplink performance degradation. When introducing non-transparent uplink resource silencing, the impact of increased peak-to-average power ratio (PAPR) due to UE complexity and discontinuous uplink transmissions should be considered.

[0109] Uplink resource silencing can be used to support inter-network node CLI measurements (e.g., gNB-to-gNB CLI measurements). Different uplink empty / silent resources can be used to measure the spatial characteristics of network node-to-network node CLI caused by various downlink signals and to avoid cross-link interference. The uplink resource silencing mode can be different for various downlink channels and / or downlink signals. For network node-to-network node co-channel CLI measurements, RE silencing can be supported at the locations of the REs from the interfering cell's Synchronization Signal Block (SSB), System Information Block Type 1 (SIB1), and Broadcast Physical Downlink Control Channel (PDCCH) in the uplink time slot to measure the spatial characteristics of downlink broadcast interference. RE silencing can also be supported at the locations of the REs from the interfering cell's Unicast Physical Downlink Shared Channel (PDSCH) and PDCCH in the uplink time slot to obtain the spatial characteristics of unicast PDSCH and PDCCH CLI. It can support silencing REs at the location of the non-zero power (NZP) channel state information reference signal (CSI-RS) from the harassing cell in the uplink time slot to avoid strong CLI.

[0110] PTRS can be used to track the phase of local oscillators at the receiver and transmitter. Phase tracking enables the suppression of phase noise and common phase errors, which can be useful at high carrier frequencies such as millimeter waves. Due to the properties of phase noise, PTRS can have relatively low density in the frequency domain but relatively high density in the time domain. For downlink PTRS, the PTRS can be associated with a DMRS port and can be limited by the scheduling bandwidth and duration of the PDSCH / PUSCH. After the PTRS port is associated with the DMRS port, the PTRS can be transmitted using the same subcarrier as the associated DMRS, and the same sequence as the DMRS can be repeated for the PTRS in a time slot. For uplink PTRS, one or two PTRS ports can be scheduled at least in part based on UE capabilities. Two PTRS ports can be used for non-coherent / partially coherent uplink transmission, where the UE has two local oscillators (e.g., when the UE is equipped with two or more transmit panels for the uplink direction). When the UE has reported the ability to support fully coherent uplink transmission, only a single PTRS port can be used.

[0111] PTRS tones can be transmitted according to various PTRS modes, at times and frequencies specified by parameters L and K, respectively. When L=1, PTRS can be transmitted on every PDSCH symbol. When L=2, PTRS can be transmitted on one symbol out of every two PDSCH symbols. When L=4, PTRS can be transmitted on one symbol out of every four PDSCH symbols. When K=4, one PTRS tone can be transmitted every four RBs. When K=2, one PTRS tone can be transmitted every two RBs. PTRS modes can be designed to have relatively good frequency diversity (e.g., PTRS is uniformly distributed in the frequency domain).

[0112] Figure 6 This is a diagram illustrating Example 600 of the PTRS pattern according to this disclosure.

[0113] As shown by reference numeral 602, the PTRS mode can be associated with K=2 and L=1. In this case, one PTRS tone can be transmitted for every two RBs, and PTRS can be transmitted on each PDSCH symbol. As shown by reference numeral 604, the PTRS mode can be associated with K=2 and L=2. In this case, one PTRS tone can be transmitted for every two RBs, and PTRS can be transmitted on one symbol out of every two PDSCH symbols. As shown by reference numeral 606, the PTRS mode can be associated with K=4 and L=1. In this case, one PTRS tone can be transmitted for every four RBs, and PTRS can be transmitted on each PDSCH symbol.

[0114] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0115] Uplink PTRS for DFT-s-OFDM waveforms is supported. Possible PTRS presence / absence can be configured using the uplink PTRS present-transform-precoding (UL-PTRS-present-transform-precoding) RRC parameter. Multiple modes / densities of PTRS for DFT-s-OFDM are supported. DFT pre-PTRS insertion for uplink DFT-s-OFDM can be performed in multiple blocks per symbol. Supported block sizes K can be 2 and 4, which can be implicitly configured depending on the MCS and allocated bandwidth. The supported number of blocks X per DFT-s-OFDM symbol can be 2, 4, and 8, where X can implicitly depend on the allocated bandwidth, MCS, and / or the K value. The time-domain PTRS density can be configured by the uplink PTRS time-density-transform-precoding (UL-PTRS-time-density-transform-precoding) RRC parameter, where supported time densities can be {1, 2}. The temporal PTRS density can be based at least in part on each symbol carrying a PUSCH or every other symbol carrying a PUSCH.

[0116] Figure 7 This is a diagram illustrating example 700 inserted according to the PTRS of this disclosure.

[0117] like Figure 7 As shown, in the DFT pre-PTRS insertion for uplink DFT-s-OFDM using multiple blocks per symbol, the supported block size (K) can be 2, and the supported number of blocks per DFT-s-OFDM symbol (X) can be 2. A first sub-region may include a first PTRS group, and a second sub-region may include a second PTRS group, wherein each PTRS group may be associated with an uplink PTRS. The first and second PTRS groups may be separated by PUSCH samples.

[0118] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0119] For the uplink direction, one or two PTRS ports can be scheduled, at least in part, based on UE capabilities. Two PTRS ports can be used for non-coherent / partially coherent uplink transmission, with two local oscillators in the UE. When the UE has reported the ability to support fully coherent uplink transmission, only a single PTRS port can be used. In the uplink direction, Q... pWhen scheduling a UE with {1, 2} PTRS ports, the PTRS power can be increased based on the number of PUSCH layers. The power increase value can vary depending on the transmission scheme. The power increase value can also vary depending on the transmission codebook used (e.g., fully / partially coherent or incoherent). The PTRS uplink configuration can include a higher-layer parameter for uplink PTRS power (ptrs-Power) set to {00, 01, ...}, which indicates the different options to be used for power increase. The higher-layer parameter for uplink PTRS power indicates the uplink PTRS power increase factor per PTRS port.

[0120] Different PTRS power boost values ​​(in dB) can be defined based on the number of PUSCH layers and the codebook type. The number of PUSCH layers can be {1, 2, 3, 4}. The codebook type can be fully coherent, partially coherent, partially incoherent and based on a non-codebook, and / or incoherent and based on a non-codebook.

[0121] Figure 8 This is an illustration of Example 800 of an uplink resource silent mode that overlaps with a PUSCH carrying PTRS according to this disclosure.

[0122] like Figure 8 As shown, the UE can be configured using an uplink resource silence mode, which may overlap with a PUSCH carrying PTRS signals. The uplink resource silence mode and the PUSCH carrying PTRS signals may overlap in uplink resources, which may be associated with SBFD time slots. SBFD time slots may include, in the frequency domain, a first downlink resource, a second downlink resource, and uplink resources between the first and second downlink resources, wherein the uplink resources are associated with an uplink resource silence mode overlapping with the PUSCH carrying PTRS signals.

[0123] The UE may not be configured to handle such overlapping scenarios. Specifically, the UE may not be configured to handle situations where it is configured to use uplink resources in silent mode that overlap with a PUSCH carrying PTRS signals. Due to the uplink resource silent mode, some uplink resources may be silent, and these resources may overlap with PUSCHs carrying PTRS signals, thus preventing PTRS signal transmission. Furthermore, PTRS can be used for phase error tracking, so the UE may not consider the performance impact when handling overlapping scenarios. Because of the inability to handle overlapping scenarios, the UE may suffer from phase error tracking degradation, negatively impacting the overall performance of the UE.

[0124] As indicated above, Figure 8This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0125] In various aspects of the technologies and apparatus described herein, the UE may receive configuration associated with uplink PTRS from a network node. The UE may receive an indication of an uplink resource quiescent mode from the network node. The uplink resource quiescent mode may overlap with a PUSCH carrying uplink PTRS (e.g., in time and / or frequency) during SBFD operation. The network node may be associated with FD operation. The UE may perform a disposition on the uplink resource quiescent mode that overlaps with the PUSCH carrying uplink PTRS. For example, the UE may prioritize the uplink resource quiescent mode over the uplink PTRS. Alternatively, the UE may prioritize the uplink PTRS over the uplink resource quiescent mode. Based on this disposition, the UE may transmit the uplink PTRS to the network node via the PUSCH, at least in part, based on the premise that the uplink PTRS prioritizes the uplink resource quiescent mode. Alternatively, based on this disposition, the UE may use the uplink resource quiescent mode to quiet uplink resources, at least in part, based on the premise that the uplink resource quiescent mode prioritizes the uplink PTRS.

[0126] In some aspects, by configuring the UE to handle overlapping scenarios where the uplink resource silencing mode overlaps with a PUSCH carrying uplink PTRS, the UE can be able to transmit uplink PTRS and / or silence uplink resources using the uplink resource silencing mode. Based at least in part on this handling, uplink PTRS can reside on separate symbols and / or separate REs on the same symbol instead of conflicting with each other, which improves the overall performance of the UE. In some cases, the UE can handle overlapping scenarios based on uplink PTRS priority relative to the uplink resource silencing mode priority. Furthermore, in some cases, the UE can still transmit uplink PTRS at least in part based on this handling, which improves the UE's phase error tracking.

[0127] Figure 9 This is a diagram illustrating example 900 of the uplink resource silent mode overlapping with PTRS in SBFD operation according to the provisions of this disclosure. Figure 9 As shown, Example 900 includes communication between a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the UE and the network node may be included in a wireless network (such as wireless network 100). The network node may be associated with FD operation.

[0128] As shown by reference numeral 902 in the attached figure, the UE can receive configuration associated with the uplink PTRS from the network node. This configuration can indicate the time density indicated by parameter L and the frequency density indicated by parameter K associated with the uplink PTRS.

[0129] As shown by reference numeral 904 in the attached figure, the UE may receive an indication of an uplink resource silencing mode from the network node. The uplink resource silencing mode indicates the specific uplink resources that the UE should silence, whereby the UE can use such silenced uplink resources to measure the spatial characteristics of network node-to-network node CLI caused by various downlink signals and to avoid CLI. The uplink resource silencing mode can be used for various downlink channels and / or downlink signals. The UE may receive an indication from the network node to activate the uplink resource silencing mode. In some aspects, the uplink resource silencing mode may overlap with a PUSCH carrying uplink PTRS during SBFD operation. This overlap may be in the time domain and / or the frequency domain.

[0130] As shown by reference numeral 906 in the attached figure, the UE can perform processing on uplink resource silencing modes that overlap with PUSCH carrying uplink PTRS. When performing this processing, the UE can take appropriate actions to resolve the overlap between the uplink resource silencing mode and the PUSCH carrying uplink PTRS. For example, the UE can prioritize the uplink resource silencing mode over the uplink PTRS. Alternatively, the UE can prioritize the uplink PTRS over the uplink resource silencing mode. In some cases, the UE can allow both the uplink resource silencing mode and the uplink PTRS, provided that the uplink silencing resource and the uplink PTRS are associated with different symbols and / or different REs of the same symbol.

[0131] In some aspects, a PUSCH carrying uplink PTRS can be associated with CP-OFDM. In some aspects, the UE can prohibit uplink resource silencing mode and uplink PTRS from overlapping on the same symbol. In some aspects, the UE can allow uplink resource silencing mode and uplink PTRS to overlap on the same symbol. The UE can define uplink resource silencing mode and uplink PTRS to different REs. In some aspects, the UE can prioritize uplink resource silencing mode over uplink PTRS, wherein PTRS symbols can be skipped at least partially based on PTRS symbols overlapping with silencing REs. In some aspects, the UE can prioritize uplink PTRS over uplink resource silencing mode at least partially based on conflicts between uplink resource silencing mode and uplink PTRS on one or more REs, wherein uplink silencing can be skipped for that one or more REs.

[0132] In some aspects, for CP-OFDM uplink signals with PTRS, the overlap between uplink resource quiescent mode and PUSCH transmission can be handled. In a first option, overlap between uplink resource quiescent mode and PTRS symbols can be disallowed. When PTRS is configured on each PUSCH symbol, uplink resource quiescent can be skipped for that PUSCH transmission. Otherwise, only PUSCH symbols without PTRS can have uplink resource quiescent. Alternatively, a PTRS configuration (e.g., a PTRS uplink resource quiescent configuration) can be defined, where the PTRS configuration is active only when uplink resource quiescent is active. Such a configuration can be designed via RRC to not overlap with the uplink resource quiescent mode. In a second option, when overlap is resolved by network nodes through appropriate configuration, uplink resource quiescent mode can be allowed on PTRS symbols (e.g., not configuring uplink resource quiescent mode and PTRS symbols on the same RE). Alternatively, when resolving overlap by offsetting the RE of the PTRS (which increments to avoid overlap with the uplink resource quiescent mode), the uplink resource quiescent mode can be allowed on the PTRS symbol. In the third option, the uplink resource quiescent mode can be given higher priority than PTRS, and the PTRS symbol can be skipped when it overlaps with a quiescent RE. This option may negatively impact phase error tracking. In the fourth option, PTRS can be given priority when the uplink resource quiescent mode and PTRS conflict on the same RE. In this option, PTRS can be given higher priority than the uplink resource quiescent mode.

[0133] In some aspects, a PUSCH carrying uplink PTRS can be associated with DFT-s-OFDM. In some aspects, the UE can disable uplink resource silencing on the PUSCH. In some aspects, the UE can discard uplink PTRS at least partially based on the overlap between the uplink resource silencing mode and the PUSCH. In some aspects, the UE can prioritize uplink PTRS at least partially based on the overlap between the uplink resource silencing mode and the PUSCH, wherein uplink silencing may not be performed on overlapping resources.

[0134] In some aspects, when uplink resource silencing overlaps with PTRS in DFT-s-OFDM, uplink PTRS might be inserted before the DFT in the time domain for the DFT-s-OFDM PUSCH. Therefore, uplink resource silencing (in this case, puncturing) can negatively impact uplink PTRS. In the first option, uplink resource silencing on the DFT-s-OFDM PUSCH can be disallowed (this can be avoided through network configuration), otherwise it is considered an error condition. In the second option, PTRS samples can be discarded when the uplink resource silencing mode overlaps with the DFT-s-OFDM PUSCH. In this case, uplink PTRS can be omitted. In the third option, PTRS samples can be prioritized when the uplink resource silencing mode overlaps with the DFT-s-OFDM PUSCH. In this case, uplink resource silencing can be prevented on the overlapping resources.

[0135] As shown by reference numeral 908 in the attached figure, the UE may, according to this arrangement, transmit uplink PTRS to the network node via PUSCH, at least in part, based on the uplink PTRS priority over uplink resource silencing mode. In this case, the UE may transmit uplink PTRS instead of silencing uplink resources.

[0136] As shown by reference numeral 910 in the attached figure, the UE may, according to this procedure, use the uplink resource silencing mode to silence uplink resources, at least in part, based on the principle that the uplink resource silencing mode takes precedence over the uplink PTRS. In this case, the UE may not send uplink PTRS, but may instead silence uplink resources according to the uplink resource silencing mode.

[0137] In some aspects, uplink resource silencing mode and uplink PTRS can be allowed on the same symbol and can be configured on different REs. In some aspects, the UE can boost the power of the remaining uplink shared channel REs to compensate for silencing REs. In some aspects, the UE can boost the power of uplink PTRS to compensate for silencing REs. The power of uplink PTRS can be boosted at least in part based on implicit power boosting in addition to the legacy PTRS power boosting factor, or the power of uplink PTRS can be boosted using a separate power boosting factor to be used when uplink PTRS overlaps with uplink resource silencing mode.

[0138] In some aspects, uplink resource silencing mode and uplink PTRS can be allowed on the same symbol but configured on different REs. In the first option, to maintain the same per-symbol power across PUSCH symbols, the power of the remaining uplink shared channel (UL-SCH) REs can be increased to compensate for the silencing REs. In the second option, to maintain the same per-symbol power across PUSCH symbols, the power of uplink PTRS can be increased to compensate for the silencing REs. The PTRS power increase can be based at least in part on implicit power increases in addition to the legacy PTRS power increase factor. Alternatively, a separate power increase factor can be defined in the specification for the time when uplink PTRS overlaps with uplink resource silencing.

[0139] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.

[0140] Figure 10 This is a diagram illustrating example 1000 of the uplink resource silent mode overlapping with PTRS in SBFD operation according to the present disclosure.

[0141] As shown by reference numeral 1002, in the first option, uplink resource silencing mode may not overlap with PTRS symbols. In the first option, uplink resource silencing and PTRS may not be allowed on the same symbol. As shown by reference numeral 1004, in the second option, uplink resource silencing mode may be allowed on PTRS symbols as long as the overlap is resolved. In the second option, uplink resource silencing and PTRS may not be allowed on the same RE (e.g., uplink resource silencing and PTRS may be associated with different REs of the same symbol). As shown by reference numeral 1006, in the third option, uplink resource silencing mode may be given higher priority, and PTRS symbols may be skipped when overlapping with silencing REs. In the third option, PTRS may be skipped. As shown by reference numeral 1008, in the fourth option, PTRS may be given higher priority, and uplink resource silencing modes that conflict with PTRS on some REs may be skipped. In the fourth option, uplink resource silencing may be skipped.

[0142] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.

[0143] Figure 11This is a diagram illustrating an example procedure 1100 performed, for example, at a UE or a device of a UE, according to this disclosure. Example procedure 1100 is an example in which the device or the UE (e.g., UE 120) performs operations associated with disposing of an uplink resource silent mode overlapping with PTRS in SBFD operation.

[0144] like Figure 11 As shown, in some aspects, process 1100 may include receiving configuration associated with the uplink PTRS (block 1110). For example, the UE (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1306 described herein can receive configuration associated with the uplink PTRS, as described above. Figures 9 to 10 As described.

[0145] like Figure 11 Further shown, in some aspects, process 1100 may include receiving an indication of an uplink resource silencing mode, wherein the uplink resource silencing mode overlaps with a PUSCH carrying the uplink PTRS in subband full-duplex operation (box 1120). For example, the UE (e.g., using...) Figure 13 The receiving component 1302 and / or communication manager 1306 described herein can receive an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in subband full-duplex operation, as described above. Figures 9 to 10 As described.

[0146] like Figure 11 Further shown, in some aspects, process 1100 may include performing disposal of the uplink resource silencing mode that overlaps with the PUSCH carrying the uplink PTRS (box 1130). For example, the UE (e.g., using...) Figure 13 The communication manager 1306 described herein can perform the handling of the uplink resource quiescent mode that overlaps with the PUSCH carrying the uplink PTRS, as described above. Figures 9 to 10 As described.

[0147] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0148] In a first aspect, process 1100 includes, according to the disposal, sending the uplink PTRS via the PUSCH at least in part based on the uplink PTRS taking precedence over the uplink resource silent mode.

[0149] In a second aspect, process 1100 includes, according to the disposal, using the uplink resource silencing mode to silence the uplink resource at least in part based on the fact that the uplink resource silencing mode takes precedence over the uplink PTRS.

[0150] Thirdly, the PUSCH carrying the uplink PTRS is associated with CP-OFDM.

[0151] In the fourth aspect, process 1100 includes prohibiting the uplink resource silent mode from overlapping with the uplink PTRS on the same symbol.

[0152] In a fifth aspect, process 1100 includes allowing the uplink resource quiz mode and the uplink PTRS to overlap on the same symbol, and defining the uplink resource quiz mode and the uplink PTRS to different REs.

[0153] In a sixth aspect, process 1100 includes prioritizing the uplink resource silent mode over the uplink PTRS, and skipping the PTRS symbol at least in part based on the overlap of the PTRS symbol with the silent RE.

[0154] In the seventh aspect, process 1100 includes prioritizing the uplink PTRS over the uplink resource silencing mode based at least in part on the conflict between the uplink resource silencing mode and the uplink PTRS on one or more REs, and skipping uplink silencing for the one or more REs.

[0155] In the eighth aspect, the PUSCH carrying the uplink PTRS is associated with DFT-s-OFDM.

[0156] In the ninth aspect, procedure 1100 includes prohibiting uplink resource silencing on the PUSCH.

[0157] In the tenth aspect, process 1100 includes dropping the uplink PTRS at least in part based on the overlap between the uplink resource silent mode and the PUSCH.

[0158] In the eleventh aspect, process 1100 includes giving priority to the uplink PTRS based at least in part on the overlap between the uplink resource silencing mode and the PUSCH, and not performing uplink silencing on the overlapping resources.

[0159] In the twelfth aspect, the uplink resource quiescent mode and the uplink PTRS are allowed to be on the same symbol and configured on different REs, and process 1100 includes increasing the power of the remaining uplink shared channel REs to compensate for the quiescent REs.

[0160] In the thirteenth aspect, the uplink resource quiescent mode and the uplink PTRS are allowed to be on the same symbol and configured on different REs, and process 1100 includes boosting the power of the uplink PTRS to compensate for the quiescent RE, wherein the power of the uplink PTRS is boosted at least in part based on implicit power boost in addition to the legacy PTRS power boost factor, or the power of the uplink PTRS is boosted using a separate power boost factor to be used when the uplink PTRS overlaps with the uplink resource quiescent mode.

[0161] although Figure 11 An example box for process 1100 is shown, but in some respects, it differs from... Figure 11 Compared to the boxes depicted, process 1100 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1100 may be executed in parallel.

[0162] Figure 12 This is a diagram illustrating an example process 1200 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 1200 is an example in which the device or the network node (e.g., network node 110) performs operations associated with disposing of an uplink resource silent mode overlapping with PTRS in SBFD operation.

[0163] like Figure 12 As shown, in some aspects, process 1200 may include sending configuration associated with the uplink PTRS (box 1210). For example, the network node (e.g., using...) Figure 14 The transmitting component 1404 and / or communication manager 1406 described herein can transmit configurations associated with the uplink PTRS, as described above. Figures 9 to 10 As described.

[0164] like Figure 12 Further shown, in some aspects, process 1200 may include sending an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation (box 1220). For example, the network node (e.g., using...) Figure 14 The transmitting component 1404 and / or communication manager 1406 described herein can transmit an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS during SBFD operation, as described above. Figures 9 to 10 As described.

[0165] like Figure 12Further shown, in some aspects, process 1200 may include receiving the uplink PTRS (box 1230) at least in part based on the handling of the uplink resource quiescent mode that overlaps with the PUSCH carrying the uplink PTRS. For example, the network node (e.g., using...) Figure 14 The receiving component 1402 and / or communication manager 1406 described herein may receive the uplink PTRS at least in part based on the handling of the uplink resource quiescent mode that overlaps with the PUSCH carrying the uplink PTRS, as described above. Figures 9 to 10 As described.

[0166] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.

[0167] In a first aspect, process 1200 includes receiving the uplink PTRS via the PUSCH, at least in part, based on the uplink PTRS taking precedence over the uplink resource silent mode, according to the disposal.

[0168] Secondly, the PUSCH carrying the uplink PTRS is associated with CP-OFDM.

[0169] Thirdly, according to this action, the uplink resource silent mode is prohibited from overlapping with the uplink PTRS on the same symbol.

[0170] In the fourth aspect, according to this treatment, the uplink resource quiz mode and the uplink PTRS are allowed to overlap on the same symbol, and the uplink resource quiz mode and the uplink PTRS are defined to different REs.

[0171] In the fifth aspect, according to this treatment, the uplink PTRS is prioritized over the uplink resource silence mode, at least in part, based on the conflict between the uplink resource silence mode and the uplink PTRS on one or more REs, and uplink silence is skipped for the one or more REs.

[0172] In the sixth aspect, the PUSCH carrying the uplink PTRS is associated with DFT-s-OFDM.

[0173] In the seventh aspect, according to this measure, uplink resource silencing is prohibited on this PUSCH.

[0174] In the eighth aspect, according to this treatment, the uplink PTRS is given priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, and uplink silencing is not performed on the overlapping resources.

[0175] although Figure 12 An example box for process 1200 is shown, but in some respects, it differs from... Figure 12 Compared to the boxes depicted, process 1200 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 1200 may be executed in parallel.

[0176] Figure 13 This is a diagram of an example device 1300 for wireless communication according to the present disclosure. Device 1300 may be a UE, or a UE may include device 1300. In some aspects, device 1300 includes a receiving component 1302, a transmitting component 1304, and / or a communication manager 1306 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1306 is combined with... Figure 1 The described communication manager 140. As shown, device 1300 can communicate with another device 1308 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1302 and transmitting component 1304.

[0177] In some respects, device 1300 can be configured to perform the functions described herein. Figures 9 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Figure 11 The process 1100. In some respects, Figure 13 The illustrated device 1300 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 13 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and capable of being executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0178] Receiver 1302 may receive communications from device 1308, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0179] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1308. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1308. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1308. In some aspects, transmitting component 1304 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0180] The communication manager 1306 may support the operation of the receiving component 1302 and / or the transmitting component 1304. For example, the communication manager 1306 may receive information associated with configuring the reception of communications by the receiving component 1302 and / or the transmission of communications by the transmitting component 1304. Additionally or alternatively, the communication manager 1306 may generate control information and / or provide control information to the receiving component 1302 and / or the transmitting component 1304 to control the reception and / or transmission of communications.

[0181] The receiving component 1302 can receive configuration associated with the uplink PTRS. The receiving component 1302 can also receive an indication of an uplink resource silencing mode, wherein the uplink resource silencing mode overlaps with a PUSCH carrying the uplink PTRS in subband full-duplex operation. The communication manager 1306 can perform processing on the uplink resource silencing mode overlapping with the PUSCH carrying the uplink PTRS. The transmitting component 1304 can, according to this processing, transmit the uplink PTRS via the PUSCH based at least in part on the fact that the uplink PTRS takes precedence over the uplink resource silencing mode. The communication manager 1306 can, according to this processing, use the uplink resource silencing mode to silence the uplink resource at least in part on the fact that the uplink resource silencing mode takes precedence over the uplink PTRS.

[0182] Figure 13 The number and arrangement of components shown are provided as an example. In reality, with... Figure 13 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 13 The two or more components shown can be implemented within a single component, or Figure 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 13 The set (one or more) components shown are executable and described as being composed of Figure 13 The other set of components shown performs one or more functions.

[0183] Figure 14 This is a diagram of an example device 1400 for wireless communication according to the present disclosure. Device 1400 may be a network node, or a network node may include device 1400. In some aspects, device 1400 includes a receiving component 1402, a transmitting component 1404, and / or a communication manager 1406 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1406 is combined with... Figure 1 The described communication manager 150. As shown, device 1400 can communicate with another device 1408 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1402 and transmitting component 1404.

[0184] In some respects, device 1400 can be configured to perform the functions described herein. Figures 9 to 10 One or more operations described herein. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Figure 12 The process is 1200. In some respects, Figure 14The illustrated device 1400 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 14 One or more components shown can be combined Figure 2 Implemented within one or more of the described components. Additionally or alternatively, one or more of the components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and capable of being executed by one or more controllers or one or more processors to perform the function or operation of the component.

[0185] Receiver 1402 may receive communications from device 1408, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1400. In some aspects, receiver 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1400. In some aspects, receiver 1402 may include combinations of... Figure 2 The described network node may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1402 and / or transmitter component 1404 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1400 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0186] Transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1408. In some aspects, one or more other components of device 1400 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1408. In some aspects, transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1408. In some aspects, transmitting component 1404 may include combinations of... Figure 2The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1404 may co-located with the receive component 1402 in one or more transceivers.

[0187] The communication manager 1406 may support the operation of the receiving component 1402 and / or the transmitting component 1404. For example, the communication manager 1406 may receive information associated with configuring the reception of communications by the receiving component 1402 and / or the transmission of communications by the transmitting component 1404. Additionally or alternatively, the communication manager 1406 may generate control information and / or provide control information to the receiving component 1402 and / or the transmitting component 1404 to control the reception and / or transmission of communications.

[0188] Transmitting component 1404 may transmit configuration associated with the uplink PTRS. Transmitting component 1404 may transmit an indication of an uplink resource quiescent mode, wherein the uplink resource quiescent mode overlaps with a PUSCH carrying the uplink PTRS in subband full-duplex operation. Receiving component 1402 may receive the uplink PTRS at least in part based on the handling of the uplink resource quiescent mode overlapping with the PUSCH carrying the uplink PTRS. Receiving component 1402 may, according to this handling, receive the uplink PTRS via the PUSCH at least in part based on the uplink PTRS taking precedence over the uplink resource quiescent mode.

[0189] Figure 14 The number and arrangement of components shown are provided as an example. In reality, with... Figure 14 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 14 The two or more components shown can be implemented within a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 14 The set (one or more) components shown are executable and described as being composed of Figure 14 The other set of components shown performs one or more functions.

[0190] The following provides an overview of some aspects of this disclosure:

[0191] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration associated with an uplink phase tracking reference signal (PTRS); receiving an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation; and performing disposal of the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0192] Aspect 2: According to the method of aspect 1, the method further includes: according to the handling, transmitting the uplink PTRS via the PUSCH at least in part based on the uplink PTRS taking precedence over the uplink resource silent mode.

[0193] Aspect 3: The method according to any one of Aspects 1 to 2, the method further comprising: according to the disposal, using the uplink resource silencing mode to silence the uplink resource at least in part based on the uplink resource silencing mode taking precedence over the uplink PTRS.

[0194] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the PUSCH carrying the uplink PTRS is associated with Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM).

[0195] Aspect 5: The method according to any one of Aspects 1 to 4, wherein performing the disposal further includes: prohibiting the uplink resource silent mode from overlapping with the uplink PTRS on the same symbol.

[0196] Aspect 6: The method according to any one of Aspects 1 to 5, wherein performing the disposal further includes: allowing the uplink resource quiescent mode and the uplink PTRS to overlap on the same symbol; and defining the uplink resource quiescent mode and the uplink PTRS to different resource elements.

[0197] Aspect 7: The method according to any one of Aspects 1 to 6, wherein performing the disposal further includes: prioritizing the uplink resource silent mode over the uplink PTRS, wherein the PTRS symbol is skipped at least in part based on the overlap of the PTRS symbol with the silent resource element.

[0198] Aspect 8: The method according to any one of Aspects 1 to 7, wherein performing the disposal further comprises: at least in part based on the uplink resource silencing mode conflicting with the uplink PTRS on one or more resource elements (REs) to give priority to the uplink resource silencing mode, wherein uplink silencing is skipped for the one or more REs.

[0199] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the PUSCH carrying the uplink PTRS is associated with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

[0200] Aspect 10: The method according to any one of Aspects 1 to 9, wherein performing the disposal further includes: disabling uplink resource silencing on the PUSCH.

[0201] Aspect 11: The method according to any one of Aspects 1 to 10, wherein performing the disposal further includes: dropping the uplink PTRS at least in part based on the overlap between the uplink resource silent mode and the PUSCH.

[0202] Aspect 12: The method according to any one of Aspects 1 to 11, wherein performing the disposal further includes: giving the uplink PTRS priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, wherein uplink silencing is not performed on the overlapping resources.

[0203] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the uplink resource quiescent mode and the uplink PTRS are allowed on the same symbol and configured on different resource elements (REs), and the method further includes: increasing the power of the remaining uplink shared channel REs to compensate for the quiescent REs.

[0204] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the uplink resource quiescent mode and the uplink PTRS are allowed on the same symbol and configured on different resource elements (REs), and the method further comprises: boosting the power of the uplink PTRS to compensate for the quiescent RE, wherein the power of the uplink PTRS is boosted at least in part based on implicit power boost in addition to a legacy PTRS power boost factor, or the power of the uplink PTRS is boosted using a separate power boost factor to be used when the uplink PTRS overlaps with the uplink resource quiescent mode.

[0205] Aspect 15: A method of wireless communication performed by a network node, the method comprising: transmitting a configuration associated with an uplink phase tracking reference signal (PTRS); transmitting an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with a physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation; and receiving the uplink PTRS based at least in part on the disposal of the uplink resource silence mode overlapping with the PUSCH carrying the uplink PTRS.

[0206] Aspect 16: The method according to aspect 15, the method further comprising: receiving the uplink PTRS via the PUSCH at least in part based on the uplink PTRS taking precedence over the uplink resource silent mode, according to the handling.

[0207] Aspect 17: The method according to any one of Aspects 15 to 16, wherein the PUSCH carrying the uplink PTRS is associated with Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM).

[0208] Aspect 18: The method according to any one of Aspects 15 to 17, wherein, according to the disposal, the uplink resource silent mode is prohibited from overlapping with the uplink PTRS on the same symbol.

[0209] Aspect 19: The method according to any one of Aspects 15 to 18, wherein, according to the disposal, the uplink resource quiescent mode and the uplink PTRS are allowed to overlap on the same symbol, and the uplink resource quiescent mode and the uplink PTRS are defined to different resource elements.

[0210] Aspect 20: The method according to any one of Aspects 15 to 19, wherein, according to the disposal, the uplink PTRS is prioritized over the uplink resource silence mode based at least in part on the conflict between the uplink resource silence mode and the uplink PTRS on one or more resource elements (REs), and uplink silence is skipped for the one or more REs.

[0211] Aspect 21: The method according to any one of Aspects 15 to 20, wherein the PUSCH carrying the uplink PTRS is associated with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

[0212] Aspect 22: The method according to any one of Aspects 15 to 21, wherein, according to the disposal, uplink resource silencing is prohibited on the PUSCH.

[0213] Aspect 23: The method according to any one of Aspects 15 to 22, wherein, according to the disposal, the uplink PTRS is given priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, and uplink silencing is not performed on the overlapping resources.

[0214] Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 14.

[0215] Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 14.

[0216] Aspect 26: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 14.

[0217] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 14.

[0218] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 14.

[0219] Aspect 29: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 14.

[0220] Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 14.

[0221] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform one or more of the methods according to aspects 15 to 23.

[0222] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 15 to 23.

[0223] Aspect 33: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 15 to 23.

[0224] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 15 to 23.

[0225] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 15 to 23.

[0226] Aspect 36: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 15 to 23.

[0227] Aspect 37: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 15 to 23.

[0228] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various practices.

[0229] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0230] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0231] As used in this article, the phrase “at least one of the items” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0232] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0233] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and One or more processors, said one or more processors coupled to said memory and configured to cause said UE to: Receive configuration associated with the uplink phase tracking reference signal (PTRS); Receive an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with the physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation. as well as Perform a silent mode for the uplink resources that overlap with the PUSCH carrying the uplink PTRS.

2. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: According to the described procedure, the uplink PTRS is transmitted via the PUSCH at least in part based on the fact that the uplink PTRS takes precedence over the uplink resource silent mode.

3. The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to: According to the described procedure, the uplink resource silencing mode is used at least in part based on the fact that the uplink resource silencing mode takes precedence over the uplink PTRS.

4. The apparatus of claim 1, wherein the PUSCH carrying the uplink PTRS is associated with Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM).

5. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: The uplink resource silent mode and the uplink PTRS are prohibited from overlapping on the same symbol.

6. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: Allowing the uplink resource silent mode to overlap with the uplink PTRS on the same symbol; and The uplink resource silent mode and the uplink PTRS are defined to different resource elements.

7. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: The uplink resource silent mode takes precedence over the uplink PTRS, wherein the PTRS symbol is skipped at least in part based on the overlap of the PTRS symbol with the silent resource element.

8. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: The uplink PTRS is prioritized over the uplink resource silence mode, at least in part, based on the conflict between the uplink resource silence mode and the uplink PTRS on one or more resource elements (REs), wherein uplink silence is skipped for the one or more REs.

9. The apparatus of claim 1, wherein the PUSCH carrying the uplink PTRS is associated with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

10. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: Uplink resource silencing is disabled on the PUSCH.

11. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: The uplink PTRS is dropped at least in part based on the overlap between the uplink resource silent mode and the PUSCH.

12. The apparatus of claim 1, wherein, in order to perform the processing, the one or more processors are further configured to cause the UE to: The uplink PTRS is given priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, wherein uplink silencing is not performed on the overlapping resources.

13. The apparatus of claim 1, wherein the uplink resource silent mode and the uplink PTRS are allowed on the same symbol and configured on different resource elements (REs), and the one or more processors are further configured to cause the UE to: Increase the power of the remaining uplink shared channel REs to compensate for the silent REs.

14. The apparatus of claim 1, wherein the uplink resource silent mode and the uplink PTRS are allowed on the same symbol and configured on different resource elements (REs), and the one or more processors are further configured to cause the UE to: Increase the power of the uplink PTRS to compensate for quiescent REs, wherein the power of the uplink PTRS is increased at least in part based on implicit power boost in addition to the legacy PTRS power boost factor, or the power of the uplink PTRS is increased using a separate power boost factor to be used when the uplink PTRS overlaps with the uplink resource quiescent mode.

15. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories and configured to cause the network node to: Send the configuration associated with the uplink phase tracking reference signal (PTRS); Send an indication of an uplink resource quiz mode, wherein the uplink resource quiz mode overlaps with the physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation; as well as The uplink PTRS is received at least in part based on the handling of the uplink resource silent mode that overlaps with the PUSCH carrying the uplink PTRS.

16. The apparatus of claim 15, wherein, in order to perform the processing, the one or more processors are further configured to cause the network node to: According to the described procedure, the uplink PTRS is received via the PUSCH at least in part based on the fact that the uplink PTRS takes precedence over the uplink resource silent mode.

17. The apparatus according to claim 15, wherein: The PUSCH carrying the uplink PTRS is associated with Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM); or The PUSCH carrying the uplink PTRS is associated with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

18. The apparatus according to claim 15, wherein: According to the aforementioned measures, the uplink resource silent mode and the uplink PTRS are prohibited from overlapping on the same symbol; or According to the described treatment, the uplink resource quiz mode and the uplink PTRS are allowed to overlap on the same symbol, and the uplink resource quiz mode and the uplink PTRS are defined to different resource elements.

19. The apparatus of claim 15, wherein, according to the disposal, the uplink PTRS is prioritized over the uplink resource silence mode at least in part based on a conflict between the uplink resource silence mode and the uplink PTRS on one or more resource elements (REs), and uplink silence is skipped for the one or more REs.

20. The apparatus according to claim 15, wherein: According to the aforementioned action, uplink resource silencing is prohibited on the PUSCH; or According to the described procedure, the uplink PTRS is given priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, and uplink silencing is not performed on the overlapping resources.

21. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive configuration associated with the uplink phase tracking reference signal (PTRS); Receive an indication of an uplink resource silence mode, wherein the uplink resource silence mode overlaps with the physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation. as well as Perform a silent mode for the uplink resources that overlap with the PUSCH carrying the uplink PTRS.

22. The method according to claim 21, further comprising: According to the aforementioned processing, the uplink PTRS is transmitted via the PUSCH at least in part based on the fact that the uplink PTRS takes precedence over the uplink resource silent mode; or According to the described procedure, the uplink resource silencing mode is used at least in part based on the fact that the uplink resource silencing mode takes precedence over the uplink PTRS.

23. The method according to claim 21, wherein: The PUSCH carrying the uplink PTRS is associated with Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM); or The PUSCH carrying the uplink PTRS is associated with Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

24. The method of claim 21, wherein performing the disposal further comprises: The uplink resource silent mode and the uplink PTRS are prohibited from overlapping on the same symbol.

25. The method of claim 21, wherein performing the disposal further comprises: The uplink resource silent mode is allowed to overlap with the uplink PTRS on the same symbol; as well as The uplink resource silent mode and the uplink PTRS are defined to different resource elements.

26. The method of claim 21, wherein performing the disposal further comprises: The uplink resource silent mode takes precedence over the uplink PTRS, wherein the PTRS symbol is skipped at least in part based on the overlap of the PTRS symbol with the silent resource element; or The uplink PTRS is prioritized over the uplink resource silence mode, at least in part, based on the conflict between the uplink resource silence mode and the uplink PTRS on one or more resource elements (REs), wherein uplink silence is skipped for the one or more REs.

27. The method of claim 21, wherein performing the disposal further comprises: Uplink resource silencing is disabled on the PUSCH. The uplink PTRS is dropped at least in part based on the overlap between the uplink resource silent mode and the PUSCH. or The uplink PTRS is given priority at least in part based on the overlap between the uplink resource silencing mode and the PUSCH, wherein uplink silencing is not performed on the overlapping resources.

28. The method of claim 21, wherein the uplink resource silent mode and the uplink PTRS are allowed on the same symbol and configured on different resource elements (REs), and the method further comprises: Increase the power of the remaining uplink shared channel REs to compensate for the silent REs; or Increase the power of the uplink PTRS to compensate for quiescent REs, wherein the power of the uplink PTRS is increased at least in part based on implicit power boost in addition to the legacy PTRS power boost factor, or the power of the uplink PTRS is increased using a separate power boost factor to be used when the uplink PTRS overlaps with the uplink resource quiescent mode.

29. A method for wireless communication performed by a network node, the method comprising: Send the configuration associated with the uplink phase tracking reference signal (PTRS); Send an indication of an uplink resource quiz mode, wherein the uplink resource quiz mode overlaps with the physical uplink shared channel (PUSCH) carrying the uplink PTRS in subband full-duplex operation; as well as The uplink PTRS is received at least in part based on the handling of the uplink resource silent mode that overlaps with the PUSCH carrying the uplink PTRS.

30. The method according to claim 29, further comprising: According to the described procedure, the uplink PTRS is received via the PUSCH at least in part based on the fact that the uplink PTRS takes precedence over the uplink resource silent mode.

Images