Dynamic update of sub-band full duplex slots and symbols

Abstract

Wireless communication systems, apparatuses, and methods are provided. A method of wireless communication performed by a user equipment (UE) includes receiving, from a network element, a first configuration indicating a time location and a frequency location for a network side subband full duplex (SBFD) mode of operation, where the time location indicates at least one SBFD symbol or slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink sub-bands and uplink sub-bands or a plurality of uplink sub-bands and guard bands; and receiving, from the network element, a second configuration indicating a change from the at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of U.S. Patent Application No. 18 / 059,665, filed on Nov. 29, 2022, the disclosure of which is incorporated herein by reference in its entirety as if set forth fully below and for all applicable purposes. Technical Field

[0003] This application relates to wireless communication systems, and more particularly to dynamic updates of sub - band full - duplex time slots and symbols in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems can be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multi - access communication system may include multiple base stations (BSs), each of which simultaneously supports communication of multiple communication devices, which may also be referred to as user equipment (UE).

[0005] To meet the growing demand for extended mobile broadband connectivity, wireless communication technologies are evolving from LTE technology to the next - generation New Radio (NR) technology. For example, compared to LTE, NR is designed to provide lower latency, higher bandwidth or throughput, and higher reliability. NR is designed to operate over a wide array of frequency bands, e.g., from low frequency bands below about 1 gigahertz (GHz) and intermediate frequency bands from about 1 GHz to about 6 GHz to high frequency bands such as millimeter - wave (mmWave) bands. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed spectrum and shared spectrum. Spectrum sharing enables operators to have the opportunity to aggregate spectrum to dynamically support high - bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0006] NR can support various deployment scenarios to benefit from various spectrums within different frequency ranges, licensed and / or unlicensed, and / or co - existence of LTE and NR technologies. For example, NR can be deployed in a stand - alone NR mode on licensed bands and / or unlicensed bands, or in a dual - connectivity mode with various combinations of NR and LTE on licensed bands and / or unlicensed bands.

[0007] In a wireless communication network, a BS can communicate with a UE in both the uplink direction and the downlink direction. A sidelink was introduced in LTE to allow a UE to transmit data to another UE (e.g., from one vehicle to another vehicle) without tunneling through the BS and / or the associated core network. LTE sidelink technology has been extended to provide device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, and / or cellular vehicle-to-everything (C-V2X) communication. Similarly, NR can be extended to support sidelink communication, D2D communication, V2X communication, and / or C-V2X on licensed bands and / or unlicensed bands (e.g., shared bands). SUMMARY OF THE DISCLOSURE

[0008] Some aspects of the present disclosure are summarized below to provide a basic understanding of the technologies discussed. This Summary is not an exhaustive overview of all the expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this Summary is to present some concepts of one or more aspects of the present disclosure in a generalized form as a prelude to the more detailed embodiments that are presented later.

[0009] In one aspect of the present disclosure, a method of wireless communication performed by a user equipment (UE) may include: receiving, from a network unit, a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode, where the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band; and receiving, from the network unit, a second configuration indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0010] In an additional aspect of the present disclosure, a method of wireless communication performed by a network unit may include: sending, to a user equipment (UE), a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode, where the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot), and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band; and sending, to the UE, a second configuration indicating a change from at least one SBFD symbol / slot to a different SBFD symbol / slot format.

[0011] In an additional aspect of the present disclosure, a user equipment (UE) may include: a memory; a transceiver; and at least one processor coupled to the memory and the transceiver, wherein the UE is configured to: receive, from a network element, a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode, wherein the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band; and receive, from the network element, a second configuration indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0012] In an additional aspect of the present disclosure, a network element may include: a memory; a transceiver; and at least one processor coupled to the memory and the transceiver, wherein the network element is configured to: send, to a user equipment (UE), a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode, wherein the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot), and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band; and send, to the UE, a second configuration indicating a change from at least one SBFD symbol / slot to a different SBFD symbol / slot format.

[0013] After reading the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features, and embodiments of the present invention will become apparent to those of ordinary skill in the art. Although the features of the present invention may be discussed below with respect to certain aspects and drawings, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments of the present invention discussed herein. In a similar manner, although the exemplary aspects may be discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A wireless communication network is illustrated in accordance with some aspects of the present disclosure.

[0015] Figure 2 An example decomposed base station architecture is illustrated in accordance with some aspects of the present disclosure.

[0016] Figure 3 A wireless communication network operating in a subband full-duplex mode is illustrated in accordance with some aspects of the present disclosure.

[0017] Figure 4A Illustrates sub - bands and guard bands in a component carrier according to some aspects of the present disclosure.

[0018] Figure 4B Illustrates sub - bands and guard bands in a component carrier according to some aspects of the present disclosure.

[0019] Figure 5 Is a signal flow diagram of a communication method according to some aspects of the present disclosure.

[0020] Figure 6 Is a block diagram of an exemplary user equipment (UE) according to some aspects of the present disclosure.

[0021] Figure 7 Is a block diagram of an exemplary network element according to some aspects of the present disclosure.

[0022] Figure 8 Is a flowchart of a communication method according to some aspects of the present disclosure.

[0023] Figure 9 Is a flowchart of a communication method according to some aspects of the present disclosure. Detailed Description

[0024] The detailed description set forth below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. For a thorough understanding of the various concepts, the detailed description includes specific details. It will be apparent, however, to one of ordinary skill in the art that the concepts may be practiced without these specific details. In some instances, well - known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0025] The present disclosure generally relates to wireless communication systems, which are also referred to as wireless communication networks. In various examples, technologies and devices can be used in wireless communication networks such as code - division multiple - access (CDMA) networks, time - division multiple - access (TDMA) networks, frequency - division multiple - access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single - carrier FDMA (SC - FDMA) networks, LTE networks, GSM networks, fifth - generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms “network” and “system” can be used interchangeably.

[0026] OFDMA networks can implement radio technologies such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long-Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). These radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a cooperation among groups of telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP Long-Term Evolution (LTE) is a 3GPP plan aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP can define the specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure relates to the evolution from LTE, 4G, 5G, NR, and more advanced wireless technologies, where access to the wireless spectrum is shared among networks using a series of new and different radio access technologies or radio air interfaces.

[0027] Specifically, 5G networks consider various deployments, various spectrums, and various services and devices that can be implemented using an OFDM-based unified air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to (1) provide coverage for massive Internet of Things (IoT) with ultra-high density (e.g., about 1M nodes / km2), ultra-low complexity (e.g., about 10s bits / second), and ultra-low power consumption (e.g., about 10+ year battery life), and provide deep coverage with the ability to reach challenging locations; (2) provide coverage including critical mission control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond), and users with extensive mobility or lack of mobility; and (3) have enhanced mobile broadband, including extremely high capacity (e.g., about 10 Tbps / km2), extremely high data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rate), and deep awareness with advanced discovery and optimization capabilities.

[0028] 5G NR can be implemented to use an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); have a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time-division duplex (TDD) / frequency-division duplex (FDD) designs; and have advanced radio technologies such as massive multiple-input multiple-output (MIMO), robust millimeter-wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of the parameter sets in 5G NR and the scaling of the subcarrier spacing can efficiently address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro-coverage deployments with less than 3 GHz FDD / TDD implementations, the subcarrier spacing can occur at 15 kHz for bandwidths (BW) such as 5 MHz, 10 MHz, 20 MHz, etc. For various other outdoor and small-cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing can occur at 30 kHz for 80 MHz / 100 MHz BW. For various other indoor broadband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz for 160 MHz BW. Finally, for various deployments using mmWave components at 28 GHz with TDD for transmission, the subcarrier spacing can occur at 120 kHz for 500 MHz BW.

[0029] The scalable parameter sets of 5G NR facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs allows transmissions to start at symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgments in the same subframe. The self-contained integrated subframe supports communication in unlicensed spectrum or contention-based shared spectrum, and an adaptive uplink / downlink that can be flexibly configured on a per-cell basis to dynamically switch between the uplink and downlink to meet current traffic demands.

[0030] The following further describes various other aspects and features of the present disclosure. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, those of ordinary skill in the art should understand that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of the aspects set forth herein can be used to implement a device or practice a method. In addition, such a device can be implemented or such a method can be practiced using other structures, functionality, or a combination of structures and functionality other than or different from one or more of the aspects set forth herein. For example, a method can be implemented as part of a system, apparatus, device, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. Moreover, one aspect can include at least one element of a claim.

[0031] Deploying NR on unlicensed spectrum is referred to as NR-U (NR Unlicensed). The Federal Communications Commission (FCC) and the European Telecommunications Standards Institute (ETSI) are working on regulating 6 GHz as a new unlicensed band for wireless communication. Adding the 6 GHz band allows hundreds of megahertz (MHz) of bandwidth (BW) to be available for unlicensed band communication. Additionally, NR-U can also be deployed on the 2.4 GHz unlicensed band, which is currently shared by various radio access technologies (RATs) such as IEEE 802.11 wireless local area network (WLAN) or WiFi and / or Licensed-Assisted Access (LAA). Sidelink communication can benefit from the additional bandwidth available in the unlicensed spectrum. However, channel access in a particular unlicensed spectrum can be managed by an official agency. For example, some unlicensed bands may impose restrictions on the power spectral density (PSD) and / or the minimum occupied channel bandwidth (OCB) of transmissions in the unlicensed band. For example, the Unlicensed National Information Infrastructure (UNII) radio bands have a minimum OCB requirement of approximately at least 70%.

[0032] Some sidelink systems can operate on a 20 MHz bandwidth in the unlicensed band, for example, for listen-before-talk (LBT)-based channel access. The BS can configure a sidelink resource pool for sidelink communication on one or more 20 MHz LBT subbands. The sidelink resource pool is typically allocated multiple frequency subchannels within a sidelink bandwidth part (SL-BWP), and the sidelink UE can select sidelink resources (e.g., one or more subchannels in frequency and one or more time slots) from the sidelink resource pool for sidelink communication.

[0033] The deployment of a communication system, such as a 5G New Radio (NR) system, can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)), or one or more units (or one or more components) that perform base station functions can be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

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

[0035] Base station type operations or network designs can consider the aggregation characteristics of base station functionality. For example, a disaggregated base station can be used in an integrated access backhaul (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 referred to as a cloud radio access network (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which can achieve flexibility in network design. The various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0036] Various aspects generally relate to wireless communication and, more specifically, to signaling for dynamic waveform switching. Some aspects more specifically relate to a network element that signals a user equipment (UE) to switch between a first waveform type and a second waveform type for uplink communication. In some examples, the network element may send an indicator to the UE to enable switching between waveform types. When waveform switching is enabled, the network element may send downlink control information (DCI) to the UE indicating which waveform type is used for uplink communication. In some examples, for the first waveform type and the second waveform type, the size of the DCI may be the same size. Accordingly, the UE may use a common DCI size for the first waveform type and the second waveform type to perform blind decoding of the DCI. The DCI may also include scheduling resources for physical uplink shared channel (PUSCH) communication associated with the UE. The UE may use the indicated waveform type to send PUSCH communication to the network element via the scheduling resources.

[0037] Additionally or alternatively, the UE may switch between the first waveform type and the second waveform type on a semi-static basis. In some examples, the network element may send an indicator to the UE to enable switching between waveform types. When waveform switching is enabled, the network element may send non-uplink scheduling DCI and / or medium access control control element (MAC-CE) communication to the UE indicating which waveform type is used for uplink communication. The network element may then use the DCI size associated with the previously indicated waveform type to send uplink scheduling DCI to the UE. The DCI size associated with the first waveform type may be different from the DCI associated with the second waveform type. Accordingly, the UE may perform blind decoding of the DCI based on the DCI size associated with the indicated waveform type. The UE may use the indicated waveform type to send PUSCH communication to the network element via the scheduling resources.

[0038] Certain aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, by implementing dynamic waveform switching in accordance with embodiments of this disclosure, compared to performing blind decoding of a first DCI associated with a first waveform type and a second DCI of a different size associated with a second waveform type, the techniques described may be used to reduce computational resources, memory requirements, latency, and / or power consumption in the UE by performing blind decoding of a DCI having a common size for the first waveform type and the second waveform type. Dynamic waveform switching in accordance with embodiments of this disclosure may increase network coverage and / or network capacity. For example, the UE may switch to using a DFT-s-OFDM waveform to send uplink communication to increase range and coverage. In some examples, the UE may switch to using a CP-OFDM waveform to send uplink communication to increase throughput and / or data rate.

[0039] Figure 1 Wireless communication network 100 is illustrated in accordance with some aspects of the present disclosure. Network 100 includes a plurality of base stations (BSs) 105 and other network entities. A BS 105 can be a station that communicates with a UE 115 and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each BS 105 can provide communication coverage for a specific geographic area. In 3GPP, the term “cell” can refer to this specific geographic coverage area of the BS 105 and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0040] The BS 105 can provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., with a radius of several kilometers) and can allow unrestricted access by UEs having a service subscription with the network provider. A small cell (such as a pico cell) generally will cover a relatively small geographic area and can allow unrestricted access by UEs having a service subscription with the network provider. A small cell (such as a femto cell) generally will also cover a relatively small geographic area (e.g., a home), and in addition to unrestricted access, can also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell can be referred to as a macro BS. A BS for a small cell can be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 the example shown, BSs 105d and 105e can be conventional macro BSs, while BSs 105a to 105c can be macro BSs having the capability of one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BSs 105a to 105c can utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS 105f can be a small cell BS, which can be a home node or a portable access point. A BS 105 can support one or more (e.g., two, three, four, etc.) cells.

[0041] Network 100 can support synchronous operation or asynchronous operation. For synchronous operation, the BSs can have similar frame timings, and transmissions from different BSs can be approximately aligned in time. For asynchronous operation, the BSs can have different frame timings, and transmissions from different BSs may not be aligned in time.

[0042] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, mobile station, subscriber unit, station, etc. UE 115 can be a cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). In another aspect, the UE can be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a - 115d are examples of mobile smart phone type devices accessing the network 100. UE 115 can also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e - 115h are examples of various machines configured for communication accessing the network 100. UE 115i - 115k are examples of vehicles equipped with wireless communication devices configured for communication accessing the network 100. UE 115 can be capable of communicating with any type of BS, whether it is a macro BS, small cell, etc. In Figure 1 it, lightning symbols (e.g., communication links) indicate wireless transmissions between UE 115 and the serving BS 105 (which is the BS designated to serve UE 115 on the downlink (DL) and / or uplink (UL)), desired transmissions between BS 105s, backhaul transmissions between BSs, or sidelink transmissions between UE 115s.

[0043] In operation, BSs 105a - 105c use 3D beamforming and cooperative spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity, to serve UE 115a and 115b. Macro BS 105d can perform backhaul communication with BSs 105a to 105c and small cell BS 105f. Macro BS 105d can also send multicast services subscribed to and received by UE 115c and 115d. Such multicast services can include mobile TV or streaming video, or can include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or Gray alerts.

[0044] BS105 can also communicate with the core network. The core network can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BS105 (e.g., the BS can be an example of an evolved Node B (eNB) or an access node controller (ANC)) can interface with the core network 130 via a backhaul link (e.g., S1, S2, etc.), and can perform radio configuration and scheduling to communicate with the UE 115. In various examples, the BS105 can communicate with each other directly or indirectly (e.g., via the core network) via a backhaul link (e.g., X1, X2, etc.), which can be a wired communication link or a wireless communication link.

[0045] Network 100 can also support mission-critical communication with ultra-reliable and redundant links for mission-critical devices such as UE 115e, which can be a vehicle (e.g., a car, a truck, a bus, an autonomous vehicle, an airplane, a ship, etc.). The redundant communication links with UE 115e can include links from macro BS105d and 105e, and links from small cell BS105f. Other machine type devices (such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device)) can communicate directly with a BS (such as small cell BS105f and macro BS105e) via network 100, or be in a multi-hop configuration by communicating with another user equipment that relays its information to the network (such as UE 115f communicating temperature measurement information to smart meter UE 115g, which is then reported to the network via small cell BS105f). In some aspects, UE 115h can harvest energy from the surrounding environment associated with UE 115h. Network 100 can also provide additional network efficiency via dynamic, low-latency TDD / FDD communication (such as vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication, cellular vehicle-to-everything (C-V2X) communication between UE 115i, 115j, or 115k and other UE 115, and / or vehicle-to-infrastructure (V2I) communication between UE 115i, 115j, or 115k and BS105).

[0046] In some specific implementations, network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are typically also referred to as subcarriers, tones, frequency slots, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0047] In some instances, BS105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) transmissions and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. This communication can have the form of a radio frame. The radio frame can be divided into multiple subframes, e.g., approximately 10. Each subframe can be divided into time slots, e.g., approximately 2. Each time slot can also be divided into mini-slots. In the FDD mode, simultaneous UL transmissions and DL transmissions can occur in different frequency bands. For example, each subframe includes a UL subframe in the UL frequency band and a DL subframe in the DL frequency band. In the TDD mode, UL transmissions and DL transmissions occur in different time periods using the same frequency band. For example, a subset of subframes in the radio frame (e.g., DL subframes) can be used for DL transmissions, and another subset of subframes in the radio frame (e.g., UL subframes) can be used for UL transmissions.

[0048] The DL subframe and the UL subframe can also be divided into several zones. For example, each DL subframe or UL subframe can have predefined zones for the transmission of reference signals, control information, and data. The reference signal is a predetermined signal that facilitates communication between BS105 and UE 115. For example, the reference signal can have a specific pilot pattern or structure, where the pilot tones can span the operable BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS105 can transmit a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) so that UE 115 can estimate the DL channel. Similarly, UE 115 can transmit a sounding reference signal (SRS) so that BS105 can estimate the UL channel. The control information can include resource assignment and protocol control. The data can include protocol data and / or operable data. In some instances, BS105 and UE 115 can communicate using self-contained subframes. The self-contained subframe can include a portion for DL communication and a portion for UL communication. The self-contained subframe can be DL-centric or UL-centric. The DL-centric subframe can include a longer DL communication duration than the UL communication duration. The UL-centric subframe can include a longer UL communication duration than the UL communication duration.

[0049] In some instances, network 100 can be an NR network deployed on licensed spectrum. BS105 can send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS105 can broadcast system information associated with network 100 (e.g., including a master information block (MIB), a remaining minimum system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, BS105 can broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on the physical broadcast channel (PBCH), and can broadcast the RMSI and / or OSI on the physical downlink shared channel (PDSCH).

[0050] In some instances, UE 115 attempting to access network 100 can perform an initial cell search by detecting the PSS from BS105. The PSS can achieve synchronization of the time slot timing and can indicate a physical layer identity value. Then, UE 115 can receive the SSS. The SSS can achieve radio frame synchronization and can provide a cell identity value, which can be combined with the physical layer identity value to identify the cell. The SSS can also achieve detection of the duplex mode and the cyclic prefix length. The PSS and the SSS can be located in the central part of the carrier or at any suitable frequency within the carrier.

[0051] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for the RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to the random access channel (RACH) procedure, paging, control resource sets (CORESETs) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, SRS, and cell barring.

[0052] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS105. For the random access procedure, the UE 115 may send a random access preamble, and the BS105 may respond with a random access response. Upon receiving the random access response, the UE 115 may send a connection request to the BS105 and the BS105 may respond with a connection response (e.g., a contention resolution message).

[0053] After establishing the connection, the UE 115 and the BS105 may enter a normal operation phase in which operable data may be exchanged. For example, the BS105 may schedule the UE 115 for UL communication and / or DL communication. The BS105 may send a UL scheduling grant and / or a DL scheduling grant to the UE 115 via the PDCCH. The BS105 may send a DL communication signal to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send a UL communication signal to the BS105 via the PUSCH and / or the PUCCH according to the UL scheduling grant.

[0054] The network 100 may be designed to enable a wide range of usage scenarios. Although in some examples the network 100 may utilize a monolithic base station, there are a variety of other architectures that may be used to implement aspects of the present disclosure. For example, the BS105 may be separated into a remote radio head (RRH) and a baseband unit (BBU). The BBU may be centralized into a BBU pool and connected to the RRH via a low-latency and high-bandwidth transmission link (such as an optical transmission link). The BBU pool may be a cloud-based resource. In some aspects, the baseband processing is performed on virtualized servers running in a data center rather than being co-located with the BS105. In another example, the base station functionality may be split between a remote unit (RU), a distributed unit (DU), and a central unit (CU). The RU typically performs low physical layer functions, while the DU performs higher layer functions, which may include higher physical layer functions. The CU performs higher RAN functions, such as radio resource control (RRC).

[0055] For simplicity of discussion, this disclosure refers to the methods of this disclosure being performed by a base station or, more generally, by a network entity, while the functionality may be performed by various architectures other than a monolithic base station. In addition to a decomposed base station, aspects of this disclosure may also be performed by a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (near-RT) RAN intelligent controller (RIC), a non-real-time (non-RT) RIC, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc.

[0056] In some aspects, UE 115 may receive an indicator from BS105 indicating a dynamic waveform switch between a first waveform type and a second waveform type. UE 115 may monitor downlink control information (DCI) from a network element based on the indicator, where at least one of the size of the DCI, the size of the bit field of the DCI, or the position of the bit field of the DCI is interpreted based on the indicator.

[0057] In some aspects, UE 115 may receive a first configuration from BS105 indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode. The time position indicates at least one SBFD symbol or slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band. In some aspects, UE 115 may receive a second configuration from BS105 indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0058] Figure 2 A diagram illustrating an exemplary decomposed base station 200 architecture is shown. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units (such as a near-real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both). The CU 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as an F1 interface). The DU 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. The RU 240 may communicate with a corresponding UE 115 via one or more radio frequency (RF) access links. In some specific implementations, a UE 115 may be served simultaneously by multiple RUs 240.

[0059] Each of the units (i.e., CU 210, DU 230, RU 240, and the near RT RIC 225, non-RT RIC 215, and SMO framework 205) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or the associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0060] In some aspects, the CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may utilize an interface that is configured to convey signals to other control functions hosted by the CU 210. The CU 210 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU-UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some embodiments, the CU 210 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 units may communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. As needed, the CU 210 may be implemented to communicate with the DU 230 for network control and signaling.

[0061] The DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, the DU 230 may host one or more of the radio link control (RLC) layer, the media access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation, etc.) at least in part depending on a functional split (such as those defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 230 or with control functions hosted by the CU 210.

[0062] Lower layer functionality may be implemented by one or more RUs 240. In some deployments, the RUs 240 controlled by the DU 230 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.) or both at least in part based on a functional split (such as a lower layer functional split). In such an architecture, the RUs 240 may be implemented to handle over-the-air (OTA) communication with one or more UEs 115. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RUs 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the DU 230 and the CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0063] The SMO framework 205 can be configured to support the RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, and these dedicated physical resources can be managed via operation and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as the Open Cloud (O-Cloud) 290) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include the CU 210, DU 230, RU 240, and the Near RT RIC 225. In some specific implementations, the SMO framework 205 can communicate with the hardware aspects of 4G RAN (such as the Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 can also include a Non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0064] The Non-RT RIC 215 can be configured to include logical 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 225. The Non-RT RIC 215 can be coupled to or communicate with the Near RT RIC 225 (such as via the A1 interface). The Near RT RIC 225 can be configured to include logical functions that enable near-real-time control and optimization of RAN elements and resources through interfaces (such as via the E2 interface) via data collection and actions, and this interface connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB to the Near RT RIC 225.

[0065] In some specific implementations, to generate the AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 225 and can be received from non-network data sources or from network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ an AI / ML model to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or via creating RAN management policies (such as A1 policies).

[0066] In some aspects, the UE 115 may receive an indicator from the RU 240 indicating a dynamic waveform switch between a first waveform type and a second waveform type. The UE 115 may monitor downlink control information (DCI) from the RU 240 based on the indicator, where at least one of the size of the DCI, the size of the bit field of the DCI, or the position of the bit field of the DCI is interpreted based on the indicator.

[0067] In some aspects, the UE 115 may receive a first configuration from the RU 240 indicating the time position and frequency position for a network-side subband full-duplex (SBFD) operation mode. The time position indicates at least one SBFD symbol or slot (SBFD symbol / slot) format, and the frequency position indicates multiple downlink subbands and uplink subbands or multiple uplink subbands and guard bands. In some aspects, the UE 115 may receive a second configuration from the RU 240 indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0068] Figure 3 Illustrated is a wireless communication network 300 operating in a subband full-duplex (SBFD) mode. The wireless communication network 300 may include the wireless communication network 100 or the wireless communication network 200. In some aspects, the network unit 105 may operate in a subband full-duplex mode, and the UEs 115a and 115b operate in a half-duplex mode. When operating in SBFD, the UE 115a and / or 115b may receive a first configuration from the network unit 105 indicating the time position and frequency position for a network-side subband full-duplex (SBFD) operation mode. In this regard, the UE 115a and / or 115b may receive the first configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, UE-specific downlink control information (DCI), and / or UE group common DCI.

[0069] In some aspects, the first configuration may enable the network unit 105 to operate in a full-duplex TDD mode, where the network unit 105 simultaneously transmits communications to the UE 115a via the link 302 and receives communications from the UE 115b via the link 304. The network unit 105 may simultaneously transmit communications to the UE 115b via the link 302 and receive communications from the UE 115a via the link 304. However, when transmitting and receiving communications simultaneously via the links 302 and 304, the network unit 105 may experience self-interference 306 (e.g., interference of the network unit's receiver caused by the transmitter of the network unit 105) and / or clutter interference (e.g., interference of the network unit 105's receiver caused by the reflection of the signal transmitted by the network unit 105). To mitigate these interference effects, the network unit 105 may send a second configuration that changes the frequency position and / or symbol / slot format associated with the subbands to the UE 115a and / or the UE 115b.

[0070] In some aspects, the UE 115a and / or the UE 115b may receive from the network unit 105 a second configuration indicating a change from the configured SBFD symbol / slot format to a different SBFD symbol / slot format. In this regard, the UE 115a and / or the UE 115b may receive the second configuration via at least one of cell common radio resource control (RRC) communications, UE-specific RRC communications, medium access control control (MAC-CE) communications, UE-specific downlink control information (DCI), or UE group common DCI. The UE 115a and / or the UE 115b may apply the second configuration to one or more component carriers indicated in the component carrier list.

[0071] Figure 4A Illustrated are subbands and guard bands in a component carrier according to some aspects of the present disclosure. In some aspects, a UE may receive from a network unit a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode. The time position 412 may indicate at least one SBFD symbol or slot (SBFD symbol / slot) format. In some aspects, the frequency position may indicate multiple downlink subbands and uplink subbands 402 and / or multiple uplink subbands 402 and guard bands 408. In some aspects, a UE may receive from a network unit a second configuration indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0072] In some aspects, the time position 412 may indicate one or more time slot positions, one or more symbol positions, and / or a time period (e.g., a number of milliseconds) during which the sub-band 402 is configured for the SBFD symbol / slot format. An SBFD symbol may be a symbol during which a network element operates in the SBFD mode. An SBFD time slot may be a time slot during which a network element operates in the SBFD mode. When operating in the SBFD mode, a network element may transmit to one or more UEs in the sub-band 402 of a component carrier 410 (e.g., a time division duplex (TDD) carrier), while receiving communications from one or more other UEs in other sub-bands 402 of the component carrier 410. Although Figure 4A the example of

[0073] shows one component carrier 410, the present disclosure is not limited thereto, and a network element may operate in the SBFD mode via multiple component carriers 410.

[0074] In some aspects, the downlink subbands 402, uplink subbands 402, and flexible subbands 402 do not overlap with each other. In this regard, the downlink subbands 402, uplink subbands 402, and flexible subbands 402 can be separated from each other by guard bands 408. The first configuration can indicate the guard bands 408 associated with the frequency positions of the subbands 402. The guard bands 408 can be frequencies at which the network unit and / or the UE suppress transmissions. The guard bands 408 can be positioned adjacent to the upper end and / or lower end of the subbands 402. For example, the guard band 408a can be positioned adjacent to the lower end of the subband 402a and adjacent to the upper end of the subband 402b. The guard band 408b can be positioned adjacent to the lower end of the subband 402b and adjacent to the upper end of the subband 402c. In some aspects, the size (e.g., frequency range) of the guard bands 408 can be based on the frequencies associated with the subbands 402, the frequency range of the subbands 402 (e.g., the number of subbands), the component carrier frequency range, or other suitable parameters.

[0075] In some aspects, the UE can apply the first configuration to one or more component carriers 410. For example, the UE can receive a list of component carriers 410 from a network unit to which the UE can apply the first configuration. In some aspects, multiple downlink subbands and uplink subbands 402 or multiple uplink subbands 402 and guard bands 408 can span multiple time division duplex (TDD) carriers, where each downlink subband 402 and / or uplink subband 402 is a component carrier 410.

[0076] In some aspects, the SBFD symbols / slots can be configured on legacy downlink symbols / slots, legacy uplink symbols / slots, and / or legacy flexible symbols / slots and are regarded as a fixed SBFD configuration having multiple downlink subbands 402, uplink subbands 402, and / or flexible subbands 402. For example, the UE can receive an initial RRC configuration (e.g., a legacy configuration) before receiving the first configuration. The legacy configuration can configure all subbands 402 of the component carrier 410 as legacy downlink symbols / slots, legacy uplink symbols / slots, or legacy flexible symbols / slots. The flexible symbols / slots can be configured for DL communication and / or UL communication. The initial RRC (e.g., legacy) configuration can configure all subbands in the subbands 402 of the component carrier 410 as a single type of communication (e.g., all subbands 402 configured for UL communication, DL communication, or flexible communication).

[0077] In some aspects, the second configuration may indicate a change (e.g., an update) from an SBFD symbol / slot format to a different SBFD symbol / slot format. The second configuration may indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial RRC configuration. For example, the change may be from an SBFD D / U / D format to the initial downlink format. The change may be from an SBFD F / U / F format to the initial flexible format. The change may be from an SBFD U / D / U format to the initial uplink format.

[0078] Additionally or alternatively, the second configuration may indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial slot indicator (SFI) configuration. For example, the change may be from an SBFD D / U / D format to the downlink format of the SFI configuration. The change may be from an SBFD F / U / F format to the flexible format of the SFI configuration. The change may be from an SBFD U / D / U format to the uplink format of the SFI configuration.

[0079] Additionally or alternatively, the second configuration may update (e.g., overwrite) the frequency position and / or the SBFD symbol / slot format for some or all of the subbands in subband 402. For example, the first configuration may configure subband 402 for an SBFD symbol / slot format (e.g., uplink, downlink, and / or flexible communication), while the second configuration changes the frequency position and / or the SBFD symbol / slot format. In some aspects, the frequency position may remain the same in the second configuration, but the SBFD symbol / slot format may change. In other words, the second configuration may change the communication type for the same subband 402 configured by the first configuration. In some aspects, the second configuration may change the frequency position of subband 402. The second configuration may increase or decrease the number (e.g., the bandwidth) of subbands 402 associated with uplink, downlink, and / or flexible communication.

[0080] In some aspects, the second configuration may change the time position 412 (e.g., the time resource) associated with the SBFD symbol / slot format. In this regard, the second configuration may change (e.g., update) one or more slot positions, one or more symbol positions, and / or the time period (e.g., a number of milliseconds) associated with the SBFD symbol / slot format.

[0081] In some aspects, the second configuration may change the guard band 408 associated with the sub-band 402. The guard band 408 may be a frequency at which a network element and / or a UE refrains from transmitting. The guard band 408 may be positioned adjacent to the upper end and / or the lower end of the sub-band 402. The second configuration may change the size of the guard band 408 based on a change in the frequency position and / or a change in the SBFD symbol / slot format.

[0082] In some aspects, the second configuration may indicate a change from an SBFD symbol / slot to a different SBFD symbol / slot format based on a buffer status report (BSR) associated with the UE. In this regard, the UE may send a buffer status report (BSR) indicating the amount of data (e.g., the number of transport blocks) that the UE has been scheduled for transmission to the network element to the network element. The network element may determine the second configuration at least in part based on the BSR. For example, if the BSR indicates that the UE has an amount of data that exceeds the resource capacity indicated in the first configuration, the network element may send the second configuration for increasing the UL communication resources to the UE. For example, the second configuration may increase the number of frequency sub-bands 402, the number of time slots, and / or the number of symbols allocated to the UE for UL communication.

[0083] Figure 4B Illustrated are a sub-band and a guard band in a component carrier according to some aspects of the present disclosure. In some aspects, a UE may receive a first configuration from a network element indicating a time position and a frequency position for a network-side sub-band full-duplex (SBFD) operation mode. The time position 412 may indicate at least one SBFD symbol or time slot (SBFD symbol / slot) format. In some aspects, the frequency position may indicate a plurality of downlink sub-bands and uplink sub-bands 402 or a plurality of uplink sub-bands 402 and a guard band 408. In some aspects, the UE may receive a second configuration from the network element indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0084] In some aspects, the time position 412 may indicate one or more time slot positions, one or more symbol positions, and / or a time period (e.g., a number of milliseconds) during which the sub-band 402 is configured for an SBFD symbol / slot format. The SBFD symbol may be a symbol during which the network element operates in the SBFD mode. The SBFD time slot may be a time slot during which the network element operates in the SBFD mode. When operating in the SBFD mode, the network element may transmit to one or more UEs in the sub-band 402 of the component carrier 410 (e.g., a time division duplex (TDD) carrier) while receiving communication from one or more other UEs in other sub-bands 402 of the component carrier 410. Although Figure 4AThe example shows a component carrier 410, but the present disclosure is not limited thereto, and the network unit may operate in the SBFD mode through multiple component carriers 410.

[0085] Figure 4B Shows a non - limiting example in which the component carrier 410 is divided into two sub - bands 402a and 402b. The sub - bands 402a and 402b may be separated by a guard band 408. The SBFD symbol / slot format associated with the sub - bands 402a and 402b may include any combination of an uplink format, a downlink format, or a flexible format. For example, the SBFD symbol / slot format may include a U / D format indicating uplink communication in the sub - band 402a of the component carrier 410 and downlink communication in the sub - band 402b. Additionally or alternatively, the SBFD symbol / slot format may include a D / U format indicating downlink communication in the sub - band 402a of the component carrier 410 and uplink communication in the sub - band 402b.

[0086] Figure 5 Is a flowchart of a communication method 500 according to some aspects of the present disclosure. Aspects of the method 500 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable components for performing these actions. For example, a wireless communication device, such as BS105, RU 240, DU 230, CU 210, and / or network unit 700, may utilize one or more components, such as a processor 702, a memory 704, a sub - band full - duplex module 708, a transceiver 710, a modem 712, and one or more antennas 716, to perform aspects of the method 500. For example, a wireless communication device, such as UE 115 or UE 600, may utilize one or more components, such as a processor 602, a memory 604, a sub - band full - duplex module 608, a transceiver 610, a modem 612, and one or more antennas 616, to perform aspects of the method 500. The method 500 may employ mechanisms and reference Figure 3 To the aspects and actions described in FIGS. 4. As illustrated, the method 500 includes a plurality of enumerated actions, but the method 500 may include additional actions before, after, and between these enumerated actions. In some aspects, one or more of these enumerated actions may be omitted or performed in a different order.

[0087] At action 502, network element 105 may send an initial configuration (e.g., a legacy configuration) indicating the symbol / slot format for one or more component carriers to UE 115. At this point, network element 105 may send the initial configuration via at least one of cell common radio resource control (RRC) communication, UE dedicated RRC communication, medium access control control (MAC-CE) communication, UE dedicated downlink control information (DCI), and / or UE group common DCI. The initial legacy configuration may configure all subbands of a component carrier as legacy downlink symbols / slots, legacy uplink symbols / slots, or legacy flexible symbols / slots. Flexible symbols / slots may be configured for DL communication and / or UL communication. The initial RRC (e.g., legacy) configuration may configure all subbands in a subband of a frequency band as a single type of communication (e.g., all subbands configured for UL communication, DL communication, or flexible communication).

[0088] At action 504, the UE may apply the initial legacy configuration to one or more component carriers.

[0089] At action 506, the UE may communicate with network element 105. For example, if a component carrier is configured for downlink communication at action 502, network element 105 may send PDSCH communication to UE 115. If a component carrier is configured for uplink communication at action 502, UE 115 may send PUSCH communication to network element 105.

[0090] At action 508, network element 105 may send a first configuration indicating the symbol / slot format to UE 115. The first configuration may indicate a time position that indicates one or more slot positions, one or more symbol positions, and / or a time period (e.g., a number of milliseconds) during which subbands are configured for the SBFD symbol / slot format. SBFD symbols may be symbols during which the network element operates in the SBFD mode. SBFD slots may be slots during which the network element operates in the SBFD mode. When operating in the SBFD mode, network element 105 may transmit to one or more UEs 115 in subbands of a component carrier (e.g., a time division duplex (TDD) carrier) while receiving communication from one or more other UEs 115 in other subbands of the component carrier.

[0091] At action 510, UE 115 may apply the first configuration to the time position and frequency position indicated by the first configuration received at action 508.

[0092] At action 512, network element 105 may send a second configuration indicating the symbol / slot format to UE 115. In some aspects, UE 115 may receive the second configuration that covers or partially covers the first configuration. For example, the second configuration may change the SBFD symbol / slot format (e.g., time slot, symbol, sub-band) of the first configuration. Additionally or alternatively, the second configuration may change the SBFD symbol / slot format to revert (e.g., fallback) to an initial (e.g., legacy) RRC configuration.

[0093] At action 514, UE 115 may send a HARQ ACK message confirming receipt of the second configuration to network element 105.

[0094] At action 516, UE 115 may apply the second configuration. In some aspects, UE 115 may apply the second configuration after a certain period of time after receiving the second configuration. In some aspects, the second configuration may indicate when UE 115 should apply the second configuration. In some aspects, the period of time may be pre-configured in UE 115. The period of time may include the number of symbols, the number of time slots, the number of milliseconds, or other suitable periods of time before UE 115 applies a third configuration. In some aspects, the period of time may be based on the subcarrier spacing (SCS) associated with a sub-band.

[0095] In some aspects, UE 115 may apply the second configuration after a certain period of time after sending the HARQ ACK to network element 105 at action 514. For example, UE 115 may apply the second configuration after a certain number of symbols, a certain number of time slots, a certain number of milliseconds, or other suitable periods of time after sending the HARQ ACK.

[0096] At action 516, UE 115 may cancel certain communications. In some aspects, UE 115 may cancel one or more scheduled communications based on the second configuration. For example, UE 115 may cancel one or more scheduled uplink communications based on the second configuration that changes one or more SBFD symbol / slot formats to a DL symbol / slot format or a flexible symbol / slot format. Additionally or alternatively, UE 115 may cancel one or more scheduled downlink communications based on the second configuration that changes one or more SBFD symbol / slot formats to a UL symbol / slot format or a flexible symbol / slot format.

[0097] In some aspects, the UE 115 may cancel one or more scheduled uplink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy downlink symbol / slot format or a legacy flexible symbol / slot format. Additionally or alternatively, the UE 115 may cancel one or more scheduled downlink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy uplink symbol / slot format or a legacy flexible symbol / slot format.

[0098] In some aspects, the UE 115 may cancel one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications based on a second configuration indicating a change to a legacy downlink symbol / slot format. The UE 115 may receive the PDCCH in one or more symbols in a CORESET configured for monitoring by the UE 115.

[0099] At operation 520, the network element 105 may optionally send a third configuration to the UE 115 based on a second configuration indicating a change to a legacy flexible symbol / slot format, the third configuration including a parameter set associated with DL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.) and / or a parameter set associated with UL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.). The UE 115 may receive PDSCH-SPS communications, CSI-RS, and PDCCH communications across downlink subbands without rate matching or puncturing. The UE 115 may transmit CG, SRS, and / or PUCCH communications across uplink subchannels using the parameter set in the third configuration without adjusting the hopping offset.

[0100] Figure 6 is a block diagram of an exemplary UE 600 according to some aspects of the present disclosure. The UE 600 may be the UE 115 in the network 100 or 200 as discussed above. As shown, the UE 600 may include a processor 602, a memory 604, a subband full-duplex module 608, a transceiver 610 including a modem subsystem 612 and a radio frequency (RF) unit 614, and one or more antennas 616. These elements may be coupled to each other, for example, via one or more buses and communicate directly or indirectly with each other.

[0101] Processor 602 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. Processor 602 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0102] Memory 604 may include cache memory (e.g., cache memory of processor 602), random access memory (RAM), magnetoresistive RAM (MRAM), read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, solid state memory devices, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some instances, memory 604 includes non-transitory computer-readable media. Memory 604 may store instructions 606. Instructions 606 may include instructions that, when executed by processor 602, cause processor 602 to perform the operations described herein with reference to UE 115 in connection with aspects of the present disclosure (e.g., Figures 3 to 6 aspects). Instructions 606 may also be referred to as code. The terms "instructions" and "code" should be construed broadly to include any type of computer-readable statement. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements.

[0103] The sub-band full-duplex module 608 may be implemented via hardware, software, or a combination thereof. For example, the sub-band full-duplex module 608 may be implemented as a processor, circuitry, and / or instructions 606 stored in memory 604 and executed by processor 602. In some aspects, the sub-band full-duplex module 608 may implement Figures 3 to 5 aspects. For example, the sub-band full-duplex module 608 may receive a first configuration from a network unit (e.g., network unit 700, base station 105, CU 210, DU 230, or RU 240) indicating the time location and frequency location for a network-side sub-band full-duplex (SBFD) operation mode. The time location may indicate at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency location may indicate multiple downlink sub-bands and uplink sub-bands or multiple uplink sub-bands and guard bands. The UE may receive a second configuration from the network unit indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0104] As shown, transceiver 610 may include a modem subsystem 612 and an RF unit 614. Transceiver 610 may be configured to communicate bidirectionally with other devices (such as BS105 and / or UE 115). Modem subsystem 612 may be configured to modulate and / or encode data from memory 604 according to a modulation and coding scheme (MCS) (e.g., low density parity check (LDPC) coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). RF unit 614 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data of a transmission from modem subsystem 612 (for an outbound transmission) or originating from another source (such as UE 115 or BS105). RF unit 614 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 610, modem subsystem 612 and RF unit 614 may be separate devices coupled together to enable UE 600 to communicate with other devices.

[0105] RF unit 614 may provide the modulated and / or processed data, such as data packets (or more generally, data messages that may include one or more data packets and other information), to antenna 616 for transmission to one or more other devices. Antenna 616 may also receive data messages transmitted from other devices. Antenna 616 may provide the received data messages for processing and / or demodulation at transceiver 610. Antenna 616 may include multiple antennas with similar or different designs to maintain multiple transmission links. RF unit 614 may configure antenna 616.

[0106] In some instances, UE 600 may include multiple transceivers 610 implementing different RATs (e.g., NR and LTE). In some instances, UE 600 may include a single transceiver 610 implementing multiple RATs (e.g., NR and LTE). In some instances, transceiver 610 may include various components, and different combinations of the components may implement the RAT.

[0107] Figure 7 is a block diagram of an exemplary network unit 700 according to some aspects of the present disclosure. Network unit 700 may be a BS105, CU 210, DU 230, or RU 240 as discussed above. As shown, network unit 700 may include a processor 702, a memory 704, a subband full duplex module 708, a transceiver 710 including a modem subsystem 712 and an RF unit 714, and one or more antennas 716. These elements may be coupled to each other via one or more buses and communicate with each other directly or indirectly, for example.

[0108] The processor 702 can have various features as a particular type of processor. For example, these features can include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 702 can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0109] The memory 704 can include cache memory (e.g., the cache memory of the processor 702), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some instances, the memory 704 can include non-transitory computer-readable media. The memory 704 can store instructions 706. The instructions 706 can include instructions that, when executed by the processor 702, cause the processor 702 to perform the operations described herein (e.g., Figures 3 to 5 aspects thereof). The instructions 706 can also be referred to as code, which can be broadly interpreted to include any type of computer-readable statement.

[0110] The subband full-duplex module 708 can be implemented via hardware, software, or a combination thereof. For example, the subband full-duplex module 708 can be implemented as a processor, a circuit, and / or instructions 706 stored in the memory 704 and executed by the processor 702.

[0111] In some aspects, the subband full-duplex module 708 can implement Figures 3 to 5 aspects thereof. For example, the subband full-duplex module 708 can send a first configuration to a UE (e.g., UE 115 or UE 600) indicating the time location and frequency location for a network-side subband full-duplex (SBFD) operation mode. The time location can indicate at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency location can indicate multiple downlink subbands and uplink subbands or multiple uplink subbands and guard bands. The network unit can send a second configuration to the UE indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

[0112] Additionally or alternatively, the subband full-duplex module 708 can be implemented in any combination of hardware and software, and in some specific implementations can involve, for example, the processor 702, the memory 704, the instructions 706, the transceiver 710, and / or the modem 712.

[0113] As shown, transceiver 710 may include a modem subsystem 712 and an RF unit 714. Transceiver 710 may be configured to communicate bidirectionally with other devices (such as UE 115 and / or UE 600). Modem subsystem 712 may be configured to modulate and / or encode data according to an MCS (such as an LDPC decoding scheme, a turbo decoding scheme, a convolutional decoding scheme, a digital beamforming scheme, etc.). RF unit 714 may be configured to process (such as perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data of a transmission from modem subsystem 712 (for an outbound transmission) or from another source (such as UE 115 or UE 600). RF unit 714 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in transceiver 710, modem subsystem 712 and / or RF unit 714 may be separate devices coupled together at network unit 700 such that network unit 700 can communicate with other devices.

[0114] RF unit 714 may provide the modulated and / or processed data, such as data packets (or more generally, data messages that may include one or more data packets and other information), to antenna 716 for transmission to one or more other devices. For example, in accordance with aspects of the present disclosure, this may include indicating the configuration of multiple sub-slots within a time slot. Antenna 716 may also receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at transceiver 710. Antenna 716 may include multiple antennas having similar or different designs in order to maintain multiple transmission links.

[0115] In some instances, network unit 700 may include multiple transceivers 710 that implement different RATs (such as NR and LTE). In some instances, network unit 700 may include a single transceiver 710 that implements multiple RATs (such as NR and LTE). In some instances, transceiver 710 may include various components, and different combinations of the components may implement RATs.

[0116] Figure 8is a flowchart of a communication method 800 according to some aspects of the present disclosure. Aspects of method 800 may be performed by a computing device of a wireless communication device, such as, for example, a processor, processing circuitry, and / or other suitable components, or other suitable components for performing these actions. For example, a wireless communication device, such as UE 115 or UE 600, may utilize one or more components, such as processor 602, memory 604, subband configuration module 608, transceiver 610, modem 612, and one or more antennas 616, to perform aspects of method 800. Method 800 may employ mechanisms similar to those in networks 100 and 200 and aspects and actions regarding Figures 3 to 5 as described. As illustrated, method 800 includes a plurality of recited actions, but method 800 may include additional actions before, after, and between these recited actions. In some aspects, one or more of these recited actions may be omitted or performed in a different order.

[0117] At action 810, method 800 includes a UE (e.g., UE 115 or UE 600) receiving a first configuration from a network element (e.g., network element 700, BS 105, RU 240, DU 230, and / or CU 210) indicating a time location and a frequency location for a network-side subband full-duplex (SBFD) operation mode. In this regard, the UE may receive the first configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control element (MAC-CE) communication, UE-specific downlink control information (DCI), and / or UE group common DCI.

[0118] In some aspects, the time location may indicate one or more slot locations, one or more symbol locations, and / or a time period (e.g., a number of milliseconds) during which a subband is configured for an SBFD symbol / slot format. An SBFD symbol may be a symbol during which the network element operates in the SBFD mode. An SBFD slot may be a slot during which the network element operates in the SBFD mode. When operating in the SBFD mode, the network element may transmit to one or more UEs in a subband of a component carrier (e.g., a time-division duplex (TDD) carrier) while receiving communication from one or more other UEs in other subbands of the component carrier. In some aspects, the network element may operate in the SBFD mode via a plurality of component carriers.

[0119] In some aspects, the frequency positions may indicate multiple downlink subbands, uplink subbands, and / or flexible subbands. The frequency positions may indicate any combination of downlink subbands, uplink subbands, and / or flexible subbands. For example, the frequency positions may include a downlink / uplink / downlink (D / U / D) format indicating: a downlink subband in a higher portion (e.g., an edge portion) of a component carrier, an uplink subband within a middle portion of the component carrier, and a downlink subband in a lower portion (e.g., an edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include a flexible / uplink / flexible (F / U / F) format indicating: a flexible subband in a higher portion (e.g., an edge portion) of a component carrier, an uplink subband within a middle portion of the component carrier, and a flexible subband in a lower portion (e.g., an edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include an uplink / downlink / uplink (U / D / U) format indicating: an uplink subband in a higher portion (e.g., an edge portion) of a component carrier, a downlink subband within a middle portion of the component carrier, and an uplink subband in a lower portion (e.g., an edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include a U / D format indicating an uplink subband in a higher portion of a component carrier and a downlink subband in a lower portion of the component carrier. Additionally or alternatively, the frequency positions may include a D / U format indicating a downlink subband in a higher portion of a component carrier and an uplink subband in a lower portion of the component carrier.

[0120] In some aspects, the downlink subbands, uplink subbands, and flexible subbands do not overlap with each other. In this regard, the downlink subbands, uplink subbands, and flexible subbands may be separated from each other by guard bands. A first configuration may indicate a guard band associated with the frequency position of a subband. The guard band may be a frequency at which a network unit and / or UE refrains from transmitting. The guard band may be positioned adjacent to the upper end and / or lower end of the subband. In some aspects, the size of the guard band may be based on the frequency associated with the subband, the frequency range of the subband (e.g., the number of subbands), or other suitable parameters.

[0121] In some aspects, a UE may apply the first configuration to one or more component carriers. For example, the UE may receive a list of component carriers from a network unit to which the UE may apply the first configuration. In some aspects, multiple downlink subbands and uplink subbands or multiple uplink subbands and guard bands span multiple time division duplex (TDD) carriers, where each downlink subband and / or uplink subband is a component carrier.

[0122] In some aspects, at least one SBFD symbol / slot can be configured to be on legacy downlink symbols / slots, legacy uplink symbols / slots, and / or legacy flexible symbols / slots, and is considered to have a fixed SBFD configuration with multiple downlink subbands, uplink subbands, and / or flexible subbands. For example, a UE can receive an initial RRC configuration (e.g., a legacy configuration) before receiving the first configuration. The legacy configuration can configure all subbands of a component carrier as legacy downlink symbols / slots, legacy uplink symbols / slots, or legacy flexible symbols / slots. The flexible symbols / slots can be configured for DL communication and / or UL communication. The initial RRC (e.g., legacy) configuration can configure all subbands in the subbands of a frequency band as a single type of communication (e.g., all subbands configured for UL communication, DL communication, or flexible communication).

[0123] At action 820, method 800 includes the UE receiving, from a network element, a second configuration indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format. At this point, the UE can receive the second configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, UE-specific downlink control information (DCI), or UE group common DCI. The UE can apply the second configuration to one or more component carriers indicated in a component carrier list.

[0124] In some aspects, the first configuration can enable a network element to operate in a full-duplex TDD mode, where the network element simultaneously sends communication to some UEs and receives communication from other UEs. However, when transmitting and receiving simultaneously, the network element may experience self-interference (e.g., interference from the network element's transmitter to the network element's receiver) and / or clutter interference (e.g., interference from reflections of signals transmitted by the network element to the network element's receiver). To mitigate these interference effects, the network element can send a second configuration that changes the frequency position and / or symbol / slot format associated with a subband to the UE.

[0125] In some aspects, the second configuration can indicate a change (e.g., an update) from an SBFD symbol / slot format to a different SBFD symbol / slot format. The second configuration can indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial RRC configuration. For example, the change can be from an SBFDD / U / D format to the initial downlink format. The change can be from an SBFD F / U / F format to the initial flexible format. The change can be from an SBFD U / D / U format to the initial uplink format.

[0126] Additionally or alternatively, the second configuration may indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial slot indicator (SFI) configuration. For example, the change may be from the SBFD D / U / D format to the downlink format of the SFI configuration. The change may be from the SBFD F / U / F format to the flexible format of the SFI configuration. The change may be from the SBFD U / D / U format to the uplink format of the SFI configuration.

[0127] Additionally or alternatively, the second configuration may update (e.g., overwrite) the frequency positions and / or the SBFD symbol / slot formats for some or all of the subbands in a subband. For example, the first configuration may configure the subbands for the SBFD symbol / slot formats (e.g., uplink, downlink, and / or flexible communication), while the second configuration changes the frequency positions and / or the SBFD symbol / slot formats. In some aspects, the frequency positions may remain the same in the second configuration, but the SBFD symbol / slot formats may change. In other words, the second configuration may change the communication type for the same subbands configured by the first configuration. In some aspects, the second configuration may change the frequency positions of the subbands. The second configuration may increase or decrease the number (e.g., bandwidth) of subbands associated with uplink, downlink, and / or flexible communication.

[0128] In some aspects, the second configuration may change the time resources associated with the SBFD symbol / slot format. In this regard, the second configuration may change (e.g., update) one or more slot positions, one or more symbol positions, and / or the time period (e.g., several milliseconds) associated with the SBFD symbol / slot format.

[0129] In some aspects, the second configuration may change the guard bands associated with the subbands. The guard bands may be frequencies that a network element and / or a UE refrains from transmitting in. The guard bands may be positioned adjacent to the upper end and / or the lower end of the subbands. The second configuration may change the size of the guard bands based on the change in the frequency positions and / or the change in the SBFD symbol / slot formats.

[0130] In some aspects, the second configuration may indicate a change from an SBFD symbol / slot to a different SBFD symbol / slot format based on a buffer status report (BSR) associated with the UE. In this regard, the UE may send a buffer status report (BSR) indicating the amount of data (e.g., number of transport blocks) that the UE has been scheduled to transmit to the network element to the network element. The network element may determine the second configuration at least in part based on the BSR. For example, if the BSR indicates that the UE has an amount of data exceeding the resource capacity indicated in the first configuration, the network element may send a second configuration increasing the UL communication resources to the UE. For example, the second configuration may increase the number of frequency subbands, number of time slots, and / or number of symbols allocated to the UE for UL communication.

[0131] In some aspects, the UE may apply the second configuration after a certain period of time after receiving the second configuration. In some aspects, the second configuration may indicate when the UE should apply the second configuration. In some aspects, the period of time may be preconfigured in the UE. The period of time may include the number of symbols, number of time slots, number of milliseconds, or other suitable period of time before the UE applies a third configuration. In some aspects, the period of time may be based on the subcarrier spacing (SCS) associated with the subband.

[0132] In some aspects, the UE may send a HARQ ACK communication acknowledging receipt of the second configuration to the network element. The UE may apply the second configuration after a certain period of time after sending the HARQ ACK to the network element. For example, the UE may apply the second configuration after a certain number of symbols, a certain number of time slots, a certain number of milliseconds, or other suitable period of time after sending the HARQ ACK.

[0133] In some aspects, the UE may receive a second configuration that overlays or partially overlays the first configuration. For example, the second configuration may change the SBFD symbol / slot format (e.g., time slot, symbol, subband) of the first configuration. Additionally or alternatively, the second configuration may change the SBFD symbol / slot format to revert (e.g., fallback) to an initial (e.g., legacy) RRC configuration.

[0134] In some aspects, the UE may cancel one or more scheduled communications based on the second configuration. For example, the UE may cancel one or more scheduled uplink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a DL symbol / slot format or a flexible symbol / slot format. Additionally or alternatively, the UE may cancel one or more scheduled downlink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a UL symbol / slot format or a flexible symbol / slot format.

[0135] In some aspects, the UE may cancel one or more scheduled uplink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy downlink symbol / slot format or a legacy flexible symbol / slot format. Additionally or alternatively, the UE may cancel one or more scheduled downlink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy uplink symbol / slot format or a legacy flexible symbol / slot format.

[0136] In some aspects, the UE may cancel one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications based on a second configuration indicating a change to a legacy downlink symbol / slot format. The UE may receive the PDCCH in one or more symbols in a CORESET configured for UE monitoring.

[0137] In some aspects, the UE may receive a third configuration from a network element based on a second configuration indicating a change to a legacy flexible symbol / slot format, the third configuration including a set of parameters associated with DL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.) and / or a set of parameters associated with UL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.). The UE may receive PDSCH-SPS communications, CSI-RS, and PDCCH communications across downlink subbands without rate matching or puncturing. The UE may transmit CG, SRS, and / or PUCCH communications across uplink subchannels using the set of parameters in the third configuration without adjusting the hopping offset.

[0138] In some aspects, the UE may monitor the second configuration in group common downlink control information (DCI) or medium access control control (MAC-CE) communications. However, the UE may not receive the second configuration (e.g., decode the second configuration) in group common DCI or MAC-CE communications. The UE may reserve resources (e.g., symbols / slots) associated with flexible SBFD symbols / slots in response to not receiving the second configuration (e.g., not successfully decoding the second configuration). The UE may monitor the PDCCH in the reserved resources and receive PDSCH communications and / or channel state information reference signal (CSI-RS) when indicated by a dynamic grant. However, the UE may cancel periodic downlink communications (e.g., SPS, CSI-RS) and / or periodic uplink communications (e.g., SRS, PUCCH, PUSCH) in response to not receiving the second configuration.

[0139] Figure 9is a flowchart of a communication method 900 according to some aspects of the present disclosure. Aspects of method 900 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable components for performing these actions. For example, a wireless communication device, such as a network unit (e.g., network unit 700, BS105, RU 240, DU 230, and / or CU 210), may utilize one or more components, such as processor 702, memory 704, subband full-duplex module 708, transceiver 710, modem 712, and one or more antennas 716, to perform aspects of method 900. Method 900 may employ mechanisms similar to those in networks 100 and 200 and aspects and actions regarding Figures 3 to 5 as described. As illustrated, method 800 includes a plurality of recited actions, but method 800 may include additional actions before, after, and between these recited actions. In some aspects, one or more of these recited actions may be omitted or performed in a different order.

[0140] At action 910, method 900 includes a network unit (e.g., network unit 700, BS105, RU 240, DU 230, and / or CU 210) sending a first configuration indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode to a UE (e.g., UE 115 or UE 600). In this regard, the network unit may send the first configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, UE-specific downlink control information (DCI), and / or UE group common DCI.

[0141] In some aspects, the time position may indicate one or more slot positions, one or more symbol positions, and / or a time period (e.g., a number of milliseconds), wherein a subband is configured for an SBFD symbol / slot format. An SBFD symbol may be a symbol during which the network unit operates in the SBFD mode. An SBFD slot may be a slot during which the network unit operates in the SBFD mode. When operating in the SBFD mode, the network unit may transmit to one or more UEs in a subband of a component carrier (e.g., a time division duplex (TDD) carrier) while receiving communication from one or more other UEs in other subbands of the component carrier. In some aspects, the network unit may operate in the SBFD mode via multiple component carriers.

[0142] In some aspects, the frequency positions may indicate multiple downlink subbands, uplink subbands, and / or flexible subbands. The frequency positions may indicate any combination of downlink subbands, uplink subbands, and / or flexible subbands. For example, the frequency positions may include a downlink / uplink / downlink (D / U / D) format indicating: a downlink subband in a higher portion (e.g., edge portion) of a component carrier, an uplink subband within a middle portion of the component carrier, and a downlink subband in a lower portion (e.g., edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include a flexible / uplink / flexible (F / U / F) format indicating: a flexible subband in a higher portion (e.g., edge portion) of a component carrier, an uplink subband within a middle portion of the component carrier, and a flexible subband in a lower portion (e.g., edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include an uplink / downlink / uplink (U / D / U) format indicating: an uplink subband in a higher portion (e.g., edge portion) of a component carrier, a downlink subband within a middle portion of the component carrier, and an uplink subband in a lower portion (e.g., edge portion) of the component carrier. Additionally or alternatively, the frequency positions may include a U / D format indicating an uplink subband in a higher portion of a component carrier and a downlink subband in a lower portion of the component carrier. Additionally or alternatively, the frequency positions may include a D / U format indicating a downlink subband in a higher portion of a component carrier and an uplink subband in a lower portion of the component carrier.

[0143] In some aspects, the downlink subbands, uplink subbands, and flexible subbands do not overlap with each other. In this regard, the downlink subbands, uplink subbands, and flexible subbands may be separated from each other by guard bands. A first configuration may indicate a guard band associated with the frequency position of a subband. The guard band may be a frequency at which a network element and / or UE refrains from transmitting. The guard band may be positioned adjacent to the upper end and / or lower end of the subband. In some aspects, the size of the guard band may be based on the frequency associated with the subband, the frequency range of the subband (e.g., the number of subbands), or other suitable parameters.

[0144] In some aspects, a UE may apply the first configuration to one or more component carriers. For example, a UE may receive a list of component carriers from a network element to which the UE may apply the first configuration. In some aspects, multiple downlink subbands and uplink subbands or multiple uplink subbands and guard bands span multiple time division duplex (TDD) carriers, where each downlink subband and / or uplink subband is a component carrier.

[0145] In some aspects, at least one SBFD symbol / slot may be configured to be on a legacy downlink symbol / slot, a legacy uplink symbol / slot, and / or a legacy flexible symbol / slot, and is considered to have a fixed SBFD configuration with multiple downlink subbands, uplink subbands, and / or flexible subbands. For example, a network element may send an initial RRC configuration (e.g., a legacy configuration) to a UE before sending a first configuration. The legacy configuration may configure all subbands of a component carrier as a legacy downlink symbol / slot, a legacy uplink symbol / slot, or a legacy flexible symbol / slot. The flexible symbol / slot may be configured for DL communication and / or UL communication. The initial RRC (e.g., legacy) configuration may configure all subbands in a subband of a frequency band as a single type of communication (e.g., all subbands configured for UL communication, DL communication, or flexible communication).

[0146] At action 920, method 900 includes a network element sending a second configuration indicating a change from at least one SBFD symbol / slot format to a different SBFD symbol / slot format to a UE. At this point, the network element may send the second configuration via at least one of cell common radio resource control (RRC) communication, UE dedicated RRC communication, medium access control control (MAC-CE) communication, UE dedicated downlink control information (DCI), or UE group common DCI. The UE may apply the second configuration to one or more component carriers indicated in a component carrier list.

[0147] In some aspects, the first configuration may enable a network element to operate in a full-duplex TDD mode, where the network element simultaneously sends communication to some UEs and receives communication from other UEs. However, when sending and receiving simultaneously, the network element may experience self-interference (e.g., interference from the network element's transmitter to the network element's receiver) and / or clutter interference (e.g., interference from reflections of signals sent by the network element to the network element's receiver). To mitigate these interference effects, the network element may send a second configuration that changes the frequency position and / or symbol / slot format associated with a subband to the UE.

[0148] In some aspects, the second configuration may indicate a change (e.g., an update) from an SBFD symbol / slot format to a different SBFD symbol / slot format. Additionally or alternatively, the second configuration may indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial RRC configuration. For example, the change may be from an SBFD D / U / D format to the initial downlink format. The change may be from an SBFD F / U / F format to the initial flexible format. The change may be from an SBFD U / D / U format to the initial uplink format.

[0149] Additionally or alternatively, the second configuration may indicate the change as a fallback from any SBFD symbol / slot format (e.g., uplink, downlink, or flexible) to the symbol / slot format of the initial slot indicator (SFI) configuration. For example, the change may be from the SBFD D / U / D format to the downlink format of the SFI configuration. The change may be from the SBFD F / U / F format to the flexible format of the SFI configuration. The change may be from the SBFD U / D / U format to the uplink format of the SFI configuration.

[0150] Additionally or alternatively, the second configuration may update (e.g., overwrite) the frequency positions and / or the SBFD symbol / slot format for some or all of the subbands in a subband. For example, the first configuration may configure the subbands for the SBFD symbol / slot format (e.g., uplink, downlink, and / or flexible communication), while the second configuration changes the frequency positions and / or the SBFD symbol / slot format. In some aspects, the frequency positions may remain the same in the second configuration, but the SBFD symbol / slot format may change. In other words, the second configuration may change the communication type for the same subbands configured by the first configuration. In some aspects, the second configuration may change the frequency positions of the subbands. The second configuration may increase or decrease the number (e.g., bandwidth) of subbands associated with uplink, downlink, and / or flexible communication.

[0151] In some aspects, the second configuration may change the time resources associated with the SBFD symbol / slot format. In this regard, the second configuration may change (e.g., update) one or more slot positions, one or more symbol positions, and / or the time period (e.g., several milliseconds) associated with the SBFD symbol / slot format.

[0152] In some aspects, the second configuration may change the guard bands associated with the subbands. The guard bands may be frequencies that a network element and / or a UE refrains from transmitting in. The guard bands may be positioned adjacent to the upper end and / or the lower end of the subbands. The second configuration may change the size of the guard bands based on the change in the frequency positions and / or the change in the SBFD symbol / slot format.

[0153] In some aspects, the second configuration may indicate a change from an SBFD symbol / slot to a different SBFD symbol / slot format based on a buffer status report (BSR) associated with the UE. In this regard, the network unit may receive from the UE a buffer status report (BSR) indicating the amount of data (e.g., number of transport blocks) that the UE has been scheduled to transmit to the network unit. The network unit may determine the second configuration at least in part based on the BSR. For example, if the BSR indicates that the UE has an amount of data exceeding the resource capacity indicated in the first configuration, the network unit may send the second configuration increasing the UL communication resources to the UE. For example, the second configuration may increase the number of frequency subbands, number of time slots, and / or number of symbols allocated to the UE for UL communication.

[0154] In some aspects, the UE may apply the second configuration after a certain period of time after receiving the second configuration. In some aspects, the second configuration may indicate when the UE should apply the second configuration. In some aspects, the period of time may be preconfigured in the UE. The period of time may include the number of symbols, number of time slots, number of milliseconds, or other suitable period of time before the UE applies a third configuration. In some aspects, the period of time may be based on the subcarrier spacing (SCS) associated with the subband.

[0155] In some aspects, the network unit may receive from the UE a HARQ ACK communication acknowledging receipt of the second configuration. The UE may apply the second configuration after a certain period of time after sending the HARQ ACK to the network unit. For example, the UE may apply the second configuration after a certain number of symbols, a certain number of time slots, a certain number of milliseconds, or other suitable period of time after sending the HARQ ACK.

[0156] In some aspects, the network unit may send a second configuration that overlays or partially overlays the first configuration. For example, the second configuration may change the SBFD symbol / slot format (e.g., time slot, symbol, subband) of the first configuration. Additionally or alternatively, the second configuration may change the SBFD symbol / slot format to revert (e.g., fallback) to an initial (e.g., legacy) RRC configuration.

[0157] In some aspects, the network unit may cancel one or more scheduled communications based on the second configuration. For example, the network unit may cancel one or more scheduled uplink communications based on the second configuration that changes one or more SBFD symbol / slot formats to a DL symbol / slot format or a flexible symbol / slot format. Additionally or alternatively, the network unit may cancel one or more scheduled downlink communications based on the second configuration that changes one or more SBFD symbol / slot formats to a UL symbol / slot format or a flexible symbol / slot format.

[0158] In some aspects, the network element may cancel one or more scheduled uplink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy downlink symbol / slot format or a legacy flexible symbol / slot format. Additionally or alternatively, the network element may cancel one or more scheduled downlink communications based on a second configuration that changes one or more SBFD symbol / slot formats to a legacy uplink symbol / slot format or a legacy flexible symbol / slot format.

[0159] In some aspects, the network element may cancel one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications based on a second configuration indicating a change to a legacy downlink symbol / slot format. The network element may transmit the PDCCH in one or more symbols in a CORESET configured for UE monitoring.

[0160] In some aspects, the network element may send a third configuration to the UE based on a second configuration indicating a change to a legacy flexible symbol / slot format, the third configuration including a set of parameters associated with DL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.) and / or a set of parameters associated with UL communications (e.g., frequency domain resource allocation, transmit power, beam selection, timing advance, modulation and coding scheme, etc.). The network element may transmit PDSCH-SPS communications, CSI-RS, and PDCCH communications across downlink subbands without rate matching or puncturing. The UE may transmit CG, SRS, and / or PUCCH communications across uplink subchannels using the set of parameters in the third configuration without adjusting the hopping offset.

[0161] In some aspects, the network element may send the second configuration in group common downlink control information (DCI) or medium access control control (MAC-CE) communications. However, the UE may monitor but not receive the second configuration (e.g., decode the second configuration) in group common DCI or MAC-CE communications. The UE may reserve resources (e.g., symbols / slots) associated with flexible SBFD symbols / slots in response to not receiving the second configuration (e.g., not successfully decoding the second configuration). The UE may monitor the PDCCH in the reserved resources and receive PDSCH communications and / or channel state information reference signal (CSI-RS) when indicated by a dynamic grant. However, the UE may cancel periodic downlink communications (e.g., SPS, CSI-RS) and / or periodic uplink communications (e.g., SRS, PUCCH, PUSCH) in response to not receiving the second configuration.

[0162] Other aspects of the present disclosure include the following:

[0163] Aspect 1 includes a method for wireless communication performed by a user equipment (UE), the method including: receiving, from a network unit, a first configuration indicating a time position and a frequency position for a network-side sub-band full-duplex (SBFD) operation mode, where the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot), and the frequency position indicates a plurality of downlink sub-bands and uplink sub-bands or a plurality of uplink sub-bands and a guard band; and receiving, from the network unit, a second configuration indicating a change from the at least one SBFD symbol / slot to a different SBFD symbol / slot format.

[0164] Aspect 2 includes the method according to aspect 1, where the at least one SBFD symbol / slot is configured in a legacy downlink symbol / slot or a flexible symbol / slot.

[0165] Aspect 3 includes the method according to any one of aspects 1 to 2, where the at least one SBFD symbol / slot is configured on a legacy downlink symbol / slot or a legacy flexible symbol / slot and is regarded as a fixed SBFD configuration having a plurality of downlink sub-bands and uplink sub-bands.

[0166] Aspect 4 includes the method according to any one of aspects 1 to 3, further including applying the first configuration to one or more component carriers.

[0167] Aspect 5 includes the method according to any one of aspects 1 to 4, where the one or more component carriers are indicated in a component carrier list.

[0168] Aspect 6 includes the method according to any one of aspects 1 to 5, further including applying the second configuration to one or more component carriers.

[0169] Aspect 7 includes the method according to any one of aspects 1 to 6, where the one or more component carriers are indicated in a component carrier list.

[0170] Aspect 8 includes the method according to any one of aspects 1 to 7, where the downlink sub-bands do not overlap with the uplink sub-bands.

[0171] Aspect 9 includes the method according to any one of aspects 1 to 8, where the uplink sub-bands are located within an intermediate portion of a component carrier.

[0172] Aspect 10 includes the method according to any one of aspects 1 to 9, where the uplink sub-bands are located at an edge portion of a component carrier.

[0173] Aspect 11 includes the method according to any one of Aspects 1 to 10, wherein the plurality of downlink subbands and uplink subbands or the plurality of uplink subbands and guard bands are within a time division duplex (TDD) carrier.

[0174] Aspect 12 includes the method according to any one of Aspects 1 to 11, wherein the plurality of downlink subbands and uplink subbands or the plurality of uplink subbands and guard bands span multiple time division duplex (TDD) carriers, and each downlink subband or uplink subband is a component carrier.

[0175] Aspect 13 includes the method according to any one of Aspects 1 to 12, wherein the frequency position further indicates a plurality of uplink subbands and flexible subbands, and the SBFD symbol / slot is configured in a legacy flexible symbol / slot.

[0176] Aspect 14 includes the method according to any one of Aspects 1 to 13, further comprising sending a buffer status report (BSR) associated with the UE to the network unit, wherein the second configuration is at least partially based on the BSR.

[0177] Aspect 15 includes the method according to any one of Aspects 1 to 14, wherein receiving the first configuration includes receiving the first configuration via at least one of system information block (SIB1) signaling, cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, or downlink control information (DCI).

[0178] Aspect 16 includes the method according to any one of Aspects 1 to 15, wherein receiving the second configuration includes receiving the second configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, UE-specific downlink control information (DCI), or UE group common DCI.

[0179] Aspect 17 includes the method according to any one of Aspects 1 to 16, further comprising applying the second configuration after a gap period after receiving the second configuration.

[0180] Aspect 18 includes the method according to any one of Aspects 1 to 17, wherein the gap period includes at least one of the number of symbols, the number of slots, or the number of milliseconds, and the subcarrier spacing (SCS) is based on the SCS associated with downlink control information (DCI), medium access control control (MAC-CE) communication, or the applied bandwidth part SCS.

[0181] Aspect 19 includes the method according to any one of Aspects 1 to 18, further comprising: sending an acknowledgement (ACK) associated with receiving the second configuration to the network unit; and applying the second configuration after a gap period after sending the ACK.

[0182] Aspect 20 includes the method according to any one of Aspects 1 to 19, wherein the gap period includes at least one of a certain number of symbols, a certain number of time slots, or a certain number of milliseconds.

[0183] Aspect 21 includes the method according to any one of Aspects 1 to 20, further comprising canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

[0184] Aspect 22 includes the method according to any one of Aspects 1 to 21, further comprising canceling one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

[0185] Aspect 23 includes the method according to any one of Aspects 1 to 22, receiving a third configuration including a set of parameters associated with downlink communication from the network unit at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

[0186] Aspect 24 includes the method according to any one of Aspects 1 to 23, further comprising receiving a third configuration including a set of parameters associated with uplink communication from the network unit at least partially based on the second configuration indicating the change to the legacy uplink symbol / slot.

[0187] Aspect 25 includes the method according to any one of Aspects 1 to 24, further comprising: canceling one or more scheduled downlink communications at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot; and canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot.

[0188] Aspect 26 includes the method according to any one of Aspects 1 to 25, further comprising: canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot; and receiving a third configuration including a set of parameters associated with downlink communication from the network unit at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot.

[0189] Aspect 27 includes the method according to any one of Aspects 1 to 26, further comprising canceling one or more scheduled downlink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot format.

[0190] Aspect 28 includes the method according to any one of Aspects 1 to 27, further comprising canceling one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot.

[0191] Aspect 29 includes the method according to any one of Aspects 1 to 28, wherein the change is to at least one of the symbol / slot of the initial Radio Resource Control (RRC) configuration or the symbol / slot format associated with a Slot Format Indicator (SFI) from the SBFD symbol / slot.

[0192] Aspect 30 includes the method according to any one of Aspects 1 to 29, wherein the symbol / slot of the initial RRC configuration is a common downlink symbol / slot of the RRC configuration or a dedicated downlink symbol / slot of the RRC configuration.

[0193] Aspect 31 includes the method according to any one of Aspects 1 to 30, wherein the symbol / slot of the initial RRC configuration is a flexible symbol / slot of the RRC configuration.

[0194] Aspect 32 includes the method according to any one of Aspects 1 to 31, wherein the symbol / slot of the RRC configuration is a common uplink symbol / slot of the RRC configuration or a dedicated uplink symbol / slot of the RRC configuration.

[0195] Aspect 33 includes the method according to any one of Aspects 1 to 32, wherein the change is to an uplink symbol / slot of the RRC configuration from at least one of a downlink symbol / slot of the initial Radio Resource Control (RRC) configuration or a symbol / slot format associated with a Slot Format Indicator (SFI).

[0196] Aspect 34 includes the method according to any one of Aspects 1 to 33, wherein the change is to a downlink symbol / slot of the RRC configuration from at least one of an uplink symbol / slot of the initial Radio Resource Control (RRC) configuration or a symbol / slot format associated with a Slot Format Indicator (SFI).

[0197] Aspect 35 includes the method according to any one of Aspects 1 to 34, wherein the second configuration indicates a change in at least one of the size of the downlink subband, the size of the uplink subband, or the size of the guard band.

[0198] Aspect 36 includes the method according to any one of Aspects 1 to 35, further comprising: monitoring the second configuration in group common downlink control information (DCI) or medium access control control element (MAC-CE) communication; not detecting the second configuration in the group common DCI or the MAC-CE communication; reserving resources associated with one or more flexible SBFD symbols / slots; receiving at least one of physical downlink shared channel (PDSCH) communication or channel state information reference signal (CSI-RS); canceling one or more scheduled downlink communications; and canceling one or more scheduled uplink communications.

[0199] Aspect 37 includes a method of wireless communication performed by a network unit, the method comprising: sending a first configuration to a user equipment (UE) indicating a time position and a frequency position for a network-side subband full-duplex (SBFD) operation mode, wherein the time position indicates at least one SBFD symbol or slot (SBFD symbol / slot), and the frequency position indicates a plurality of downlink subbands and uplink subbands or a plurality of uplink subbands and a guard band; and sending a second configuration to the UE indicating a change from the at least one SBFD symbol / slot to a different SBFD symbol / slot format.

[0200] Aspect 38 includes the method according to Aspect 37, wherein the at least one SBFD symbol / slot is configured in a legacy downlink symbol / slot or a flexible symbol / slot.

[0201] Aspect 39 includes the method according to any one of Aspects 37 to 38, wherein the at least one SBFD symbol / slot is configured on a legacy downlink symbol / slot or a legacy flexible symbol / slot and is regarded as a fixed SBFD configuration having a plurality of downlink subbands and uplink subbands.

[0202] Aspect 40 includes the method according to any one of Aspects 37 to 39, further comprising applying the first configuration to one or more component carriers.

[0203] Aspect 41 includes the method according to any one of Aspects 37 to 40, wherein the one or more component carriers are indicated in a component carrier list.

[0204] Aspect 42 includes the method according to any one of Aspects 37 to 41, further comprising applying the second configuration to one or more component carriers.

[0205] Aspect 43 includes the method according to any one of Aspects 37 to 42, wherein the one or more component carriers are indicated in a component carrier list.

[0206] Aspect 44 includes the method according to any one of Aspects 37 to 43, wherein the downlink sub-band does not overlap with the uplink sub-band.

[0207] Aspect 45 includes the method according to any one of Aspects 37 to 44, wherein the uplink sub-band is located within the middle portion of the component carrier.

[0208] Aspect 46 includes the method according to any one of Aspects 37 to 45, wherein the uplink sub-band is located at the edge portion of the component carrier.

[0209] Aspect 47 includes the method according to any one of Aspects 37 to 46, wherein the plurality of downlink sub-bands and uplink sub-bands or the plurality of uplink sub-bands and guard bands are within a time-division duplex (TDD) carrier.

[0210] Aspect 48 includes the method according to any one of Aspects 37 to 47, wherein the plurality of downlink sub-bands and uplink sub-bands or the plurality of uplink sub-bands and guard bands span multiple time-division duplex (TDD) carriers, and each downlink sub-band or uplink sub-band is a component carrier.

[0211] Aspect 49 includes the method according to any one of Aspects 37 to 48, wherein the frequency position further indicates a plurality of uplink sub-bands and flexible sub-bands, and wherein the SBFD symbol / slot is configured in a legacy flexible symbol / slot.

[0212] Aspect 50 includes the method according to any one of Aspects 37 to 49, further comprising receiving a buffer status report (BSR) associated with the UE from the UE, wherein the second configuration is at least partially based on the BSR.

[0213] Aspect 51 includes the method according to any one of Aspects 37 to 50, wherein transmitting the first configuration includes transmitting the first configuration via at least one of system information block (SIB1) signaling, cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, or downlink control information (DCI).

[0214] Aspect 52 includes the method according to any one of Aspects 37 to 51, wherein transmitting the second configuration includes transmitting the second configuration via at least one of cell common radio resource control (RRC) communication, UE-specific RRC communication, medium access control control (MAC-CE) communication, UE-specific downlink control information (DCI), or UE group common DCI.

[0215] Aspect 53 includes the method according to any one of Aspects 37 to 52, further including applying the second configuration after a gap period after transmitting the second configuration.

[0216] Aspect 54 includes the method according to any one of Aspects 37 to 53, wherein the gap period includes at least one of a number of symbols, a number of time slots, or a number of milliseconds, and wherein the subcarrier spacing (SCS) is based on the SCS associated with downlink control information (DCI), medium access control control (MAC-CE) communication, or the applied bandwidth part SCS.

[0217] Aspect 55 includes the method according to any one of Aspects 37 to 54, further including: receiving an acknowledgement (ACK) associated with receiving the second configuration from the UE; and applying the second configuration after a gap period after transmitting the ACK.

[0218] Aspect 56 includes the method according to any one of Aspects 37 to 55, wherein the gap period includes at least one of a certain number of symbols, a certain number of time slots, or a certain number of milliseconds.

[0219] Aspect 57 includes the method according to any one of Aspects 37 to 56, further including canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to legacy downlink symbols / time slots.

[0220] Aspect 58 includes the method according to any one of Aspects 37 to 57, further including canceling one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communication at least partially based on the second configuration indicating the change to legacy downlink symbols / time slots.

[0221] Aspect 59 includes the method according to any one of Aspects 37 to 58, and transmitting a third configuration including a parameter set associated with downlink communication to the UE at least partially based on the second configuration indicating the change to legacy downlink symbols / time slots.

[0222] Aspect 60 includes the method according to any one of Aspects 37 to 59, further including transmitting a third configuration including a parameter set associated with uplink communication to the UE at least partially based on the second configuration indicating the change to legacy uplink symbols / time slots.

[0223] Aspect 61 includes the method according to any one of Aspects 37 to 60, further comprising: canceling one or more scheduled downlink communications at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot; and canceling one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot.

[0224] Aspect 62 includes the method according to any one of Aspects 37 to 61, further comprising: canceling one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot; and transmitting to the UE a third configuration including a set of parameters associated with downlink communication at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot.

[0225] Aspect 63 includes the method according to any one of Aspects 37 to 62, further comprising canceling one or more scheduled downlink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot format.

[0226] Aspect 64 includes the method according to any one of Aspects 37 to 63, further comprising canceling one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot.

[0227] Aspect 65 includes the method according to any one of Aspects 37 to 64, wherein the change is to at least one of the symbol / slot of the initial Radio Resource Control (RRC) configuration or the symbol / slot format associated with the Slot Format Indicator (SFI) from the SBFD symbol / slot.

[0228] Aspect 66 includes the method according to any one of Aspects 37 to 65, wherein the symbol / slot of the initial RRC configuration is the common downlink symbol / slot of the RRC configuration or the dedicated downlink symbol / slot of the RRC configuration.

[0229] Aspect 67 includes the method according to any one of Aspects 37 to 66, wherein the symbol / slot of the initial RRC configuration is the flexible symbol / slot of the RRC configuration.

[0230] Aspect 68 includes the method according to any one of Aspects 37 to 67, wherein the symbol / slot of the RRC configuration is the common uplink symbol / slot of the RRC configuration or the dedicated uplink symbol / slot of the RRC configuration.

[0231] Aspect 69 includes the method according to any one of Aspects 37 to 68, wherein the change is from at least one of a downlink symbol / slot of an initial radio resource control (RRC) configuration or a symbol / slot format associated with a slot format indicator (SFI) to an uplink symbol / slot of an RRC configuration.

[0232] Aspect 70 includes the method according to any one of Aspects 37 to 69, wherein the change is from at least one of an uplink symbol / slot of an initial radio resource control (RRC) configuration or a symbol / slot format associated with a slot format indicator (SFI) to a downlink symbol / slot of an RRC configuration.

[0233] Aspect 71 includes the method according to any one of Aspects 37 to 70, wherein the second configuration indicates a change in at least one of a size of the downlink subband, a size of the uplink subband, or a size of the guard band.

[0234] Aspect 72 includes a non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions including one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the UE to perform any one of Aspects 1 to 36.

[0235] Aspect 73 includes a non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions including one or more instructions that, when executed by one or more processors of a network unit, cause the network unit to perform any one of Aspects 37 to 71.

[0236] Aspect 74 includes a user equipment (UE) including one or more components for performing any one or more of Aspects 1 to 36.

[0237] Aspect 75 includes a network unit including one or more components for performing any one or more of Aspects 37 to 71.

[0238] Aspect 76 includes a user equipment (UE) including: a memory; a transceiver; and at least one processor coupled to the memory and the transceiver, wherein the UE is configured to perform any one or more of Aspects 1 to 36.

[0239] Aspect 77 includes a network unit including: a memory; a transceiver; and at least one processor coupled to the memory and the transceiver, wherein the network unit is configured to perform any one or more of Aspects 37 to 71.

[0240] Aspect 78 includes a method of wireless communication performed by a user equipment (UE), wherein at least one sub-band full-duplex (SBFD) symbol / slot is configured for legacy downlink symbol / slot or downlink / uplink / downlink communication in a flexible symbol / slot.

[0241] Aspect 79 includes a method of wireless communication performed by a user equipment (UE), wherein at least one sub-band full-duplex (SBFD) symbol / slot is configured on a legacy downlink symbol / slot or a legacy flexible symbol / slot and is regarded as a fixed SBFD configuration having a plurality of downlink sub-bands and uplink sub-bands.

[0242] Aspect 80 includes a method of wireless communication performed by a user equipment (UE), the method including applying a first configuration indicating a time position and a frequency position for a network-side sub-band full-duplex (SBFD) operation mode to one or more component carriers.

[0243] Aspect 81 includes a method of wireless communication performed by a user equipment (UE), wherein at least one sub-band full-duplex (SBFD) symbol / slot is configured for flexible / uplink / flexible communication on a legacy flexible symbol / slot and is regarded as a flexible SBFD configuration having a plurality of flexible sub-bands and uplink sub-bands.

[0244] Information and signals can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0245] Various illustrative blocks and modules described in connection with the disclosure herein can be implemented or performed using a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but in an alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0246] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted through a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in different places, including being distributed such that various parts of the functions are implemented at different physical locations. Further, as used herein, including in the claims, the "or" as used in a list of items (e.g., a list of items followed by "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0247] As will be understood by those skilled in the art so far and depending on the particular application at hand, many modifications, substitutions, and variations can be made to the materials, devices, configurations, and methods of use of the devices of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific examples illustrated and described herein, as they are only some of the examples, but should be fully commensurate with the appended claims hereinafter and their functional equivalents.

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: Receiving, from a network element, a first configuration indicating a time position and a frequency position for a network-side sub-band full-duplex (SBFD) operation mode, wherein the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink sub-bands and uplink sub-bands or a plurality of uplink sub-bands and a guard band; And Receiving, from the network element, a second configuration indicating a change from the at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

2. The method according to claim 1, wherein the at least one SBFD symbol / slot is configured in a legacy downlink symbol / slot or a flexible symbol / slot.

3. The method according to claim 1, wherein the at least one SBFD symbol / slot is configured on a legacy downlink symbol / slot or a legacy flexible symbol / slot and is regarded as a fixed SBFD configuration having a plurality of downlink sub-bands and uplink sub-bands.

4. The method according to claim 1, further comprising applying the first configuration to one or more component carriers.

5. The method according to claim 1, wherein the plurality of downlink sub-bands and uplink sub-bands or the plurality of uplink sub-bands and the guard band are within a time-division duplex (TDD) carrier.

6. The method according to claim 1, further comprising: Applying the second configuration after a gap period after receiving the second configuration.

7. The method according to claim 1, further comprising: Canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

8. The method according to claim 1, further comprising: Canceling one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

9. The method according to claim 1, further comprising: Receiving, from the network element, a third configuration including a set of parameters associated with downlink communication at least partially based on the second configuration indicating the change to the legacy downlink symbol / slot.

10. The method according to claim 1, further comprising: Receiving, from the network element, a third configuration including a set of parameters associated with uplink communication at least partially based on the second configuration indicating the change to the legacy uplink symbol / slot.

11. The method according to claim 1, further comprising: Canceling one or more scheduled downlink communications at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot; And Canceling one or more scheduled uplink communications at least partially based on the second configuration indicating the change to the legacy flexible symbol / slot.

12. The method according to claim 1, further comprising: Cancel one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot; and Receive a third configuration including a set of parameters associated with downlink communication from the network unit at least in part based on the second configuration indicating the change to the legacy flexible symbol / slot.

13. The method according to claim 1, further comprising: Cancel one or more scheduled downlink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot format.

14. The method according to claim 1, further comprising: Cancel one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy uplink symbol / slot.

15. The method according to claim 1, wherein the change is to at least one of the symbol / slot of the initial Radio Resource Control (RRC) configuration or the symbol / slot format associated with a Slot Format Indicator (SFI) from the SBFD symbol / slot.

16. The method according to claim 15, wherein the symbol / slot of the initial RRC configuration is a common downlink symbol / slot of the RRC configuration or a dedicated downlink symbol / slot of the RRC configuration.

17. The method according to claim 15, wherein the symbol / slot of the initial RRC configuration is a flexible symbol / slot of the RRC configuration.

18. The method according to claim 15, wherein the symbol / slot of the RRC configuration is a common uplink symbol / slot of the RRC configuration or a dedicated uplink symbol / slot of the RRC configuration.

19. The method according to claim 1, wherein the change is to an uplink symbol / slot of the RRC configuration from at least one of a downlink symbol / slot of the initial Radio Resource Control (RRC) configuration or a symbol / slot format associated with a Slot Format Indicator (SFI).

20. The method according to claim 1, wherein the change is to a downlink symbol / slot of the RRC configuration from at least one of an uplink symbol / slot of the initial Radio Resource Control (RRC) configuration or a symbol / slot format associated with a Slot Format Indicator (SFI).

21. The method according to claim 1, wherein the second configuration indicates a change in at least one of the size of the downlink sub-band, the size of the uplink sub-band, or the size of the guard band.

22. The method according to claim 1, further comprising: Monitoring the second configuration in group common downlink control information (DCI) or medium access control control (MAC-CE) communication; Not detecting the second configuration in the group common DCI or the MAC-CE communication; Reserving resources associated with one or more flexible SBFD symbols / slots; Receiving at least one of physical downlink shared channel (PDSCH) communication or channel state information reference signal (CSI-RS); Canceling one or more scheduled downlink communications; and Cancel one or more scheduled uplink communications.

23. A user equipment (UE) comprising: A memory; A transceiver; And At least one processor coupled to the memory and the transceiver, wherein the UE is configured to: Receive from a network element a first configuration indicating a time position and a frequency position for a network-side sub-band full-duplex (SBFD) operation mode, wherein the time position indicates at least one SBFD symbol or time slot (SBFD symbol / slot) format, and the frequency position indicates a plurality of downlink sub-bands and uplink sub-bands or a plurality of uplink sub-bands and a guard band; And Receive from the network element a second configuration indicating a change from the at least one SBFD symbol / slot format to a different SBFD symbol / slot format.

24. The UE according to claim 23, wherein the at least one SBFD symbol / slot is configured to be within a legacy downlink symbol / slot or a flexible symbol / slot.

25. The UE according to claim 23, wherein the at least one SBFD symbol / slot is configured to be on a legacy downlink symbol / slot or a legacy flexible symbol / slot and is regarded as a fixed SBFD configuration having a plurality of downlink sub-bands and uplink sub-bands.

26. The UE according to claim 23, wherein the UE is further configured to: Apply the first configuration to one or more component carriers.

27. The UE according to claim 23, wherein the plurality of downlink sub-bands and uplink sub-bands or the plurality of uplink sub-bands and the guard band are within a time-division duplex (TDD) carrier.

28. The UE according to claim 23, wherein the UE is further configured to: Apply the second configuration after a gap period after receiving the second configuration.

29. The UE according to claim 23, wherein the UE is further configured to: Cancel one or more scheduled uplink communications at least in part based on the second configuration indicating the change to the legacy downlink symbol / slot.

30. The UE according to claim 23, wherein the UE is further configured to: Cancel one or more scheduled downlink communications other than physical downlink control channel (PDCCH) communications at least in part based on the second configuration indicating the change to the legacy downlink symbol / slot.

Images