WO2025251328A1

WO2025251328A1 - Mapping of synchronization signal blocks to configured grant occasions in configured grant small data transfer for subband full duplex

Info

Publication number: WO2025251328A1
Application number: PCT/CN2024/098298
Authority: WO
Inventors: Chiranjib Saha; Muhammad Sayed Khairy Abdelghaffar; Shankar Krishnan; Ruiming Zheng; Umesh PHUYAL; Prasada Veera Reddy KADIRI
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-06-08
Filing date: 2024-06-08
Publication date: 2025-12-11
Anticipated expiration: 2026-12-08

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of synchronization signal blocks (SSBs) to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols. The UE may transmit, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions. Numerous other aspects are described.

Description

MAPPING OF SYNCHRONIZATION SIGNAL BLOCKS TO CONFIGURED GRANT OCCASIONS IN CONFIGURED GRANT SMALL DATA TRANSFER FOR SUBBAND FULL DUPLEX

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for mapping of synchronization signal blocks to configured grant occasions in configured grant small data transfer for subband full duplex.

BACKGROUND

Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and/or other traffic. The services may include unicast, multicast, and/or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and/or device transmit power, among other examples) . Examples of such multiple-access RATs include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR) . NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication) , massive multiple-input multiple-output (MIMO) , disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and/or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.

SUMMARY

Some aspects described herein relate to an apparatus for wireless communication at a user equipment (UE) . The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to receive a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of synchronization signal blocks (SSBs) to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols. The one or more processors may be configured to cause the UE to transmit, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.

Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network node to transmit a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The one or more processors may be configured to cause the network node to receive, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The method may include transmitting, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The method may include receiving, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication. The set of instructions may include one or more instructions that, when executed by one or more processors of a UE, may cause the UE to receive a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The set of instructions may include one or more instructions that, when executed by one or more processors of the UE, may cause the UE to transmit, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication. The set of instructions may include one or more instructions that, when executed by one or more processors of a network node, may cause the network node to transmit a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The set of instructions may include one or more instructions that, when executed by one or more processors of the network node, may cause the network node to receive, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The apparatus may include means for transmitting, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The apparatus may include means for receiving, in accordance with the mapping, an SDT communication in at least one of the CG occasions.

Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and/or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

Fig. 1 is a diagram illustrating an example of a wireless communication network, in accordance with the present disclosure.

Fig. 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network, in accordance with the present disclosure.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

Fig. 4 is a diagram illustrating examples of full-duplex communication in a wireless network, in accordance with the present disclosure.

Fig. 5 is a diagram illustrating an example of uplink configured grant (CG) communication, in accordance with the present disclosure.

Fig. 6 is a diagram illustrating an example of CG-based small data transfer (SDT) , in accordance with the present disclosure.

Fig. 7 is a diagram illustrating an example of subband full duplex (SBFD) -specific CG-SDT, in accordance with the present disclosure.

Fig. 8 is a diagram illustrating an example associated with signaling for synchronization signal block (SSB) -to-CG mapping for SBFD CGs, in accordance with the present disclosure.

Fig. 9 is a diagram illustrating an example associated with a CG-SDT configuration, in accordance with the present disclosure.

Fig. 10 is a diagram illustrating examples associated with indication of SBFD-CG occasions, in accordance with the present disclosure.

Fig. 11 is a diagram illustrating examples associated with UE handling of association periods and association period patterns, in accordance with the present disclosure.

Fig. 12 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.

Fig. 13 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.

Fig. 14 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

Fig. 15 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and/or functionalities in addition to or other than the structures and/or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

A user equipment (UE) may transmit a short data burst, referred to as a small data transfer (SDT) to a network node. In some examples, the network node may configure the UE with a configured grant (CG) SDT (CG-SDT) configuration. The UE may, in accordance with the CG-SDT, transmit a CG-SDT communication while the UE is in a radio resource control (RRC) idle state, an RRC inactive state, and/or another power-saving state. The UE may transmit the CG-SDT communication in a CG-SDT uplink transmission occasion, which is a resource in a time and frequency domain in which the network node is available for reception of CG-SDT communications. CG-SDT may allow a grant-free uplink transmission to occur while the UE is in an RRC idle state, an RRC inactive state, and/or another power-saving state (e.g., without dedicating signaling overhead and/or other resources to transitioning to an RRC active state) .

A network node may also transmit a synchronization signal block (SSB) communication to provide control information to the UE. For example, the network node may transmit the SSB communication to convey a synchronization signal (SS) , such as a primary synchronization signal (PSS) or a secondary synchronization signal (SSS) , and a physical broadcast channel (PBCH) , among other examples. In some examples, SSBs may be associated with different possible beams, and a UE may select a particular beam for transmitting the CG-SDT communication. Accordingly, there may be a mapping of SSBs to CG-SDT uplink transmission occasions that enables the network node to identify an SSB beam that a UE has selected by detecting which CG-SDT uplink transmission occasion the UE used to transmit the CG-SDT communication. Similarly, the UE may use the mapping to select a CG-SDT uplink transmission occasion to use for transmitting the CG-SDT communication based at least in part on an SSB that the UE has selected. The mapping between SSBs and CG-SDT uplink transmission occasions may help the UE and the network node to remain synchronized with respect to selected communication configurations, such as selected beam parameters, thereby avoiding dropped communications.

In subband full duplex (SBFD) operation, a network node may transmit a downlink communication to a first UE and receive an uplink communication from a second UE at the same time, but on different frequency resources. Because SBFD involves full duplex operation at the network-side, SBFD may have a tighter link budget and/or require stronger radio propagation conditions than non-SBFD (e.g., time division duplex (TDD) ) . As a result, SBFD CG-SDT may be operable for only certain beams (e.g., beams that comply with the tighter link budget and/or stronger radio propagation conditions) . Therefore, SBFD CG-SDT communications carried via other beams may not be successfully decoded by a receiver.

Various aspects relate generally to a mapping of SSBs to CG occasions in CG-SDT for SBFD. Some aspects more specifically relate to SBFD-aware UEs configured to handle the mapping of SSBs to CG occasions in CG-SDT for SBFD in addition to a mapping of SSBs to CG occasions in CG-SDT for TDD. In some aspects, a network node may configure an SBFD-aware UE with the mapping of SSBs to CG occasions in CG-SDT for SBFD. This mapping may correlate SSBs with CG occasions in at least SBFD symbols. In some aspects, the SBFD-aware UE may transmit an SDT communication in at least one of the CG occasions to the network node in accordance with the mapping.

Some aspects may involve an association period and/or an association period pattern. An association period may include one or more CG-SDT configuration periods, which may in turn be an integer multiple of an SSB burst period. An association period pattern may include one or more association periods. In some aspects, the CG occasions may be mapped to the SSBs based at least in part on an association period and/or an association period pattern that is used for CG occasions computed by non-SBFD-aware UEs. In some aspects, the CG occasions may be mapped to the SSBs based at least in part on an association period and/or an association period pattern that is used for CG occasions computed by SBFD-aware UEs and not by non-SBFD-aware UEs.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by configure the SBFD-aware UE with the mapping of SSBs to CG occasions in CG-SDT for SBFD, the described techniques can be used to help to ensure that one or more CG-SDT communications can be decoded successfully. For example, the network node and/or the SBFD-aware UE may communicate, based at least in part on the mapping, using one or more beams that enable the CG-SDT communications comply with tight link budgets and/or strong radio propagation conditions that are commonly present in SBFD scenarios.

Mapping the CG occasions to the SSBs based at least in part on an association period and/or an association period pattern that is used for CG occasions computed by non-SBFD-aware UEs may help to reduce complexity at the SBFD-aware UE. Mapping the CG occasions to the SSBs based at least in part on an association period and/or an association period pattern that is used for CG occasions computed by SBFD-aware UEs and not by non-SBFD-aware UEs may help to ensure that the last CG occasion (s) in the SBFD-dedicated association period and/or the SBFD-dedicated association period pattern are mapped to SSB (s) .

Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB) , ultra-reliable low-latency communication (URLLC) , massive machine-type communication (mMTC) , millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV) .

As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and/or artificial intelligence or machine learning (AI/ML) , among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and/or support one or more of the foregoing use cases.

Fig. 1 is a diagram illustrating an example of a wireless communication network 100, in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.

The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and/or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless communication networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular RAT (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G/NR RAT, and/or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz) , which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz, ” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and/or that are included in mid-band frequencies. Similarly, the term “millimeter wave, ” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4-1, or FR5, and/or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and/or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS) , in which multiple RATs (for example, 4G/Long Term Evolution (LTE) and 5G/NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.

A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP) , a transmission reception point (TRP) , a mobility element, a core, a network entity, a network element, a network equipment, and/or another type of device, component, or system included in a radio access network (RAN) .

A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures) . For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack) , or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture) , meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 may implement a radio protocol stack that is physically distributed and/or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance) , or in a virtualized radio access network (vRAN) , also known as a cloud radio access network (C-RAN) , to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs) , one or more distributed units (DUs) , and/or one or more radio units (RUs) . A CU may host one or more higher layer control functions, such as RRC functions, packet data convergence protocol (PDCP) functions, and/or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and/or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT) , an inverse FFT (iFFT) , beamforming, physical random access channel (PRACH) extraction and filtering, and/or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and/or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and/or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and/or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node) .

The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and/or disaggregated network nodes, among other examples. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c. Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and/or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) , whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts) .

In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link) . The radio access link may include a downlink and an uplink. “Downlink” (or “DL” ) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL” ) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit downlink control information (DCI) (for example, scheduling information, reference signals, and/or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs) , and downlink data channels may include one or more physical downlink shared channels (PDSCHs) . Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and/or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs) , and uplink data channels may include one or more physical uplink shared channels (PUSCHs) . The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

Downlink and uplink resources may include time domain resources (frames, subframes, slots, and/or symbols) , frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and/or resource elements) , and/or spatial domain resources (particular transmit directions and/or beam parameters) . Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs) . A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs) . A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and/or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and/or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor) , leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “IAB-donor” ) . The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF) . An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “IAB-nodes” ) . Each non-anchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and/or spatial resources) may be shared between access links and backhaul links.

In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110) . In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network. ” In the example shown in Fig. 1, the network node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and/or smart jewelry, such as a smart ring or a smart bracelet) , an entertainment device (for example, a music device, a video device, and/or a satellite radio) , an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device) , a UE function of a network node, and/or any other suitable device or function that may communicate via a wireless medium.

A UE 120 and/or a network node 110 may include one or more chips, system-on-chips (SoCs) , chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs) , graphics processing units (GPUs) , neural processing units (NPUs) and/or digital signal processors (DSPs) ) , processing blocks, application-specific integrated circuits (ASIC) , programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs) ) , or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry” ) . One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.

The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM) , or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, Institute of Electrical and Electronics Engineers (IEEE) compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem) . In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC) , UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs” . An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag. Some UEs 120 may be considered IoT devices and/or may be implemented as NB-IoT (narrowband IoT) devices. An IoT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and/or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100) .

Some UEs 120 may be classified according to different categories in association with different complexities and/or different capabilities. UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and/or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and/or premium UEs that are capable of URLLC, eMBB, and/or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and/or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability) . A UE 120 of the third category may be referred to as a reduced capacity UE ( “RedCap UE” ) , a mid-tier UE, an NR-Light UE, and/or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and/or eMTC UEs, and mission-critical IoT devices and/or premium UEs. RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and/or cameras that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and/or smart city deployments, among other examples.

In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary) . As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and/or vehicle-to-pedestrian (V2P) protocols) , and/or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and/or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and/or other operations for sidelink communications.

In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half-duplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve TDD, in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time) . In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources) . By operating in a full-duplex mode, network nodes 110 and/or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation may involve frequency-division duplexing (FDD) , in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO) . Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs) , reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT) .

In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols; and transmit , in accordance with the mapping, an SDT communication in at least one of the CG occasions. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols; and receive , in accordance with the mapping, an SDT communication in at least one of the CG occasions. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network, in accordance with the present disclosure.

As shown in Fig. 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t ≥ 1) , a set of antennas 234 (shown as 234a through 234v, where v ≥ 1) , a MIMO detector 236, a receive processor 238, a data sink 239, a controller/processor 240, a memory 242, a communication unit 244, a scheduler 246, and/or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and/or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller/processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and/or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and/or other components that facilitate communication with the UE 120 or another network node.

The terms “processor, ” “controller, ” or “controller/processor” may refer to one or more controllers and/or one or more processors. For example, reference to “a/the processor, ” “a/the controller/processor, ” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig. 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and/or controller/processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and/or controller/processor 280.

In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data ( “downlink data” ) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue) . In some examples, the transmit processor 214 may select one or more modulation and coding schemes (MCSs) for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS (s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI) ) and/or control information (for example, CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and/or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , or a channel state information (CSI) reference signal (CSI-RS) ) and/or synchronization signals (for example, a primary synchronization signal (PSS) or an SSS) .

The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing (OFDM) ) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and/or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and/or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and/or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232) , may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and/or may be further processed by the receive processor 238 to obtain decoded data and/or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and/or another type of data sink) and provide the decoded control information to a processor, such as the controller/processor 240.

The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and/or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and/or frequency domain resources that the UE 120 may use to transmit and/or receive communications using an RRC configuration (for example, a semi-static configuration) , for example, to perform semi-persistent scheduling (SPS) or to configure a CG for the UE 120.

One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and/or the controller/processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , and/or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110) . In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and/or with other network nodes. The communication unit 244 may support wired and/or wireless communication protocols and/or connections, such as Ethernet, optical fiber, common public radio interface (CPRI) , and/or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and/or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and/or an interface, such as a network interface.

The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r ≥ 1) , a set of modems 254 (shown as modems 254a through 254u, where u ≥ 1) , a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, a memory 282, and/or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller/processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and/or another component that facilitates communication with the network node 110 and/or another UE 120.

For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and/or an application executed on the UE 120) , and may provide decoded control information and system information to the controller/processor 280.

For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data ( “uplink data” ) from a data source 262 (such as a data pipeline, a data queue, and/or an application executed on the UE 120) and control information from the controller/processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and/or other types of control information. In some aspects, the receive processor 258 and/or the controller/processor 280 may determine, for a received signal (such as received from the network node 110 or another UE) , one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, a CQI parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and/or another parameter. The control information may facilitate parameter selection and/or scheduling for the UE 120 by the network node 110.

The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS) , and/or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM) . The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain an uplink signal.

The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and/or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .

One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and/or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam) . For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.

The amplitudes and/or phases of signals transmitted via antenna elements and/or sub-elements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and/or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and/or a vertical direction) , and/or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and/or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and/or phases of the signal (s) to form one or more beams. The shape of a beam (such as the amplitude, width, and/or presence of side lobes) and/or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and/or amplitudes of the multiple signals relative to each other.

Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.

While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110) . The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and/or a Near-RT RIC 370 (for example, via an E2 link) . The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

In some aspects, the CU 310 may be logically split into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 may be controlled by the corresponding DU 330.

The SMO Framework 360 may support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and/or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and/or a 6G RAN, such as an open eNB (O-eNB) 380, via an O1 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflows including model training and updates, and/or policy-based guidance of applications and/or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an A1 interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and/or an O-eNB with the Near-RT RIC 370.

In some aspects, to generate AI/ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI/ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .

The network node 110, the controller/processor 240 of the network node 110, the UE 120, the controller/processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component (s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with mapping of SSBs to CG occasions in CG-SDT for SBFD, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, any other component (s) of Fig. 2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 1200 of Fig. 12, process 1300 of Fig. 13, or other processes as described herein (alone or in conjunction with one or more other processors) . The memory 242 may store data and program codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types) . The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types) . For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 1200 of Fig. 12, process 1300 of Fig. 13, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, the UE 120 includes means for receiving a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols (e.g., using antenna 252, modem 254, MIMO detector 256, receive processor 258, controller/processor 280, memory 282, and/or the like) ; and/or means for transmitting, in accordance with the mapping, a SDT communication in at least one of the CG occasions (e.g., using controller/processor 280, transmit processor 264, TX MIMO processor 266, modem 254, antenna 252, memory 282, and/or the like) . The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, the network node 110 includes means for transmitting a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols (e.g., using controller/processor 240, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, memory 242, and/or the like) ; and/or means for receiving, in accordance with the mapping, an SDT communication in at least one of the CG occasions (e.g., using antenna 234, modem 232, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, and/or the like) . The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

Fig. 4 is a diagram illustrating examples 400, 405, and 410 of full-duplex communication in a wireless network, in accordance with the present disclosure. “Full-duplex communication” in a wireless network refers to simultaneous bi-directional communication between devices in the wireless network. For example, a network node 110 operating in a full-duplex mode may transmit an uplink communication from a first UE 120a and receive a downlink communication from a second UE 120b at the same time (e.g., in the same slot or the same symbol) . “Half-duplex communication” in a wireless network refers to unidirectional communications (e.g., only downlink communication or only uplink communication) between devices at a given time (e.g., in a given slot or a given symbol) .

As shown in Fig. 4, examples 400 and 405 show examples of in-band full-duplex (IBFD) communication. In IBFD, a UE 120a may transmit an uplink communication to a network node 110 and a UE 120b receive a downlink communication from the network node 110 on the same time and frequency resources. As shown in example 400, in a first example of IBFD, the time and frequency resources for uplink communication may fully overlap with the time and frequency resources for downlink communication. As shown in example 405, in a second example of IBFD, the time and frequency resources for uplink communication may partially overlap with the time and frequency resources for downlink communication.

As further shown in Fig. 4, example 410 shows an example of SBFD communication, which may also be referred to as “sub-band frequency division duplex” (SBFDD) or “flexible duplex. ” In SBFD, a UE 120a may transmit an uplink communication to a network node 110 and a UE 120b may receive a downlink communication from the network node 110 at the same time, but on different frequency resources. For example, the different frequency resources may be sub-bands of a frequency band, such as a time division duplexing band. In this case, the frequency resources used for downlink communication may be separated from the frequency resources used for uplink communication, in the frequency domain, by a guard band.

In some examples, SBFD operation at the network node 110 within a TDD carrier may involve configuration and indication of SBFD uplink, downlink, and/or guardband subbands. For example, the network node 110 may transmit a semi-static indication of a time and/or frequency domain location of SBFD subbands to one or more UEs 120 that are in an RRC connected mode. In some examples, an indication of time and/or frequency domain locations of the SBFD subbands may be provided in a system information block (SIB) .

Additionally, or alternatively, SBFD operation at the network node 110 within a TDD carrier may involve a random access procedure on SBFD symbols. For example, the SBFD operation may support random access in SBFD symbols by one or more UEs 120 that are in an RRC connected mode. In some examples, one or more UEs 120 that are in an RRC idle or inactive mode may support SBFD operation for random access.

Additionally, or alternatively, SBFD operation at the network node 110 within a TDD carrier may involve UE transmission, reception and measurement behavior and procedures in SBFD symbols and/or non-SBFD symbols for SBFD-aware UEs 120. In some examples, the SBFD operation may involve SBFD-aware UE behavior in SBFD symbols, such as transmission and reception behaviors on SBFD subbands configured in downlink and/or flexible symbols indicated by TDD-UL-DL-ConfigCommon. For example, uplink transmissions may occur within uplink subbands only, and downlink receptions may occur within downlink subband (s) only (except for cross-link interference (CLI) measurement by the UE 120 outside of the downlink subbands) . When flexible symbols are used, uplink symbol may not be converted to downlink or SBFD symbols.

In some examples, the SBFD operation may involve enhancements on resource allocation in the frequency domain in SBFD symbols, such as partial resource block groups (RBGs) , precoding resource block group (PRG) , CSI subbands, or the like. For example, resource allocation may occur in the frequency domain for PDSCH and/or CSI-RS across two downlink subbands in SBFD symbols, and/or unaligned boundaries between SBFD subband (s) and RBG (s) , CSI reporting subband (s) , CSI-RS resource (s) , and/or PRG (s) may be handled.

In some examples, the SBFD operation may involve enhancements on physical channels, signals, and/or procedures across SBFD symbols and non-SBFD symbols in different slots. For example, each transmission or reception within a slot may have either all SBFD symbols or all non-SBFD symbols. In some examples, resource allocation in the frequency domain for transmission or reception in SBFD symbols and non-SBFD symbols may have different available frequency resources in different slots. In some examples, a CSI report indicating which associated CSI-RS instances occur in both SBFD symbols and non-SBFD symbols in different slots may be provided.

In some examples, the SBFD operation may involve SBFD-specific resource and configurations. For example, the SBFD operation may involve configurations for SRS, PUCCH and PUSCH on SBFD symbols and non-SBFD symbols (e.g., resources, frequency hopping parameters, uplink power control parameters, beam and/or spatial relations, or the like) .

In some examples, the SBFD operation may involve collision handling. For example, the SBFD operation may involve collision handling between downlink reception in downlink subband (s) and uplink transmission in an uplink subband in a SBFD symbol.

As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

Fig. 5 is a diagram illustrating an example 500 of uplink CG communication, in accordance with the present disclosure. CG communications may include periodic uplink communications that are configured for a UE 120, such that the network node 110 does not need to send separate DCI to schedule each uplink communication, thereby conserving signaling overhead.

As shown in example 500, a UE 120 may be configured with a CG configuration for CG communications. For example, the UE 120 may receive the CG configuration via an RRC message transmitted by a network node 110. The CG configuration may indicate a resource allocation associated with CG uplink communications (e.g., in a time domain, frequency domain, spatial domain, and/or code domain) and a periodicity at which the resource allocation is repeated, resulting in periodically reoccurring scheduled CG occasions 505 for the UE 120. In some examples, the CG configuration may identify a resource pool or multiple resource pools that are available to the UE 120 for an uplink transmission. The CG configuration may configure contention-free CG communications (e.g., where resources are dedicated for the UE 120 to transmit uplink communications) or contention-based CG communications (e.g., where the UE 120 contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure) .

The network node 110 may transmit CG activation DCI to the UE 120 to activate the CG configuration for the UE 120. The network node 110 may indicate, in the CG activation DCI, communication parameters, such as an MCS, a resource block (RB) allocation, and/or antenna ports, for the CG PUSCH communications to be transmitted in the scheduled CG occasions 505. The UE 120 may begin transmitting in the CG occasions 505 based at least in part on receiving the CG activation DCI. For example, beginning with a next scheduled CG occasion 505 subsequent to receiving the CG activation DCI, the UE 120 may transmit a PUSCH communication in the scheduled CG occasions 505 using the communication parameters indicated in the CG activation DCI. The UE 120 may refrain from transmitting in configured CG occasions 505 prior to receiving the CG activation DCI.

The network node may transmit CG reactivation DCI to the UE 120 to change the communication parameters for the CG PUSCH communications. Based at least in part on receiving the CG reactivation DCI, and the UE 120 may begin transmitting in the scheduled CG occasions 505 using the communication parameters indicated in the CG reactivation DCI. For example, beginning with a next scheduled CG occasion 505 subsequent to receiving the CG reactivation DCI, the UE 120 may transmit PUSCH communications in the scheduled CG occasions 505 based at least in part on the communication parameters indicated in the CG reactivation DCI.

In some cases, such as when the network node 110 needs to override a scheduled CG communication for a higher priority communication, the network node 110 may transmit CG cancellation DCI to the UE 120 to temporarily cancel or deactivate one or more subsequent CG occasions 505 for the UE 120. The CG cancellation DCI may deactivate only a subsequent one CG occasion 505 or a subsequent N CG occasions 505 (where N is an integer) . CG occasions 505 after the one or more (e.g., N) CG occasions 505 subsequent to the CG cancellation DCI may remain activated. Based at least in part on receiving the CG cancellation DCI, the UE 120 may refrain from transmitting in the one or more (e.g., N) CG occasions 505 subsequent to receiving the CG cancellation DCI. As shown in example 500, the CG cancellation DCI cancels one subsequent CG occasion 505 for the UE 120. After the CG occasion 505 (or N CG occasions) subsequent to receiving the CG cancellation DCI, the UE 120 may automatically resume transmission in the scheduled CG occasions 505.

The network node 110 may transmit CG release DCI to the UE 120 to deactivate the CG configuration for the UE 120. The UE 120 may stop transmitting in the scheduled CG occasions 505 based at least in part on receiving the CG release DCI. For example, the UE 120 may refrain from transmitting in any scheduled CG occasions 505 until another CG activation DCI is received from the network node 110. Whereas the CG cancellation DCI may deactivate only a subsequent one CG occasion 505 or a subsequent N CG occasions 505, the CG release DCI deactivates all subsequent CG occasions 505 for a given CG configuration for the UE 120 until the given CG configuration is activated again by a new CG activation DCI.

As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

Fig. 6 is a diagram illustrating an example 600 of CG-based SDT, in accordance with the present disclosure. As shown in Fig. 6, a network node 110 and a UE 120 may communicate with one another.

As shown by reference number 610, the network node 110 may transmit, and the UE 120 may receive, a CG resource configuration. The CG resource configuration may be a CG-SDT configuration of one or more CG-SDT resources (e.g., CG resources for UE SDT) . The CG resource configuration may be contained in an RRC release (RRCRelease) message with a suspend configured parameter (e.g., SuspendConfig) . In some examples, the RRCRelease message may also reconfigure or release CG-SDT resources that are to be used while the UE 120 is in an RRC inactive state. In some examples, the CG-SDT resources may be valid only within the cell from which the UE 120 received the RRCRelease message. In some examples, the network node 110 may transmit one or more CG-SDT resource configurations to the UE 120 in the RRC inactive state.

In some examples, the SuspendConfig may define a CG configuration for SBFD-aware UEs 120. The CG configuration may enable the SBFD-aware UEs 120 to transmit CG PUSCH communications in uplink subband symbols. Thus, the CG resource configuration may configure the one or more CG-SDT resources for uplink subband symbols. The one or more CG-SDT resources may be selected in the uplink subband symbols in accordance with one or more conditions. In some examples, an SBFD-aware UE 120 may fall back to non-SBFD CG-SDT based at least in part on a timer.

As shown by reference number 620, the UE 120 may transition to the RRC inactive state. As shown by reference number 630, the UE 120 may transmit, and the network node 110 may receive, a first uplink message. For example, the first uplink message may be a CG transmission that includes an RRC resume request (RRCResumeReq) and SDT uplink data. As shown by reference number 640, the network node 110 may transmit, and the UE 120 may receive, a response to the first uplink message. For example, the response may include a dynamic grant (DG) for a different transmission or a retransmission.

As shown by reference number 650, the network node 110 and the UE 120 may exchange subsequent data transmissions. For example, as shown by reference number 660, the UE 120 may transmit, and the network node 110 may receive, uplink data. As shown by reference number 670, the network node 110 may transmit, and the UE 120 may receive, a downlink response to the uplink data. As shown by reference number 680, the UE 120 may transmit, and the network node 110 may receive, further uplink data. As shown by reference number 690, the network node 110 may transmit, and the UE 120 may receive, an RRCRelease message with SuspendConfig.

As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

Fig. 7 is a diagram illustrating an example 700 of SBFD-specific CG-SDT, in accordance with the present disclosure.

From the perspective of the RRC layer, when certain conditions are fulfilled, a UE 120 in the RRC inactive state may initiate a resume procedure for SDT. The resume procedure may enable the UE 120 to transmit SDT communications in CG-SDT resources while the UE 120 remains in the RRC inactive state. The conditions may include: one or more upper layers requesting resumption of the RRC connection; the SDT resources (e.g., the CG-SDT resources) being configured; all pending uplink data being mapped to one or more radio bearers configured for SDT; and one or more lower layers (e.g., a MAC layer of the UE 120) checking certain criteria (e.g., in response to the one or more upper layers initiating the criteria checking for an SDT procedure) .

Example 700 relates to the criteria that are checked by the one or more lower layers. As shown by reference number 710, the one or more lower layers may determine that the data volume of the pending uplink data across all logical channels configured for SDT satisfies (e.g., is less than or equal to) a first configured threshold (e.g., a data volume threshold) and/or that a downlink RSRP satisfies (e.g., exceeds) a second configured threshold (e.g., an SDT RSRP threshold indicated in SIB1) .

As shown by reference number 720, the one or more lower layers may determine whether to use normal uplink (NUL) or supplementary uplink (SUL) for SDT. For example, the one or more lower layers may determine whether to use NUL or SUL for SDT using an RSRP-based condition.

As shown by reference number 730, the one or more lower layers may determine whether a valid SDT resource (e.g., a CG resource or a random access resource) is available and perform SDT type selection (e.g., between CG-SDT and random access SDT (RA-SDT) ) . For example, as shown by reference number 740, the one or more lower layers may determine whether a CG resource (e.g., a CG occasion) is configured with a valid timing advance (TA) . The CG resource may be a NUL CG resource or a SUL CG resource, depending on whether the one or more lower layers determined to use NUL or SUL in connected with reference number 720.

If a CG resource is configured with a valid TA, then the one or more lower layers may select CG-SDT and, as shown by reference number 750, choose SBFD CG (e.g., choose a CG resource in one or more SBFD symbols) or TDD CG (e.g., a CG resource in one or more uplink or downlink symbols) . As shown by reference number 760, the one or more lower layers may choose one or more candidate SSBs based at least in part on a third configured threshold. In some examples, the third configured threshold may depend on whether the one or more lower layers chose SBFD CG or TDD CG.

If no CG resource is configured with a valid TA (e.g., if the CG resources are invalid) , then, as shown by reference number 770, the one or more lower layers may determine whether to perform a two-step random access procedure or a four-step random access procedure. For example, the one or more lower layers may determine whether an RSRP satisfies (e.g., exceeds) a fourth configured threshold. If the RSRP satisfies the fourth configured threshold, then, as shown by reference number 780, the one or more lower layers may perform a two-step random access. If the RSRP does not satisfy the fourth configured threshold, then, as shown by reference number 790, the one or more lower layers may perform a four-step random access. The two-step or four-step random access may be a NUL two-step or four-step random access or a SUL two-step or four-step random access, depending on whether the one or more lower layers determined to use NUL or SUL in connected with reference number 720.

As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.

Because SBFD involves full duplex operation at the network-side, SBFD may have a tighter link budget and/or require stronger radio propagation conditions than TDD. As a result, SBFD CG-SDT may be operable for only certain beams (e.g., beams that comply with the tighter link budget and/or stronger radio propagation conditions) . Therefore, SBFD CG-SDT communications carried via other beams may not be successfully decoded by a receiver.

Fig. 8 is a diagram illustrating an example 800 associated with signaling for SSB-to-CG mapping for SBFD CGs, in accordance with the present disclosure. As shown in Fig. 8, a network node 110 and a UE 120 may communicate with one another. In some examples, the UE 120 may be an SBFD-aware UE.

As shown by reference number 810, the network node 110 may transmit, and the UE 120 may receive, a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The mapping of SSBs to CG occasions may correlate SSBs to respective CG occasions. In some examples, the mapping may be indicated by an sdt-SSB-Subset-SBFD parameter. The CG occasions (e.g., CG PUSCH occasions) may be indicated by a CG configuration that is transmitted or received before the CG-SDT configuration is transmitted or received. The CG configuration may configure SBFD-aware UEs (e.g., the UE 120) and non-SBFD-aware (e.g., legacy) UEs; CG occasions that are computed by the legacy UEs may be referred to as “TDD CG occasions, ” and additional CG occasions that are computed by the SBFD-aware UEs (e.g., the UE 120) may be referred to as “SBFD CG occasions. ” TDD CG occasions may be located in uplink symbols, and SBFD CG occasions may be located in an uplink subband of SBFD symbols.

In some aspects, the CG-SDT configuration may further indicate one or more of a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols, one or more DMRS ports associated with the CG occasions in the one or more SBFD symbols, or quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols. The quantity of the SSBs may be associated with each of the CG occasions in the one or more SBFD symbols in that the quantity of the SSBs may be configured (e.g., using an SDT-SSB-Per-CG-PUSCH parameter) for each of the CG occasions in the one or more SBFD symbols. The one or more DMRS ports may be associated with the CG occasions in the one or more SBFD symbols in that the one or more DMRS ports may be configured (e.g., using an sdt-DMRSports parameter) for the CG occasions in the one or more SBFD symbols. The quantity of DMRS sequences may be associated with the CG occasions in the one or more SBFD symbols in that the quantity of DMRS sequences may be configured (e.g., using an sdt-NrofDMRS-Sequences parameter) for the CG occasions in the one or more SBFD symbols.

In some aspects, the mapping may be associated with a first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with a second mapping of SSBs to one or more of the CG occasions in one or more TDD symbols. For example, the first mapping may correlate SSBs with TDD CG occasions (e.g., CG PUSCH occasions derived from TDD CG occasions) and associated DMRS resources, and the second mapping may correlate SSBs with SBFD CG occasions (e.g., CG PUSCH occasions derived from SBFD CG occasions) and associated DMRS resources. The mapping may be associated with the first mapping and the second mapping in that the UE 120 may derive and/or maintain (e.g., store) the first mapping and the second mapping based at least in part on the mapping. The CG occasions in the one or more TDD symbols may be CG occasions in uplink symbols in a TDD pattern.

In some aspects, the mapping may be associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices. The SSB indices may be associated with the SSBs in that the SSB indices may correspond to respective SSBs. The mapping may be associated with the increasing order of the SSB indices in that the mapping may map the SSBs to the CG occasions in increasing order of the SSB indices over time. For example, a mapping rule of the SSBs to the CG occasions may be used with an increasing order of SSB indices (e.g., SSB0, SSB1, SSB2 …SSBN, where N is the total quantity of SSB indices) . The mapping may be associated with the decreasing order of the SSB indices in that the mapping may map the SSBs to the CG occasions in decreasing order of the SSB indices over time. For example, the mapping rule of the SSBs to the CG occasions may be used with a decreasing (e.g., reverse) order of SSB indices (e.g., SSBN, SSBN-1, …SSB2, SSB1) .

In some examples, SS/PBCH block indexes (e.g., SSB indices) may be mapped to valid PUSCH occasions and associated DMRS resources in the following order. First, the SSB indices may be mapped in increasing order of DMRS resource indexes within a PUSCH occasion (where a DMRS resource index DMRS_id is determined first in ascending order of a DMRS port index and second in an ascending order of a DMRS sequence index) . Second, the SSB indices may be mapped in increasing or decreasing order of PUSCH configuration period indexes.

In some aspects, the mapping may be associated with a configured starting SSB index. The mapping may be associated with the configured starting SSB index in that the mapping may map an SSB with the configured starting SSB index to the first CG occasion (in time) of the CG occasions. For example, the network may use the CG-SDT configuration to indicate that the mapping begins with an SSB index i at a subframe 0 (where subframe 0 may correspond to the first CG occasion) . Thus, the network may indicate the SSB index at which the mapping begins (e.g., rather than the UE 120 starting from the lowest SSB index) .

As shown by reference number 820, the UE 120 may transmit, and the network node 110 may receive, in accordance with the mapping, an SDT communication in at least one of the CG occasions. For example, the network node 110 may transmit, and the UE 120 may receive, the SSBs on respective beams, and the UE 120 may select a particular beam and indicate the selected beam to the network node 110 by transmitting the SDT communication in the at least one of the CG occasions corresponding to the selected beam.

As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.

Fig. 9 is a diagram illustrating an example 900 associated with a CG-SDT configuration, in accordance with the present disclosure.

As shown, the CG-SDT configuration may include an sdt-SSB-Subset parameter, which may indicate a mapping of SSBs to TDD CG occasions, and an sdt-SSB-Subset-SBFD parameter 910, which may indicate the mapping of SSBs to CG occasions in one or more symbols including the one or more SBFD symbols. In some examples, the UE 120 may receive, in the CG-SDT configuration, one or more of the SDT-SSB-Per-CG-PUSCH parameter for SBFD CG occasions, the sdt-DMRSports parameter for SBFD CG occasions, the sdt-NrofDMRS-Sequences for SBFD CG occasions, or the like.

As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with respect to Fig. 9.

Fig. 10 is a diagram illustrating examples 1000 and 1010 associated with indication of SBFD-CG occasions, in accordance with the present disclosure.

In some aspects, the network node 110 may transmit, and the UE 120 may receive, a CG configuration, associated with SBFD-aware UEs (e.g., the UE 120) and non-SBFD-aware UEs, that indicates the CG occasions. A non-SBFD-aware UE may be a UE that is not capable of transmitting communications in an uplink subband of an SBFD slot or a UE that behaves as such (e.g., due to a configuration, a UE implementation, or the like) . The CG configuration may be associated with SBFD-aware UEs and non-SBFD-aware UEs in that the CG configuration (e.g., the same CG configuration) may configure both the SBFD-aware UEs and the non-SBFD-aware UEs. Thus, TDD CG occasions and SBFD CG occasions may be configured under one CG configuration.

For instance, example 1000 includes a set of slots that are downlink ( “D” ) , uplink ( “U” ) , flexible ( “F” ) , or SBFD. The SBFD slots contain a downlink subband and an uplink subband. The CG configuration may configure (e.g., with a two-slot periodicity) a set of CG occasions 1020 at a non-SBFD-aware UE and a set of CG occasions 1030 at the UE 120 (e.g., an SBFD-aware UE) . The CG occasions in the sets of CG occasions 1020 and 1030 may be identified based at least in part on a rule for validation of the CG occasions in the uplink subbands of SBFD symbols (e.g., SBFD slots) . For example, the CG occasions that fall in uplink slots may be valid for both the non-SBFD-aware UE and the UE 120, and SBFD-dedicated CG occasions 1040 (e.g., the CG occasions that fall in SBFD slots) may be valid for the UE 120 and not for the non-SBFD-aware UE.

In some aspects (e.g., involving the CG configuration associated with SBFD-aware UEs and non-SBFD-aware UEs) , one or more of the CG occasions may be SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols. For example, an indication of the TDD CG occasions and SBFD CG occasions configured under one CG configuration may be implicit: a CG occasion may be identified as a TDD CG occasion or an SBFD CG occasion based at least in part on a location of the CG occasion in an uplink symbol or an uplink subband of an SBFD symbol.

In some aspects (e.g., involving the CG configuration associated with SBFD-aware UEs and non-SBFD-aware UEs) , one or more of the CG occasions may be SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern. For example, an indication of the TDD CG occasions and SBFD CG occasions configured under one CG configuration may be explicit (e.g., the network node 110 may explicitly indicate the TDD CG occasions and/or the SBFD CG occasions to the UE 120) . For example, the UE 120 may receive an indication of first timing pattern for the SBFD CG occasions and a second timing pattern for the TDD CG occasions. An indication of a timing pattern may include an indication of one or more of a periodicity, an offset, or the like.

In some aspects, the network node 110 may transmit, and the UE 120 may receive, an SBFD-dedicated CG configuration that indicates the CG occasions. For example, the SBFD-dedicated CG configuration may configure SBFD-aware UEs (e.g., and not non-SBFD-aware UEs) . In some examples, the network node 110 may transmit, and a non-SBFD-aware UE may receive, a non-SBFD CG configuration.

For instance, example 1010 includes the same set of slots as example 1000. The SBFD-dedicated CG configuration 1050 configures the UE 120 with CG occasions with a periodicity of two slots, and the non-SBFD CG configuration 1060 configures a non-SBFD-aware UE with CG occasions with a periodicity of ten slots. The validity of the CG occasions configured by the SBFD-dedicated CG configuration 1050 is based at least in part on the SBFD-dedicated CG configuration 1050. For example, the CG occasions configured by the SBFD-dedicated CG configuration 1050 that fall in SBFD slots may be valid, and the CG occasions configured by the SBFD-dedicated CG configuration 1050 that fall in uplink slots may not be valid.

As indicated above, Fig. 10 is provided as an example. Other examples may differ from what is described with respect to Fig. 10.

Fig. 11 is a diagram illustrating examples 1100 and 1105 associated with UE handling of association periods and association period patterns, in accordance with the present disclosure.

In some aspects, the mapping may be associated with one or more of a TDD association period or a TDD association period pattern. A TDD association period or a TDD association period pattern is an association period or an association period pattern that is used for TDD CG occasions. The mapping may be associated with one or more of the TDD association period or the TDD association period pattern in that the TDD association period and/or the TDD association period pattern may be used for the CG occasions in the mapping (e.g., SBFD CG occasions) .

For instance, example 1100 includes a set of slots that are downlink, uplink, flexible, or SBFD. Example 1100 further includes a set of CG occasions 1110 at a non-SBFD-aware UE and a set of CG occasions 1115 at the UE 120 (e.g., an SBFD-aware UE) . In example 1100, the CG occasions that fall in uplink slots are valid for the non-SBFD-aware UE and not for the UE 120, and SBFD-dedicated CG occasions 1120 (e.g., the CG occasions that fall in SBFD slots) may be valid for the UE 120 and not for the non-SBFD-aware UE. As shown, the same association period 1125 is applied to both the set of CG occasions 1110 and the set of CG occasions 1115.

One association period may include an integer multiple of SSB mapping cycles. An SSB mapping cycle is a set of CG occasions having all SSB indexes mapped thereto. Furthermore, an association period may have a different (e.g., greater) quantity of SSB mapping cycles for SBFD CG occasions than for TDD CG occasions. For example, the association period 1125 has one SSB mapping cycle for TDD CG occasions and three SSB mapping cycles for SBFD CG occasions.

In some examples, for a set of CG occasions that are not mapped to an SSB within an association period, no SS/PBCH block indexes (e.g., SSB indexes) can be mapped to that set of CG occasions. Furthermore, CG occasions (e.g., SBFD CG occasions) that are not associated with an SSB after an integer multiple of association periods may not be used for a CG (e.g., PUSCH) transmission. For example, as shown in example 1100, the CG occasion 1130 is not mapped to an SSB index because the association period 1125 would otherwise contain a fractional SSB mapping cycle (e.g., the SSB mapping cycle would end with index SSB0 instead of index SSB2) . As a result, the UE 120 may not transmit a CG-SDT communication in the CG occasion 1130.

In some aspects, the mapping may be associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern. The mapping may be associated with one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern in that the SBFD-dedicated association period and/or the SBFD-dedicated association period pattern may be based at least in part on (e.g., used for) the CG occasions in the mapping (e.g., SBFD CG occasions) . In some examples, the SBFD-dedicated association period and the SBFD-dedicated association period pattern may be separate (e.g., different) than the TDD association period and/or TDD association period pattern, which may be used for TDD CG occasions. In some examples, the mapping may be associated with one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern in cases involving the SBFD-dedicated CG configuration (e.g., the SBFD-dedicated CG configuration may indicate one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern) .

For instance, example 1105 includes a set of slots that are downlink, uplink, flexible, or SBFD. Example 1105 further includes a set of CG occasions 1135 at a non-SBFD-aware UE and a set of CG occasions 1140 at the UE 120 (e.g., an SBFD-aware UE) . In example 1105, the CG occasions that fall in uplink slots are valid for the non-SBFD-aware UE and not for the UE 120, and SBFD-dedicated CG occasions 1145 (e.g., the CG occasions that fall in SBFD slots) may be valid for the UE 120 and not for the non-SBFD-aware UE. A TDD association period may be applied to the set of CG occasions 1135, and an SBFD-dedicated association period pattern 1150 including SBFD-dedicated association periods 1155, 1160, and 1165 may be applied to the set of CG occasions 1140. The lengths of SBFD-dedicated association periods 1155, 1160, and 1165 are, respectively, 5N_cg, 3T_cg, and 6T_cg, where T_cg= 2 slots.

In some aspects, the mapping may be associated with one or more of a TDD association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern. For example, the UE 120 may switch between the TDD association period and/or the TDD association period pattern, and the SBFD-dedicated association period and/or the SBFD-dedicated association period. For example, the UE 120 may drop the SBFD-dedicated association periods 1155, 1160, and 1165 in favor of the TDD association period, and/or may drop the TDD association period in favor of the SBFD-dedicated association periods 1155, 1160, and 1165. The UE 120 may use the SBFD-dedicated association periods 1155, 1160, and 1165, or the TDD association period, for any suitable length of time.

The mapping may be associated with one or more of a TDD association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern, based at least in part on one or more triggers. In some examples, the one or more triggers may include an indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern. For example, the network node 110 may transmit, and the UE 120 may receive, the indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern. The network node 110 may transmit the indication based at least in part on certain logical channels being prohibited (e.g., restricted) or allowed for SBFD CG occasions. For example, the network node 110 may enable or disable SBFD CGs over SIB or MAC-CE. For example, during an ongoing CG-SDT session, the network node 110 may enable or disable CGs for the ongoing CG session using MAC-CE.

In some examples, the one or more triggers may include a synchronized signal reference signal received power (SS-RSRP) . For example, the SS-RSRP not satisfying (e.g., being less than) an SS-RSRP threshold may prompt the UE 120 to associate the mapping with the one or more of the TDD association period or the TDD association period pattern. The SS-RSRP satisfying (e.g., being greater than) an SS-RSRP threshold may prompt the UE 120 to associate the mapping with the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern.

In some examples, the one or more triggers may include a quantity of retransmissions or an expiry of a CG-SDT communication timer. The CG-SDT communication timer may start after the first PUSCH transmission in a CG occasion for SDT. For example, N retransmissions and/or expiry of the CG-SDT communication timer may prompt the UE 120 to associate the mapping with the one or more of the TDD association period or the TDD association period pattern.

As indicated above, Fig. 11 is provided as an example. Other examples may differ from what is described with respect to Fig. 11.

The mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols may help to ensure that one or more CG-SDT communications (e.g., the SDT communication) can be decoded successfully. For example, the network node 110 and/or the UE 120 may communicate, based at least in part on the mapping, using one or more beams that enable the CG-SDT communications comply with tight link budgets and/or strong radio propagation conditions that are commonly present in SBFD scenarios.

The mapping being associated with the first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with the second mapping of SSBs to one or more of the CG occasions in the one or more TDD symbols, may help to ensure that SBFD-aware UEs (e.g., the UE 120) behave like non-SBFD-aware UEs at TDD CG occasions (e.g., by using the first mapping at TDD CG occasions) , thereby avoiding ambiguity between the mapping for the SBFD-aware UEs and a mapping for the non-SBFD-aware UEs.

The mapping being associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices, may enable the UE 120 to select a beam with fewer resources than the UE 120 would otherwise use to select a beam.

The mapping being associated with the configured starting SSB index may help the UE 120 to map the same SSB to a CG occasion as an SSB mapped to the CG occasion by a non-SBFD-aware UE. As a result, the UE 120 may avoid skipping the CG occasion (e.g., by identifying a CG occasion closest in time to the SSB) and thereby reduce latency.

The mapping being associated with one or more of the TDD association period or the TDD association period pattern may help to reduce complexity at the UE 120. The mapping being associated with one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern may help to ensure that the last CG occasion (s) in the SBFD-dedicated association period and/or the SBFD-dedicated association period pattern are mapped to SSB (s) .

Fig. 12 is a diagram illustrating an example process 1200 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 1200 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with mapping of SSBs to CG occasions in CG-SDT for SBFD.

As shown in Fig. 12, in some aspects, process 1200 may include receiving a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols (block 1210) . For example, the UE (e.g., using communication manager 140 and/or reception component 1402, depicted in Fig. 14) may receive a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols, as described above, for example, with reference to Figs. 8, 9, 10, and/or 11.

As further shown in Fig. 12, in some aspects, process 1200 may include transmitting, in accordance with the mapping, an SDT communication in at least one of the CG occasions (block 1220) . For example, the UE (e.g., using communication manager 140 and/or transmission component 1404, depicted in Fig. 14) may transmit, in accordance with the mapping, an SDT communication in at least one of the CG occasions, as described above, for example, with reference to Figs. 8, 9, 10, and/or 11.

Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a first aspect, the CG-SDT configuration further indicates one or more of a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols, one or more DMRS ports associated with the CG occasions in the one or more SBFD symbols, or a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.

In a second aspect, alone or in combination with the first aspect, process 1200 includes receiving a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.

In a third aspect, alone or in combination with one or more of the first and second aspects, one or more of the CG occasions are SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, one or more of the CG occasions are SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 1200 includes receiving an SBFD-dedicated CG configuration that indicates the CG occasions.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the mapping is associated with a first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with a second mapping of SSBs to one or more of the CG occasions in one or more TDD symbols.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the mapping is associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the mapping is associated with a configured starting SSB index.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the mapping is associated with one or more of a TDD association period or a TDD association period pattern.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the mapping is associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the mapping is associated with one or more of a TDD association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern, based at least in part on an indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern, a SS-RSRP, or a quantity of retransmissions or an expiry of a CG-SDT communication timer.

Although Fig. 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

Fig. 13 is a diagram illustrating an example process 1300 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 1300 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with mapping of SSBs to CG occasions in CG-SDT for SBFD.

As shown in Fig. 13, in some aspects, process 1300 may include transmitting a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols (block 1310) . For example, the network node (e.g., using communication manager 150 and/or transmission component 1504, depicted in Fig. 15) may transmit a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols, as described above, for example, with reference to Figs. 8, 9, 10, and/or 11.

As further shown in Fig. 13, in some aspects, process 1300 may include receiving, in accordance with the mapping, an SDT communication in at least one of the CG occasions (block 1320) . For example, the network node (e.g., using communication manager 150 and/or reception component 1502, depicted in Fig. 15) may receive, in accordance with the mapping, an SDT communication in at least one of the CG occasions, as described above, for example, with reference to Figs. 8, 9, 10, and/or 11.

Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.

In a second aspect, alone or in combination with the first aspect, process 1300 includes transmitting a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 1300 includes transmitting an SBFD-dedicated CG configuration that indicates the CG occasions.

Although Fig. 13 shows example blocks of process 1300, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure. The apparatus 1400 may be a UE, or a UE may include the apparatus 1400. In some aspects, the apparatus 1400 includes a reception component 1402, a transmission component 1404, and/or a communication manager 1406, 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 manager 1406 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 1400 may communicate with another apparatus 1408, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1402 and the transmission component 1404.

In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 8-11. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12. In some aspects, the apparatus 1400 and/or one or more components shown in Fig. 14 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1408. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may 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 apparatus 1400. In some aspects, the reception component 1402 may 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 UE described in connection with Fig. 2.

The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1408. In some aspects, the transmission component 1404 may 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 apparatus 1408. In some aspects, the transmission component 1404 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in one or more transceivers.

The communication manager 1406 may support operations of the reception component 1402 and/or the transmission component 1404. For example, the communication manager 1406 may receive information associated with configuring reception of communications by the reception component 1402 and/or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communication manager 1406 may generate and/or provide control information to the reception component 1402 and/or the transmission component 1404 to control reception and/or transmission of communications.

The reception component 1402 may receive a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The transmission component 1404 may transmit, in accordance with the mapping, an SDT communication in at least one of the CG occasions. In some aspects, the reception component 1402 may receive a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions. In some aspects, the reception component 1402 may receive an SBFD-dedicated CG configuration that indicates the CG occasions.

The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may perform one or more functions described as being performed by another set of components shown in Fig. 14.

Fig. 15 is a diagram of an example apparatus 1500 for wireless communication, in accordance with the present disclosure. The apparatus 1500 may be a network node, or a network node may include the apparatus 1500. In some aspects, the apparatus 1500 includes a reception component 1502, a transmission component 1504, and/or a communication manager 1506, 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 manager 1506 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 1500 may communicate with another apparatus 1508, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 1502 and the transmission component 1504.

In some aspects, the apparatus 1500 may be configured to perform one or more operations described herein in connection with Figs. 8-11. Additionally, or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as process 1300 of Fig. 13. In some aspects, the apparatus 1500 and/or one or more components shown in Fig. 15 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 15 may be implemented within one or more components described in connection with Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 1502 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1508. The reception component 1502 may provide received communications to one or more other components of the apparatus 1500. In some aspects, the reception component 1502 may 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 apparatus 1500. In some aspects, the reception component 1502 may 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 node described in connection with Fig. 2. In some aspects, the reception component 1502 and/or the transmission component 1504 may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus 1500 via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The transmission component 1504 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1508. In some aspects, one or more other components of the apparatus 1500 may generate communications and may provide the generated communications to the transmission component 1504 for transmission to the apparatus 1508. In some aspects, the transmission component 1504 may 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 apparatus 1508. In some aspects, the transmission component 1504 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 1504 may be co-located with the reception component 1502 in one or more transceivers.

The communication manager 1506 may support operations of the reception component 1502 and/or the transmission component 1504. For example, the communication manager 1506 may receive information associated with configuring reception of communications by the reception component 1502 and/or transmission of communications by the transmission component 1504. Additionally, or alternatively, the communication manager 1506 may generate and/or provide control information to the reception component 1502 and/or the transmission component 1504 to control reception and/or transmission of communications.

The transmission component 1504 may transmit a CG-SDT configuration that indicates a mapping of SSBs to CG occasions in one or more symbols including one or more SBFD symbols. The reception component 1502 may receive, in accordance with the mapping, an SDT communication in at least one of the CG occasions. In some aspects, the transmission component 1504 may transmit a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions. In some aspects, the transmission component 1504 may transmit an SBFD-dedicated CG configuration that indicates the CG occasions.

The number and arrangement of components shown in Fig. 15 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 15. Furthermore, two or more components shown in Fig. 15 may be implemented within a single component, or a single component shown in Fig. 15 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 15 may perform one or more functions described as being performed by another set of components shown in Fig. 15.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: receiving a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of SSBs to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols; and transmitting, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.

Aspect 2: The method of Aspect 1, wherein the CG-SDT configuration further indicates one or more of: a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols, one or more demodulation reference signal (DMRS) ports associated with the CG occasions in the one or more SBFD symbols, or a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.

Aspect 3: The method of any of Aspects 1-2, further comprising: receiving a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.

Aspect 4: The method of Aspect 3, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols.

Aspect 5: The method of Aspect 3, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern.

Aspect 6: The method of any of Aspects 1-5, further comprising: receiving an SBFD-dedicated CG configuration that indicates the CG occasions.

Aspect 7: The method of any of Aspects 1-6, wherein the mapping is associated with a first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with a second mapping of SSBs to one or more of the CG occasions in one or more time division duplex (TDD) symbols.

Aspect 8: The method of any of Aspects 1-7, wherein the mapping is associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices.

Aspect 9: The method of any of Aspects 1-8, wherein the mapping is associated with a configured starting SSB index.

Aspect 10: The method of any of Aspects 1-9, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern.

Aspect 11: The method of any of Aspects 1-10, wherein the mapping is associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern.

Aspect 12: The method of any of Aspects 1-11, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern, based at least in part on: an indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern, a synchronized signal reference signal received power (SS-RSRP) , or a quantity of retransmissions or an expiry of a CG-SDT communication timer.

Aspect 13: A method of wireless communication performed by a network node, comprising: transmitting a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of SSBs to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols; and receiving, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.

Aspect 14: The method of Aspect 13, wherein the CG-SDT configuration further indicates one or more of: a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols, one or more demodulation reference signal (DMRS) ports associated with the CG occasions in the one or more SBFD symbols, or a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.

Aspect 15: The method of any of Aspects 13-14, further comprising: transmitting a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.

Aspect 16: The method of Aspect 15, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols.

Aspect 17: The method of Aspect 15, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern.

Aspect 18: The method of any of Aspects 13-17, further comprising: transmitting an SBFD-dedicated CG configuration that indicates the CG occasions.

Aspect 19: The method of any of Aspects 13-18, wherein the mapping is associated with a first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with a second mapping of SSBs to one or more of the CG occasions in one or more time division duplex (TDD) symbols.

Aspect 20: The method of any of Aspects 13-19, wherein the mapping is associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices.

Aspect 21: The method of any of Aspects 13-20, wherein the mapping is associated with a configured starting SSB index.

Aspect 22: The method of any of Aspects 13-21, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern.

Aspect 23: The method of any of Aspects 13-22, wherein the mapping is associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern.

Aspect 24: The method of any of Aspects 13-23, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern, based at least in part on: an indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern, a synchronized signal reference signal received power (SS-RSRP) , or a quantity of retransmissions or an expiry of a CG-SDT communication timer.

Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-24.

Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-24.

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

Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-24.

Aspect 29: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-24.

Aspect 30: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-24.

Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-24.

The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B) . Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) . It should be understood that “one or more” is equivalent to “at least one. ”

Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

Claims

An apparatus for wireless communication at a user equipment (UE) , comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, configured to cause the UE to:

receive a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of synchronization signal blocks (SSBs) to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols; and

transmit, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.
The apparatus of claim 1, wherein the CG-SDT configuration further indicates one or more of:

a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols,

one or more demodulation reference signal (DMRS) ports associated with the CG occasions in the one or more SBFD symbols, or

a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.
The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to:

receive a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.
The apparatus of claim 3, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols.
The apparatus of claim 3, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern.
The apparatus of claim 1, wherein the one or more processors are further configured to cause the UE to:

receive an SBFD-dedicated CG configuration that indicates the CG occasions.
The apparatus of claim 1, wherein the mapping is associated with a first mapping of SSBs to one or more of the CG occasions in the one or more SBFD symbols, and associated with a second mapping of SSBs to one or more of the CG occasions in one or more time division duplex (TDD) symbols.
The apparatus of claim 1, wherein the mapping is associated with an increasing order of SSB indices associated with the SSBs, or associated with a decreasing order of the SSB indices.
The apparatus of claim 1, wherein the mapping is associated with a configured starting SSB index.
The apparatus of claim 1, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern.
The apparatus of claim 1, wherein the mapping is associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern.
The apparatus of claim 1, wherein the mapping is associated with one or more of a time division duplex (TDD) association period or a TDD association period pattern, or associated with one or more of an SBFD-dedicated association period or an SBFD-dedicated association period pattern, based at least in part on:

an indication to associate the mapping with the one or more of the TDD association period or the TDD association period pattern, or the one or more of the SBFD-dedicated association period or the SBFD-dedicated association period pattern,

a synchronized signal reference signal received power (SS-RSRP) , or

a quantity of retransmissions or an expiry of a CG-SDT communication timer.
A method of wireless communication performed by a user equipment (UE) , comprising:

receiving a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of synchronization signal blocks (SSBs) to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols; and

transmitting, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.
The method of claim 13, wherein the CG-SDT configuration further indicates one or more of:

a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols,

one or more demodulation reference signal (DMRS) ports associated with the CG occasions in the one or more SBFD symbols, or

a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.
The method of claim 13, further comprising:

receiving a CG configuration, associated with SBFD-aware UEs and non-SBFD-aware UEs, that indicates the CG occasions.
The method of claim 15, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on the one or more of the CG occasions being in the one or more SBFD symbols.
The method of claim 15, wherein one or more of the CG occasions are SBFD CG occasions based at least in part on an SBFD CG occasion timing pattern.
The method of claim 13, further comprising:

receiving an SBFD-dedicated CG configuration that indicates the CG occasions.
An apparatus for wireless communication, comprising:

means for receiving a configured grant small data transfer (CG-SDT) configuration that indicates a mapping of synchronization signal blocks (SSBs) to configured grant (CG) occasions in one or more symbols including one or more subband full duplex (SBFD) symbols; and

means for transmitting, in accordance with the mapping, a small data transfer (SDT) communication in at least one of the CG occasions.
The apparatus of claim 19, wherein the CG-SDT configuration further indicates one or more of:

a quantity of the SSBs associated with each of the CG occasions in the one or more SBFD symbols,

one or more demodulation reference signal (DMRS) ports associated with the CG occasions in the one or more SBFD symbols, or

a quantity of DMRS sequences associated with the CG occasions in the one or more SBFD symbols.