COMMON SEARCH SPACE COLLISION HANDLING FOR SUB-BAND FULL DUPLEX SETS OF SYMBOLS

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive configuration information that schedules a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) in a sub-band full duplex (SBFD) set of symbols. The UE may receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The UE may perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for common search space collision handling for sub-band full duplex sets of symbols.

BACKGROUND

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving configuration information that schedules a physical downlink control channel (PDCCH) communication associated with a common search space (CSS) in a sub-band full duplex (SBFD) set of symbols. The method may include receiving an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The method may include performing one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The method may include transmitting, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The method may include performing one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or any combination, to receive configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The one or more processors may be configured, individually or any combination, to receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The one or more processors may be configured, individually or any combination, to perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or any combination, to transmit, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The one or more processors may be configured, individually or any combination, to transmit, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The one or more processors may be configured, individually or any combination, to perform one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The set of instructions, when executed by one or more processors of the UE, may cause the UE to perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The set of instructions, when executed by one or more processors of the network node, may cause the network node to perform one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The apparatus may include means for receiving an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The apparatus may include means for performing one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The apparatus may include means for transmitting, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The apparatus may include means for performing one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

DETAILED DESCRIPTION

In some examples, a user equipment (UE) may be configured to receive a downlink communication in a full duplex (FD) slot and/or a FD set of symbols, such as within a sub-band FD (SBFD) slot and/or a SBFD set of symbols. For example, the UE may be configured with a common search space (CSS) that is associated with monitoring occasions (MOs) for receiving a physical downlink control channel (PDCCH) that occur within an SBFD set of symbols. In examples in which a PDCCH communication associated with a CSS (sometimes referred to herein as a CSS PDCCH communication) collides with SBFD symbols, an SBFD-aware UE (a UE for which a network node's SBFD operation is non-transparent to the UE) may be aware of a collision between the CSS PDCCH communication and the SBFD symbols, but may be unaware of how to handle the collision. Accordingly, whether a particular UE receives or transmits a particular communication in a collision scenario may be left to UE implementation. This may result in a UE missing important control information or other high-priority traffic from a network node and/or a UE selectively transmitting or receiving communications in a transparent manner to the network node, resulting in increased communication errors and thus high power, computing, and network resource consumption for purposes of correcting communication errors. Additionally, or alternatively, in order to avoid communication errors or for a similar purpose, a network node may simply refrain from configuring CSS symbols (e.g., symbols associated with MOs for receiving a CSS PDCCH communication) as SBFD symbols, thus forgoing benefits associated with SBFD operation, such as latency reduction, uplink coverage enhancement, or flexible allocation of uplink and downlink resources, among other benefits.

Some techniques and apparatuses described herein enable enhanced collision handling for SBFD-aware UEs, such as collision handling for a CSS configured with MOs occurring in SBFD symbols. In some aspects, a UE may receive configuration information that schedules a CSS PDCCH communication in an SBFD set of symbols. Moreover, the UE may receive an implicit or explicit indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols, such as for a purpose of receiving or refraining from receiving the CSS PDCCH communication. Accordingly, the UE may perform one of receiving the CSS PDCCH communication or refraining from receiving the CSS PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

As a result, the UE and the network node may communicate with more transparency and/or exchange control information or other high-priority traffic, thus communicating with decreased communication errors, leading to reduced power, computing, and network resource consumption otherwise used for purposes of correcting communication errors. Moreover, the techniques and apparatuses may enable configuration of CSS symbols as SBFD symbols, resulting in latency reduction (e.g., by enabling uplink transmissions in legacy downlink slots and/or downlink reception in legacy uplink slots), enhanced uplink coverage, flexible uplink/downlink resource adaptation according to uplink/downlink traffic, and overall more efficient usage of network resources.

In some aspects, the UE120may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, the network node110may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; transmit, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and perform one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

In some aspects, the UE120includes means for receiving configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; means for receiving an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and/or means for performing one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. The means for the UE120to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, the network node110includes means for transmitting, to a UE120, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; means for transmitting, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and/or means for performing one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. The means for the network node110to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.4is a diagram illustrating an example 400 of an FD zone, a non-FD zone, and self-interference associated with FD communications, in accordance with the present disclosure. As shown, example 400 includes a network node (e.g., network node110), a UE1 (e.g., UE120), and a UE2 (e.g., another UE120). In some aspects, the network node110may be capable of FD communication. FD communication may include a contemporaneous uplink and downlink communication using the same resources. For example, the network node may perform a DL transmission to a UE1 (shown by reference number410) and may receive a UL transmission from a UE2 (shown by reference number420) using the same frequency resources and at least partially overlapping in time.

As shown by reference number430, the DL transmission from the network node may self-interfere with the UL transmission to the network node. This may be caused by a variety of factors, such as the higher transmit power for the DL transmission (as compared to the UL transmission) and/or radio frequency bleeding. Furthermore, as shown by reference number440, the UL transmission to the network node110from the UE2 may interfere with the DL transmission from the network node to the UE1, thereby diminishing DL performance of the UE1.

An FD zone is shown by reference number450and a non-FD zone is shown by reference number460. “FD zone” may refer to a time period and/or a frequency region in which a wireless communication device (e.g., a network node110, a UE120, or a similar device) performs FD communication, and “non-FD zone” may refer to a time period and/or a frequency region in which a wireless communication device performs non-FD communication. The FD zone may be associated with higher self-interference, and therefore a lower signal-to-interference-plus-noise ratio (SINR), than the non-FD zone.

In some cases, a network node110may operate using a non-overlapping uplink and downlink sub band; e.g., an SBFD scheme. “SBFD scheme” may refer to an FD mode in which a slot provides bidirectional transmission on different sub-bands within a same component carrier. Example slot structures associated with SBFD schemes are described in more detail below in connection withFIG.5.

FIG.5is a diagram illustrating an example 500 of slot structures associated with SBFD schemes, in accordance with the present disclosure. In some instances, the example slot structures shown inFIG.5may be associated with SBFD operation within a time division duplex (TDD) carrier.

SBFD operation implies simultaneous transmission and reception of downlink communications and uplink communications on a sub-band basis at a network node110. SBFD operation may enable latency reduction by permitting transmission of uplink channels and/or signals in an uplink sub-band of a semi-statically configured downlink slot (sometimes referred to as a “D slot” and/or a legacy downlink slot) and/or reception of downlink channels and/or signals in a downlink sub-band of a semi-statically configured uplink slot (sometimes referred to as a “U slot” and/or a legacy uplink slot). Additionally, or alternatively, SBFD operation may enable uplink coverage enhancement and/or flexible uplink/downlink resource adaptation according to real-time uplink/downlink traffic.

Reference numbers502and504show example TDD pattern periods associated with SBFD operation. In the example shown by reference number502, the TDD pattern period includes five slots (indexed as slot n through slot n+4). Some slots of the example TDD pattern period may include only SBFD symbols (e.g., symbols including a downlink sub-band and an uplink sub-band), and thus may be referred to as SBFD slots. For example, the first three slots of the example TDD pattern period in the example indicated by reference number502(e.g., slots n through n+2) are SBFD slots that include a downlink sub-band (shown using cross-hatching) and an uplink sub-band (shown using stippling). As shown inFIG.5, in some examples one or more sub-bands in an SBFD slot may be non-contiguous sub-bands. For example, the downlink sub-band in the SBFD slots is a non-contiguous sub-band, and thus occupies a top portion of a bandwidth associated with a component carrier and a bottom portion of the bandwidth associated with the component carrier, with the uplink sub-band occupying the middle portion of the bandwidth associated with the component carrier. In some other examples, the uplink sub-band may be a non-contiguous sub-band or both the downlink sub-band and the uplink sub-band may be contiguous sub-bands.

As further shown in the example indicted by reference number502, some slots of the example TDD pattern period may include only non-SBFD symbols (e.g., downlink-only symbols or uplink-only symbols), and thus may be referred to as downlink-only slots (e.g., D slots) or uplink-only slots (e.g., U slots). For example, the fifth slot (e.g., slot n+4) is an uplink-only slot (e.g., U slot) that includes only uplink symbols. Moreover, some slots may include both SBFD symbols and non-SBFD symbols, and thus may be referred to as a slot with mixed symbols. For example, in the example indicated by reference number502, the fourth slot (e.g., slot n+3) is a slot with mixed symbols, including SBFD symbols and uplink symbols. In such examples, the slot with mixed symbols may further include guard symbols separating the SBFD symbols from the non-SBFD symbols. Additionally, or alternatively, in some examples, a portion of the TDD frame period associated with switching between SBFD symbols and non-SBFD symbols (e.g., the portion of the TDD frame period associated with the guard symbols in the example indicated by reference number502) may be referred to as a “transition point.” In some examples, a transition point may be aligned with a slot boundary, while, in some other examples, a transition point may be within a slot (e.g., such as shown in the example indicated by reference number502).

In some examples, a TDD frame period may be limited to a maximum number of transition points, such as for a purpose of avoiding frequent switching between SBFD symbols and non-SBFD symbols. For example, a TDD frame period may be limited to a maximum of two transition points, including one transition point from non-SBFD symbols to SBFD symbols and one transition point from SBFD symbols to non-SBFD symbols. More particularly, the example TDD frame period shown in connection with reference number504includes two transition points, including a first transition point associated with switching from non-SBFD symbols to SBFD symbols (e.g., a transition point from downlink symbols to SBFD symbols shown within slot n+1) and a second transition point associated with switching from SBFD symbols to non-SBFD symbols (e.g., a transition point from SBFD symbols to uplink symbols shown within slot n+3).

In some examples, a UE120may be configured to receive, in an SBFD slot, a downlink communication from a network node110. For example, a UE120may be scheduled to receive a communication (e.g., a PDCCH communication) associated with a search space and/or a CSS (e.g., a CSS PDCCH communication) in an SBFD slot. “Search space” may refer to a set of possible locations (e.g., in time and/or frequency) where a PDCCH may be located. A control resource set (CORESET) may include one or more search spaces, such as a UE-specific search space, a group-common search space, and/or a CSS. “CSS” may refer to a set of all possible PDCCH locations across all UEs. In some aspects, a CSS may correspond to a Type 0 CSS (sometimes referred to as Type 0-PDCCH), a Type 0A CSS (sometimes referred to as Type 0A-PDCCH), a Type 1 CSS (sometimes referred to as Type 1-PDCCH), a Type 2 CSS (sometimes referred to as Type 2-PDCCH), a Type 2A CSS (sometimes referred to as Type 2A-PDCCH), or a Type 3 CSS (sometimes referred to as Type 3-PDCCH). A Type 0 CSS may be indicated using a system information (SI) radio network temporary identifier (RNTI) (SI-RNTI) for remaining minimum system information (RMSI) on a primary cell and/or may be associated with a system information block (SIB) decoding use case, such as for decoding SIB1. A Type 0A CSS may be indicated using an SI-RNTI on a primary cell and/or may also be associated with a SIB decoding use case, such as for decoding other SIBs (e.g., SIBs other than SIB1). A Type 1 CSS may be indicated using a random access RNTI (RA-RNTI), a temporary cell RNTI (TC-RNTI), or a cell RNTI (C-RNTI) on a primary cell and/or may be associated with a message 2 (Msg2) and/or message 4 (Msg4) decoding in a random access channel (RACH) use case. A Type 2 CSS may be indicated using a paging RNTI (P-RNTI) on a primary cell and/or may be associated with a paging decoding use case.

In some examples, a network node110may configure a CORESET and a search space in a way such that MOs of the search space occur in SBFD symbols, such that the MOs of the search space occur in non-SBFD symbols, such that the MOs of the search space occur in both SBFD symbols and non-SBFD symbols, such that the MOs of the search space do not overlap a boundary of a downlink sub-band in SBFD symbols, or such that the MOs of the search space do overlap a boundary of a downlink sub-band in SBFD symbols, among other examples. Accordingly, in aspects in which a CSS PDCCH communication collides with SBFD symbols, an SBFD-aware UE120(a UE120for which the network node110's SBFD operation is non-transparent to the UE120) may be aware of a collision between the PDCCH communication associated with the CSS and the SBFD symbols, but may otherwise be unaware of how to handle the collision (e.g., the UE120may not be specified and/or configured with a rule for handling the collision). Accordingly, whether a particular UE120receives or transmits a particular communication in a collision scenario may be left to UE120implementation. This may result in a UE120missing control information or other high-priority traffic from a network node110, and/or a UE120selectively transmitting or receiving communications in a transparent manner to the network node110, leading to increased communication errors; high power, computing, and network resource consumption for purposes of correcting communication errors; increased latency and reduced throughput associated with communication channels between a network node110and a UE120; and otherwise inefficient usage of network resources.

Some techniques and apparatuses described herein enable enhanced collision handling for SBFD-aware UEs, such as enhanced collision handling for a CSS configured with MOs occurring in SBFD symbols. In some aspects, a UE120may receive configuration information that schedules a PDCCH communication associated with a CSS (e.g., a CSS PDCCH communication) in an SBFD set of symbols. Moreover, the UE120may receive an implicit or explicit indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols, such as for a purpose of receiving or refraining from receiving the CSS PDCCH communication. Accordingly, the UE120may perform one of receiving the CSS PDCCH communication or refraining from receiving the CSS PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols. As a result, the UE120and the network node110may communicate with more transparency and/or exchange control information or other high-priority traffic, thus communicating with decreased communication errors, leading to reduced power, computing, and network resource consumption otherwise used for purposes of correcting communication errors; decreased latency and increased throughput associated with communication channels between the network node110and the UE120; and otherwise more efficient usage of network resources.

FIGS.6A-6Care diagrams of an example 600 associated with CSS collision handling for SBFD sets of symbols, in accordance with the present disclosure. The example 600 may be associated with a network node110(e.g., a CU, a DU, and/or an RU) communicating with a UE120. In some aspects, the network node110and the UE120may be part of a wireless network (e.g., wireless network100). The UE120and the network node110may have established a wireless connection prior to operations shown inFIGS.6A-6C. In some aspects, the network node110and/or the UE120may be capable of SBFD operation. For example, the network node110may be capable of SBFD operation and/or the UE120may be an SBFD-aware UE for which the network node110's SBFD operation is non-transparent to the UE120.

In some aspects, a UE120may not expect a set of symbols associated with a CSS (e.g., sometimes referred to herein as CSS symbols, which may be a set of symbols that is scheduled by the network node110as a MO for the UE120to receive a CSS PDCCH communication) to be configured as an SBFD set of symbols. For example, a wireless communication standard, such as a wireless communication standard promulgated by the 3GPP, may specify that CSS symbols may not be configured as SBFD symbols. For example, as shown inFIG.6A, and as indicated by reference number602, CSS symbols may be associated with downlink-only symbols within a slot, such that a CSS and/or a CSS PDCCH communication does not overlap with an uplink sub-band in the slot. In such aspects, a CSS PDCCH communication may not collide with SBFD symbols and/or uplink transmissions, and thus the UE120may not need to determine how to handle any CSS collision scenarios. Put another way, in such aspects, the UE120may only receive communications in the set of symbols associated with the CSS, and thus there is no risk of colliding communications between uplink transmissions and a CSS PDCCH communication.

In some other aspects, CSS symbols may be permitted to be configured as SBFD symbols, and thus a UE120may be capable of identifying whether to receive a downlink communication associated with the CSS symbols (e.g., a CSS PDCCH communication) based at least in part on an indication received by the UE120. Put another way, when the CSS symbols are semi-statically configured as SBFD symbols (e.g., when the CSS symbols occur within an SBFD slot), the UE120may be capable of identifying whether the CSS symbols should be treated as non-SBFD symbols, such as by treating the CSS symbols as downlink symbols (e.g., by applying an automatic gain control (AGC) gain associated with a downlink slot and/or a transmission configuration indicator (TCI) state associated with the downlink slot) in order to receive the CSS PDCCH communication.

More particularly, as shown inFIG.6Aand as indicated by reference number604, in some aspects CSS symbols may be configured as SBFD symbols (e.g., a MO associated with a CSS may overlap both downlink sub-bands and uplink sub-bands of an SBFD slot), and thus, in some aspects, the CSS symbols may be treated as downlink symbols (e.g., the UE120may not be permitted to transmit uplink communications in the uplink sub-band of the CSS symbols), such as for a purpose of receiving a CSS PDCCH communication. Put another way, in the example indicated by reference number604, the UE120may be permitted to only receive communications in the CSS symbols, and thus may not be permitted to transmit communications in the CSS symbols.

In some aspects, when treating the CSS symbols as non-SBFD symbols (e.g., downlink symbols), the UE120may be capable of receiving additional downlink communications (e.g., communications in addition to a CSS PDCCH communication) in the CSS symbols, such as another frequency division multiplexed (FDMed) downlink communication (e.g., a FDMed physical downlink shared channel (PDSCH) communication) that is rated-matched around a CORESET of the CSS. Additionally, or alternatively, when treating the CSS symbols as non-SBFD symbols (e.g., downlink symbols), the UE120may be capable of receiving downlink communications (e.g., a PDCCH communication associated with the CSS and/or any other FDMed downlink communication) in all frequency resources in the CSS symbols, including the uplink sub-band of the SBFD set of symbols. For example, as indicated by the example shown in connection with reference number604, the CSS may overlap with the uplink sub-band, and thus in some aspects the UE120may have a capability of receiving a downlink communication in all frequency resources in the CSS symbols, including those that overlap with the uplink sub-band, such as for a purpose of receiving a CORESET that at least partially overlaps with the uplink sub-band. However, in some other aspects, when treating the CSS symbols as downlink symbols, the UE120may be capable of receiving downlink communications (e.g., a PDCCH communication associated with the CSS and/or any other FDMed downlink communication) in only a downlink sub-band of the CSS symbols.

In some other aspects, a UE120may be capable of identifying whether the UE120is to transmit communications in the CSS symbols (e.g., in an uplink sub-band of the CSS symbols) and/or receive communications in the CSS symbols (e.g., in a downlink sub-band of the CSS symbols or in both the downlink sub-band and an uplink sub-band of the CSS symbols, as described above) based at least in part on an implicit or explicit indication received by the UE120. More particularly, as shown inFIG.6A, and as indicated by reference number606, the UE120may selectively receive a CSS PDCCH communication in the CSS symbols, such as by treating the CSS symbols as non-SBFD symbols, or transmit a physical uplink shared channel (PUSCH) communication in the CSS symbols, such as by treating the CSS symbols as SBFD symbols and/or by transmitting the PUSCH communication in the uplink sub-band of the CSS symbols.

For example, based at least in part on a priority rule, configuration information, explicit signaling, or the like, the UE120may identify whether to treat the CSS symbols as SBFD symbols, such as for a purpose of transmitting an uplink communication in the uplink sub-band of the SBFD set of symbols, or to treat the CSS symbols as non-SBFD symbols, such as for a purpose of receiving a CSS PDCCH communication and/or another downlink communications in the CSS symbols. In some aspects, the UE120may identify whether to treat the CSS symbols as SBFD symbols or non-SBFD symbols based at least in part on the configuration information that configures the CSS. For example, a UE120may understand a configuration of a CSS in an SBFD set of symbols as an implicit indication that uplink transmissions are not to occur in the CSS symbols (e.g., configuring CSS symbols as SBFD symbols may be an implicit indication that the set of symbols are to be treated as downlink symbols for receiving a CSS PDCCH communication). Additionally, or alternatively, a UE120may understand a scheduling communication, such as a scheduling downlink control information (DCI), that schedules an uplink transmission that at least partially overlaps with the CSS symbols as an implicit indication that uplink transmissions may occur in the CSS symbols (e.g., transmitting a scheduling DCI may be an implicit indication that that the CSS symbols are not to be treated as downlink symbols and/or that the UE120may skip PDCCH monitoring and instead transmit a communication in the CSS symbols).

Similarly, a UE120may be configured with a priority rule, such that the UE120understands that being scheduled with an higher-priority communication in the CSS symbols than the CSS PDCCH communication as an implicit indication that uplink transmissions may occur in the set of symbols (e.g., that the set of symbols are not to be treated as downlink symbols and/or that the UE120may skip PDCCH monitoring and instead transmit or receive a communication in the CSS symbols). For example, the priority rule may indicate that some semi-statically scheduled uplink transmissions may be associated with a higher priority than a priority of a CSS PDCCH communication, while some semi-statically scheduled uplink transmissions may be associated with a lower priority than a CSS PDCCH communication.

In some other aspects, the network node110may transmit, and the UE120may receive, an explicit indication (e.g., via RRC signaling, one or more MAC control elements (MAC-CEs), or one or more DCI communications, among other examples) that indicates whether the UE120should treat the CSS symbols as non-SBFD set of symbols, which is sometimes referred to herein as an explicit CSS indication. Accordingly, the UE120may identify whether to treat the CSS symbols as non-SBFD symbols (e.g., in order to receive a CSS PDCCH communication) or else treat the CSS symbols as SBFD symbols (e.g., in order to transmit an uplink communication in an uplink sub-band of the CSS symbols) based at least in part on the explicit CSS indication. Aspects of implicit and explicit indications are described in more detail below in connection withFIG.6C.

In some aspects, when CSS symbols are to be treated as non-SBFD symbols, the UE120may treat only the CSS symbols as non-SBFD symbols while treating the remaining symbols within an SBFD slots as SBFD symbols, or else the UE120may treat the CSS symbols as well as additional symbols within the slot as non-SBFD symbols. For example, as shown inFIG.6B, and as indicated by reference number608, the CSS symbols may be configured within an SBFD slot, such that the CSS symbols are associated with SBFD symbols and/or such that the CSS symbols overlap a downlink sub-band and an uplink sub-band of the SBFD slot. In some aspects, as indicated by the example shown in connection with reference number610, based on the configuration information, an implicit or explicit indication transmitted by the network node110to the UE120, a rule specified by a wireless communication standard (e.g., a wireless communication standard promulgated by the 3GPP), or otherwise, the UE120may treat only the CSS symbols as non-SBFD symbols (e.g., downlink symbols). More particularly, as shown by reference number612, in this example only the CSS symbols are treated as non-SBFD symbols (e.g., as downlink symbols), with the other symbols of the SBFD slot remaining as SBFD symbols. Treating only the CSS symbols as non-SBFD symbols may be useful in aspects in which a CSS PDCCH communication is not associated with a subsequent PDSCH communication (e.g., Type 3 CSS), and thus SBFD benefits may be maintained for the remainder of the slot (e.g., the portion of the SBFD slot not overlapping the CSS symbols).

In some other aspects, as indicated by the example shown in connection with reference number614, based on the configuration information, an implicit or explicit indication transmitted by the network node110to the UE120, a rule specified by a wireless communication standard (e.g., a wireless communication standard promulgated by the 3GPP), or otherwise, the UE120may treat the CSS symbols and an additional set of symbols (e.g., S symbols) as non-SBFD symbols (e.g., downlink symbols). More particularly, as shown by reference number616, in this example the CSS symbols and an additional S symbols are treated as non-SBFD symbols (e.g., as downlink symbols), with the other symbols of the SBFD slot remaining as SBFD symbols. In such aspects, the network node110may indicate, to the UE120, the additional quantity of symbols (e.g., S symbols) to be treated as non-SBFD symbols, such as via RRC signaling. Treating the CSS symbols and the additional S symbols as non-SBFD symbols may be useful in aspects in which a CSS PDCCH is associated with a subsequent PDSCH communication, such as aspects associated with a type of CSS other than a Type 3 CSS.

In some other aspects, as indicated by the example shown in connection with reference number618, based on the configuration information, an implicit or explicit indication transmitted by the network node110to the UE120, a rule specified by a wireless communication standard (e.g., a wireless communication standard promulgated by the 3GPP), or otherwise, the UE120may treat all OFDM symbols within a slot containing the CSS as non-SBFD symbols (e.g., downlink symbols). More particularly, as shown by reference number620, in this example all OFDM symbols of the SBFD slot are treated as non-SBFD symbols (e.g., as downlink symbols). Treating all OFDM symbols of the SBFD slot as non-SBFD symbols may be useful in aspects in which a CSS PDCCH communication is associated with a subsequent PDSCH communication, such as aspects associated with a type of CSS other than a Type 3 CSS.

FIG.6Cshows example signaling that may be utilized in accordance with CSS collision handling for SBFD sets of symbols, such as in accordance the operations described above in connection withFIGS.6A and6B. As shown inFIG.6C, and as indicated by reference number622, the network node110may transmit, and the UE120may receive, configuration information. In some aspects, the UE120may receive the configuration information via one or more of system information (e.g., a master information block (MIB) and/or a SIB, among other examples), RRC signaling, one or more MAC-CEs, and/or DCI, among other examples.

In some aspects, the configuration information may indicate one or more candidate configurations and/or communication parameters. In some aspects, the one or more candidate configurations and/or communication parameters may be selected, activated, and/or deactivated by a subsequent indication. For example, the subsequent indication may select a candidate configuration and/or communication parameter from the one or more candidate configurations and/or communication parameters. In some aspects, the subsequent indication (e.g., an indication described herein) may include a dynamic indication, such as one or more MAC-CEs and/or one or more DCI messages, among other examples.

In some aspects, the configuration information may be based at least in part on a capability of the UE120(e.g., whether the UE120is an SBFD-aware UE). In that regard, the UE120may transmit, and the network node110may receive, a capabilities report. The capabilities report may indicate whether the UE120supports a feature and/or one or more parameters related to the feature. For example, the capability information may indicate a capability and/or parameter for SBFD operation. As another example, the capabilities report may indicate whether the UE120is an SBFD-aware UE. One or more operations described herein may be based on capability information of the capabilities report. For example, the UE120may perform a communication in accordance with the capability information, or may receive configuration information that is in accordance with the capability information. In some aspects, the capabilities report may indicate UE support for collision handling when a CSS is scheduled in an SBFD set of symbols.

In some aspects, the configuration information described in connection with reference number622and/or the capabilities report may include information transmitted via multiple communications. Additionally, or alternatively, the network node110may transmit the configuration information, or a communication including at least a portion of the configuration information, before and/or after the UE120transmits the capabilities report. For example, the network node110may transmit a first portion of the configuration information before the capabilities report, the UE120may transmit at least a portion of the capabilities report, and the network node110may transmit a second portion of the configuration information after receiving the capabilities report.

In some aspects, the configuration information may schedule a PDCCH communication associated with a CSS in an SBFD set of symbols, such as within an SBFD slot624. For example, the configuration information may configure CSS symbols such that one or more MOs associated with the CSS occur within the SBFD slot624and/or overlap with an uplink sub-band of the SBFD slot624, as described above in connection with reference number608ofFIG.6B.

In that regard, the SBFD set of symbols in which the CSS is to occur (e.g., the CSS symbols) may be a subset of OFDM symbols associated with the SBFD slot624. In such aspects, the configuration information may indicate whether other SBFD symbols in the SBFD slot624are to be treated as non-SBFD symbols (e.g., downlink symbols) when the CSS symbols are treated as non-SBFD symbols, as described above in connection with the various examples shown inFIG.6B. For example, in some aspects, the configuration information may indicate that, when the CSS symbols are to be treated as non-SBFD symbols, only the CSS symbols are to be treated as non-SBFD symbols (e.g., no additional OFDM symbols within the SBFD slot are to be treated as non-SBFD symbols), such as described above in connection with reference numbers610and612ofFIG.6B. In some other aspects, the configuration information may indicate that, when the CSS symbols are to be treated as non-SBFD symbols, the CSS symbols and an additional set of OFDM symbols (e.g., S OFDM symbols) of the SBFD slot624are to be treated as non-SBFD of symbols, as described above in connection with reference numbers614and616ofFIG.6B. In some other aspects, the configuration information may indicate that, when the CSS symbols are to be treated as non-SBFD symbols, all OFDM symbols of the SBFD slot624are to be treated as the non-SBFD set of symbols, as described above in connection with reference numbers618and620ofFIG.6B.

The UE120may configure itself based at least in part on the configuration information. In some aspects, the UE120may be configured to perform one or more operations described herein based at least in part on the configuration information.

As described above in connection withFIG.6A, in some aspects the UE120may receive an indication (e.g., an implicit indication or an explicit indication) of whether the CSS symbols are to be treated as non-SBFD symbols. For example, in some aspects, the indication of whether the CSS symbols are to be treated as non-SBFD symbols is associated with the configuration information described above in connection with reference number622. Put another way, receiving a configuration of a CSS in the SBFD slot624may implicitly indicate to the UE120that the UE120is to receive a PDCCH communication in the CSS symbols (and thus that the UE120is not to transmit an uplink communication in an uplink sub-band of the CSS symbols).

Additionally, or alternatively, the indication of whether the CSS symbols are to be treated as non-SBFD symbols may be based at least in part on a type of the CSS, such as one of a Type 0 CSS, a Type 0A CSS, a Type 1 CSS, a Type 2 CSS, a Type 2A CSS, or a Type 3 CSS. For example, a wireless communication standard (e.g., a wireless communication standard promulgated by the 3GPP) may specify that for a certain type of CSS (e.g., Type 0 CSS and/or Type 0A CSS, which may be associated with SIB1 or other system information (OSI), among other examples), an SBFD set of symbols that collides with the CSS should be treated as a non-SBFD set of symbols (e.g., converted to downlink symbols), such that a UE120does not miss SIB1, OSI, or the like. Accordingly, receiving a configuration of a certain type of CSS (e.g., Type 0 CSS or Type 0A CSS) in the SBFD slot624may implicitly indicate to the UE120that the UE120is to receive a PDCCH communication in the CSS symbols (and thus that the UE120is not to transmit an uplink communication in an uplink sub-band of the CSS symbols).

In some aspects, the network node110may transmit, and the UE120may receive, an explicit indication (e.g., an explicit CSS indication) that indicates whether the UE120is to treat the CSS symbols as non-SBFD symbols. More particularly, as indicated by reference number626, the network node110may transmit, and the UE120may receive, an explicit CSS indication that indicates whether the UE120is to treat the CSS symbols as non-SBFD symbols. For example, the network node110may transmit, and the UE120may receive, the explicit CSS indication in aspects in which the CSS is associated with an optional CSS, such as a Type 1 CSS (e.g., a CSS associated with an RA-RNTI and/or a TC-RNTI), a Type 2 CSS and/or a Type 2A CSS (e.g., a CSS associated with a P-RNTI), or a Type 3 CSS, among other examples. In such aspects, when the explicit CSS indication indicates that the CSS symbols are to be treated as non-SBFD symbols, the UE120may assume that the portion of the SBFD slot624that collides with the CSS is a non-SBFD set of symbols (e.g., a downlink set of symbols). In that regard, the UE120may apply an AGC gain associated with the non-SBFD set of symbols (e.g., a downlink slot) for receiving a CSS PDCCH communication, the UE120may apply a TCI associated with the non-SBFD set of symbols for receiving the CSS PDCCH communication, and/or the UE120may apply another parameter associated with the non-SBFD set of symbols for receiving the CSS PDCCH communication.

On the other hand, when the explicit CSS indication indicates that the CSS symbols are not to be treated as non-SBFD symbols, the network node110may use the colliding SBFD symbols opportunistically, such as for a purpose of scheduling an uplink transmission in an uplink sub-band of the SBFD slot624when there is no broadcast or multicast scheduling associated with the SBFD slot624.

In some aspects, the explicit CSS indication may be a common indication associated with multiple CSS types (e.g., multiple ones of a Type 0 CSS, a Type 0A CSS, a Type 1 CSS, a Type 2 CSS, a Type 2A CSS, or a Type 3 CSS, among other examples), while, in some other aspects, the explicit CSS indication may be separate indication specific to a certain CSS type (e.g., the explicit CSS indication may be associated with a single CSS type, such as only one of a Type 0 CSS, a Type 0A CSS, a Type 1 CSS, a Type 2 CSS, a Type 2A CSS, or a Type 3 CSS, among other examples). In aspects in which the explicit CSS indication is a common indication, the explicit CSS indication may be transmitted by the network node110, and received by the UE120, in a SIB. In aspects in which the explicit CSS indication is a separate indication specific to a certain CSS type, the explicit CSS indication may be transmitted by the network node110, and received by the UE120, in one of a SIB or RRC signaling. For example, for an explicit CSS indication that is specific to one of a Type 1 CSS, a Type 2 CSS, or a Type 2A CSS, the explicit CSS indication may be transmitted via a SIB and/or a common PDCCH configuration information element (IE) (sometimes referred to as a PDCCHConfigCommon IE). For an explicit CSS indication that is specific to a Type 3 CSS, the explicit CSS indication may be transmitted via a search space configuration of the CSS.

In some other aspects, the indication of whether the CSS symbols are to be treated as the non-SBFD set of symbols may be associated with a scheduling communication transmitted by the network node110to the UE120. Put another way, receiving a scheduling communication that schedules an uplink communication in the CSS symbols may implicitly indicate to the UE120that the UE120is to transmit the uplink communication in the CSS symbols (and thus that the UE120is not to treat the CSS symbols as non-SBFD symbols to receive the PDCCH communication). Accordingly, as shown by reference number628, the network node110may transmit, and the UE120may receive, a scheduling communication scheduling an uplink transmission in the SBFD set of symbols, which may serve as the indication of whether the CSS symbols are to be treated as non-SBFD symbols.

Additionally, or alternatively, the indication of whether the CSS symbols are to be treated as the non-SBFD set of symbols may be based on a priority of overlapping communications scheduled in the SBFD slot624. For example, the UE120may be configured (e.g., via the configuration information described above in connection with reference number622) with priority information indicating a priority level of certain communications that may be scheduled in the SBFD slot624. Accordingly, when the scheduling communication described above in connection with reference number628schedules an uplink transmission that overlaps the CSS PDCCH communication and that is associated with a higher priority than a priority associated with the CSS PDCCH communication, then the UE120may refrain from monitoring the CSS and instead transmit the uplink communication (e.g., the UE120may not treat the CSS symbols as non-SBFD symbols). On the other hand, when the scheduling communication described above in connection with reference number628schedules an uplink transmission that is associated with a lower priority than a priority associated with the CSS PDCCH communication, then the UE120may refrain from transmitting the uplink communication and may instead monitor the CSS for the PDCCH communication (e.g., the UE120may treat the CSS symbols as non-SBFD symbols).

Moreover, in aspects in which the CSS symbols are not to be treated as non-SBFD symbols, the network node110may opportunistically use the SBFD slots for scheduling certain downlink communications and/or simultaneous downlink/uplink scheduling, such as when the network node110refrains from transmitting a PDCCH communication associated with the CSS in the CSS symbols. For example, the network node110may dynamically use the CSS symbols for broadcast or multicast PDCCH and/or PDSCH scheduling, or simultaneous downlink/uplink scheduling, among other examples. In such aspects, the communication shown in connection with reference number628may be used as a scheduling communication that schedules one of a downlink communication or an uplink communication in the SBFD slot624. Aspects of uplink communications or downlink communications that may be received in the SBFD set of symbols are described in more detail below in connection with reference numbers630-634.

As indicated by reference number630, the network node110may selectively transmit, and/or the UE120may selectively receive, the PDCCH communication that is associated with the CSS (e.g., the CSS PDCCH communication). More particularly, the network node110may perform one of transmitting, to the UE120, the CSS PDCCH communication or refraining from transmitting the CSS PDCCH communication based on whether the CSS symbols are to be treated as non-SBFD symbols, and/or the UE120may perform one of receiving the CSS PDCCH communication or refraining from receiving the CSS PDCCH communication based on whether the CSS symbols are to be treated as non-SBFD symbols. In aspects in which the network node110transmits the CSS PDCCH communication and/or in aspects in which the UE120receives the CSS PDCCH communication, the CSS PDCCH communication may be transmitted by the network node110and/or received by the UE120in only a downlink sub-band of the SBFD slot624. Put another way, the CSS symbols may still be treated as SBFD symbols and thus the UE120may be expected to monitor only the downlink sub-band of the CSS symbols for the CSS PDCCH communication.

In some other aspects, the CSS PDCCH communication may be transmitted by the network node110and/or received by the UE120in a downlink sub-band of the SBFD slot624and an uplink sub-band of the SBFD slot624. Put another way, the UE120may be configured to receive the CSS PDCCH communication (and/or any additional downlink transmission, such as a FDMed PUSCH communication that is rate-matched around the CORESET of the CSS) in all frequency resources in the CSS symbols, including the uplink sub-band, such as by treating the CSS symbols as non-SBFD symbols. In such aspects, the UE120may receive the PDCCH communication based at least in part on applying at least one of AGC gain associated with a non-SBFD slot (e.g., a downlink slot) or a TCI state associated with the non-SBFD slot (e.g., the downlink slot).

Moreover, as described above in connection with reference number628, in some aspects the network node110may schedule an uplink communication and/or a downlink communication in the SBFD slot624, such as an uplink communication and/or a downlink communication that at least partially overlaps with the CSS symbols. Accordingly, as indicated by reference number632, the UE120may transmit, and the network node110may receive, an uplink communication in the CSS symbols of the SBFD slot624, and/or, as indicated by reference number634, the network node110may transmit, and the UE120may receive, a downlink communication in the CSS symbols of the SBFD slot624. For example, UE120may transmit the uplink communication based at least in part on the uplink communication being associated with a higher priority than a priority associated with the CSS PDCCH communication. Additionally, or alternatively, the network node110may transmit the downlink communication (e.g., a PUSCH communication associated with the CSS PDCCH communication) in symbols following the CSS symbols (as described above in connection with reference numbers614-620ofFIG.6B) and/or another downlink communication that at least partially overlaps with the CSS symbols (e.g., broadcast and/or multicast PDCCH and/or PDSCH scheduling when no CSS PDCCH is to be transmitted).

In some aspects, whether UE120is to transmit the uplink communication shown in connection with reference number632may be based at least in part on a type of the uplink communication that is scheduled. For example, the UE120may refrain from transmitting certain semi-statically scheduled uplink transmission in the CSS symbols based at least in part on the CSS symbols not being treated as the non-SBFD symbols. For example, the UE120may not be permitted to transmit a periodic sounding reference signal (P-SRS) communication, a configured grant physical uplink shared channel (CG-PUSCH) communication, a periodic physical uplink control channel (P-PUCCH) communication, or the like in an SBFD slot that collides with a CSS. Accordingly, in such aspects the UE120may refrain from transmitting a P-SRS communication, a CG-PUSCH communication, a P-PUCCH communication, and/or a similar semi-statically scheduled uplink transmission in the CSS symbols. Additionally, or alternatively, the UE120may be permitted to transmit a dynamically scheduled uplink transmission in the CSS symbols (e.g., the network node110may implicitly indicate that the UE120does not need to monitor for a CSS PDCCH communication when the network node110dynamically schedules an uplink transmission that at least partially overlaps with the CSS symbols, as described above in connection with reference number628). Accordingly, based at least in part on being scheduled with a dynamic uplink transmission (e.g., via the scheduling communication described above in connection with reference number628) and/or receiving an implicit or explicit indication that the CSS symbols are not to be treated as non-SBFD symbols, the UE120may transmit the dynamically scheduled uplink transmission in the operations shown in connection with reference number632.

Based at least in part on the UE120and/or the network node110performing CSS collision handling in SBFD sets of symbols, the UE120and/or the network node110may conserve computing, power, network, and/or communication resources that may have otherwise been consumed by correcting communication errors associated with colliding communications in SBFD sets of symbols. For example, based at least in part on the UE120and/or the network node110performing CSS collision handling in SBFD sets of symbols, the UE120and the network node110may communicate with a reduced error rate, which may conserve computing, power, network, and/or communication resources that may have otherwise been consumed to detect and/or correct communication errors.

As indicated above,FIGS.6A-6Care provided as an example. Other examples may differ from what is described with respect toFIGS.6A-6C.

FIG.7is a diagram illustrating an example process700performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process700is an example where the apparatus or the UE (e.g., UE120) performs operations associated with CSS collision handling for SBFD sets of symbols.

As shown inFIG.7, in some aspects, process700may include receiving configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols (block710). For example, the UE (e.g., using reception component902and/or communication manager906, depicted inFIG.9) may receive configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols, as described above.

As further shown inFIG.7, in some aspects, process700may include receiving an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols (block720). For example, the UE (e.g., using reception component902and/or communication manager906, depicted inFIG.9) may receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols, as described above.

As further shown inFIG.7, in some aspects, process700may include performing one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols (block730). For example, the UE (e.g., using communication manager906, depicted inFIG.9) may perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols, as described above.

In a first aspect, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is associated with the configuration information, and performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on treating the SBFD set of symbols as the non-SBFD set of symbols.

In a second aspect, alone or in combination with the first aspect, process700includes receiving the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

In a third aspect, alone or in combination with one or more of the first and second aspects, process700includes receiving the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is a communication that schedules, in the SBFD set of symbols, an uplink transmission that is associated with a higher priority than a priority associated with the PDCCH communication, and performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes refraining from receiving the PDCCH communication based at least in part on receiving the communication that schedules the uplink transmission.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is based at least in part on a type of the CSS that is associated with the PDCCH communication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the type of the CSS is one of a Type 0 CSS or a Type 0A CSS, and performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on the type of the CSS being the one of the Type 0 CSS or the Type 0A CSS.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is an explicit CSS indication.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the explicit CSS indication indicates that the SBFD set of symbols is to be treated as the non-SBFD set of symbols, and performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on applying at least one of an automatic gain control gain associated with a non-SBFD slot or a transmission configuration indicator state associated with the non-SBFD slot.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the explicit CSS indication indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process700further comprises receiving a scheduling communication scheduling an uplink transmission in the SBFD set of symbols.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the explicit CSS indication is associated with multiple CSS types, and the explicit CSS indication is received via a system information block.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the explicit CSS indication is associated with a single CSS type, and the explicit CSS indication is received via one of a SIB or RRC signaling.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the single CSS type is one of a Type 1 CSS, a Type 2 CSS, or a Type 2A CSS, and the explicit CSS indication is received via the SIB or a common PDCCH configuration associated with the RRC signaling.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the single CSS type is a Type 3 CSS, and the explicit CSS indication is received via a search space configuration of the CSS.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that only the subset of OFDM symbols overlapping with CSS symbols are to be treated as the non-SBFD set of symbols.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that the subset of OFDM symbols overlapping with CSS symbols and an additional set of OFDM symbols in the SBFD slot that are non-overlapping with the CSS symbols are to be treated as the non-SBFD set of symbols.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that all OFDM symbols, of the SBFD slot, are to be treated as the non-SBFD set of symbols.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process700further comprises receiving a scheduling communication that schedules one of a downlink communication or an uplink communication in the SBFD set of symbols.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process700further comprises refraining from transmitting a semi-statically scheduled uplink transmission in the SBFD set of symbols based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process700further comprises transmitting a dynamically scheduled uplink transmission in the SBFD set of symbols.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process700further comprises applying at least one of an automatic gain control gain associated with an SBFD slot or a transmission configuration indicator state associated with the SBFD slot based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

FIG.8is a diagram illustrating an example process800performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process800is an example where the apparatus or the network node (e.g., network node110) performs operations associated with CSS collision handling for SBFD sets of symbols.

As shown inFIG.8, in some aspects, process800may include transmitting, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols (block810). For example, the network node (e.g., using transmission component1004and/or communication manager1006, depicted inFIG.10) may transmit, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols, as described above.

As further shown inFIG.8, in some aspects, process800may include transmitting, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols (block820). For example, the network node (e.g., using transmission component1004and/or communication manager1006, depicted inFIG.10) may transmit, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols, as described above.

As further shown inFIG.8, in some aspects, process800may include performing one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols (block830). For example, the network node (e.g., using communication manager1006, depicted inFIG.10) may perform one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols, as described above.

In a first aspect, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is associated with the configuration information, and performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication based at least in part on treating the SBFD set of symbols as the non-SBFD set of symbols.

In a second aspect, alone or in combination with the first aspect, process800includes transmitting, to the UE, the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

In a third aspect, alone or in combination with one or more of the first and second aspects, process800includes transmitting, to the UE, the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is a communication that schedules, in the SBFD set of symbols, an uplink transmission that is associated with a higher priority than a priority of the PDCCH communication, and performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes refraining from transmitting the PDCCH communication based at least in part on transmitting the communication that schedules the uplink transmission.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is based at least in part on a type of the CSS that is associated with the PDCCH communication.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the type of the CSS is one of a Type 0 CSS or a Type 0A CSS, and performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication based at least in part on the type of the CSS being the one of the Type 0 CSS or the Type 0A CSS.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is an explicit CSS indication.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the explicit CSS indication indicates that the SBFD set of symbols is to be treated as the non-SBFD set of symbols, and performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication using at least a transmission configuration indicator state associated with the non-SBFD slot.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the explicit CSS indication indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process800further comprises transmitting, to the UE, a scheduling communication scheduling an uplink transmission in the SBFD set of symbols.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the explicit CSS indication is associated with multiple CSS types, and the explicit CSS indication is transmitted via a system information block.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the explicit CSS indication is associated with a single CSS type, and the explicit CSS indication is transmitted via one of a SIB or RRC signaling.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the single CSS type is one of a Type 1 CSS, a Type 2 CSS, or a Type 2A CSS, and the explicit CSS indication is transmitted via the SIB or a common PDCCH configuration associated with the RRC signaling.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the single CSS type is a Type 3 CSS, and the explicit CSS indication is transmitted via a search space configuration of the CSS.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that only the subset of OFDM symbols overlapping with CSS symbols are to be treated as the non-SBFD set of symbols.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that the subset of OFDM symbols overlapping with CSS symbols and an additional set of OFDM symbols in the SBFD slot that are non-overlapping with the CSS symbols are to be treated as the non-SBFD set of symbols.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and the configuration information further indicates that all OFDM symbols, of the SBFD slot, are to be treated as the non-SBFD set of symbols.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process800further comprises transmitting, to the UE, a scheduling communication that schedules one of a downlink communication or an uplink communication in the SBFD set of symbols.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process800further comprises refraining from receiving a semi-statically scheduled uplink transmission in the SBFD set of symbols based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process800further comprises receiving, from the UE, a dynamically scheduled uplink transmission in the SBFD set of symbols.

In a twentieth aspect, alone or in combination with one or more of the first through nineteenth aspects, the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and the process800further comprises using a transmission configuration indicator state associated with the SBFD slot based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

FIG.9is a diagram of an example apparatus900for wireless communication, in accordance with the present disclosure. The apparatus900may be a UE, or a UE may include the apparatus900. In some aspects, the apparatus900includes a reception component902, a transmission component904, and/or a communication manager906, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager906is the communication manager140described in connection withFIG.1. As shown, the apparatus900may communicate with another apparatus908, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component902and the transmission component904.

The transmission component904may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus908. In some aspects, one or more other components of the apparatus900may generate communications and may provide the generated communications to the transmission component904for transmission to the apparatus908. In some aspects, the transmission component904may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus908. In some aspects, the transmission component904may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE120described in connection withFIG.2. In some aspects, the transmission component904may be co-located with the reception component902in one or more transceivers.

The communication manager906may support operations of the reception component902and/or the transmission component904. For example, the communication manager906may receive information associated with configuring reception of communications by the reception component902and/or transmission of communications by the transmission component904. Additionally, or alternatively, the communication manager906may generate and/or provide control information to the reception component902and/or the transmission component904to control reception and/or transmission of communications.

The reception component902may receive configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The reception component902may receive an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The communication manager906may perform one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

The reception component902may receive the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

The reception component902may receive the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

FIG.10is a diagram of an example apparatus1000for wireless communication, in accordance with the present disclosure. The apparatus1000may be a network node, or a network node may include the apparatus1000. In some aspects, the apparatus1000includes a reception component1002, a transmission component1004, and/or a communication manager1006, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager1006is the communication manager150described in connection withFIG.1. As shown, the apparatus1000may communicate with another apparatus1008, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component1002and the transmission component1004.

The reception component1002may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus1008. The reception component1002may provide received communications to one or more other components of the apparatus1000. In some aspects, the reception component1002may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus1000. In some aspects, the reception component1002may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node110described in connection withFIG.2. In some aspects, the reception component1002and/or the transmission component1004may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus1000via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The transmission component1004may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1008. In some aspects, one or more other components of the apparatus1000may generate communications and may provide the generated communications to the transmission component1004for transmission to the apparatus1008. In some aspects, the transmission component1004may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1008. In some aspects, the transmission component1004may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node110described in connection withFIG.2. In some aspects, the transmission component1004may be co-located with the reception component1002in one or more transceivers.

The communication manager1006may support operations of the reception component1002and/or the transmission component1004. For example, the communication manager1006may receive information associated with configuring reception of communications by the reception component1002and/or transmission of communications by the transmission component1004. Additionally, or alternatively, the communication manager1006may generate and/or provide control information to the reception component1002and/or the transmission component1004to control reception and/or transmission of communications.

The transmission component1004may transmit, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols. The transmission component1004may transmit, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols. The communication manager1006may perform one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

The transmission component1004may transmit, to the UE, the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

The transmission component1004may transmit, to the UE, the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

Aspect 1: A method of wireless communication performed by a UE, comprising: receiving configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; receiving an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and performing one of receiving the PDCCH communication or refraining from receiving the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Aspect 2: The method of Aspect 1, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is associated with the configuration information, and wherein performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on treating the SBFD set of symbols as the non-SBFD set of symbols.

Aspect 3: The method of Aspect 2, further comprising receiving the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

Aspect 4: The method of Aspect 2, further comprising receiving the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

Aspect 5: The method of any of Aspects 1-4, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is a communication that schedules, in the SBFD set of symbols, an uplink transmission that is associated with a higher priority than a priority associated with the PDCCH communication, and wherein performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes refraining from receiving the PDCCH communication based at least in part on receiving the communication that schedules the uplink transmission.

Aspect 6: The method of any of Aspects 1-5, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is based at least in part on a type of the CSS that is associated with the PDCCH communication.

Aspect 7: The method of Aspect 6, wherein the type of the CSS is one of a Type 0 CSS or a Type 0A CSS, and wherein performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on the type of the CSS being the one of the Type 0 CSS or the Type 0A CSS.

Aspect 8: The method of any of Aspects 1-7, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is an explicit CSS indication.

Aspect 9: The method of Aspect 8, wherein the explicit CSS indication indicates that the SBFD set of symbols is to be treated as the non-SBFD set of symbols, and wherein performing the one of receiving the PDCCH communication or refraining from receiving the PDCCH communication includes receiving the PDCCH communication based at least in part on applying at least one of an automatic gain control gain associated with a non-SBFD slot or a transmission configuration indicator state associated with the non-SBFD slot.

Aspect 10: The method of Aspect 8, wherein the explicit CSS indication indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises receiving a scheduling communication scheduling an uplink transmission in the SBFD set of symbols.

Aspect 11: The method of Aspect 8, wherein the explicit CSS indication is associated with multiple CSS types, and wherein the explicit CSS indication is received via a system information block.

Aspect 12: The method of Aspect 8, wherein the explicit CSS indication is associated with a single CSS type, and wherein the explicit CSS indication is received via one of a SIB or RRC signaling.

Aspect 13: The method of Aspect 12, wherein the single CSS type is one of a Type 1 CSS, a Type 2 CSS, or a Type 2A CSS, and wherein the explicit CSS indication is received via the SIB or a common PDCCH configuration associated with the RRC signaling.

Aspect 14: The method of Aspect 12, wherein the single CSS type is a Type 3 CSS, and wherein the explicit CSS indication is received via a search space configuration of the CSS.

Aspect 15: The method of any of Aspects 1-14, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that only the subset of OFDM symbols overlapping with CSS symbols are to be treated as the non-SBFD set of symbols.

Aspect 16: The method of any of Aspects 1-14, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that the subset of OFDM symbols overlapping with CSS symbols and an additional set of OFDM symbols in the SBFD slot that are non-overlapping with the CSS symbols are to be treated as the non-SBFD set of symbols.

Aspect 17: The method of any of Aspects 1-14, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that all OFDM symbols, of the SBFD slot, are to be treated as the non-SBFD set of symbols.

Aspect 18: The method of any of Aspects 1-17, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises receiving a scheduling communication that schedules one of a downlink communication or an uplink communication in the SBFD set of symbols.

Aspect 19: The method of any of Aspects 1-18, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises refraining from transmitting a semi-statically scheduled uplink transmission in the SBFD set of symbols based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

Aspect 20: The method of any of Aspects 1-19, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises transmitting a dynamically scheduled uplink transmission in the SBFD set of symbols.

Aspect 21: The method of any of Aspects 1-20, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises applying at least one of an automatic gain control gain associated with an SBFD slot or a transmission configuration indicator state associated with the SBFD slot based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

Aspect 22: A method of wireless communication performed by a network node, comprising: transmitting, to a UE, configuration information that schedules a PDCCH communication associated with a CSS in an SBFD set of symbols; transmitting, to the UE, an indication of whether the SBFD set of symbols is to be treated as a non-SBFD set of symbols; and performing one of transmitting, to the UE, the PDCCH communication or refraining from transmitting the PDCCH communication based on whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols.

Aspect 23: The method of Aspect 22, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is associated with the configuration information, and wherein performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication based at least in part on treating the SBFD set of symbols as the non-SBFD set of symbols.

Aspect 24: The method of Aspect 23, further comprising transmitting, to the UE, the PDCCH communication only in one or more downlink sub-bands associated with the SBFD set of symbols.

Aspect 25: The method of Aspect 23, further comprising transmitting, to the UE, the PDCCH communication in one or more downlink sub-bands associated with the SBFD set of symbols and one or more uplink sub-bands or guard bands associated with the SBFD set of symbols.

Aspect 26: The method of any of Aspects 22-25, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is a communication that schedules, in the SBFD set of symbols, an uplink transmission that is associated with a higher priority than a priority of the PDCCH communication, and wherein performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes refraining from transmitting the PDCCH communication based at least in part on transmitting the communication that schedules the uplink transmission.

Aspect 27: The method of any of Aspects 22-26, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is based at least in part on a type of the CSS that is associated with the PDCCH communication.

Aspect 28: The method of Aspect 27, wherein the type of the CSS is one of a Type 0 CSS or a Type 0A CSS, and wherein performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication based at least in part on the type of the CSS being the one of the Type 0 CSS or the Type 0A CSS.

Aspect 29: The method of any of Aspects 22-28, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols is an explicit CSS indication.

Aspect 30: The method of Aspect 29, wherein the explicit CSS indication indicates that the SBFD set of symbols is to be treated as the non-SBFD set of symbols, and wherein performing the one of transmitting the PDCCH communication or refraining from transmitting the PDCCH communication includes transmitting the PDCCH communication using at least a transmission configuration indicator state associated with the non-SBFD slot.

Aspect 31: The method of Aspect 29, wherein the explicit CSS indication indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises transmitting, to the UE, a scheduling communication scheduling an uplink transmission in the SBFD set of symbols.

Aspect 32: The method of Aspect 29, wherein the explicit CSS indication is associated with multiple CSS types, and wherein the explicit CSS indication is transmitted via a system information block.

Aspect 33: The method of Aspect 29, wherein the explicit CSS indication is associated with a single CSS type, and wherein the explicit CSS indication is transmitted via one of a SIB or RRC signaling.

Aspect 34: The method of Aspect 33, wherein the single CSS type is one of a Type 1 CSS, a Type 2 CSS, or a Type 2A CSS, and wherein the explicit CSS indication is transmitted via the SIB or a common PDCCH configuration associated with the RRC signaling.

Aspect 35: The method of Aspect 33, wherein the single CSS type is a Type 3 CSS, and wherein the explicit CSS indication is transmitted via a search space configuration of the CSS.

Aspect 36: The method of any of Aspects 22-35, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that only the subset of OFDM symbols overlapping with CSS symbols are to be treated as the non-SBFD set of symbols.

Aspect 37: The method of any of Aspects 22-35, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that the subset of OFDM symbols overlapping with CSS symbols and an additional set of OFDM symbols in the SBFD slot that are non-overlapping with the CSS symbols are to be treated as the non-SBFD set of symbols.

Aspect 38: The method of any of Aspects 22-35, wherein the SBFD set of symbols is a subset of OFDM symbols associated with an SBFD slot, and wherein the configuration information further indicates that all OFDM symbols, of the SBFD slot, are to be treated as the non-SBFD set of symbols.

Aspect 39: The method of any of Aspects 22-38, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises transmitting, to the UE, a scheduling communication that schedules one of a downlink communication or an uplink communication in the SBFD set of symbols.

Aspect 40: The method of any of Aspects 22-39, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises refraining from receiving a semi-statically scheduled uplink transmission in the SBFD set of symbols based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

Aspect 41: The method of any of Aspects 22-40, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises receiving, from the UE, a dynamically scheduled uplink transmission in the SBFD set of symbols.

Aspect 42: The method of any of Aspects 22-41, wherein the indication of whether the SBFD set of symbols is to be treated as the non-SBFD set of symbols indicates that the SBFD set of symbols is not to be treated as the non-SBFD set of symbols, and wherein the method further comprises using a transmission configuration indicator state associated with the SBFD slot based at least in part on the SBFD set of symbols not being treated as the non-SBFD set of symbols.

Aspect 45: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-42.