Sub-band full duplex resource configuration

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network node can output a first configuration for a set of resources, the first configuration being associated with a time division duplex mode, and the first configuration configuring the set of resources in one of an uplink format, a downlink format, or a flexible format. The network node can output a second configuration to configure one or more resources in the set of resources in a sub-band full duplex (SBFD) format based at least in part on the one or more resources satisfying a condition. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 811,493, entitled “SUB-BAND FULL DUPLEX RESOURCE CONFIGURATION,” filed on July 8, 2022, which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for sub-band full-duplex (SBFD) resource configuration. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, as well as supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include: outputting a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The method may include: outputting a second configuration configuring the one or more resources in the resource set as a sub-band full duplex (SBFD) format based at least in part on one or more resources in the resource set satisfying a condition.

[0008] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include: receiving a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The method may include: receiving a second configuration configuring the one or more resources in the resource set as an SBFD format based at least in part on one or more resources satisfying a condition, the condition being associated with configuring the one or more resources as an SBFD format. The method may include: communicating on the one or more resources.

[0009] Some aspects described herein relate to a network node for wireless communication. The network node may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to: output a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The one or more processors may be configured to: output a second configuration configuring the one or more resources in the resource set as a SBFD format based at least in part on one or more resources in the resource set satisfying a condition.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include: a memory; and one or more processors coupled to the memory. The one or more processors may be configured to: receive a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The one or more processors may be configured to: receive a second configuration configuring the one or more resources as an SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources as an SBFD format. The one or more processors may be configured to: communicate on the one or more resources.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to output a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The instruction set, when executed by one or more processors of the network node, may cause the network node to output a second configuration configuring the one or more resources in the resource set to a SBFD format based at least in part on one or more resources satisfying a condition.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a second configuration configuring the one or more resources as an SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources as an SBFD format. The instruction set, when executed by one or more processors of the UE, may cause the UE to communicate on the one or more resources.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a component for outputting a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The apparatus may include: a component for outputting a second configuration configuring the one or more resources in the resource set as a SBFD format based at least in part on one or more resources in the resource set satisfying a condition.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a component for receiving a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The apparatus may include: a component for receiving a second configuration configuring the one or more resources in the resource set as an SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources as an SBFD format. The apparatus may include: a component for communicating on the one or more resources.

[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements, and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

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

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

[0021] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0022] FIG. 4A to FIG. 4D is a diagram illustrating an example of full-duplex communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of a time slot format for scheduling UE communications according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of sub-band full-duplex (SBFD) resources and communications according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of signaling associated with reconfiguring resources according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example process, for example, performed by a network node, according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0028] Fig.10 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0029] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or post-5G (e.g., 6G) RAT.

[0033] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0034] In some examples, the network node 110 is or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0035] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0036] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.

[0037] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0038] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0039] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0040] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be fixed or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or subscriber units. UE 120 can be a cellular phone (e.g., a smart phone), 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 smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless or wired medium.

[0041] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer site equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0042] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using network node 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by network node 110.

[0044] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. according to frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the "below 6GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30GHz–300GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating 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.

[0047] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may output a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format; and output a second configuration configuring the one or more resources in the resource set as an SBFD format based at least in part on one or more resources satisfying a condition. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a first configuration for a resource set, the first configuration associated with a time division duplex mode, and the first configuration configures the resource set as one of an uplink format, a downlink format, or a flexible format; receive a second configuration configuring the one or more resources in the resource set as an SBFD format based at least in part on one or more resources satisfying a condition, the condition associated with configuring the one or more resources as an SBFD format; and communicate on the one or more resources. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0049] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0050] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0051] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., code and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0052] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0053] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0054] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0055] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 3 to 11 ) or any aspects of any of the methods described herein.

[0056] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 3 to 11 ) or any aspects of any of the methods described herein.

[0057] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the network node 110 may perform one or more techniques associated with resource configuration, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 of and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0058] In some aspects, a network node (e.g., network node 110) includes: a component for outputting a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format; and / or a component for outputting a second configuration configuring the one or more resources in the resource set as a sub-band full duplex (SBFD) format based at least in part on one or more resources in the resource set satisfying a condition. In some aspects, the components for the network node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0059] In some aspects, a UE (e.g., UE 120) includes: a component for receiving a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format; a component for receiving a second configuration configuring the one or more resources in the resource set as a SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources as a SBFD format; and / or a component for communicating on the one or more resources. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0060] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0061] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0062] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or components. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0063] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0064] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0065] Figure 3 3 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0066] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0067] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0068] 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 RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0069] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform, such as an open cloud (O-Cloud) platform 390, to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface, such as an O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0071] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0072] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received at the SMO framework 305 or the non-RT RIC 315 from a non-network data source or from a network function. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0073] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0074] FIG. 4A to FIG. 4D 4 is a diagram illustrating examples 400, 410, 420, 430 of full-duplex (FD) communication according to the present disclosure. FD communication is a communication that uses overlapping time resources to send and receive at a single node (such as a UE or a base station). For example, a UE or a network node may use the same time resources to perform transmission and reception, such as via frequency division multiplexing (FDM) or space division multiplexing (SDM). "FDM" refers to performing two or more communications using different frequency resource allocations. "SDM" refers to performing two or more communications using different spatial parameters (such as different transmit configuration indicators (TCI) states that define different beams). SDM communications may use overlapping time resources and frequency resources, and FDM communications may use overlapping time resources and spatial resources (i.e., overlapping beam parameters, TCI states, etc.). The TCI state indicates the spatial parameters used for communication. For example, the TCI state used for communication may identify a source signal (such as a synchronization signal block, a channel state information reference signal, etc.) and a spatial parameter to be derived from the source signal for the purpose of sending or receiving communication. For example, the TCI state may indicate a quasi-co-location (QCL) type. The QCL type may indicate one or more spatial parameters to be derived from a source signal. The source signal may be referred to as a QCL source. FD communications may include dynamic services (such as those scheduled by downlink control information (DCI)) and / or semi-static services. Semi-static services are services associated with semi-persistent resources (such as resources configured by semi-persistent scheduling (SPS) or configured grants (CG)).

[0075] Figure 4AThe example 400 includes UE1 402 and two network nodes (e.g., TRPs) 404-1, 404-2, where UE1 402 is transmitting uplink transmissions to network node 404-1 and receiving downlink transmissions from network node 404-2. In some aspects, the network node 404 described in conjunction with FIG. 4 can be a base station, a TRP associated with (e.g., managed by) a network node, a RU, a DU, or a similar network node. In some aspects, the UE 402 described in conjunction with FIG. 4 can be a TRP associated with (e.g., managed by) a network node. Figure 1 , Figure 2 and Figure 3 UE 120 or similar UE described herein. Figure 4A In the example 400 of , FD is enabled for UE1 402 but not for network nodes 404-1, 404-2. Therefore, network nodes 404-1 and 404-2 are half-duplex (HD) network nodes.

[0076] Figure 4B Example 410 includes two UEs (UE1 402-1 and UE2 402-2), a network node 404-1, and a network node 404-2. UE1 402-1 is receiving a downlink transmission from the network node 404-1, and UE2 402-2 is sending an uplink transmission to the network node 404-1. Figure 4B In the example 410, FD is enabled for the network node 404-1 but not for UE1 402-1 and UE2 402-2. Therefore, UE1 402-1 and UE2 402-2 are half-duplex UEs.

[0077] Figure 4C Example 420 includes UE1 402 and network node 404, where UE1 402 is receiving downlink transmissions from network node 404 and UE1 402 is sending uplink transmissions to network node 404. Figure 4C In example 420, FD is enabled for both UE1 402 and network node 404. Figure 4C In example 420, UE1 402 and network node 404 communicate using a beam pair. The beam pair may include a downlink beam and an uplink beam. For example, UE1 402 may communicate with network node 404 using a beam pair including a downlink beam at UE1 402 (i.e., a receive beam) and an uplink beam at UE1 402 (i.e., a transmit beam). Network node 404 may use a downlink beam at network node 404 (i.e., a transmit beam) to transmit communications received via the downlink beam of UE1 402, and may use an uplink beam at network node 404 (i.e., a receive beam) to receive communications sent via the uplink beam of UE1 402.

[0078] Figure 4C Example 430 includes a network node 110 and a cell (such as a combination Figure 1 102) is associated with two network nodes 404-1 and 404-2. Network nodes 404-1 and 404-2 may be co-located (e.g., located at the same device, such as network node 110 or other device), or may be non-co-located (e.g., located separately from each other and / or network node 110, and thus may be independent devices).

[0079] exist FIG. 4A to FIG. 4D In FIG. 4 , interference is indicated by dashed lines. Interference may occur between network nodes of examples 400 , 410 , 420 , 430 (referred to as cross-link interference (CLI)). Figure 4A In , the downlink transmission of network node 404-2 interferes with the uplink transmission of network node 404-1. Figure 4B In the example, the uplink reception of network node 404-1 may be interfered by the transmission from network node 404-2. The CLI between network nodes 404 is referred to herein as inter-network node CLI. Figure 4B In some examples, the uplink transmission of UE2 402-2 may interfere with the downlink transmission of UE1 402-1 (not shown). Figure 4D In the example, the uplink transmission of UE2 402-2 interferes with the downlink transmission of UE1 402-1. In some cases, self-interference may occur. Self-interference occurs when the transmission of a node interferes with the receiving operation of the node. For example, self-interference may occur due to the reception of radiated energy from the transmitting antenna by the receiving antenna, crosstalk between components, etc. Figure 4C Examples of self-interference at UE 402 (from uplink transmission to downlink reception) and at network node 404 (from downlink transmission to uplink reception) are shown in FIG. It should be noted that the above-described CLI and self-interference conditions may occur in both HD and FD deployments.

[0080] As described below, some network nodes support sub-band full-duplex (SBFD) communications. SBFD communications may involve configuring certain resources to have an SBFD format. Some techniques described herein provide rules (e.g., conditions) for which resources may or may not be configured to have an SBFD format, whether resources having a particular format may be reconfigured to have another format, and / or whether communications for UEs that do not support SBFD communications may be configured in SBFD time slots, as described elsewhere herein.

[0081] As indicated above, FIG. 4A to FIG. 4Dis provided as one or more examples. Other examples may be related to FIG. 4A to FIG. 4D The examples described are different.

[0082] Figure 5 5 is a diagram illustrating an example 500 of a time slot format for scheduling UE communications according to the present disclosure. As described above, the transmission timeline can be organized into radio frames, subframes, time slots, and symbols. However, for ease of description, Figure 5 Only the time slot and symbol granularity are depicted in. Example 500 illustrates how a time division duplex (TDD) time slot (eg, a time slot on a TDD carrier) may be configured to be usable for uplink and / or downlink communications using a combination of semi-static signaling and dynamic signaling.

[0083] A timeline of time slots is shown by reference numeral 510, which includes a plurality of time slots 515a through 515s. Each time slot 515 and / or portions thereof (e.g., symbols) may be scheduled and / or configured for uplink ("UL") communications, downlink ("DL") communications, or as flexible ("F"). Flexible time slots (e.g., 515h through 515m) may be used for uplink communications or downlink communications. Resources configured and / or scheduled for uplink communications are described herein as having an uplink (U) format. Resources configured and / or scheduled for downlink communications are described herein as having a downlink (D) format. Resources configured and / or scheduled to include only flexible resources are described herein as having a flexible (F) format. All symbols within each time slot may be similarly assigned (e.g., all "UL," all "DL," or all "F"), otherwise the time slot may include multiple symbol assignment types. For example, in Figure 5 , time slots 515a to 515f (represented by “nrofDownlinkSlots”) are depicted as downlink time slots without showing symbol granularity because all symbols in each of those time slots are configured as downlink symbols. Similarly, time slots 515o to 515s (represented by “nrofUplinkSlots”) are depicted as uplink time slots without showing symbol granularity because all symbols in each of those time slots are configured as uplink symbols. In this regard, “nrofDownlinkSlots” refers to the number of consecutive full DL time slots (e.g., time slots that only include DL symbols) at the beginning of each time line of time slots 510 (e.g., time slots 515a to 515f), and “nrofUplinkSlots” refers to the number of consecutive full UL time slots (e.g., time slots that only include UL symbols) at the end of each time line of time slots 510 (e.g., time slots 515o to 515s).

[0084] Slots 515g and 515n include symbols of more than one format. More specifically, slot 515g includes six downlink symbols (represented by "nrofDownlinkSymbols"), of which the remaining eight symbols are flexible and can therefore be used for uplink or downlink, for a total of fourteen symbols. Slot 515n includes six uplink symbols (represented by "nrofUplinkSymbols"), of which the remaining eight symbols are flexible and can therefore be used for uplink or downlink, also for a total of fourteen symbols. In this regard, "nrofDownlinkSymbols" refers to the number of consecutive DL symbols at the beginning of slot 515g after the last full DL slot 515f, and "nrofUplinkSymbols" refers to the number of consecutive UL symbols at the end of slot 515n before the first full UL slot 515o. The remaining time slots in the timeline of time slots 510 (eg, time slots 515h through 515m) are flexible (eg, fully flexible, where all symbols in these time slots are configured as flexible symbols) and are therefore usable for uplink and downlink communications.

[0085] Resources (e.g., time slots and / or symbols) that are semi-statically configured as flexible may be later reconfigured for uplink or downlink communications. In some aspects, common configuration parameters (e.g., tdd-UL-DL-ConfigurationCommon or similar common configuration parameters) sent to all UEs in a cell define a semi-static time slot and / or symbol structure, including designating certain time slots or symbols for uplink communications, downlink communications, or as flexible for uplink or downlink communications. For example, the common configuration parameters may semi-statically configure time slots and symbols to have, for example, Figure 5 The initial configuration shown in . A dedicated configuration parameter (e.g., tdd-UL-DL-ConfigurationDedicated) that may be sent to a specific UE via a slot format indicator (SFI) may then be used to reconfigure the flexible slots and symbols as uplink or downlink slots and symbols. In some cases, for the remaining flexible slots or symbols (e.g., still configured as flexible slots or symbols after reconfiguration due to dedicated configuration parameters), the UE may monitor physical downlink control channel (PDCCH) information and determine whether the flexible slots or symbols should be configured as uplink slots or symbols or downlink slots or symbols based at least in part on the uplink and / or downlink resource allocation indicated by the PDCCH information. In some cases, the flexible slots or symbols may be dynamically changed by a network node via a DCI message or similar message (which may be referred to as a UE-specific configuration).

[0086] Resources (e.g., time slots and / or symbols) may be configured to have an SBFD format. Resources having an SBFD format include one or more SBFD symbols. An SBFD symbol is a symbol having one or more subbands (referred to herein as SBFD subbands) that a network node (such as a gNB) may use or will use for SBFD operations. For SBFD operations within a TDD carrier, an SBFD subband may include 1 resource block or a group of consecutive resource blocks for the same transmission direction. In some aspects, for SBFD operations within a TDD carrier, an SBFD subband consists of 1 resource block or a group of consecutive resource blocks for the same transmission direction. In some aspects, an "SBFD symbol" is defined as a symbol having a subband that the gNB will use for SBFD operations. In some aspects, for SBFD operations within a TDD carrier, an SBFD subband consists of 1 resource block (RB) or a group of consecutive RBs for the same transmission direction. In combination Figure 6 Additional description of SBFD resources is provided.Techniques described herein provide rules (eg, conditions) for reconfiguring resources and / or subbands between downlink formats, uplink formats, flexible formats, and SBFD formats.

[0087] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0088] Figure 6 is a diagram illustrating an example 600 of SBFD resources and communications according to the present disclosure. Figure 6 Examples 605 and 610 of SBFD resources are shown, as well as an example 615 of configuring communications between network node 110 and UEs 1 and 2 (eg, UE 120) using the SBFD configuration.

[0089] SBFD resources (i.e., resources with SBFD format) may include one or more symbols and / or one or more time slots. As mentioned above, SBFD resources may include at least one uplink subband (i.e., a subband for uplink communication of UE) and at least one downlink subband (i.e., a subband for downlink communication of UE). Example 605 includes two non-contiguous downlink subbands and one uplink subband. Example 610 includes one downlink subband and one uplink subband. The two downlink subbands of Example 605 may be used by a single UE, or may be used by different UEs (e.g., a first UE for a first downlink subband and a second UE for a second downlink subband). As mentioned above, a subband may include one or more continuous resource blocks associated with a transmission direction. Here, Example 605 includes two subbands associated with a downlink transmission direction and one subband associated with an uplink transmission direction, and Example 610 includes one subband associated with a downlink transmission direction and one subband associated with an uplink transmission direction. Examples 605 and 610 may illustrate a symbol having an SBFD format (e.g., a symbol in which there is a set of resource blocks including at least one downlink subband and a set of resource blocks including at least one uplink subband), a time slot having an SBFD format (e.g., a time slot in which there is at least one downlink subband and at least one uplink subband), or another time resource having an SBFD format.

[0090] In resources with SBFD format, the network node 110 may perform simultaneous transmission of downlink transmission and reception of uplink transmission on a subband basis. For example, the network node 110 may communicate with UE1 on the downlink and with UE2 on the uplink at the same time. In some examples, UE1 and / or UE2 may be configured only with subbands used by UE1 and / or UE2 for communication. For example, UE1 may be configured only with downlink subbands, and UE2 may be configured only with uplink subbands of SBFD formatted resources. This may be because, for example, UE1 and / or UE2 do not have the capability for SBFD communication. In some examples, UE1 and / or UE2 may be configured to utilize SBFD formatted resources. For example, if the UE has the capability for SBFD communication, the UE may know that a given resource has an SBFD format (while utilizing the resource only in one transmission direction), or may perform FD communication in a given resource.

[0091] The resource may be configured as a SBFD format. In some aspects, the resource may be configured as a SBFD format based at least in part on an indication of a change in the format of the resource. For example, the network node may provide signaling indicating that the format of the resource is selected as a SBFD format (similar to how signaling may indicate whether the format is an uplink format, a downlink format, or a flexible format). As another example, the network node may configure one or more subbands of the resource such that the resource includes at least one uplink subband and at least one downlink subband. For example, the network node may reconfigure a subband of a time slot having a downlink format as an uplink subband, thereby converting the time slot to have a SBFD format.

[0092] SBFD communication can provide (relative to full-band communication) an increased uplink duty cycle, resulting in reduced latency (because it is possible to receive downlink signaling in an uplink timeslot) and improved uplink coverage. In addition, SBFD communication can provide enhanced system capabilities, resource utilization, and spectrum efficiency. Still further, SBFD communication can achieve flexible and dynamic uplink / downlink resource adaptation according to uplink / downlink traffic in a robust manner.

[0093] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0094] The network node may configure the format of a resource set (such as a time slot or symbol) as described above. For example, the network node may configure the resource to have an uplink format, a downlink format, a flexible format, or an SBFD format. In some cases, it may be beneficial for the network node to reconfigure the format of the resources in the resource set, such as from a first format (selected from a downlink format, an uplink format, a flexible format, or an SBFD format) to a second different format (selected from a downlink format, an uplink format, a flexible format, or an SBFD format). In some cases, it may also be beneficial to reconfigure one or more subbands of the resource. However, there are situations in which reconfiguring the format associated with the resource or the subband associated with the resource may be harmful to the operation of the network. For example, if the downlink or flexible resource is reconfigured to an SBFD or uplink format, the transmission of some downlink channels or symbols may be negatively affected. As another example, if the uplink resource is reconfigured to an SBFD or downlink format, the transmission of some uplink transmissions may be negatively affected. In addition, reconfiguring resources or subbands from an SBFD format to another format (such as a downlink format or subband, an uplink format or subband, or a flexible format or subband) may be beneficial. However, reconfiguring resources or subbands from an SBFD format to a non-SBFD format may be detrimental to the communication operation of the network. Reconfiguring the format of resources and / or subbands without considering the detrimental consequences of the reconfiguration may result in reduced network throughput, reduced reliability, and reduced communication efficiency.

[0095] Some of the techniques described herein provide conditions (e.g., rules) for configuring a format (such as one or more time slots or one or more symbols) associated with a resource. In some aspects, the condition may relate to whether a resource with a downlink format or a flexible format can be reconfigured to an SBFD format (i.e., including an uplink subband). In some aspects, the condition may relate to whether a resource with an uplink format can be reconfigured to an SBFD format (i.e., including a downlink subband). In some aspects, the condition may relate to whether a conventional UE (i.e., a UE without SBFD capability) can be scheduled to send uplink communications and / or receive downlink communications in an SBFD resource. In some aspects, the condition may relate to whether an SBFD resource can be configured to fall back to a downlink format, an uplink format, and / or a flexible format. In some aspects, the condition may relate to whether a subband of an SBFD resource can be converted to a different format. Therefore, system operation can define a resource that can be configured as an SBFD resource. By providing conditions for reconfiguring resources between different formats associated with SBFD communications, network throughput is improved, reliability is improved, and communication efficiency is improved.

[0096] Figure 7is a diagram illustrating an example 700 of signaling associated with reconfiguring resources according to the present disclosure. Example 700 includes a UE (e.g., UE 120) and a network node (e.g., network node 110). In some aspects, the network node may include multiple network nodes, such as one or more CUs, one or more DUs, and / or one or more RUs. Operations described as being performed by a network node may be performed by one of the multiple network nodes.

[0097] As in Figure 7 , and as shown by reference numeral 710, the network node may output a first configuration for a resource set. For example, the network node may send and the UE may receive the first configuration. As another example, the network node may output the first configuration for sending (e.g., by the RU) to the UE. The first configuration may be associated with a TDD mode. For example, as combined with Figure 5 As described, the first configuration may include public configuration parameters and / or dedicated configuration parameters for the TDD mode. In some aspects, the first configuration may be a cell public configuration (i.e., public configuration parameters). In some aspects, the first configuration may include SFI (i.e., dedicated configuration parameters). In some aspects, the first configuration may include UE-specific configuration. The first configuration may configure the resource set to an uplink format, a downlink format, or a flexible format. For example, the full bandwidth of the resource set may be configured to one of an uplink format, a downlink format, or a flexible format. The resource set may include one or more time resources, such as one or more time slots, one or more symbols, or a combination thereof.

[0098] As shown in reference numeral 720, the network node may output a second configuration that configures one or more resources in the resource set to a SBFD format. The second configuration may configure one or more resources (e.g., one or more time slots, one or more symbols, or a combination thereof) to a SBFD format based at least in part on one or more resources satisfying a condition. The condition may define one or more rules for reconfiguring a resource or a subband of a resource from a first format (or subband) to a second format (or subband). In some aspects, the condition may indicate one or more formats or subbands to which a resource may be reconfigured based at least in part on the original (e.g., before reconfiguration) format or subband of the resource. In some aspects, the condition may indicate one or more formats or subbands to which a resource cannot be reconfigured based at least in part on the original (e.g., before reconfiguration) format or subband of the resource. In some aspects, the condition may indicate one or more formats or subbands to which a resource may or may not be reconfigured based at least in part on whether the resource is associated with a restricted use. Specific examples of the condition are provided in conjunction with reference numerals 730, 740, 780, and 790.

[0099] As shown in the figure numeral 730, in some aspects, the second configuration can configure the SBFD format in the resource with the downlink format or the flexible format. For example, the second configuration can explicitly change the format of the resource to the SBFD format or can configure the uplink subband in the resource. For example, the second configuration can configure the SBFD format or the uplink subband according to the condition. In some aspects, the condition indicates that any resource configured with the flexible format or the downlink format can be configured as the SBFD format. For example, it can be allowed to configure the SBFD format or the uplink subband in all downlink symbols or time slots and all flexible symbols or time slots.

[0100] In some aspects, the condition indicates that resources configured in a flexible format or downlink format and not associated with restricted use may be configured as SBFD format. For example, it may be permitted to configure SBFD format or uplink subbands in downlink symbols or time slots and flexible symbols or time slots but not in all downlink symbols or time slots. Restricted use is a use (such as transmission, reception, or configuration) that renders the resource unsuitable for reconfiguration to SBFD format. In some aspects, restricted use may include at least one of: synchronization signal block transmission (e.g., including symbols or time slots of synchronization signal block transmission), control resource sets associated with control channels for system information blocks (e.g., including symbols or time slots of control resource set (CORESET) zero), common search space (CSS) control channel transmission (e.g., symbols or time slots in which CSS physical downlink control channel (PDCCH) is configured), shared channel transmission scheduled via common search space control channel transmission (e.g., symbols or time slots in which CSS-PDCCH-scheduled physical downlink shared channel (PDSCH) is scheduled), common reference signal transmission (e.g., tracking reference signal (TRS) transmission), or common semi-persistent scheduling (SPS transmission (such as for broadcast signals)). Therefore, the negative impact on the transmission, reception, and configuration of resources associated with restricted use is reduced, thereby increasing the throughput and reliability of communications.

[0101] As shown in reference numeral 740, in some aspects, the second configuration may configure a SBFD format in the resource having an uplink format. For example, the second configuration may explicitly change the format of the resource to the SBFD format or may configure a downlink subband in the resource. In some aspects, the second configuration may configure the SBFD format or the downlink subband according to the condition. For example, the second configuration may configure the SBFD format or the downlink subband in the resource only if the condition indicates that the SBFD format or the downlink subband may be configured in the resource.

[0102] In some aspects, the condition indicates that the resource configured with the uplink format and not associated with restricted use can be configured as the SBFD format. For example, it is allowed to configure the SBFD format or downlink subband in some uplink resources but not all uplink resources. In this context (for example, for the resource configured with the uplink format), restricted use may include at least one of the random access channel opportunity, the sounding reference signal (SRS) transmission or the physical uplink control channel (PUCCH) transmission. Therefore, the negative impact of the transmission, reception and configuration of the resource associated with restricted use is reduced, thereby increasing the throughput and reliability of communication. In some aspects, the condition indicates that the resource configured with the uplink format cannot be configured as the SBFD format. In this case, the network node may not configure the resource with the uplink format as the SBFD format or include the downlink subband. Therefore, the stability of the resource configured with the uplink format can be increased, which improves the predictability of network services and configuration.

[0103] The network node may schedule downlink transmission or uplink transmission of the UE as indicated by reference numeral 750. For example, the network node may send a DCI that schedules the downlink transmission or uplink transmission.

[0104] In some aspects, a UE is associated with SBFD capability. Such a UE may be referred to as a legacy UE (relative to a UE associated with SBFD capability). In some aspects, uplink transmissions are permitted to be scheduled only in resources having an uplink format or a flexible format. In such aspects, for example, uplink transmissions may not be permitted to be scheduled in resources having an SBFD format (e.g., for a UE not associated with SBFD capability). Thus, a legacy UE (not having SBFD capability) may only be permitted to send uplink transmissions in uplink symbols or flexible symbols, but not in SBFD symbols.

[0105] In some aspects, for UEs not associated with SBFD capabilities (e.g., legacy UEs), uplink transmissions are permitted to be scheduled in uplink subbands of resources having SBFD formats (e.g., only in uplink subbands). For example, a legacy UE may be allowed to utilize SBFD operation at a network node only in an uplink subband and send uplink transmissions in SBFD resources. Thus, for legacy UEs performing unidirectional communication, a network node may implement SBFD communication in SBFD resources, which improves resource utilization at the network node and compatibility with legacy UEs.

[0106] In some aspects, for UEs not associated with SBFD capabilities (e.g., legacy UEs), downlink transmissions are permitted to be scheduled only in resources having a downlink format or a flexible format. For example, it may be that downlink transmissions are not permitted to be scheduled in resources having a SBFD format. Thus, a legacy UE may be scheduled to receive downlink transmissions only in downlink or flexible resources and not in SBFD resources.

[0107] In some aspects, for UEs not associated with SBFD capabilities (e.g., legacy UEs), downlink transmissions are permitted to be scheduled in downlink subbands of resources having SBFD formats. For example, a legacy UE may be allowed to utilize SBFD operations at a network node only in a downlink subband while receiving downlink transmissions in SBFD resources. Thus, for legacy UEs performing unidirectional communications, a network node may implement SBFD communications in SBFD resources, which improves resource utilization at the network node and compatibility with legacy UEs.

[0108] As shown by reference numeral 760, the UE and the network node may perform downlink transmission or uplink transmission. For example, the UE may transmit and the network node may receive uplink transmission. As another example, the network node may transmit and the UE may receive downlink transmission.

[0109] As shown in reference numeral 770, in some aspects, the network node may output a third configuration. The third configuration may configure the resource or a subband of the resource from the SBFD format to another format based at least in part on one or more resources satisfying a condition. As described above, the condition may define one or more rules for reconfiguring the resource or a subband of the resource from a first format (or subband) to a second format (or subband). The third configuration may be a cell-common configuration, an SFI-based configuration, or a UE-specific configuration.

[0110] As shown in reference numeral 780, in some aspects, the third configuration may configure the resources configured by the second configuration to have a SBFD format to have a downlink format, an uplink format, or a flexible format. Configuring the resources having the SBFD format to have a downlink format, an uplink format, or a flexible format may be referred to as "falling back" to the downlink format, the uplink format, or the flexible format. The third configuration may configure the resources according to the conditions described above in conjunction with reference numeral 720. A specific example of the condition is provided below.

[0111] In some aspects, the condition indicates that resources with SBFD format are not allowed to be reconfigured to downlink format, uplink format, or flexible format. For example, SBFD resources may not be allowed to fall back to downlink format, uplink format, or flexible format. In this example, the network node may not send a third configuration to reconfigure the SBFD resources to downlink resources, uplink resources, or flexible resources.

[0112] In some aspects, the condition indicates that resources with SBFD format are not allowed to be reconfigured to a downlink format, an uplink format, or a flexible format based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a slot format indication, or a cell-common configuration. For example, the condition may indicate whether resources with SBFD format configured as UE-specific configuration (e.g., UE-specific RRC signaling) are allowed to be reconfigured to a downlink format, an uplink format, or a flexible format. Additionally or alternatively, the condition may indicate whether resources with SBFD format configured as SFI are allowed to be reconfigured to a downlink format, an uplink format, or a flexible format. Additionally or alternatively, the condition may indicate whether resources with SBFD format configured as cell-common configuration are allowed to be reconfigured to a downlink format, an uplink format, or a flexible format.

[0113] In some aspects, the third configuration may reconfigure the resource with the SBFD format to at least one of a downlink format, an uplink format, or a flexible format. For example, the third configuration may include an indication of reconfiguring the resource with the SBFD format. In some aspects, the condition may indicate that the resource with the SBFD format is allowed to be reconfigured to a downlink format. In some aspects, the condition may indicate that the resource with the SBFD format is allowed to be reconfigured to an uplink format. In some aspects, the condition may indicate that the resource with the SBFD format is allowed to be reconfigured to a flexible format. In some aspects, the condition may indicate that the resource with the SBFD format may be reconfigured to any one of a downlink format, an uplink format, or a flexible format.

[0114] In some aspects, the condition may indicate whether resources associated with the SBFD format may be reconfigured based at least in part on whether the second configuration (e.g., a configuration as associated with the SBFD format) is a UE-specific configuration, an SFI-based configuration, or a cell-common configuration. For example, the condition may indicate that resources with an SBFD format configured as a UE-specific configuration are permitted to be reconfigured as a downlink format, an uplink format, and / or a flexible format. Additionally or alternatively, the condition may indicate that resources with an SBFD format configured as a SFI are permitted to be reconfigured as a downlink format, an uplink format, and / or a flexible format. Additionally or alternatively, the condition may indicate that resources with an SBFD format configured as a cell-common configuration are permitted to be reconfigured as a downlink format, an uplink format, and / or a flexible format.

[0115] As shown in reference numeral 790, in some aspects, the second configuration may configure the subband of the resource configured by the second configuration to have the SBFD format as a downlink subband, an uplink subband, or a flexible subband. The third configuration may configure the resource according to the conditions described above in conjunction with reference numeral 720. Specific examples of conditions related to reconfiguring the subband of the resource having the SBFD format are provided below.

[0116] In some aspects, the condition indicates that a subband of a resource having an SBFD format is not permitted to be reconfigured as any of a downlink subband, an uplink subband, or a flexible subband. In this example, the network node may not reconfigure a subband of a resource having an SBFD format as a downlink subband, an uplink subband, or a flexible subband. In some aspects, the condition may indicate that an uplink subband of a resource in an SBFD format is not permitted to be reconfigured as a downlink subband. Additionally or alternatively, the condition may indicate that a downlink subband of a resource in an SBFD format is not permitted to be reconfigured as an uplink subband. Additionally or alternatively, the condition may indicate that a downlink subband or an uplink subband of a resource in an SBFD format is not permitted to be reconfigured as a flexible subband. Additionally or alternatively, the condition may indicate that a downlink or uplink subband of a resource in an SBFD format is permitted to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

[0117] In some aspects, the condition (as described with respect to reconfiguring the subband of the SBFD resources) indicates whether the subband is permitted to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a slot format indication, or a cell-common configuration. For example, the condition may indicate whether a subband of resources having an SBFD format configured as a UE-specific configuration is permitted to be reconfigured as a downlink subband, an uplink subband, and / or a flexible subband. Additionally or alternatively, the condition may indicate whether a subband of resources having an SBFD format configured as a SFI is permitted to be reconfigured as a downlink subband, an uplink subband, and / or a flexible subband. Additionally or alternatively, the condition may indicate whether a subband of resources having an SBFD format configured as a cell-common configuration is permitted to be reconfigured as a downlink subband, an uplink subband, and / or a flexible subband.

[0118] As shown in reference numeral 795, the UE and the network node may communicate on one or more resources. For example, if the resource is configured as an uplink resource, or if the UE is scheduled to send an uplink transmission on an uplink subband of the resource, the UE may send and the network node may receive the uplink transmission. As another example, if the resource is configured as a downlink resource, or if the UE is scheduled to receive a downlink transmission on a downlink subband of the resource, the network node may send and the UE may receive the downlink transmission.

[0119] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0120] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network node according to the present disclosure. The example process 800 is an example in which a network node (eg, network node 110, CU, DU, RU, or a combination thereof) performs operations associated with sub-band full-duplex resource configuration.

[0121] like Figure 8 As shown in FIG. 8 , in some aspects, process 800 may include outputting a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format (block 810). For example, a network node (e.g., using Fig.10 The communication manager 150 and / or configuration component 1008 depicted in the figure can output a first configuration for a resource set, which is associated with a time division duplex mode and configures the resource set to one of an uplink format, a downlink format, or a flexible format, as described above.

[0122] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include outputting a second configuration of configuring the one or more resources in the resource set in the SBFD format based at least in part on one or more resources satisfying a condition (block 820). Fig.10 The communication manager 150 and / or configuration component 1008 depicted in FIG. 1 may output a second configuration configuring the one or more resources in the resource set into a SBFD format based at least in part on one or more resources in the resource set satisfying a condition, as described above.

[0123] Process 800 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 herein.

[0124] In a first aspect, the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol.

[0125] In a second aspect, alone or in combination with the first aspect, the condition indicates that any resource configured in a flexible format or a downlink format may be configured in a SBFD format.

[0126] In a third aspect, alone or in combination with one or more of the first and second aspects, the condition indicates that resources configured in a flexible format or a downlink format and not associated with restricted usage may be configured in a SBFD format.

[0127] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the restricted use includes at least one of the following: synchronization signal block transmission, a control resource set associated with a control channel for a system information block, a common search space control channel transmission, a shared channel transmission scheduled via a common search space control channel transmission, a common reference signal transmission, or a common semi-persistent scheduling transmission.

[0128] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the condition indicates that resources configured in an uplink format cannot be configured in a SBFD format.

[0129] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the condition indicates that resources configured in an uplink format and not associated with restricted use may be configured in a SBFD format.

[0130] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the restricted use includes at least one of a random access channel opportunity, a sounding reference signal transmission, or a physical uplink control channel transmission.

[0131] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 800 includes scheduling uplink transmissions of a UE not associated with SBFD capability, wherein the uplink transmissions are permitted to be scheduled only in resources having an uplink format or a flexible format.

[0132] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, uplink transmissions are not permitted to be scheduled in resources having a SBFD format.

[0133] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 800 includes scheduling uplink transmissions of a UE not associated with SBFD capability, wherein the uplink transmissions are permitted to be scheduled in an uplink subband of resources having a SBFD format.

[0134] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 800 includes scheduling downlink transmissions of a UE not associated with SBFD capability, wherein the downlink transmissions are permitted to be scheduled only in resources having a downlink format or a flexible format.

[0135] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, downlink transmissions are not permitted to be scheduled in resources having a SBFD format.

[0136] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 800 includes scheduling downlink transmissions of a UE not associated with SBFD capability, wherein the downlink transmissions are permitted to be scheduled in a downlink subband of resources having a SBFD format.

[0137] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the condition indicates that resources having the SBFD format are not permitted to be reconfigured into a downlink format, an uplink format, or a flexible format.

[0138] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the condition indicates that resources with SBFD format are not allowed to be reconfigured to a downlink format, an uplink format or a flexible format based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication or a cell-common configuration.

[0139] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 800 includes sending an indication to reconfigure resources having a SBFD format to at least one of a downlink format, an uplink format, or a flexible format.

[0140] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, reconfiguring resources is based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a slot format indication, or a cell-common configuration.

[0141] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the condition indicates that a subband of resources having an SBFD format is not allowed to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband.

[0142] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the condition indicates that the subband is not allowed to be reconfigured as at least one of a downlink subband, an uplink subband or a flexible subband based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication, or a cell-common configuration.

[0143] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the condition indicates that an uplink subband of resources in a SBFD format is not permitted to be reconfigured as a downlink subband.

[0144] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, the condition indicates that a downlink subband of resources in a SBFD format is not permitted to be reconfigured as an uplink subband.

[0145] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the condition indicates that a downlink or uplink subband of resources in a SBFD format is not permitted to be reconfigured as a flexible subband.

[0146] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the condition indicates that a downlink or uplink subband of resources in a SBFD format is permitted to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

[0147] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8The blocks depicted in the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of the process 800 may be performed in parallel.

[0148] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a UE according to the present disclosure. Example process 900 is an example in which a UE (eg, UE 120) performs operations associated with sub-band full-duplex resource configuration.

[0149] like Fig. 9 As shown in FIG. 1 , in some aspects, process 900 may include receiving a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format (block 910). For example, a UE (e.g., using Fig.11 The communication manager 140 and / or receiving component 1102 depicted in the figure can receive a first configuration for a resource set, which is associated with a time division duplex mode and configures the resource set as one of an uplink format, a downlink format, or a flexible format, as described above.

[0150] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include receiving a second configuration to configure one or more resources in a resource set as a SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources as a SBFD format (block 920). Figure 1 The communication manager 140 and / or receiving component 1102 depicted in FIG. 1 may receive a second configuration that configures one or more resources in the resource set into an SBFD format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources into the SBFD format, as described above.

[0151] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include communicating on one or more resources (block 930). For example, a UE (e.g., using Fig.11 The communication manager 140 and / or the sending component 1104 or the receiving component 1102 depicted in can communicate over one or more resources, as described above.

[0152] 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 herein.

[0153] In a first aspect, the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol.

[0154] In a second aspect, alone or in combination with the first aspect, the condition indicates that any resource configured in a flexible format or a downlink format may be configured in a SBFD format.

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, the condition indicates that resources configured in a flexible format or a downlink format and not associated with restricted usage may be configured in a SBFD format.

[0156] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the restricted use includes at least one of the following: synchronization signal block transmission, a control resource set associated with a control channel for a system information block, a common search space control channel transmission, a shared channel transmission scheduled via a common search space control channel transmission, a common reference signal transmission, or a common semi-persistent scheduling transmission.

[0157] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the condition indicates that resources configured in an uplink format cannot be configured in a SBFD format.

[0158] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the condition indicates that resources configured in an uplink format and not associated with restricted use may be configured in a SBFD format.

[0159] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the restricted use includes at least one of a random access channel opportunity, a sounding reference signal transmission, or a physical uplink control channel transmission.

[0160] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 900 includes receiving downlink control information for scheduling uplink transmissions of a UE, wherein the UE is not associated with SBFD capability and wherein the uplink transmissions are permitted to be scheduled only in resources having an uplink format or a flexible format.

[0161] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, uplink transmissions are not permitted to be scheduled in resources having a SBFD format.

[0162] In a tenth aspect, either alone or in combination with one or more of aspects one to nine, process 900 comprises receiving downlink control information for scheduling an uplink transmission, wherein the UE is not associated with SBFD capability, and wherein the uplink transmission is permitted to be scheduled in an uplink subband of resources having a SBFD format.

[0163] In an eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 900 includes receiving downlink control information for scheduling downlink transmissions, wherein the UE is not associated with SBFD capability, and wherein the downlink transmissions are permitted to be scheduled only in resources having a downlink format or a flexible format.

[0164] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, downlink transmissions are not permitted to be scheduled in resources having a SBFD format.

[0165] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, process 900 includes receiving downlink control information for scheduling a downlink transmission, wherein the UE is not associated with SBFD capability, and wherein the downlink transmission is permitted to be scheduled in a downlink subband of resources having a SBFD format.

[0166] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the condition indicates that resources having the SBFD format are not permitted to be reconfigured into a downlink format, an uplink format, or a flexible format.

[0167] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the condition indicates that resources are not allowed to be reconfigured to a downlink format, an uplink format or a flexible format based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication, or a cell-common configuration.

[0168] In a sixteenth aspect, either alone or in combination with one or more of the first to fifteenth aspects, process 900 includes receiving an indication to reconfigure resources to at least one of a downlink format, an uplink format, or a flexible format.

[0169] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, the indication is based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication, or a cell-common configuration.

[0170] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the condition indicates that a subband of resources in SBFD format is not allowed to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband.

[0171] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, the condition indicates that the subband is not allowed to be reconfigured as at least one of a downlink subband, an uplink subband or a flexible subband based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication, or a cell-common configuration.

[0172] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, the condition indicates that an uplink subband of resources in a SBFD format is not permitted to be reconfigured as a downlink subband.

[0173] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, the condition indicates that a downlink subband of resources in a SBFD format is not permitted to be reconfigured as an uplink subband.

[0174] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, the condition indicates that a downlink or uplink subband of resources in a SBFD format is not permitted to be reconfigured as a flexible subband.

[0175] In a twenty-third aspect, either alone or in combination with one or more of the first to twenty-second aspects, the condition indicates that a downlink or uplink subband of resources in a SBFD format is permitted to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

[0176] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted in the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks in the blocks of the process 900 may be performed in parallel.

[0177] Fig.101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a network node, or a network node may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 150. Communication manager 150 may include configuration component 1008, etc.

[0178] In some aspects, the apparatus 1000 may be configured to perform the Figures 3 to 11 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein (such as Figure 8 In some aspects, Fig.10 The apparatus 1000 and / or one or more components shown in FIG. 1 may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0179] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0180] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the apparatus 1006. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the apparatus 1006. In some aspects, the 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 the apparatus 1006. In some aspects, the transmitting component 1004 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0181] The configuration component 1008 can output a first configuration for the resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The configuration component 1008 can output a second configuration configuring the one or more resources in the resource set as a SBFD format based at least in part on one or more resources satisfying a condition.

[0182] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.10 Two or more components shown in the figure may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.10 One or more functions performed by another group of components shown in the figure.

[0183] Fig.111 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. Apparatus 1100 may be a UE, or a UE may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and transmitting component 1104. As further shown, apparatus 1100 may include a communication manager 140.

[0184] In some aspects, the apparatus 1100 may be configured to perform the Figures 3 to 11 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein (such as Fig. 9 In some aspects, the apparatus 1100 and / or Fig.11 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0185] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0186] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 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 the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0187] The receiving component 1102 can receive a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format. The receiving component 1102 can receive a second configuration configuring the one or more resources in the resource set as a SBFD format based at least in part on one or more resources satisfying a condition, the condition being associated with configuring the one or more resources as a SBFD format. The receiving component 1102 and the sending component 1104 can communicate on the one or more resources.

[0188] Fig.11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.11 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.11 Two or more components shown in the figure may be implemented in a single component, or Fig.11 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.11 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.11 One or more functions performed by another group of components shown in the figure.

[0189] The following provides an overview of some aspects of the disclosure:

[0190] Aspect 1: A method of wireless communication performed by a network node, comprising: outputting a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set as one of an uplink format, a downlink format, or a flexible format; and outputting a second configuration configuring the one or more resources in the resource set as a sub-band full-duplex (SBFD) format based at least in part on one or more resources in the resource set satisfying a condition.

[0191] Aspect 2: The method according to aspect 1, wherein the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol.

[0192] Aspect 3: The method according to any one of aspects 1 to 2, wherein the condition indicates that any resource configured in the flexible format or the downlink format can be configured in the SBFD format.

[0193] Aspect 4: The method according to any one of aspects 1 to 3, wherein the condition indicates that resources configured in the flexible format or the downlink format and not associated with restricted usage can be configured in the SBFD format.

[0194] Aspect 5: A method according to Aspect 4, wherein the restricted use includes at least one of the following: synchronization signal block transmission, a control resource set associated with a control channel for a system information block, a common search space control channel transmission, a shared channel transmission scheduled via a common search space control channel transmission, a common reference signal transmission, or a common semi-persistent scheduling transmission.

[0195] Aspect 6: The method according to any one of aspects 1 to 5, wherein the condition indicates that the resources configured in the uplink format cannot be configured in the SBFD format.

[0196] Aspect 7: The method according to any one of aspects 1 to 6, wherein the condition indicates that resources configured in the uplink format and not associated with restricted use can be configured in the SBFD format.

[0197] Aspect 8: The method according to aspect 7, wherein the restricted use includes at least one of the following: random access channel opportunity, sounding reference signal transmission or physical uplink control channel transmission.

[0198] Aspect 9: The method according to any one of aspects 1 to 8 further includes: scheduling uplink transmission of a user equipment not associated with SBFD capability, wherein the uplink transmission is permitted to be scheduled only in resources having the uplink format or the flexible format.

[0199] Aspect 10: The method according to aspect 9, wherein the uplink transmission is not permitted to be scheduled in resources having the SBFD format.

[0200] Aspect 11: The method according to any one of aspects 1 to 10 further comprises: scheduling uplink transmission of a user equipment not associated with SBFD capability, wherein the uplink transmission is permitted to be scheduled in an uplink subband of the resource having the SBFD format.

[0201] Aspect 12: The method according to any one of Aspects 1 to 11 further comprises: scheduling downlink transmission of a user equipment not associated with SBFD capability, wherein the downlink transmission is permitted to be scheduled only in resources having the downlink format or the flexible format.

[0202] Aspect 13: The method according to aspect 12, wherein the downlink transmission is not permitted to be scheduled in resources having the SBFD format.

[0203] Aspect 14: The method according to any one of aspects 1 to 11 further comprises: scheduling downlink transmissions of user equipment not associated with SBFD capability, wherein the downlink transmissions are permitted to be scheduled in a downlink subband of the resource having the SBFD format.

[0204] Aspect 15: The method according to any one of aspects 1 to 14, wherein the condition indicates that the resource having the SBFD format is not permitted to be reconfigured to the downlink format, the uplink format or the flexible format.

[0205] Aspect 16: A method according to Aspect 15, wherein the condition indicates that the resources having the SBFD format are not allowed to be reconfigured to the downlink format, the uplink format or the flexible format based at least in part on whether the second configuration is a user equipment-specific configuration, a configuration based on a time slot format indication or a cell-common configuration.

[0206] Aspect 17: The method according to any one of Aspects 1 to 16 further includes: sending an indication to reconfigure the resource having the SBFD format to at least one of the following: the downlink format, the uplink format or the flexible format.

[0207] Aspect 18: The method according to aspect 13, wherein reconfiguring the resources is based at least in part on whether the second configuration is a user equipment specific configuration, a configuration based on a slot format indication, or a cell common configuration.

[0208] Aspect 19: The method according to any one of aspects 1 to 18, wherein the condition indicates that the subband of the resource having the SBFD format is not permitted to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband.

[0209] Aspect 20: A method according to Aspect 17, wherein the condition indicates that the subband is not allowed to be reconfigured as at least one of the downlink subband, the uplink subband or the flexible subband based at least in part on whether the second configuration is a user equipment-specific configuration, a configuration based on a time slot format indication or a cell-common configuration.

[0210] Aspect 21: The method according to any one of aspects 1 to 20, wherein the condition indicates that an uplink subband of the resource in the SBFD format is not permitted to be reconfigured as a downlink subband.

[0211] Aspect 22: The method according to any one of aspects 1 to 21, wherein the condition indicates that a downlink subband of the resource in the SBFD format is not permitted to be reconfigured as an uplink subband.

[0212] Aspect 23: The method according to any one of aspects 1 to 22, wherein the condition indicates that a downlink or uplink subband of the resource in the SBFD format is not permitted to be reconfigured as a flexible subband.

[0213] Aspect 24: The method according to any one of aspects 1 to 23, wherein the conditional indication permits a downlink or uplink subband of the resource in the SBFD format to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

[0214] Aspect 25: A method for wireless communication performed by a user equipment (UE), comprising: receiving a first configuration for a resource set, the first configuration being associated with a time division duplex mode, and the first configuration configuring the resource set to one of an uplink format, a downlink format, or a flexible format; receiving a second configuration configuring the one or more resources to a sub-band full-duplex (SBFD) format based at least in part on one or more resources in the resource set satisfying a condition, the condition being associated with configuring the one or more resources to the SBFD format; and communicating on the one or more resources.

[0215] Aspect 26: The method according to aspect 25, wherein the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol.

[0216] Aspect 27: The method according to any one of aspects 25 to 26, wherein the condition indicates that any resource configured in the flexible format or the downlink format can be configured as the SBFD format.

[0217] Aspect 28: The method according to any one of aspects 25 to 27, wherein the condition indicates that resources configured in the flexible format or the downlink format and not associated with restricted usage can be configured in the SBFD format.

[0218] Aspect 29: A method according to Aspect 28, wherein the restricted use includes at least one of the following: synchronization signal block transmission, a control resource set associated with a control channel for a system information block, a common search space control channel transmission, a shared channel transmission scheduled via a common search space control channel transmission, a common reference signal transmission, or a common semi-persistent scheduling transmission.

[0219] Aspect 30: The method according to any one of aspects 25 to 29, wherein the condition indicates that the resources configured in the uplink format cannot be configured as the SBFD format.

[0220] Aspect 31: The method according to any one of aspects 25 to 30, wherein the condition indicates that resources configured in the uplink format and not associated with restricted usage can be configured in the SBFD format.

[0221] Aspect 32: The method according to aspect 31, wherein the restricted use includes at least one of the following: random access channel opportunities, sounding reference signal transmissions, or physical uplink control channel transmissions.

[0222] Aspect 33: The method according to any one of Aspects 25 to 32 further includes: receiving downlink control information for scheduling uplink transmission of the UE, wherein the UE is not associated with SBFD capability, and wherein the uplink transmission is permitted to be scheduled only in resources having the uplink format or the flexible format.

[0223] Aspect 34: The method according to aspect 33, wherein the uplink transmission is not permitted to be scheduled in resources having the SBFD format.

[0224] Aspect 35: The method according to any one of Aspects 25 to 34 further includes: receiving downlink control information for scheduling uplink transmission, wherein the UE is not associated with SBFD capability, and wherein the uplink transmission is permitted to be scheduled in an uplink subband of the resource having the SBFD format.

[0225] Aspect 36: The method according to any one of Aspects 25 to 35 further includes: receiving downlink control information for scheduling downlink transmission, wherein the UE is not associated with SBFD capability, and wherein the downlink transmission is permitted to be scheduled only in resources having the downlink format or the flexible format.

[0226] Aspect 37: The method according to aspect 36, wherein the downlink transmission is not permitted to be scheduled in resources having the SBFD format.

[0227] Aspect 38: The method according to any one of Aspects 25 to 37 further includes: receiving downlink control information for scheduling downlink transmission, wherein the UE is not associated with SBFD capability, and wherein the downlink transmission is permitted to be scheduled in a downlink subband of the resource having the SBFD format.

[0228] Aspect 39: The method according to any one of aspects 25 to 38, wherein the condition indicates that the resource having the SBFD format is not permitted to be reconfigured to the downlink format, the uplink format or the flexible format.

[0229] Aspect 40: A method according to aspect 39, wherein the condition indicates that the resource is not allowed to be reconfigured to the downlink format, the uplink format or the flexible format based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication or a cell-common configuration.

[0230] Aspect 41: The method according to any one of aspects 25 to 40 further comprises: receiving an indication to reconfigure the resources to at least one of: the downlink format, the uplink format or the flexible format.

[0231] Aspect 42: The method according to aspect 41, wherein the indication is based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a slot format indication, or a cell-common configuration.

[0232] Aspect 43: The method according to any one of aspects 25 to 42, wherein the condition indicates that a subband of the resource in the SBFD format is not permitted to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband.

[0233] Aspect 44: A method according to Aspect 43, wherein the condition indicates that the subband is not allowed to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband based at least in part on whether the second configuration is a UE-specific configuration, a configuration based on a time slot format indication, or a cell-common configuration.

[0234] Aspect 45: The method according to any one of aspects 25 to 44, wherein the condition indicates that an uplink subband of the resource in the SBFD format is not permitted to be reconfigured as a downlink subband.

[0235] Aspect 46: The method according to any one of aspects 25 to 45, wherein the condition indicates that a downlink subband of the resource in the SBFD format is not permitted to be reconfigured as an uplink subband.

[0236] Aspect 47: The method according to any one of aspects 25 to 46, wherein the condition indicates that a downlink or uplink subband of the resource in the SBFD format is not permitted to be reconfigured as a flexible subband.

[0237] Aspect 48: The method according to any one of aspects 25 to 47, wherein the conditional indication permits a downlink or uplink subband of the resource in the SBFD format to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

[0238] Aspect 49: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 48.

[0239] Aspect 50: An apparatus for wireless communication, comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 48.

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

[0241] Aspect 52: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 48.

[0242] Aspect 53: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 48.

[0243] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0244] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads, processes and / or functions implemented, etc. As used herein, "processor" is implemented in hardware and / or a combination of hardware and software. It will be clear that the system and / or method described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0245] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0246] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0247] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more entries, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries, and can be used interchangeably with "one or more". If only one entry is intended to be referred to, the phrase "only one" or similar terms are used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise clearly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A network node for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: outputting a first configuration for a set of resources, the first configuration being associated with a time division duplex mode, and the first configuration configuring the set of resources as one of an uplink format, a downlink format, or a flexible format; as well as Based at least in part on one or more resources in the set of resources satisfying a condition, a second configuration is outputted that configures the one or more resources into a sub-band full-duplex (SBFD) format. 2 . The network node according to claim 1 , wherein the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol. 3 . The network node according to claim 1 , wherein the condition indicates that any resource configured in the flexible format or the downlink format can be configured in the SBFD format. 4 . The network node according to claim 1 , wherein the condition indicates that resources configured in the flexible format or the downlink format and not associated with restricted usage can be configured in the SBFD format.

5. The network node of claim 4, wherein the restricted use comprises at least one of: Synchronous signal block sending, a set of control resources associated with a control channel for a system information block, The common search space control channel is sent, A shared channel transmission scheduled via a common search space control channel transmission, Common reference signal transmission, or Public semi-persistent schedule send.

6. The network node of claim 1, wherein the condition indicates that resources configured in the uplink format cannot be configured in the SBFD format. 7 . The network node of claim 1 , wherein the condition indicates that resources configured in the uplink format and not associated with restricted usage can be configured in the SBFD format.

8. The network node of claim 7, wherein the restricted use comprises at least one of: Random access channel opportunity, Sounding reference signal transmission, or Physical uplink control channel transmission.

9. The network node of claim 1 , wherein the one or more processors are further configured to: An uplink transmission of a user equipment not associated with SBFD capability is scheduled, wherein the uplink transmission is permitted to be scheduled only in resources having the uplink format or the flexible format.

10. The network node of claim 1, wherein the one or more processors are further configured to: An uplink transmission of a user equipment not associated with SBFD capability is scheduled, wherein the uplink transmission is granted to be scheduled in an uplink subband of the one or more resources having the SBFD format.

11. The network node of claim 1 , wherein the one or more processors are further configured to: A downlink transmission of a user equipment not associated with SBFD capability is scheduled, wherein the downlink transmission is permitted to be scheduled only in resources having the downlink format or the flexible format.

12. The network node of claim 11, wherein the downlink transmission is not permitted to be scheduled in resources having the SBFD format.

13. The network node of claim 1 , wherein the one or more processors are further configured to: A downlink transmission of a user equipment not associated with SBFD capability is scheduled, wherein the downlink transmission is granted to be scheduled in a downlink subband of the one or more resources having the SBFD format.

14. The network node of claim 1, wherein the condition indicates that the one or more resources having the SBFD format are not permitted to be reconfigured to the downlink format, the uplink format, or the flexible format.

15. The network node of claim 1 , wherein the one or more processors are further configured to send an indication to reconfigure the one or more resources having the SBFD format to at least one of: The downlink format, the uplink format, or The flexible format.

16. The network node of claim 1, wherein the condition indicates that a subband of the one or more resources having the SBFD format is not permitted to be reconfigured as at least one of a downlink subband, an uplink subband, or a flexible subband.

17. The network node of claim 1, wherein the condition indicates permission for a downlink or uplink subband of the one or more resources in the SBFD format to be reconfigured as a flexible subband, a downlink subband, or an uplink subband.

18. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: receiving a first configuration for a set of resources, the first configuration being associated with a time division duplex mode, and the first configuration configuring the set of resources as one of an uplink format, a downlink format, or a flexible format; receiving a second configuration to configure the one or more resources in the set of resources into a sub-band full-duplex (SBFD) format based at least in part on one or more resources in the set of resources satisfying a condition, the condition being associated with configuring the one or more resources into the SBFD format; as well as Communicating over the one or more resources. 19 . The UE according to claim 18 , wherein the condition indicates that resources configured in the flexible format or the downlink format and not associated with restricted use can be configured in the SBFD format. 20 . The UE of claim 18 , wherein the condition indicates that resources configured in the uplink format and not associated with restricted use can be configured as the SBFD format.

21. The UE of claim 18, wherein the one or more processors are further configured to: Downlink control information is received to schedule uplink transmissions of the UE, wherein the UE is not associated with SBFD capability, and wherein the uplink transmissions are permitted to be scheduled only in resources having the uplink format or the flexible format.

22. The UE of claim 18, wherein the one or more processors are further configured to: Downlink control information scheduling an uplink transmission is received, wherein the UE is not associated with SBFD capability, and wherein the uplink transmission is granted to be scheduled in an uplink subband of the one or more resources having the SBFD format.

23. The UE of claim 18, wherein the one or more processors are further configured to: Downlink control information scheduling a downlink transmission is received, wherein the UE is not associated with SBFD capability, and wherein the downlink transmission is permitted to be scheduled only in resources having the downlink format or the flexible format.

24. The UE of claim 18, wherein the one or more processors are further configured to: Downlink control information scheduling a downlink transmission is received, wherein the UE is not associated with SBFD capability, and wherein the downlink transmission is granted to be scheduled in a downlink subband of the one or more resources having the SBFD format.

25. The UE of claim 18, wherein the one or more processors are further configured to receive an indication to reconfigure the one or more resources to at least one of: The downlink format, the uplink format, or The flexible format.

26. A method of wireless communication performed by a network node, comprising: outputting a first configuration for a set of resources, the first configuration being associated with a time division duplex mode, and the first configuration configuring the set of resources as one of an uplink format, a downlink format, or a flexible format; as well as Based at least in part on one or more resources in the set of resources satisfying a condition, a second configuration is outputted that configures the one or more resources into a sub-band full-duplex (SBFD) format.

27. The method of claim 26, wherein the SBFD format includes at least one downlink subband and at least one uplink subband in the same symbol.

28. The method of claim 26, wherein the condition indicates that any resource configured in the flexible format or the downlink format can be configured in the SBFD format.

29. A method of wireless communication performed by a user equipment (UE), comprising: receiving a first configuration for a set of resources, the first configuration being associated with a time division duplex mode, and the first configuration configuring the set of resources as one of an uplink format, a downlink format, or a flexible format; receiving a second configuration to configure the one or more resources in the set of resources into a sub-band full-duplex (SBFD) format based at least in part on one or more resources in the set of resources satisfying a condition, the condition being associated with configuring the one or more resources into the SBFD format; as well as Communicating over the one or more resources.

30. The method of claim 29, wherein the condition indicates that resources configured in the flexible format or the downlink format and not associated with restricted use can be configured in the SBFD format.

Images