Techniques for facilitating dynamic update indication of SBFD / non-SBFD symbols / slots

Abstract

Apparatuses, methods, and computer readable media for providing an update indication for semi-statically configured SBFD / non-SBFD time resource units are disclosed herein. An example method for wireless communication at a UE includes receiving a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource mode. The method also includes receiving an indication indicating a second resource pattern for a subset of the one or more time resource units. In addition, the method includes communicating with the network entity in each respective time resource unit using a communication mode based on the second resource mode.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 170,504, filed on February 16, 2023, entitled “TECHNIQUES TO FACILITATE ANSBFD / NON-SBFD SYMBOL / SLOT DYNAMIC UPDATE INDICATION,” which is expressly incorporated herein by reference in its entirety. Background Art

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communications employing sub-band full-duplex (SBFD) communications.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continued mobile broadband evolution promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method for wireless communication at a user equipment (UE) is provided. The method may include receiving a first resource pattern for one or more time resource units for a time division duplex (TDD) transmit slot format mode, wherein one of a full-duplex (FD) communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example method may also include receiving an indication of a second resource pattern for a subset of the one or more time resource units. In addition, the example method may include communicating with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0008] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a UE, comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to receive a first resource pattern of one or more time resource units for a TDD transmit time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The at least one processor may also be configured to receive an indication of a second resource pattern for a subset of the one or more time resource units. In addition, the at least one processor may be configured to communicate with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0009] In another aspect of the present disclosure, an apparatus for wireless communication at a UE is provided. The apparatus may include means for receiving a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example apparatus may also include means for receiving an indication of a second resource pattern for a subset of the one or more time resource units. The example apparatus may also include means for communicating with a network entity in each corresponding time resource unit using a communication mode based on the second resource pattern.

[0010] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. When the code is executed, the processor may receive a first resource pattern for one or more time resource units of a TDD transmit time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. When the example code is executed, the processor may also receive an indication of a second resource pattern for a subset of the one or more time resource units. In addition, when the example code is executed, the processor may communicate with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0011] In one aspect of the present disclosure, a method for wireless communication at a UE is provided. The method may include receiving a first resource allocation pattern for a time resource unit for a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example method may also include receiving an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the example method may include communicating with a network entity in the time resource unit using a communication mode based on the TDD transmit time slot format pattern and the indication.

[0012] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a UE, comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to receive a first resource allocation pattern for a time resource unit of a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The at least one processor may also be configured to receive an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the at least one processor may be configured to communicate with a network entity in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0013] In another aspect of the present disclosure, a device for wireless communication at a UE is provided. The device may include a component for receiving a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example device may also include a component for receiving an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the example device may include a component for communicating with a network entity in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0014] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a UE is provided. When the code is executed, the processor may receive a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. When the sample code is executed, the processor may also receive an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, when the sample code is executed, the processor may communicate with a network entity in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0015] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method may include outputting a first resource pattern for one or more time resource units of a TDD transmit slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example method may also include outputting an indication of a second resource pattern for a subset of the one or more time resource units. In addition, the example method may include communicating in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0016] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a network entity comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to output a first resource pattern for one or more time resource units of a TDD transmit time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The at least one processor may also be configured to output an indication of a second resource pattern for a subset of the one or more time resource units. In addition, the at least one processor may be configured to communicate in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0017] In another aspect of the present disclosure, an apparatus for wireless communication at a network entity is provided. The apparatus may include a component for outputting a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example apparatus may also include a component for outputting an indication of a second resource pattern for a subset of the one or more time resource units. In addition, the example apparatus may include a component for communicating in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0018] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a network entity is provided. When the code is executed, the processor may output a first resource pattern for one or more time resource units of a TDD transmit time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. When the example code is executed, the processor may also output an indication of a second resource pattern for a subset of the one or more time resource units. In addition, when the example code is executed, the processor may communicate in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0019] In one aspect of the present disclosure, a method for wireless communication at a network entity is provided. The method may include outputting a first resource allocation pattern for a time resource unit of a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example method may also include outputting an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the example method may include communicating in the time resource unit using a communication mode based on the TDD transmit time slot format pattern and the indication.

[0020] In another aspect of the present disclosure, a device for wireless communication is provided. The device may be a network entity comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to output a first resource allocation pattern for a time resource unit of a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The at least one processor may also be configured to output an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the at least one processor may be configured to communicate in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0021] In another aspect of the present disclosure, a device for wireless communication at a network entity is provided. The device may include a component for outputting a first resource allocation pattern for a time resource unit of a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example device may also include a component for outputting an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, the example device may include a component for communicating in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0022] In another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer-executable code for wireless communication at a network entity is provided. When the code is executed, the processor may output a first resource allocation pattern for a time resource unit of a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. When the example code is executed, the processor may also output an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. In addition, when the example code is executed, the processor may communicate in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0023] To achieve the foregoing and related ends, one or more aspects may include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network (NW).

[0025] Figure 2 A diagram illustrating the architecture of an example of a decomposed base station is shown.

[0026] Figure 3A is a diagram illustrating an example of the first subframe within the 5G NR frame structure.

[0027] Figure 3B is a diagram illustrating an example of DL channels within a 5G NR subframe.

[0028] Figure 3C is a diagram illustrating an example of a second subframe within a 5G NR frame structure.

[0029] Figure 3D is a diagram illustrating an example of UL channels within a 5G NR subframe.

[0030] Figure 4 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device.

[0031] Figure 5A An example of full-duplex communication according to the teachings disclosed herein is illustrated, wherein a network entity is in communication with a first UE and a second UE.

[0032] Figure 5B A first example of communication according to the teachings disclosed herein is illustrated, wherein an antenna array is configured for downlink communication.

[0033] Figure 5C A second example of communication according to the teachings disclosed herein is illustrated, wherein the antenna array is configured for uplink communication.

[0034] Figure 5D A third example of communication according to the teachings disclosed herein is illustrated, wherein the antenna array is configured for a full-duplex communication mode.

[0035] Figure 6 An example network entity supporting a full-duplex communication mode and including multiple antenna panels according to the teachings disclosed herein is illustrated.

[0036] Figure 7A Example resource allocations for IBFD operations according to the teachings disclosed herein are illustrated.

[0037] Figure 7B Another example resource allocation for IBFD operations according to the teachings disclosed herein is illustrated.

[0038] Figure 7C Example resource allocations for SBFD operations according to the teachings disclosed herein are illustrated.

[0039] Figure 8 An example communication flow between a network entity and a UE according to the teachings disclosed herein is illustrated.

[0040] Figure 9 Various example resource allocation patterns for time resource units according to the teachings disclosed herein are illustrated.

[0041] Figure 10 is a diagram illustrating a change of resource pattern at a UE according to the teachings disclosed herein.

[0042] Figure 11 An example communication flow between a network entity and a UE according to the teachings disclosed herein is illustrated.

[0043] Figure 12 Illustrated are example updates that may be made to time resources configured as legacy downlink time resource units in at least one of the first resource mode or the second resource mode in accordance with the teachings disclosed herein.

[0044] Figure 13Illustrated are example updates that may be made to time resources configured as legacy uplink time resource units in at least one of the first resource mode or the second resource mode in accordance with the teachings disclosed herein.

[0045] Figure 14 Illustrated are example updates that may be made to a time resource configured as a legacy flexible time resource unit in at least one of a first resource mode or a second resource mode in accordance with the teachings disclosed herein.

[0046] Figure 15 Illustrated are example updates that may be made to a time resource configured as a legacy flexible time resource unit in at least one of a first resource mode or a second resource mode in accordance with the teachings disclosed herein.

[0047] Figure 16 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0048] Figure 17 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0049] Figure 18 is a diagram illustrating an example of a hardware implementation for an apparatus.

[0050] Figure 19 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0051] Figure 20 is a flow chart of a method of wireless communication according to the teachings disclosed herein.

[0052] Figure 21 is a diagram illustrating an example of a hardware implementation for a network entity.

[0053] Figure 22 is a diagram illustrating an update to a resource pattern including downlink time resource units according to the teachings disclosed herein.

[0054] Figure 23 is a diagram illustrating an update to a resource pattern including flexible time resource units according to the teachings disclosed herein.

[0055] Figure 24 is a diagram illustrating an update to a resource pattern including flexible time resource units according to the teachings disclosed herein.

[0056] Figure 25 is a diagram illustrating an update to a resource pattern including uplink time resource units according to the teachings disclosed herein.

[0057] Figure 26 is a diagram illustrating an update to a resource pattern including a mix of downlink time resource units, flexible time resource units, and uplink time resource units according to the teachings disclosed herein. DETAILED DESCRIPTION

[0058] The simultaneous use of the same set of frequency resources (e.g., the same carrier bandwidth, the same frequency band) for both uplink and downlink in a given time slot may be referred to herein as sub-band full-duplex (SBFD), which may also be referred to as "flexible duplexing." In SBFD mode operation, transmissions in different directions are carried in different sub-bands or bandwidth portions of the carrier bandwidth or frequency band. Wireless communication devices capable of operating in full-duplex mode may be able to use SBFD to increase the amount of data transferred compared to time division duplex (TDD) half-duplex (HD) mode operation. For example, in TDD HD mode operation, data may be sent and received in the same carrier bandwidth or frequency band, but not simultaneously. In contrast, in SBFD mode operation, data may be sent and received simultaneously.

[0059] As used herein, the term "duplex mode" refers to the operating mode of a device (e.g., a UE, a network entity). Examples of duplex modes may include, but are not limited to, half-duplex, full-duplex, and full-duplex-aware. In half-duplex operating mode, a device can have bidirectional communication (e.g., uplink and downlink), but HD bidirectional communication does not occur simultaneously (e.g., does not overlap in the time domain). Time division duplex (TDD) is an example of an HD system. In full-duplex (FD) operating mode, a device can have bidirectional communication, and FD communication can occur simultaneously. Paired spectrum and unpaired spectrum are examples of FD communication systems. Frequency division duplex (FDD) is an example of an FD paired spectrum system (where uplink and downlink can occur simultaneously in different but paired predefined frequency bands). In-band full-duplex (IBFD) and SBFD are two non-limiting examples of FD unpaired spectrum systems (where uplink and downlink can occur simultaneously in the same frequency band / carrier bandwidth). In FD-aware operating mode, a device can be aware that time-frequency resources can be allocated according to any type of FD communication system. However, the device is not configured as an FD device (eg, the device is an HD device only).The examples described herein may be explained in the context of an SBFD system.

[0060] A device (e.g., a scheduled UE) may be configured with a first resource pattern comprising one or more time resource units configured for TDD mode operation. For example, one or more time resource units may be configured as downlink time resource units, uplink time resource units, and / or flexible time resource units. As used herein, the term "time resource unit" may refer to another scheduling unit in a time slot, a symbol, or a time domain, such as a transmit time interval (TTI). When configured for TDD mode operation, the corresponding time resource unit is indicated for a non-FD communication mode. In some examples, a network entity (e.g., a scheduling entity) may convert one or more time resource units in the time resource unit from TDD mode operation to SBFD mode operation. For example, a TDD resource pattern may include five time resource units. The TDD resource pattern may indicate that the first two time resource units are used for downlink, the third time resource unit is flexible (e.g., can be used for uplink or downlink), and the last two time resource units are used for uplink. In such an example, a UE with uplink traffic to be sent cannot send uplink traffic until at least the third time resource unit, and may not be able to send uplink traffic until the fourth time resource unit. A network entity may detect an increase in uplink traffic or downlink traffic. A time resource unit configured for SBFD mode operation may enable the time resource unit to be used for both uplink and downlink traffic. For example, a network entity may convert the first two time resource units to support SBFD mode operation. In some such examples, at least four of the time resource units (e.g., the first two time resource units and the last two time resource units) may now be used to send uplink traffic. Therefore, converting the time resource unit to SBFD mode operation may reduce the latency associated with the increased traffic because additional resources may be used for the traffic.

[0061] The network entity can configure the SBFD resource mode by indicating one or more time resource units to be converted for SBFD mode operation. For example, in the above example, the SBFD resource mode includes the first two time resource units configured for SBFD mode operation, a flexible third time resource unit, and the last two time resource units configured for uplink. In some examples, the SBFD resource mode can be a semi-static resource mode. For example, the SBFD resource mode in the above example (e.g., the first two time resource units configured for SBFD mode operation, followed by a flexible time resource unit, and then the last two time resource units configured for uplink) can continue until the network entity deactivates the SBFD resource mode or indicates a different resource mode for the five time resource units. The time resource units configured for SBFD mode operation can be indicated for the FD communication mode.

[0062] In some examples, the network entity may detect another change in uplink traffic or downlink traffic. In some such examples, the network entity may update one or more time resource units of the SBFD resource pattern to adapt to the change in uplink traffic or downlink traffic. For example, the network entity may configure an updated SBFD resource pattern that includes one or more further adapted time resource units. In some examples, the updated SBFD resource pattern may include additional time resource units configured for SBFD mode operation compared to the original SBFD resource pattern. For example, the updated SBFD resource pattern may include the first three time resource units configured for SBFD mode operation, followed by two time resource units configured for uplink. In some examples, the time resource units of the updated SBFD resource pattern may include a smaller number of time resource units configured for SBFD mode operation. For example, the updated SBFD resource pattern may include a first time resource unit configured for SBFD mode operation, a second time resource unit configured for downlink, a flexible third time resource unit, and a final two time resource units configured for uplink.

[0063] The various aspects disclosed herein facilitate dynamically updating a semi-statically configured resource pattern comprising one or more SBFD time resource units. For example, a network entity may provide an update indication (e.g., via downlink control information (DCI) and / or medium access control (MAC)-control element (MAC-CE)) that indicates that the semi-statically configured SBFD time resource unit is changed to a TDD time resource unit (e.g., a time resource unit configured for TDD mode operation). For example, and with reference to the above example, the update indication may indicate that the second time resource unit of the SBFD resource pattern is converted from being configured for SBFD mode operation to being used for downlink. In some examples, the update indication may indicate that the TDD time resource unit is changed to an SBFD time resource unit. For example, and with reference to the above example, the update indication may indicate that the fourth time resource unit of the SBFD resource pattern is converted from being used for uplink to supporting SBFD mode operation. Thus, the update indication may indicate a change in the pattern of different time resource units (e.g., the five time resource units of the above example).

[0064] In some examples, the update indication may indicate a change in the resource allocation pattern for a time resource unit. The resource allocation pattern may indicate how the frequency resources of the time resource unit are configured. For example, for a time resource unit configured for TDD mode operation, all frequency resources of the time resource unit may be dedicated to the downlink, uplink, or flexible. In contrast, the resource allocation pattern for a time resource unit configured for SBFD mode operation may include different subbands configured for transmission in different directions. For example, a first resource allocation pattern for an SBFD time resource unit may include three subbands. In some such examples, the first subband for the downlink may be separated from the second subband for the uplink by a first guard band, and the second subband for the uplink may be separated from the third subband for the downlink by a second guard band. As another example, the second resource allocation pattern for an SBFD time resource unit may include one subband for the downlink, separated from one subband for the uplink by a guard band. In another example, the third resource allocation pattern for an SBFD time resource unit may include three subbands, but each subband may be oriented in the opposite direction from the corresponding subband in the first resource allocation pattern.

[0065] As described above, in some examples, an update indication may cause a change in the resource allocation pattern of a time resource unit. For example, the update indication may change the resource allocation pattern of an SBFD time resource unit from a first resource allocation pattern to a second resource allocation pattern. In some examples, the update indication may cause the resource allocation pattern of the SBFD time resource unit to revert to its TDD resource allocation pattern. For example, and referring to the above example, the update indication may convert the second time resource unit back to a time resource unit for downlink operation. In other examples, the update indication may change the subband size of one or more of the subbands. In some examples, the update indication may change the resource allocation of a non-SBFD time resource unit to a resource allocation pattern that supports SBFD mode operation. For example, the update indication may change the time resource unit for downlink operation to a time resource unit that supports SBFD mode operation by indicating the subband used for uplink and the frequency location of the subband used for uplink within the bandwidth of the time resource unit. In other examples, the update indication may indicate that the resource allocation of the time resource unit remains unchanged. For example, the SBFD time resource unit may remain an SBFD time resource unit, or the non-SBFD time resource unit may remain a non-SBFD time resource unit.

[0066] As used herein, the term "resource mode" refers to the configuration of an operating mode (e.g., SBFD mode operation or non-SBFD mode operation) for one or more time resources. As used herein, the term "resource allocation mode" refers to the allocation of resources within a time resource unit (e.g., one or more subbands and their corresponding directions).

[0067] In some examples, the update indication may provide an update to a resource pattern. In some examples, the update indication may provide an update to a resource allocation pattern. In some examples, the update indication may provide an update to both a resource pattern and a resource allocation pattern.

[0068] In some examples, updates to one or more time resource units may be periodic (or semi-persistent / sticky). In other examples, updates to one or more time resource units may be aperiodic.

[0069] In some examples, the update indication may include a bitmap comprising one or more code points. In some examples, each code point of the bitmap may be associated with a different time resource unit. For example, and with reference to the above example, the bitmap may include a code point for each time resource unit of the SBFD resource mode. For example, the bitmap may include five code points, the five code points including a first code point mapped to a first time resource unit, a second code point mapped to a second time resource unit, and so on. In other examples, the bitmap may include code points for a subset of time resource units. For example, and with reference to the above example, the bitmap may include a code point for each SBFD time resource unit of the SBFD resource mode. For example, the bitmap may include two code points, the two code points including a first code point mapped to a first time resource unit and a second code point mapped to a second time resource unit.

[0070] In some examples, the changes indicated by the update indication may apply to a single component carrier (CC). In other examples, the changes indicated by the update indication may apply to multiple CCs via a CC list.

[0071] Thus, aspects disclosed herein can implement update indications for dynamically updating SBFD / non-SBFD time resource units, which can facilitate improved communication performance, for example, by reducing latency associated with traffic. Such update indications can allow network entities to adapt to traffic changes more quickly than semi-statically configured updates. Furthermore, dynamically, rather than semi-statically, updating SBFD / non-SBFD time resource units allows resources to be adapted to traffic bursts.

[0072] Although the following description provides examples involving 5G NR, the concepts described herein may be applicable to other similar areas such as 6G, 5G evolution, LTE, LTE-A, CDMA, GSM, and / or other wireless technologies and / or future wireless technologies.

[0073] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0074] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0075] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic component, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, a thread of execution, a process, a function or any combination thereof.

[0076] Thus, in one or more example aspects, specific implementations and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0077] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and / or use cases may be produced in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be produced via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0078] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (e.g., EPC 160), and another core network 190 (e.g., 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. Small cells include femto cells, pico cells, and micro cells.

[0079] A base station 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A base station 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interface with the core network 190 via a second backhaul link 184. Among other functions, the base station 102 can perform one or more of the following functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 can communicate with each other directly or indirectly (eg, via EPC 160 or core network 190) via a third backhaul link 134 (eg, an X2 interface). First backhaul link 132, second backhaul link 184, and third backhaul link 134 can be wired or wireless.

[0080] In some aspects, a base station (e.g., one of base stations 102 or one of base stations 180) may be referred to as a RAN and may include converged or disaggregated components. As an example of a disaggregated RAN, a base station may include a central unit (CU) (e.g., CU 106), one or more distributed units (DUs) (e.g., DU 105), and / or one or more remote units (RUs) (e.g., RU 109), as shown in FIG. Figure 1 As illustrated. The RAN can be decomposed by splitting between the RU 109 and the converged CU / DU. The RAN can be decomposed by splitting between the CU 106, DU 105, and RU 109. The RAN can be decomposed by splitting between the CU 106 and the converged DU / RU. The CU 106 and one or more DUs can be connected via an F1 interface. The DU 105 and RU 109 can be connected via a fronthaul interface. The connection between the CU 106 and the DU 105 can be referred to as midhaul, and the connection between the DU 105 and the RU 109 can be referred to as fronthaul. The connection between the CU 106 and the core network 190 can be referred to as backhaul.

[0081] The RAN may be based on a functional split between various components of the RAN (e.g., between the CU 106, DU 105, or RU 109). The CU 106 may be configured to perform one or more aspects of a wireless communication protocol, e.g., handle one or more layers of a protocol stack, and one or more DUs may be configured to handle other aspects of the wireless communication protocol, e.g., other layers of the protocol stack. In different implementations, the split between the layers handled by the CU and the layers handled by the DU may occur at different layers of the protocol stack. As a non-limiting example, the DU 105 may provide a logical node that hosts the radio link control (RLC) layer, the medium access control (MAC) layer, and at least a portion of the physical (PHY) layer based on the functional split. The RU may provide a logical node that is configured to host at least a portion of the PHY layer and radio frequency (RF) processing. The CU 106 may host, for example, higher layer functions above the RLC layer, such as the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, and / or upper layers. In other implementations, the split between the layer functions provided by the CU, DU, or RU may vary.

[0082] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas. For example, small cell 103 can have a coverage area 111 that overlaps with the corresponding geographic coverage area 110 of one or more base stations (e.g., one or more macro base stations, such as base station 102). A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include uplink (UL) (also known as reverse link) transmissions from the UE to the base station and / or downlink (DL) (also known as forward link) transmissions from the base station to the UE. The communication link 120 can use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be over one or more carriers. For each carrier allocated in the carrier aggregation for up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 can use spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0083] Certain UEs may communicate with each other using device-to-device (D2D) communication links, such as D2D communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be accomplished through various wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0084] The wireless communication system may also include a Wi-Fi access point (AP), such as AP 150, that communicates with a Wi-Fi station (STA), such as STA 152, via a communication link 154, e.g., in the 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available prior to communicating.

[0085] Small cell 103 can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 103 can adopt NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as that used by Wi-Fi AP 150. Small cell 103 adopting NR in unlicensed spectrum can improve access network coverage and / or increase access network capacity.

[0086] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0088] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" or the like is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0089] A base station, whether a small cell 103 or a large cell (e.g., a macro base station), may include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNBs, may operate in the traditional sub-6 GHz spectrum, in millimeter wave frequencies, and / or near millimeter wave frequencies to communicate with UE 104. When a gNB operates in millimeter wave frequencies or near millimeter wave frequencies, base station 180 may be referred to as a millimeter wave base station. A millimeter wave base station may utilize beamforming 181 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0090] Base station 180 may transmit beamformed signals in one or more transmit directions 182 to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 183. UE 104 may also transmit beamformed signals in one or more transmit directions to base station 180. Base station 180 may receive beamformed signals in one or more receive directions from UE 104. Base station 180 and UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 and UE 104. The transmit and receive directions of base station 180 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.

[0091] The EPC 160 may include a mobility management entity (e.g., MME 162), other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway (e.g., PDN gateway 172). The MME 162 may communicate with a home subscriber server (HSS) (e.g., HSS 174). The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Generally speaking, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are passed through the serving gateway 166, which is itself connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to the IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. It serves as the entry point for content providers' MBMS delivery, authorizes and initiates MBMS bearer services within the Public Land Mobile Network (PLMN), and schedules MBMS delivery. The MBMS Gateway 168 distributes MBMS services to base stations 102 within a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services. It is also responsible for session management (start / stop) and for collecting eMBMS-related billing information.

[0092] The core network 190 may include an access and mobility management function (AMF) (e.g., AMF 192), other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) (e.g., UPF 195). The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally speaking, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are passed through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to the IP services 197. The IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), packet switched (PS) streaming (PSS) services, and / or other IP services.

[0093] Base station 102 may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit receive point (TRP), network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and DU) and a RU, or as a disaggregated base station including one or more of a CU, DU, and / or RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN). Base station 102 provides an access point for UE 104 to EPC 160 or core network 190.

[0094] Examples of UEs include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional device. Some of the UEs may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UEs may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access a network collectively and / or individually.

[0095] Reference again Figure 1 In certain aspects, a device communicating with a network entity, such as one of the UEs 104 communicating with one of the base stations 102 or components of the base station (e.g., the CU 106, the DU 105, and / or the RU 109), may be configured to manage one or more aspects of wireless communications. For example, one of the UEs 104 may have an SBFD configuration switching component 198 that may be configured to facilitate dynamic updating of time resource units (e.g., symbols or time slots) configured with an SBFD mode via signaling.

[0096] In certain aspects, the SBFD configuration switching component 198 may be configured to receive a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example SBFD configuration switching component 198 may also be configured to receive an indication of a second resource pattern for a subset of the one or more time resource units. Additionally, the example SBFD configuration switching component 198 may be configured to communicate with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0097] In another aspect, the SBFD configuration switching component 198 can be configured to receive a first resource allocation pattern for a time resource unit of a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example SBFD configuration switching component 198 can also be configured to receive an indication indicating a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. Additionally, the example SBFD configuration switching component 198 can be configured to communicate with a network entity in the time resource unit using the communication mode based on the TDD transmit time slot format pattern and the indication.

[0098] In another configuration, a network entity, such as one of the base stations 102 or a component of the base station (e.g., CU 106, DU 105, and / or RU 109), may be configured to manage one or more aspects of wireless communications. For example, one of the base stations 102 may have an SBFD update configuration component 199 that may be configured to facilitate dynamically applying updates to semi-statically configured SBFD resource allocations.

[0099] In certain aspects, the SBFD update configuration component 199 may be configured to output a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The SBFD update configuration component 199 may also be configured to output an indication of a second resource pattern for a subset of the one or more time resource units. Additionally, the SBFD update configuration component 199 may be configured to communicate in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0100] In another aspect, the SBFD update configuration component 199 may be configured to output a first resource allocation pattern for a time resource unit of a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The SBFD update configuration component 199 may also be configured to output an indication indicating a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. Additionally, the SBFD update configuration component 199 may be configured to communicate in the time resource unit using a communication pattern based on the TDD transmit time slot format pattern and the indication.

[0101] Aspects disclosed herein facilitate dynamically providing update indications to change resource allocations of semi-statically configured SBFD time resource units, which can improve spectrum efficiency and reduce latency.

[0102] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element 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 a converged or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0103] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed across 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 may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0104] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (a network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0105] As an example, Figure 2 A diagram illustrating the architecture of an example of a disaggregated base station 200 is shown. The architecture of disaggregated base station 200 may include one or more CUs (e.g., CU 210), which may communicate directly with core network 220 via backhaul links or indirectly through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) (e.g., near-RT RIC 225) via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework (e.g., SMO framework 205), or both. CU 210 may communicate with one or more DUs (e.g., DU 212) via corresponding midhaul links (e.g., F1 interfaces). DU 212 may communicate with one or more RUs (e.g., RU 214) via corresponding fronthaul links. RU 214 may communicate with corresponding UEs (e.g., UE 204) via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RUs simultaneously.

[0106] Each of the units (i.e., CU (e.g., CU 210), DU (e.g., DU 212), RU (e.g., RU 214), and near-RT RIC (e.g., near-RT RIC 225), non-RT RIC (e.g., non-RT RIC 215), and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an 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 configured to receive signals or transmit signals to one or more of the other units via the wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or transmit signals to one or more of the other units via the wireless transmission medium.

[0107] In some aspects, the CU 210 may host one or more high-level 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 be implemented using an interface that is configured to communicate signals with 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 specific implementations, the CU 210 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 210 may be implemented to communicate with the DU 212 for network control and signal transmission.

[0108] DU 212 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs. In some aspects, DU 212 may host one or more of a radio link control (RLC) layer, a medium 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.) based at least in part on a functional split (such as those defined by 3GPP). In some aspects, DU 212 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 DU 212 or with control functions hosted by CU 210.

[0109] Lower layer functionality may be implemented by one or more RUs. In some deployments, the RU 214 controlled by the DU 212 may correspond to a logical node that hosts 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, based at least in part on functional splitting (such as lower layer functional splitting). In this architecture, the RU 214 may be implemented to handle over-the-air (OTA) communications with one or more UEs (e.g., UE 204). In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 214 may be controlled by the corresponding DU. In some scenarios, this configuration may enable the DU and CU 210 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0110] The SMO framework 205 can be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as 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 an O2 interface). Such virtualized network elements may include, but are not limited to, CUs, DUs, RUs, and near-RT RICs. In some implementations, the SMO framework 205 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 211) via the O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0111] The non-RT RIC 215 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (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 may be coupled to or in communication with the near-RT RIC 225 (e.g., via an A1 interface). The near-RT RIC 225 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions via an interface (e.g., via an E2 interface) that connects one or more CUs, one or more DUs, or both, and the O-eNB with the near-RT RIC 225.

[0112] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 225. This information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function 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 in performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0113] At least one of the CU 210, the DU 212, and the RU 214 may be referred to as a base station 202. Thus, the base station 202 may include one or more of the CU 210, the DU 212, and the RU 214 (each component is indicated by a dashed line to indicate that each component may or may not be included in the base station 202). The base station 202 provides an access point to the core network 220 for the UE 204. The communication link between the RU (e.g., the RU 214) and the UE (e.g., the UE 204) may include uplink (UL) (also known as a reverse link) transmissions from the UE 204 to the RU 214 and / or downlink (DL) (also known as a forward link) transmissions from the RU 214 to the UE 204.

[0114] Certain UEs may communicate with each other using D2D communication (e.g., D2D communication link 258). D2D communication link 258 may use DL / UL WWAN spectrum. D2D communication link 258 may use one or more sidelink channels. D2D communication may be performed via various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0115] The wireless communication system may also include a Wi-Fi AP 250 that communicates with a UE 204 (also referred to as a Wi-Fi STA) via a communication link 254, for example, in the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 204 / Wi-Fi AP 250 may perform a CCA prior to communication to determine whether the channel is available.

[0116] Base station 202 and UE 204 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 202 may transmit beamformed signals 282 to UE 204 in one or more transmit directions. UE 204 may receive beamformed signals from base station 202 in one or more receive directions. UE 204 may also transmit beamformed signals 284 to base station 202 in one or more transmit directions. Base station 202 may receive beamformed signals from UE 204 in one or more receive directions. Base station 202 / UE 204 may perform beam training to determine the optimal receive and transmit directions for each of base station 202 / UE 204. The transmit and receive directions of base station 202 may or may not be the same. The transmit and receive directions of UE 204 may or may not be the same.

[0117] The core network 220 may include an access and mobility management function (AMF) (e.g., AMF 261), a session management function (SMF) (e.g., SMF 262), a user plane function (UPF) (e.g., UPF 263), a unified data management (UDM) (e.g., UDM 264), one or more location servers 268, and other functional entities. The AMF 261 is a control node that handles signaling between the UE 204 and the core network 220. The AMF 261 supports registration management, connection management, mobility management, and other functions. The SMF 262 supports session management and other functions. The UPF 263 supports packet routing, packet forwarding, and other functions. The UDM 264 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 268 are exemplified as including a gateway mobile location center (GMLC) (e.g., GMLC 265) and a location management function (LMF) (e.g., LMF 266). However, in general, the one or more location servers 268 may include one or more location / positioning servers, which may include one or more of the GMLC 265, LMF 266, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Positioning Center (MPC), etc. The GMLC 265 and LMF 266 support UE location services. The GMLC 265 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 266 receives measurements and assistance information from the NG-RAN and UE 204 via the AMF 261 to calculate the location of the UE 204. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 204. Positioning the UE 204 may involve signal measurements, position estimates, and optionally velocity calculations based on these measurements. Signal measurements may be performed by the UE 204 and / or the base station 202 serving the UE 204. The measured signals may be based on one or more of a satellite positioning system (SPS) 270 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or other systems / signals / sensors.

[0118] A wireless device, such as UE 204, may include an SBFD configuration switching component 198 that may be configured to facilitate dynamic updating of time resource units (eg, symbols or time slots) configured with an SBFD mode via signaling, such as in conjunction with Figure 1 The example described.

[0119] In certain aspects, a base station (such as decomposed base station 200) or a component of a base station may include an SBFD update configuration component 199 that may be configured to facilitate dynamically applying updates to semi-statically configured SBFD resource configurations, such as in conjunction with Figure 1 The example described.

[0120] Figure 3A FIG301 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 3B FIG330 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 3C FIG350 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 3D FIG38 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 3A 、 Figure 3C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0121] Figures 3A to 3DThe frame structure is illustrated, and aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The numerology defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration is scalable with 1 / SCS.

[0122]

[0123] Table 1: Parameter set, SCS and CP

[0124] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ As shown in Table 1, the subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. Symbol length / duration is inversely related to subcarrier spacing. Figures 3A to 3D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 3B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0125] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0126] like Figure 3A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RSs may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RSs may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0127] Figure 3B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by the UE to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0128] like Figure 3CAs illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and on the specific PUCCH format used, the PUCCH DM-RS may be transmitted in different configurations. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and the UE may transmit the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0129] Figure 3D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0130] Figure 4 is a block diagram illustrating an example of a first wireless device configured to exchange wireless communications with a second wireless device. Figure 4 In the illustrated example of , the first wireless device may include a base station 410, the second wireless device may include a UE 450, and the base station 410 may communicate with the UE 450 in an access network. Figure 4 As shown, base station 410 includes a transmit processor (TX processor 416), a transmitter 418Tx, a receiver 418Rx, antennas 420, a receive processor (RX processor 470), a channel estimator 474, a controller / processor 475, and a memory 476. Example UE 450 includes antennas 452, a transmitter 454Tx, a receiver 454Rx, an RX processor 456, a channel estimator 458, a controller / processor 459, a memory 460, and a TX processor 468. In other examples, base station 410 and / or UE 450 may include additional or alternative components.

[0131] In the DL, Internet Protocol (IP) packets may be provided to the controller / processor 475. The controller / processor 475 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 475 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0132] The TX processor 416 and the RX processor 470 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 416 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-order phase-shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 474 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 450. Each spatial stream may then be provided to a different one of the antennas 420 via a separate transmitter (e.g., transmitter 418Tx). Each transmitter 418Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0133] At the UE 450, each receiver 454Rx receives a signal via its corresponding antenna in the antennas 452. Each receiver 454Rx recovers the information modulated onto the RF carrier and provides the information to the RX processor 456. The TX processor 468 and the RX processor 456 implement Layer 1 functionality associated with various signal processing functions. The RX processor 456 may perform spatial processing on the information to recover any spatial streams destined for the UE 450. In the event that multiple spatial streams are destined for the UE 450, two or more of the multiple spatial streams may be combined by the RX processor 456 into a single OFDM symbol stream. The RX processor 456 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 410. These soft decisions may be based on channel estimates calculated by the channel estimator 458. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 410. The data and control signals are then provided to a controller / processor 459, which implements layer 3 and layer 2 functionality.

[0134] The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the UL, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 459 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0135] Similar to the functionality described in conjunction with DL transmissions performed by the base station 410, the controller / processor 459 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0136] Channel estimates derived by the channel estimator 458 from a reference signal or feedback sent by the base station 410 may be used by the TX processor 468 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 468 may be provided to different ones of the antennas 452 via separate transmitters (e.g., transmitter 454Tx). Each transmitter 454Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0137] UL transmissions are processed at the base station 410 in a manner similar to that described in conjunction with the receiver functionality at the UE 450. Each receiver 418Rx receives a signal through its corresponding one of the antennas 420. Each receiver 418Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 470.

[0138] The controller / processor 475 may be associated with a memory 476 that stores program codes and data. The memory 476 may be referred to as a computer-readable medium. In the UL, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 475 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0139] At least one of the TX processor 468, the RX processor 456, and the controller / processor 459 may be configured to perform operations related to Figure 1 The SBFD configuration switching component 198 combines various aspects.

[0140] At least one of the TX processor 416, the RX processor 470, and the controller / processor 475 may be configured to perform operations related to Figure 1 The SBFD update configuration component 199 combines various aspects.

[0141] Wireless communication systems can be configured to share available system resources and provide various communication services (e.g., telephony, video, data, messaging, broadcasts, etc.) based on, for example, multiple access technologies that support communication with multiple users. In one example, wireless devices can communicate in full-duplex mode, where uplink and downlink communications can be exchanged in the same frequency band at overlapping times.

[0142] UE and / or network entity (e.g., as combined with Figure 1 and Figure 2 The base station or component of the base station described in the example of FIG. 5 may support a full-duplex communication mode. For example, a UE may send uplink communications from one antenna panel and may receive downlink communications using another antenna panel. In an additional or alternative example, a network entity may use a first antenna panel to send downlink communications to a first UE and may use a second antenna panel to receive uplink communications from a second UE. For another example, a network entity may use a first antenna panel to send downlink communications to a UE and may use a second antenna panel to receive uplink communications from the same UE. In some examples, the full-duplex communication mode may be conditional on beam or spatial separation or other conditions.

[0143] A full-duplex communication mode can reduce latency. For example, a full-duplex communication mode can enable a UE to receive downlink communications in an uplink-only time slot, which can reduce latency for downlink communications. A full-duplex communication mode can improve spectral efficiency, such as per-cell or per-UE spectral efficiency. A full-duplex communication mode can enable more efficient use of wireless resources. For example, because a full-duplex communication mode supports sending and receiving information at a wireless device in a temporally overlapping manner, spectral efficiency can be improved relative to the spectral efficiency of a half-duplex communication mode, which supports sending or receiving information in one direction at a time without overlapping uplink and downlink communications.

[0144] Figure 5AAn example of full-duplex communication 500 as presented herein is illustrated, wherein a network entity 502 is in communication with a first UE 504 and a second UE 506. One or more aspects described with respect to the network entity 502 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. Figure 5A In the example of FIG, the network entity 502 is a full-duplex network entity, and the first UE 504 and the second UE 506 can be configured as half-duplex UEs or full-duplex UEs. Figure 5A As shown, the network entity 502 includes an antenna array 510 . Figure 5A Antenna array 510 includes a first antenna panel 512 ("Panel 1"), a second antenna panel 514 ("Panel 2"), and a physical spacing 516 ("D") between first antenna panel 512 and second antenna panel 514. Each of the two antenna panels can be a sub-array of antennas. A given panel can transmit and / or receive a beam or group of beams.

[0145] Figure 5B 、 Figure 5C and Figure 5D Demonstrates the use of Figure 5A 1. Example antenna array 510 for communicating between network entity 502, first UE 504, and second UE 506. The communications may employ multi-user MIMO (MU-MIMO).

[0146] Figure 5B A first example 520 of communication as presented herein is illustrated, wherein the antenna array 510 is configured for downlink communication. For example, the first antenna panel 512 may be configured to transmit a first downlink communication 522 to the first UE 504, and the second antenna panel 514 may be configured to transmit a second downlink communication 524 to the second UE 506.

[0147] Figure 5C A second example 540 of communications as presented herein is illustrated, wherein the antenna array 510 is configured for uplink communications. For example, the first antenna panel 512 may be configured to receive a first uplink communication 542 from the first UE 504, and the second antenna panel 514 may be configured to receive a second uplink communication 544 from the second UE 506.

[0148] Figure 5D A third example 560 of communication as presented herein is illustrated, wherein the antenna array 510 is configured for full-duplex communication mode. For example, the first antenna panel 512 may be configured to transmit downlink communications 562 to the first UE 504, and the second antenna panel 514 may be configured to receive uplink communications 564 from the second UE 506.

[0149] Full-duplex communication mode enables wireless devices to achieve increased throughput and spectral efficiency relative to half-duplex mode communication. However, full-duplex communication mode may also be associated with higher levels of self-interference, which may result in a reduced signal-to-interference-plus-noise ratio (SINR).

[0150] Figure 6 FIG6 is a diagram 600 illustrating an example network entity 602 supporting full-duplex communication mode and including multiple antenna panels as presented herein. One or more aspects described with respect to the network entity 602 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. Figure 6 In the illustrated example of FIG, the network entity 602 is in full-duplex communication mode with the first UE 604 and the second UE 606. For example, the first antenna panel 610 ("Panel 1") can be configured to send downlink communications 612 to the first UE 604. Additionally, the second antenna panel 620 ("Panel 2") can be configured to receive uplink communications 622 from the second UE 606. Figure 6 In the example of , the antenna panel can be configured such that at least a portion of downlink communications 612 and uplink communications 622 overlap in the time domain.

[0151] In some examples, self-interference may occur when a transmitted signal leaks into a receiving port. Figure 6 In the example of FIG. 5 , leakage from a first antenna panel 610 configured to transmit to a second antenna panel 620 configured to receive is shown.

[0152] Additionally or alternatively, self-interference may occur when an object reflects a transmitted signal back to the receiving port, which may be referred to as "spurious interference." For example, in Figure 6 In the example shown in FIG, a signal 630 transmitted by the first antenna panel 610 toward the first UE 604 can reflect from the object 632 and enter the second antenna panel 620, which can cause a spurious echo effect. The reflected signal can interfere with uplink communications (such as uplink communications 622) transmitted by the second UE 606 toward the second antenna panel 620.

[0153] Full-duplex communication mode can occur within the same frequency band. When a wireless device operates in full-duplex communication mode, uplink and downlink communications can occur within the same frequency sub-band, within partially overlapping frequency sub-bands, or within different frequency sub-bands. Uplink communications can be communicated using uplink resources, and downlink communications can be communicated using downlink resources. A wireless device can implement full-duplex communication mode via either intra-band full-duplex (IBFD) or sub-band full-duplex (SBFD). When operating with IBFD, the wireless device transmits and receives on overlapping (or partially overlapping) time-domain and frequency-domain resources. That is, downlink and uplink communications share or partially share the same time-domain and frequency-domain resources. When operating with SFFD, the wireless device transmits and receives simultaneously but using different frequency-domain resources. That is, downlink and uplink communications overlap in time-domain resources but do not overlap with respect to frequency-domain resources. Therefore, sub-band full-duplex can also be referred to as "sub-band non-overlapping full-duplex."

[0154] Figure 7A 、 Figure 7B and Figure 7C Various examples of resource allocation for IBFD operations and SBFD operations as presented herein are illustrated. Figure 7A 、 Figure 7B and Figure 7C In the example of , resource allocation is for one time resource unit 702. Downlink resources and uplink resources that are immediately adjacent to each other correspond to frequency domain resources with a guard band width of 0. Figure 7A An example first resource allocation 700 is illustrated and facilitates IBFD operations. Figure 7B An example second resource allocation 720 is illustrated and facilitates IBFD operations. Figure 7C An example third resource allocation 740 is illustrated and facilitates SBFD operations.

[0155] exist Figure 7A In the first resource allocation 700, the resources used for uplink communication (e.g., resources used to send or receive uplink information) and the resources used for downlink communication (e.g., resources used to send or receive downlink information) completely overlap in the frequency domain. For example, the uplink resource 704 completely overlaps with the downlink resource 706. Figure 7B In the second resource allocation 720, the uplink resources 722 partially overlap with the downlink resources 724 in the frequency domain.

[0156] exist Figure 7CIn the third resource allocation 740, the resources used for uplink communication and the resources used for downlink communication may overlap in time using different frequency sub-bands. For example, uplink resources 742 are separated from downlink resources 744 by a guard band 746. Guard band 746 may be a frequency domain resource or a gap in the frequency domain resource provided between uplink resources 742 and downlink resources 744. Separating uplink resources 742 from downlink resources 744 using guard band 746 may help reduce self-interference.

[0157] In some examples, uplink resources and downlink resources allocated for SBFD operation can be configured within the same TDD time resource unit. In contrast, uplink resources and / or downlink resources allocated for IBFD operation can be configured across two or more TDD time resource units.

[0158] If combined Figures 3A to 3D As described, the UE can be configured with a slot format for a slot via the received SFI. The slots can be all downlink (e.g., slot format 0 including all downlink symbols), all uplink (e.g., slot format 1 including all uplink symbols), all flexible (e.g., slot format 2 including all flexible symbols), or a mixture of downlink symbols, uplink symbols, and flexible symbols.

[0159] Figure 8 An example communication flow 800 between a network entity 802 and a UE 804 as presented herein is illustrated. One or more aspects described with respect to the network entity 802 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. The UE 804 may be an SBFD-aware UE (e.g., a UE that supports the capability of communicating via SBFD operation). In the illustrated example, the communication flow 800 facilitates converting one or more time resource units of a first transmit time slot format pattern 810 into corresponding semi-statically configured SBFD time resource units of a second transmit time slot format pattern 830. Aspects of the network entity 802 may be performed by Figure 1 One of the base stations 102 and / or Figure 4 Various aspects of UE 804 may be implemented by base station 410. Figure 1 One of the UEs 104 and / or Figure 4 UE 450 to achieve. Although Figure 8 Not shown in the illustrated example, it will be appreciated that in additional or alternative examples, the network entity 802 and / or the UE 804 can communicate with one or more other base stations or UEs.

[0160] exist Figure 8In the illustrated example of , the network entity 802 outputs (e.g., transmits) a transmit slot format mode indication 806 that is received (e.g., obtained) by the UE 804. The transmit slot format mode indication 806 may indicate a traffic direction (e.g., downlink, uplink, or flexible) for one or more time resource units. Figure 8 In the illustrated example, the transmit slot format mode indication 806 indicates the traffic direction for five slots (e.g., slot n to slot n+4). Aspects of the transmit slot format mode indication 806 may be implemented via a "tdd-UL-DL-ConfigurationCommon" information element (IE), a "tdd_ULDL-ConfigurationDedicated" IE, or through DCI. The transmit slot format mode indication 806 may indicate the periodicity of the DL-UL pattern (e.g., which may be referred to as a "dl-UL-TransmissionPeriodicity" field), the number of consecutive full downlink slots at the beginning of each DL-UL pattern (e.g., which may be referred to as a "nrofDownlinkSlots" field), the number of consecutive downlink symbols in the beginning of the slot after the last full downlink slot (e.g., which may be referred to as a "nrofDownlinkSymbols" field), the number of consecutive full uplink slots at the end of each DL-UL pattern (e.g., which may be referred to as a "nrofUplinkSlots" field), and the number of consecutive uplink symbols in the end of the slot before the first full downlink slot (e.g., which may be referred to as a "nrofUplinkSymbols" field). The remaining symbols of the DL-UL pattern may be flexible symbols.

[0161] exist Figure 8 In the illustrated example of FIG, the transmit slot format mode indication 806 configures the first transmit slot format mode 810 for communication between the network entity 802 and the UE 804. Figure 8 The time resource unit of the first transmit time slot format pattern 810 is a time slot. Figure 8The first transmit slot format pattern 810 configures a resource pattern for five time slots (e.g., time slot n to time slot n+4). The example first transmit slot format pattern 810 includes a mix of downlink time slots, uplink time slots, and flexible time slots. For example, the first transmit slot format pattern 810 includes a first downlink time slot 812 ("time slot n"), a second downlink time slot 814 ("time slot n+1"), a flexible time slot 816 ("time slot n+2"), a first uplink time slot 818 ("time slot n+3"), and a second uplink time slot 820 ("time slot n+4"). Based on the first transmit slot format pattern 810, the UE 804 receives downlink information (e.g., downlink control and / or downlink data) from the network entity 802 in the first downlink time slot 812, the second downlink time slot 814, and / or the flexible time slot 816. The UE 804 may send uplink information (e.g., uplink control and / or uplink data) to the network entity 802 in the flexible time slot 816, the first uplink time slot 818, and / or the second uplink time slot 820. Thus, the resulting uplink and downlink traffic is time division duplex (TDD), as arranged by the dedicated time slots and as arranged by the symbol assignments in the flexible time slots.

[0162] exist Figure 8 In the example of FIG, if UE 804 has uplink information to communicate to network entity 802, uplink communications may experience increased latency because UE 804 is restricted to transmitting in the first uplink time slot 818 and the second uplink time slot 820 (and may be able to transmit in the flexible time slot 816). Additionally or alternatively, if network entity 802 has downlink information to communicate to UE 804, downlink communications may experience latency because network entity 802 is restricted to transmitting in the first downlink time slot 812 and the second downlink time slot 814 (and may be able to transmit in the flexible time slot 816).

[0163] Thus, in some examples, to reduce latency and / or increase energy for at least uplink communications, the network entity 802 can be configured to convert one or more time resource units (e.g., time slots) of the first transmit time slot format pattern 810 into SBFD time resource units (e.g., SBFD time slots). For example, the network entity 802 can send an SBFD configuration 808 that is received by the UE 804. The SBFD configuration 808 can indicate that one or more time slots of the first transmit time slot format pattern 810 are to be converted into SBFD time slots. The SBFD configuration 808 can also indicate a subband to be used for the corresponding SBFD time slot.

[0164] exist Figure 8In the illustrated example, the SBFD configuration 808 changes the resource pattern of five time slots (eg, time slot n to time slot n+4) from the first transmit time slot format pattern 810 to the second transmit time slot format pattern 830 . Figure 8 The second transmit slot format pattern 830 includes a downlink time slot 832 ("time slot n"), a first SBFD time slot 834 ("time slot n+1"), a second SBFD time slot 836 ("time slot n+2"), a third SBFD time slot 838 ("time slot n+3"), and an uplink time slot 840 ("time slot n+4"). A transmit pattern that includes SBFD time slots (e.g., the second transmit slot format pattern 830) may be referred to as an "SBFD time resource and frequency resource" mode. Additionally or alternatively, the second transmit slot format pattern 830 may be referred to as a "flexible TDD" mode or a "dynamic TDD" mode because the time slots of the first transmit slot format pattern 810 can be converted into SBFD time slots.

[0165] exist Figure 8 In the illustrated example, downlink time slot 832 and uplink time slot 840 remain legacy TDD time slots, which may also be referred to as "non-SBFD time slots." For example, downlink time slot 832 is still dedicated to downlink traffic, and uplink time slot 840 is still dedicated to uplink traffic. SBFD configuration 808 converts the resource allocation (e.g., time domain resources and frequency domain resources) of the three middle time slots to support SBFD operation. That is, downlink time slot 832 and uplink time slot 840 may support non-FD communication mode, while first SBFD time slot 834, second SBFD time slot 836, and third SBFD time slot 838 may support FD communication mode. SBFD time slots may include a combination of uplink subbands and downlink subbands. In some examples, SBFD time slots may include flexible subbands.

[0166] As used herein, the term "uplink subband" refers to one or more frequency domain resources dedicated to uplink traffic. The term "downlink subband" refers to one or more frequency domain resources dedicated to downlink traffic. The term "flexible subband" refers to one or more frequency domain resources that can be assigned to uplink traffic or downlink traffic. The term "legacy TDD time slot" refers to a time slot (or time resource unit) with resource allocation dedicated to traffic in one direction (e.g., Figure 8810, downlink time slot 832, and uplink time slot 840). Additionally, the resource allocation associated with a legacy TDD time slot can facilitate a non-FD communication mode during the corresponding time slot. The term "SBFD time slot" refers to a time slot (or time resource unit) having a resource allocation that includes a combination of uplink subbands, downlink subbands, and flexible subbands. Additionally, the resource allocation associated with an SBFD time slot can facilitate an FD communication mode.

[0167] Based on the second transmit slot format pattern 830, the UE 804 may receive downlink information from the network entity 802 in the downlink time slot 832, the first SBFD time slot 834, the second SBFD time slot 836, and / or the third SBFD time slot 838. The UE 804 may transmit uplink information to the network entity 802 in the first SBFD time slot 834, the second SBFD time slot 836, the third SBFD time slot 838, and / or the uplink time slot 840. Therefore, when compared to the first transmit slot format pattern 810, the second transmit slot format pattern 830 may reduce latency for downlink communications and / or uplink communications.

[0168] In some examples, the second transmit slot format pattern 830 can be a repeating periodic pattern. In some such examples, one repetition of the periodic pattern can be referred to as a cycle. For example, a cycle 850 associated with the second transmit slot format pattern 830 includes five time slots (e.g., time slot n to time slot n+4). The cycle 850 can be associated with a duration based on the time domain resources used for the corresponding time slot.

[0169] In some examples, the SBFD configuration 808 can indicate that the second transmit slot format mode 830 is a semi-static mode, which can also be referred to as a "semi-statically configured SBFD time resources and frequency resources" mode. In some such examples, the conversion of non-SBFD time slots (e.g., time slots configured with a non-SBFD resource mode) to SBFD time slots (e.g., time slots configured with an SBFD resource mode) continues until the change is deactivated or the network entity 802 provides a new transmit mode (e.g., via a new TDD time slot format indication). That is, the conversion to the second transmit slot format mode 830 can be "sticky" in that it remains active for more than one cycle.

[0170] Figure 9 Various example resource allocation patterns for time resource units (e.g., time slots, symbols, etc.) as presented herein are illustrated. Figure 9In the illustrated example, a first resource allocation pattern 900 for a time resource unit is dedicated to downlink traffic (e.g., a legacy downlink time resource unit). A second resource allocation pattern 902 for a time resource unit is dedicated to uplink traffic (e.g., a legacy uplink time resource unit). A third resource allocation pattern 904 for a time resource unit is flexible and can be assigned to downlink traffic or uplink traffic. In some examples, a non-FD communication mode can be indicated for time resource units associated with the first resource allocation pattern 900, the second resource allocation pattern 902, and the third resource allocation pattern 904.

[0171] like Figure 9 As shown, SBFD time resources can be configured with different resource allocation patterns. For example, the fourth resource allocation pattern 906 and the fifth resource allocation pattern 908 include a downlink subband and an uplink subband separated by a guard band. Figure 9 In the example of FIG4 , for the fourth resource allocation pattern 906, the downlink subband is larger than the uplink subband. For the fifth resource allocation pattern 908, the uplink subband is larger than the downlink subband. In some examples, the fourth resource allocation pattern 906 may also be referred to as a "downlink / uplink" time resource unit, a "DL / UL" time resource unit, or a "D / U" time resource unit. In some examples, the fifth resource allocation pattern 908 may also be referred to as an "uplink / downlink" time resource unit, a "UL / DL" time resource unit, or a "U / D" time resource unit.

[0172] The sixth resource allocation pattern 910 includes a flexible subband and an uplink subband separated by a guard band. Figure 9 In the example of FIG, the flexible subband is larger than the uplink subband for the sixth resource allocation pattern 910. In some examples, the sixth resource allocation pattern 910 may also be referred to as a "flexible / uplink" time resource unit, a "F / UL" time resource unit, or a "F / U" time resource unit.

[0173] The seventh resource allocation pattern 912 includes an upper downlink subband and a lower downlink subband, each separated from the uplink subband by a respective guard band.

[0174] The eighth resource allocation pattern 914 includes an upper uplink subband and a lower uplink subband, each separated from a downlink subband by a respective guard band.

[0175] The ninth resource allocation pattern 916 includes an upper flexible subband and a lower flexible subband, each separated from an uplink subband by a corresponding guard band. Flexible subbands other than the uplink subband can be used for uplink traffic or downlink traffic, excluding the guard band.

[0176] Similar to the seventh resource allocation pattern 912, the tenth resource allocation pattern 918 includes an upper downlink subband and a lower downlink subband, each separated from an uplink subband by a corresponding guard band. Figure 9 As shown, the subband sizes (e.g., the number of RBs in the frequency domain) of the uplink subband and the two downlink subbands are different between the seventh resource allocation pattern 912 and the tenth resource allocation pattern 918. In some examples, the seventh resource allocation pattern 912 and the tenth resource allocation pattern 918 can be referred to as "downlink / uplink / downlink" time resource units, "DL / UL / DL" time resource units, or "D / U / D" time resource units.

[0177] Similar to the eighth resource allocation pattern 914, the eleventh resource allocation pattern 920 includes an upper uplink subband and a lower uplink subband, each separated from a downlink subband by a corresponding guard band. Figure 9 As shown, the subband sizes of the downlink subband and the two uplink subbands are different between the eighth resource allocation pattern 914 and the eleventh resource allocation pattern 920. In some examples, the eighth resource allocation pattern 914 and the eleventh resource allocation pattern 920 can be referred to as "uplink / downlink / uplink" time resource units, "UL / DL / UL" time resource units, or "U / D / U" time resource units.

[0178] Similar to the ninth resource allocation pattern 916, the twelfth resource allocation pattern 922 includes an upper flexible subband and a lower flexible subband, each separated from an uplink subband by a corresponding guard band. Figure 9 As shown, the subband sizes of the uplink subband and the two flexible subbands are different between the ninth resource allocation pattern 916 and the twelfth resource allocation pattern 922. In some examples, the ninth resource allocation pattern 916 and the twelfth resource allocation pattern 922 can be referred to as "flexible / uplink / flexible" time resource units, "F / UL / F" time resource units, or "F / U / F" time resource units.

[0179] I understand. Figure 9 The resource allocation modes are examples of some resource allocation modes, and other examples may include additional or alternative resource allocation modes. In addition, from the perspective of the UE, it can be understood that uplink transmission is performed within the active uplink BWP and downlink reception is performed within the active downlink BWP.

[0180] In some examples, the UE may be configured Figure 9In some such examples, the resource allocation pattern for the time resource unit can be indicated via an index, such as a subband pattern index. For example, the first resource allocation pattern 900 can be indicated via an index of "1," the second resource allocation pattern 902 can be indicated via an index of "2," and so on.

[0181] In some examples, when a network entity converts legacy downlink timeslots to support SBFD operation, the SBFD configuration (e.g., Figure 8 The SBFD configuration 808) may indicate that an uplink subband is added within a time slot. Figure 9 In the illustrated example, the first resource allocation pattern 900 is associated with a legacy time slot, and the fourth resource allocation pattern 906, the seventh resource allocation pattern 912, and the tenth resource allocation pattern 918 are examples of resource allocations in which uplink subbands are added within the time slot. In some such examples, uplink communication within the uplink subband is permitted. Uplink communication outside the uplink subband is not permitted. Downlink reception within the downlink subband is permitted at the UE. The frequency location of the downlink subband may be known to the UE (e.g., an SBFD-aware UE). The frequency location of the downlink subband may be explicitly indicated to the UE or may be implicitly derived by the UE. In some examples, the location of the guard band may be explicitly indicated. In other examples, the location of the guard band may be implicitly derived, for example, based on the remaining RBs outside the downlink and uplink subbands.

[0182] In some examples, when a network entity converts legacy flexible time slots to support SBFD operation, the SBFD configuration (e.g., Figure 8 The SBFD configuration 808 may indicate that an uplink subband is added within a timeslot. In some such examples, uplink communication within the uplink subband is permitted. Additionally, different options for flexible subbands outside of the uplink subband may be supported.

[0183] In a first example option, the flexible subbands are considered downlink subbands. For example, converting legacy flexible time slots to support SBFD operation may result in a resource allocation pattern corresponding to the fourth resource allocation pattern 906, the seventh resource allocation pattern 912, or the tenth resource allocation pattern 918. Based on the first example option, uplink communications outside of the uplink subbands are not permitted. The frequency locations of the downlink subbands may be known to the UE (e.g., an SBFD-aware UE). In some such examples, downlink reception within the downlink subbands is permitted. Downlink reception outside of the downlink subbands may or may not be permitted.

[0184] In the second example option, the flexible subband remains flexible and can be assigned to downlink traffic or uplink traffic. For example, based on the second example option, converting the legacy flexible time slot to support SBFD operation can produce a resource allocation pattern corresponding to the sixth resource allocation pattern 910, the ninth resource allocation pattern 916, or the twelfth resource allocation pattern 922. Based on the second example option, from the perspective of the network entity, RBs outside the uplink subband can be used for uplink traffic or downlink traffic, excluding the guard band (if any). In addition, the traffic direction for all those RBs can be the same. For example, with reference to the ninth resource allocation pattern 916, if the network entity assigns the upper flexible subband for downlink traffic, the lower flexible subband is also assigned for downlink traffic. In addition, for all RBs outside the uplink subband, the UE can be restricted from using a single RB for both downlink and uplink traffic. In some examples, the frequency position of the downlink subband can be known to the UE (e.g., an SBFD-aware UE). Downlink reception within the downlink subband is permitted at the UE. In some examples, if a flexible subband is assigned to uplink traffic, the time resource unit can be treated as a legacy uplink time resource unit and the corresponding guard band can be removed. Therefore, if there is an uplink traffic burst, the entire resource of the time resource unit can be used for uplink traffic.

[0185] While examples for converting legacy flexible time slots to support SBFD operation include indicating uplink subbands, in other examples, SBFD configurations (e.g., Figure 8 SBFD configuration 808) can indicate the addition of a downlink subband within a timeslot. Based on the first example option, RBs outside the downlink subband can be assigned to uplink traffic. In some such examples, resource allocation for the corresponding time resource unit can correspond to a UL / DL / UL pattern, such as the eighth resource allocation pattern 914 and the eleventh resource allocation pattern 920. Based on the second example option, RBs outside the downlink subband can be assigned to uplink traffic or downlink traffic. In the example where RBs are assigned to downlink traffic, the corresponding time resource unit can be regarded as a legacy downlink time resource unit, and the corresponding guard band can be removed. Therefore, if there is a downlink traffic burst, all resources of the time resource unit can be used for downlink traffic.

[0186] In some examples, when a network entity converts legacy uplink timeslots to support SBFD operation, the SBFD configuration (e.g., Figure 8 The SBFD configuration 808) may indicate adding a downlink subband in a time slot. Figure 9In the illustrated example, the second resource allocation pattern 902 is associated with a legacy time slot, and the fifth resource allocation pattern 908, the eighth resource allocation pattern 914, and the eleventh resource allocation pattern 920 are examples of resource allocations in which a downlink subband is added within the time slot. In some such examples, downlink communication within the downlink subband is permitted. Downlink communication outside the downlink subband is not permitted. Uplink transmission within the uplink subband is permitted at the UE. The frequency location of the uplink subband may be known to the UE (e.g., an SBFD-aware UE). The frequency location of the uplink subband may be explicitly indicated to the UE or may be implicitly derived by the UE. In some examples, the location of the guard band may be explicitly indicated. In other examples, the location of the guard band may be implicitly derived, for example, based on the remaining RBs outside the uplink and downlink subbands.

[0187] The various aspects disclosed herein facilitate dynamically providing update indications to change resource allocations of semi-statically configured SBFD time resource units. Figure 8 In an example of , the network entity 802 may (e.g., via the SBFD configuration 808) convert the transmission mode from the first transmission time slot format mode 810 to the second transmission time slot format mode 830. Additionally, the second transmission time slot format mode 830 may be a semi-static configuration mode. The network entity 802 may then determine to change the resource allocation of one or more time resource units in the time resource units of the second transmission time slot format mode 830. Various aspects described herein provide techniques for dynamically updating the resource allocation of one or more time resource units. For example, the network entity may provide (e.g., via a DCI and / or a medium access control (MAC)-control element (MAC-CE)) an update indication indicating that the change Figure 8 The update indication may be used to change the resource allocation of the first SBFD time slot 834. In some examples, the update indication may cause the resource allocation of the first SBFD time slot 834 to fall back to its legacy TDD resource allocation. For example, the update indication may convert the first SBFD time slot 834 back to a legacy downlink time slot (e.g., the second downlink time slot 814). In other examples, the update indication may change the resource allocation to another SBFD mode or may change the subband size of one or more of the subbands.

[0188] In some examples, updates to one or more time resource units may be periodic (or semi-persistent / sticky). In other examples, updates to one or more time resource units may be aperiodic.

[0189] In some examples, the update indication may include a bitmap comprising one or more code points. In some examples, each code point in the bitmap may be associated with a different time resource unit. In some examples, the bitmap may include a code point for each time resource unit used to transmit the slot format pattern. In other examples, the bitmap may include a code point for each SBFD time slot used to transmit the slot format pattern.

[0190] In some examples, updates to the transmit slot format pattern may apply to a single component carrier (CC). In other examples, updates to the transmit slot format pattern may apply to multiple CCs via a CC list.

[0191] Figure 10 is a diagram illustrating the change of resource pattern at the UE as presented herein. Figure 10 In the illustrated example of , the time resource unit is a time slot. However, other examples may include other time resource units, such as symbols. Figure 10 An example of includes a transmit slot format pattern 1000 that includes eight time slots (e.g., slot n through slot n+7). The transmit slot format pattern 1000 includes a mix of TDD time slots that include legacy downlink time slots, legacy flexible time slots, and legacy uplink time slots. Figure 8 The example transmission slot format mode indication 806) is used to configure the transmission slot format mode 1000. The transmission slot format mode 1000 can be a periodic mode. Figure 10 In the example of FIG, the time slots of the transmission time slot format pattern 1000 are indicated to be used for the non-FD communication mode.

[0192] like Figure 10 As shown, the resource pattern associated with the transmit slot format pattern 1000 may be changed. For example, a SBFD configuration (such as Figure 8 The example SBFD configuration 808) may semi-statically configure a first resource pattern 1020. The first resource pattern 1020 includes a mix of legacy time slots and SBFD time slots. For example, the SBFD configuration may change time slot n from a legacy downlink time slot to a SBFD time slot, may change time slot n+3 and time slot n+4 from legacy flexible time slots to SBFD time slots, and may change time slot n+7 from a legacy uplink time slot to a SBFD time slot. Figure 10 In the example of , time slots configured as SBFD time slots are indicated for the FD communication mode, and the remaining time slots are indicated for the non-FD communication mode.

[0193] At a later time, the UE may receive an indication indicating a second resource mode 1040. The second resource mode 1040 converts one or more of the time slots of the first resource mode 1020 from SBFD time slots to legacy time slots, or from legacy time slots to SBFD time slots. For example, time slot n+1 and time slot n+2 are converted from legacy downlink time slots to SBFD time slots, and time slot n+4 is converted from an SBFD time slot to a legacy flexible time slot. The indication indicating the second resource mode may include a dynamic update indication that enables the network entity to update the resource allocation of the time slots via DCI and / or MAC-CE. That is, the dynamic update indication enables the network entity to adapt the resource pattern associated with time slots n to time slot n+7 more quickly than changes in resource allocation via RRC signaling.

[0194] Figure 11 An example communication flow 1100 between a network entity 1102 and a UE 1104 as presented herein is illustrated. One or more aspects described with respect to the network entity 1102 may be performed by a base station or a component of the network entity, such as a CU, DU, and / or RU. Figure 11 In the example of , UE 1104 is an SBFD-aware UE that supports the capability of communicating via SBFD operation. Figure 11 In the illustrated example of FIG, the communication flow 1100 facilitates dynamically updating a semi-statically configured resource pattern comprising one or more SBFD time resource units. Figure 1 One of the base stations 102 and / or Figure 4 4. Various aspects of UE 1104 may be implemented by Figure 1 One of the UEs 104 and / or Figure 4 UE 450 to achieve. Although Figure 11 Not shown in the illustrated example, it will be appreciated that in additional or alternative examples, the network entity 1102 and / or the UE 1104 can communicate with one or more other network entities or UEs.

[0195] exist Figure 11 In the illustrated example of FIG, the network entity 1102 sends a transmit slot format mode indication 1110 that is received by the UE 1104. The transmit slot format mode indication 1110 may indicate a first resource mode 1112. Aspects of the transmit slot format mode indication 1110 and the first resource mode 1112 may be similar to Figure 8 The transmit time slot format mode indication 806 and the first transmit time slot format mode 810 are shown.

[0196] exist Figure 11In the illustrated example, UE 1104 may perform an application process 1114 to apply first resource pattern 1112. For example, UE 1104 may configure one or more hardware components to receive downlink communications and / or send uplink communications based on first resource pattern 1112.

[0197] like Figure 11 As shown, network entity 1102 and UE 1104 may exchange communications 1120. Network entity 1102 and UE 1104 may exchange communications 1120 based on first resource pattern 1112.

[0198] exist Figure 11 In the illustrated example of FIG, the network entity 1102 may send an SBFD configuration 1130 that is received by the UE 1104. The SBFD configuration 1130 may convert one or more of the time slots of the first resource pattern 1112 from legacy TDD time slots to SBFD time slots. The SBFD configuration 1130 may indicate a second resource pattern 1132. Aspects of the SBFD configuration 1130 and the second resource pattern 1132 may be similar to Figure 8 SBFD configuration 808 and second transmit timeslot format mode 830 .

[0199] exist Figure 11 In the illustrated example, UE 1104 may perform an application process 1134 to apply second resource pattern 1132. For example, UE 1104 may configure one or more hardware components to receive downlink communications and / or send uplink communications based on second resource pattern 1132.

[0200] like Figure 11 As shown, network entity 1102 and UE 1104 may exchange communications 1140. Network entity 1102 and UE 1104 may exchange communications 1140 based on second resource pattern 1132.

[0201] exist Figure 11 In the illustrated example, after configuring the second resource pattern 1132, the network entity 1102 may detect a change in uplink traffic and / or downlink traffic. For example, the network entity may determine that an uplink traffic burst exists. In some such examples, the network entity may update a resource allocation pattern for one or more time resource units in the time resource units of the transmission slot format pattern to accommodate the change in uplink traffic and / or downlink traffic.

[0202] like Figure 11As shown, network entity 1102 may send an update indication 1150, which is received by UE 1104. Update indication 1150 may facilitate dynamically updating or modifying the resource allocation pattern of one or more time resource units of second resource pattern 1132. Update indication 1150 may indicate a third resource pattern 1152. In some examples, update indication 1150 may reduce the number of SBFD time slots between second resource pattern 1132 and third resource pattern 1152 by changing SBFD time slots to legacy TDD time slots. In some examples, update indication 1150 may increase the number of SBFD time slots between second resource pattern 1132 and third resource pattern 1152 by changing legacy TDD time slots to SBFD time slots. In some examples, update indication 1150 may change the subband size of the SBFD time slots. In some examples, update indication 1150 may change the resource allocation pattern of the SBFD time slots. In some examples, update indication 1150 may indicate that the time resource units have not changed. In some such examples, the resource allocation pattern of the time resource units remains the same between the second resource pattern 1132 and the third resource pattern 1152 .

[0203] In some examples, the update indication 1150 may be included in a field of the communication. For example, the update indication 1150 may be provided via a field of the DCI.

[0204] exist Figure 11 In the illustrated example, UE 1104 may perform an application process 1154 to apply third resource pattern 1152. For example, UE 1104 may configure one or more hardware components to receive downlink communications and / or send uplink communications based on third resource pattern 1152.

[0205] like Figure 11 As shown, network entity 1102 and UE 1104 may exchange communications 1160. Network entity 1102 and UE 1104 may exchange communications 1160 based on third resource pattern 1152.

[0206] In some examples, update indication 1150 can indicate that updates to the resource pattern are semi-static (e.g., periodic or "sticky") and follow the periodicity of the original pattern (e.g., first resource pattern 1112). In some examples, update indication 1150 includes a bitmap 1170 that includes code points for one or more of the time resource units of second resource pattern 1132. In some examples, bitmap 1170 includes a code point for each SBFD time resource unit of second resource pattern 1132. For example, and with reference to Figure 10For example, bitmap 1170 may include four code points corresponding to time slot n, time slot n+3, time slot n+4, and time slot n+7. In some such examples, because bitmap 1170 does not include code points for non-SBFD time resource units, overhead can be reduced.

[0207] In some examples, the bitmap 1170 includes a code point for each time resource unit of the second resource pattern 1132. For example, and with reference to Figure 10 In some such examples, including a code point for each time slot enables the addition of a new SBFD time resource unit. For example, and with reference to Figure 10 For example, time slot n+2 may be converted from a legacy downlink time slot to a SBFD time slot.

[0208] In some examples, the update indication 1150 includes a mode identifier 1172 ("mode ID") indicating the configured periodic mode. For example, and with reference to Figure 10 For example, a first value of the pattern identifier 1172 may indicate a resource pattern corresponding to the second resource pattern 1040, a second value of the pattern identifier 1172 may indicate a resource pattern including eight SBFD time resource units, and so on.

[0209] In some examples, for each cycle, update indication 1150 includes an offset 1174 and the length of the update symbol (e.g., symbol length 1176). In some examples, offset 1174 can be a fixed (e.g., or static) value. In some examples, offset 1174 can be based on the capabilities of UE 1104. In some examples, offset 1174 can be relative to receiving update indication 1150.

[0210] In some examples, offset 1174 may be relative to application time 1156. Application time 1156 may refer to the amount of time associated with applying third resource pattern 1152. For example, application time 1156 may include the time to decode update indication 1150, tune filters, and the like. Application time 1156 may be measured in terms of symbols (e.g., N symbols), time (e.g., kms), and the like. In some examples, application time 1156 may be a fixed (e.g., or static) value based on receiving update indication 1150. In some examples, application time 1156 may be a fixed (e.g., or static) value based on feedback in response to update indication 1150. For example, UE 1104 may send feedback 1158 after receiving update indication 1150. Feedback 1158 may include HARQ feedback, such as an ACK. In examples where application time 1156 is based on symbols (e.g., N symbols), the value may depend on update indication 1150, feedback 1158, or the SCS of the downlink / uplink BWP.

[0211] In some examples, the application time 1156 may be configured. For example, the network entity 1102 may send a configuration 1108 that is received by the UE 1104. In some examples, the network entity 1102 sends the configuration 1108 via RRC signaling. In some examples, the network entity 1102 sends the configuration 1108 via a scheduling DCI. In some examples, the network entity 1102 sends the configuration 1108 via a MAC-CE.

[0212] In some examples, update indication 1150 may indicate that the update to the resource pattern is aperiodic. In some such examples, the change may apply to one occasion or to multiple occasions. In some examples, update indication 1150 includes window 1180. Window 1180 may indicate that the change applies X ms and the last Y time resource units (e.g., time slots, symbols, etc.) after receiving update indication 1150. In some examples, the changes applied within the window may be indicated via a bitmap (such as bitmap 1170). In some such examples, the bitmap may include codepoints for SBFD time resource units. In other examples, the bitmap may include codepoints for SBFD time resource units and non-SBFD time resource units. In some examples, the applied changes may apply to all time resource units within window 1180. In some examples, within window 1180, the changes may be indicated via an offset and the length of the update symbol (such as offset 1174 and symbol length 1176).

[0213] In some examples, update indication 1150 can indicate the indicated timing or location at which the change applies. For example, update indication 1150 can include an offset, such as offset 1174. In some such examples, the change can be applied to the location based on offset 1174 and relative to receiving update indication 1150. For example, if offset 1174 is set to 5 time resource units (e.g., time slots, symbols, etc.) and UE 1104 receives update indication 1150 in time slot n, UE 1104 can apply the update to time slot n+5.

[0214] In some examples, network entity 1102 may explicitly indicate an update location associated with update indication 1150. Network entity 1102 may explicitly indicate the update location via DCI and / or MAC-CE.

[0215] In some examples, the network entity 1102 may provide the update indication 1150 via a group-common DCI, such as via an SFI. The network entity 1102 may provide the update indication 1150 via a group-common DCI for periodic updates or aperiodic updates.

[0216] In some examples, the network entity 1102 may provide an update indication 1150 for a periodic update or an aperiodic update via DCI. The DCI may include scheduled DCI, non-scheduled DCI (e.g., which may have more bits available to include the update indication 1150 than scheduled DCI), or a new type of DCI. In some examples, the update indication 1150 received via the DCI may be a "sticky" update, and the change remains in effect until the UE 1104 receives another update indication. In some examples, if the DCI schedules multiple transmissions for multiple time slots, the change may remain in effect for the time slot in which the DCI is received, or may remain in effect for multiple time slots.

[0217] In some examples, the network entity 1102 may provide an update indication 1150 for a periodic update or an aperiodic update via a MAC-CE. In some examples, the update indication 1150 received via the MAC-CE may be a "sticky" update, and the change remains in effect until the UE 1104 receives another update indication. In some examples, the update indication 1150 is associated with a timer. For example, the MAC-CE may include a timer value 1178 indicating the amount of time the change is valid. In some such examples, after the timer value 1178 expires, the resource mode falls back to a semi-statically configured resource mode (e.g., the second resource mode 1132) or falls back to a configured (or pre-configured) resource mode.

[0218] In some examples, the network entity 1102 may implicitly indicate an update location associated with the update indication 1150. For example, the update location may be implied via a scheduled channel or reference signal (such as a PDSCH scheduled via DCI). For example, DCI scheduling data may be associated with a channel / reference signal. For example, if the scheduled channel / reference signal symbol corresponds to a common pattern indication, the UE 1104 may determine to change the resource allocation mode for the symbol to its legacy resource allocation. In some examples, the symbol-level bitmap may indicate whether the corresponding symbol remains the same (e.g., unchanged) or falls back to its legacy resource allocation. In some examples, the symbol-level bitmap may include all SBFD symbols. In other examples, the symbol-level bitmap may include SBFD symbols and non-SBFD symbols.

[0219] In some examples, if the DCI schedules multiple PDSCH transmissions and / or multiple PUSCH transmissions, the change may remain in effect for the timeslots in which the multiple transmissions are scheduled or for multiple scheduled timeslots.

[0220] In some examples, the third resource pattern 1152 may be applied to a single component carrier (CC). In other examples, the third resource pattern 1152 may be applied to multiple CCs. In some examples, multiple CCs may be indicated via a CC list 1182. For example, Figure 11 CC list 1182 includes four CCs (e.g., CC1, CC2, CC4, and CC7). In some examples, CC list 1182 may include activated CCs and deactivated CCs. In some such examples, UE 1104 may apply the update to the activated CCs. In some examples, CC list 1182 may include activated CCs. In some such examples, the CCs included in CC list 1182 (e.g., CC1, CC2, CC4, and CC7) are each activated CCs. In some examples, CC list 1182 may indicate which CCs the third resource pattern 1152 applies to. For example, CC list 1182 may indicate that the update applies to CC1 and CC4. In some examples, UE 1104 may receive update indication 1150 via a primary CC or a reference CC, but the update applies to a secondary CC. For example, UE 1104 may receive communication 1140 via CC1, but the update applies to CC2, CC4, and / or CC7.

[0221] As described above, aspects disclosed herein facilitate dynamically updating a semi-statically configured resource pattern comprising one or more SBFD time resource units. Figure 12 Example updates that may be made to time resource units that are configured as legacy downlink time resource units in at least one of the first resource pattern 1200 or the second resource pattern 1202 are illustrated. Figure 12As shown, the first resource pattern 1200 includes two legacy downlink time resource units (eg, time slots). Aspects of the first resource pattern 1200 may be similar to Figure 10 Transmit slot format mode 1000 and / or Figure 11 The first resource model 1200 can be converted into a second resource model 1202. Aspects of the second resource model 1202 can be similar to Figure 10 The first resource mode 1020 and / or Figure 11 The second resource mode 1132. Figure 12 As shown in , time slot n is converted from a legacy downlink time slot to a SBFD time slot. Figure 12 In the example of FIG. 1 , the resource allocation pattern associated with time slot n of the second resource pattern 1202 corresponds to Figure 9 The seventh resource allocation mode 912.

[0222] Figure 12 The examples illustrate five different updates (e.g., cases) that may be indicated when SBFD is configured in legacy downlink time resource units (e.g., time slots, symbols, etc.). In the first update 1210, the resource allocation pattern of the SBFD time resource unit is unchanged. For example, in case 1, the resource allocation pattern for time slot n is still Figure 9 In some examples, if an update indication is excluded or not provided for a particular time resource unit, the default update may be to not change the corresponding time resource unit.

[0223] In the second update 1212, the resource allocation mode of the SBFD time resource unit falls back to its legacy mode. For example, in case 2, the resource allocation mode of time slot n is converted from SBFD time slot to legacy downlink mode.

[0224] In the third update 1214, the resource allocation pattern of the SBFD time resource unit includes a change in the size of at least one of the uplink subband and the downlink subband. For example, the resource allocation pattern associated with Case 3 includes a larger downlink subband and a smaller uplink subband, which corresponds to Figure 9 The tenth resource allocation mode 918.

[0225] In the fourth update 1216, the resource allocation pattern of the SBFD time resource unit includes different sub-band patterns. For example, the resource allocation pattern associated with Case 4 includes a single downlink sub-band and a single uplink sub-band, as combined with Figure 9 The fourth resource allocation mode 906 is described.

[0226] In the fifth update 1218, the resource allocation pattern of the SBFD time resource unit includes changing the time resource unit to a different type of legacy time resource unit (e.g., changing to a different resource allocation pattern than when the time resource unit is semi-statically configured as a SBFD time resource unit). For example, the resource allocation pattern associated with case 5 includes a legacy uplink time resource unit, such as in conjunction with Figure 9 In another example, the resource allocation mode of the SBFD time resource unit may include converting the time resource unit into a legacy flexible time resource unit, such as in combination with Figure 9 The third resource allocation mode 904 is described.

[0227] like Figure 12 As shown, the update indication may also add new SBFD time resource units. For example, time slot n+1 is still a legacy downlink time slot in the first resource pattern 1200 and the second resource pattern 1202. The example sixth update 1220 changes the resource allocation mode of time slot n+1 to a SBFD time slot. Figure 12 In the example of , the resource allocation pattern for time slot n+1 includes adding a single uplink subband, such as in combination with Figure 9 The seventh resource allocation mode 912 is described.

[0228] although Figure 12 The examples include six different situations, but other examples may include additional or alternative situations.

[0229] In some examples, the different updates that can be applied to the time resource unit may depend on the size of the update indicator. For example, if the update indicator is set to a 1-bit indication, two cases can be indicated. In another example, if the update indicator is set to a 2-bit indication, up to four cases can be indicated. Additionally, if the update indicator is set to a 3-bit indication, up to eight cases can be indicated.

[0230] exist Figure 12 In the illustrated example, a first mapping 1230 is included that maps the value of the 1-bit indication 1232 to different cases. For example, a first value of "0" is mapped to case 1 (e.g., no change). In addition, a second value of "1" is mapped to case 2 (e.g., fallback to legacy resource allocation).

[0231] exist Figure 12 In the illustrated example, the second mapping 1240 maps the values ​​of the 2-bit indication 1242 to different corresponding cases. For example, the first value "00" and the second value "01" are mapped to the same cases as in the first mapping 1230. In addition, the third value "10" is mapped to case 3 (e.g., a change in subband size), and the fourth value "11" is mapped to case 6 (e.g., adding an SBFD time resource unit).

[0232] exist Figure 12 In the illustrated example of , the third mapping 1250 maps the value of the 3-bit indication 1252 to different corresponding cases. Figure 12 In the example of , the first four values ​​of the 3-bit indication 1252 are mapped to the same cases as in the second mapping 1240. Additionally, the fifth value "100" is mapped to case 4 (e.g., different subband mode), and the sixth value "101" is mapped to case 5 (e.g., overriding the original legacy type).

[0233] In some examples, the network entity may configure a mapping between the update indication value and the situation. For example, the network entity may indicate that the update indication is 2 bits and indicate a mapping of each of four values ​​to a corresponding situation. In some examples, the mapping between the update indication value and the situation may be preconfigured at the UE.

[0234] Figure 22 is a diagram illustrating an update to a resource pattern including downlink time resource units as presented herein. Figure 22 In the illustrated example of FIG, the first resource pattern 2200 includes six time resource units (eg, time slot n to time slot n+5), and each time resource unit is used for downlink. The second resource pattern 2210 illustrates the use of a SBFD configuration (such as Figure 8 The resource mode for the six time resource units is then used for the SBFD configuration 808. Figure 22 As shown in the example of , the second resource pattern 2210 includes two SBFD time resource units, followed by one downlink time resource unit, and then three SBFD time resource units.

[0235] exist Figure 22 In the illustrated example, the third resource pattern 2220 illustrates that in the application update indication (such as Figure 11 The example update indicates 1150) followed by the resource mode for six time resource units. Figure 22 As shown, the update indicates that the resource allocation pattern for each of the six time slots has been changed. Figure 22 In the illustrated example, the update indication includes a bitmap 2230 including six code points, each code point being mapped to a corresponding time resource unit. For example, the first code point 2232 is mapped to time slot n, the second code point 2234 is mapped to time slot n+1, and so on. Figure 22 As shown, each code point in bitmap 2230 is three bits. Table 2240 maps the values ​​of the 3-bit code points to cases such as Figure 12As an example, based on table 2240, the first code point 2232 ("000") maps to case 1 where there is no change in the time resource. Similar mappings between the values ​​of table 2240 and different cases can be used to determine the updates to be applied to the corresponding time resource unit.

[0236] although Figure 22 Examples include 3-bit code points, but other examples may include n-bit code points, where n is an integer and different cases may be indicated by the n bits.

[0237] Figure 13 Example updates that may be made to time resources configured as legacy uplink time resource units in at least one of the first resource pattern 1300 or the second resource pattern 1302 are illustrated. Figure 13 As shown, the first resource pattern 1300 includes two legacy uplink time resource units (e.g., time slots). Aspects of the first resource pattern 1300 may be similar to Figure 10 Transmit slot format mode 1000 and / or Figure 11 The first resource model 1300 can be converted into a second resource model 1302. Aspects of the second resource model 1302 can be similar to Figure 10 The first resource mode 1020 and / or Figure 11 The second resource mode 1132. Figure 13 As shown in , time slot n is converted from a legacy uplink time slot to a SBFD time slot. Figure 13 In the example of FIG. 1 , the resource allocation pattern associated with time slot n of the second resource pattern 1302 corresponds to Figure 9 The eighth resource allocation mode 914.

[0238] Figure 13 The examples illustrate five different updates (e.g., scenarios) that may be indicated when SBFD is configured in legacy uplink time resource units (e.g., time slots, symbols, etc.). In the first update 1310, the resource allocation pattern of the SBFD time resource unit is unchanged. For example, in scenario 1, the resource allocation pattern for time slot n is still Figure 9 In some examples, if an update indication is excluded or not provided for a particular time resource unit, the default update may be to not change the corresponding time resource unit.

[0239] In the second update 1312, the resource allocation mode of the SBFD time resource unit falls back to its legacy mode. For example, in case 2, the resource allocation mode of time slot n is converted from SBFD time slot to legacy uplink mode.

[0240] In the third update 1314, the resource allocation pattern of the SBFD time resource unit includes a change in the size of at least one of the uplink subband and the downlink subband. For example, the resource allocation pattern associated with Case 3 includes a larger uplink subband and a smaller downlink subband, which corresponds to Figure 9 The eleventh resource allocation mode 920.

[0241] In the fourth update 1316, the resource allocation pattern of the SBFD time resource unit includes different sub-band patterns. For example, the resource allocation pattern associated with Case 4 includes a single downlink sub-band and a single uplink sub-band, as combined with Figure 9 The fifth resource allocation mode 908 is described.

[0242] In the fifth update 1318, the resource allocation pattern of the SBFD time resource unit includes changing the time resource unit to a different type of legacy time resource unit (e.g., covering the original legacy pattern of the time resource unit). For example, the resource allocation pattern associated with case 5 includes a legacy downlink time resource unit, such as in conjunction with Figure 9 In another example, the resource allocation mode of the SBFD time resource unit may include converting the time resource unit into a legacy flexible time resource unit, such as in combination with Figure 9 The third resource allocation mode 904 is described.

[0243] like Figure 13 As shown, the update indication may also add new SBFD time resource units. For example, time slot n+1 is still a legacy uplink time slot in the first resource pattern 1300 and the second resource pattern 1302. The example sixth update 1320 changes the resource allocation mode of time slot n+1 to a SBFD time slot. Figure 13 In the example of time slot n+1, the resource allocation pattern includes adding a single downlink subband, such as in combination with Figure 9 The eighth resource allocation mode 914 is described.

[0244] although Figure 13 The example includes six different situations, but other examples may include additional or alternative situations.

[0245] In some examples, the different updates that can be applied to the time resource unit may depend on the size of the update indicator. For example, if the update indicator is set to a 1-bit indication, two cases can be indicated. In another example, if the update indicator is set to a 2-bit indication, up to four cases can be indicated. Additionally, if the update indicator is set to a 3-bit indication, up to eight cases can be indicated.

[0246] exist Figure 13In the illustrated example, a first mapping 1330 is included that maps the value of a 1-bit indication 1332 to different cases. For example, a first value of "0" is mapped to case 1 (e.g., no change). Additionally, a second value of "1" is mapped to case 2 (e.g., fallback to legacy resource allocation).

[0247] exist Figure 13 In the illustrated example, the second mapping 1340 maps the values ​​of the 2-bit indication 1342 to different corresponding cases. For example, the first value "00" and the second value "01" are mapped to the same cases as in the first mapping 1330. In addition, the third value "10" is mapped to case 3 (e.g., a change in subband size), and the fourth value "11" is mapped to case 6 (e.g., adding an SBFD time resource unit).

[0248] exist Figure 13 In the illustrated example of , the third mapping 1350 maps the value of the 3-bit indication 1352 to different corresponding cases. Figure 13 In the example of , the first four values ​​of the 3-bit indication 1352 are mapped to the same cases as in the second mapping 1340. Additionally, the fifth value "100" is mapped to case 4 (e.g., different subband mode), and the sixth value "101" is mapped to case 5 (e.g., overriding the original legacy type).

[0249] In some examples, the network entity may configure a mapping between the update indication value and the situation. For example, the network entity may indicate that the update indication is 2 bits and indicate a mapping of each of four values ​​to a corresponding situation. In some examples, the mapping between the update indication value and the situation may be preconfigured at the UE.

[0250] Figure 23 is a diagram illustrating an update to a resource pattern including uplink time resource units as presented herein. Figure 23 In the illustrated example of FIG, the first resource pattern 2300 includes six time resource units (eg, time slot n to time slot n+5), and each time resource unit is used for uplink. The second resource pattern 2310 illustrates the use of a SBFD configuration (such as Figure 8 The resource mode for the six time resource units is then used for the SBFD configuration 808. Figure 23 As shown in the example of , the second resource pattern 2310 includes two SBFD time resource units, followed by one uplink time resource unit, and then three SBFD time resource units.

[0251] exist Figure 23 In the illustrated example of , the third resource pattern 2320 illustrates that in an application update indication (such as Figure 11 The example update indicates 1150) followed by the resource mode for six time resource units. Figure 23 As shown, the update indicates that the resource allocation pattern for each of the six time slots has been changed. Figure 23 In the illustrated example, the update indication includes a bitmap 2330 including six code points, each code point being mapped to a corresponding time resource unit. For example, the first code point 2332 is mapped to time slot n, the second code point 2334 is mapped to time slot n+1, and so on. Figure 23 As shown, each code point in bitmap 2330 is three bits. Table 2340 maps the values ​​of the 3-bit code points to cases such as Figure 13 As an example, based on table 2340, the first code point 2332 ("000") maps to case 1 where there is no change in the time resource. Similar mappings between the values ​​of table 2340 and different cases can be used to determine the updates to be applied to the corresponding time resource unit.

[0252] although Figure 23 Examples include 3-bit code points, but other examples may include n-bit code points, where n is an integer and different cases may be indicated by the n bits.

[0253] Figure 14 and Figure 15 Example updates that may be made to time resources configured as legacy flexible time resource units in at least one of the first resource mode or the second resource mode are illustrated. Figure 14 In the example shown in FIG. 1 , a combination of Figure 9 The first example option discussed. For example, the legacy flexible time resource unit is converted to a SBFD time resource unit comprising two downlink subbands and a single uplink subband. Figure 15 In the example shown in FIG. 1 , a combination of Figure 9 The second example option discussed is that, for example, the legacy flexible time resource unit is converted to a SBFD time resource comprising two flexible subbands and a single uplink subband.

[0254] like Figure 14 As shown, the first resource pattern 1400 includes two legacy flexible time resource units (eg, time slots). Aspects of the first resource pattern 1400 may be similar to Figure 10 Transmit slot format mode 1000 and / or Figure 11 The first resource model 1400 can be converted into a second resource model 1402. Aspects of the second resource model 1402 can be similar to Figure 10 The first resource mode 1020 and / or Figure 11 The second resource mode 1132. Figure 14 As shown in Figure 1, time slot n is converted from a legacy flexible time slot to a SBFD time slot. Figure 14In the example of FIG. 1 , the resource allocation pattern associated with time slot n of the second resource pattern 1402 corresponds to Figure 9 The seventh resource allocation mode 912.

[0255] Figure 14 The example of illustrates six different updates (e.g., scenarios) that can be indicated when configuring SBFD in legacy flexible time resource units (e.g., time slots, symbols, etc.) and employing the first example option. In the first update 1410, the resource allocation pattern of the SBFD time resource unit does not change. For example, in scenario 1, the resource allocation pattern for time slot n is still Figure 9 In some examples, if an update indication is excluded or not provided for a particular time resource unit, the default update may be to not change the corresponding time resource unit.

[0256] In the second update 1412, the resource allocation mode of the SBFD time resource unit falls back to its legacy mode. For example, in case 2, the resource allocation mode of time slot n is converted from SBFD time slot to the legacy flexible mode.

[0257] exist Figure 14 In the example of FIG, the third update 1414 and the fourth update 1416 include changing the resource allocation mode of the SBFD time resource unit to a different legacy mode. For example, the third update 1414 (e.g., case 3) includes converting the time resource unit to a legacy downlink time resource unit, such as in combination with Figure 9 The fourth update 1416 (eg, case 4) includes converting the time resource units to legacy uplink time resource units, as described in conjunction with the first resource allocation pattern 900. Figure 9 The second resource allocation mode 902 is described.

[0258] In the fifth update 1418, the resource allocation pattern of the SBFD time resource unit includes a change in the size of at least one subband. For example, the resource allocation pattern associated with Case 5 includes a larger downlink subband and a smaller uplink subband, which corresponds to Figure 9 The tenth resource allocation mode 918.

[0259] In the sixth update 1420, the resource allocation pattern of the SBFD time resource unit includes different sub-band patterns. For example, the resource allocation pattern associated with Case 6 includes a single downlink sub-band and a single uplink sub-band, as combined with Figure 9 The fourth resource allocation mode 906 is described.

[0260] like Figure 14As shown, the update indication may also add new SBFD time resource units. For example, time slot n+1 is still a legacy flexible time slot in the first resource mode 1400 and the second resource mode 1402. The example seventh update 1422 changes the resource allocation mode of time slot n+1 to a SBFD time slot. Figure 14 In the example of time slot n+1, the resource allocation mode includes changing to D / U / D mode, such as combining Figure 9 The seventh resource allocation mode 912 is described.

[0261] although Figure 14 The examples include seven different situations, but other examples may include additional or alternative situations.

[0262] In some examples, the different updates that can be applied to the time resource unit may depend on the size of the update indicator. For example, if the update indicator is set to a 1-bit indication, two cases can be indicated. In another example, if the update indicator is set to a 2-bit indication, up to four cases can be indicated. Additionally, if the update indicator is set to a 3-bit indication, up to eight cases can be indicated.

[0263] exist Figure 14 In the illustrated example, a first mapping 1430 is included that maps the value of a 1-bit indication 1432 to different cases. For example, a first value of "0" is mapped to case 1 (e.g., no change). Additionally, a second value of "1" is mapped to case 2 (e.g., fallback to legacy resource allocation).

[0264] exist Figure 14 In the illustrated example, the second mapping 1440 maps the values ​​of the 2-bit indication 1442 to different corresponding cases. For example, the first value "00" and the second value "01" are mapped to the same cases as in the first mapping 1430. In addition, the third value "10" is mapped to case 5 (e.g., a change in subband size), and the fourth value "11" is mapped to case 7 (e.g., adding an SBFD time resource unit).

[0265] exist Figure 14 In the illustrated example of , the third mapping 1450 maps the value of the 3-bit indication 1452 to different corresponding cases. Figure 14 In the example of , the first four values ​​of the 3-bit indication 1452 are mapped to the same cases as in the second mapping 1440. In addition, the fifth value "100" is mapped to case 3, and the sixth value "101" is mapped to case 4, each of which is associated with overriding the original legacy type. The seventh value "110" is mapped to case 6 (e.g., different subband mode).

[0266] If combined Figure 12As described, in some examples, the network entity may configure a mapping between the update indication value and the situation. For example, the network entity may indicate that the update indication is 2 bits and indicate a mapping of each of four values ​​to a corresponding situation. In some examples, the mapping between the update indication value and the situation may be preconfigured at the UE.

[0267] Figure 24 is a diagram illustrating an update to a resource pattern including flexible time resource units as presented herein. Figure 24 In the illustrated example of FIG, the first resource pattern 2400 includes seven time resource units (eg, time slot n to time slot n+6), and each time resource unit is flexible. The second resource pattern 2410 illustrates the flexible use of the SBFD configuration (eg, Figure 8 The resource mode for seven time resource units is then used after the SBFD configuration 808. Figure 24 As shown in the example of , the second resource pattern 2410 includes three SBFD time resource units, followed by one flexible time resource unit, and then three SBFD time resource units.

[0268] exist Figure 24 In the illustrated example of , the third resource pattern 2420 illustrates that in an application update indication (such as Figure 11 The example update indicates 1150) followed by a resource pattern for seven time resource units. Figure 24 As shown, the update indicates that the resource allocation pattern for one or more of the time slots has been changed. Figure 24 In the illustrated example, the update indication includes a bitmap 2430 including seven code points, each code point being mapped to a corresponding time resource unit. For example, the first code point 2432 is mapped to time slot n, the second code point 2434 is mapped to time slot n+1, and so on. Figure 24 As shown, each code point in bitmap 2430 is two bits. Table 2440 maps the values ​​of the 2-bit code points to cases such as Figure 14 As an example, based on table 2440, the first code point 2432 ("00") maps to case 1 where there is no change in the time resource. Similar mappings between the values ​​of table 2440 and different cases can be used to determine the updates to be applied to the corresponding time resource unit.

[0269] although Figure 24 Examples include 2-bit code points, but other examples may include n-bit code points, where n is an integer and different cases may be indicated by n bits.

[0270] exist Figure 15 In the illustrated example of , the first resource pattern 1500 includes two legacy flexible time resource units (eg, time slots). Aspects of the first resource pattern 1500 may be similar to Figure 10 Transmit slot format mode 1000 and / or Figure 11 The first resource model 1500 can be converted into a second resource model 1502. Aspects of the second resource model 1502 can be similar to Figure 10 The first resource mode 1020 and / or Figure 11 The second resource mode 1132. Figure 15 As shown in Figure 1, time slot n is converted from a legacy flexible time slot to a SBFD time slot. Figure 15 In the example of FIG. 1 , the resource allocation pattern associated with time slot n of the second resource pattern 1502 corresponds to Figure 9 A ninth resource allocation mode 916 (eg, F / U / F mode) is provided.

[0271] Figure 15 The example of illustrates seven different updates (e.g., situations) that can be indicated when configuring SBFD in legacy flexible time resource units (e.g., time slots, symbols, etc.) and adopting the second example option. In the first update 1510, the resource allocation pattern of the SBFD time resource unit does not change. For example, the resource allocation pattern for time slot n is still Figure 9 The ninth resource allocation mode 916. In some examples, if an update indication is excluded or not provided for a particular time resource unit, the default update may be to not change the corresponding time resource unit.

[0272] In the second update 1512, the resource allocation mode of the SBFD time resource unit falls back to its legacy mode. For example, in case 2, the resource allocation mode of time slot n is converted from SBFD time slot to the legacy flexible mode.

[0273] exist Figure 15 In the example of , the third update 1514 and the fourth update 1516 include changing the resource allocation mode of the SBFD time resource unit to a different legacy mode. For example, the third update 1514 (e.g., case 3) includes converting the time resource unit to a legacy uplink time resource unit, such as in combination with Figure 9 The fourth update 1516 (eg, case 4) includes converting the time resource units to legacy uplink time resource units, as described in conjunction with the second resource allocation pattern 902. Figure 9 The first resource allocation pattern 900 is described.

[0274] In the fifth update 1518, the resource allocation pattern of the SBFD time resource unit includes a change in the size of at least one subband. For example, the resource allocation pattern associated with Case 5 includes a larger flexible subband and a smaller uplink subband, which corresponds to Figure 9 The twelfth resource allocation mode 922.

[0275] exist Figure 15 In the example of FIG, the sixth update 1520 and the seventh update 1522 include changing the resource allocation mode of the SBFD time resource unit to a different subband mode. For example, the sixth update 1520 (eg, case 6) includes converting the resource allocation mode to a D / U / D mode, such as in combination with Figure 9 The seventh update 1522 (e.g., case 7) includes converting the resource allocation mode to F / U mode, as described in conjunction with Figure 9 The sixth resource allocation mode 910 is described.

[0276] like Figure 15 As shown, the update indication may also add new SBFD time resource units. For example, time slot n+1 is still a legacy flexible time slot in the first resource mode 1500 and the second resource mode 1502. The example eighth update 1524 changes the resource allocation mode of time slot n+1 to a SBFD time slot. Figure 15 In the example of time slot n+1, the resource allocation mode includes changing to F / U / F mode, such as combining Figure 9 The ninth resource allocation mode 916 is described.

[0277] although Figure 15 The example includes eight different situations, but other examples may include additional or alternative situations.

[0278] In some examples, the different updates that can be applied to the time resource unit may depend on the size of the update indicator. For example, if the update indicator is set to a 1-bit indication, two cases can be indicated. In another example, if the update indicator is set to a 2-bit indication, up to four cases can be indicated. Additionally, if the update indicator is set to a 3-bit indication, up to eight cases can be indicated.

[0279] exist Figure 15 In the illustrated example, a first mapping 1530 is included that maps the value of a 1-bit indication 1532 to different cases. For example, a first value of "0" is mapped to case 1 (e.g., no change). Additionally, a second value of "1" is mapped to case 2 (e.g., fallback to legacy resource allocation).

[0280] exist Figure 15 In the illustrated example, the second mapping 1540 maps the values ​​of the 2-bit indication 1542 to different corresponding cases. For example, the first value "00" and the second value "01" are mapped to the same cases as in the first mapping 1530. In addition, the third value "10" is mapped to case 5 (e.g., a change in subband size), and the fourth value "11" is mapped to case 8 (e.g., adding an SBFD time resource unit).

[0281] exist Figure 15 In the illustrated example of , the third mapping 1550 maps the value of the 3-bit indication 1552 to different corresponding cases. Figure 15 In the example of , the first four values ​​of the 3-bit indication 1552 are mapped to the same cases as in the second mapping 1540. In addition, the fifth value "100" is mapped to case 3, and the sixth value "101" is mapped to case 4, each of which is associated with overriding the original legacy type. The seventh value "110" is mapped to case 6, and the eighth value "110" is mapped to case 7, each of which is associated with a different sub-band frequency band.

[0282] If combined Figure 12 As described, in some examples, the network entity may configure a mapping between the update indication value and the situation. For example, the network entity may indicate that the update indication is 2 bits and indicate a mapping of each of four values ​​to a corresponding situation. In some examples, the mapping between the update indication value and the situation may be preconfigured at the UE.

[0283] Figure 25 is a diagram illustrating an update to a resource pattern including flexible time resource units as presented herein. Figure 25 In the illustrated example of FIG, the first resource pattern 2500 includes eight time resource units (eg, time slot n to time slot n+7), and each time resource unit is flexible. The second resource pattern 2510 illustrates the use of a flexible resource unit when an SBFD configuration (such as Figure 8 The resource mode for eight time resource units is then used after the SBFD configuration 808. Figure 25 As shown in the example of , the second resource pattern 2510 includes five SBFD time resource units, followed by one flexible time resource unit, and then two SBFD time resource units.

[0284] exist Figure 25 In the illustrated example of , the third resource pattern 2520 illustrates that in an application update indication (such as Figure 11 The example update indicates 1150) followed by a resource pattern for eight time resource units. Figure 25 As shown, the update indicates that the resource allocation pattern for one or more of the time slots has been changed. Figure 25 In the illustrated example, the update indication includes a bitmap 2530 including eight code points, each of which is mapped to a corresponding time resource unit. For example, the first code point 2532 is mapped to time slot n, the second code point 2534 is mapped to time slot n+1, and so on. Figure 25 As shown, each code point in bitmap 2530 is two bits. Table 2540 maps the values ​​of the 2-bit code points to cases such as Figure 15As an example, based on table 2540, the first code point 2532 ("00") maps to case 1 where there is no change in the time resource. Similar mappings between the values ​​of table 2540 and different cases can be used to determine the updates to be applied to the corresponding time resource unit.

[0285] although Figure 25 Examples include 2-bit code points, but other examples may include n-bit code points, where n is an integer and different cases may be indicated by n bits.

[0286] Figure 26 is a diagram illustrating an update to a resource pattern including a mix of downlink time resource units, flexible time resource units, and uplink time resource units as presented herein. Figure 26 In the illustrated example, the first resource pattern 2600 includes eight time resource units (e.g., time slot n to time slot n+7), and each time resource unit is used for downlink, used for uplink, or is flexible. In the illustrated example, the first two flexible time resource units (e.g., time slot n+2 and time slot n+3) are associated with the first example option for flexible time resource units, as shown in conjunction with Figure 14 and Figure 24 The next two flexible time resource units (eg, time slot n+4 and time slot n+5) are associated with a second example option for flexible time resource units, as described in conjunction with Figure 15 and Figure 25 described.

[0287] The second resource pattern 2610 illustrates the application of SBFD configuration (such as Figure 8 The resource mode for eight time resource units is then used after the SBFD configuration 808. Figure 26 As shown in the example of FIG, the second resource pattern 2610 includes alternating SBFD time resource units and non-SBFD time resource units.

[0288] exist Figure 26 In the illustrated example, the third resource pattern 2620 illustrates that in the application update indication (such as Figure 11 The example update indicates 1150) followed by a resource pattern for eight time resource units. Figure 26 As shown, the update indicates that the resource allocation pattern for one or more of the time slots has been changed. Figure 26 In the illustrated example, the update indication includes a bitmap 2630 including eight code points, each code point being mapped to a corresponding time resource unit. For example, the first code point 2632 is mapped to time slot n, the second code point 2634 is mapped to time slot n+1, and so on. Figure 26 As shown, each code point of bitmap 2630 is two bits.

[0289] exist Figure 26 In the example, the UE can be configured with different tables based on the legacy time resource units. For example, the first table 2640 can be associated with downlink time resource units (e.g., time slot n and time slot n+1), the second table 2642 can be associated with the first option flexible time resource units (e.g., time slot n+2 and time slot n+3), the third table 2644 can be associated with the second option flexible time resource units (e.g., time slot n+4 and time slot n+5), and the fourth table 2646 can be associated with uplink time resource units (e.g., time slot n+6 and time slot n+7). Each table in the corresponding table maps the value of a 1-bit code point to a case. For example, because the code point in the example table is a 1-bit code point, the network entity can configure the case where the first value "0" is mapped, and can configure the case where the second value "1" is mapped.

[0290] As an example, a code point value of "0" maps to no change in each of these tables (e.g., case 1). Figure 26 As shown, the time resource unit with code point value "0" is the same in the second resource pattern 2610 and the third resource pattern 2620. In addition, the time resource unit with code point value "1" has different resource allocation patterns between the second resource pattern 2610 and the third resource pattern 2620.

[0291] although Figure 21 Examples include 1-bit code points, but other examples may include n-bit code points, where n is an integer and different cases may be indicated by n bits.

[0292] Figure 16 1600 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, one of UEs 104; device 1804).

[0293] At 1602, the UE receives a first resource pattern of one or more time resource units for a TDD transmit slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern, such as in combination with at least Figure 11 As described in the SBFD configuration 1130 and the second resource mode 1132. As an example, the FD communication mode can be used for SBFD communication, and the non-FD communication mode can be used for HD communication. In some examples, the time resource unit may include a time slot or a symbol. As an example, the reception may be performed by Figure 18 The SBFD configuration of the device 1804 may be performed by the switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880.

[0294] At 1604, the UE receives an indication of a second resource pattern for a subset of one or more time resource units, such as in conjunction with at least Figure 11 As described by the update indication 1150. As an example, the reception can be performed by Figure 18 The SBFD configuration of the device 1804 may be performed by the switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880.

[0295] As an example, the indication may provide an update for a time slot format pattern level. For a first time resource unit in one or more time resource units, the first value of the indication may indicate that the first resource pattern and the second resource pattern are the same resource pattern, and the second value of the indication may indicate that the first resource pattern and the second resource pattern are different resource patterns. Different resource patterns may include a first change in time pattern, a second change in frequency pattern, or a third change in time and frequency pattern. In some aspects, the indication may indicate that the second resource pattern for a subset of one or more time resource units is periodic. The indication may include a bitmap of one or more code points, and each code point of the bitmap corresponds to a different time resource unit in a subset of one or more time resource units. In some aspects, each time resource unit in a subset of one or more time resource units may be associated with an FD communication mode. In some aspects, a subset of one or more time resource units may include one or more time resource units of a TDD transmission time slot format pattern.

[0296] In some aspects, the indication may include an identifier corresponding to a periodic pattern that includes a second resource pattern for a subset of the one or more time resource units. As an example, the indication may indicate a predefined periodic pattern ID.

[0297] In some aspects, the indication may include a first indicator indicating an offset and a second indicator indicating a number of time resource units associated with one or more cycles of the periodic pattern. In some aspects, the offset may be relative to a first event associated with receiving the indication. In some aspects, the offset may be relative to a second event associated with the application time. In some aspects, the offset may be a value indicated by the first indicator.

[0298] The indication may be received via at least one of a DCI or a MAC-CE. As an example, the indication may be received via a group-common DCI. As another example, the indication may be received via a non-data-scheduled DCI or a data-scheduled DCI. In some aspects, the indication may indicate that the second resource mode is valid until the UE receives a second indication indicating a third resource mode. The indication may be received via a MAC-CE (e.g., in a MAC-CE). The indication may indicate that the second resource mode is valid until the UE receives a second indication indicating a third resource mode. The indication may indicate that the second resource mode is valid for a duration, and wherein after the duration expires, the UE is to fall back to the third resource mode.

[0299] In some aspects, the UE may receive scheduling information for at least one of a channel and a reference signal, and the scheduling information may indicate the indication. As an example, the scheduling information may include a 1-bit indicator for at least one of the channel and the reference signal. In some aspects, the scheduling information may include a symbol-level bitmap. Each bit of the symbol-level bitmap may correspond to a corresponding symbol scheduled via the scheduling information. Each bit of the symbol-level bitmap may correspond to a corresponding symbol indicated as FD communication mode and scheduled via the scheduling information.

[0300] In some aspects, the indication may indicate that the second resource pattern for a subset of one or more time resource units is aperiodic. As an example, the indication may indicate a time window during which the subset of one or more time resource units is updated. As another example, the indication may include a bitmap of one or more codepoints, with each codepoint of the bitmap indicating an update to a resource allocation associated with a corresponding time resource unit in the subset of one or more time resource units within the time window. As another example, the indication may indicate that the second resource pattern applies to each time resource unit within the time window. The indication may include a first indicator indicating an offset, and the second resource pattern is applied to the at least one time resource unit based on at least one of: the offset and a first event associated with receipt of the indication; the offset and a second event associated with the application time, or a value indicated by the first indicator. In some aspects, the indication may be received via at least one of a DCI or a MAC-CE. For example, the indication may be received via group-common DCI. In some aspects, the indication may be received via non-data-scheduled DCI or data-scheduled DCI. The indication may indicate that the second resource pattern is valid for the at least one time resource unit. The indication may be received via a MAC-CE. The indication may indicate that the second resource mode is valid until the UE receives a second indication indicating a third resource mode. In some aspects, the indication may indicate that the second resource mode is valid for a duration, and wherein after expiration of the duration, the UE is to fall back to the third resource mode.

[0301] In some aspects, the UE may receive scheduling information for at least one of a channel and a reference signal, and the scheduling information may indicate the indication. In some aspects, the scheduling information may include a 1-bit indicator for at least one of the channel and the reference signal. In some aspects, the scheduling information may include a symbol-level bitmap. Each bit of the symbol-level bitmap may correspond to a corresponding symbol scheduled via the scheduling information. Each bit of the symbol-level bitmap may correspond to a corresponding symbol indicated as FD communication mode and scheduled via the scheduling information.

[0302] In some aspects, a first time resource unit among the one or more time resource units may be configured for a non-FD communication mode via a first resource mode, and the indication may indicate that resource allocation of the first time resource unit is transitioned from the non-FD communication mode to the FD communication mode. In some aspects, the first time resource unit may include a non-FD downlink time resource unit, a non-FD uplink time resource unit, or a non-FD flexible time resource unit. In some aspects, the first time resource unit may include a non-FD flexible time resource unit.

[0303] In some aspects, the second resource pattern may be applied to a single component carrier of a TDD transmit slot format pattern. In some aspects, the second resource pattern may be applied to two or more CCs of the TDD transmit slot format pattern via a CC list. The CC list may include all activated CCs and deactivated CCs for the UE. The CC list may include all activated CCs for the UE. The CC list may include two or more CCs.

[0304] In some aspects, the indication may be received via a primary component carrier of the TDD transmit slot format pattern, and the second resource pattern is applied to at least one secondary component carrier of the TDD transmit slot format pattern.

[0305] At 1606, the UE communicates with the network entity in each corresponding time resource unit using a communication mode based on the second resource mode, such as in combination with at least Figure 11 As described in the communication 1160. As an example, the communication can be, for example, Figure 18 The SBFD configuration of the device 1804 may be performed by the switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880.

[0306] In some aspects, the UE may configure or apply the second resource pattern to a subset of the one or more time resource units based on an application time after an event associated with receiving the indication. In some examples, the application time may be measured from the end of the downlink communication including the indication.

[0307] In some aspects, the UE may send feedback in response to receiving the indication, and wherein the application time is measured from the end of the feedback of the indication. The UE may also receive an application indication indicating the application time. The application time may be based on UE capabilities.

[0308] Figure 17 1700 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, one of UEs 104; device 1804).

[0309] At 1702, the UE receives a first resource allocation pattern for a time resource unit for a TDD transmit slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern, such as in combination with at least Figure 11 As described by the SBFD configuration 1130 and the second resource mode 1132. As an example, the receiving may be performed by Figure 18 The SBFD configuration switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880 of the apparatus 1804 may be performed. The first resource allocation mode may indicate that the communication mode of the time resource unit is switched from a non-FD downlink communication mode to a FD communication mode, and the first resource allocation mode may further configure at least one uplink frequency subband for the time resource unit.

[0310] At 1704, the UE receives an indication indicating a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern, such as in combination with at least Figure 11 Update instructions 1150 and / or Figures 12 to 15 As an example, the receiving can be performed by Figure 18 The SBFD configuration of the device 1804 may be performed by the switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880.

[0311] In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode. The first resource allocation mode may indicate a non-FD downlink communication mode for the second time resource unit for the TDD transmit slot format mode, and the third value of the indication for the second time resource unit may indicate that the communication mode of the second time resource unit is to be converted from the non-FD downlink communication mode to the FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation mode includes a second change in the subband mode of the time resource unit. The UE may also receive an indicator mapped to the first change or mapped to the second change. In some aspects, the third value of the indication for the time resource unit may indicate that the communication mode of the time resource unit is to be converted from the FD communication mode to the non-FD uplink communication mode.

[0312] In some aspects, the first resource allocation mode may indicate that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to an FD communication mode, and the first resource allocation mode may further configure at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit. In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode. In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to be converted from the FD communication mode to the non-FD downlink communication mode. In some aspects, the UE may also receive a configuration that configures the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or a non-FD flexible communication mode. In some aspects, the first resource allocation mode may indicate a non-FD flexible communication mode for a second time resource unit of a TDD transmit slot format mode, and the third value of the indication for the second time resource unit may indicate that the communication mode of the second time resource unit is to be converted from the non-FD flexible communication mode to the FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicate that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit. In some aspects, the UE may also receive an indicator mapped to the first change or mapped to the second change. In some aspects, the third value of the indication for the time resource unit may indicate a transition of the communication mode of the time resource unit from an FD communication mode to a non-FD uplink communication mode.

[0313] In some aspects, the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to a FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit. The second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode. In some aspects, the UE may receive a configuration that configures the second value of the indication as corresponding to a non-FD downlink communication mode, a non-FD uplink communication mode, or a non-FD flexible communication mode. The third value of the indication may indicate that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD uplink communication mode. The third value of the indication may indicate that the second resource allocation mode includes at least one downlink frequency subband. The third value of the indication may indicate that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD downlink communication mode. The first resource allocation mode may indicate a non-FD flexible communication mode for a second time resource unit of a TDD transmit slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is switched from the non-FD flexible communication mode to the FD communication mode. The third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of an uplink frequency subband and a flexible frequency subband of the time resource unit, or indicate that the second resource allocation mode includes a second change in the subband pattern of the time resource unit. The UE may receive an indicator mapped to the first change or mapped to the second change.

[0314] In some aspects, the first resource allocation mode may indicate a change in the communication mode of the time resource unit from a non-FD uplink communication mode to an FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit. The second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode. The first resource allocation mode may indicate a non-FD uplink communication mode for a second time resource unit of a TDD transmit slot format mode, and wherein the third value of the indication for the second time resource unit indicates a transition in the communication mode of the second time resource unit from a non-FD uplink communication mode to an FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation mode includes a second change in the subband mode of the time resource unit. The UE may receive an indicator mapped to the first change or to the second change. In some aspects, the indicated third value for the time resource unit may indicate transitioning the communication mode of the time resource unit from the FD communication mode to the non-FD downlink communication mode.

[0315] In some aspects, the first resource allocation mode may indicate a non-FD communication mode for a second time resource unit for a TDD transmit time slot format mode, and wherein a third value of the indication for the second time resource unit indicates a transition of the communication mode of the second time resource unit from a non-FD communication mode to a FD communication mode.

[0316] At 1706, the UE communicates with the network entity in time resource units using a communication mode based on the TDD transmit slot format mode and the indication, such as in combination with at least Figure 11 As described in the communication 1160. As an example, the communication can be, for example, Figure 18 The SBFD configuration of the device 1804 may be performed by the switching component 198 and / or the cellular RF transceiver 1822 or one or more antennas 1880.

[0317] Figure 181800 is a diagram illustrating an example of a hardware implementation for an apparatus 1804. The apparatus 1804 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1804 may include a cellular baseband processor 1824 (also referred to as a modem) coupled to one or more transceivers (e.g., a cellular RF transceiver 1822). The cellular baseband processor 1824 may include on-chip memory 1824′. In some aspects, the apparatus 1804 may also include one or more subscriber identity module (SIM) cards 1820 and an application processor 1806 coupled to a secure digital (SD) card 1808 and a screen 1810. The application processor 1806 may include on-chip memory 1806′. In some aspects, the device 1804 may also include a Bluetooth module 1812, a WLAN module 1814, an SPS module 1816 (e.g., a GNSS module), one or more sensor modules 1818 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1826, a power source 1830, and / or a camera 1832. The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1812, the WLAN module 1814, and the SPS module 1816 may include their own dedicated antennas and / or utilize one or more antennas 1880 for communication. The cellular baseband processor 1824 communicates with one of the UEs 104 and / or with a RU associated with the network entity 1802 via one or more antennas 1880 through a transceiver (e.g., a cellular RF transceiver 1822). The cellular baseband processor 1824 and the application processor 1806 may each include computer-readable media / memory, such as on-chip memory 1824′ and on-chip memory 1806′, respectively. The additional memory module 1826 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory (e.g., on-chip memory 1824′, on-chip memory 1806′, and / or additional memory module 1826) may be non-transitory. The cellular baseband processor 1824 and the application processor 1806 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. This software, when executed by the cellular baseband processor 1824 / application processor 1806, enables the cellular baseband processor 1824 / application processor 1806 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1824 / applications processor 1806 when executing software.The cellular baseband processor 1824 / application processor 1806 may be a component of the UE 450 and may include the memory 460 and / or at least one of the TX processor 468, the RX processor 456, and the controller / processor 459. In one configuration, the device 1804 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1824 and / or the application processor 1806, while in another configuration, the device 1804 may be the entire UE (e.g., see. Figure 4 UE 450) and includes additional modules of device 1804.

[0318] As discussed above, the SBFD configuration switching component 198 can be configured to: receive a first resource pattern for one or more time resource units for a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; receive an indication of a second resource pattern for a subset of the one or more time resource units; and communicate with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0319] On the other hand, the SBFD configuration switching component 198 can be configured to: receive a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation mode; receive an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation mode and the first resource allocation mode are the same resource allocation mode, and the second value of the indication indicating that the second resource allocation mode is different from the first resource allocation mode; and communicate with a network entity in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0320] The SBFD configuration switching component 198 may be within the cellular baseband processor 1824, the application processor 1806, or both the cellular baseband processor 1824 and the application processor 1806. The SBFD configuration switching component 198 may be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored on a computer readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1804 may include a variety of components configured for various functions. For example, the SBFD configuration switching component 198 may include a processor that performs Figure 16 and / or Figure 17Each block of the algorithm in the flowchart is one or more hardware components.

[0321] In one configuration, the apparatus 1804 (and in particular the cellular baseband processor 1824 and / or the application processor 1806) may include means for receiving a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example apparatus 1804 also includes means for receiving an indication of a second resource pattern for a subset of the one or more time resource units. The example apparatus 1804 also includes means for communicating with a network entity in each respective time resource unit using a communication mode based on the second resource pattern.

[0322] In another configuration, the example apparatus 1804 further includes means for receiving scheduling information for at least one of a channel and a reference signal, and wherein the scheduling information indicates the indication.

[0323] In another configuration, the example apparatus 1804 further includes means for sending feedback in response to receiving the indication, and wherein the application time is measured from an end of the feedback of the indication.

[0324] In another configuration, the example apparatus 1804 further includes means for receiving an application indication indicating an application time.

[0325] In another configuration, the example apparatus 1804 includes means for receiving a first resource allocation pattern for a time resource unit of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example apparatus 1804 also includes means for receiving an indication of a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. The example apparatus 1804 also includes means for communicating with a network entity in the time resource unit using a communication mode based on the TDD transmit slot format pattern and the indication.

[0326] In another configuration, the example apparatus 1804 further includes means for receiving an indicator that maps to the first change or maps to the second change.

[0327] In another configuration, the example apparatus 1804 further includes means for receiving a configuration configuring the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or a non-FD flexible communication mode.

[0328] The means may be the SBFD configuration switching component 198 of the apparatus 1804 configured to perform the functions recited by the means. As described above, the apparatus 1804 may include the TX processor 468, the RX processor 456, and the controller / processor 459. Thus, in one configuration, the means may be the TX processor 468, the RX processor 456, and / or the controller / processor 459 configured to perform the functions recited by the means.

[0329] Figure 19 1900 is a flow chart of a method of wireless communication. The method may be performed by a base station (eg, one of base stations 102, base station 202; network entity 1802; network entity 2102) in a converged or decomposed form.

[0330] At 1902, a network entity outputs a first resource pattern of one or more time resource units for a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern, such as in combination with at least Figure 11 As described in the SBFD configuration 1130. As an example, the output can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0331] As an example, the FD communication mode may be used for SBFD communication, and the non-FD communication mode may be used for HD communication.In some examples, a time resource unit may include a time slot or a symbol.

[0332] At 1904, the network entity outputs an indication of a second resource mode for a subset of the one or more time resource units, such as in conjunction with at least Figure 11 As described by the update indication 1150. As an example, the output can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0333] As an example, the indication may provide an update for a time slot format pattern level. For a first time resource unit in one or more time resource units, the first value of the indication may indicate that the first resource pattern and the second resource pattern are the same resource pattern, and the second value of the indication may indicate that the first resource pattern and the second resource pattern are different resource patterns. Different resource patterns may include a first change in time pattern, a second change in frequency pattern, or a third change in time and frequency pattern. In some aspects, the indication may indicate that the second resource pattern for a subset of one or more time resource units is periodic. The indication may include a bitmap of one or more code points, and each code point of the bitmap corresponds to a different time resource unit in a subset of one or more time resource units. In some aspects, each time resource unit in a subset of one or more time resource units may be associated with an FD communication mode. In some aspects, a subset of one or more time resource units may include one or more time resource units of a TDD transmission time slot format pattern.

[0334] In some aspects, the indication may include an identifier corresponding to a periodic pattern that includes a second resource pattern for a subset of the one or more time resource units. As an example, the indication may indicate a predefined periodic pattern ID.

[0335] In some aspects, the indication may include a first indicator indicating an offset and a second indicator indicating a number of time resource units associated with one or more cycles of the periodic pattern. In some aspects, the offset may be relative to a first event associated with receiving the indication. In some aspects, the offset may be relative to a second event associated with the application time. In some aspects, the offset may be a value indicated by the first indicator.

[0336] The indication may be output via at least one of a DCI or a MAC-CE. As an example, the indication may be output via a group-common DCI. As another example, the indication may be output via a non-data-scheduled DCI or a data-scheduled DCI. In some aspects, the indication may indicate that the second resource mode is valid until the network entity outputs a second indication indicating a third resource mode. The indication may be output via a MAC-CE (e.g., in a MAC-CE). The indication may indicate that the second resource mode is valid until the network entity outputs a second indication indicating a third resource mode. The indication may indicate that the second resource mode is valid for a duration, and wherein after expiration of the duration, communications in each corresponding time resource unit are to fall back to the third resource mode.

[0337] In some aspects, a network entity may output scheduling information for at least one of a channel and a reference signal, and the scheduling information may indicate the indication. As an example, the scheduling information may include a 1-bit indicator for at least one of the channel and the reference signal. In some aspects, the scheduling information may include a symbol-level bitmap. Each bit of the symbol-level bitmap may correspond to a corresponding symbol scheduled via the scheduling information. Each bit of the symbol-level bitmap may correspond to a corresponding symbol indicated as FD communication mode and scheduled via the scheduling information.

[0338] In some aspects, the indication may indicate that the second resource pattern for a subset of one or more time resource units is aperiodic. As an example, the indication may indicate a time window during which the subset of one or more time resource units is updated. As another example, the indication may include a bitmap of one or more codepoints, with each codepoint of the bitmap indicating an update to a resource allocation associated with a corresponding time resource unit in the subset of one or more time resource units within the time window. As another example, the indication may indicate that the second resource pattern applies to each time resource unit within the time window. The indication may include a first indicator indicating an offset, and the second resource pattern is applied to the at least one time resource unit based on at least one of: the offset and a first event associated with receipt of the indication; the offset and a second event associated with an application time, or a value indicated by the first indicator. In some aspects, the indication may be output via at least one of a DCI or a MAC-CE. For example, the indication may be output via group-common DCI. In some aspects, the indication may be output via non-data-scheduled DCI or data-scheduled DCI. The indication may indicate that the second resource pattern is valid for the at least one time resource unit. The indication may be output via a MAC-CE. The indication may indicate that the second resource mode is valid until the network entity outputs a second indication indicating a third resource mode. In some aspects, the indication may indicate that the second resource mode is valid for a duration, and wherein after expiration of the duration, communications in each corresponding time resource unit are to fall back to the third resource mode.

[0339] In some aspects, a network entity may output scheduling information for at least one of a channel and a reference signal, and the scheduling information may indicate the indication. In some aspects, the scheduling information may include a 1-bit indicator for at least one of the channel and the reference signal. In some aspects, the scheduling information may include a symbol-level bitmap. Each bit of the symbol-level bitmap may correspond to a corresponding symbol scheduled via the scheduling information. Each bit of the symbol-level bitmap may correspond to a corresponding symbol indicated as FD communication mode and scheduled via the scheduling information.

[0340] In some aspects, a first time resource unit among the one or more time resource units may be configured for a non-FD communication mode via a first resource mode, and the indication may indicate that resource allocation of the first time resource unit is transitioned from the non-FD communication mode to the FD communication mode. In some aspects, the first time resource unit may include a non-FD downlink time resource unit, a non-FD uplink time resource unit, or a non-FD flexible time resource unit. In some aspects, the first time resource unit may include a non-FD flexible time resource unit.

[0341] In some aspects, the second resource pattern may be applied to a single component carrier of a TDD transmit slot format pattern. In some aspects, the second resource pattern may be applied to two or more CCs of the TDD transmit slot format pattern via a CC list. The CC list may include activated CCs and deactivated CCs. The CC list may include all activated CCs. The CC list may include two or more CCs.

[0342] In some aspects, the indication may be received via a primary component carrier of the TDD transmit slot format pattern, and the second resource pattern is applied to at least one secondary component carrier of the TDD transmit slot format pattern.

[0343] At 1906, the network entity may communicate in each corresponding time resource unit using a communication mode based on a second resource mode, such as in conjunction with at least Figure 11 As described in the communication 1160. As an example, the communication can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0344] Figure 20 2000 is a flow chart of a method of wireless communication. The method may be performed by a base station (eg, one of base stations 102, base station 202; network entity 1802, network entity 2102) in a converged or decomposed form.

[0345] At 2002, a network entity outputs a first resource allocation pattern for a time resource unit of a TDD transmission slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern, such as in combination with at least Figure 11 As described in the SBFD configuration 1130. As an example, the output can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0346] The first resource allocation pattern may indicate switching the communication mode of the time resource unit from the non-FD downlink communication mode to the FD communication mode, and the first resource allocation pattern may further configure at least one uplink frequency subband for the time resource unit.

[0347] At 2004, the network entity outputs an indication indicating a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern, such as in combination with at least Figure 11 As described by the update indication 1150. As an example, the output can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0348] In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode. The first resource allocation mode may indicate a non-FD downlink communication mode for the second time resource unit for the TDD transmit slot format mode, and the third value of the indication for the second time resource unit may indicate that the communication mode of the second time resource unit is to be converted from the non-FD downlink communication mode to the FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation mode includes a second change in the subband mode of the time resource unit. The network entity may also output an indicator mapped to the first change or mapped to the second change. In some aspects, the third value of the indication for the time resource unit may indicate that the communication mode of the time resource unit is to be converted from the FD communication mode to the non-FD uplink communication mode.

[0349] In some aspects, the first resource allocation mode may indicate that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to an FD communication mode, and the first resource allocation mode may further configure at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit. In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode. In some aspects, the second value of the indication may indicate that the communication mode of the time resource unit is to be converted from the FD communication mode to the non-FD downlink communication mode. In some aspects, the network entity may also output a configuration that configures the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or a non-FD flexible communication mode. In some aspects, the first resource allocation mode may indicate a non-FD flexible communication mode for a second time resource unit of a TDD transmit slot format mode, and the third value of the indication for the second time resource unit may indicate that the communication mode of the second time resource unit is to be converted from the non-FD flexible communication mode to the FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicate that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit. In some aspects, the network entity may also output an indicator mapped to the first change or mapped to the second change. In some aspects, the third value of the indication for the time resource unit may indicate a transition of the communication mode of the time resource unit from an FD communication mode to a non-FD uplink communication mode.

[0350] In some aspects, the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to an FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit. The second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode. In some aspects, the network entity may output a configuration that configures the second value of the indication as corresponding to a non-FD downlink communication mode, a non-FD uplink communication mode, or a non-FD flexible communication mode. The third value of the indication may indicate that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD uplink communication mode. The third value of the indication may indicate that the second resource allocation mode includes at least one downlink frequency subband. The third value of the indication may indicate that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD downlink communication mode. The first resource allocation mode may indicate a non-FD flexible communication mode for a second time resource unit of a TDD transmission slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is switched from the non-FD flexible communication mode to the FD communication mode. The third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of an uplink frequency subband and a flexible frequency subband of the time resource unit, or indicate that the second resource allocation mode includes a second change in the subband mode of the time resource unit. The network entity may output an indicator mapped to the first change or mapped to the second change.

[0351] In some aspects, the first resource allocation mode may indicate a change in the communication mode of the time resource unit from a non-FD uplink communication mode to an FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit. The second value of the indication may indicate that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode. The first resource allocation mode may indicate a non-FD uplink communication mode for a second time resource unit of a TDD transmit slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from a non-FD uplink communication mode to an FD communication mode. In some aspects, the third value of the indication for the time resource unit may indicate that the second resource allocation mode includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation mode includes a second change in the subband mode of the time resource unit. The network entity may output an indicator mapped to the first change or mapped to the second change. In some aspects, the indicated third value for the time resource unit may indicate transitioning the communication mode of the time resource unit from the FD communication mode to the non-FD downlink communication mode.

[0352] In some aspects, the first resource allocation mode may indicate a non-FD communication mode for a second time resource unit for a TDD transmit time slot format mode, and wherein a third value of the indication for the second time resource unit indicates a transition of the communication mode of the second time resource unit from a non-FD communication mode to a FD communication mode.

[0353] At 2006, the network entity communicates in time resource units using a communication mode based on a TDD transmission slot format mode and an indication, such as in combination with at least Figure 11 As described in the communication 1160. As an example, the communication can be, for example, Figure 21 The SBFD update configuration component 199 of the network entity 2102 and / or the one or more transceivers 2146 or the one or more antennas 2180 is performed.

[0354] Figure 21Diagram 2100 illustrates an example hardware implementation for a network entity 2102. Network entity 2102 may be a base station (BS), a component of a BS, or may implement BS functionality. Network entity 2102 may include at least one of a CU 2110, a DU 2130, or a RU 2140. For example, depending on the layer functionality handled by SBFD update configuration component 199, network entity 2102 may include a CU 2110; both the CU 2110 and the DU 2130; each of the CU 2110, the DU 2130, and the RU 2140; the DU 2130; both the DU 2130 and the RU 2140; or the RU 2140. CU 2110 may include a CU processor 2112. CU processor 2112 may include on-chip memory 2112′. In some aspects, additional memory modules 2114 and communication interfaces 2118 may also be included. The CU 2110 communicates with the DU 2130 via a midhaul link, such as the F1 interface. The DU 2130 may include a DU processor 2132. The DU processor 2132 may include on-chip memory 2132′. In some aspects, the DU 2130 may also include an additional memory module 2134 and a communication interface 2138. The DU 2130 communicates with the RU 2140 via a fronthaul link. The RU 2140 may include a RU processor 2142. The RU processor 2142 may include on-chip memory 2142′. In some aspects, the RU 2140 may also include an additional memory module 2144, one or more transceivers 2146, one or more antennas 2180, and a communication interface 2148. The RU 2140 communicates with one of the UEs 104. On-chip memory (e.g., on-chip memory 2112', on-chip memory 2132', and / or on-chip memory 2142') and / or additional memory modules (e.g., additional memory module 2114, additional memory module 2134, and / or additional memory module 2144) can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the CU processor 2112, the DU processor 2132, and the RU processor 2142 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software enables the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0355] As discussed above, the SBFD update configuration component 199 can be configured to: output a first resource pattern for one or more time resource units for a TDD transmit time slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; output an indication of a second resource pattern for a subset of the one or more time resource units; and communicate in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0356] On the other hand, the SBFD update configuration component 199 can be configured to: output a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation mode; output an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation mode and the first resource allocation mode are the same resource allocation mode, and the second value of the indication indicating that the second resource allocation mode is different from the first resource allocation mode; and communicate in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0357] The SBFD update configuration component 199 may be within one or more processors of one or more of the CU 2110, DU 2130, and RU 2140. The SBFD update configuration component 199 may be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2102 may include a variety of components configured for various functions.

[0358] In one configuration, the network entity 2102 may include means for outputting a first resource pattern for one or more time resource units of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern. The example network entity 2102 also includes means for outputting an indication of a second resource pattern for a subset of the one or more time resource units. The example network entity 2102 also includes means for communicating in each corresponding time resource unit using a communication mode based on the second resource pattern.

[0359] In another configuration, the example network entity 2102 includes means for outputting a first resource allocation pattern for a time resource unit of a TDD transmit slot format pattern, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern. The example network entity 2102 also includes means for outputting an indication of a second resource allocation pattern for the time resource unit, a first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern. The example network entity 2102 also includes means for communicating in the time resource unit using a communication mode based on the TDD transmit slot format pattern and the indication.

[0360] The means may be the SBFD update configuration component 199 of the network entity 2102 configured to perform the functions recited by the means. As described above, the network entity 2102 may include the TX processor 416, the RX processor 470, and the controller / processor 475. Thus, in one configuration, the means may be the TX processor 416, the RX processor 470, and / or the controller / processor 475 configured to perform the functions recited by the means.

[0361] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0362] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but there is no need for a specific or immediate time limit for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, which may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. A device configured to "output" data (such as, transmit, signal or message) may (for example) send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data. The information stored in the memory includes instructions and / or data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Thus, no claim element will be construed as part-plus-function unless the element is explicitly recited using the phrase "means for..."

[0363] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0364] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0365] Aspect 1 is a method for performing wireless communication at a UE, the method comprising: receiving a first resource pattern of one or more time resource units for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; receiving an indication of a second resource pattern for a subset of the one or more time resource units; and communicating with a network entity in each corresponding time resource unit using a communication mode based on the second resource pattern.

[0366] Aspect 2 is a method according to Aspect 1, and the method further includes: for the first time resource unit among the one or more time resource units, the first value of the indication indicates that the first resource mode and the second resource mode are the same resource mode, and the second value of the indication indicates that the first resource mode and the second resource mode are different resource modes.

[0367] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising: the different resource patterns comprising a first change of a time pattern, a second change of a frequency pattern, or a third change of a time and frequency pattern.

[0368] Aspect 4 is a method according to any one of aspects 1 to 3, further comprising: the indication indicating that the second resource pattern for the subset of the one or more time resource units is periodic.

[0369] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: the indication includes a bitmap of one or more code points, and each code point of the bitmap corresponds to a different time resource unit in the subset of the one or more time resource units.

[0370] Aspect 6 is a method according to any one of aspects 1 to 5, further comprising: each time resource unit in the subset of the one or more time resource units is associated with the FD communication mode.

[0371] Aspect 7 is a method according to any one of Aspects 1 to 5, the method further comprising: the subset of the one or more time resource units includes the one or more time resource units of the TDD transmission time slot format pattern.

[0372] Aspect 8 is a method according to any one of aspects 1 to 4, the method further comprising: the indication comprising an identifier corresponding to a periodic pattern, the periodic pattern comprising the second resource pattern for the subset of the one or more time resource units.

[0373] Aspect 9 is a method according to any one of Aspects 1 to 4, the method further comprising: the indication comprises a first indicator indicating an offset and a second indicator indicating the number of time resource units associated with one or more cycles of a periodic pattern, and wherein the offset is one of: relative to a first event associated with receiving the indication; relative to a second event associated with an application time, or a value indicated by the first indicator.

[0374] Aspect 10 is a method according to any one of aspects 1 to 9, further comprising: receiving the indication via at least one of downlink control information (DCI) or medium access control-control element (MAC-CE).

[0375] Aspect 11 is a method according to any one of aspects 1 to 10, further comprising: receiving the indication via a group-common DCI.

[0376] Aspect 12 is a method according to any one of aspects 1 to 11, further comprising: receiving the indication via non-data scheduling DCI or data scheduling DCI.

[0377] Aspect 13 is a method according to any one of aspects 1 to 12, the method further comprising: the indication indicating that the second resource pattern is valid until the UE receives a second indication indicating a third resource pattern.

[0378] Aspect 14 is a method according to any one of aspects 1 to 10, further comprising: receiving the indication via the MAC-CE.

[0379] Aspect 15 is a method according to any one of aspects 1 to 14, the method further comprising: the indication indicating that the second resource pattern is valid until the UE receives a second indication indicating a third resource pattern.

[0380] Aspect 16 is a method according to any one of aspects 1 to 15, the method further comprising: the indication indicating that the second resource mode is valid for a duration, and wherein after the duration expires, the UE is to fall back to the third resource mode.

[0381] Aspect 17 is a method according to any one of aspects 1 to 4, further comprising: receiving scheduling information for at least one of a channel and a reference signal, and wherein the scheduling information indicates the indication.

[0382] Aspect 18 is a method according to any one of aspects 1 to 17, the method further comprising: the scheduling information comprising a 1-bit indicator for at least one of the channel and the reference signal.

[0383] Aspect 19 is a method according to any one of aspects 1 to 18, the method further comprising: the scheduling information includes a symbol-level bitmap.

[0384] Aspect 20 is a method according to any one of aspects 1 to 19, further comprising: each bit of the symbol-level bitmap corresponds to a corresponding symbol scheduled via the scheduling information.

[0385] Aspect 21 is a method according to any one of aspects 1 to 19, further comprising: each bit of the symbol-level bitmap corresponds to a corresponding symbol indicated as the FD communication mode and scheduled via the scheduling information.

[0386] Aspect 22 is a method according to any one of aspects 1 to 21, the method further comprising: the indication indicating that the second resource pattern for the subset of the one or more time resource units is aperiodic.

[0387] Aspect 23 is a method according to any one of aspects 1 to 22, the method further comprising: the indication indicating a time window during which the subset of the one or more time resource units is updated.

[0388] Aspect 24 is a method according to any one of Aspects 1 to 23, the method further comprising: the indication includes a bitmap of one or more code points, and each code point of the bitmap indicates an update to the resource allocation associated with the corresponding time resource unit in the subset of the one or more time resource units located within the time window.

[0389] Aspect 25 is a method according to any one of aspects 1 to 24, further comprising: the indication indicating that the second resource pattern applies to each time resource unit within the time window.

[0390] Aspect 26 is a method according to any one of Aspects 1 to 23, the method further comprising: the indication includes a first indicator indicating an offset, and the second resource mode is applied to at least one time resource unit based on at least one of: the offset and a first event related to receiving the indication; the offset and a second event related to the application time or a value indicated by the first indicator.

[0391] Aspect 27 is a method according to any one of aspects 1 to 26, the method further comprising: receiving the indication via at least one of downlink control information (DCI) or medium access control-control element (MAC-CE).

[0392] Aspect 28 is a method according to any one of aspects 1 to 27, further comprising: receiving the indication via a group-common DCI.

[0393] Aspect 29 is a method according to any one of aspects 1 to 27, the method further comprising: receiving the indication via non-data scheduling DCI or data scheduling DCI.

[0394] Aspect 30 is a method according to any one of aspects 1 to 29, further comprising: the indication indicating that the second resource pattern is valid for at least one time resource unit.

[0395] Aspect 31 is a method according to any one of aspects 1 to 27, further comprising: receiving the indication via the MAC-CE.

[0396] Aspect 32 is a method according to any one of aspects 1 to 31, the method further comprising: the indication indicating that the second resource pattern is valid until the UE receives a second indication indicating a third resource pattern.

[0397] Aspect 33 is a method according to any one of aspects 1 to 32, the method further comprising: the indication indicating that the second resource mode is valid for a duration, and wherein after the duration expires, the UE is to fall back to the third resource mode.

[0398] Aspect 34 is a method according to any one of aspects 1 to 33, the method further comprising: receiving scheduling information for at least one of a channel and a reference signal, and wherein the scheduling information indicates the indication.

[0399] Aspect 35 is a method according to any one of aspects 1 to 34, the method further comprising: the scheduling information comprising a 1-bit indicator for at least one of the channel and the reference signal.

[0400] Aspect 36 is a method according to any one of aspects 1 to 34, the method further comprising: the scheduling information includes a symbol-level bitmap.

[0401] Aspect 37 is a method according to any one of aspects 1 to 36, the method further comprising: each bit of the symbol-level bitmap corresponds to a corresponding symbol scheduled via the scheduling information.

[0402] Aspect 38 is a method according to any one of aspects 1 to 36, the method further comprising: each bit of the symbol-level bitmap corresponds to a corresponding symbol indicated as the FD communication mode and scheduled via the scheduling information.

[0403] Aspect 39 is a method according to any one of aspects 1 to 38, the method further comprising: the second resource pattern is applied to a single component carrier of the TDD transmission time slot format pattern.

[0404] Aspect 40 is a method according to any one of aspects 1 to 39, further comprising: applying the second resource pattern to two or more CCs of the TDD transmission slot format pattern via a CC list.

[0405] Aspect 41 is a method according to any one of aspects 1 to 40, further comprising: the CC list including all activated CCs and deactivated CCs for the UE.

[0406] Aspect 42 is a method according to any one of aspects 1 to 41, the method further comprising: the CC list including all activated CCs for the UE.

[0407] Aspect 43 is a method according to any one of aspects 1 to 42, further comprising: the CC list including the two or more CCs.

[0408] Aspect 44 is a method according to any one of Aspects 1 to 43, the method further comprising: receiving the indication via a primary component carrier of the TDD transmission time slot format mode, and the second resource pattern is applied to at least one secondary component carrier of the TDD transmission time slot format mode.

[0409] Aspect 45 is a method according to any one of Aspects 1 to 44, and the method also includes: the UE configuring the second resource pattern to the subset of the one or more time resource units according to the application time after the event related to receiving the indication.

[0410] Aspect 46 is a method according to any one of aspects 1 to 45, the method further comprising: measuring the application time from the end of the downlink communication including the indication.

[0411] Aspect 47 is a method according to any one of aspects 1 to 45, the method further comprising: sending feedback in response to receiving the indication, and wherein the application time is measured from an end of the feedback of the indication.

[0412] Aspect 48 is a method according to any one of aspects 1 to 45, further comprising: receiving an application indication indicating the application time.

[0413] Aspect 49 is a method according to any one of aspects 1 to 45, further comprising: the application time is based on UE capabilities.

[0414] Aspect 50 is a method according to any one of Aspects 1 to 49, further comprising: a first time resource unit among the one or more time resource units is configured for the non-FD communication mode via the first resource mode, and wherein the indication indicates that the resource allocation of the first time resource unit is converted from the non-FD communication mode to the FD communication mode.

[0415] Aspect 51 is a method according to any one of aspects 1 to 50, the method further comprising: the first time resource unit includes a non-FD downlink time resource unit, a non-FD uplink time resource unit or a non-FD flexible time resource unit.

[0416] Aspect 52 is a method according to any one of aspects 1 to 50, further comprising: the first time resource unit comprising a non-FD flexible time resource unit.

[0417] Aspect 53 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 1 to 52.

[0418] In aspect 54, the apparatus of aspect 53 further comprises at least one antenna coupled to the at least one processor.

[0419] In aspect 55, the apparatus of aspect 53 or 54 further comprises a transceiver coupled to the at least one processor.

[0420] Aspect 56 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 52.

[0421] In aspect 57, the apparatus of aspect 56 further comprises at least one antenna coupled to the means for performing the method of any one of aspects 1 to 52.

[0422] In aspect 58, the apparatus according to aspect 56 or 57 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 1 to 52.

[0423] Aspect 59 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 1 to 52.

[0424] Aspect 60 is a method for performing wireless communication at a UE, the method comprising: receiving a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern; receiving an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation mode is different from the first resource allocation mode; and communicating with a network entity in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0425] Aspect 61 is a method according to Aspect 60, and the method also includes: the first resource allocation mode indicates that the communication mode of the time resource unit is converted from the non-FD downlink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one uplink frequency subband for the time resource unit.

[0426] Aspect 62 is a method according to any one of aspects 60 and 61, and the method also includes: the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode.

[0427] Aspect 63 is a method according to any one of Aspects 60 to 62, the method further comprising: the first resource allocation mode indicates the non-FD downlink communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from the non-FD downlink communication mode to the FD communication mode.

[0428] Aspect 64 is a method according to any one of Aspects 60 to 63, and the method further includes: the third value indicated for the time resource unit indicates that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit.

[0429] Aspect 65 is a method according to any one of aspects 60 to 64, further comprising: receiving an indicator mapped to the first change or mapped to the second change.

[0430] Aspect 66 is a method according to any one of Aspects 60 to 65, and the method also includes: the third value of the indication for the time resource unit indicates that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD uplink communication mode.

[0431] Aspect 67 is a method according to Aspect 60, and the method also includes: the first resource allocation mode indicates that the communication mode of the time resource unit is converted from the non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit.

[0432] Aspect 68 is a method according to any one of aspects 60 to 67, the method further comprising: the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode.

[0433] Aspect 69 is a method according to any one of aspects 60 to 68, the method further comprising: the second value of the indication indicates that the communication mode of the time resource unit is switched from the FD communication mode to a non-FD downlink communication mode.

[0434] Aspect 70 is a method according to any one of Aspects 60 to 69, and the method also includes: receiving a configuration to configure the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or the non-FD flexible communication mode.

[0435] Aspect 71 is a method according to any one of Aspects 60 to 70, the method further comprising: the first resource allocation mode indicates the non-FD flexible communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from the non-FD flexible communication mode to the FD communication mode.

[0436] Aspect 72 is a method according to any one of Aspects 60 to 71, and the method further includes: the third value indicated for the time resource unit indicates that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit.

[0437] Aspect 73 is a method according to any one of aspects 60 to 72, further comprising: receiving an indicator mapped to the first change or mapped to the second change.

[0438] Aspect 74 is a method according to any one of Aspects 60 to 73, and the method also includes: the third value of the indication for the time resource unit indicates that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD uplink communication mode.

[0439] Aspect 75 is a method according to Aspect 60, and the method also includes: the first resource allocation mode indicates that the communication mode of the time resource unit is converted from the non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit.

[0440] Aspect 76 is a method according to any one of aspects 60 to 75, the method further comprising: the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode.

[0441] Aspect 77 is a method according to any one of Aspects 60 to 76, and the method also includes: receiving a configuration to configure the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or the non-FD flexible communication mode.

[0442] Aspect 78 is a method according to any one of aspects 60 to 77, the method further comprising: the third value of the indication indicates that the communication mode of the time resource unit is converted from the FD communication mode to a non-FD uplink communication mode.

[0443] Aspect 79 is a method according to any one of aspects 60 to 78, the method further comprising: a third value of the indication indicating that the second resource allocation pattern includes at least one downlink frequency subband.

[0444] Aspect 80 is a method according to any one of aspects 60 to 79, the method further comprising: the third value of the indication instructs to switch the communication mode of the time resource unit from the FD communication mode to a non-FD downlink communication mode.

[0445] Aspect 81 is a method according to any one of Aspects 60 to 80, the method further comprising: the first resource allocation mode indicates the non-FD flexible communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from the non-FD flexible communication mode to the FD communication mode.

[0446] Aspect 82 is a method according to any one of Aspects 60 to 81, and the method further includes: the third value indicated for the time resource unit indicates that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and flexible frequency subband of the time resource unit, or indicates that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit.

[0447] Aspect 83 is a method according to any one of aspects 60 to 82, further comprising: receiving an indicator mapped to the first change or mapped to the second change.

[0448] Aspect 84 is a method according to Aspect 83, and the method also includes: the first resource allocation mode indicates that the communication mode of the time resource unit is changed from the non-FD uplink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit.

[0449] Aspect 85 is a method according to any one of aspects 60 to 84, the method further comprising: the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode.

[0450] Aspect 86 is a method according to any one of Aspects 60 to 85, the method further comprising: the first resource allocation mode indicates the non-FD uplink communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from the non-FD uplink communication mode to the FD communication mode.

[0451] Aspect 87 is a method according to any one of Aspects 60 to 86, and the method also includes: the third value indicated for the time resource unit indicates that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit.

[0452] Aspect 88 is a method according to any one of aspects 60 to 87, the method further comprising: receiving an indicator mapped to the first change or mapped to the second change.

[0453] Aspect 89 is a method according to any one of Aspects 60 to 88, and the method also includes: the third value of the indication for the time resource unit indicates that the communication mode of the time resource unit is converted from the FD communication mode to the non-FD downlink communication mode.

[0454] Aspect 90 is a method according to any one of Aspects 60 to 89, the method further comprising: the first resource allocation mode indicates the non-FD communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates converting the communication mode of the second time resource unit from the non-FD communication mode to the FD communication mode.

[0455] Aspect 91 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 60 to 90.

[0456] In aspect 92, the apparatus of aspect 91 further comprises at least one antenna coupled to the at least one processor.

[0457] In aspect 93, the apparatus of aspect 91 or 92 further comprises a transceiver coupled to the at least one processor.

[0458] Aspect 94 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 60 to 90.

[0459] In aspect 95, the apparatus of aspect 94 further comprises at least one antenna coupled to the means for performing the method of any one of aspects 60 to 90.

[0460] In aspect 96, the apparatus according to aspect 94 or 95 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 60 to 90.

[0461] Aspect 97 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 60 to 90.

[0462] Aspect 98 is a method for wireless communication at a network entity, the method comprising: outputting a first resource pattern for one or more time resource units for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; outputting an indication of a second resource pattern for a subset of the one or more time resource units; and communicating in each corresponding time resource unit using a communication pattern based on the second resource pattern.

[0463] Aspect 99 is a method according to Aspect 98, the method further comprising: for a first time resource unit among the one or more time resource units, the first value of the indication indicates that the first resource mode and the second resource mode are the same resource mode, and the second value of the indication indicates that the first resource mode and the second resource mode are different resource modes.

[0464] Aspect 100 is a method according to any one of Aspects 98 and 99, further comprising: the indication indicating that the second resource pattern for the subset of the one or more time resource units is periodic, and wherein the indication includes a bitmap of one or more code points, and each code point of the bitmap corresponds to a different time resource unit in the subset of the one or more time resource units.

[0465] Aspect 101 is an apparatus for wireless communications at a network entity, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 98 to 100.

[0466] In aspect 102, the apparatus according to aspect 101 further comprises at least one antenna coupled to the at least one processor.

[0467] In aspect 103, the apparatus according to aspect 101 or 102 further comprises a transceiver coupled to the at least one processor.

[0468] Aspect 104 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 98 to 100.

[0469] In aspect 105, the apparatus according to aspect 104 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 98 to 100.

[0470] In aspect 106, the apparatus according to aspect 104 or 105 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 98 to 100.

[0471] Aspect 107 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 98 to 100.

[0472] Aspect 108 is a method for performing wireless communications at a network entity, the method comprising: outputting a first resource allocation pattern for a time resource unit for a TDD transmission time slot format mode, wherein one of an FD communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern; outputting an indication of a second resource allocation pattern for the time resource unit, the first value of the indication indicating that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication indicating that the second resource allocation pattern is different from the first resource allocation pattern; and communicating in the time resource unit using a communication mode based on the TDD transmission time slot format mode and the indication.

[0473] Aspect 109 is a method according to Aspect 108, the method further comprising: the first resource allocation mode indicates that the communication mode of the time resource unit is converted from the non-FD downlink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one uplink frequency subband for the time resource unit, and wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode.

[0474] Aspect 110 is a method according to aspect 108, the method further comprising: wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit.

[0475] Aspect 111 is a method according to Aspect 108, and the method also includes: the first resource allocation mode indicates that the communication mode of the time resource unit is converted from the non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit.

[0476] Aspect 112 is a method according to aspect 108, the method further comprising: the first resource allocation mode indicates that the communication mode of the time resource unit is changed from the non-FD uplink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit, and wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode.

[0477] Aspect 113 is an apparatus for wireless communications at a network entity, the apparatus comprising at least one processor coupled to a memory and configured to implement any one of aspects 108 to 112.

[0478] In aspect 114, the apparatus according to aspect 113 further comprises at least one antenna coupled to the at least one processor.

[0479] In aspect 115, the apparatus according to aspect 113 or 114 further comprises a transceiver coupled to the at least one processor.

[0480] Aspect 116 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 108 to 112.

[0481] In aspect 117, the apparatus according to aspect 116 further comprises at least one antenna coupled to the means for performing the method according to any one of aspects 108 to 112.

[0482] In aspect 118, the apparatus according to aspect 116 or 117 further comprises a transceiver coupled to the means for performing the method according to any one of aspects 108 to 112.

[0483] Aspect 119 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed, causes a processor to implement any one of aspects 108 to 112 .

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: receiving a first resource pattern of one or more time resource units for a time division duplex (TDD) transmit slot format pattern, wherein one of a full-duplex (FD) communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; receiving an indication of a second resource mode configured to indicate a subset of the one or more time resource units; as well as Communicating with a network entity in each corresponding time resource unit using a communication pattern based on the second resource pattern.

2. The device according to claim 1, wherein For a first time resource unit of the one or more time resource units, a first value of the indication indicates that the first resource pattern and the second resource pattern are the same resource pattern, and a second value of the indication indicates that the first resource pattern and the second resource pattern are different resource patterns. 3 . The apparatus of claim 1 , wherein the indication indicates that the second resource pattern for the subset of the one or more time resource units is periodic. 4 . The apparatus of claim 3 , wherein the indication comprises a bitmap of one or more code points, and each code point of the bitmap is configured to correspond to a different time resource unit in the subset of the one or more time resource units. 5 . The apparatus of claim 3 , wherein the indication comprises an identifier corresponding to a periodic pattern including the second resource pattern for the subset of the one or more time resource units.

6. The apparatus of claim 3 , wherein the indication comprises a first indicator configured to indicate an offset and a second indicator configured to indicate a number of time resource units associated with one or more cycles of the periodic pattern, and wherein the offset is one of: relative to a first event associated with receiving said indication; relative to a second event relative to the application time, or The value indicated by the first indicator.

7. The apparatus of claim 1, wherein the indication indicates that the second resource pattern for the subset of the one or more time resource units is aperiodic.

8. The apparatus of claim 1, wherein the second resource pattern is applicable to a single component carrier of the TDD transmit slot format pattern.

9. The apparatus according to claim 1, further comprising: at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to: The second resource pattern is configured to the subset of the one or more time resource units based on an application time after an event associated with receiving the indication.

10. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: receiving a first resource allocation pattern for time resource units of a time division duplex (TDD) transmit slot format mode, wherein one of a full duplex (FD) communication mode or a non-FD communication mode is indicated for the time resource units based on the first resource allocation pattern; receiving an indication configured to indicate a second resource allocation pattern for the time resource unit, a first value of the indication configured to indicate that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and a second value of the indication configured to indicate that the second resource allocation pattern is different from the first resource allocation pattern; as well as Communicating with a network entity in the time resource unit using a communication pattern based on the TDD transmit slot format pattern and the indication.

11. The apparatus according to claim 10, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD downlink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one uplink frequency subband for the time resource unit. 12 . The apparatus of claim 11 , wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode.

13. An apparatus according to claim 10, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit. 14 . The apparatus of claim 13 , wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode.

15. An apparatus according to claim 10, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit. 16 . The apparatus of claim 15 , wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD flexible communication mode.

17. The apparatus according to claim 15, further comprising: at least one antenna coupled to the at least one processor, wherein the at least one processor is further configured to: A configuration is received for configuring the second value of the indication to correspond to a non-FD downlink communication mode, a non-FD uplink communication mode, or the non-FD flexible communication mode.

18. The apparatus of claim 10, wherein the first resource allocation mode indicates changing the communication mode of the time resource unit from a non-FD uplink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit. 19 . The apparatus of claim 18 , wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode.

20. An apparatus according to claim 19, wherein the indicated third value for the time resource unit indicates that the second resource allocation pattern includes a first change in the size of at least one of the uplink frequency subband and the downlink frequency subband of the time resource unit, or indicates that the second resource allocation pattern includes a second change in the subband pattern of the time resource unit.

21. The apparatus of claim 19, wherein the indicated third value for the time resource unit indicates transitioning the communication mode of the time resource unit from the FD communication mode to a non-FD downlink communication mode.

22. An apparatus according to claim 10, wherein the first resource allocation mode indicates the non-FD communication mode of the second time resource unit used for the TDD transmission time slot format mode, and wherein the third value of the indication for the second time resource unit indicates that the communication mode of the second time resource unit is converted from the non-FD communication mode to the FD communication mode.

23. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: outputting a first resource pattern of one or more time resource units for a time division duplex (TDD) transmit slot format pattern, wherein one of a full-duplex (FD) communication mode or a non-FD communication mode is indicated for each of the one or more time resource units based on the first resource pattern; outputting an indication indicating a second resource mode for a subset of the one or more time resource units; as well as Communicating in each corresponding time resource unit uses a communication pattern based on the second resource pattern.

24. The device according to claim 23, wherein For a first time resource unit of the one or more time resource units, a first value of the indication indicates that the first resource pattern and the second resource pattern are the same resource pattern, and a second value of the indication indicates that the first resource pattern and the second resource pattern are different resource patterns.

25. The apparatus of claim 23 , wherein the indication indicates that the second resource pattern for the subset of the one or more time resource units is periodic, and wherein the indication comprises a bitmap of one or more code points, and each code point of the bitmap corresponds to a different time resource unit in the subset of the one or more time resource units.

26. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: outputting a first resource allocation pattern for a time resource unit of a time division duplex (TDD) transmit slot format mode, wherein one of a full duplex (FD) communication mode or a non-FD communication mode is indicated for the time resource unit based on the first resource allocation pattern; outputting an indication indicating a second resource allocation pattern for the time resource unit, a first value of the indication being configured to indicate that the second resource allocation pattern and the first resource allocation pattern are the same resource allocation pattern, and the second value of the indication is configured to indicate that the second resource allocation mode is different from the first resource allocation mode; as well as Communicating in the time resource unit using a communication pattern based on the TDD transmit slot format pattern and the indication.

27. An apparatus according to claim 26, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD downlink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one uplink frequency subband for the time resource unit, and wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD downlink communication mode.

28. An apparatus according to claim 26, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband and at least one uplink frequency subband for the time resource unit.

29. An apparatus according to claim 26, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is converted from a non-FD flexible communication mode to the FD communication mode, and the first resource allocation mode further configures at least one flexible frequency subband and at least one uplink frequency subband for the time resource unit.

30. An apparatus according to claim 26, wherein the first resource allocation mode indicates that the communication mode of the time resource unit is changed from a non-FD uplink communication mode to the FD communication mode, and the first resource allocation mode further configures at least one downlink frequency subband for the time resource unit, and wherein the second value of the indication indicates that the communication mode of the time resource unit is to fall back from the FD communication mode to the non-FD uplink communication mode.

Images