Patent Description:
Wireless communication systems, as are for example described in <CIT>, are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. Examples of such multiple-access systems include code-division multiple access (CDMA) systems, time-division multiple access (TDMA) systems, frequency-division multiple access (FDMA) systems, and orthogonal frequency-division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

For example, a fifth generation (<NUM>) wireless communications technology (which can be referred to as <NUM> new radio (<NUM> NR)) is envisaged to expand and support diverse usage scenarios and applications with respect to current mobile network generations. In an aspect, <NUM> communications technology can include: enhanced mobile broadband addressing human-centric use cases for access to multimedia content, services and data; ultra-reliable-low latency communications (URLLC) with certain specifications for latency and reliability; and massive machine type communications, which can allow a very large number of connected devices and transmission of a relatively low volume of non-delay-sensitive information.

In some wireless communication technologies, devices, such as base stations, user equipment (UE), etc., can communicate in full-duplex such to receive and transmit communications in a same time period. Full-duplex communication modes may include a full-duplex base station communicating with one or more UEs, a full-duplex base station communicating with one or more full-duplex UEs, a full-duplex UE communicating with a base station (or multiple transmission/reception points (TRPs)), etc..

The described features generally relate to full-duplex (FD) wireless communications based on reference signal (RS) configuration. In an example, at least for time periods where FD wireless communications are supported or configured, RSs can be differently configured than time periods where FD wireless communications may not be supported. For example, the RSs can correspond to demodulation reference signal (DMRS), common reference signal (CRS), channel state information reference signal (CSI-RS), etc. In an example, a base station can transmit the RSs along with data (e.g., physical downlink shared channel (PDSCH)) over the frequency resources and based on a RS configuration, and a user equipment (UE) can determine a transport block size (TBS) based on the RS configuration. For example, to determine the TBS, the UE can determine a number of resource elements (REs), in the frequency resources of the channel, that are for data. In one example, the UE can determine the data REs based on determining the REs indicated for transmitting the RS based on the RS configuration. The UE can determine RS REs differently for RSs that are transmitted in periods of FD communications based on the different RS configuration.

For example, FD communications can include a base station transmitting shared channel (e.g., PDSCH), control channel (e.g., physical downlink control channel (PDCCH)), demodulation reference signal (DMRS), etc. to a user equipment (UE) while the UE is transmitting shared channel (e.g., physical uplink shared channel (PUSCH)), control channel (e.g., physical uplink control channel (PUCCH)), DMRS, etc. to the base station or another base station or other signals or corresponding channels to other devices, etc. in the same time period. In an example, a time period or time division can include one or more symbols (e.g., one or more orthogonal frequency division multiplexing (OFDM) symbols, single carrier frequency division multiplexing (SC-FDM) symbols, etc.), a slot of multiple symbols, a subframe of multiple slots, etc. For example, the devices can use frequency resources (e.g., sets of subcarriers) over the same time period to facilitate FD communications. In an example, the frequency resources over the same time period can include sets of REs (e.g., subcarriers over the time period or portion thereof, such as a symbol), sets of RBs (e.g., where each RB can include a collection of REs), etc. In an example, FD communication modes may include a FD base station communicating with one or more UEs, a FD base station communicating with one or more FD UEs, a FD UE communicating with a base station (or multiple transmission/reception points (TRPs)), etc. Devices capable of FD communications may experience self-interference caused by transmitting signals while receiving signals in the same time period.

In one example, FD communications can include in-band full duplex (IBFD) where the single node can transmit and receive on the same time and frequency resource, and the downlink and uplink can share the same IBFD time/frequency resources (e.g., full and/or partial overlap). In another example, FD communications can include sub-band FD (also referred to as "flexible duplex") where the single node can transmit and receive at the same time but on different frequency resources within the same frequency band (or over communication resources in the same CC), where the downlink resource and the uplink resources can be separated in the frequency domain (e.g., by a guard band). For example, the guard band in sub-band FD can be on the order of resource block (RB) widths (e.g., <NUM> kilohertz (KHz) for third generation partnership project (3GPP) long term evolution (LTE) and fifth generation (<NUM>) new radio (NR), <NUM> and <NUM> for NR, etc.). This can be distinguished from a guard band in frequency division duplexing (FDD) communications defined in LTE and NR, which can be <NUM> megahertz (MHz) or more, and the associated resources in FDD are defined between frequency bands, but not within the same frequency band (or resources in the same CC) as is the case in sub-band FD communications.

In some examples of FD communications, various antenna configurations can be used within a device (e.g., an access point or UE) to facilitate FD communications and mitigate self-interference. In one configuration, a transmit antenna array can be spatially separated from a receive antenna array within the device to provide improved isolation and reduce leakage (e.g., self-interference) from the transmit antenna array into the receive antenna array. For example, different antenna panels can be used at a base station (e.g., to provide ><NUM> decibel (dB) isolation) where a first panel can be configured for downlink transmission at both edges of a frequency band, and a second panel can be configured for uplink reception in the middle of the frequency band. In another example, in sub-band FD (e.g., to provide ><NUM> dB isolation), downlink (DL) and uplink (UL) are in different portion of the band with guard band in between. Receiver weighted overlap add (Rx-WOLA) can be used to reduce the adjacent channel leakage ratio (ACLR) leakage to UL signal. Analog low pass filter (LPF) can be used to improve analog to digital conversion (ADC) dynamic range. In addition, for example, receiver automatic gain control (Rx-AGC) states can be improved to improve the noise floor (NF). In another example, digital interference cancellation (IC) of the ACLR leakage can be used (e.g., to provide ><NUM> dB isolation). Non-linear model can be used per each Tx-Rx pair, in one example.

At least in sub-band FD communications, time periods configured for sub-band FD communications can have different RS formats than time periods not configured for FD communications. For example, for a time period configured for transmitting a RS while communications are also being received, the RS configuration can be different than other RS configurations in at least one of uniformity or density of REs indicated for transmitting the RS throughout a set of frequency resources defined for the channel. In one example, the different RS configuration can indicate REs for transmitting the RS such that frequency resources that are closer in frequency to frequency resources for receiving communications can have more REs dedicated to transmitting the RS (e.g., a more dense allocation of REs for transmitting the RS) or may have a non-uniform allocation of REs to improve likelihood that the RS is received by one or more devices in such time periods (e.g., despite the one or more devices transmitting communications during the time periods). Aspects described herein relate to determining TBS during such time periods to account for possible different configurations of REs for transmitting the RS. In particular, at least for time periods having FD communications, the number of REs per physical RB (PRB) can be determined based on the different RS configuration and then used to determine the TBS. This can facilitate proper TBS computation depending on whether a time period is used for FD communications or not.

As used in this application, the terms "component," "module," "system" and the like are intended to include a computer-related entity, such as but not limited to hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.

Techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other systems. The terms "system" and "network" may often be used interchangeably. IS-<NUM> Releases <NUM> and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-<NUM> (TIA-<NUM>) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. The description below, however, describes an LTE/LTE-A system for purposes of example, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE/LTE-A applications (e.g., to fifth generation (<NUM>) new radio (NR) networks or other next generation communication systems).

The wireless communications system (also referred to as a wireless wide area network (WWAN)) can include base stations <NUM>, UEs <NUM>, an Evolved Packet Core (EPC) <NUM>, and/or a <NUM> Core (5GC) <NUM>. The macro cells can include base stations. The small cells can include femtocells, picocells, and microcells. In an example, the base stations <NUM> may also include gNBs <NUM>, as described further herein. In one example, some nodes of the wireless communication system may have a modem <NUM> and communicating component <NUM> for determining REs configured for a RS and/or computing an associated TBS, in accordance with aspects described herein. In addition, some nodes may have a modem <NUM> and configuring component <NUM> for configuring a device for determining REs configured for a RS, in accordance with aspects described herein. Though a UE <NUM> is shown as having the modem <NUM> and communicating component <NUM> and a base station <NUM>/gNB <NUM> is shown as having the modem <NUM> and configuring component <NUM>, this is one illustrative example, and substantially any node or type of node may include a modem <NUM> and communicating component <NUM> and/or a modem <NUM> and configuring component <NUM> for providing corresponding functionalities described herein.

The base stations <NUM> configured for <NUM> LTE (which can collectively be referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., using an S1 interface). The base stations <NUM> configured for <NUM> NR (which can collectively be referred to as Next Generation RAN (NG-RAN)) may interface with 5GC <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or 5GC <NUM>) with each other over backhaul links <NUM> (e.g., using an X2 interface).

The base stations <NUM> may wirelessly communicate with one or more UEs <NUM>. A network that includes both small cell and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group, which can be referred to as a closed subscriber group (CSG). The base stations <NUM> / UEs <NUM> may use spectrum up to Y MHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (e.g., for x component carriers) used for transmission in the DL and/or the UL direction. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

In another example, certain UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>.

A base station <NUM>, whether a small cell <NUM>' or a large cell (e.g., macro base station), may include an eNB, gNodeB (gNB), or other type of base station. A base station <NUM> referred to herein can include a gNB <NUM>.

The 5GC <NUM> may include a Access and Mobility Management Function (AMF) <NUM>, other AMFs <NUM>, a Session Management Function (SMF) <NUM>, and a User Plane Function (UPF) <NUM>. The AMF <NUM> can be a control node that processes the signaling between the UEs <NUM> and the 5GC <NUM>. Generally, the AMF <NUM> can provide QoS flow and session management. User Internet protocol (IP) packets (e.g., from one or more UEs <NUM>) can be transferred through the UPF <NUM>. The UPF <NUM> can provide UE IP address allocation for one or more UEs, as well as other functions.

The base station <NUM> provides an access point to the EPC <NUM> or 5GC <NUM> for a UE <NUM>. IoT UEs may include machine type communication (MTC)/enhanced MTC (eMTC, also referred to as category (CAT)-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, as well as other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (enhanced further eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. The UE <NUM> may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

In an example, communicating component <NUM> can determine a different RS configuration for receiving downlink RSs from a base station <NUM> at least for time periods configured for FD communications. The different RS configuration can be different at least in uniformity or density of REs used for transmitting, by the base station <NUM>, the RS than that used in time periods not configured for FD communications. In one example, the different RS configuration can be different at least in a set of RBs that are closer in frequency to the frequency resources configured for uplink communications to improve signal quality of the downlink RS in such time periods (and thus improve demodulation results where the RS is a DMRS, etc.). In any case, communicating component <NUM> can receive signals over the frequency resources and can process the signals based on the RS configuration. In one example, communicating component <NUM> can determine a number of RS REs of the frequency resources that are defined for transmitting the RS, and can determine the TBS based at least on the REs that are not defined for transmitting the RS. Where the frequency resources include two or more sets of frequency resources having different RS configuration, communicating component <NUM> can separately compute the data REs that do not include the RS REs for each set, and then determine the TBS based on the various computed data REs.

Turning now to <FIG>, aspects are depicted with reference to one or more components and one or more methods that may perform the actions or operations described herein, where aspects in dashed line may be optional. Although the operations described below in <FIG> are presented in a particular order and/or as being performed by an example component, it should be understood that the ordering of the actions and the components performing the actions may be varied, depending on the implementation. Moreover, it should be understood that the following actions, functions, and/or described components may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or by any other combination of a hardware component and/or a software component capable of performing the described actions or functions.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or communicating component <NUM> for determining REs configured for a RS and/or computing an associated TBS, in accordance with aspects described herein.

In an aspect, the one or more processors <NUM> can include a modem <NUM> and/or can be part of the modem <NUM> that uses one or more modem processors. Thus, the various functions related to communicating component <NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with communicating component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or communicating component <NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining communicating component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor <NUM> to execute communicating component <NUM> and/or one or more of its subcomponents.

Receiver <NUM> may include hardware, and/or software code executable by a processor for receiving data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium). Additionally, receiver <NUM> may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter <NUM> may include hardware, and/or software code executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., computer-readable medium).

In an aspect, communicating component <NUM> can optionally include a RS resource determining component <NUM> for determining a RS configuration for a set of frequency resources, and/or a TBS computing component <NUM> for computing a TBS based on determining a number of REs based on the RS configuration, in accordance with aspects described herein.

Referring to <FIG>, one example of an implementation of base station <NUM> (e.g., a base station <NUM> and/or gNB <NUM>, as described above) may include a variety of components, some of which have already been described above, but including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and configuring component <NUM> for configuring a device for determining REs configured for a RS, in accordance with aspects described herein.

In an aspect, configuring component <NUM> can optionally include a configuration generating component <NUM> for generating a RS configuration based on which to transmit RSs, in accordance with aspects described herein.

<FIG> illustrates a flow chart of an example of a method <NUM> for determining a TBS for downlink communications received in a time period configured for FD communications based on an associated RS configuration, in accordance with aspects described herein. In an example, a UE <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG> and <FIG>.

In method <NUM>, optionally at Block <NUM>, downlink communications can be received from a base station. In an aspect, communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can receive downlink communications from the base station. For example, communicating component <NUM> can receive downlink communications in scheduled resources, which may include portions of frequency over periods of time. As described, the portions of frequency can include subcarriers and the periods of time can include symbols (e.g., OFDM or SC-FDM symbols), slots of multiple symbols, subframes or other collections of multiple slots, etc. Frequency and time resources can include RBs (e.g., where a RB can include multiple subcarriers (e.g., <NUM> consecutive subcarriers) over a symbol), Res (e.g., where a RB can include multiple Res), etc. The downlink communications from the base station can include control channel (e.g., physical downlink control channel (PDCCH)) or data channel (e.g., physical downlink shared channel (PDSCH)) communications, RSs (e.g., DMRS to facilitate demodulating PDCCH or PDSCH, CRS, downlink channel state information reference signal (CSI-RS)), etc..

In an example, communicating component <NUM> can receive, over downlink resources allocated in one or more symbols used for full-duplex communications, a first set of resource blocks having a first reference signal configuration that is different in at least one of uniformity or density, in frequency, of resource elements indicated for receiving a reference signal than a second reference signal configuration. In addition, for example, communicating component <NUM> can receive, over the downlink resources allocated in the one or more symbols, a second set of resource blocks having the second reference signal configuration that is different from the first reference signal configuration.

An example is shown in <FIG>, which illustrates a resource allocation for FD communications having a downlink (DL) bandwidth part (BWP) over symbols <NUM>-<NUM>. In symbol <NUM>, PDCCH is scheduled, which can include scheduling information for the remaining symbols. Symbols <NUM>-<NUM> can include PDSCH resources scheduled in the DL BWP along with DMRS. In addition, resource allocation <NUM> includes an uplink (UL) BWP within which uplink data channel (e.g., physical uplink shared channel (PUSCH)) resources are scheduled along with DMRS, in symbols <NUM>-<NUM>. The DL BWP and UL BWP are shown as separated by a guard band in frequency. Communicating component <NUM> can receive downlink communications according to this or other configured resource allocations.

In method <NUM>, at Block <NUM>, a first set of RBs having a first RS configuration can be determined for downlink resources allocated in one or more symbols used for FD communications. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine, for the downlink resources allocated in the one or more symbols used for FD communications, the first set of RBs having the first RS configuration. For example, RS resource determining component <NUM> can determine the first RS configuration for symbols used for FD communications (e.g., symbol <NUM> in resource allocation <NUM> in <FIG>) to be different from a second RS configuration. For example, the second RS configuration can be a legacy RS configuration and/or a RS configuration used for symbols not configured for FD communications (e.g., symbols <NUM> and <NUM> in resource allocation <NUM> in <FIG>).

For example, the first RS configuration can be different from the second RS configuration in at least one of uniformity or density of REs indicated for transmitting the RS within the frequency resources. In one example, the first RS configuration can have a greater density of REs than the second RS configuration at least in a first portion of the frequency resources that are closer, in frequency, to the frequency resources scheduled for uplink communications in the symbol. An example is shown in <FIG>, which illustrates symbol <NUM> used for DMRS transmission where the symbol can include a first set of frequency resources <NUM> having a more dense distribution of REs <NUM> used for DMRS than REs <NUM> in a second set of frequency resources <NUM>. In addition, for example, at least the REs <NUM> can have a non-uniform distribution in frequency. For example, more dense distribution of REs used for DMRS can refer to having a larger ratio of number of REs used for DMRS to number of REs in the set of frequency resources. In another example, similar configurations of REs may also apply for downlink CSI-RS (e.g., a first RS configuration with a greater density of REs than a second RS configuration for CSI-RS). In one example, a second RS configuration (e.g., an RS configuration for an RS that is not in a time period having frequency resources scheduled for uplink communications, such as the RS in symbols <NUM> and <NUM>) may have at least one of a substantially uniform or less dense distribution of REs within the frequency resources. In one example, the second set of REs <NUM> in the first RS configuration may be defined according to, or similarly as, the second RS configuration (e.g. a legacy RS configuration), such that the first set of REs <NUM> in this specific example are modified based on proximity, in frequency, to the UL BWP.

In method <NUM>, at Block <NUM>, a first number of REs in the first set of RBs can be calculated based on the first RS configuration. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can calculate, based on the first RS configuration, the first number of REs (e.g., REs used for data) in the first set of RBs. For example, in calculating the first number of REs at Block <NUM>, optionally at Block <NUM>, a first set of frequency locations of RS REs in the first set of RBs indicated by the first RS configuration can be determined. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the first set of frequency locations of RS REs in the first set of RBs indicated by the first RS configuration. In another example, in calculating the first number of REs at Block <NUM>, optionally at Block <NUM>, a first offset metric associated with the first set of RBs can be determined. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the first offset metric associated with the first set of RBs. For example, the offset metric can be configured by higher layer signaling (e.g., radio resource control (RRC) signaling) from the base station, and can also be used in calculating the first number of REs.

For example, for a uniform distribution of REs assigned for transmitting RS (also referred to herein as RS REs), some radio access technologies (RATs), such as <NUM> NR, define that the number of REs (N'RE) allocated for PDSCH within a PRB is computed based on the following: <MAT> where <MAT> = <NUM> is the number of subcarriers in a PRB, <MAT> is the number of scheduled OFDM symbols in a slot, <MAT> is the number of REs for DMRS per PRB in the scheduled duration including overhead of DMRS code division multiplexing (CDM) groups indicated by downlink control information (DCI) format 1_0/1_1, and <MAT> is overhead configured by a higher layer parameter (e.g., RRC parameter Xoh-PDSCH, configured as <NUM>, <NUM>, <NUM>, or <NUM>), or zero if not configured. In one example, where the RS REs indicated in the first RS configuration for transmitting the RS are uniform (e.g., where the first RS configuration indicates a period or other regular interval for determining the REs, etc.), RS resource determining component <NUM> can determine the number of REs using a similar formula. For example, RS resource determining component <NUM> can determine the number of REs based on the following: <MAT> where <MAT> is the number of REs for DMRS per PRB in symbols that are configured for FD communications in the scheduled duration of including overhead of DMRS CDM groups indicated by DCI format 1_0/1_1, and <MAT> is overhead configured by a higher layer parameter (e.g., RRC parameter Xoh-PDSCH, configured as <NUM>, <NUM>, <NUM>, or <NUM>), or zero if not configured, in symbols that are configured for FD communications. The overhead metric <MAT> can account for CSI-RS and control resource set (CORESET) design for the first set of RBs. Additionally, RS resource determining component <NUM> can determine at least one of <MAT> or <MAT> in a configuration received from the base station <NUM> (e.g., in RRC signaling).

In addition, for example, in determining the first number of REs, RS resource determining component <NUM> can quantize the number of REs allocated for PDSCH within a PRB. In an example, RS resource determining component <NUM> can determine the quantized number N'RE as defined in <NUM> NR based on the Table below.

In another example, RS resource determining component <NUM> can quantize the number of REs in symbols configured for FD communications based on a different table, function, or other determination.

In another example, where the RS REs indicated in the first RS configuration for transmitting the RS are not uniform, RS resource determining component <NUM> can determine the first number of REs based on determining the number of allocated PRBs and the exact location, in frequency, of the PRBs. For example, RS resource determining component <NUM> can determine location, in frequency (also referred to herein as "frequency location") of the RS REs within the first set of RBs, which can be based on the first RS configuration that indicates frequency location of the RS REs. For example, the first RS configuration can indicate the non-uniform distribution by specifying frequency locations, different periods for different portions of RBs, etc. RS resource determining component <NUM> can determine frequency location of the RS REs within the first set of RBs based on this information and then can determine the REs not indicated for transmitting RSs to determine the first number of REs. In another example, the first RS configuration, or another configuration, can indicate the frequency location and/or size of PRBs or corresponding REs used for data. As described further herein, the first RS configuration or other configurations can be known by the UE <NUM> (e.g., stored in memory <NUM>) or otherwise received in signaling from the base station <NUM>.

In method <NUM>, optionally at Block <NUM>, a TBS of a downlink communication received in the downlink resources can be determined based at least in part on the first number of REs. In an aspect, TBS computing component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the TBS of the downlink communication received in the downlink resources based at least in part on the first number of REs. In <NUM> NR, for example, the total number of REs allocated for PDSCH (NRE) can be determined by NRE = N'RE · nPRB, where nPRB is the total number of allocated PRBs for the UE. In addition, based on an intermediate number of information bits (Ninfo) is obtained by Ninfo = NRE · R · Qm · v, where R and Qm are determined from the modulation and coding scheme (MCS) field for the downlink communications and v corresponds to the number of PDSCH layers. If Ninfo ≤ <NUM>, the TBS can be determined based on quantizing Ninfo as: <MAT> where <MAT>. The TBS can be determined from the below table that is not less than N'info.

If Ninfo > <NUM>, the TBS can be determined based on quantizing Ninfo as: <MAT> where <MAT> and where ties in the round function are broken towards the next largest integer. In addition, in this example, if <MAT>, the TBS can be determined as: <MAT> Otherwise, if <MAT> and N'info > <NUM>: <MAT> Otherwise, if <MAT> and N'info ≤ <NUM>: <MAT>.

In an example, TBS computing component <NUM> can determine the TBS of the downlink communication received in the downlink resources based at least in part on the first number of REs calculated by RS resource determining component <NUM>, as described above. For example, TBS computing component <NUM> can determine the TBS of the downlink communication received in the downlink resources based at least in part on the first number of REs determined for symbols over which FD communications are configured.

In one example, the frequency resources for transmitting RSs in symbols used for FD communications can be split into multiple portions, where each portion can have a RS configuration. The RS configuration for each portion can be the same or different from another portion. Referring to <FIG>, the frequency resources can be split into a first portion (set <NUM><NUM>) and a second portion (set <NUM><NUM>). In the first portion, in this specific example, REs <NUM> used for transmitting the RS can be non-uniformly distributed such that REs closer to the UL BWP can be more dense than those further from the UL BWP. In addition, for example, the REs <NUM> can be more dense than REs <NUM> of the second portion. Moreover, for example, the REs <NUM> in the second portion may be uniformly distributed and/or may be allocated according to a legacy RS configuration. In any case, for example, RS resource determining component <NUM> can determine the number of REs for each portion, and TBS computing component <NUM> can compute the TBS based on the number of REs in the first portion and the number of REs in the second portion.

In method <NUM>, optionally at Block <NUM> a downlink communication received in the downlink resources can be decoded according to the TBS. In an aspect, communicating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can decode, according to the TBS, the downlink communication received in the downlink resources. For example, communicating component <NUM> can use the transport block size to determine where the codeblock starts and where it ends such that the decoding process is successful. Any misalignment in the true transport block size may result in failure, and as such, communicating component <NUM> can match the code block size from the TBS.

In method <NUM>, optionally at Block <NUM> (e.g., where the frequency resources are split into multiple portions), a second set of RBs having a second RS configuration can be determined for downlink resources allocated in one or more symbols used for FD communications. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine, for the downlink resources allocated in the one or more symbols used for FD communications, the second set of RBs having the second RS configuration. For example, RS resource determining component <NUM> can determine the second RS configuration used for the second set of RBs in symbols used for FD communications (e.g., symbol <NUM> in resource allocation <NUM> in <FIG>) to be different from the first RS configuration used for the first set of RBs.

For example, the first RS configuration can be different from the second RS configuration in at least one of uniformity or density of REs indicated for transmitting the RS within the frequency resources, as described. In one example, the first RS configuration can have a greater density of REs than the second RS configuration at least in a first portion of the frequency resources that are closer in frequency to the frequency resources scheduled for uplink communications in the symbol. An example is shown and described in <FIG> above.

In this example, in method <NUM>, optionally at Block <NUM>, a second number of REs in the second set of RBs can be calculated based on the second RS configuration. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can calculate, based on the second RS configuration, the second number of REs (e.g., REs used for data) in the second set of RBs. For example, in calculating the second number of REs at Block <NUM>, optionally at Block <NUM>, a second set of frequency locations of RS REs in the second set of RBs indicated by the second RS configuration can be determined. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the second set of frequency locations of RS REs in the second set of RBs indicated by the second RS configuration. In another example, in calculating the second number of REs at Block <NUM>, optionally at Block <NUM>, a second offset metric associated with the second set of RBs can be determined. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can determine the second offset metric associated with the second set of RBs. For example, the second offset metric can be configured by higher layer signaling (e.g., RRC signaling) from the base station, and can also be used in calculating the second number of REs.

For example, as described, where the first RS configuration indicates RS REs that are uniformly distributed in the first set of RBs, RS resource determining component <NUM> can compute the number of REs (N'RE<NUM>) allocated for PDSCH within the first set of RBs, based on the following: <MAT> Similarly, for example, where the second RS configuration indicates RS REs that are uniformly distributed in the second set of RBs, RS resource determining component <NUM> can compute the number of REs (N'RE<NUM>) allocated for PDSCH within the second set of RBs, based on the following: <MAT> where the above formula assumes that the <MAT> and <MAT> specified for the second set of RBs are the same as the values defined in <NUM> NR (though other values can be used and configured for the UE). RS resource determining component <NUM> can also quantize N'RE<NUM> as N'RE<NUM> and N'RE<NUM> as N'RE<NUM> based on one or more tables, as described above. In this example, RS resource determining component <NUM> can determine the total number of REs allocated for PDSCH, N'RE, by N'RE = N'RE<NUM> · nPRB<NUM> + N'RE<NUM> · nPRB<NUM>, where nPRB<NUM> and nPRB<NUM> are the total number of allocated PRBs for the UE in the first set of RBs and the second set of RBs, respectively. TBS computing component <NUM> can compute the TBS (e.g., as described above) based on this calculated total number of REs.

In another example, where the first RS configuration indicates RS REs that are not uniformly distributed, RS resource determining component <NUM> can determine the total number of REs, N'RE<NUM>, for the first set of RBs based on the number of allocated PRBs and the frequency location of the PRBs. In addition, in this example, where the second set of RBs have a uniform distribution of RS REs, RS resource determining component <NUM> can compute the number of REs (N'RE<NUM>) allocated for PDSCH within the second set of RBs, based on the following: <MAT> where the above formula assumes that the <MAT> and <MAT> specified for the second set of RBs are the same as the values defined in <NUM> NR (though other values can be used and configured for the UE). RS resource determining component <NUM> can also quantize N'RE<NUM> as N'RE<NUM> and N'RE<NUM> as N'RE<NUM> based on one or more tables, as described above. In this example, RS resource determining component <NUM> can determine the total number of REs allocated for PDSCH, N'RE, by N'RE = N'RE<NUM> · nPRB<NUM> + N'RE<NUM> · nPRB<NUM>, where nPRB<NUM> and nPRB<NUM> are the total number of allocated PRBs for the UE in the first set of RBs and the second set of RBs, respectively. TBS computing component <NUM> can compute the TBS (e.g., as described above) based on this calculated total number of REs.

In some examples, RS resource determining component <NUM> can determine the split of multiple portions (e.g., which portion of frequency corresponds to the first portion and which corresponds to the second portion) from a configuration, which may be received from the base station <NUM>. For example, the base station can specify (e.g., via RRC signaling), the RS RE configuration for all portions (e.g., via corresponding RS configurations described above). In an example, in method <NUM>, optionally at Block <NUM>, the first RS configuration can be received from a base station. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can receive the first RS configuration from the base station. For example, RS resource determining component <NUM> can receive the first configuration in RRC signaling from the base station <NUM>. As described, for example, the first RS configuration can indicate at least frequency location information for RS REs, whether in the form of <MAT> or <MAT> for uniform distribution of RS REs, exact (or relative) frequency locations of the RS REs, exact (or relative) frequency locations of the data PRBs, etc., as described above, such that the number of REs for the data PRBs can be determined.

In an example, in method <NUM>, optionally at Block <NUM>, the second RS configuration can be received from a base station. In an aspect, RS resource determining component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, communicating component <NUM>, etc., can receive the second RS configuration from the base station. For example, RS resource determining component <NUM> can receive the second configuration in RRC signaling from the base station <NUM>. As described, for example, the second RS configuration can indicate at least frequency location information for RS REs, whether in the form of <MAT> or <MAT> for uniform distribution of RS REs (according to current <NUM> NR definition), exact (or relative) frequency locations of the RS REs, exact (or relative) frequency locations of the data PRBs, etc., as described above, such that the number of REs for the data PRBs can be determined.

In addition, in an example, RS resource determining component <NUM> can determine to consider at least the first RS configuration (and/or the first RS configuration for the first set of RBs and the second RS configuration for the second set of RBs) based on determining that the one or more symbols are configured for FD communications. In another example, RS resource determining component <NUM> can determine to use different tables to quantize the number of REs, as described above, based on determining that the one or more symbols are configured for FD communications. In another example, TBS computing component <NUM> can determine to compute the TBS using the modified mechanisms for calculating the REs above based on determining that the one or more symbols are configured for FD communications.

In addition, though described in terms of two sets of RBs and two corresponding RS configurations, the frequency resources can be split into additional portions with additional RS configurations indicated for each portion to allow the UE <NUM> to compute the number of REs for determining TBS, as described. Each additional portion can vary in at least one of uniformity or density of RS REs within the set of RBs, as described. Moreover, though described in terms of DMRS, similar concepts can be applied for determining the number of REs based on one or more DL CSI-RS configurations, which may apply to one or more sets of RBs and/or may indicate a distribution of CSI-RS REs that differ in at least one of uniformity or density, etc..

<FIG> illustrates a flow chart of an example of a method <NUM> for determining one or more RS configurations for transmitting an RS in one or more sets of RBs, in accordance with aspects described herein. In an example, a base station <NUM> can perform the functions described in method <NUM> using one or more of the components described in <FIG> and <FIG>.

In method <NUM>, at Block <NUM>, a first RS configuration for a first set of RBs, for downlink resources allocated in one or more symbols used for FD communications, can be determined. In an aspect, configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can determine, for downlink resources allocated in one or more symbols used for FD communications, the first RS configured for the first set of RBs. For example, configuring component <NUM> can determine or generate the first RS configuration as a distribution of RS REs used for transmitting a RS in frequency resources of one or more symbols, as described above, where the distribution can differ in at least one of uniformity or density from a second RS configuration (e.g., a legacy RS configuration specified in <NUM> NR).

In method <NUM>, at Block <NUM>, downlink communications can be transmitted, to a UE, and based on the first RS configuration, over the first set of RBs. In an aspect, configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can transmit, to the UE and based on the first RS configuration, the downlink communications over the first set of RBs. For example, configuring component <NUM> can transmit the downlink communications over the first set of RBs based on the first RS configuration such that the configuring component <NUM> transmits RSs in the RS REs and data in the remaining REs of the first set of RBs over the one or more symbols configured for FD communications.

In one example, as described above, for the one or more symbols configured for FD communications, the frequency resources may be split into multiple sets, where each set of RBs can differ in at least one of uniformity or density of RS REs, where one specific example is shown in <FIG>. Thus, in one example in method <NUM>, optionally at Block <NUM>, a second RS configuration for a second set of RBs, for downlink resources allocated in one or more symbols used for FD communications, can be determined. In an aspect, configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can determine or generate, for downlink resources allocated in one or more symbols used for FD communications, the second RS configuration for the second set of RBs. For example, configuring component <NUM> can determine the second RS configuration as a distribution of RS REs used for transmitting a RS in the second set of RBs of the one or more symbols, as described above, where the distribution can differ in at least one of uniformity or density from the first RS configuration. In one example, the second RS configuration can be a legacy RS configuration specified in <NUM> NR, which can be substantially uniform and defined according to a number of REs for DMRS per PRB (e.g., <MAT>).

In this example, in method <NUM>, optionally at Block <NUM>, downlink communications can be transmitted, to a UE, and based on the second RS configuration, over the second set of RBs. In an aspect, configuring component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, etc., can transmit, to the UE and based on the second RS configuration, the downlink communications over the second set of RBs. For example, configuring component <NUM> can transmit the downlink communications over the second set of RBs based on the second RS configuration such that the configuring component <NUM> transmits RSs in the RS REs and data in the remaining REs of the second set of RBs.

In method <NUM>, optionally at Block <NUM>, the first RS configuration can be transmitted to the UE. In an aspect, configuration generating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, configuring component <NUM>, etc., can transmit the first RS configuration to the UE. For example, configuration generating component <NUM> can generate the first RS configuration to indicate at least frequency location information for RS REs, whether in the form of <MAT> or <MAT> for uniform distribution of RS REs, exact (or relative) frequency locations of the RS REs, exact (or relative) frequency locations of the data PRBs, etc., as described above, such that the number of REs for the data PRBs can be determined. Configuration generating component <NUM> can transmit the first configuration to the UE (e.g., in RRC signaling) to allow the UE to determine the number of REs for the data PRBs in the first set of RBs to compute the TBS, as described above.

In method <NUM>, optionally at Block <NUM> (e.g., where the base station <NUM> determines the second RS configuration), the second RS configuration can be transmitted to the UE. In an aspect, configuration generating component <NUM>, e.g., in conjunction with processor(s) <NUM>, memory <NUM>, transceiver <NUM>, configuring component <NUM>, etc., can transmit the second RS configuration to the UE. For example, configuration generating component <NUM> can generate the second RS configuration to indicate at least frequency location information for RS REs, whether in the form of <MAT> or <MAT> for uniform distribution of RS REs, exact (or relative) frequency locations of the RS REs, exact (or relative) frequency locations of the data PRBs, etc., as described above, such that the number of REs for the data PRBs can be determined. Configuration generating component <NUM> can transmit the second configuration to the UE (e.g., in RRC signaling) to allow the UE to determine the number of REs for the data PRBs in the second set of RBs to compute the TBS, as described above.

<FIG> is a block diagram of a MIMO communication system <NUM> including a base station <NUM> and a UE <NUM>. The MIMO communication system <NUM> may illustrate aspects of the wireless communication access network <NUM> described with reference to <FIG>. The base station <NUM> may be an example of aspects of the base station <NUM> described with reference to <FIG>. The base station <NUM> may be equipped with antennas <NUM> and <NUM>, and the UE <NUM> may be equipped with antennas <NUM> and <NUM>. In the MIMO communication system <NUM>, the base station <NUM> may be able to send data over multiple communication links at the same time. Each communication link may be called a "layer" and the "rank" of the communication link may indicate the number of layers used for communication. For example, in a 2x2 MIMO communication system where base station <NUM> transmits two "layers," the rank of the communication link between the base station <NUM> and the UE <NUM> is two.

The UE <NUM> may be an example of aspects of the UEs <NUM> described with reference to <FIG>. At the UE <NUM>, the UE antennas <NUM> and <NUM> may receive the DL signals from the base station <NUM> and may provide the received signals to the modulator/demodulators <NUM> and <NUM>, respectively. Each modulator/demodulator <NUM> through <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator <NUM> through <NUM> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector <NUM> may obtain received symbols from the modulator/demodulators <NUM> and <NUM>, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive (Rx) processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE <NUM> to a data output, and provide decoded control information to a processor <NUM>, or memory <NUM>.

The processor <NUM> may in some cases execute stored instructions to instantiate a communicating component <NUM> (see e.g., <FIG> and <FIG>).

The processor <NUM> may in some cases execute stored instructions to instantiate a configuring component <NUM> (see e.g., <FIG> and <FIG>).

Similarly, the components of the base station <NUM> may, individually or collectively, be implemented with one or more application specific integrated circuits (ASICs) adapted to perform some or all of the applicable functions in hardware.

The above detailed description set forth above in connection with the appended drawings describes examples, wherein the term "example," when used in this description, means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a specially programmed device, such as but not limited to a processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A specially programmed processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. 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, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. If implemented in software (e.g., executed by a processor), the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. For example, due to the nature of software, functions described above can be implemented using software (e.g., executed by a specially programmed processor), hardware, hardwiring, or combinations of any of these.

Claim 1:
An apparatus for wireless communication, the apparatus being a user equipment, UE (<NUM>), and comprising:
means for receiving, over downlink resources allocated in a symbol used for full-duplex communication, a first set of resource blocks including a first number of resource elements corresponding to a reference signal and a second set of resource blocks including a second number of resource elements corresponding to the reference signal, wherein the first number of resource elements is calculated based on a first reference signal configuration and the second number of resource elements is calculated based on a second reference signal configuration, wherein the first number of resource elements in accordance with the first reference signal configuration are different in at least one of uniformity of distribution or density, in frequency, than the second reference signal configuration; and
means for decoding, according to a transport block size that is based at least in part on at least the first number of resource elements, a downlink communication received in the downlink resources.