Sub-band full-duplex awareness for network-controlled repeaters

Abstract

Various aspects of this disclosure relate generally to wireless communication. In some aspects, a repeater node can receive subband full-duplex (SBFD) configuration information associated with a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols. The repeater node can forward communications received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information. Numerous other aspects are described.

Description

Cross-references to related applications

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 608,655, filed March 18, 2024, entitled “SUB-BAND FULL-DUPLEXAWARENESS FOR A NETWORK-CONTROLLED REPEATER”, which is 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 more particularly to techniques, apparatus and methods associated with sub-band full-duplex sensing (SBFD) of repeaters (NCRs) for network control. 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] Some aspects described herein relate to a repeater node for wireless communication. The repeater node may include: one or more memories; and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive sub-band full-duplex (SBFD) configuration information associated with a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates a forwarding direction for the repeater node within the one or more SBFD symbols. The one or more processors may be configured to forward communications received within the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0006] Some aspects described herein relate to a method for wireless communication performed by a repeater node. The method may include: receiving SBFD configuration information associated with a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates a forwarding direction for the repeater node within the one or more SBFD symbols. The method may include: forwarding communication received within the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0007] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving SBFD configuration information associated with a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates a forwarding direction for the apparatus within the one or more SBFD symbols. The apparatus may include components for forwarding communications received within the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0008] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a repeater node. When executed by one or more processors of the repeater node, the set of instructions enables the repeater node to receive SBFD configuration information associated with a network node from a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates a forwarding direction for the repeater node within those one or more SBFD symbols. When executed by one or more processors of the repeater node, the set of instructions enables the repeater node to forward communications received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0009] 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.

[0010] 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

[0011] 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.

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

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

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

[0015] Figure 4 This is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0016] Figure 5 This is an illustration of an example of a full-duplex deployment scenario according to this disclosure.

[0017] Figure 6A This is a diagram illustrating examples of different duplex modes according to this disclosure.

[0018] Figure 6B This is a diagram illustrating an example of subband full-duplex (SBFD) activation according to this disclosure.

[0019] Figure 7 This is a diagram illustrating an example of a network-controlled repeater (NCR) according to this disclosure.

[0020] Figures 8A to 8C This is a diagram illustrating an example of SBFD perception associated with NCR according to this disclosure.

[0021] Figure 9 This is a flowchart illustrating an example procedure performed by an NCR, for example, according to this disclosure.

[0022] Figure 10 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0023] 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 so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection 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 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 practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0024] 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.

[0025] In some cases, a wireless network may include one or more repeaters (e.g., one or more network-controlled repeater (NCR) nodes) that receive radio frequency (RF) signals (e.g., analog RF signals) from network nodes, amplify the RF signals, and transmit or forward the amplified RF signals to user equipment (UE). For example, one or more repeaters may include one or more analog repeaters, sometimes referred to as Layer 1 (L1) repeaters. Additionally or alternatively, one or more repeaters may include one or more radio transmit / receive points (TRPs) that act as distributed units (DUs) or radio units (RUs) and communicate wirelessly with network nodes that act as central units (CUs) or access node controllers. One or more repeaters may receive, amplify, and transmit analog RF signals without performing analog-to-digital conversion on the analog RF signals and / or without performing any digital signal processing on the RF signals. Alternatively, one or more repeaters may transmit the received RF signals after decoding the received RF signals and / or modifying the information carried in the received RF signals. In this way, one or more repeaters can improve network performance and / or increase reliability by providing link diversity and / or extending the communication coverage area of ​​network nodes.

[0026] Another technique that can be used to improve performance in wireless networks is to implement full-duplex communication, which typically involves simultaneous bidirectional communication between devices in the wireless network. For example, a network node operating in full-duplex mode can simultaneously (e.g., in the same time slot or the same symbol) receive uplink communication and transmit downlink communication. For instance, a network node can support sub-band full-duplex (SBFD) communication mode, which may also be referred to as "sub-band frequency division duplex (SBFDD)" mode, "flexible duplex" mode, etc. In SBFD mode, a network node can receive uplink communication from a first UE and simultaneously transmit downlink communication to a second UE on a different frequency resource. For example, the different frequency resources could be sub-bands of a band such as a time division duplex (TDD) band. In this case, the frequency resources used for downlink communication can be separated from the frequency resources used for uplink communication in the frequency domain by one or more guard bands. In this way, SBFD mode can facilitate increased throughput by allowing simultaneous uplink and downlink communication, reduce latency by allowing uplink and / or downlink communication to occur earlier in time, and / or increase spectral efficiency by simultaneously utilizing downlink and uplink resources.

[0027] However, in some network deployments, SBFD communication modes may be supported only by network nodes, where other nodes such as the UE and NCR are limited to TDD or half-duplex operation (e.g., transmitting or receiving only in any given transmission time interval). For example, the NCR typically uses semi-static TDD information provided by the network node to the NCR's mobile terminal (MT) component to determine the forwarding direction (downlink or uplink) to be used by the NCR's forwarding (FWD) component in each symbol or time slot. As described herein, the NCR's FWD component typically forwards wideband analog signals over an operational bandwidth that covers one or more component carriers used by the MT component to communicate with the network node, and the FWD component is deactivated or turned off within semi-static flexible resources (e.g., available as uplink or downlink resources). Although the UE is typically limited to half-duplex operation, a half-duplex UE can be SBFD-aware (e.g., able to receive information indicating the SBFD configuration of the network node), allowing the SBFD-aware UE to adjust scheduling, measurement, and / or other operations within an SBFD symbol.

[0028] The various aspects collectively involve providing repeater nodes with information related to the SBFD configuration associated with network nodes, enabling repeater nodes to adjust operations within one or more SBFD symbols and / or non-SBFD symbols to improve forwarding services used to extend the coverage of network nodes. For example, in some aspects, information may be provided to repeater nodes indicating the SBFD configuration associated with the network node and indicating whether the repeater node should forward communications in the uplink or downlink direction within one or more SBFD symbols. For example, in some aspects, network nodes may provide repeater nodes with a semi-static indication of the SBFD configuration used by the network node, which may indicate SBFD time resources (e.g., SBFD symbols or SBFD time slots) and / or SBFD subband configuration. Furthermore, the forwarding direction to be used in an SBFD symbol may be indicated dynamically or semi-statically, and the forwarding direction may be common to all SBFD symbols or may be indicated in a granular manner (e.g., using different forwarding directions in different sets or subsets of SBFD symbols). Additionally or alternatively, the forwarding direction may be implicitly indicated based on one or more configurations or rules or on the specific implementation of the repeater node. Furthermore, some aspects described herein relate to forwarding operations that can be used by the repeater node based on: the repeater node's subband filtering capabilities; SBFD configuration indications based on SBFD configurations provided for the repeater node's MT component with SBFD capabilities; different communication configurations to be used in SBFD and / or non-SBFD symbols; and / or techniques for applying SBFD configurations associated with network nodes to repeater nodes with bidirectional forwarding capabilities.

[0029] 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 providing repeater nodes with information related to the SBFD configuration used by the network nodes controlling the repeater nodes, the described techniques can be used to configure operations to improve the forwarding operations and / or forwarding services provided by the repeater nodes to repeater nodes operating according to the SBFD configuration. For example, a repeater node can be configured to forward communication in the uplink direction in one or more SBFD symbols to improve uplink performance and / or forward communication in the downlink direction in one or more SBFD symbols to improve downlink performance. Furthermore, some aspects described herein can be used to dynamically or semi-statically indicate the forwarding direction to be used by the repeater nodes to improve performance during periods of time associated with traffic that is busy on the uplink or downlink.

[0030] 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).

[0031] As the demand for broadband access increases and as the technologies supported by wireless communication networks evolve, 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 for 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 ambient IoT) networks, redcap UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, 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 manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. 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.

[0032] 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 elements of 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 UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0033] 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 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 RATs, 5G / NRRATs, and / or 6G RATs, 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.

[0034] 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.

[0035] 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), TRP, mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in the radio access network (RAN).

[0036] 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.

[0037] 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.

[0038] Network nodes 110 of the wireless communication network 100 may include one or more CUs, one or more DUs, and / or one or more 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 those 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 architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0039] 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.

[0040] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for a specific geographic area. 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 macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell can be referred to as a macro network node. Network node 110 used for a picocell 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 move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0041] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet network nodes, femtonet network nodes, relay network nodes, repeater 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, relay network nodes, and repeater network nodes can have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0042] In some examples, network node 110 may be, may include, or may 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. "Downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and "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 physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0043] 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, and / or resource elements), 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 allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). 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.

[0044] 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, repeater 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. In some examples, 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.

[0045] In some examples, any network node 110 that forwards communications may be referred to as a repeater network node, repeater station, repeater, relay network node, relay station, or relay. A repeater or relay may receive communications from an upstream station (e.g., another network node 110 or UE 120) and forward 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 repeater 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 repeater or relay station capable of forwarding transmissions to or from other UE 120s, or can operate as such a repeater or relay station. The UE 120 forwarding communications can be referred to as a UE repeater, repeater UE, UE relay, or relay UE, etc.

[0046] 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, or may be included in the following: access terminal, another terminal, mobile station, or 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 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.

[0047] 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. The 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 can be configured to perform the set of functions.

[0048] 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 include, or may be included in, a housing that accommodates components associated with UE 120, including the processing system.

[0049] 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 collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, 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).

[0050] 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 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 first-category UEs 120 and second-capability UEs 120). 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.

[0051] 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.

[0052] 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 TDD, in which the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., these 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., in 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.

[0053] 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 techniques typically utilize 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 RATs can employ advanced MIMO techniques such as mTRP operations (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).

[0054] In some aspects, a repeater node (e.g., repeater network node 110d) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive SBFD configuration information associated with a network node (e.g., network node 110a), wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols; and forwards communications received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0055] 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.

[0056] 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.

[0057] like Figure 2 As 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.

[0058] 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 2The 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.

[0059] 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.

[0060] 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)).

[0061] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may 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 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the downlink signal set (e.g., ...) together via the corresponding set of antennas 234. T (One downlink signal).

[0062] 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.

[0063] 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 by MIMO detector 236 (e.g., receive (Rx) MIMO processor) where applicable, 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.

[0064] 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.

[0065] 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 between analog signals (such as those used for transmission or reception via an air interface) and 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.

[0066] 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, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0067] 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, and / or a memory 282, 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 aspects, may perform aspects of the methods, processes, 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.

[0068] 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 receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may 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 may obtain the received symbols from the set of modems 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and provide the decoded control information and system information to controller / processor 280.

[0069] 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 CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0070] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set 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 output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may 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 the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0071] Modems 254a to 254u can transmit uplink signal sets (e.g., via corresponding sets of antennas 252) R One uplink signal or U Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use 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).

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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).

[0076] 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.

[0077] Figure 3This 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.

[0078] 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.

[0079] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (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. 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.

[0080] The SMO framework 360 supports RAN deployment and provisioning for 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 the 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.

[0081] 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 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.

[0082] 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 can 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 modulate 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 via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0083] 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.

[0084] 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 technologies associated with SBFD awareness for NCR or perform one or more operations associated therewith, 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 technologies associated with SBFD awareness for NCR or perform one or more operations associated therewith, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 9 The operation of process 900 or other processes as described herein. In some respects, the repeater node, NCR, or NCR node described herein is Figure 2 The network node 110 shown is included Figure 2 Among the network nodes 110 shown, including Figure 2 One or more components of the network node 110 shown, and / or including Figure 2One or more components of the UE 120 shown. 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 9 The process 900 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.

[0085] In some aspects, the repeater node includes components for receiving SBFD configuration information associated with network node 110 from network node 110, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols; and / or components for forwarding communications received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information. In some aspects, components for the repeater node to perform the operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246. Additionally or alternatively, components for the repeater node to perform the operations described herein may include, for example, one or more of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0086] 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.

[0087] Figure 4These are illustrations of examples 400, 405, and 410 of full-duplex communication in a wireless network according to this disclosure. As described herein, “full-duplex communication” refers to the simultaneous uplink and downlink communication in a wireless network, which can be the capability of a UE, a network node, or another suitable device (e.g., the MT component and / or FWD component of an NCR). For example, a UE operating in full-duplex mode can transmit uplink communication and receive downlink communication at the same time (e.g., in the same time slot or the same symbol), and a network node operating in full-duplex mode can receive uplink communication and transmit downlink communication at the same time. “Half-duplex communication” in a wireless network refers to unidirectional communication at a given time (e.g., downlink communication only or uplink communication only) (e.g., a device only transmits or only receives in a given time slot or a given symbol). In some cases, one or more nodes in a wireless network may support both full-duplex and half-duplex communication, and other nodes may support only half-duplex communication. For example, in some aspects, network nodes may support both full-duplex and half-duplex communication, and one or more UEs and / or repeater nodes may support only half-duplex communication. In another example, a repeater node may include an MT component that supports both full-duplex and half-duplex communication and an FWD component that supports only half-duplex communication.

[0088] like Figure 4 As shown, Examples 400 and 405 illustrate examples of in-band full-duplex (IBFD) communication. In a scenario where the network node supports IBDF and the UE only supports half-duplex communication, the network node can receive uplink communication from a first UE and can send downlink communication to a second UE on the same time and frequency resources. As shown in Example 400, in the first example of IBDF, the time and frequency resources used for uplink communication can completely overlap with those used for downlink communication (e.g., all time and frequency resources allocated to uplink communication can also be used for downlink communication). As shown in Example 405, in the second example of IBDF, the time and frequency resources used for uplink communication can partially overlap with those used for downlink communication (e.g., some time and frequency resources are reserved for uplink communication only).

[0089] like Figure 4As further illustrated, Example 410 shows an example of SBFD communication, which may also be referred to as "Subband Frequency Division Duplex (SBFDD)," "Flexible Duplex," or "FDD in Unpaired Spectrum." In some aspects, the SBFD communication mode may be supported solely by network nodes, by network nodes and UEs, by network nodes and repeater nodes, and / or by any suitable combination thereof. In SBFD communication, nodes operating according to an SBFD configuration may simultaneously transmit and receive different communications on different frequency resources. For example, a network node operating according to an SBFD configuration may simultaneously receive uplink communication from a first UE in an uplink subband and transmit downlink communication to a second UE in a downlink subband, where the uplink and downlink subbands may occupy different frequency resources. Similarly, when a UE supports an SBFD configuration, the UE may transmit uplink communication to and receive downlink communication from a network node at the same time but on different frequency resources. For example, different frequency resources may be subbands of a band such as a TDD band. In this case, frequency resources used for downlink communication can be separated from frequency resources used for uplink communication in the frequency domain by guard bands.

[0090] 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.

[0091] Figure 5 These are illustrations of examples 500, 510, and 520 illustrating a full-duplex deployment scenario according to this disclosure. For example... Figure 5 As shown, Examples 500, 510, and 520 include one or more UEs communicating with one or more network nodes in a wireless network supporting full-duplex communication. Generally, as described herein, utilizing full-duplex communication modes can provide reduced latency by allowing downlink transmissions to occur only in uplink symbols or time slots and / or by allowing uplink transmissions to occur only in downlink symbols or time slots. Furthermore, by simultaneously utilizing time and frequency resources for downlink and uplink communication, full-duplex communication can improve spectral efficiency or throughput per cell or per UE, and / or achieve more efficient resource utilization. However, as described further in detail herein, full-duplex communication modes can be associated with dynamic interference conditions.

[0092] For example, such as Figure 5 As shown, Example 500 includes a first UE (shown as UE1) and a second UE (shown as UE2) communicating with a first network node (shown as NN1) operating in full-duplex mode, wherein the first UE and the second UE operate in half-duplex mode. For example, as Figure 5As shown, a first UE can send one or more uplink transmissions to a first network node, and a second UE can concurrently receive one or more downlink transmissions from the first network node. Therefore, in Example 500, the first network node operates in full-duplex mode, and the first and second UEs each operate in half-duplex mode. As shown in Example 500, various forms of interference may exist, which may degrade the downlink reception performance at one or more UEs and / or the uplink reception performance at the first network node operating in full-duplex mode. For example, as shown, the first network node may experience cross-link interference (CLI) caused by downlink transmissions from a second network node (shown as NN2) that may be located in an adjacent or nearby cell. Furthermore, as shown, uplink transmissions from the first UE to the first network node can cause CLIs at the second UE (e.g., CLIs interfering with downlink reception at the second UE). Additionally, as shown, the first network node may experience self-interference, where downlink transmissions to the second UE interfere with the reception of uplink transmissions from the first UE. For example, as described herein, self-interference can typically occur when a transmitted signal leaks into the receiving port and / or when objects in the surrounding environment reflect the transmitted signal back to the receiving port (e.g., causing clutter echo effects), thus interfering with the reception of the desired signal at the receiving port. Generally, the full-duplex mode used by the first network node in Example 500 could be SBFD mode, where the component carrier bandwidth is divided into one or more uplink subbands and one or more downlink subbands separated by one or more guard bands.

[0093] like Figure 5Further, in Example 510, the first UE can communicate with the first network node in full-duplex mode. For example, in Example 510, the first UE can receive one or more downlink transmissions from the first network node, and the first UE can concurrently send one or more uplink transmissions to the first network node. Therefore, in Example 510, both the first network node and the first UE operate in full-duplex mode. Furthermore, as shown, the first network node can communicate with a second UE operating in half-duplex mode. As shown in Example 510, the first UE can experience self-interference, where uplink transmission interference to the first network node originates from the reception of downlink transmissions by the first network node, and the first UE can cause cross-link interference at the second UE, where uplink transmission interference to the first network node interferes with downlink reception at the second UE. Additionally, in Example 510, the first network node may experience CLI caused by one or more downlink transmissions from the second network node interfering with the reception of uplink transmissions from the first UE, and the first network node may experience self-interference, wherein the downlink transmissions to the first UE and / or the second UE interfere with the reception of uplink transmissions from the first UE. In Example 510, full-duplex communication may be performed in SBFD mode (where the component carrier bandwidth is divided into non-overlapping uplink and downlink subbands) or in IBFD mode (where uplink and downlink resources are fully or partially overlapping).

[0094] like Figure 5 Further illustrated, in Example 520, the first UE can communicate with the first and second network nodes in full-duplex mode (e.g., multi-TRP mode). For example, in Example 520, the first UE can send one or more uplink transmissions to the first network node, and the first UE can concurrently receive one or more downlink transmissions from the second network node. Therefore, in Example 520, the first UE operates in full-duplex mode, and both the first and second network nodes operate in half-duplex mode. As shown in Example 520, the first UE may experience self-interference, where uplink transmissions to the first network node interfere with the reception of downlink transmissions from the second network node. Furthermore, uplink transmissions performed by the first UE can cause CLIs at the second UE that is receiving downlink transmissions from the second network node. Additionally, as shown, downlink transmissions performed by the second network node can cause CLIs at the first network node that interfere with the reception of uplink transmissions from the first UE. In Example 520, full-duplex communication can be performed in SBFD mode (where the component carrier bandwidth is divided into non-overlapping uplink and downlink subbands) or in IBFD mode (where the uplink and downlink resources are fully or partially overlapping).

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

[0096] Figure 6A This is a diagram illustrating example 600 according to different duplex modes of this disclosure, and Figure 6B This is a diagram illustrating an example 600B activated according to the SBFD of this disclosure. For example, as described in further detail herein, Figure 6A Examples 610 illustrate an FDD mode that can be used in paired spectrum, 620 illustrate a TDD mode that can be used in unpaired spectrum, and 630 illustrate an SBFD mode that can be used in unpaired spectrum. Figure 6B Example 600B illustrates a technique that can be used to activate SBFD mode.

[0097] In some respects, wireless communication standards and / or regulatory bodies can typically specify one or more duplex modes for the use of radio spectrum. For example, 3GPP can specify how radio spectrum is used for 5G / NR radio access technologies and interfaces. For instance, specifications can indicate whether a frequency band is used as paired spectrum in FDD mode or as unpaired spectrum in TDD mode.

[0098] For example, as shown in Example 610, paired spectrum in FDD mode can use a first frequency region (or channel) for uplink communication and a second frequency region (or channel) for downlink communication. In these cases, the frequency regions or channels used for uplink and downlink communication do not overlap, have different center frequencies, and are sufficiently spaced to prevent interference between downlink and uplink communication. For example, paired spectrum in FDD mode can include uplink operating bands and downlink operating bands configured to use non-overlapping frequency regions separated by guard bands. Therefore, when operating in FDD mode in paired spectrum, a network node or UE with full-duplex capability can perform concurrent transmit and receive operations using the separate operating bands allocated to downlink and uplink communication. For example, paired bands in NR include NR operating bands n1, n2, n3, n5, n7, n8, n12, n20, n25, and n28, as specified in 3GPP Technical Specification (TS) 38.101-1.

[0099] Alternatively, as shown in Example 620, unpaired spectrum in TDD mode can allow downlink and uplink operation within a single frequency region (e.g., a single operating band). For example, when operating in TDD mode in unpaired spectrum, downlink and uplink communication can occur in the same frequency range. Some deployments can use TDD in unpaired bands, whereby some transmission time intervals (e.g., frames, slots, and / or symbols) are used for downlink-only communication, and other transmission time intervals are used for uplink-only communication. In this case, depending on whether communication is performed in a downlink interval, an uplink interval, or a special interval (in which downlink or uplink communication can be scheduled), essentially the entire bandwidth of the component carrier can be used for downlink or uplink communication. Examples of unpaired bands include NR operating bands n40, n41, and n50, as specified in 3GPP TS 38.101-1. However, in some cases, using TDD in unpaired spectrum can be inefficient. For example, uplink transmit power may be limited, meaning the UE may not be able to transmit with sufficient power, thus failing to efficiently utilize the full bandwidth of the uplink time slot. This can be particularly problematic at the cell edges of larger cells. Furthermore, TDD can introduce latency compared to a full-duplex scheme that can perform both uplink and downlink communication within the same time interval, as TDD restricts the use of a given transmission time interval to either uplink or downlink communication only. Additionally, by restricting the use of a given transmission time interval to either uplink or downlink communication only, TDD can reduce spectral efficiency and / or throughput.

[0100] Therefore, as shown in Example 630, unpaired frequency bands can be configured in full-duplex mode to enable concurrent transmit and receive operations in unpaired spectrum (e.g., TDD bands). For example, in Figure 6A In Example 630, an SBFD mode is depicted, which may be referred to herein as frequency division multiplexing (FDM) mode or full-duplex using other appropriate terms, to enable TDD and / or FDD operations in unpaired spectrum. For example, as Figure 6AAs shown, the unpaired frequency bands configured in SBFD mode can associate one or more transmission time intervals with downlink-only communication (e.g., "D" time slot), one or more transmission time intervals with uplink-only communication (e.g., "U" time slot), and one or more transmission time intervals with both downlink and uplink communication (e.g., "D+U" time slot). Each transmission time interval can be associated with a control area, which is exemplified as a portion of a time interval with diagonal padding for uplink control (e.g., PUCCH) or darker shading padding for downlink control (e.g., PDCCH). Additionally or alternatively, each time interval can be associated with a data area, which is shown as a PDSCH for downlink frequency areas or a PUSCH for uplink frequency areas.

[0101] In some respects, unpaired frequency bands configured in SBFD mode may include one or more downlink-only time intervals, one or more uplink-only time intervals, and / or one or more full-duplex time intervals (e.g., frames, subframes, time slots, and / or symbols, etc.) associated with the FDD configuration. For example, as Figure 6A As shown, the FDD configuration associated with a full-duplex time interval can indicate one or more downlink frequency zones (or sub-bands) and one or more uplink frequency zones (or sub-bands) separated by guard bands. Therefore, the FDD configuration can divide unpaired frequency bands (e.g., one or more component carriers of an unpaired frequency band) into uplink frequency zones, downlink frequency zones, and / or other zones (e.g., guard bands, etc.). This allows a network node or UE with full-duplex capability to perform simultaneous transmission and reception operations during one or more time intervals divided into downlink and uplink sub-bands with guard band spacing, preventing uplink transmission from causing self-interference relative to downlink reception. For example, in a given full-duplex time interval, a half-duplex UE can transmit using the uplink frequency zone or receive using the downlink frequency zone (e.g., a UE communicating in half-duplex mode can receive only in the downlink frequency zone or transmit only in the uplink frequency zone during a full-duplex time interval). Alternatively, a full-duplex UE can transmit using the uplink frequency zone and / or receive using the downlink frequency zone. Additionally or alternatively, a full-duplex network node can transmit downlink communication to a first UE in the downlink frequency zone and simultaneously receive uplink communication from a second UE in the uplink frequency zone. In some aspects, the FDD configuration can identify the BWP configuration corresponding to the uplink and downlink frequency zones. For example, the corresponding BWP can be configured for each uplink frequency zone and each downlink frequency zone.

[0102] Additionally or alternatively, full-duplex communication can be enabled in unpaired spectrum in IBFD mode, which may be referred to herein as full-duplex in spatial division multiplexing (SDM) mode. For example, in IBFD or SDM mode, uplink communication may occur on time and frequency resources that completely overlap with those allocated to downlink communication (e.g., all time and frequency resources available for uplink communication can also be used for downlink communication), or on time and frequency resources that partially overlap with those available for downlink communication (e.g., some time and frequency resources available for uplink communication can also be used for downlink communication, and some time and frequency resources available for uplink communication are uplink-only). Generally, in IBFD mode, full-duplex communication may depend on sufficient beam separation between the uplink and downlink beams (e.g., uplink transmission may originate from one antenna panel and downlink reception may originate from another antenna panel) to minimize self-interference that may occur when transmitted signals leak into the receiver port and / or when objects in the surrounding environment reflect transmitted signals back to the receiver port (e.g., causing spurious echo effects).

[0103] In some cases, as described herein, one or more frequency zones supporting SBFD communication can be configured to dynamically switch between TDD mode and SBFD mode operation. For example, as... Figure 6B As shown, Example 600B includes a first configuration 640 (e.g., a legacy or default configuration associated with TDD mode). In some aspects, the first configuration 640 may indicate a first timeslot format mode (sometimes referred to as TDD mode) associated with a half-duplex mode (e.g., where each interval is downlink-only or uplink-only). The first timeslot format mode may include one or more downlink intervals (e.g., shown as three downlink timeslots 642a, 642b, and 642c, but each downlink interval may correspond to a downlink symbol or another suitable transmission time interval for downlink communication), one or more flexible intervals (not shown), and / or one or more uplink intervals (e.g., shown as one uplink timeslot 644, but each uplink interval may correspond to an uplink symbol or another suitable transmission time interval for uplink communication). The first timeslot format mode may repeat over time. In some aspects, network node 110 may use one or more timeslot format indicators to indicate the first timeslot format mode to UE 120. The time slot format indicator used for a time slot can indicate whether the corresponding time slot is an uplink time slot, a downlink time slot, or a flexible time slot (for example, it can be used as an uplink or downlink time slot).

[0104] Network node 110 may (e.g., using indications such as RRC messages, MAC-CE, or DCI) instruct UE 120 to switch from first configuration 640 to second configuration 650. Alternatively, UE 120 may indicate to network node 110 that UE 120 is switching from first configuration 640 to second configuration 650. Second configuration 650 may indicate a second time slot format pattern that repeats over time, similar to the first time slot format pattern. In any of the aspects described above, UE 120 may switch from first configuration 640 to second configuration 650 for a period of time (e.g., a number of symbols and / or a certain amount of time (e.g., in milliseconds)) based at least in part on an indication received from network node 110 (e.g., before switching back to first configuration 640). During this period, UE 120 may communicate using the second time slot format pattern and may then revert to using the first time slot format pattern after the end of the period. The time period may be indicated by network node 110 (e.g., in an instruction to switch from first configuration 640 to second configuration 650, as described above) and / or at least partially based on programmed and / or otherwise pre-configured rules. For example, the rules may be at least partially based on a table (e.g., defined in a 3GPP specification and / or another wireless communication standard) that associates different subcarrier spacings (SCS) and / or sets of parameters (e.g., represented by µ and associated with corresponding SCS) with corresponding time periods for switching configurations.

[0105] In Example 600B, the second timeslot format mode includes two SBFD timeslots in place of the downlink timeslots in the first timeslot format mode. In Example 600B, the second timeslot format mode includes a downlink timeslot 652 followed by one or more SBFD timeslots, each of which includes a portion of the timeslots for the downlink (e.g., a portion or subband of a frequency allocated for use by network node 110 and UE 120) (e.g., portions of timeslots 654a, 654b, 654c, and 654d as shown) and a portion of the timeslots for the uplink (e.g., portions of timeslots 656a and 656b as shown), followed by an uplink timeslot 658. Therefore, compared to using the first time slot format mode (e.g., the fourth time slot in the sequence, shown as uplink time slot 644), UE 120 can operate using the second time slot format mode to transmit uplink communication in an earlier time slot (e.g., the second time slot in the sequence, shown as partial uplink time slot 656a). Other examples may include additional or alternative variations. For example, the second configuration 650 may indicate an SBFD time slot instead of an uplink time slot (e.g., uplink time slot 644) in the first configuration 640. In another example, the second configuration 650 may indicate a downlink time slot or an uplink time slot instead of an SBFD time slot in the first configuration 640. Figure 6B (Not shown in the image). In another example, the second configuration 650 may indicate a downlink time slot or an uplink time slot to replace the uplink time slot or downlink time slot in the first configuration 640, respectively. "SBFD time slot" may refer to a time slot in which the SBFD format is used. The SBFD format may include a time slot format in which (e.g., for both uplink and downlink communication) full-duplex communication is supported, wherein one or more frequencies for the uplink portion of the time slot are separated from one or more frequencies for the downlink portion of the time slot by guard bands. In some aspects, the SBFD format may include a single uplink portion and a single downlink portion separated by guard bands. In some aspects, the SBFD format may include multiple downlink portions and a single uplink portion, the single uplink portion being separated from the multiple downlink portions by corresponding guard bands (e.g., as shown in the image). Figure 6B(As shown). In some aspects, the SBFD format may include multiple uplink portions and a single downlink portion, the single downlink portion being separated from the multiple uplink portions by corresponding guard bands. In some aspects, the SBFD format may include multiple uplink portions and multiple downlink portions, wherein each uplink portion is separated from the downlink portion by a guard band. In some aspects, operating using SBFD mode may include activating or using full-duplex (FD) mode in one or more time slots, at least in part, based on one or more time slots having the SBFD format. A time slot may support SBFD mode if uplink bandwidth portions and downlink bandwidth portions are permitted to be active or simultaneously active in a time slot in an SBFD manner (e.g., separated by guard bands).

[0106] By switching from the first configuration 640 to the second configuration 650, network node 110 and UE 120 may experience increased communication quality and / or reliability. For example, network node 110 and UE 120 may experience increased throughput (e.g., using full-duplex mode), reduced latency (e.g., UE 120 may be able to use the second configuration 650 instead of the first configuration 640 to send uplink and / or downlink communications faster), and increased network resource utilization (e.g., by using both downlink and uplink bandwidth portions simultaneously instead of using only the downlink or uplink bandwidth portions).

[0107] As indicated above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0108] Figure 7 This is a diagram illustrating example 700 of the NCR according to this disclosure. In some aspects, such as Figure 7 As shown, Example 700 includes an NCR node 730, which can be configured to forward communication between network node 710 and UE 720 in the wireless network. Figure 7 As shown, NCR node 730 may include MT component 732 (shown as NCR-MT component) that can communicate with network node 710 via control link 740, and FWD component 734 (shown as NCR-FWD component) that can communicate with network node 710 via backhaul link 742 (shown as NCR-FWD backhaul link) and with UE 720 via access link 744 (shown as NCR-FWD access link). In some aspects, network node 710 may be network node 110, CU 310 and / or DU 330 as described herein. Furthermore, UE 720 may be UE 120 as described herein, and NCR node 730 may be relay network node 110d and / or RU 340 as described herein. Therefore, as described herein, the NCR-FWD component 734 of the NCR node 730 can be configured to receive downlink access link transmissions (e.g., PDCCH or PDSCH) destined for the UE 720 from the network node 710 via the NCR-FWD backhaul link 742, and can forward the downlink access link transmissions to the UE 720 via the NCR-FWD access link 744 (e.g., sending a regenerated version of the downlink access link transmission). Furthermore, the NCR-FWD component 734 of the NCR node 730 can be configured to receive uplink access link transmissions (e.g., PUCCH or PUSCH) destined for the network node 710 from the UE 720 via the NCR-FWD access link 744, and can forward the uplink access link transmissions to the network node 710 via the NCR-FWD backhaul link 742 (e.g., sending a regenerated version of the uplink access link transmission). Therefore, as shown in the figure, the access link connection between network node 710 and UE 720 may include downlink and uplink services routed via NCR-FWD component 734 of NCR node 730. For example, as described herein, NCR-MT component 732 may communicate with network node 710 via control link 740 to exchange side control information, which may have a configuration similar to the Uu interface in an NR network.

[0109] Furthermore, the NCR-FWD component 734 can be configured to perform amplification and forwarding processing to repeat downlink RF signals received from network node 710 via NCR-FWD backhaul link 742 and / or repeat uplink RF signals received from UE 720 via NCR-FWD access link 744. In some aspects, as described herein, various behaviors of the NCR-FWD component 734 can be controlled based on side control information received by the NCR-MT component 732 from network node 710 via control link 740. For example, as described herein, the side control information may include receive configuration, buffer configuration, forwarding configuration, information requests, and / or any other suitable configuration or control information related to the forwarding of RF signals between network node 710 and UE 720. In some respects, as described herein, NCR node 730 can be configured as an in-band RF repeater to extend coverage in one or more frequency bands or ranges (e.g., FR1 and / or FR2), and can be deployed in a single-hop fixed configuration transparent to UE 720 (e.g., only one NCR node 730 exists between network node 710 and UE 720, and NCR node 730 does not move or otherwise change location). Furthermore, in some respects, NCR node 730 can simultaneously maintain a first link with network node 710 and a second link with UE 720, allowing RF signals to be repeated by NCR node 730 with low additional latency.

[0110] In some cases, as described herein, full-duplex communication can be implemented in a wireless network to improve performance (e.g., by reducing latency or improving spectral efficiency). For example, network node 710 may support SBFD communication mode, where network node 710 can use different frequency resources (e.g., downlink subbands and uplink subbands) to simultaneously receive uplink communication from a first UE 720 and send downlink communication to a second UE 720. However, in some network deployments, SBFD communication mode may be supported only by network node 710, where other nodes such as UE 720 and NCR node 730 are limited to TDD or half-duplex operation (e.g., only transmitting or only receiving in any given transmission time interval). For example, NCR node 730 typically uses semi-static TDD information provided by (controlling) network node 710 to the MT component 732 of NCR node 730 to determine the forwarding direction (downlink or uplink) to be used by the FWD component 734 of NCR node 730 in each symbol or time slot. Although the FWD component 734 of the NCR node 730 may be limited to half-duplex operation, providing the NCR node 730 with information related to the SBFD configuration associated with the network node 710 allows the NCR node 730 to adjust the operation within one or more SBFD symbols and / or non-SBFD symbols to improve the forwarding service used to extend the coverage of the network node 710.

[0111] For example, as described herein, NCR node 730 may be provided with information indicating the SBFD configuration associated with network node 710 and indicating whether the repeater node should forward communication in the uplink or downlink direction within one or more SBFD symbols. For example, in some aspects, network node 710 may provide the repeater node with a semi-static indication of the SBFD configuration used by network node 710, which may indicate SBFD time resources (e.g., SBFD symbols or SBFD time slots) and / or SBFD subband configuration. Furthermore, the forwarding direction to be used in an SBFD symbol may be indicated dynamically or semi-statically, and the forwarding direction may be common to all SBFD symbols or may be indicated in a granular manner (e.g., using different forwarding directions in different sets or subsets of SBFD symbols). Additionally or alternatively, the forwarding direction may be implicitly indicated based on one or more configurations or rules or based on the specific implementation of NCR node 730. Furthermore, some aspects described herein relate to forwarding operations that can be used by NCR node 730 based on: the subband filtering capability of the repeater node, SBFD configuration indications based on the SBFD configuration provided for the MT component 732 with SBFD capability of NCR node 730, different communication configurations to be used in SBFD and / or non-SBFD symbols, and / or techniques for applying the SBFD configuration associated with network node 710 to NCR node 730 with bidirectional forwarding capability.

[0112] 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.

[0113] Figures 8A to 8C This is a diagram illustrating an example of SBFD perception associated with NCR according to this disclosure. For example... Figures 8A to 8C As shown, Example 800 includes communication between network node 810, NCR node 830 (e.g., a repeater node controlled by network node 810), and UE 820. In some aspects, network node 810 may correspond to network node 110, CU 310, DU 340, RU 340, and / or network node 710 as described herein; NCR node 830 may correspond to repeater network node 110d, DU 330, RU, and / or NCR node 830 as described herein; and UE 820 may correspond to UE 120 and / or UE 720 as described herein. In some aspects, network node 810, UE 820, and NCR node 830 may be included in a wireless network (such as wireless network 100). Network node 810 and UE 820 may communicate via a radio access link (which may include an uplink and a downlink).

[0114] In addition, the NCR node 830 may include an MT component ( Figures 8A to 8C (not shown in the image) and FWD components ( Figures 8A to 8C (Not shown in the diagram). For example, the MT component of NCR node 830 can communicate with network node 810 via a control link to exchange control information related to forwarding operations performed by the FWD component of NCR node 830, and the FWD component can forward communications in the uplink and / or downlink directions based on the control information received by the MT component. For example, when the control information configures NCR node 830 to perform a forwarding operation in the downlink direction, NCR node 830 can receive one or more downlink communications (e.g., PDCCH transmission, PDSCH transmission, downlink reference signal transmission, etc.) from network node 810 via a backhaul link, and can forward such one or more downlink communications to UE 820 via an access link. Additionally or alternatively, when the control information configures NCR node 830 to perform a forwarding operation in the uplink, NCR node 830 can receive one or more uplink communications (e.g., PUCCH transmission, PUSCH transmission, uplink reference signal transmission, etc.) from UE 820 via an access link, and can forward such one or more uplink communications to network node 810 via a backhaul link.

[0115] In some aspects, such as Figures 8A to 8C As shown by reference numeral 840 in the accompanying drawings, network node 810 can be configured to operate in SBFD communication mode, wherein the unpaired (e.g., TDD) band comprises one or more symbols configured to implement concurrent transmission and reception operations in the unpaired (e.g., TDD) band in full-duplex mode. For example, as described herein, the unpaired (e.g., TDD) band configured in SBFD mode may include one or more time resources dedicated to downlink communication (e.g., downlink-only slots or symbols), one or more time resources dedicated to uplink communication (e.g., uplink-only slots or symbols), and one or more time resources supporting full-duplex (e.g., simultaneous downlink and uplink) communication (e.g., SBFD slots or symbols). For example, as... Figures 8A to 8C As shown and described in more detail elsewhere in this document, one or more time resources supporting SBFD communication can divide frequency resources within a TDD band into one or more downlink subbands, and at most one uplink subband can be used to support SBFD operation within one or more time resources supporting SBFD communication on a TDD carrier (e.g., excluding any legacy uplink symbols), wherein one or more guard bands separate the downlink subband from the uplink subband. For example, in Figures 8A to 8CIn the figure, reference numeral 840 corresponds to an SBFD configuration, wherein the bandwidth of the TDD carrier is divided within one or more SBFD time resources into a first downlink subband spanning a first (lower) frequency, a second downlink subband spanning a second (higher) frequency, and an uplink subband spanning frequencies between the first and second downlink subbands. Furthermore, as further shown by reference numeral 840, the bandwidth of the TDD carrier may include a first guard band separating the first downlink subband from the uplink subband and a second guard band separating the second downlink subband from the uplink subband.

[0116] As described herein, some aspects relate to SBFD configuration, where downlink-only, uplink-only, and SBFD time resources are symbol-level resources. However, some aspects described herein can be similarly applied to wireless network deployments where downlink-only, uplink-only, and SBFD time resources are slot-level resources or associated with other suitable transmission time intervals. Furthermore, some aspects described herein relate to wireless network deployments where only network node 810 supports SBFD operation, while UE 820 and NCR node 830 are limited to TDD half-duplex operation. For example, when NCR node 830 is limited to TDD half-duplex operation, NCR node 830 may forward signals only in the downlink direction or only in the uplink direction within each symbol, slot, or other transmission time interval to help extend the coverage of network node 710. In some aspects, as described herein, NCR node 830 may receive information related to the SBFD configuration of network node 710, enabling NCR node 830 to improve forwarding services used to extend the coverage of network node 710. Additionally or alternatively, some aspects described herein relate to wireless network deployments where one or more components of network node 810 and NCR node 830 support SBFD operation (e.g., the MT component of NCR node 830 may have SBFD capability for one or more component carriers for communication with network node 810 via a control link, and / or the FWD component of NCR node 830 may have bidirectional forwarding capability to enable concurrent forwarding in the uplink and downlink directions within SBFD symbols, time slots, or other time resources). In such cases, UE 820 may support full-duplex (e.g., SBFD) operation, or may only support TDD half-duplex operation. In either case, UE 820 is aware of the SBFD configuration of network node 810 (and also NCR node 830 if the NCR has SBFD capability), and can adjust scheduling, measurement, and / or other operations within SBFD time resources according to the SBFD configuration of network node 810. In addition, in some cases, various options can be configured to support downlink communication within uplink subbands and / or support uplink communication within downlink subbands associated with one or more time resources allocated to SBFD communication.

[0117] For example, such as Figure 8AAs shown by reference numeral 850 in the accompanying drawings, network node 810 can transmit SBFD configuration information associated with network node 810, and NCR node 830 can receive this SBFD configuration information. For example, in some aspects, the SBFD configuration information associated with network node 810 can be provided semi-statically (e.g., via RRC signaling or another suitable semi-static indication) (e.g., to the MT component of NCR node 830). Furthermore, in some aspects, the SBFD configuration can indicate the time resources in which network node 810 communicates in SBFD mode (e.g., one or more SBFD slots, SBFD symbols, and / or other SBFD time resources in which network node 810 supports simultaneous uplink and downlink communication within a TDD carrier). Additionally or alternatively, the SBFD configuration information may include other suitable information related to the SBFD time resources, such as periodicity or duty cycle. Furthermore, in some aspects, the SBFD configuration information may also indicate the SBFD subband configuration (e.g., frequency domain configuration) of network node 810 within the time resources in which it communicates in SBFD mode. For example, SBFD subband configuration can indicate frequency resources associated with one or more downlink subbands, frequency resources associated with one or more uplink subbands, and frequency resources associated with one or more protection bands that separate the downlink and uplink subbands. For example, frequency resources can indicate one or more resource blocks (RBs) and / or resource elements (REs) allocated to one or more downlink subbands, one or more uplink subbands, and / or one or more protection bands.

[0118] In some aspects, such as Figure 8AAs further shown by reference numeral 850, network node 810 can transmit and NCR node 830 can receive information indicating or configuring the forwarding direction of NCR node 830 in one or more SBFD time resources. Additionally or alternatively, network node 810 can transmit and NCR node 830 can receive information indicating or configuring NCR node 830 to forward one or more subbands of communication in one or more SBFD time resources (e.g., NCR node 830 forwarding an uplink subband of communication in the uplink direction in one or more SBFD time resources, or NCR node 830 forwarding a downlink subband of communication in the downlink direction in one or more SBFD time resources, etc.). For example, when NCR node 830 is configured in TDD mode such that NCR node 830 forwards only in the downlink direction or only in the uplink direction in each symbol, slot, or other time resource, network node 810 can (e.g., to the MT component) transmit control information to configure NCR node 830 to forward communication in the downlink direction or uplink direction in one or more SBFD time resources. Additionally or alternatively, if the NCR node 830 has broadband bidirectional forwarding capabilities, enabling it to forward simultaneously in both downlink and uplink directions, the network node 810 may (e.g., to the MT component) transmit control information to configure the NCR node 830 to forward communication in the downlink, uplink, or both downlink and uplink directions in one or more SBFD time resources. In either case, the indication or configuration of the forwarding direction may be common to all SBFD time resources (e.g., the NCR node 830 forwards only in the downlink direction, only in the uplink direction, or both in the downlink and uplink directions in each SBFD time resource), or the indication or configuration of the forwarding direction may be provided for different sets of SBFD symbols. For example, when indicating or configuring forwarding directions for different SBFD symbol sets, the NCR node 830 can be configured to forward only for the SBFD symbol set in the downlink direction, only for the SBFD symbol set in the uplink direction, for the SBFD symbol set in both the downlink and uplink directions, and / or any suitable combination thereof.

[0119] In some aspects, network node 810 may use dynamic signaling (e.g., using one or more DCI messages or other dynamic signaling) and / or semi-static signaling (e.g., using one or more RRC messages or other semi-static signaling) to explicitly indicate the forwarding direction and / or subband of communication that NCR node 830 will forward in SBFD time resources. Additionally or alternatively, the forwarding direction and / or subband of communication that NCR node 830 will forward in SBFD time resources may be implicitly indicated according to one or more rules, configurations, conditions, or other suitable parameters. For example, in some aspects, the direction in which NCR node 830 will forward communication in SBFD time resources may be implicitly indicated according to a legacy TDD configuration or TDD mode associated with the TDD carrier implementing SBFD communication. For example, as described elsewhere herein, SBFD communication may be implemented in a TDD carrier associated with a legacy TDD mode that indicates one or more downlink time resources, one or more uplink time resources, and one or more flexible resources that repeat periodically in the time domain according to the configuration. Furthermore, when SBFD communication is implemented on a TDD carrier, the SBFD mode can be configured to indicate one or more time resources, where the frequency resources of the TDD mode are divided into downlink subbands and uplink subbands to support full-duplex operation. Therefore, in such cases, the NCR node 830 can implicitly determine the forwarding direction within the SBFD time resources based on the downlink or uplink configuration of the underlying SBFD time resources within the legacy TDD mode. For example, the NCR node 830 can forward communication in the downlink direction within any SBFD time resource corresponding to the legacy downlink time resource, and can forward communication in the uplink direction within any SBFD time resource corresponding to the legacy uplink time resource. Alternatively, the NCR node 830 can use other suitable rules within the SBFD time resources corresponding to the legacy flexible time resources (e.g., any one or more rules described further in detail below).

[0120] Additionally or alternatively, the direction in which NCR node 830 forwards communication in SBFD time resources may be implicitly indicated by a semi-static TDD state or dynamic TDD state associated with one or more non-SBFD time resources adjacent to the SBFD time resources. For example, when NCR node 830 is scheduled to forward communication on a contiguous set of symbols including one or more non-SBFD time resources before or after the one or more non-SBFD time resources, NCR node 830 may forward communication in the one or more SBFD time resources in the same direction as the one or more non-SBFD time resources before or after the one or more SBFD time resources (e.g., uplink only, downlink only, or both downlink and uplink). Additionally or alternatively, the forwarding direction used by NCR node 830 in SBFD time resources may depend on the operating state or scheduling of the MT component associated with NCR node 830. For example, if the MT component associated with NCR node 830 is active in the downlink or uplink direction in one or more time resources that fully or partially overlap with SBFD time resources, the FWD component associated with NCR node 830 may use the same forwarding direction as the MT component in the overlapping time resources. Additionally or alternatively, the forwarding direction of NCR node 830 may be based on the specific implementation of NCR node 830 (e.g., based on energy detection within the downlink subband and / or uplink subband within the SBFD time resources, wherein NCR node 830 forwards signals based on the energy level or input power of an indicator SBFD symbol measured in the downlink or uplink subband).

[0121] Therefore, as Figure 8AAs further illustrated by reference numeral 855, the NCR node 830 may forward one or more communications received in the SBFD time resource in the forwarding direction explicitly or implicitly indicated as described above. For example, when the NCR node 830 is configured to forward only in the downlink direction within the SBFD time resource, the NCR node 830 may forward any downlink communications received from the network node 810 within the SBFD time resource to the UE 820 (and may filter or otherwise discard any uplink communications received from the UE 820 within the SBFD time resource, wherein the NCR node 830 forwards only in the downlink direction). Alternatively, when the NCR node 830 is configured to forward only in the uplink direction within the SBFD time resource, the NCR node 830 may forward any uplink communications received from the UE 820 within the SBFD time resource to the network node 810 (and may filter or otherwise discard any downlink communications received from the network node 810 within the SBFD time resource, wherein the NCR node 830 forwards only in the uplink direction). Alternatively, if the NCR node 830 has bidirectional forwarding capability and is configured to forward in both the downlink and uplink directions within the SBFD time resources, the NCR node 830 may forward any uplink communication received from the UE 820 within the SBFD time resources to the network node 810, and may also forward any downlink communication received from the network node 810 within the SBFD time resources to the UE 820.

[0122] In some aspects, such as Figure 8B As shown, the forwarding operations associated with NCR node 830 can be configured within the SBFD time resources based on the subband filtering capability associated with NCR node 830. For example, in some cases, NCR node 830 can perform wideband forwarding of analog signals located within the operating bandwidth, which covers one or more component carriers associated with the MT component of NCR node 830. Alternatively, in some cases, NCR node 830 can support subband filtering of one or more downlink subbands and / or one or more uplink subbands, in which case NCR node 830 selectively forwards only signals within certain subbands and / or filters (does not forward) signals within certain subbands. In this way, the subband filtering capability can improve the performance at network node 810 within the SBFD time resources, since wideband forwarding across the entire operating bandwidth can lead to interference with uplink reception at network node 810.

[0123] Therefore, as Figure 8BAs shown by reference numeral 860 in the accompanying drawings, NCR node 830 may send information to network node 810 indicating the subband filtering capabilities of NCR node 830 (e.g., whether NCR node 830 supports filtering of one or more downlink subbands and / or one or more uplink subbands). Additionally or alternatively, an Operations, Regulation, and Administration (OAM) entity (e.g., a core network entity) may indicate the subband filtering capabilities of NCR node 830 to network node 810. For example, due to a “mezzanine” configuration of downlink and uplink subbands (e.g., where the uplink subband occupies frequency resources between a first downlink subband and a second downlink subband), the subband filtering capabilities of NCR node 830 may be indicated to network node 810. For example, a downlink subband filter based on a downlink / uplink / downlink subband configuration in SBFD time resources may require a U-shaped filter design, which could lead to a more challenging implementation compared to a narrowband uplink filter. Therefore, as described herein, NCR node 830 is typically configured to forward communication only in the downlink direction or only in the uplink direction when NCR node 830 only supports TDD half-duplex operation. However, when NCR node 830 supports downlink subband filtering and / or uplink subband filtering, NCR node 830 may be configured to forward only communication within the relevant downlink and / or uplink subbands (e.g., outside the filtering capabilities of NCR node 830), and filter any communication within unrelated downlink and / or uplink subbands (e.g., within the filtering capabilities of NCR node 830) without forwarding. Alternatively, when NCR node 830 has bidirectional forwarding capabilities and supports downlink and / or uplink subband filtering, network node 810 may instruct or otherwise configure NCR node 830 to simultaneously forward certain downlink and / or uplink subbands and associated downlink and / or uplink states within SBFD time resources.

[0124] Therefore, as Figure 8BAs further illustrated by reference numeral 865, the NCR node 830 can forward one or more communications received in the SBFD time resource in the forwarding direction explicitly or implicitly indicated as described above, based on the subband filtering capability of the NCR node 830. For example, if the NCR node 830 is configured to forward only in the downlink direction within the SBFD time resource, and downlink communication is received in a downlink subband outside the downlink subband filtering capability of the NCR node 830, the NCR node 830 may forward any downlink communication received from the network node 810 within the SBFD time resource to the UE 820. Furthermore, the NCR node 830 may filter or otherwise discard any uplink communication received from the UE 820 within the SBFD time resource where the NCR node 830 forwards only in the downlink direction, and may filter any downlink communication received from the network node 810 within the downlink subband where the NCR node 830 has filtering capability, without forwarding. Alternatively, if NCR node 830 is configured to forward only in the uplink direction within SBFD time resources, and if uplink communication is received in an uplink subband outside the uplink subband filtering capability of NCR node 830, NCR node 830 may forward any uplink communication received from UE 820 within SBFD time resources to network node 810. Furthermore, NCR node 830 may filter or otherwise discard any downlink communication received from network node 810 within SBFD time resources where NCR node 830 forwards only in the uplink direction, and may filter any uplink communication received from UE 820 within an uplink subband where NCR node 830 has filtering capability without forwarding. Alternatively, if the NCR node 830 has bidirectional forwarding capability and subband filtering capability, the NCR node 830 can forward any uplink communication received from the UE 820 and any downlink communication received from the network node 810 in a subband that is not within the filtering capability of the NCR node 830, and can filter any uplink communication received from the UE 820 and any downlink communication received from the network node 810 in a subband that is within the filtering capability of the NCR node 830 without forwarding.

[0125] In some respects, as described herein, network node 810 may support dynamic SBFD, where SBFD time resources can be dynamically configured as SBFD resources, downlink-only resources, or uplink-only resources (e.g., depending on whether current service requirements are downlink-heavy, uplink-heavy, associated with downlink latency requirements, associated with uplink latency requirements, etc.). Therefore, to support dynamic SBFD operation, where resources supporting SBFD operation can be configured in downlink-only mode, uplink-only mode, or SBFD mode, network node 810 may dynamically indicate the downlink forwarding status and / or uplink forwarding status associated with the resources supporting SBFD operation.

[0126] For example, such as Figure 8C As shown by reference numeral 870 in the accompanying drawings, network node 810 may provide NCR node 830 with an SBFD-specific forwarding configuration to be used in one or more SBFD time resources, wherein the SBFD-specific forwarding configuration may indicate to NCR node 830 whether to perform wideband downlink forwarding over the entire bandwidth of a TDD carrier supporting SBFD operation or to perform wideband uplink forwarding over the entire bandwidth of a TDD carrier supporting SBFD operation. Additionally or alternatively, the SBFD-specific forwarding configuration may indicate to NCR node 830 whether to perform downlink forwarding in one or more subbands and / or uplink forwarding in one or more subbands. In such cases, network node 810 may optionally further indicate to NCR node 830 one or more subbands in which downlink forwarding and / or uplink forwarding will be performed.

[0127] Additionally or alternatively, as described herein, the SBFD-specific forwarding configuration provided to NCR node 830 may be associated with configuration information provided by network node 810 to the MT component of NCR node 830. For example, as described herein, the MT component of NCR node 830 includes one or more serving cells or component carriers for supporting communication with network node 810 via a control link, and the control information provided to the MT component may instruct the network node 810 on the SBFD configuration for the one or more serving cells or component carriers associated with the MT component. Therefore, in some aspects, the SBFD configuration information used by the FWD component of NCR node 830 may correspond to the SBFD configuration information previously obtained by the MT component of NCR node 830 from network node 810 for the one or more serving cells or component carriers associated with the MT component. However, in some cases, the one or more serving cells or component carriers associated with the MT component may be a subset of the component carriers that the FWD component of NCR node 830 is configured to forward. Alternatively, when the NCR node 830 is configured as an out-of-band repeater, the component carriers for forwarding by the FWD component of the NCR node 830 may differ from the one or more component carriers used to support communication between the MT component and the network node 810. Therefore, in some aspects, the MT component of the NCR node 830 may be provided with the SBFD configuration of the network node 810 for one or more component carriers that are non-serving cells of the MT component and within the operating bandwidth of the FWD component. Additionally or alternatively, the network node 810 may provide the MT component with a unified set of uplink and downlink subbands, representing the union of all component carriers supported by the MT component and the FWD component. In such cases, each subband may be referenced within the set using an index, which may be provided to the MT component in side control information and / or instructions for forwarding operations of the FWD component.

[0128] Additionally or alternatively, as described herein, the SBFD-specific forwarding configuration provided to NCR node 830 may include one or more configurations that NCR node 830 will employ in SBFD time resources, and network node 810 may use semi-static (e.g., RRC) signaling or other suitable signaling to indicate such one or more configurations to NCR node 830. Additionally or alternatively, network node 810 may provide NCR node 830 with a first set of configurations to be used in SBFD time resources and a second set of configurations to be used in non-SBFD time resources (e.g., using semi-static signaling), and dynamic or semi-persistent indications (e.g., DCI messages, MAC-CE, or RRC configurations) may be provided to NCR node 830 to indicate a first configuration within the first set of configurations to be used in SBFD time resources and / or a second configuration within the second set of configurations to be used in non-SBFD time resources. For example, as described herein, configurations to be used in SBFD and / or non-SBFD time resources may include an access link beam for receiving or transmitting communication from or to the UE 820, a backhaul beam for receiving or transmitting communication from or to the network node 810, power configuration, amplification configuration, and / or transmit / receive or forward timing alignment configuration, etc. Furthermore, in some aspects, configurations to be used in SBFD and / or non-SBFD time resources may be associated with a single value, set of values, and / or range of values ​​for any one or more of the access link beam, backhaul beam, power configuration, amplification configuration, transmit / receive or forward timing alignment configuration, and / or other suitable communication parameters.

[0129] Therefore, as Figure 8CAs further illustrated by reference numeral 875, the NCR node 830 may forward one or more communications received in the SBFD time resource using an applicable forwarding configuration in the forwarding direction explicitly or implicitly indicated by the subband filtering capability of the NCR node 830, in the manner described above. For example, in some aspects, the NCR node 830 may perform wideband downlink forwarding, wideband uplink forwarding, subband downlink forwarding, and / or subband uplink forwarding within the SBFD time resource based on a dynamic SBFD mode configured or indicated by the network node 810. Additionally or alternatively, the NCR node 830 may determine the SBFD configuration associated with the SBFD time resource based on: the SBFD configuration provided for one or more serving cells or component carriers of the MT component; the SBFD configuration provided for one or more component carriers within the operating bandwidth of the FWD component to the MT component; and / or the index of a subband in a set of references to uplink and downlink subbands, which represents the union of all component carriers associated with the MT and FWD components. Additionally or alternatively, as described herein, the NCR node 830 may use a semi-static configuration associated with the SBFD time resource and / or dynamic indications of the configurations within the set of configurations associated with the SBFD time resource to determine the access beam, return beam, power configuration, amplification configuration, transmit / receive or forward timing alignment configuration and / or other suitable communication parameters to be used in one or more SBFD time resources.

[0130] As indicated above, Figures 8A to 8C Provided as an example. Other examples may be found with reference to [the relevant source]. Figures 8A to 8C The examples described are different.

[0131] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a repeater node or a device of a repeater node, according to the present disclosure. Example process 900 is an example in which a device or repeater node (e.g., repeater network node 110d, NCR node 730, NCR node 830, etc.) performs operations associated with SBFD sensing.

[0132] like Figure 9 As shown, in some aspects, process 900 may include: receiving SBFD configuration information associated with a network node from a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols (box 910). For example, the repeater node (e.g., using...) Figure 10The receiving component 1002 and / or communication manager 1006 depicted herein can receive SBFD configuration information associated with the network node from the network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in one or more SBFD symbols, as described above.

[0133] like Figure 9 Further shown, in some aspects, process 900 may include: forwarding communications received in one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information (box 920). For example, a repeater node (e.g., using...) Figure 10 The transmitting component 1004 and / or the communication manager 1006 depicted herein may forward communications received in one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information, as described above.

[0134] Process 900 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.

[0135] In the first aspect, SBFD configuration information indicates one or more time resources associated with one or more SBFD symbols.

[0136] In a second aspect, either alone or in combination with the first aspect, the SBFD configuration information indicates one or more uplink subbands, one or more downlink subbands, and one or more guard bands associated with the one or more SBFD symbols.

[0137] In the third aspect, either alone or in combination with one or more of the first and second aspects, the forwarding direction is shared for all SBFD symbols, or is indicated separately for different sets of SBFD symbols.

[0138] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the forwarding direction is implicitly indicated according to the TDD configuration associated with the one or more SBFD symbols.

[0139] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the forwarding direction is implicitly indicated according to a TDD configuration associated with one or more non-SBFD symbols adjacent to the one or more SBFD symbols.

[0140] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the forwarding direction is implicitly indicated during the one or more SBFD symbols according to a schedule or one or more operating parameters associated with the MT component of the repeater node.

[0141] In the seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 900 includes: sending to the network node information indicating a subband filtering capability associated with the repeater node, and the subband filtering capability being associated with one or more downlink subbands or one or more uplink subbands.

[0142] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the communication is forwarded based at least in part on receiving the communication in one or more subbands not included in the subband filtering capability associated with the repeater node.

[0143] In the ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 includes: receiving, in the one or more SBFD symbols, one or more communications in one or more subbands included in the subband filtering capability associated with the repeater node; and filtering the one or more communications received in the one or more subbands included in the subband filtering capability associated with the repeater node without forwarding.

[0144] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the SBFD configuration information indicates one or more of the broadband forwarding status or subband forwarding status in one or more of the uplink or downlink directions.

[0145] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the SBFD configuration information is indicated for one or more serving cells associated with the MT component of the repeater node.

[0146] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, the SBFD configuration information is indicated for one or more component carriers that are non-service component carriers for the MT component of the repeater node and within the operating bandwidth of the FWD component of the repeater node.

[0147] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the SBFD configuration information is indicated for a plurality of uplink subbands and a plurality of downlink subbands, which represent the union of all component carriers associated with the MT component and FWD component of the repeater node, and the SBFD configuration information includes one or more indexes to identify subsets of the plurality of uplink subbands and the plurality of downlink subbands, in which the repeater node will forward the one or more communications received in the one or more SBFD symbols.

[0148] In the fourteenth aspect, alone or in combination with one or more of the first to eighth aspects, process 900 includes: receiving control information from the network node, the control information indicating one or more forwarding configurations to be used in the one or more SBFD symbols.

[0149] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, process 900 includes: receiving control information from the network node indicating a first set of forwarding configurations to be used in the one or more SBFD symbols and a second set of forwarding configurations to be used in the one or more non-SBFD symbols; and receiving from the network node an indication of the first forwarding configuration to be used in the one or more SBFD symbols within the first set of activated forwarding configurations and a second forwarding configuration to be used in the one or more non-SBFD symbols within the second set of forwarding configurations.

[0150] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, at least in part, the relay node is based on having bidirectional forwarding capability, the forwarding direction including uplink and downlink directions.

[0151] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, at least in part based on the fact that the repeater node has bidirectional forwarding capability and subband filtering capability, the SBFD configuration information indicates that the forwarding direction includes one or more subbands in the uplink direction and the downlink direction.

[0152] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

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

[0154] In some respects, device 1000 can be configured to perform the above and Figures 8A to 8C One or more operations described herein. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 9 The process is 900. In some respects, Figure 10 The illustrated device 1000 and / or one or more components may include a combination Figure 2 The network node 110 and / or one or more components of the UE 120 described. For example, in some aspects, Figure 10 The device 1000 and / or one or more components shown may include one or more components of a network-controlled repeater node, which may include MT components and FWD components, the MT component including a combination of Figure 2 The described UE 120 includes one or more components, the FWD component comprising... Figure 2 One or more components of the described network node 110. Additionally or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components 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 executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0155] Receiver 1002 may receive communications from device 1008, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 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 1000. In some aspects, receiver 1002 may include combinations of... Figure 2 The described repeater node 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.

[0156] Transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1008. In some aspects, one or more other components of device 1000 may generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1008. In some aspects, transmitting component 1004 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 1008. In some aspects, transmitting component 1004 may include combinations of... Figure 2 The described repeater node 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 1004 may co-located with the receive component 1002 in one or more transceivers.

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

[0158] The receiving component 1002 can receive SBFD configuration information associated with the network node from the network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols. The transmitting component 1004 can forward the communication received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0159] The transmitting component 1004 can send information to the network node indicating the subband filtering capability associated with the repeater node, wherein the subband filtering capability is associated with one or more downlink subbands or one or more uplink subbands.

[0160] The receiving component 1002 can receive one or more communications in one or more subbands included in the subband filtering capability associated with the repeater node in one or more SBFD symbols. The communication manager 1006 can filter one or more communications received in one or more subbands included in the subband filtering capability associated with the repeater node without forwarding.

[0161] The receiving component 1002 can receive control information from a network node indicating one or more forwarding configurations to be used in one or more SBFD symbols.

[0162] The receiving component 1002 can receive control information from the network node indicating a first set of forwarding configurations to be used in one or more SBFD symbols and a second set of forwarding configurations to be used in one or more non-SBFD symbols. The receiving component 1002 can also receive from the network node indications for activating the first forwarding configuration in the first set of forwarding configurations to be used in one or more SBFD symbols and the second forwarding configuration in the second set of forwarding configurations to be used in one or more non-SBFD symbols.

[0163] Figure 10 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 10 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The collection of (one or more) components shown is executable and described as being composed of Figure 10 Another set of components shown performs one or more functions.

[0164] The following provides an overview of some aspects of this disclosure: Aspect 1: A wireless communication method performed by a repeater node, the method comprising: receiving SBFD configuration information associated with the network node from a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates a forwarding direction for the repeater node in the one or more SBFD symbols; and forwarding communication received in the one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

[0165] Aspect 2: According to the method of aspect 1, wherein the SBFD configuration information indicates one or more time resources associated with the one or more SBFD symbols.

[0166] Aspect 3: According to the method of aspect 2, wherein the SBFD configuration information indicates one or more uplink subbands, one or more downlink subbands and one or more guard bands associated with the one or more SBFD symbols.

[0167] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the forwarding direction is shared for all SBFD symbols or is indicated separately for different sets of SBFD symbols.

[0168] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the forwarding direction is implicitly indicated according to the TDD configuration associated with the one or more SBFD symbols.

[0169] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the forwarding direction is implicitly indicated according to a TDD configuration associated with one or more non-SBFD symbols adjacent to the one or more SBFD symbols.

[0170] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the forwarding direction is implicitly indicated during the one or more SBFD symbols according to a schedule or one or more operating parameters associated with the MT component of the repeater node.

[0171] Aspect 8: The method according to any one of Aspects 1 to 7, the method further comprising: sending to the network node information indicating subband filtering capability associated with the repeater node, wherein the subband filtering capability is associated with one or more downlink subbands or one or more uplink subbands.

[0172] Aspect 9: The method according to aspect 8, wherein the communication is forwarded at least in part based on receiving the communication in one or more subbands not included in the subband filtering capability associated with the repeater node.

[0173] Aspect 10: The method according to aspect 8, the method further comprising: receiving, in the one or more SBFD symbols, one or more communications in one or more subbands included in the subband filtering capability associated with the repeater node; and filtering the one or more communications received in the one or more subbands included in the subband filtering capability associated with the repeater node without forwarding.

[0174] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the SBFD configuration information indicates one or more of a broadband forwarding state or a subband forwarding state in one or more of the uplink direction or the downlink direction.

[0175] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the SBFD configuration information is indicated for one or more serving cells associated with the MT component of the repeater node.

[0176] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the SBFD configuration information is indicated for one or more component carriers, the one or more component carriers being non-service component carriers for the MT component of the repeater node and within the operating bandwidth of the FWD component of the repeater node.

[0177] Aspect 14: The method according to any one of Aspects 1 to 13, wherein the SBFD configuration information is indicated for a plurality of uplink subbands and a plurality of downlink subbands, the plurality of uplink subbands and the plurality of downlink subbands representing the union of all component carriers associated with the MT component and FWD component of the repeater node, and wherein the SBFD configuration information includes one or more indexes to identify subsets of the plurality of uplink subbands and the plurality of downlink subbands, the repeater node forwarding the one or more communications received in the one or more SBFD symbols in the subsets.

[0178] Aspect 15: The method according to any one of Aspects 1 to 14, the method further comprising: receiving control information from the network node, the control information indicating one or more forwarding configurations to be used in the one or more SBFD symbols.

[0179] Aspect 16: The method according to any one of Aspects 1 to 15, the method further comprising: receiving control information from the network node, the control information indicating a first set of forwarding configurations to be used in the one or more SBFD symbols and a second set of forwarding configurations to be used in the one or more non-SBFD symbols; and receiving from the network node an indication of a first forwarding configuration to be used in the one or more SBFD symbols within the first set of activated forwarding configurations and a second forwarding configuration to be used in the one or more non-SBFD symbols within the second set of forwarding configurations.

[0180] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the relay node has bidirectional forwarding capability at least in part, the forwarding direction including uplink direction and downlink direction.

[0181] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the SBFD configuration information indicates that the forwarding direction includes one or more subbands in the uplink direction and the downlink direction, based at least in part on the fact that the repeater node has bidirectional forwarding capability and subband filtering capability.

[0182] Aspect 19: 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 18.

[0183] Aspect 20: 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 18.

[0184] Aspect 21: 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 18.

[0185] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 18.

[0186] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, 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 18.

[0187] Aspect 24: 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 18.

[0188] 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 individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 18.

[0189] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0190] 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.

[0191] 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.

[0192] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: 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 of the same element (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).

[0193] 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 “the” is intended to include one or more items mentioned in connection with the article “the” 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”.

[0194] 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. A repeater node for wireless communication, the repeater node comprising: One or more memory units; and One or more processors, coupled to one or more memories, are configured to cause the repeater node to: Receive subband full-duplex (SBFD) configuration information associated with the network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols; as well as The communication received in the one or more SBFD symbols is forwarded in the forwarding direction indicated in the SBFD configuration information.

2. The repeater node of claim 1, wherein the SBFD configuration information indicates one or more time resources associated with the one or more SBFD symbols.

3. The repeater node of claim 2, wherein the SBFD configuration information indicates one or more uplink subbands, one or more downlink subbands, and one or more guard bands associated with the one or more SBFD symbols.

4. The repeater node according to claim 1, wherein the forwarding direction is shared for all SBFD symbols, or is individually indicated for different sets of SBFD symbols.

5. The repeater node of claim 1, wherein the forwarding direction is implicitly indicated according to the time-division duplex configuration associated with the one or more SBFD symbols.

6. The repeater node of claim 1, wherein the forwarding direction is implicitly indicated according to a time-division duplex configuration associated with one or more non-SBFD symbols adjacent to the one or more SBFD symbols.

7. The repeater node of claim 1, wherein the forwarding direction is implicitly indicated during the one or more SBFD symbols according to a schedule or one or more operating parameters associated with the mobile terminal component of the repeater node.

8. The repeater node of claim 1, wherein the one or more processors are further configured to cause the repeater node to: Send information to the network node indicating the subband filtering capability associated with the repeater node, wherein the subband filtering capability is associated with one or more downlink subbands or one or more uplink subbands.

9. The repeater node of claim 8, wherein the communication is forwarded at least in part based on receiving the communication in one or more subbands not included in the subband filtering capability associated with the repeater node.

10. The repeater node of claim 8, wherein the one or more processors are further configured to cause the repeater node to: In the one or more SBFD symbols, receive one or more communications in one or more subbands included in the subband filtering capability associated with the repeater node; and Without forwarding, the one or more communications received in one or more subbands included in the subband filtering capability associated with the repeater node are filtered.

11. The repeater node according to claim 1, wherein the SBFD configuration information indicates one or more of a broadband forwarding state or a subband forwarding state in one or more of the uplink or downlink directions.

12. The repeater node of claim 1, wherein the SBFD configuration information is indicated for one or more serving cells associated with a mobile terminal component of the repeater node.

13. The repeater node of claim 1, wherein the SBFD configuration information is indicated for one or more component carriers, the one or more component carriers being non-serving component carriers for a mobile terminal component of the repeater node and within the operating bandwidth of a forwarding component of the repeater node.

14. The repeater node of claim 1, wherein the SBFD configuration information is indicated for a plurality of uplink subbands and a plurality of downlink subbands, the plurality of uplink subbands and the plurality of downlink subbands representing the union of all component carriers associated with the mobile terminal component and the forwarding component of the repeater node, and wherein the SBFD configuration information includes one or more indexes to identify subsets of the plurality of uplink subbands and the plurality of downlink subbands, the repeater node forwarding the one or more communications received in the one or more SBFD symbols in the subsets.

15. The repeater node of claim 1, wherein the one or more processors are further configured to cause the repeater node to: The network node receives control information indicating one or more forwarding configurations to be used in the one or more SBFD symbols.

16. The repeater node of claim 1, wherein the one or more processors are further configured to cause the repeater node to: Receive control information from the network node, the control information indicating a first set of forwarding configurations to be used in the one or more SBFD symbols and a second set of forwarding configurations to be used in one or more non-SBFD symbols; and The network node receives an indication of a first forwarding configuration to be used on the one or more SBFD symbols from the first set of activated forwarding configurations, and a second forwarding configuration to be used on one or more non-SBFD symbols from the second set of forwarding configurations.

17. The repeater node of claim 1, wherein the repeater node has bidirectional forwarding capability at least in part, the forwarding direction including uplink direction and downlink direction.

18. The repeater node of claim 1, wherein, based at least in part on the repeater node having bidirectional forwarding capability and subband filtering capability, the SBFD configuration information indicates that the forwarding direction includes one or more subbands in the uplink direction and the downlink direction.

19. A method for wireless communication performed by a repeater node, the method comprising: Receive subband full-duplex (SBFD) configuration information associated with the network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the repeater node in the one or more SBFD symbols; as well as The communication received in the one or more SBFD symbols is forwarded in the forwarding direction indicated in the SBFD configuration information.

20. An apparatus for wireless communication, the apparatus comprising: A component for receiving subband full-duplex (SBFD) configuration information associated with a network node, wherein the SBFD configuration information indicates one or more SBFD symbols and indicates the forwarding direction for the device in the one or more SBFD symbols; and A component for forwarding communications received in one or more SBFD symbols in the forwarding direction indicated in the SBFD configuration information.

Images