Patent ID: 12238040

DETAILED DESCRIPTION

In some wireless communications systems, a user equipment (UE) may receive two or more repetitions of a transport block within a transmission interval (e.g., within a slot) (e.g., in the case of a physical downlink shared channel (PDSCH) transmission scheme). The transport block may include a total number of information bits, and each repetition may include a set of bits representative of the total number of information bits. As such, the UE may process more bits as the UE decodes each additional repetition of the transport block. In some cases, the UE may perform separate rate matching where the UE may perform rate matching across each repetition separately to decode the transport block. Although the repetitions corresponds to the same transport block, the UE may lack the ability to sum a data rate for PDSCHs across multiple component carriers (CCs) or in one CC of the PDSCH, and as such, the UE may fail to process or decode all of the information bits in each repetition of the transport block.

Techniques described herein enable a UE to use improved data rate decoding for PDSCH transport blocks. In some cases, a base station may schedule two or more repetitions of a transport block for a PDSCH in a first CC of multiple CCs, where a first repetition may be scheduled in a first transmission occasion and a second repetition may be scheduled in a second transmission occasion. The base station may schedule the first and second repetitions based on a time division multiplexing (TDM) resource allocation scheme or a frequency division multiplexing (FDM) resource allocation scheme. The UE may monitor for each repetition of the transport block in the respective transmission occasion, and the UE may decode the transport block based on a number of transmission occasions associated with the PDSCH in the first CC and a data rate limit across the multiple CCs including the first CC.

In some examples, the UE may have a data rate capability for the multiple CCs including the first CC, where the data rate limit may be determined based on the data rate capability of the UE, and where the base station may schedule the two repetitions based on receiving a capability message indicating the data rate capability of the UE. The UE may calculate a data rate across all CCs in one or more PDSCHs for a TDM resource allocation scheme or an FDM resource allocation scheme, where the UE may count each transmission occasion (e.g., each repetition) received in the PDSCH separately toward a total number of transport blocks in that CC. In some cases, the UE may calculate a data rate in one PDSCH in one CC for a TDM resource allocation scheme or an FDM resource allocation scheme, where the UE may count each transmission occasion (e.g., each repetition) as one PDSCH.

Particular aspects of the subject matter described herein may be implemented to realize one or more advantages. The described techniques may support improvements in data rate decoding for transport blocks. For example, in some cases, the described techniques may enable the UE to decode a transport block based on a number of transmission occasions associated with repetitions of the transport block and a data rate limit, which may reduce power consumption and improve user experience. As such, supported techniques may include improved network operations, and, in some examples, may promote network efficiencies, among other benefits.

Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are then described in the context of resource allocation schemes and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to data rate decoding for transport blocks.

FIG.1illustrates an example of a wireless communications system100that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The wireless communications system100may include one or more base stations105, one or more UEs115, and a core network130. In some examples, the wireless communications system100may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communications system100may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

The base stations105may be dispersed throughout a geographic area to form the wireless communications system100and may be devices in different forms or having different capabilities. The base stations105and the UEs115may wirelessly communicate via one or more communication links125. Each base station105may provide a coverage area110over which the UEs115and the base station105may establish one or more communication links125. The coverage area110may be an example of a geographic area over which a base station105and a UE115may support the communication of signals according to one or more radio access technologies.

The UEs115may be dispersed throughout a coverage area110of the wireless communications system100, and each UE115may be stationary, or mobile, or both at different times. The UEs115may be devices in different forms or having different capabilities. Some example UEs115are illustrated inFIG.1. The UEs115described herein may be able to communicate with various types of devices, such as other UEs115, the base stations105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as shown inFIG.1.

The base stations105may communicate with the core network130, or with one another, or both. For example, the base stations105may interface with the core network130through one or more backhaul links120(e.g., via an S1, N2, N3, or other interface). The base stations105may communicate with one another over the backhaul links120(e.g., via an X2, Xn, or other interface) either directly (e.g., directly between base stations105), or indirectly (e.g., via core network130), or both. In some examples, the backhaul links120may be or include one or more wireless links.

One or more of the base stations105described herein may include or may be referred to by a person having ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.

A UE115may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE115may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE115may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.

The UEs115described herein may be able to communicate with various types of devices, such as other UEs115that may sometimes act as relays as well as the base stations105and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown inFIG.1.

The UEs115and the base stations105may wirelessly communicate with one another via one or more communication links125over one or more carriers. The term “carrier” may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication links125. For example, a carrier used for a communication link125may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system100may support communication with a UE115using carrier aggregation or multi-carrier operation. A UE115may be configured with multiple downlink CCs and one or more uplink CCs according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) CCs.

In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be positioned according to a channel raster for discovery by the UEs115. A carrier may be operated in a standalone mode where initial acquisition and connection may be conducted by the UEs115via the carrier, or the carrier may be operated in a non-standalone mode where a connection is anchored using a different carrier (e.g., of the same or a different radio access technology).

The communication links125shown in the wireless communications system100may include uplink transmissions from a UE115to a base station105, or downlink transmissions from a base station105to a UE115. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system100. For example, the carrier bandwidth may be one of a number of determined bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system100(e.g., the base stations105, the UEs115, or both) may have hardware configurations that support communications over a particular carrier bandwidth or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system100may include base stations105or UEs115that support simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE115may be configured for operating over portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

Signal waveforms transmitted over a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal FDM (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may consist of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements that a UE115receives and the higher the order of the modulation scheme, the higher the data rate may be for the UE115. A wireless communications resource may refer to a combination of a radio frequency spectrum resource, a time resource, and a spatial resource (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communications with a UE115.

One or more numerologies for a carrier may be supported, where a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE115may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE115may be restricted to one or more active BWPs.

The time intervals for the base stations105or the UEs115may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of TS=1/(Δfmax·Nf) seconds, where Δfmaxmay represent the maximum supported subcarrier spacing, and Nfmay represent the maximum supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

Each frame may include multiple consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems100, a slot may further be divided into multiple mini-slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system100and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system100may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

Physical channels may be multiplexed on a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed on a downlink carrier, for example, using one or more of TDM techniques, FDM techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs115. For example, one or more of the UEs115may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs115and UE-specific search space sets for sending control information to a specific UE115.

Each base station105may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a base station105(e.g., over a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others). In some examples, a cell may also refer to a geographic coverage area110or a portion of a geographic coverage area110(e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the base station105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with geographic coverage areas110, among other examples.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs115with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered base station105, as compared with a macro cell, and a small cell may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs115with service subscriptions with the network provider or may provide restricted access to the UEs115having an association with the small cell (e.g., the UEs115in a closed subscriber group (CSG), the UEs115associated with users in a home or office). A base station105may support one or multiple cells and may also support communications over the one or more cells using one or multiple CCs.

In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

In some examples, a base station105may be movable and therefore provide communication coverage for a moving geographic coverage area110. In some examples, different geographic coverage areas110associated with different technologies may overlap, but the different geographic coverage areas110may be supported by the same base station105. In other examples, the overlapping geographic coverage areas110associated with different technologies may be supported by different base stations105. The wireless communications system100may include, for example, a heterogeneous network in which different types of the base stations105provide coverage for various geographic coverage areas110using the same or different radio access technologies.

Some UEs115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station105without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that makes use of the information or presents the information to humans interacting with the application program. Some UEs115may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

Some UEs115may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a move that supports one-way communication via transmission or reception, but not transmission and reception simultaneously). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs115include entering a power saving deep sleep mode when not engaging in active communications, operating over a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs115may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

The wireless communications system100may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system100may be configured to support ultra-reliable low-latency communications (URLLC) or mission critical communications. The UEs115may be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission critical functions). Ultra-reliable communications may include private communication or group communication and may be supported by one or more mission critical services such as mission critical push-to-talk (MCPTT), mission critical video (MCVideo), or mission critical data (MCData). Support for mission critical functions may include prioritization of services, and mission critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission critical, and ultra-reliable low-latency may be used interchangeably herein.

In some examples, a UE115may also be able to communicate directly with other UEs115over a device-to-device (D2D) communication link135(e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs115utilizing D2D communications may be within the geographic coverage area110of a base station105. Other UEs115in such a group may be outside the geographic coverage area110of a base station105or be otherwise unable to receive transmissions from a base station105. In some examples, groups of the UEs115communicating via D2D communications may utilize a one-to-many (1:M) system in which each UE115transmits to every other UE115in the group. In some examples, a base station105facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out between the UEs115without the involvement of a base station105.

The core network130may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network130may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs115served by the base stations105associated with the core network130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services150for one or more network operators. The IP services150may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

Some of the network devices, such as a base station105, may include subcomponents such as an access network entity140, which may be an example of an access node controller (ANC). Each access network entity140may communicate with the UEs115through one or more other access network transmission entities145, which may be referred to as radio heads, smart radio heads, or transmission/reception points (TRPs). Each access network transmission entity145may include one or more antenna panels. In some configurations, various functions of each access network entity140or base station105may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., a base station105).

The wireless communications system100may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. The UHF waves may be blocked or redirected by buildings and environmental features, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs115located indoors. The transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

The wireless communications system100may also operate in a super high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter band, or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system100may support millimeter wave (mmW) communications between the UEs115and the base stations105, and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate use of antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater atmospheric attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

The wireless communications system100may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communications system100may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, devices such as the base stations105and the UEs115may employ carrier sensing for collision detection and avoidance. In some examples, operations in unlicensed bands may be based on a carrier aggregation configuration in conjunction with CCs operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

A base station105or a UE115may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a base station105or a UE115may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a base station105may be located in diverse geographic locations. A base station105may have an antenna array with a number of rows and columns of antenna ports that the base station105may use to support beamforming of communications with a UE115. Likewise, a UE115may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support radio frequency beamforming for a signal transmitted via an antenna port.

The base stations105or the UEs115may use MIMO communications to exploit multipath signal propagation and increase the spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a base station105, a UE115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating at particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

The wireless communications system100may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE115and a base station105or a core network130supporting radio bearers for user plane data. At the physical layer, transport channels may be mapped to physical channels.

The UEs115and the base stations105may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly over a communication link125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device may support same-slot HARQ feedback, where the device may provide HARQ feedback in a specific slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

In some cases, a UE115may use improved data rate decoding for PDSCH transport blocks. For example, a base station105may schedule two or more repetitions of a transport block for a PDSCH in a first CC of multiple CCs, where a first repetition may be scheduled in a first transmission occasion and a second repetition may be scheduled in a second transmission occasion. The base station105may schedule the first and second repetitions based on a TDM resource allocation scheme or an FDM resource allocation scheme. The UE115may monitor for each repetition of the transport block in the respective transmission occasion, and the UE115may decode the transport block based on a number of transmission occasions associated with the PDSCH in the first CC and a data rate limit across the multiple CCs including the first CC.

In some examples, the UE115may have a data rate capability for the multiple CCs including the first CC, where the data rate limit may be determined based on the data rate capability of the UE115, and where the base station105may schedule the two repetitions based on receiving a capability message indicating the data rate capability of the UE115. The UE115may calculate a data rate across all CCs in one or more PDSCHs for a TDM resource allocation scheme or an FDM resource allocation scheme, where the UE115may count each transmission occasion (e.g., each repetition) received in the PDSCH separately toward a total number of transport blocks in that CC. In some cases, the UE115may calculate a data rate in one PDSCH in one CC for a TDM resource allocation scheme or an FDM resource allocation scheme, where the UE115may count each transmission occasion (e.g., each repetition) as one PDSCH.

FIG.2illustrates an example of a wireless communications system200that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. In some examples, the wireless communications system200may implement aspects of the wireless communications system100or may be implemented by aspects of the wireless communications system100. For example, the wireless communications system200may include a UE115-aand a base station105-a, which may be examples of corresponding devices described herein. The wireless communications system200may include features for improved communications between the UE115-aand the base station105-a, among other benefits.

In some cases, a UE115-amay have some processing capability (e.g., capability 1, capability 2) for processing a PDSCH. The UE115-amay be associated with a PDSCH processing time, which may be the time duration between the UE115-areceiving a last symbol of a PDSCH and the UE115-atransmitting a first symbol of a physical uplink control channel (PUCCH) that may carry HARQ acknowledgment (ACK) feedback corresponding to the PDSCH. In some cases, a number of symbols N1may determine the processing time, where N1may depend on a capability of the UE115-a(e.g., processing capability 1, processing capability 2), a subcarrier spacing (e.g., μ), and whether additional demodulation reference signal (DMRS) symbols are configured (e.g., for capability 1). For a UE115-athat supports a processing capability 2 on a given cell, the processing time (e.g., according to the UE processing capability 2) may be applied if a higher layer parameter (e.g., processingType2Enabled in PDSCH-ServingCellConfig) is configured for the cell and set to an enabled setting. In some cases, the processing capability 2 may be defined for frequency range 1 (FR1).

The UE115-amay sum a data rate across CCs (e.g., in a slot) based on a processing capability of the UE115-a. In some examples, the UE115-amay sum the data rate across all CCs (e.g., in a slot) according to Equation 1:

∑j=0J-1∑m=1M-1Vj,mTslotμ⁡(j)≤DataRate(1)

In some examples, Tslotμ(j)may represent the duration of a slot sj, and Vj,mmay represent the number of information bits of the mth transport block in slot sjin the jth CC (e.g., of the jth serving cell). The UE115-amay sum over all of the M transport blocks received in the CCjof the slot sjacross the CCs, which may be less than or equal to the data rate (e.g., DataRate) of the UE115-a. The data rate may be calculated based on a capability of the UE115-a. As such, the data rate may depend on what information the UE115-amay receive, including corresponding configurations and scheduling (e.g., via downlink control information (DCI)) in different CCs. In some cases, the base station105-aand the UE115-amay refrain from exceeding the data rate in Equation 1.

In some cases, the UE115-amay additionally, or alternatively, have a per-CC data rate limitation, which may be a data rate limitation when PDSCH processing capability 2 is configured for a CC (e.g., a base station105-amay fail to distribute a load across CCs for capability 2). The per-CC data rate limitation may be calculated according to Equation 2:

∑m=1M-1Vj,mL×Tsμ≤DataRateCC(2)

In some cases, the UE115-amay calculate the per-CC data rate limitation in addition to the data rate limitation across all CCs to ensure that both limitations are satisfied for capability 2 or for PDSCH retransmissions. Equation 2 may be calculated for a single PDSCH in one CC, where L may represent the number of symbols assigned to the PDSCH,

Tsμ=10-82μ·Nsymbolslot,
and μ may represent the numerology of the PDSCH. The per-CC data rate (e.g., DataRateCC) may be calculated based on a capability of the UE115-afor a given CC (e.g., instead of across CCs).

The data rate capability of the UE115-amay be based on a reported UE capability (e.g., instead of being related to a network configuration for scheduling information). The data rate (e.g., in Mbps) may be calculated according to Equation 3:

data⁢rate=10-6·∑j=1J(vlayers(j)·Qm(j)·f(j)·Rmax·NPRBBW⁡(j),μ·12Tsμ·(1-OH(j)))(3)

The data rate (e.g., in Mbps) may be calculated based on parameters the UE115-amay indicate in UE capability signaling. In some cases, vlayers(j)may represent a number of supported layers given by a higher layer parameter for a PDSCH or a physical uplink shared channel (PUSCH) (e.g., maxNumberMIMO-LayersPDSCH for downlink, maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for uplink), Qm(j)may represent a supported modulation order given by a higher layer parameter (e.g., supportedModulationOrderDL for downlink, supporedModulationOrderUL for uplink), and f(j)may represent a scaling factor given by a higher layer parameter (e.g., scalingFactor), which may take a value of 1, 0.8, 0.75, and 0.4. In some cases, the scaling factor may enable the UE115-athe flexibility to indicate that the UE115-amay refrain from operating at a peak data rate across all CCs at any given time, even if the UE115-asupports a high number of layers and a high modulation order. In some cases, Rmaxmay represent a code rate (e.g., a maximum code rate), NPRBBW(j),μmay represent a number of RBs in a symbol, where μ may represent the numerology (e.g., subcarrier spacing), and Tsμmay represent an average OFDM symbol duration in a subframe for numerology μ. In some cases, OH(j)may represent an overhead value, and may take a different value depending on the operating frequency range (e.g., FR1, FR2) and the type of communications (e.g., uplink, downlink). As such, the UE115-amay calculate a data rate with respect to one symbol.

The UE115-amay receive a transport block from the base station105-aconfigured for different PDSCH transmission schemes. For example, the transport block may be transmitted using a TDM resource allocation scheme or an FDM resource allocation scheme, which are described herein with reference toFIGS.3A and3B, respectively. In some cases, the UE115-amay receive two or more repetitions of the same transport block within one slot (e.g., as in the case of PDSCH transmission schemes TDMSchemeA and FDMSchemeB). The UE115-amay perform separate rate matching in order to decode the transport block, and the UE115-amay perform the rate matching across each repetition separately. That is, even though the repetitions may correspond to the same transport block, the UE115-amay count each repetition separately for the purpose of either sum data rate limitation across all CCs or sum data rate limitation in one CC. For example, the sum data rate as calculated in Equation 1 may be based on one transport block (e.g., the Mth transport block) instead of the number of repetitions of the transport block. That is, the UE115-amay receive two repetitions of the transport block, and without an indication from the UE115-athat the UE115-amay count the two repetitions (e.g., the two transmission occasions) separately toward the data rate, the repetitions may be counted once, which may not represent the full complexity at the UE115-a.

In some examples, for the sum data rate limitation in one CC for an FDM resource allocation scheme, each transmission occasion may satisfy the half of a data rate per CC given that two transmission occasions corresponding to the two repetitions of the transport block may be in the same symbols. That is, the per-CC data rate limitation described with reference to Equation 2 may be divided by two in the case of an FDM resource allocation scheme because each repetition may contribute individually to the complexity associated with the data rate. In some cases, for PUSCH repetitions in one slot (e.g., PUSCH repetition Type B), each repetition may be counted separately toward the sum data rate. In addition, for the per-CC data rate limitation, each repetition (e.g., for PUSCH repetition Type B) may be treated as one PUSCH. However, PDSCH repetitions for the TDM resource allocation scheme and the FDM resource allocation scheme may lack these data rate limitation techniques.

The wireless communications system200may implement techniques for improved data rate decoding of transport blocks. For example, the wireless communications system200may support decoding transport blocks for PDSCHs across multiple CCs. In some examples, for sum data rate limitation across all CCs (e.g., in one or more PDSCHs), if in a jth CC with reference to Equation (1, a PDSCH with two or more transmission occasions220of a same transport block (e.g., two or more repetitions of the transport block) are received by the UE115-a, each transmission occasion220may be counted separately toward the quantity of M transport blocks in the slot in that CC. For example, in a given CC, the UE115-amay receive M transport blocks in a given slot sj. If the UE115-areceives two different repetitions of two different transport blocks in the slot sj, then the UE115-amay count 4 transport blocks toward the total quantity of M transport blocks.

The UE115-amay use the sum data rate limitation across all CCs for a TDM resource allocation scheme (e.g., TDMSchemeA), where the UE115-amay receive two non-overlapping transmission occasions in the time domain, and for an FDM resource allocation scheme (e.g., FDMSchemeB), where the UE115-amay receive two non-overlapping transmission occasions in the frequency domain. For example, the UE115-amay receive a transmission occasion220-aand a transmission occasion220-bthat may be non-overlapping in the time domain or in the frequency domain. The TDM resource allocation scheme and the FDM resource allocation scheme are described herein in more detail with reference toFIGS.3A and3B, respectively. The UE115-amay also use the sum data rate limitation across all CCs in which a PDSCH with two or more transmission occasions220may be received. For example, a first PDSCH in a first CC may include two repetitions of the transport block and a second PDSCH different from the first PDSCH in a second CC may include two repetitions of the transport block. If each of the CCs follows the TDM resource allocation scheme or the FDM resource allocation scheme, then the UE115-amay count each transmission occasion220separately toward the M transport blocks in each CC. The sum of all of the transmission occasions220over all of the CCs may then be less than or equal to the sum data rate across all CCs (e.g., following Equation 1).

In some examples, the wireless communications system200may support decoding transport blocks for a PDSCH in one CC. For sum data rate limitation in one PDSCH in one CC, using Equation 2, the UE115-amay treat each transmission occasion220(e.g., each repetition of the transport block) as one PDSCH. The UE115-amay use the per-CC data rate for the TDM resource allocation scheme (e.g., TDMSchemeA), where the UE115-amay receive two non-overlapping transmission occasions in the time domain, and the FDM resource allocation scheme (e.g., FDMSchemeB), where the UE115-amay receive two non-overlapping transmission occasions in the frequency domain. In some cases, for the TDM resource allocation scheme, the number of symbols L as described with reference to Equation 2, may be equal to the duration of one transmission occasion220rather than the duration of both transmission occasions220together. In some cases, for the FDM resource allocation scheme, the data rate per transmission occasion220may be smaller than or equal to half of the per-CC data rate (e.g., DataRateCC/2) because the UE115-amay receive the two transmission occasions220at the same time in the same symbols.

The UE115-amay use the per-CC data rate when the UE115-areceives a PDSCH in a CC configured with a PDSCH processing capability of the UE115-a(e.g., a processing capability 2, a data rate capability), where the processing capability may enable advanced or enhanced processing. Additionally, or alternatively, the UE115-amay use the per-CC data rate if a scheduled PDSCH is a retransmission with a reserved modulation and coding scheme (MCS) value (e.g., from an MCS table), in which case the UE115-amay perform a transport block size (TBS) calculation based on a previous transmission.

In some examples, the UE115-amay communicate with the base station105-avia a communications link210, which may be a downlink communications link. The UE115-amay receive DCI215from the base station105-a, which may schedule the two repetitions of the transport block for a PDSCH in a first CC of multiple CCs. A first repetition may be scheduled in the transmission occasion220-aand a second repetition may be scheduled in the transmission occasion220-b. In some cases, UE115-amay transmit a capability message to the base station105-a, which may indicate a data rate capability of the UE115-afor the multiple CCs. The base station105-amay schedule the transmission occasions220based on the capability message. The UE115-amay monitor for the transmission occasion220-aand the transmission occasion220-b(e.g., and the respective repetitions of the transport block), and the UE115-amay decode the transport block based on a number of transmission occasions220associated with the PDSCH in the first CC and a data rate limit across the multiple CCs including the first CC.

In some examples, the UE115-amay be configured for sum data rate limitation across all CCs, where the UE115-amay count the transmission occasion220-aand the transmission occasion220-bseparately for a data rate calculation (e.g., toward the M transport blocks in the slot sjin the jth CC). As such, if M is the number of transport blocks transmitted in the slot sj, and if there are two transmission occasions220of the same transport block in the time domain or in the frequency domain (e.g., according to TDMSchemeA or FDMSchemeB) in the slot sj, then the UE115-amay count each transmission occasion220separately. In some other examples, the UE115-amay be configured for sum data rate limitation in one PDSCH in one CC (e.g., per-CC data rate), where the UE115-amay determine a second data rate limit (e.g., DataRateCC) associated with the PDSCH for the first CC based on a quantity of symbols L for the transmission occasion220-a, and a third data rate limit associated with the PDSCH for the first CC based on a quantity of symbols L for the transmission occasion220-b. That is, if L is the quantity of symbols assigned to the PDSCH, then for a PDSCH that includes two transmission occasions220in the time domain in one slot, L may be the quantity of symbols of one transmission occasion220.

FIG.3Aillustrates an example of a resource allocation scheme300that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. In some examples, the resource allocation scheme300may implement aspects of the wireless communications systems100and200or may be implemented by aspects of the wireless communications systems100and200, as described with reference toFIGS.1and2.

In some cases, a UE may communicate with a base station using a multiplexing scheme. For example, the UE may use the resource allocation scheme300(e.g., TDMSchemeA), where the UE may receive DCI that may schedule two TDM transmission occasions of the same transport block (e.g., two repetitions of the same transport block) within one transmission interval, such as a slot305. In some cases, the slot305may include 14 symbols. The UE may receive the two repetitions when a transmission configuration indicator (TCI) field within the DCI indicates two TCI states. For example, the UE may receive a transmission occasion310-aand a transmission occasion310-b, where the transmission occasions correspond to a first repetition and a second repetition of the transport block (e.g., for a PDSCH in a CC). The transmission occasion310-amay have a TCI state 1, and the transmission occasion310-bmay have a TCI state 2.

In some examples, a time domain resource allocation (TDRA) field in the DCI may be for the transmission occasion310-a(e.g., the first repetition). The TDRA field may indicate the length L (e.g., in number of symbols) and a starting symbol (S) of the transmission occasion310-a. For example, the TDRA field of the DCI may indicate that S=3 and L=4. As such, the transmission occasion310-amay start at the fourth symbol (having slot index 3) in the slot305and extend for four total symbols. In some cases, the transmission occasion310-b(e.g., the second repetition) may have the same length as the transmission occasion310-a. As such, the transmission occasion310-bmay likewise have a length in symbols of L=4. In some cases, a gap315may be configurable between the transmission occasion310-aand the transmission occasion310-b. The gap315may be RRC configured and may have a duration of two symbols. In some examples, the first repetition and the second repetition may have different redundancy versions (RVs). For example, the first repetition may have an RV of 0 and the second repetition may have an RV of 2.

The UE may indicate to a base station whether the UE supports the resource allocation scheme300or a different scheme such as an FDM resource allocation scheme, as described herein with reference toFIG.3B. Based on the indication from the UE, the base station may configure and dynamically schedule the transmission occasion310-aand the transmission occasion310-busing the DCI.

The UE may monitor transmission occasions310-aand310-bto decode a transport block having multiple repetitions. For example, the UE may monitor transmission occasion310-afor a first repetition of the transport block over a given CC and the UE may monitor transmission occasion310-bfor a second repetition of the transport block over the same CC or a different CC. To decode the transport block, the UE may count or sum the data rate separately for each repetition or transmission occasion. That is, the UE may consider a sum data rate limitation across all CCs as part of the data rate calculation for decoding the transport block because each repetition individually contributes to the complexity associated with the data rate.

FIG.3Billustrates an example of a resource allocation scheme301that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. In some examples, the resource allocation scheme301may implement aspects of the wireless communications systems100and200or may be implemented by aspects of the wireless communications systems100and200, as described herein with reference toFIGS.1and2.

In some cases, a UE may communicate signaling with a base station using a multiplexing scheme. For example, the UE may use the resource allocation scheme301(e.g., FDMSchemeB), where the UE may receive a DCI scheduling two FDMed (e.g., non-overlapping frequency domain resource allocation (FDRA)) transmission occasions310of the same transport block (e.g., two repetitions of the same transport block). The UE may receive the two repetitions when a TCI field within the DCI indicates two TCI states. For example, the UE may receive a PDSCH320including a quantity of RBs, where a transmission occasion310-c(e.g., a first repetition of the transport block) may correspond to a first RB set and a transmission occasion310-d(e.g., a second repetition of the transport block) may correspond to a second RB set.

In some cases, the transmission occasion310-cmay have a first TCI state, and the transmission occasion310-dmay have a second TCI state. The transmission occasion310-cand the transmission occasion310-dmay each have a length L=6 symbols, and each RB set may include four RBs. In some cases, an FDRA field may be for overall RBs across the transmission occasion310-cand the transmission occasion310-d. As such, the FDRA field may indicate all of the RBs in the first RB set and the second RB set (e.g., across both repetitions corresponding to both transmission occasions310), and the first RB set and the second RB set may each correspond to a different TCI state. In some examples, the first repetition and the second repetition may have different RVs. For example, the first repetition may have an RV of 0 and the second repetition may have an RV of 2.

The UE may indicate to a base station whether the UE supports the resource allocation scheme301or a different scheme such as a TDM resource allocation scheme, which is described herein with reference toFIG.3A. Based on the indication from the UE, the base station may configure and dynamically schedule the transmission occasion310-cand the transmission occasion310-dusing DCI.

The UE may monitor transmission occasions310-cand310-dto decode a transport block having multiple repetitions. For example, the UE may monitor transmission occasion310-cfor a first repetition of the transport block over a given CC and the UE may monitor transmission occasion310-dfor a second repetition of the transport block over the same CC or a different CC. To decode the transport block, the UE may count or sum the data rate separately for each repetition or transmission occasion. That is, the UE may consider a sum data rate limitation across all CCs as part of the data rate calculation for decoding the transport block because each repetition individually contributes to the complexity associated with the data rate.

FIG.4illustrates an example of a process flow400that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The process flow400may implement aspects of wireless communications systems100and200, or may be implemented by aspects of the wireless communications system100and200. For example, the process flow400may illustrate operations between a UE115-band a base station105-b, which may be examples of corresponding devices described herein. In the following description of the process flow400, the operations between the UE115-band the base station105-bmay be transmitted in a different order than the example order shown, or the operations performed by the UE115-band the base station105-bmay be performed in different orders or at different times. Some operations may also be omitted from the process flow400, and other operations may be added to the process flow400.

At405, the UE115-bmay transmit, to the base station105-b, a UE capability message indicating a data rate capability of the UE115-bfor multiple CCs including a first CC. In some cases, the data rate capability may indicate that the UE115-bmay sum a data rate across the multiple CCs or sum the data rate in the first CC.

At410, the UE115-bmay receive, from the base station105-b, a downlink control message (e.g., DCI) that schedules a first repetition and a second repetition of a transport block for a PDSCH in a first CC of multiple CCs. In some cases, the first repetition may be scheduled in a first transmission occasion of multiple transmission occasions and the second repetition may be scheduled in a second transmission occasion of the multiple transmission occasions associated with the PDSCH. In some cases, the UE115-bmay receive the downlink control message based on the data rate capability of the UE115-b.

At415, the UE115-bmay monitor for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based at least in part on the downlink control message.

At420, the UE115-bmay decode the transport block based on the monitoring, a number of transmission occasions of the multiple transmission occasions associated with the PDSCH in the first CC, and a data rate limit across the plurality of CCs including the first CC. For example, the UE115-bmay sum a data rate across all CCs in one or more PDSCHs, where the data rate limit may be based on the data rate capability of the UE115-b. In some cases, the UE115-bmay sum the data rate across the first CC in the PDSCH, where a second data rate limit for the first CC may be half of a data rate capability of the UE for the first CC.

FIG.5shows a block diagram500of a device505that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device505may be an example of aspects of a UE115as described herein. The device505may include a receiver510, a transmitter515, and a communications manager520. The device505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver510may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). Information may be passed on to other components of the device505. The receiver510may utilize a single antenna or a set of multiple antennas.

The transmitter515may provide a means for transmitting signals generated by other components of the device505. For example, the transmitter515may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). In some examples, the transmitter515may be co-located with a receiver510in a transceiver module. The transmitter515may utilize a single antenna or a set of multiple antennas.

The communications manager520, the receiver510, the transmitter515, or various combinations thereof or various components thereof may be examples of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager520, the receiver510, the transmitter515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager520may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver510, the transmitter515, or both. For example, the communications manager520may receive information from the receiver510, send information to the transmitter515, or be integrated in combination with the receiver510, the transmitter515, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager520may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager520may be configured as or otherwise support a means for receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The communications manager520may be configured as or otherwise support a means for monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The communications manager520may be configured as or otherwise support a means for decoding the transport block based on the monitoring, a number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the set of multiple CCs including the first CC.

By including or configuring the communications manager520in accordance with examples as described herein, the device505(e.g., a processor controlling or otherwise coupled to the receiver510, the transmitter515, the communications manager520, or a combination thereof) may support techniques for data rate decoding for transport blocks, which may reduce power consumption and improve coordination between devices. Further, the supported techniques may improve network operations and promote network efficiencies.

FIG.6shows a block diagram600of a device605that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device605may be an example of aspects of a device505or a UE115as described herein. The device605may include a receiver610, a transmitter615, and a communications manager620. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver610may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). Information may be passed on to other components of the device605. The receiver610may utilize a single antenna or a set of multiple antennas.

The transmitter615may provide a means for transmitting signals generated by other components of the device605. For example, the transmitter615may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). In some examples, the transmitter615may be co-located with a receiver610in a transceiver module. The transmitter615may utilize a single antenna or a set of multiple antennas.

The device605, or various components thereof, may be an example of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager620may include a downlink control message reception component625, a monitoring component630, a decoding component635, or any combination thereof. The communications manager620may be an example of aspects of a communications manager520as described herein. In some examples, the communications manager620, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver610, the transmitter615, or both. For example, the communications manager620may receive information from the receiver610, send information to the transmitter615, or be integrated in combination with the receiver610, the transmitter615, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager620may support wireless communications at a UE in accordance with examples as disclosed herein. The downlink control message reception component625may be configured as or otherwise support a means for receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The monitoring component630may be configured as or otherwise support a means for monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The decoding component635may be configured as or otherwise support a means for decoding the transport block based on the monitoring, a number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the set of multiple CCs including the first CC.

FIG.7shows a block diagram700of a communications manager720that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The communications manager720may be an example of aspects of a communications manager520, a communications manager620, or both, as described herein. The communications manager720, or various components thereof, may be an example of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager720may include a downlink control message reception component725, a monitoring component730, a decoding component735, a data rate capability component740, a data rate capability component745, a TCI state component750, a CC configuration component755, a data rate determination component760, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager720may support wireless communications at a UE in accordance with examples as disclosed herein. The downlink control message reception component725may be configured as or otherwise support a means for receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The monitoring component730may be configured as or otherwise support a means for monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The decoding component735may be configured as or otherwise support a means for decoding the transport block based on the monitoring, a number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the set of multiple CCs including the first CC.

In some examples, the data rate capability component740may be configured as or otherwise support a means for transmitting, to the base station, a UE capability message indicating a data rate capability of the UE for the set of multiple CCs including the first CC, where the data rate limit is based on the data rate capability of the UE.

In some examples, the data rate limit is based on a data rate capability of the UE, a number of information bits of the transport block, and the number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC.

In some examples, the TCI state component750may be configured as or otherwise support a means for receiving, from the base station, a message indicating a TCI state for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

In some examples, to support decoding the transport block, the decoding component735may be configured as or otherwise support a means for counting the first transmission occasion and the second transmission occasion separately for a data rate calculation associated with the downlink shared channel in the first CC.

In some examples, to support receiving the downlink control message, the downlink control message reception component725may be configured as or otherwise support a means for receiving the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, where the first transmission occasion and the second transmission occasion are non-overlapping in time.

In some examples, to support receiving the downlink control message, the downlink control message reception component725may be configured as or otherwise support a means for receiving the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, where the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

In some examples, the CC configuration component755may be configured as or otherwise support a means for receiving, from the base station, a message indicating a configuration for the first CC used for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

In some examples, to support decoding the transport block, the decoding component735may be configured as or otherwise support a means for determining a second data rate limit associated with the downlink shared channel for the first CC based on a first number of symbols for the first transmission occasion.

In some examples, the decoding component735may be configured as or otherwise support a means for determining a third data rate limit associated with the downlink shared channel for the first CC based on a second number of symbols for the second transmission occasion.

In some examples, the data rate capability component740may be configured as or otherwise support a means for transmitting, to the base station, a UE capability message indicating a data rate capability of the UE for the first CC, where the data rate limit is based on the data rate capability of the UE.

In some examples, the second data rate limit for the first CC is half of a data rate capability of the UE for the first CC, where the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

In some examples, the data rate determination component760may be configured as or otherwise support a means for determining a respective data rate for each of the first and second transmission occasions based on the second data rate limit for the first CC, where the first CC is configured with an enhanced downlink shared channel processing time.

In some examples, the data rate determination component760may be configured as or otherwise support a means for determining a respective data rate for each of the first and second transmission occasions based at least in part on the second data rate limit for the first CC, where the downlink shared channel is a retransmission of a second downlink shared channel.

In some examples, to support determining the respective data rate, the data rate determination component760may be configured as or otherwise support a means for determining the respective data rate for each of the first and second transmission occasions based on a modulation and coding scheme.

In some examples, the data rate determination component760may be configured as or otherwise support a means for determining a TBS based on the second downlink shared channel.

FIG.8shows a diagram of a system800including a device805that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device805may be an example of or include the components of a device505, a device605, or a UE115as described herein. The device805may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager820, an input/output (I/O) controller810, a transceiver815, an antenna825, a memory830, code835, and a processor840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus845).

The I/O controller810may manage input and output signals for the device805. The I/O controller810may also manage peripherals not integrated into the device805. In some cases, the I/O controller810may represent a physical connection or port to an external peripheral. In some cases, the I/O controller810may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I/O controller810may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller810may be implemented as part of a processor, such as the processor840. In some cases, a user may interact with the device805via the I/O controller810or via hardware components controlled by the I/O controller810.

In some cases, the device805may include a single antenna825. However, in some other cases, the device805may have more than one antenna825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver815may communicate bi-directionally, via the one or more antennas825, wired, or wireless links as described herein. For example, the transceiver815may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver815may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas825for transmission, and to demodulate packets received from the one or more antennas825. The transceiver815, or the transceiver815and one or more antennas825, may be an example of a transmitter515, a transmitter615, a receiver510, a receiver610, or any combination thereof or component thereof, as described herein.

The memory830may include random access memory (RAM) and read-only memory (ROM). The memory830may store computer-readable, computer-executable code835including instructions that, when executed by the processor840, cause the device805to perform various functions described herein. The code835may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code835may not be directly executable by the processor840but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory830may contain, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor840may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor840may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor840. The processor840may be configured to execute computer-readable instructions stored in a memory (e.g., the memory830) to cause the device805to perform various functions (e.g., functions or tasks supporting data rate decoding for transport blocks). For example, the device805or a component of the device805may include a processor840and memory830coupled to the processor840, the processor840and memory830configured to perform various functions described herein.

The communications manager820may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager820may be configured as or otherwise support a means for receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The communications manager820may be configured as or otherwise support a means for monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The communications manager820may be configured as or otherwise support a means for decoding the transport block based on the monitoring, a number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the set of multiple CCs including the first CC.

By including or configuring the communications manager820in accordance with examples as described herein, the device805may support techniques for data rate decoding for transport blocks, which may increase the likelihood of successful reception of a transport block. Such techniques may reduce retransmission associated with a transport block, which may increase network efficiency and reduce power consumption, which may result in increased battery life. Further, the supported techniques may improve network operations through more effective resource usage.

In some examples, the communications manager820may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver815, the one or more antennas825, or any combination thereof. Although the communications manager820is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager820may be supported by or performed by the processor840, the memory830, the code835, or any combination thereof. For example, the code835may include instructions executable by the processor840to cause the device805to perform various aspects of data rate decoding for transport blocks as described herein, or the processor840and the memory830may be otherwise configured to perform or support such operations.

FIG.9shows a block diagram900of a device905that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device905may be an example of aspects of a base station105as described herein. The device905may include a receiver910, a transmitter915, and a communications manager920. The device905may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver910may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). Information may be passed on to other components of the device905. The receiver910may utilize a single antenna or a set of multiple antennas.

The transmitter915may provide a means for transmitting signals generated by other components of the device905. For example, the transmitter915may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). In some examples, the transmitter915may be co-located with a receiver910in a transceiver module. The transmitter915may utilize a single antenna or a set of multiple antennas.

The communications manager920, the receiver910, the transmitter915, or various combinations thereof or various components thereof may be examples of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

Additionally, or alternatively, in some examples, the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager920, the receiver910, the transmitter915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

In some examples, the communications manager920may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver910, the transmitter915, or both. For example, the communications manager920may receive information from the receiver910, send information to the transmitter915, or be integrated in combination with the receiver910, the transmitter915, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager920may support wireless communications at a base station in accordance with examples as disclosed herein. For example, the communications manager920may be configured as or otherwise support a means for receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The communications manager920may be configured as or otherwise support a means for transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel.

By including or configuring the communications manager920in accordance with examples as described herein, the device905(e.g., a processor controlling or otherwise coupled to the receiver910, the transmitter915, the communications manager920, or a combination thereof) may support techniques for data rate decoding for transport blocks, which may reduce power consumption and improve coordination between devices. Further, the supported techniques may improve network operations and promote network efficiencies.

FIG.10shows a block diagram1000of a device1005that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device1005may be an example of aspects of a device905or a base station105as described herein. The device1005may include a receiver1010, a transmitter1015, and a communications manager1020. The device1005may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver1010may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). Information may be passed on to other components of the device1005. The receiver1010may utilize a single antenna or a set of multiple antennas.

The transmitter1015may provide a means for transmitting signals generated by other components of the device1005. For example, the transmitter1015may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to data rate decoding for transport blocks). In some examples, the transmitter1015may be co-located with a receiver1010in a transceiver module. The transmitter1015may utilize a single antenna or a set of multiple antennas.

The device1005, or various components thereof, may be an example of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager1020may include a capability message reception component1025a downlink control message transmission component1030, or any combination thereof. The communications manager1020may be an example of aspects of a communications manager920as described herein. In some examples, the communications manager1020, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver1010, the transmitter1015, or both. For example, the communications manager1020may receive information from the receiver1010, send information to the transmitter1015, or be integrated in combination with the receiver1010, the transmitter1015, or both to receive information, transmit information, or perform various other operations as described herein.

The communications manager1020may support wireless communications at a base station in accordance with examples as disclosed herein. The capability message reception component1025may be configured as or otherwise support a means for receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The downlink control message transmission component1030may be configured as or otherwise support a means for transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel.

FIG.11shows a block diagram1100of a communications manager1120that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The communications manager1120may be an example of aspects of a communications manager920, a communications manager1020, or both, as described herein. The communications manager1120, or various components thereof, may be an example of means for performing various aspects of data rate decoding for transport blocks as described herein. For example, the communications manager1120may include a capability message reception component1125, a downlink control message transmission component1130, a TCI state configuration component1135, a TDM resource allocation component1140, an FDM resource allocation component1145, a CC component1150, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The communications manager1120may support wireless communications at a base station in accordance with examples as disclosed herein. The capability message reception component1125may be configured as or otherwise support a means for receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The downlink control message transmission component1130may be configured as or otherwise support a means for transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel.

In some examples, the TCI state configuration component1135may be configured as or otherwise support a means for transmitting, to the UE, a message indicating a TCI state for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

In some examples, to support transmitting the downlink control message, the TDM resource allocation component1140may be configured as or otherwise support a means for transmitting the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, where the first transmission occasion and the second transmission occasion are non-overlapping in time.

In some examples, to support transmitting the downlink control message, the FDM resource allocation component1145may be configured as or otherwise support a means for transmitting the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, where the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

In some examples, the CC component1150may be configured as or otherwise support a means for transmitting, to the UE, a message indicating a configuration for the first CC used for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

In some examples, the capability message reception component1125may be configured as or otherwise support a means for receiving, from the UE, the UE capability message indicating the data rate capability of the UE for the first CC, where a data rate limit is based on the data rate capability of the UE.

FIG.12shows a diagram of a system1200including a device1205that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The device1205may be an example of or include the components of a device905, a device1005, or a base station105as described herein. The device1205may communicate wirelessly with one or more base stations105, UEs115, or any combination thereof. The device1205may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1220, a network communications manager1210, a transceiver1215, an antenna1225, a memory1230, code1235, a processor1240, and an inter-station communications manager1245. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1250).

The network communications manager1210may manage communications with a core network130(e.g., via one or more wired backhaul links). For example, the network communications manager1210may manage the transfer of data communications for client devices, such as one or more UEs115.

In some cases, the device1205may include a single antenna1225. However, in some other cases the device1205may have more than one antenna1225, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1215may communicate bi-directionally, via the one or more antennas1225, wired, or wireless links as described herein. For example, the transceiver1215may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1215may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1225for transmission, and to demodulate packets received from the one or more antennas1225. The transceiver1215, or the transceiver1215and one or more antennas1225, may be an example of a transmitter915, a transmitter1015, a receiver910, a receiver1010, or any combination thereof or component thereof, as described herein.

The memory1230may include RAM and ROM. The memory1230may store computer-readable, computer-executable code1235including instructions that, when executed by the processor1240, cause the device1205to perform various functions described herein. The code1235may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1235may not be directly executable by the processor1240but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory1230may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor1240may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor1240may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor1240. The processor1240may be configured to execute computer-readable instructions stored in a memory (e.g., the memory1230) to cause the device1205to perform various functions (e.g., functions or tasks supporting data rate decoding for transport blocks). For example, the device1205or a component of the device1205may include a processor1240and memory1230coupled to the processor1240, the processor1240and memory1230configured to perform various functions described herein.

The inter-station communications manager1245may manage communications with other base stations105, and may include a controller or scheduler for controlling communications with UEs115in cooperation with other base stations105. For example, the inter-station communications manager1245may coordinate scheduling for transmissions to UEs115for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communications manager1245may provide an X2interface within an LTE/LTE-A wireless communications network technology to provide communication between base stations105.

The communications manager1220may support wireless communications at a base station in accordance with examples as disclosed herein. For example, the communications manager1220may be configured as or otherwise support a means for receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The communications manager1220may be configured as or otherwise support a means for transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel.

By including or configuring the communications manager1220in accordance with examples as described herein, the device1205may support techniques for data rate decoding for transport blocks, which may reduce power consumption and improve coordination between devices. Further, the supported techniques may improve network operations and promote network efficiencies.

In some examples, the communications manager1220may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1215, the one or more antennas1225, or any combination thereof. Although the communications manager1220is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1220may be supported by or performed by the processor1240, the memory1230, the code1235, or any combination thereof. For example, the code1235may include instructions executable by the processor1240to cause the device1205to perform various aspects of data rate decoding for transport blocks as described herein, or the processor1240and the memory1230may be otherwise configured to perform or support such operations.

FIG.13shows a flowchart illustrating a method1300that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The operations of the method1300may be implemented by a UE or its components as described herein. For example, the operations of the method1300may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1305, the method may include receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The operations of1305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1305may be performed by a downlink control message reception component725as described with reference toFIG.7.

At1310, the method may include monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The operations of1310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1310may be performed by a monitoring component730as described with reference toFIG.7.

At1315, the method may include decoding the transport block based on the monitoring, a number of transmission occasions of the set of multiple transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the set of multiple CCs including the first CC. The operations of1315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1315may be performed by a decoding component735as described with reference toFIG.7.

FIG.14shows a flowchart illustrating a method1400that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The operations of the method1400may be implemented by a UE or its components as described herein. For example, the operations of the method1400may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1405, the method may include receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The operations of1405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1405may be performed by a downlink control message reception component725as described with reference toFIG.7.

At1410, the method may include monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The operations of1410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1410may be performed by a monitoring component730as described with reference toFIG.7.

At1415, the method may include counting the first transmission occasion and the second transmission occasion separately for a data rate calculation associated with the downlink shared channel in the first CC. The operations of1415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1415may be performed by a decoding component735as described with reference toFIG.7.

FIG.15shows a flowchart illustrating a method1500that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The operations of the method1500may be implemented by a UE or its components as described herein. For example, the operations of the method1500may be performed by a UE115as described with reference toFIGS.1through8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

At1505, the method may include receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a set of multiple CCs, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The operations of1505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1505may be performed by a downlink control message reception component725as described with reference toFIG.7.

At1510, the method may include monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based on the downlink control message. The operations of1510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1510may be performed by a monitoring component730as described with reference toFIG.7.

At1515, the method may include determining a second data rate limit associated with the downlink shared channel for the first CC based on a first number of symbols for the first transmission occasion. The operations of1515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1515may be performed by a decoding component735as described with reference toFIG.7.

FIG.16shows a flowchart illustrating a method1600that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The operations of the method1600may be implemented by a base station or its components as described herein. For example, the operations of the method1600may be performed by a base station105as described with reference toFIGS.1through4and9through12. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally, or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.

At1605, the method may include receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The operations of1605may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1605may be performed by a capability message reception component1125as described with reference toFIG.11.

At1610, the method may include transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The operations of1610may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1610may be performed by a downlink control message transmission component1130as described with reference toFIG.11.

FIG.17shows a flowchart illustrating a method1700that supports data rate decoding for transport blocks in accordance with aspects of the present disclosure. The operations of the method1700may be implemented by a base station or its components as described herein. For example, the operations of the method1700may be performed by a base station105as described with reference toFIGS.1through4and9through12. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the described functions. Additionally, or alternatively, the base station may perform aspects of the described functions using special-purpose hardware.

At1705, the method may include receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a set of multiple CCs including a first CC. The operations of1705may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1705may be performed by a capability message reception component1125as described with reference toFIG.11.

At1710, the method may include transmitting, to the UE, a message indicating a TCI state for transmission of a first repetition and a second repetition of a transport block for a downlink shared channel. The operations of1710may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1710may be performed by a TCI state configuration component1135as described with reference toFIG.11.

At1715, the method may include transmitting, to the UE, a downlink control message that schedules the first repetition and the second repetition of the transport block for the downlink shared channel in the first CC of the set of multiple CCs based on the data rate capability of the UE, where the first repetition is scheduled in a first transmission occasion of a set of multiple transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the set of multiple transmission occasions associated with the downlink shared channel. The operations of1715may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1715may be performed by a downlink control message transmission component1130as described with reference toFIG.11.

The following provides an overview of aspects of the present disclosure:

Aspect 1: A method for wireless communications at a UE, comprising: receiving, from a base station, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in a first CC of a plurality of CCs, wherein the first repetition is scheduled in a first transmission occasion of a plurality of transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the plurality of transmission occasions associated with the downlink shared channel; monitoring for the first repetition of the transport block in the first transmission occasion and for the second repetition of the transport block in the second transmission occasion based at least in part on the downlink control message; and decoding the transport block based at least in part on the monitoring, a number of transmission occasions of the plurality of transmission occasions associated with the downlink shared channel in the first CC, and a data rate limit across the plurality of CCs including the first CC.

Aspect 2: The method of aspect 1, wherein decoding the transport block comprises: counting the first transmission occasion and the second transmission occasion separately for a data rate calculation associated with the downlink shared channel in the first CC.

Aspect 3: The method of any of aspects 1 through 2, wherein the data rate limit is based at least in part on a data rate capability of the UE, a number of information bits of the transport block, and the number of transmission occasions of the plurality of transmission occasions associated with the downlink shared channel in the first CC.

Aspect 4: The method of any of aspects 1 through 3, wherein decoding the transport block comprises: determining a second data rate limit associated with the downlink shared channel for the first CC based at least in part on a first number of symbols for the first transmission occasion.

Aspect 5: The method of any of aspect 4, further comprising: transmitting, to the base station, a UE capability message indicating a data rate capability of the UE for the first CC, wherein the data rate limit is based at least in part on the data rate capability of the UE.

Aspect 6: The method of any of aspects 4 through 5, further comprising: determining a third data rate limit associated with the downlink shared channel for the first CC based at least in part on a second number of symbols for the second transmission occasion.

Aspect 7: The method of any of aspects 4 through 6, further comprising: determining a respective data rate for each of the first and second transmission occasions based at least in part on the second data rate limit for the first CC, wherein the first CC is configured with an enhanced downlink shared channel processing time.

Aspect 8: The method of any of aspects 4 through 7, further comprising: determining a respective data rate for each of the first and second transmission occasions based at least in part on the second data rate limit for the first CC, wherein the downlink shared channel is a retransmission of a second downlink shared channel.

Aspect 9: The method of aspect 8, wherein determining the respective data rate comprises: determining the respective data rate for each of the first and second transmission occasions based at least in part on a modulation and coding scheme.

Aspect 10: The method of any of aspects 8 through 9, further comprising: determining a TBS based at least in part on the second downlink shared channel.

Aspect 11: The method of any of aspects 8 through 10, wherein the second data rate limit for the first CC is half of a data rate capability of the UE for the first CC, wherein the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

Aspect 12: The method of any of aspects 1 through 11, wherein receiving the downlink control message comprises: receiving the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, wherein the first transmission occasion and the second transmission occasion are non-overlapping in time.

Aspect 13: The method of any of aspects 1 through 12, wherein receiving the downlink control message comprises: receiving the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, wherein the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

Aspect 4: The method of any of aspects 1 through 3, further comprising: receiving, from the base station, a message indicating a TCI state for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

Aspect 14: The method of any of aspects 1 through 13, further comprising: receiving, from the base station, a message indicating a configuration for the first CC used for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

Aspect 15: The method of any of aspects 1 through 14, wherein the second data rate limit for the first CC is half of the data rate capability of the UE for the first CC, wherein the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

Aspect 16: The method of any of aspects 1 through 15, further comprising: transmitting, to the base station, a UE capability message indicating a data rate capability of the UE for the plurality of CCs including the first CC, wherein the data rate limit is based at least in part on the data rate capability of the UE.

Aspect 17: A method for wireless communications at a base station, comprising: receiving, from a UE, a UE capability message indicating a data rate capability of the UE for a plurality of CCs including a first CC; and transmitting, to the UE, a downlink control message that schedules a first repetition and a second repetition of a transport block for a downlink shared channel in the first CC of the plurality of CCs based at least in part on the data rate capability of the UE, wherein the first repetition is scheduled in a first transmission occasion of a plurality of transmission occasions associated with the downlink shared channel and the second repetition is scheduled in a second transmission occasion of the plurality of transmission occasions associated with the downlink shared channel.

Aspect 18: The method of aspect 17, further comprising: transmitting, to the UE, a message indicating a TCI state for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

Aspect 19: The method of any of aspects 17 through 18, wherein transmitting the downlink control message comprises: transmitting the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, wherein the first transmission occasion and the second transmission occasion are non-overlapping in time.

Aspect 20: The method of any of aspects 17 through 19, wherein transmitting the downlink control message comprises: transmitting the downlink control message indicating the first transmission occasion and the second transmission occasion for the transport block, wherein the first transmission occasion and the second transmission occasion are non-overlapping in frequency.

Aspect 21: The method of any of aspects 17 through 20, further comprising: transmitting, to the UE, a message indicating a configuration for the first CC used for transmission of the first repetition and the second repetition of the transport block for the downlink shared channel.

Aspect 22: The method of any of aspects 17 through 21, further comprising: receiving, from the UE, the UE capability message indicating the data rate capability of the UE for the first CC, wherein a data rate limit is based at least in part on the data rate capability of the UE.

Aspect 23: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 16.

Aspect 24: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 1 through 16.

Aspect 25: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 16.

Aspect 26: An apparatus for wireless communications at a base station, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 17 through 22.

Aspect 27: An apparatus for wireless communications at a base station, comprising at least one means for performing a method of any of aspects 17 through 22.

Aspect 28: A non-transitory computer-readable medium storing code for wireless communications at a base station, the code comprising instructions executable by a processor to perform a method of any of aspects 17 through 22.

It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.

Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A 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 executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

The term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” can include receiving (such as receiving information), accessing (such as accessing data in a memory) and the like. Also, “determining” can include resolving, selecting, choosing, establishing and other such similar actions.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.