Multiplexing transport blocks during code block group based re-transmission
The method addresses the inefficiencies in CBG based re-transmission by multiplexing additional transport blocks during re-transmission, thereby increasing throughput and optimizing bandwidth usage in wireless communication systems.
Patent Information
- Application Number
- PCT/US2024/042545
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-09-13
- Filing Date
- 2024-08-15
- Publication Date
- 2025-03-20
AI Technical Summary
Current wireless communication systems face challenges in efficiently re-transmitting code block groups (CBGs) during code block group based re-transmission, leading to reduced throughput and wasted bandwidth due to the inability to multiplex transport blocks (TBs).
The method involves transmitting a first transmission corresponding to a first transport block (TB) with multiple code block groups (CBGs), obtaining scheduling information for a second transmission, and indicating CBG based re-transmission with TB multiplexing. This allows for the transmission of additional CBGs from a second TB during re-transmission, optimizing bandwidth usage.
By multiplexing additional transport blocks during CBG based re-transmission, the method increases throughput, reduces latency, and optimizes bandwidth utilization, thereby enhancing network performance and user experience.
Smart Images

Figure US2024042545_20032025_PF_FP_ABST
Abstract
Description
MULTIPLEXING TRANSPORT BLOCKS DURING CODE BLOCK GROUP BASED RE-TRANSMISSIONCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of India Patent Application No. 202341061633, entitled, “MULTIPLEXING TRANSPORT BLOCKS DURING CODE BLOCK GROUP BASED RE-TRANSMISSION,” filed on September 13, 2023, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD
[0002] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to code block group (CBG) base re-transmission. Some features may enable and provide improved communications, including transmitting multiple transport blocks (TB) using CBG based re-transmission.INTRODUCTION
[0003] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, and the like. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple access networks that support communications for multiple users by sharing the available network resources.
[0004] A wireless communication network may include several components. These components may include wireless communication devices, such as base stations (or node Bs) that may support communication for a number of user equipments (UEs). A UE may communicate with a base station via downlink and uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station.
[0005] A base station may transmit data and control information on a downlink to a UE or may receive data and control information on an uplink from the UE. On the downlink, a transmission from the base station may encounter interference due to transmissions from neighbor base stations or from other wireless radio frequency (RF) transmitters. On the uplink, a transmission from the UE may encounter interference from uplink transmissionsof other UEs communicating with the neighbor base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.
[0006] As the demand for mobile broadband access continues to increase, the possibilities of interference and congested networks grows with more UEs accessing the long-range wireless communication networks and more short-range wireless systems being deployed in communities. Research and development continue to advance wireless technologies not only to meet the growing demand for mobile broadband access, but to advance and enhance the user experience with mobile communications.BRIEF SUMMARY OF SOME EXAMPLES
[0007] The following summarizes some aspects of the present disclosure to provide a basic understanding of the discussed technology. This summary is not an extensive overview of all contemplated features of the disclosure and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in summary form as a prelude to the more detailed description that is presented later.
[0008] In one aspect of the disclosure, a method of wireless communication includes transmitting a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB. The method also includes obtaining scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing. The method further includes transmitting, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0009] In an additional aspect of the disclosure, an apparatus includes one or more processors; and one or more memories coupled with the one or more processors. The one or more memories storing processor-executable code that, when executed by the one or more processors, is configured to cause the wireless communication device to: transmit a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtain scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and transmit, based on the scheduling information, the secondtransmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0010] In an additional aspect of the disclosure, an apparatus includes: means for transmitting a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; means for obtaining scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and means for transmitting, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0011] In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include to: transmit a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtain scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and transmit, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0012] In another aspect of the disclosure, a method of wireless communication includes receiving a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB. The method also includes obtaining scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing. The method further includes receiving, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0013] In an additional aspect of the disclosure, an apparatus includes one or more processors; and one or more memories coupled with the one or more processors. The one or more memories storing processor-executable code that, when executed by the one or more processors, is configured to cause the wireless communication device to: receive a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtain scheduling information for a second transmission and indicating a CBG based retransmission withTB multiplexing; and receive, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0014] In an additional aspect of the disclosure, an apparatus includes: means for receiving a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; means for obtaining scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and means for receiving, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0015] In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: receiving a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtaining scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and receiving, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
[0016] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
[0017] While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovationsdescribed herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, aspects and / or uses may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (Al)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range in spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, radio frequency (RF)-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders / summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.BRIEF DESCRIPTION OF THE DRAWINGS
[0018] A further understanding of the nature and advantages of the present disclosure may be realized by reference to the following drawings. 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.
[0019] FIG. 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects.
[0020] FIG. 2 is a block diagram illustrating examples of a base station and a user equipment (UE) according to one or more aspects.
[0021] FIG. 3 is a block diagram illustrating an example wireless communication system that supports code block group (CBG) based re-transmission according to one or more aspects.
[0022] FIG. 4 is a block diagram illustrating an example wireless communication system that supports multiplexing transport blocks (TBs) during CBG based re-transmission according to one or more aspects.
[0023] FIG. 5 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0024] FIG. 6 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0025] FIG. 7 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0026] FIG. 8 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0027] FIG. 9 is a block diagram illustrating an example of multiplexing TBs during CBG based re-transmission operations according to one or more aspects.
[0028] FIG. 10 is a table illustrating CBG information for the example multiplexing TBs during CBG based re-transmission operations of FIG. 9.
[0029] FIG. 11 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0030] FIG. 12 is a flow diagram illustrating an example process that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0031] FIG. 13 is a block diagram of an example UE that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0032] FIG. 14 is a block diagram of an example base station that supports multiplexing TBs during CBG based re-transmission according to one or more aspects.
[0033] Like reference numbers and designations in the various drawings indicate like elements.DETAILED DESCRIPTION
[0034] The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to limit the scope of the disclosure. Rather, the detailed description includes specific details for the purpose of providing a thorough understanding of the inventive subject matter. It will be apparent to those skilled in the art that these specific details are not required in every case and that,in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.
[0035] This disclosure relates generally to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communications systems, also referred to as wireless communications networks. In various implementations, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5thGeneration (5G) or new radio (NR) networks (sometimes referred to as “5G NR” networks, systems, or devices), as well as other communications networks. As described herein, the terms “networks” and “systems” may be used interchangeably.
[0036] A CDMA network, for example, may implement a radio technology such as universal terrestrial radio access (UTRA), cdma2000, and the like. UTRA includes wideband- CDMA (W-CDMA) and low chip rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.
[0037] A TDMA network may, for example implement a radio technology such as Global System for Mobile Communication (GSM). The 3rd Generation Partnership Project (3GPP) defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSMZEDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (A interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may comprise one or more GERANs, which may be coupled with UTRANs in the case of a UMTS / GSM network. Additionally, an operator network may also include one or more LTE networks, or one or more other networks. The various different network types may use different radio access technologies (RATs) and RANs.
[0038] An OFDMA network may implement a radio technology such as evolved UTRA (E- UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA, and GSM are part of universalmobile telecommunication system (UMTS). In particular, long term evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rd Generation Partnership Project” (3 GPP), and cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3GPP is a collaboration between groups of telecommunications associations that aims to define a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3 GPP project which was aimed at improving UMTS mobile phone standard. The 3 GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G, or 5G NR technologies; however, the description is not intended to be limited to a specific technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may be related to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.
[0039] 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for 5G NR networks. The 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (loTs) with an ultra-high density (e.g., ~1 M nodes / km2), ultra-low complexity (e.g., -10 s of bits / sec), ultra-low energy (e.g., -10+ years of battery life), and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., -99.9999% reliability), ultra-low latency (e.g., - 1 millisecond (ms)), and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., - 10 Tbps / km2), extreme data rates (e.g., multi - Gbps rate, 100+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.
[0040] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is oftensubdivided, based on frequency or wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” (mmWave) band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “mmWave” band.
[0041] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “mmWave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
[0042] 5G NR devices, networks, and systems may be implemented to use optimized OFDMbased waveform features. These features may include scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD) design or frequency division duplex (FDD) design; and advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust mmWave transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in 5G NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than 3 GHz FDD or TDD implementations, subcarrier spacing may occur with 15 kHz, for example over 1, 5, 10, 20 MHz, and the like bandwidth. For other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, subcarrier spacing may occur with 30 kHz over 80 / 100 MHz bandwidth. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur with 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmittingwith mmWave components at a TDD of 28 GHz, subcarrier spacing may occur with 120 kHz over a 500 MHz bandwidth.
[0043] The scalable numerology of 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs to allow transmissions to start on symbol boundaries. 5G NR also contemplates a self-contained integrated subframe design with uplink or downlink scheduling information, data, and acknowledgement in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink or downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs.
[0044] For clarity, certain aspects of the apparatus and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric way, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.
[0045] Moreover, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to a person having ordinary skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications than the particular examples provided.
[0046] While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, implementations or uses may come about via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail devices or purchasing devices, medical devices, AI- enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range from chip-level or modular components to non- modular, non-chip-level implementations and further to aggregated, distributed, ororiginal equipment manufacturer (OEM) devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described aspects. It is intended that innovations described herein may be practiced in a wide variety of implementations, including both large devices or small devices, chip-level components, multi-component systems (e.g., radio frequency (RF)-chain, communication interface, processor), distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.
[0047] FIG. 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As appreciated by those skilled in the art, components appearing in FIG. 1 are likely to have related counterparts in other network arrangements including, for example, cellular- style network arrangements and non-cellular-style-network arrangements (e.g., device to device or peer to peer or ad hoc network arrangements, etc.).
[0048] Wireless network 100 illustrated in FIG. 1 includes a number of base stations 105 and other network entities. A base station may be a station that communicates with the UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each base station 105 may provide communication coverage for a particular geographic area. In 3GPP, the term “cell” may refer to this particular geographic coverage area of a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of wireless network 100 herein, base stations 105 may be associated with a same operator or different operators (e.g., wireless network 100 may include a plurality of operator wireless networks). Additionally, in implementations of wireless network 100 herein, base station 105 may provide wireless communications using one or more of the same frequencies (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) as a neighboring cell. In some examples, an individual base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.
[0049] A base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allowunrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a pico cell, would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell, such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in the home, and the like). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown in FIG. 1, base stations 105d and 105e are regular macro base stations, while base stations 105a- 105c are macro base stations enabled with one of 3 dimension (3D), full dimension (FD), or massive MIMO. Base stations 105a-105c take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station which may be a home node or portable access point. A base station may support one or multiple (e.g., two, three, four, and the like) cells.
[0050] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, networks may be enabled or configured to handle dynamic switching between synchronous or asynchronous operations.
[0051] UEs 115 are dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be appreciated that, although a mobile apparatus is commonly referred to as a UE in standards and specifications promulgated by the 3 GPP, such apparatus may additionally or otherwise be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, a gaming device, an augmented reality device, vehicular component, vehicular device, or vehicular module, or some other suitable terminology. Within the presentdocument, a “mobile” apparatus or UE need not necessarily have a capability to move, and may be stationary. Some non-limiting examples of a mobile apparatus, such as may include implementations of one or more of UEs 115, include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a laptop, a personal computer (PC), a notebook, a netbook, a smart book, a tablet, and a personal digital assistant (PDA). A mobile apparatus may additionally be an loT or “Internet of everything” (loE) device such as an automotive or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-copter, a quad-copter, a smart energy or security device, a solar panel or solar array, municipal lighting, water, or other infrastructure; industrial automation and enterprise devices; consumer and wearable devices, such as eyewear, a wearable camera, a smart watch, a health or fitness tracker, a mammal implantable device, gesture tracking device, medical device, a digital audio player (e.g., MP3 player), a camera, a game console, etc.; and digital home or smart home devices such as a home audio, video, and multimedia device, an appliance, a sensor, a vending machine, intelligent lighting, a home security system, a smart meter, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, UEs that do not include UICCs may also be referred to as loE devices. UEs 115a-l 15d of the implementation illustrated in FIG. 1 are examples of mobile smart phone-type devices accessing wireless network 100 A UE may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband loT (NB-IoT) and the like. UEs 115e-l 15k illustrated in FIG. 1 are examples of various machines configured for communication that access wireless network 100.
[0052] A mobile apparatus, such as UEs 115, may be able to communicate with any type of the base stations, whether macro base stations, pico base stations, femto base stations, relays, and the like. In FIG. 1, a communication link (represented as a lightning bolt) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink or uplink, or desired transmission between base stations, and backhaul transmissions between base stations. UEs may operate as base stations or other network nodes in some scenarios. Backhaul communication between base stations of wireless network 100 may occur using wired or wireless communication links.
[0053] In operation at wireless network 100, base stations 105a-105c serve UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro base station 105d performs backhaul communications with base stations 105a- 105c, as well as small cell, base station 105f. Macro base station 105d also transmits multicast services which are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
[0054] Wireless network 100 of implementations supports mission critical communications with ultra-reliable and redundant links for mission critical devices, such UE 115e, which is a drone. Redundant communication links with UE 115e include from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) may communicate through wireless network 100 either directly with base stations, such as small cell base station 105f, and macro base station 105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as UE 115f communicating temperature measurement information to the smart meter, UE 115g, which is then reported to the network through small cell base station 105f. Wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i- 115k communicating with macro base station 105e.
[0055] FIG. 2 is a block diagram illustrating examples of base station 105 and UE 115 according to one or more aspects. Base station 105 and UE 115 may be any of the base stations and one of the UEs in FIG. 1. For a restricted association scenario (as mentioned above), base station 105 may be small cell base station 105f in FIG. 1, and UE 115 may be UE 115c or 115d operating in a service area of base station 105f, which in order to access small cell base station 105f, would be included in a list of accessible UEs for small cell base station 105f. Base station 105 may also be a base station of some other type. As shown in FIG. 2, base station 105 may be equipped with antennas 234a through 234t, and UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communications.
[0056] At base station 105, transmit processor 220 may receive data from data source 212 and control information from controller 240, such as a processor. The control informationmay be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, transmit processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor 220 may also generate reference symbols, e.g., for the primary synchronization signal (PSS) and secondary synchronization signal (SSS), and cell-specific reference signal. Transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. For example, spatial processing performed on the data symbols, the control symbols, or the reference symbols may include precoding. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.
[0057] At UE 115, antennas 252a through 252r may receive the downlink signals from base station 105 and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 115 to data sink 260, and provide decoded control information to controller 280, such as a processor.
[0058] On the uplink, at UE 115, transmit processor 264 may receive and process data (e.g., for a physical uplink shared channel (PUSCH)) from data source 262 and control information (e.g., for a physical uplink control channel (PUCCH)) from controller 280. Additionally, transmit processor 264 may also generate reference symbols for a reference signal. The symbols from transmit processor 264 may be precoded by TX MIMO processor 266 ifapplicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to base station 105. At base station 105, the uplink signals from UE 115 may be received by antennas 234, processed by demodulators 232, detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 115. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller 240.
[0059] Controllers 240 and 280 may direct the operation at base station 105 and UE 115, respectively. Controller 240 or other processors and modules at base station 105 or controller 280 or other processors and modules at UE 115 may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated in FIGS. 1-14, or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or the uplink.
[0060] In some cases, UE 115 and base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) frequency spectrum. In an unlicensed frequency portion of the shared radio frequency spectrum band, UEs 115 or base stations 105 may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum. For example, UE 115 or base station 105 may perform a listen-before-talk or listen-before-transmitting (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available. In some implementations, a CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied. Specifically, signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. A CCA also may include detection of specific sequences that indicate use of the channel. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel or the acknowledge / negative-acknowledge (ACK / NACK) feedback for its own transmitted packets as a proxy for collisions.
[0061] FIG. 3 illustrates a ladder diagram 300 illustrating an example of code block group (CBG)based re-transmission. The wireless communications system of FIG. 3 may include a network, such as one or more network entities, and one or more UEs, such as UE. As illustrated in the example of FIG. 4, the network entity includes a corresponds to a base station, such as base station 105. Alternatively, the network entity may include or correspond to a different network device (e.g., not a base station), such as another UE.
[0062] During operation, the base station 105 and UE 115 may communicate wirelessly to transmit data. For example, the base station 105 may send downlink data to the UE 115 using CBGs. Occasionally, the UE 115 may not successfully receive each CBG of the transmitted CBGs due to interference, noise, errors, etc. The base station 105 may retransmits the CBGs to as illustrated in FIG. 3.
[0063] At 310, the base station 105 transmits a PDSCH to the UE 115 including multiple CBGs for a single transport block (TB). Alternatively, the PDSCH include multiple CBGs for multiple TBs.
[0064] At 315, the UE receives the PDSCH, determines which CBGs it successfully decoded, and transmits acknowledgement information for the PDSCH indicating which CBGs of the TB it successfully received and decoded. In this example, the UE 115 decoded less than all CBGs of the TB.
[0065] At 320, the base station 105 receives acknowledgement information and determines to retransmit the PDSCH, and the base station 105 transmits a DCI including scheduling information for a re-transmission of the PDSCH, or at least a portion of the PDSCH.
[0066] At 325, the base station 105 transmits a second PDSCH (a retransmission) to the UE 115. The second PDSCH (retransmission) may include each of the same CBGs as the PDSCH for the single TB, i.e., a full re-transmission. Alternatively, the second PDSCH (retransmission) may not include the successfully received and decoded CBGs of the PDSCH and only includes the CBGs of the PDSCH which were not successfully received and decoded. In such implementations where the base station 105 transmits less CBGs, the base station 105 may lower the code rate to transmit the second PDSCH (retransmission) in the same physical resources or may use fewer physical resources. This results in wasted bandwidth and network overhead.
[0067] The base station 105 may not include additional TBs in the second PDSCH that were not in the PDSCH. For example, the base station 105 may not include new CBGs for new TBs for the successfully received and decoded CBGs of the PDSCH. To illustrate, the base station 105 may not have any capability to signal it is adding a new TB and which CBGs correspond to which TB. Additionally, the UE 115 may not have any capabilityfor acknowledging CBGs for different TBs sent by the base station 105.
[0068] At 330, the UE receives the second PDSCH, determines which CBGs it successfully decoded, and transmits acknowledgement information for the second PDSCH indicating which CBGs is successfully received and decoded. In this example, the UE 115 decoded less than all CBGs.
[0069] At 335, the base station 105 receives acknowledgement information and determines to retransmit the second PDSCH, and the base station 105 transmits a DCI including scheduling information for a re-transmission of the second PDSCH, or at least a portion of the second PDSCH. In some implementations, this may include a second retransmission of the PDSCH or a retransmission of the second PDSCH.
[0070] At 340, the base station 105 transmits a third PDSCH (second retransmission) to the UE 115. When the UE 115 receives additional CBGs for the transmitted TB in the second PDSCH that it did not receive in PDSCH, but less than all CBGs of the TB, the UE 115 may require yet another retransmission, the third PDSCH, to attempt to receive all of the CBGs of the TB. However, the UE 115 may have successfully received multiple CBGs of the TB one or more times during these retransmissions. This retransmission of successfully received CBGs reduces throughput and wastes bandwidth.
[0071] In the aspects described herein, CBG based re-transmission may be enhanced by adding support for TB multiplexing during CBG based re-transmission. That is, a throughput of CBG based retransmission can be increased by multiplexing additional TBs (such as CBGs thereof) when CBGs of previously sent TBs are received. Accordingly, bandwidth reuse is reduced, and overall throughput is increased.
[0072] In the techniques described herein, scheduling and acknowledgment schemes for supporting TB multiplexing during CBG based re-transmission are disclosed along with operations for determining when and how to add additional TBs to CBG based retransmission.
[0073] FIG. 4 illustrates an example of a wireless communications system 400 that supports enhanced CBG re-transmission operations in accordance with aspects of the present disclosure. In some examples, wireless communications system 400 may implement aspects of wireless network 100. For example, wireless communications system 400 may include a network, such as one or more network entities, and one or more UEs, such as UE 115. As illustrated in the example of FIG. 4, the network entity includes a corresponds to a base station, such as base station 105. Alternatively, the network entity may include or correspond to a different network device (e.g., not a base station). Enhanced CBG re-transmission operations may reduce latency and increase throughput. For example, multiplexing TBs during CBG based re-transmission reduces latency and increases throughput by transmitting additional CBGs of additional TBs instead of retransmitting received CBGs or transmitting unreceived CBGs with a reduced code rate. Accordingly, network and device performance can be increased.
[0074] Base station 105 and UE 115 may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5GNRtwo initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “mmWave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “mmWave” band.
[0075] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “mmWave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.
[0076] It is noted that SCS may be equal to 15, 30, 60, or 120 kHz for some data channels. Base station 105 and UE 115 may be configured to communicate via one or more component carriers (CCs), such as representative first CC 481, second CC 482, third CC 483, and fourth CC 484. Although four CCs are shown, this is for illustration only, more or fewer than four CCs may be used. One or more CCs may be used to communicate control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.
[0077] Such transmissions may include a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), a Physical Uplink Control Channel (PUCCH), a Physical Uplink Shared Channel (PUSCH), a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), or a Physical Sidelink Feedback Channel (PSFCH). Such transmissions may be scheduled by aperiodic grantsand / or periodic grants.
[0078] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. The periodic grant configuration may include configured grant (CG) configurations and settings. Additionally, or alternatively, one or more periodic grants (e.g., CGs thereof) may have or be assigned to a CC ID, such as intended CC ID.
[0079] Each CC may have a corresponding configuration, such as configuration parameters / settings. The configuration may include bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally, or alternatively, one or more CCs may have or be assigned to a Cell ID, or a Bandwidth Part (BWP) ID. The Cell ID may include a unique cell ID for the CC, a virtual Cell ID, or a particular Cell ID of a particular CC of the plurality of CCs. Additionally, or alternatively, one or more CCs may have or be assigned to a HARQ ID. Each CC may also have corresponding management functionalities, such as, beam management or BWP switching functionality. In some implementations, two or more CCs are quasi co-located, such that the CCs have the same beam and / or same symbol.
[0080] In some implementations, control information may be communicated via base station 105 and UE 115. For example, the control information may be communicated suing MAC- CE transmissions, RRC transmissions, DCI (downlink control information) transmissions, UCI (uplink control information) transmissions, SCI (sidelink control information) transmissions, another transmission, or a combination thereof.
[0081] UE 115 can include a variety of components (e.g., structural, hardware components) used for carrying out one or more functions described herein. For example, these components can include processor 402, memory 404, transmitter 410, receiver 412, encoder, 413, decoder 414, CBG manager 415, re-transmission manager 416, and antennas 252a-r. Processor 402 may be configured to execute instructions stored at memory 404 to perform the operations described herein. In some implementations, processor 402 includes or corresponds to controller / processor 280, and memory 404 includes or corresponds to memory 282. Memory 404 may also be configured to store scheduling information 406, acknowledgment information 408, CBG information 442, CBG re-transmission information 444, settings data, or a combination thereof, as further described herein.
[0082] The scheduling information 406 includes or corresponds to data associated with or corresponding to scheduling one or more transmissions, such as one or more CBG based re-transmissions with multiple TBs. For example, the scheduling information 406 mayinclude resource allocation data and timing information data for CBG based transmissions or CBG based re-transmissions. The scheduling information 406 may include data indicating and / or allocating resources for the CBGs of the transmission or re-transmission and additional CBG indication information for which CBG corresponds to which TB, such as CBG to TB mapping information.
[0083] The CBG indication information may include information to identify a corresponding TB for each CBG. As an illustrative example, the CBG indication information may indicate a number or amount of TBs (e.g., 1, 2, 3, 4, etc.) and indicate transmitted CBGs for each TB (e.g., valid CBGs). To illustrate, the CBG indication could be a variable bitmap based on the TB size and CBG size, which indicates the valid CBGs for each TB.
[0084] The resource allocation information may include or correspond to information associated with or corresponding to indicating resources of the bandwidth allocated for a particular transmission (or transmissions) in a slot. For example, the resource allocation information may include resource element data. The resource element (RE) data may include data on physical layer resource elements, such as resource blocks or groups thereof, for the valid CBGs.
[0085] The timing information may include or correspond to information associated with or corresponding to indicating a timing of the transmission, such as an offset from the current transmission to the scheduled transmission. The carrier information (carrier configuration information) may include RBG size information, transmission type information, slot type information, channel bandwidth information, frequency band information, SCS information, bandwidth part (BWP) information, etc.
[0086] The acknowledgement information 408 includes or corresponds to data associated with or corresponding to acknowledgement indications for CBGs of multiplexed TBs during CBG based re-transmission. For example, the acknowledgement information 408 may include acknowledgement indications for each CBG included in the transmission (or retransmission), or for each potential CBG of the transmission (or re-transmission). To illustrate, the acknowledgement information 408 may include positive acknowledgement indications for received CBGs and negative acknowledgement indications for invalid or not received CBGs.
[0087] In some implementations, the acknowledgement information 408 includes data for all potential CBGs, even invalid or not used / sent CBGs. Potential CBGs may include or correspond to TBs which could be sent, such as when multiple TBs are sent. To illustrate, when to TBs are sent and 4 CBGs are used, an amount of the potential CBGs that couldbe sent is eight, four for the first TB and four for the second TB . Thus, there are 8 potential CBG and TB combinations. However, only four of these combinations may be valid or actually sent. The other four unused or unset combinations of CBG and TBs may be referred to as invalid CBGs.
[0088] The CBG information 442 includes or corresponds to data indicating or corresponding to CBG allocations and / or configuration. For example, the CBG information 442 may include or correspond to CBG configuration data and / or code block (CB) configuration data, and may include CBG association data for associating CBGs with TBs (e.g., CBG mapping information).
[0089] The CBG configuration information may include CB size information, CBG size information, or both. The CB size information may indicate a size of each CB of the CBG, such as by amount of REs, an amount of bits, an amount of coded bits, etc. The CBG size information may indicate an amount of CBs per CBG, a size of the CBG, such as by amount of REs, an amount of bits, an amount of coded bits, etc., or a combination thereof. To illustrate, the CBG size information may be indicated by an amount of information bits (e.g., a K value) or an amount of transmission or coded bits (e.g., an E value) for each CB or CBG. As another illustration, the CBG size information may be indicated by a TBS value (e.g., value of bits for all CBGs) and an amount of CBs or CBGs.
[0090] Additionally, or alternatively, the CBG information 442 may include CBG configuration information for different frequency spectrums, such as LTE, 5G, FR1, FR2, terrestrial broadcast, etc., for different operating modes, uplink, downlink, sidelink, or a combination thereof. Such settings may be used to determine an amount of resources for each CBG, such as for each CB thereof.
[0091] The CBG information 442 may further include CBG transmission information (CBGTI), CBG flushing out information (CBGFI), or both. The CBGTI and CBGFI may be indicated in a control channel transmission or DCI, such as by scheduling information 406 thereof. The CBGTI and CBGFI may enable a device to determine valid CBGs and / or if additional CBGs have been added, such as if a new TB has been multiplexed.
[0092] The CBG re-transmission information 444 includes or corresponds to data associated with enhanced CBG re-transmission operations. The CBG re-transmission information 444 may include one or more thresholds or conditions for determining to use CBG retransmission data for multiple transmissions or for multiplexing TBs during CBG based re-transmission. For example, the CBG re-transmission information 444 may have dataindicating different thresholds and / or conditions for when to add an additional TB or TBs, when to not add an additional TB, when to re-transmit the previous transmission, when to re-transmit a portion of the previous transmission and adjust the code rate, or a combination thereof. Additionally, the CBG re-transmission information 444 may have data indicating a different thresholds or operating conditions for multiplexing TBs, such as a maximum amount of TBs, a maximum amount of CBGs, a minimum amount of CBGs per TB, a maximum codeword amount, a minimum amount of received CBGs, etc.
[0093] The settings data includes or corresponds to data associated with enhanced CBG based re-transmission operations. The settings data may include one or more types of enhanced CBG based re-transmission operation modes and / or thresholds or conditions for switching between enhanced CBG based re-transmission modes and / or configurations thereof. For example, the settings data may have data indicating different thresholds and / or conditions for different enhanced CBG based re-transmission modes, such as uplink modes, downlink mode, sidelink modes, or a combination thereof.
[0094] Transmitter 410 is configured to transmit data to one or more other devices, and receiver 412 is configured to receive data from one or more other devices. For example, transmitter 410 may transmit data, and receiver 412 may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, UE 115 may be configured to transmit and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to- modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter 410 and receiver 412 may be replaced with a transceiver. Additionally, or alternatively, transmitter 410 or receiver, 412 may include or correspond to one or more components of UE 115 described with reference to FIG. 2.
[0095] Encoder 413 and decoder 414 may be configured to encode and decode data for transmission. CBG manager 415 may be configured to perform enhanced CBG based retransmissions operations, such as multiplexing TBs for CBG based re-transmissions. For example, CBG manager 415 may be configured to determine and / or indicate valid CBGs for a particular transmission and which CBGs correspond to which TB, that is a CBG association information or CBG mapping information. To illustrate, the CBG manager 415 may determine which CBGs are actually included in a particular transmission (thevalid CBGs) based on the scheduling information 406, such as bitmap or indicators thereof.
[0096] In some implementations, the CBG manager 415 determines resources for each valid CBG. For example, the CBG manager 415 may determines which code blocks correspond to or are associated with the valid CBGs and determine a size of each code block and CBG. To illustrate, the CBG manager 415 determines a size of each code block (and CBG) in terms of one or more of K, E, or TBS.
[0097] Re-transmission manager 416 may be configured to perform enhanced CBG based retransmissions operations, such as multiplexing TBs for CBG based re-transmissions. For example, the re-transmission manager 416 may be configured to determine to perform a retransmission and whether to add or multiplex one or more new or additional TBs (as compared to a previous transmission) for the upcoming re-transmission of at least a portion of the previous transmission. To illustrate, the re-transmission manager 416 may determine to add one or more TBs to a next re-transmission based on the acknowledgment information 408 and / or the scheduling information 406.
[0098] Base station 105 includes processor 430, memory 432, transmitter 434, receiver 436, encoder 437, decoder 438, CBG manager 439, re-transmission manager 440, and antennas 234a-t. Processor 430 may be configured to execute instructions stores at memory 432 to perform the operations described herein. In some implementations, processor 430 includes or corresponds to controller / processor 240, and memory 432 includes or corresponds to memory 242. Memory 432 may be configured to store scheduling information 406, acknowledgement information 408, CBG information 442, CBG retransmission information 444, settings data, or a combination thereof, similar to the UE 115 and as further described herein.
[0099] Transmitter 434 is configured to transmit data to one or more other devices, and receiver 436 is configured to receive data from one or more other devices. For example, transmitter 434 may transmit data, and receiver 436 may receive data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, UEs and / or base station 105 may be configured to transmit and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter 434 andreceiver 436 may be replaced with a transceiver. Additionally, or alternatively, transmitter 434 or receiver, 436 may include or correspond to one or more components of UE 115 described with reference to FIG. 2.
[0100] Encoder 437, and decoder 438 may include the same functionality as described with reference to encoder 413 and decoder 414, respectively. CBG manager 439 may include similar functionality as described with reference to CBG manager 415. For example, the CBG manager 439 may be configured to determine CBGs for multiple TBs for CBG based retransmission. Re-transmission manager 440 may include similar functionality as described with reference to re-transmission manager 416. For example, the retransmission manager 440 may be configured to transmit and receive re-transmissions with multiple TBs during CBG based retransmission.
[0101] During operation of wireless communications system 400, the network (e.g., base station 105) may determine that UE 115 has enhanced CBGbased retransmission capability. For example, UE 115 may transmit a message 448 that includes an enhanced CBG based retransmission indicator 490 (e.g., a multiplexing TB during CBG based retransmission capability indicator). Indicator 490 may indicate enhanced CBG based retransmission capability for one or more communication modes, such as downlink, uplink, etc. In some implementations, a network entity (e.g., a base station 105) sends control information to indicate to UE 115 that enhanced CBGbased retransmission operation and / or a particular type of enhanced CBG based retransmission operation is to be used. For example, in some implementations, configuration transmission 450 is transmitted to the UE 115. The configuration transmission 450 may include or indicate to use enhanced CBG based retransmission operations or to adjust or implement a setting of a particular type of enhanced CBG based retransmission operation. For example, the configuration transmission 450 may include scheduling information 406, acknowledgement information 408, as indicated in the example of FIG. 4, CBG information 442, settings data or any combination thereof.
[0102] During operation, devices of wireless communications system 400, perform enhanced CBG based retransmission operations. For example, the network and UE 115 may communicate retransmissions using CBGs to multiple TBs via uplink and / or downlink communications as illustrated in the example of FIG. 4. This enhanced CBG based retransmission capability and flexibility enables devices to adjust resources and increase throughput by taking advantage of received CBGs to send additional CBGs of additional TBs instead of repeating received CBGs for another / current TB or reducing a code rate.
[0103] In the example of FIG. 4, the base station 105 transmits a first transmission 452 to the UE 115 via a downlink channel. For example, the base station 105 transmits a first PDSCH to the UE 115 via a downlink channel, the first PDSCH including one or more CBGs for one more TBs. The first transmission 452 corresponds to a downlink message in the example of FIG. 4. In other implementations, the first transmission 452 may include or correspond to a PUSCH or a PSSCH, as described further with reference to FIGS. 6 and 7.
[0104] The UE 115 receives the first transmission 452 and attempts to decode the first transmission 452. For example, the UE 115 determines valid CBGs of the first transmission 452 based on prior received scheduling information (e.g., scheduling information 406). The scheduling information is received in prior signaling (not shown, e.g., a prior control channel transmission, such as a second control channel transmission similar to control channel transmission 456). The UE 115 then attempts to decode the determined valid CBGs. The valid CBGs may include or correspond to a single TB, or to multiple CBGs, such as when the first transmission 452 is a CBG based retransmission with TB multiplexing. The UE 115 may successful decode one or more of the determined valid CBGs. For example, UE 115 may successfully decode some CBGs of the valid CBGs and may not decode other CBGs of the valid CBGs, such as due to interference, noise, or other errors.
[0105] The UE 115 generates acknowledgement information based on decoding the CBGs. For example, the UE 115 generates acknowledgement information including positive acknowledgement indications (ACKs) for received and decoded CBGs, and including negative acknowledgement indications (NACKs) for the invalid CBGs, the not successfully decoded valid CBGs, or both. To illustrate, the UE 115 may indicate a value of 1 for all valid CBGs received and value of 0 for all valid CBGs not received. When the CBGs correspond to multiple TBs, the UE 115 may provide these indications on a per CBG and TB basis. As an illustrative example, when four CBGs are sent for two TBs with two CBGs per each TB, the acknowledgement information may include 8 indications (4x2), that is 4 CBG indications for the first TB and 4 CBG indications for the second TB.
[0106] The UE 115 transmits acknowledgement information 454 to the base station 105 via an uplink channel. For example, the UE 115 transmits a PUCCH to the base station 105 via an uplink channel, the PUCCH including acknowledgement information 454 for the first transmission 452. The acknowledgement information 454 corresponds to an uplinkmessage in the example of FIG. 4, such as a UCI or other control channel message. In other implementations, the control channel transmission 456 may include or correspond to a PDCCH or a PSCCH. Alternatively, in some other implementations, such as uplink, the scheduling device (e.g., base station 105) may already have the acknowledgement information 454 and no transmission for the acknowledgement information 454 may be needed. The acknowledgement information 454 may include or correspond to the acknowledgement information 408 or a portion thereof.
[0107] The base station 105 transmits control channel transmission 456 to the UE 115 via a downlink channel. For example, the base station 105 transmits a DCI to the UE 115 via the downlink channel, the DCI including scheduling information for a second transmission 458 (e.g., a retransmission of the first transmission 452). The retransmission includes multiple CBGs for multiple TBs.
[0108] The base station 105 transmits the second transmission 458 to the UE 115 via a downlink channel. For example, the base station 105 transmits a second PDSCH to the UE 115 via the downlink channel, the second PDSCH including one or more CBGs for multiple TBs. The second transmission 458 corresponds to a downlink message in the example of FIG. 4. In other implementations, the second transmission 458 may include or correspond to a PUSCH or a PSSCH.
[0109] The transmission of the second transmission 458 by the base station 105 may be based on the received acknowledgement information 454 and the control channel transmission 456. For example, the base station 105 transmits the second transmission 458 based on the identified CBGs from the acknowledgement information 454, which may be indicated in the control channel transmission 456. To illustrate, the base station 105 may transmit the second transmission 458 using the specific CBGs identified by CBG mapping information in the control channel transmission 456 for each TB. The CBGs may be identified by an indicator or bitmap indicated by scheduling information of the control channel transmission 456.
[0110] The UE 115 monitors for the second transmission 458 based on the control channel transmission 456, such as scheduling information and / or CBG information thereof. The may UE 115 receive the second transmission 458 and successfully decoded one or more CBGs of the second transmission 458. If the UE 115 successfully decodes all CBGs, the retransmission operations may stop, and a new transmission may be scheduled and communicated. Alternatively, even if all CBGs are received, the base station 105 may engage in one or more CBG based retransmissions to transmit remaining (e.g., unsent)CBGs of the TBs of the second transmission 458.
[0111] Although a single retransmission is illustrated in the example of FIG. 5, the UE 115 and base station 105 may engage in multiple CBG based retransmissions for multiplexing TBs, as described further with reference to FIGS. 5-10. For example, the base station 105 may transmit additional downlink transmissions (e.g., a third downlink transmission) based on second acknowledgement information (similar to acknowledgement information 454) for the second transmission 458. Additionally, or alternatively, the UE 115 may engage in multiple CBG based retransmissions for multiplexing TBs by transmitting transmissions to the base station 105 or another UE. Example operations for uplink and sidelink CBG based retransmissions for multiplexing TBs are illustrated and described with reference to FIGS. 6 and 7.
[0112] Accordingly, the network (e.g., the base station 105 and the UE 115) may be able to more efficiently and effectively make use of available spectrum by using more of the available spectrum through multiplexing TBs during CBG based re-transmission. Improved spectrum utilization through enhanced CBG based re-transmission operations may increase throughput and reduce latency, which may lead to reduced link failures. Accordingly, the network performance and experience may be increased due to the increases in speed and reductions in failure.
[0113] Referring to FIG. 5, FIG. 5 is a timing diagram 500 illustrating a wireless communication system that supports multiplexing TBs during CBG based re-transmission according to one or more aspects. The example of FIG. 5 corresponds to an example of transmitting multiple TBs during CBG based re-transmissions for downlink operations.
[0114] The example of FIG. 5 includes similar devices to the devices described in FIGS. 1, 2, and 4, such as a UE 115 and a network entity (e.g., base station 105). The devices of FIG. 5 may include one or more of the components as described in FIGS. 2 and 4. In FIG. 5, these devices may utilize antennas 252a-r, transmitter 410, receiver 412, encoder 413 and / or decoder 414, or may utilize antennas 234a-t, transmitter 434, receiver 436, encoder 437 and / or decoder 438 to communicate and receive transmissions in accordance with multiplexed TB CBG based retransmissions. In some implementations, network entity may include or correspond to multiple TRPs of a single base station (e.g., base station 105), to multiple base stations, or any combination thereof.
[0115] At 510, the base station 105 and the UE 115 optionally perform capability operations (e.g., multiplexing TBs with CBG based re-transmission capability operations). For example, the base station 105, the UE 115, or both, communicate capability information(e.g., multiplexing TBs with CBG based re-transmission capability information) to enable multiplexing TBs during CBG based re-transmissions.
[0116] To illustrate, the UE 115 transmits capability information to the base station 105. For example, the UE 115 may transmit an uplink transmission including capability information, such as transmit RRC signaling (e.g., a RRC transmission or message), including the capability information, to the base station 105. As described with reference to FIG. 4, the capability information may include or indicate one or more capabilities or parameters for multiplexing TBs during CBG based re-transmission, such as thresholds for amount of TBs, amount of CBGs, amount of code words, applicable communication modes for multiplexing TBs, etc.
[0117] The base station 105 may receive the capability information and determine configuration information. For example, the base station 105 may receive and parse the transmission at 510 from the UE 115 to determine the capability information. The base station 105 may detention configuration information based on the capability information. As described with reference to FIG. 4, the configuration information may include or indicate one or more configurations or parameters for multiplexing TBs during CBG based retransmission, such as thresholds for an amount of TBs, an amount of CBGs, or an amount of code words, applicable communication modes for multiplexing TBs, etc.
[0118] At 515, the base station 105 and the UE 115 optionally perform configuration operations (e.g., multiplexing TBs with CBG based re-transmission configuration operations). For example, the base station 105, the UE 115, or both, communicate configuration information (e.g., multiplexing TBs with CBG based re-transmission configuration information) to enable multiplexing TBs during CBG based re-transmissions.
[0119] To illustrate, the base station 105 transmits configuration information to the UE 115. For example, the base station 105 may transmit a downlink transmission including configuration information, such as transmit RRC signaling (e.g., a RRC transmission or message), including the configuration information, to the UE 115.
[0120] At 520, the base station 105 transmits a signaling indication including scheduling information (e.g., CBG indication information) for a downlink transmission. For example, the base station 105 may transmit the scheduling information in a downlink control channel transmission. As illustrated in the example of FIG. 5, the base station transmits a DCI including the scheduling information, such as the scheduling information 406 of FIG 4, and optionally CBG information (e.g., 442). In other implementations, the base station 105 may transmit a PDCCH, a MAC CE, a RRC, or another type oftransmission. The scheduling information may include or correspond to the scheduling information described with reference to FIG. 4. For example, the scheduling information may include or indicate a bitmap for CBG identification and / or CBG mapping to multiple TBs.
[0121] At 525, the UE 115 may determine timing and resource allocation information based on receiving the scheduling information at 520 and optionally based on configuration information. For example, the UE 115 may receive and parse the signaling indication (signaling transmission) to determine or identify scheduling information. As illustrated in the example of FIG. 5, the UE 115 receives a DCI including an indication for a particular transmission at a particular time and using particular resources.
[0122] The UE 115 determines valid CBGs for the upcoming downlink transmission scheduled by the signaling indication based on the scheduling information, such as based on CBG mapping information. For example, the UE 115 may determine that scheduled downlink transmission includes 8 CBGs for a particular TB (first TB) based on CBG indication information, TB indication information, or a commotion thereof.
[0123] At 530, the base station 105 transmits a downlink data transmission to the UE 115 based on the scheduling information. For example, the base station 105 transmits a first PDSCH to the UE 115 based on the scheduling information, as illustrated in the example of FIG. 5. In other implementations, data transmission may be an uplink or sidelink transmission, such as PUSCH or PSSCH, as described further with reference to FIGS. 6 and 7.
[0124] At 535, the UE 115 receives the downlink transmission and attempts to decode the determined valid CBGs of the downlink transmission. For example, the UE 115 may monitor for the first PDSCH based on the scheduling information of the DCI, and may attempt to decode the valid CBGs of the PDSCH based on the DCI (e.g., CBG information of the DCI). To illustrate, the UE 115 may decode the valid CBGs of the DCI based on a CBGTI field.
[0125] In the example of FIG. 5, the UE 115 may successfully receive of portion of the CBGs of the first PDSCH, and may not be able to decode one or more valid CBGs of the first PDSCH. The UE 115 may generate acknowledgment information (e.g., 408 or 454) for the first PDSCH based on successfully receiving the CBGs thereof. For example, the UE 115 may generate acknowledgment information for each of the 8 CBGs of the TB.
[0126] At 540, the UE 115 transmits the acknowledgment information for the first PDSCH to the base station 105. For example, the UE 115 may transmit the HARQ feedback information for the first PDSCH in a UCI or PUCCH. The acknowledgment information (HARQfeedback information) may include positive acknowledgments for the decoded CBGs and negative acknowledgments for the CBGs that were not decoded.
[0127] At 545, the base station 105 receives the acknowledgment information and determines the received CBGs for the downlink transmission. For example, the base station 105 receives the acknowledgment information in a UCI and determines that less than all 8 CBGs of the particular TB were received by the UE 115. The base station 105 may determine to engage in CBG based retransmission based on less than all CBGs being received. Based on determining to engage in CBG based retransmission, base station 105 and UE 115 perform one or more operations as described with reference to 550-565.
[0128] Additionally, when configured with TB multiplexing for CBG re-transmission, the base station 105 may determine to include one or more new TBs in the upcoming retransmission for the first PDSCH at or after 545. For example, the base station 105 may determine to include at least one other TB in a re-transmission of or for the first PDSCH based on or more TB multiplexing conditions, such as based on how many CBGs of the first PDSCH were not received, how many TBs were transmitted in the first PDSCH, or a combination thereof. Additionally, the base station 105 may determine to include a TB in the re-transmission based on a size of available TBs for transmission. In some such implementations where the base station 105 has multiple TBs available to add to the retransmission, the base station 105 may select a particular TB or TBs of the multiple available TBs based on an amount of available TBs for the upcoming re-transmission (e.g., how many CBGs of the first PDSCH were successfully received).
[0129] At 550, the base station 105 transmits a second control channel transmission for a second downlink transmission corresponding to a retransmission of the first downlink transmission with a multiplexed TB. For example, the base station 105 generates second scheduling information for a second PDSCH based on the acknowledgement information and transmits the second scheduling information in a second DCI, similar to as described with reference to the DCI at 515.
[0130] At 555, the base station 105 transmits a second downlink data transmission to the UE 115 based on the second scheduling information. For example, the base station 105 transmits a second PDSCH to the UE 115 based on the second scheduling information, as illustrated in the example of FIG. 5. In other implementations, the second downlink data transmission may be an uplink or sidelink transmission, such as PUSCH or PSSCH, as described further with reference to FIGS. 6 and 7. The second downlink data transmission (second PDSCH) includes some of the original 8 CBGs for the particular TB and includesone or more CBGs for a second TB. Additionally, the second PDSCH may include one or more CBGs for one or more additional TBs, such as a third TB. The base station 105 may change a CBG order of the re-transmitted CBGs for the particular CBG used for the first PDSCH when transmitting the second PDSCH. To illustrate, the base station 105 may reorder the CBGs to group the CBGs of each TB together for the second PDSCH.
[0131] After 555, the UE 115 receives the second downlink transmission and attempts to decode the determined valid CBGs of the second downlink transmission. For example, the UE 115 may monitor for the second PDSCH based on the second scheduling information of the second DCI, and may attempt to decode the valid CBGs of the second PDSCH based on the second DCI (e.g., second CBG information of the second DCI). To illustrate, the UE 115 may decode the valid second CBGs of the second DCI based on second CBGTI fields for each TB included in the second PDSCH.
[0132] In the example of FIG. 5, the UE 115 may successfully receive of a portion of the second CBGs of the second PDSCH, and may not be able to decode one or more valid second CBGs of the second PDSCH. The UE 115 may generate second acknowledgment information for the second PDSCH based on successfully receiving the second CBGs thereof. For example, the UE 115 may generate second acknowledgment information for a total amount of transmitted CBGs (e.g., 8 CBGs) for each TB transmitted in the second PDSCH. To illustrate, if 8 CBGs are transmitted and correspond to 3 TBs, the UE 115 may generate acknowledgment indications for 24 CBGs, 8 CBGs for each of the 3 TBs for the second acknowledgment information. However, of the 24 acknowledgement indications for the second acknowledgment information, only 8 may correspond actual, valid CBGs, transmitted CBGs.
[0133] At 560, the UE 115 transmits the second acknowledgment information for the second PDSCH to the base station 105. For example, the UE 115 may transmit the HARQ feedback information for the first PDSCH in a UCI or PUCCH. The second acknowledgment information (HARQ feedback information) may include positive acknowledgments for the decoded second CBGs and negative acknowledgments for the second CBGs that were not decoded.
[0134] Optionally, the UE 115 and base station 105 may perform one or more additional CBG based re-transmissions operations at 565. For example, the UE 115 and the base station 105 may perform similar steps 540-560 to communicate one or more second retransmissions (e.g., re-transmissions of the unreceived second CBGs of second PDSCH and any unsent CBGs for the added / multiplexed TB). An example of multiplexingmultiple TBs of multiple transmission is described further with reference to FIG. 9.
[0135] Accordingly, in the example, of FIG. 5, devices of the network may be able to have a more flexible utilization of CBG based re-transmission through the use a CBG to TB mapping to multiplex CBGs of additional TBs with unsuccessfully decoded CBGs from a prior transmission. Multiplexing TBs for CBG re-transmissions increases throughput and reduced latency by increasing bandwidth utilization and optimization, through the sending of new or additional data instead of resending received data or reducing code rates while re-sending old, unreceived data.
[0136] Referring to FIG. 6, FIG. 6 is a timing diagram 600 illustrating a wireless communication system that supports multiplexing TBs during CBG based re-transmission according to one or more aspects. The example of FIG. 6 corresponds to an example of transmitting multiple TBs during CBG based re-transmissions for uplink operations.
[0137] The example of FIG. 6 includes similar devices to the devices described in FIGS. 1, 2, and 4, such as a UE 115 and a network entity (e.g., base station 105). The devices of FIG. 6 may include one or more of the components as described in FIGS. 2 and 4. In FIG. 6, these devices may utilize antennas 252a-r, transmitter 410, receiver 412, encoder 413 and / or decoder 414, or may utilize antennas 234a-t, transmitter 434, receiver 436, encoder 437 and / or decoder 438 to communicate and receive transmissions in accordance with multiplexed TB CBG based retransmissions. In some implementations, network entity may include or correspond to multiple TRPs of a single base station (e.g., base station 105), to multiple base stations, or any combination thereof.
[0138] Although not illustrated in the example of FIG. 6, the base station 105 and the UE 115 may perform capability operations (e.g., multiplexing TBs with CBG based retransmission capability operations), perform configuration operations (e.g., multiplexing TBs with CBG based re-transmission configuration operations), or both, as described with reference to FIG. 5. For example, the base station 105, the UE 115, or both, communicate capability information (e.g., multiplexing TBs with CBG based re-transmission capability information) as described with reference to 510 of FIG. 5, and / or communicate configuration information (e.g., multiplexing TBs with CBG based re-transmission configuration information), as described with reference to 515 of FIG. 5, to enable multiplexing TBs during CBG based re-transmissions.
[0139] At 610, the base station 105 transmits a signaling indication including scheduling information (e.g., CBG indication information) for an uplink transmission. For example, the base station 105 may transmit the scheduling information in a downlink controlchannel transmission, as described with reference to 520 of FIG. 5. As illustrated in the example of FIG. 6, the base station transmits a DCI including the scheduling information, such as the scheduling information 406 of FIG 4, and optionally CBG information (e.g., 442). In other implementations, the base station 105 may transmit a PDCCH, a MAC CE, a RRC, or another type of transmission. The scheduling information may include or correspond to the scheduling information described with reference to FIG. 4. For example, the scheduling information may include or indicate a bitmap for CBG identification and / or CBG mapping to multiple TBs for an uplink transmission or PUSCH.
[0140] At 615, the UE 115 may determine timing and resource allocation information based on receiving the scheduling information at 610, and optionally based on configuration information. For example, the UE 115 may receive and parse the signaling indication (signaling transmission) to determine or identify scheduling information, as described with reference to 525 of FIG. 5. As illustrated in the example of FIG. 6, the UE 115 receives a DCI including an indication for a particular uplink transmission. The UE 115 determines valid CBGs for the upcoming uplink transmission scheduled by the DCI based on the scheduling information, such as based on CBG mapping information. For example, the UE 115 may determine that scheduled uplink transmission includes 8 CBGs for a particular TB (first TB).
[0141] At 620, the UE 115 transmits an uplink data transmission to the base station 105 based on the scheduling information. For example, the UE 115 transmits a first PUSCH to the base station 105 based on the scheduling information, as illustrated in the example of FIG. 6. In other implementations, the data transmission may be a downlink or sidelink transmission, such as PDSCH or PSSCH, as described further with reference to FIGS. 5 and 7.
[0142] At 625, the base station 105 receives the uplink transmission and attempts to decode the determined valid CBGs of the uplink transmission. For example, the base station 105 may monitor for the first PUSCH based on the scheduling information of the DCI, and may attempt to decode the valid CBGs of the PUSCH based on the DCI (e.g., CBG information of the DCI). To illustrate, the base station 105 may decode the valid CBGs of the DCI based on a CBGTI field.
[0143] In the example of FIG. 6, the base station 105 may successfully receive one or more CBGS of the valid CBGs of the first PUSCH, and may not be able to decode one or more other CBGs of the valid CBGs of the first PUSCH. The base station 105 may generateacknowledgment information for the first PUSCH based on successfully receiving the valid CBGs thereof. For example, the base station 105 may generate acknowledgment information for each of the 8 CBGs of the TB.
[0144] As compared to the operations of FIG. 5, the base station 105 may not transmit the acknowledgment information to the UE 115. As the base station 105 is the device which is scheduling the uplink transmissions for the UE 115, the base station 105 already knows which CBGs it has or has not been received. Accordingly, the base station 105 may proceed to determining whether to engage in CBG based re-transmission and / or TB multiplexing as described with reference to 545 FIG. 5.
[0145] At 630, the base station 105 determines the received CBGs for the uplink transmission based on the successfully decoded CBGs. For example, the base station 105 determines which CBGs were received and successfully decoded based on the acknowledgment information. In the example of FIG. 6, less than all 8 CBGs of the particular TB were received by the base station 105. The base station 105 may determine to engage in CBG based retransmission based on less than all CBGs being received. Based on determining to engage in CBG based retransmission, base station 105 and UE 115 perform one or more operations as described with reference to 545-565.
[0146] Additionally, when configured with TB multiplexing for CBG re-transmission, the base station 105 may determine to include one or more new TBs in the upcoming retransmission for the first PUSCH. For example, the base station 105 may determine to include at least one other TB in a re-transmission of or for the first PUSCH based on or more TB multiplexing conditions, such as based on how many CBGs of the first PUSCH were not received, how many TBs were transmitted in the first PUSCH, or a combination thereof. Additionally, the base station 105 may determine to include a TB in the retransmission based on a size of available TBs for transmissions. In some such implementations where the base station 105 has multiple TBs available to add to the retransmission, the base station 105 may select a particular TB or TBs of the multiple available TBs based on an amount of available TBs for the upcoming re-transmission (e.g., how many CBGs of the first PUSCH were successfully received).
[0147] At 635, the base station 105 transmits a second control channel transmission for a second uplink transmission corresponding to a retransmission of the first uplink transmission with a multiplexed TB. For example, the base station 105 generates second scheduling information for a second PUSCH based on the acknowledgement information and transmits the second scheduling information in a second DCI, similar to as described withreference to the DCI at 610 and the second DCI at 550 of FIG. 5.
[0148] After 635, the UE 115 may receive the second control channel transmission and determine scheduling information similar to as described with reference to 615. For example, the UE 115 may receive and parse the signaling indication (signaling transmission) to determine or identify the second scheduling information, as described with reference to 525 of FIG. 5. As illustrated in the example of FIG. 6, the UE 115 receives a second DCI including an indication for a second uplink transmission. The UE 115 determines valid CBGs for the upcoming second uplink transmission scheduled by the second DCI based on the second scheduling information, such as based on second CBG mapping information. For example, the UE 115 may determine that the scheduled second uplink transmission includes a portion of the 8 CBGs for a particular TB (first TB) and one or more CBGs for one or more additional TBs.
[0149] At 640, the UE 115 transmits a second uplink data transmission to the base station 105 based on the second scheduling information. For example, the UE 115 transmits a second PUSCH to the base station 105 based on the second scheduling information and including multiplexed TBs, as illustrated in the example of FIG. 6. In other implementations, the second uplink data transmission may be a downlink or sidelink transmission, such as PDSCH or PSSCH, as described further with reference to FIGS. 5 and 7.
[0150] In the example of FIG. 6, the second uplink transmission includes some of the original 8 CBGs for the particular TB and includes one or more CBGs for a second TB. Additionally, the second uplink transmission may include one or more CBGs for one or more additional TBs, such as a third TB.
[0151] In some implementations, the UE 115 may change a CBG order of the re-transmitted CBGs for the particular CBG used for the first PUSCH when transmitting the second PUSCH (such as when indicated to by the base station 105). To illustrate, the base station 105 may reorder the CBGs to group the CBGs of each TB together and indicate this explicit mapping to the UE 115, or the base station 105 may indicate, such as by a flag, bit or field, for the UE 115 to engage in CBG re-ordering, and the UE 115 may re-order the CBGs based on prior CBG re-ordering information (e.g., such as indicated by CBG configuration information).
[0152] After 640, the base station 105 receives the second uplink transmission and attempts to decode the determined valid CBGs of the second uplink transmission. For example, the base station 105 may monitor for the second PUSCH based on the second scheduling information of the second DCI, and may attempt to decode the valid CBGs of the secondPUSCH based on the second DCI (e.g., second CBG information of the second DCI). To illustrate, the base station 105 may decode the valid second CBGs of the second DCI based on second CBGTI fields for each TB included in the second PUSCH.
[0153] In the example of FIG. 6, the base station 105 may successfully receive of portion of the second CBGs of the second PUSCH, and may not be able to decode one or more valid second CBGs of the second PUSCH. The base station 105 may generate second acknowledgment information for the second PUSCH based on successfully receiving the second CBGs thereof. For example, the base station 105 may generate second acknowledgment information for a total amount of transmitted CBGs (e.g., 8 CBGs) for each TB transmitted in the second PUSCH. To illustrate, if 8 CBGs are transmitted and correspond to 3 TBs, the base station 105 may generate acknowledgment indications for 24 CBGs, 8 CBGs for each of the 3 TBs for the second acknowledgment information. However, of the 24 acknowledgement indications for the second acknowledgment information, only 8 may correspond actual, valid CBGs, transmitted CBGs.
[0154] Optionally, the UE 115 and base station 105 may perform one or more additional CBG based re-transmissions operations at 645. For example, the UE 115 and the base station 105 may perform similar steps 635-640 to communicate one or more second retransmissions, as described with reference to 565 of FIG. 5.
[0155] Accordingly, in the example, of FIG. 6, devices of the network may be able to have a more flexible utilization of CBG based re-transmission through the use a CBG to TB mapping to multiplex CBGs of additional TBs with unsuccessfully decoded CBGs from a prior transmission. Multiplexing TBs for CBG re-transmissions increases throughput and reduced latency by increasing bandwidth utilization and optimization, through the sending of new or additional data instead of resending received data or reducing code rates while re-sending old, unreceived data.
[0156] Referring to FIG. 7, FIG. 7 is a timing diagram 700 illustrating a wireless communication system that supports multiplexing TBs during CBG based re-transmission according to one or more aspects. The example of FIG. 7 corresponds to an example of transmitting multiple TBs during CBG based re-transmissions for sidelink operations. More specifically, the sidelink operations of FIG. 7 correspond type 2 or mode 2 sidelink operations (base station independent or unassisted operations) where the scheduling or master UE ( a first UE 115) is transmitting the sidelink transmissions. In other implementations, the scheduling or master UE ( the first UE 115) may schedule sidelink transmissions for another device and receive and / or relay such transmissions. In suchsidelink implementations, where a scheduling UE is receiving multiplexed TB CBG based retransmissions, the scheduling UE may not transmit feedback information for the received multiplexed TB CBG based retransmissions similar to the base station 105 of the uplink operations of FIG. 5, that is the scheduling device already knows or has the feedback information / what CBGs were successfully decoded.
[0157] Additionally, or alternatively, although the sidelink operations illustrated correspond to type 2 or mode 2 sidelink operations (base station independent or unassisted operations), the sidelink operations may include or correspond to type 1 or mode 1 sidelink operations (base station dependent or assisted operations) in other implementations. In such type 1 or mode 1 sidelink operations, a base station, such as base station 105, may schedule the sidelink transmissions and sidelink re-transmissions. To enable such scheduling, the receiving or transmitting UEs may transmit control information to the base station 105, such as acknowledgment information for a receiving UE (RxUE) and / or available TB information for a transmitting UE (TxUE).
[0158] The example of FIG. 7 includes similar devices to the devices described in FIGS. 1, 2, and 4, such as a first UE 115 and a second UE 703. The devices of FIG. 7 may include one or more of the components as described in FIGS. 2 and 4. In FIG. 7, these devices may utilize antennas 252a-r, transmitter 410, receiver 412, encoder 413 and / or decoder 414 in accordance with multiplexed TB CBG based retransmissions.
[0159] Although not illustrated in the example of FIG. 7, the first UE 115 and the second UE 715 may perform capability operations (e.g., multiplexing TBs with CBG based retransmission capability operations), perform configuration operations (e.g., multiplexing TBs with CBG based re-transmission configuration operations), or both as described with reference to FIGS. 5 and 6. For example, the first UE 115, the second UE 715, or both, communicate capability information (e.g., multiplexing TBs with CBG based retransmission capability information) as described with reference to 510 of FIG. 5, and / or communicate configuration information (e.g., multiplexing TBs with CBG based retransmission configuration information), as described with reference to 515 of FIG. 5, to enable multiplexing TBs during CBG based re-transmissions.
[0160] At 710, the first UE 115 or the second UE 703 communicate a signaling indication including scheduling information (e.g., CBG resource allocation information) for a sidelink transmission. For example, the first UE 115 may transmit the scheduling information in a sidelink control channel transmission, as described with reference to 520 of FIG. 5. As illustrated in the example of FIG. 7, the first UE 115 transmits a SCIincluding the scheduling information, such as the scheduling information 406 of FIG 4, and optionally CBG information (e.g., 442). In other implementations, the first UE 115 may transmit a PSCCH, a SL-MAC CE, a SL-RRC, or another type of transmission. The scheduling information may include or correspond to the scheduling information described with reference to FIG. 4. For example, the scheduling information may include or indicate a bitmap for CBG identification and / or CBG mapping to multiple TBs for a sidelink transmission or PSSCH. Alternatively, the second UE 703 may transmit the scheduling information for transmitted or received sidelink data communications in other implementations.
[0161] At 715, the second UE 703 may determine timing and resource allocation information based on receiving the scheduling information at 710 and optionally based on configuration information. For example, the second UE 703 may receive and parse the signaling indication (signaling transmission) to determine or identify scheduling information, as described with reference to 525 of FIG. 5. As illustrated in the example of FIG. 7, the second UE 703 receives a SCI including an indication for a particular transmission. The second UE 703 determines valid CBGs for the upcoming sidelink transmission scheduled by the SCI based on the scheduling information, such as based on CBG mapping information thereof. For example, the second UE 703 may determine that scheduled uplink transmission includes 8 CBGs for a particular TB (first TB).
[0162] At 720, the first UE 115 transmits a sidelink data transmission to the second UE 703 based on the scheduling information. For example, the first UE 115 transmits a first PSSCH to the second UE 703 based on the scheduling information, as illustrated in the example of FIG. 7. In other implementations, data transmission may be an uplink or downlink transmission, such as PDSCH or PUSCH, as described further with reference to FIGS. 5 and 6.
[0163] At 725, the second UE 703 receives the sidelink transmission and attempts to decode the determined valid CBGs of the sidelink transmission. For example, the second UE 703 may monitor for the first PSSCH based on the scheduling information of the SCI, and may attempt to decode the valid CBGs of the PSSCH based on the SCI (e.g., CBG information of the SCI). To illustrate, the second UE 703 may decode the valid CBGs of the SCI based on a CBGTI field of the SCI.
[0164] In the example of FIG. 7, the second UE 703 may successfully receive of one or more CBGs of the valid CBGs of the first PSSCH, and may not be able to decode one or more other CBGs of the valid CBGs of the first PSSCH. The second UE 703 may generateacknowledgment information for the first PSSCH based on successfully receiving the valid CBGs thereof. For example, the second UE 703 may generate acknowledgment information for each of the 8 CBGs of the TB.
[0165] As compared to the operations of FIG. 6, the second UE 703 may transmit the acknowledgment information to the first UE 115 as the first UE 115 scheduled the PSSCH, along with any retransmissions thereof. As the first UE 115 is the device which is scheduling the sidelink transmissions for the second UE 703, the first UE 115 may not know which CBGs have or have not been received for outgoing sidelink data transmissions. Alternatively, the second UE 703 may transmit the acknowledgment information to a network device when a network device schedules the sidelink transmissions.
[0166] In other implementations, the second UE 703 may not transmit acknowledgment information (e.g., HARQ feedback information). In some such implementations, the second UE 703 may schedule the CBG based retransmission for the PSSCH. For example, the second UE 703 may perform one or more operations at 735-740 and as described with reference to the first UE 115 to determine to send a CBG based retransmission and whether to multiplex a TB for the CBG based retransmission of the PSSCH.
[0167] At 730, the second UE 703 transmits the acknowledgment information for the first PSSCH to the first UE 115. For example, the second UE 703 may transmit the HARQ feedback information for the first PSSCH in a SCI or PSCCH. The acknowledgment information (HARQ feedback information) may include positive acknowledgments for the decoded CBGs and negative acknowledgments for the CBGs that were not decoded.
[0168] At 735, the first UE 115 receives the acknowledgment information and determines the received CBGs for the sidelink transmission. For example, the first UE 115 receives the acknowledgment information in a SCI and determines that less than all 8 CBGs of the particular TB were received by the second UE 703. The first UE 115 may determine to engage in CBG based retransmission based on less than all CBGs being received. Based on determining to engage in CBG based retransmission, the first UE 115 and the second UE may perform one or more operations as described with reference to 740-750.
[0169] Additionally, when configured with TB multiplexing for CBG re-transmission, the first UE 115 may determine to include one or more new TBs in the upcoming re-transmission for the first PDSCH. For example, the first UE 115 may determine to include at least one other TB in a re-transmission of or for the first PDSCH based on or more TB multiplexingconditions, such as based on how many CBGs of the first PDSCH were not received, how many TBs were transmitted in the first PDSCH, or a combination thereof. Additionally, the first UE 115 may determine to include a TB in the re-transmission based on a size of available TBs for transmissions. In some such implementations where the first UE 115 has multiple TBs available to add to the re-transmission, the first UE 115 may select a particular TB or TBs of the multiple available TBs based on an amount of available TBs for the upcoming re-transmission (e.g., how many CBGs of the first PSSCH were successfully received).
[0170] At 740, the first UE 115 transmits a second control channel transmission for a second sidelink transmission corresponding to a retransmission of the first sidelink transmission with a multiplexed TB. For example, the first UE 115 generates second scheduling information for a second PSSCH based on the acknowledgement information and transmits the second scheduling information in a second SCI, similar to as described with reference to the SCI at 710 and the second DCI at 550 of FIG. 5.
[0171] Between 740 and 745, the second UE 703 may determine valid CBGs based on the second control channel transmission, such as the second scheduling information thereof. The second UE 703 may determine the valid CBGs similarly to the operations as described with reference to 725 and 525 of FIG. 5.
[0172] At 745, the first UE 115 transmits a second sidelink data transmission to the second UE 703 based on the second scheduling information. For example, the first UE 115 transmits a second PSSCH to the second UE 703 based on the second scheduling information, as illustrated in the example of FIG. 7. In other implementations, the second sidelink data transmission may be a downlink or sidelink transmission, such as PDSCH or PUSCH, as described further with reference to FIGS. 5 and 6. The second sidelink transmission includes some of the original 8 CBGs for the particular TB and includes one or more CBGs for a second TB. Additionally, the second sidelink transmission may include one or more CBGs for one or more additional TBs, such as a third TB. The first UE 115 or second UE 703 may change a CBG order of the re-transmitted CBGs for the particular CBG used for the first PDSCH when transmitting the second PDSCH (such as when indicated to by the first UE 115). To illustrate, the first UE 115 may reorder the CBGs to group the CBGs of each TB together and indicate this explicit mapping to the second UE 703, or the first UE 115 may indicate, such as by a flag, bit or field, to engage in CBG reordering and the second UE 703 may determine to re-order the CBGs based on prior CBG re-ordering information (e.g., such as indicated by CBG configuration information).
[0173] After 745, the second UE 703 receives the second sidelink transmission and attempts to decode the determined valid CBGs of the second sidelink transmission. For example, the second UE 703 may monitor for the second PSSCH based on the second scheduling information of the second SCI, and may attempt to decode the valid CBGs of the second PSSCH based on the second SCI (e.g., second CBG information of the second SCI). To illustrate, the second UE 703 may decode the valid second CBGs of the second SCI based on second CBGTI fields (of the second SCI) for each TB included in the second PDSCH.
[0174] In the example of FIG. 7, the second UE 703 may successfully receive of portion of the second CBGs of the second PSSCH, and may not be able to decode one or more valid second CBGs of the second PSSCH. The second UE 703 may generate second acknowledgment information for the second PSSCH based on successfully receiving the second CBGs thereof. For example, the second UE 703 may generate second acknowledgment information for a total amount of transmitted CBGs (e.g., 8 CBGs) for each TB transmitted in the second PSSCH. To illustrate, if 8 CBGs are transmitted and correspond to 3 TBs, the second UE 703 may generate acknowledgment indications for 24 CBGs, 8 CBGs for each of the 3 TBs for the second acknowledgment information. However, of the 24 acknowledgement indications for the second acknowledgment information, only 8 may correspond actual, valid CBGs, transmitted CBGs.
[0175] Optionally, the second UE 703 and first UE 115 may perform one or more additional CBG based re-transmissions operations at 750. For example, the second UE 703 and the first UE 115 may perform similar steps 735-745 to communicate one or more second retransmissions, as described with reference to 565 of FIG. 5.
[0176] Accordingly, in the example, of FIG. 7, devices of the network may be able to have a more flexible utilization of CBG based re-transmission through the use a CBG to TB mapping to multiplex CBGs of additional TBs with unsuccessfully decoded CBGs from a prior transmission. Multiplexing TBs for CBG re-transmissions increases throughput and reduced latency by increasing bandwidth utilization and optimization, through the sending of new or additional data instead of resending received data or reducing code rates while re-sending old, unreceived data.
[0177] Referring to FIG. 8, FIG. 8 depicts a flow diagram 800 illustrating an example of operations of multiplexing TBs during CBG based re-transmission. Diagram 800 illustrates processing operations for both a UE and a network device for multiplexing TBs during CBG based re-transmission. Although illustrated for in the context of uplink and downlink operations, in other implementations, the operations may correspond to sidelinkoperations or involve the transmission of PUSCHs. For example, the network device could schedule sidelink transmissions (PSSCHs) between two UEs or the network device could be replaced with a scheduling UE or master UE for UE to UE communications, as described with reference to FIG. 7. As another example, the PDSCHs referenced in FIG. 8 could be PUSCHs and the network device could attempt to decode received CBGs in PUSCH transmissions from a UE as described with reference to FIG. 6.
[0178] During operation, at 810, a UE attempts to decode all valid CBGs of a received transmission based on CBGTI fields for each TB in a prior DCI. For example, the UE receives a PDSCH transmission which includes CBGs for one or more TBs, and the UE determines valid CBGs (which CBGs of which TBs are actually transmitted) based on CBGTI fields for each TB. The UE may then attempt to decode each valid CBG and may not attempt to receive or decode non-valid CBGs.
[0179] At 815, the UE signals acknowledgement information for each CBG and per each TB. For example, the UE transmits a PUCCH (e.g., UCI) or PUSCH indicating ACKs for received CBGs and NACKs for CBGs which were not received or not scheduled. The NACKs may include NACKs for valid CBGs which were not received and for not-valid CBGs which were not sent.
[0180] At 820, the base station receives the acknowledgement information and decodes the acknowledgement information. For example, the base station receives a PUCCH or other uplink transmission including the acknowledgement information and determines the indicated ACKs and NACKs for each CBG of each TB of the transmitted PDSCH based on the acknowledgement information.
[0181] At 825, the base station determines a total amount (e.g., a number or value) of received CBGs (passed valid CBGs) across all TBs of the transmission and / or associated with the same DCI. For example, the base station determines an amount of positive acknowledgement indications (ACKs) in the acknowledgement information.
[0182] At 830, the base station evaluates one or more conditions for multiplexing TBs with CBG based re-transmission. For example, the base station may evaluate one or more conditions for determining to retransmit all of the previous CBGs of the prior transmission, or to add one or more CBGs of one or more additional TBs for a next transmission (for transmission along with retransmission of the CBGs of the previous transmission which were not received).
[0183] In the example illustrated in FIG. 8, the base station evaluates two conditions, both of which must be satisfied, to schedule a new TB for a CBG based retransmission. Whenboth conditions are satisfied the base station proceeds to 840. As illustrative, non-limiting examples, the two conditions include a minimum number of passed CBGs and a maximum number of multiplexed TBs in the example of FIG. 8. The minimum number of passed CBGs may include a minimum number or threshold of passed CBGs of the prior transmission which must be received before another TB can be added (e.g., before additional CBGs for the additional TB can be multiplexed). This minimum number or threshold may be considered for a particular TB of the transmission individually or for all TBs of the transmission collectively. Additionally, the minimum number of passed CBGs may take into account received CBGs from other previous transmissions. Alternatively, the condition may include a minimum number of received CBGs for the prior transmission only. As compared to the passed condition, the received condition may only evaluate the CBGs of the last transmission, while the passed condition may take into account CBGs received from earlier transmissions / retransmissions with the prior transmission itself is a retransmission.
[0184] The TB condition may include a maximum number or threshold of TBs of the prior transmission or a maximum number or threshold of TBs for the planned re-transmission. This TB condition may only look at the number of TBs previously used in the immediately prior transmission, or this TB condition may further evaluate which TBs of the prior transmission have been completed or if a bandwidth for an upcoming retransmission is larger (can accommodate more CBGs or TBs).
[0185] In this particular implementation, if either condition is not satisfied, the base station does not schedule a new TB for the CBG based retransmission and the base station proceeds to 835. In other implementations, other conditions may be used in addition to or in place of the illustrated two conditions. Alternatively, only one condition may be satisfied to schedule a new TB for the CBG based retransmission in some other implementations.
[0186] At 835, the base station determines to not schedule a new TB and proceeds with retransmission of the CBGs with no new transmission of new CBGs and / or no new transmission of new TBs. For example, the base station determines to not schedule a new TB for a second PDSCH and the second PDSCH proceeds with re-transmission of the CBGs with without multiplexing a new TB. This transmission may be re-transmission with or without TB multiplexing based on if the original PDSCH included multiple TBs.
[0187] At 840, the base station determines to multiplex a new TB for the upcoming retransmission. The base station schedules a new TB with a TBS determined based on a K value of CBs in passing CBGs of the previous DCI. For example, the base stationdetermines to schedule a second TB for the second PDSCH with a TBS determined based on a K value of CBs of decoded CBGs at 810.
[0188] After either of 835 or 840, the base station transmits a DCI (e.g., another or second DCI) indicating the second PDSCH. The second DCI either indicates a new TB has been included in the second PDSCH (as compared to the first PDSCH), as in 840, or does not indicate any new TB in the second PDSCH, as in 835.
[0189] At 845, the UE receives the DCI and determines a number of TBs for the second PDSCH. For example, the UE receives a second DCI and determines a number of TBs for the second PDSCH based on a TB indication (e.g., amount of TB indication or TB multiplexing indication) or mapping information, such as a CBG to TB mapping information, in the second DCI.
[0190] At 850, the UE determines valid CBGs per TB based on the second DCI. For example, the UE determines valid which CBGs correspond to which TB based on a CBG indication per TB or on CBG mapping information, such as a CBG bitmap, in the second DCI. An example mapping of CBG to TB is illustrated in FIG. 9.
[0191] At 855, the UE determines, for each valid TB indicated by the second DCI, K and E values for each CB per CBG based on the second DCI. For example, the UE determines, for each TB with a valid CBG in the second PDSCH, K and E values for each CB per CBG based on a resource allocation and an MCS associated with the second PDSCH as indicated by the second DCI.
[0192] After 855, the process repeats (e.g., goes back to 810). For example, the UE monitors for and receives the second PDSCH and attempts to decode all the valid CBGs based on the second DCI. The process may repeat until CBGs for all of the multiplexed TBs are successfully received and decoded.
[0193] Referring to FIG. 9, FIG. 9 depicts diagrams 900 and 950 illustrating an example of operations for multiplexing TBs during CBG based re-transmission. In FIG. 9, diagram 900 illustrates a table depicting CBG based re-transmission over four transmissions, and diagram 950 depicts CBGs of the four TBs used in the four transmissions shown in diagram 900. Diagram 900 further illustrates a mapping of CBGs to TBs for each transmission of the four transmissions.
[0194] In FIG. 9, diagram 900 depicts transmission and reception of CBGs for multiple TBs over four transmissions, TxO, Txl, Tx2, and Tx3. As illustrated in the example of FIG. 9, a first transmission (TxO) corresponds to a first transmission, and second, third and fourth transmissions correspond to re-transmissions (e.g., first, second and third re-transmissionsrespectively). The re-transmissions include transmissions for multiple TBs where one or more associated CBGs of at least one TB of the multiple TBs is being retransmitted from a prior transmission.
[0195] Diagram 900 includes four columns, each column corresponding to a transmission of the four transmissions. For each transmission / column, there are a plurality of rows for each CBG. The plurality of rows for each CBG include a corresponding row for each TB of the four TBs. Each column includes one transmission entry per CBG (per groups of four rows) indicating which TBs are sent for that particular CBG, and for the particular transmission / column.
[0196] In FIG. 9, a legend is also provided depicting a status for the transmitted CBGs of a transmission. The status for the transmitted CBGs include initial Tx fail, initial TX pass, retransmit fail, and retransmit pass.
[0197] In FIG. 9, diagram 950 depicts a mapping or association of CBGs to four TBs, TB0, TB1, TB2, and TBs. As illustrated in FIG. 9, a first TB (TB0) is associated with 8 CBGs (CBG0-CBG7), a second TB (TB1) is associated with 4 CBGs (CBG2, CBG3, CBG6, and CBG7), a third TB (TB2) is associated with 4 CBGs (CBG0, CBG2, CBG4, and CBG7), a fourth TB (TB3) is associated with 5 CBGSs (CBG3-CBG7). As will be described with reference to the transmissions of diagram 900, each transmission of a TB may not include this exact mapping, that is each transmission for a TB may not include all CBGs associated with the TB. The CBGs for a particular TB may be sent piecemeal over multiple transmissions.
[0198] During operation, two devices may engage in CBG based retransmission with multiplexed TBs, as described with reference to FIGS. 4-8. The devices may engage in CBG based re-transmission over multiple transmissions, and for example CBG based transmissions are illustrated in FIG. 9.
[0199] As illustrated in diagram 900, for the first transmission TxO (initial transmission), 8 CBGs of CBG0-CBG7 are transmitted for a first TB, TB0. Of the 8 CBGs (valid CBGs), 4 of them are successfully received by the receiving device, CBG2, CBG3, CBG6, and CBG7. The other 4 CBGs, CBG0, CBG1, CBG4, and CBG5, are not successfully received and decoded. For example, the receiving device may detect a failure or error with respect to a cyclic redundancy check (CRC).
[0200] The devices may engage in CBG retransmission with multiplexing TBs based on some of the CBGs of the first transmission TxO not being received, and the transmitting device may transmit the second transmission Txl (first re-transmission). For the secondtransmission Txl (first re-transmission), 8 total CBGs of CBG0-CBG7 are transmitted for the first TB (TBO) and a second TB (TB 1), with four CBGs for each TB. As described with reference to FIGS. 4-8, because there are multiple TBs or multiplexed TBs in the second transmission, the valid CBGs may be indicated for each TB. The valid CBGs may be indicated explicitly, like CBGO for TBO, CBG1 for TBO, etc., or the valid CBGs may be indicated by a bitmap as described above.
[0201] Of the 8 CBGs (valid CBGs) of the second transmission Txl (first re-transmission), 4 of them are successfully received by the receiving device, CBGO of TBO, CBG2 for TB1, CBG5 for TB1, and CBG7 for TB1. The other 4 CBGs, CBG1 of TBO, CBG3 of TB1, CBG5 of TBO, and CBG6 of TB1, are not successfully received and decoded.
[0202] The transmitting device may transmit the third transmission Tx2 (second re-transmission) based on some of the CBGs of the second transmission Txl not being received. For the third transmission Tx2 (second re-transmission), 8 total CBGs of CBG0-CBG7 are transmitted for the first TB (TBO), the second TB (TB1), and a third TB (TB2), with 2 CBGs for the first TB (TBO), 2 CBGs for the second TB (TB1), and 4 CBGs for the third TB (TB2). The transmitted CBGs include CBG1 and CBG5 for the first TB (TBO), include CBG3 and CBG6 for the second TB (TB1), and include CBGO, CBG2, CBG4, and CBG7 for the third TB (TB2).
[0203] Of the 8 CBGs (valid CBGs) of the third transmission Tx2 (second re-transmission), 5 of them are successfully received by the receiving device, CBG3 of TB2, CBG4 for TB2, CBG5 for TB2, CBG6 for TB1, and CBG7 for TB2. The other 3 CBGs, CBGO of TBO, CBG1 of TB2, and CBG2 of TB1, are not successfully received and decoded.
[0204] The transmitting device may transmit the fourth transmission Tx3 (third re-transmission) based on some of the CBGs of the third transmission Tx2 not being received. For the fourth transmission Tx3 (third re-transmission), 8 total CBGs of CBG0-CBG7 are transmitted for the first TB (TBO), the third TB (TB2), and a fourth TB (TB3), with 1 CBG for the first TB (TBO), 2 CBGs for the third TB (TB2), and 5 CBGs for the fourth TB (TB3). The transmitted CBGs include CBG1 for the first TB (TBO), CBGO and CBG2 for the third TB (TB2), and CBG3, CBG4, CBG5, CBG6, and CBG7 for the fourth TB (TB3).
[0205] Of the 8 CBGs (valid CBGs) of the fourth transmission Tx3 (third re-transmission), 3 of them are successfully received by the receiving device, CBGO of TB2, CBG1 for TBO, and CBG2 for TB2. The other 5 CBGs, CBG4 of TB3, CBG5 of TB3, CBG6 of TB3, CBG7 of TB3, and CBG7 of TB3 are not successfully received and decoded.
[0206] As compared to the operations of FIG. 3, the code rate (R) for each CBG of the retransmissions may not be reduced from a code rate of the corresponding CBG of the first transmission (initial transmission). For example, the code rate may not reduce to one- half or one-quarter of the code rate of the initial transmission. Furthermore, additional CBGs and TBs were transmitted in the re-transmissions, which increase throughput and reduce latency. Accordingly, network operations are improved.
[0207] Referring to FIG. 10, FIG. 10 depicts a table 1000 illustrating CBG information for the example multiplexing TBs during the CBG based re-transmission operations of FIG. 9. Table 1000 of FIG. 10 depicts information for three of the four TBs transmitted in the four transmissions described with reference to FIG. 9, specifically TB0-TB2.
[0208] Table 1000 illustrates code block size information, code block to code block group mapping information, CBG to TB mapping information, and TB size information for each TB illustrated in FIG. 10. The code block size information may include or indicate a size for each code block of the transmission. As illustrated in FIG. 10, the code blocks may be arranged sequentially and / or by code block group.
[0209] The code block size information may be the same from transmission to transmission in some implementations, as illustrated in the example of FIG. 10. In other implementations, the code block size information may change from transmission to transmission. For example, code blocks 1-5 of CBG0 may have a different size in a second transmission (first re-transmission). To illustrate, a size of the code blocks may change when associated with a different TB, such as when transmitting information / a CBG for another TB. Although each code block of a particular code block group has the same size in the example of FIG 10, in other implementations, one or more code blocks of a particular code block group may be a different size than another code block of the particular code block group.
[0210] The size of each CB may be indicated by an amount of REs (e.g., an RE value), an amount of information bits(e.g., a K value), an amount of transmission bits (e.g., an E value), or a combination thereof. In the example of FIG. 10, the table 1000 provides K, RE, and E values (e.g., an amount, number or quantity of the parameter) for each CB of the TB. Information bits (e.g., K) may include or correspond to bits which indicate data, and transmission bits (e.g., E) may include the information bits and additional parity bits (e.g., CRC bits). The K value corresponds to the quantity of information bits (before encoding) for a CB. TBS corresponds to the total quantity of information bits (before encoding) carried by a TB, and the E value corresponds to the quantity of transmission bits (afterencoding, rate-matching, etc.) for a CB.
[0211] The code block to code block group mapping information may include or indicate which code block groups include which code blocks, such as to indicate a corresponding or associated CBG for each CB. As illustrated in FIG. 10, the code block to code block group mapping may be the same from transmission to transmission in some implementations. In other implementations, the code block to code block group mapping may change from transmission to transmission. For example, CBG-0 may include code blocks 1-4, code blocks 6-10, or code blocks 11-15, etc., in other transmissions (as compared to the code blocks 1-5 in FIG. 9). The code block to code block group mapping may be adjusted to re-order or reorganize the code blocks or code block groups such that the CBGs for a particular TB are grouped with one another. To illustrate, a first code block to code block group mapping for a first transmission may be adjusted for a second transmission to keep first code blocks, first code block groups, or both of TBO together and / or to keep second code blocks, second code block groups, or both of TB1 together.
[0212] The size of each CBG may be indicated by an RE value, a K value, a CB value, an E value, or a combination thereof. In the example of FIG. 10, the table 1000 provides K, RE, CB, and E values for each CBG of each TB.
[0213] The CBG to TB mapping information may include or indicate which code block groups correspond to which TB or vice versa, such as to indicate a corresponding or associated CBG for each TB. In FIG. 10, the mapping information is static as details for the CBGs and TBs transmitted are illustrated. In other implementations, the CBGs for TB1 and TB2 may be sequential or grouped together based on a CBG reordering configuration (e.g., CBG / TB reordering enabled).
[0214] For CBG or TB reordering, the devices of the network may perform implicit re-ordering operations or explicit re-ordering operations. Implicit re-ordering operations may include mapping CBGs based on a master or absolute CBG mapping index (e.g., master or constant CBG mapping information. The master or absolute CBG index remains the same across multiple or all re-transmissions and maps CBGs to a time-frequency grid (e.g., two dimensional resource grid) such that CBGs for a TB will be contiguous. Accordingly, the CBGs for each TB of the transmission will be grouped to enable time and / or frequency hopping. In some such implicit re-ordering operations, the order of TB mapping to the resource grid can be pre-configured, semi-statically configured, or dynamically configured. For example, the order of TB mapping to the resource grid may be signaled or determined based on a number of TBs multiplexed in a given slot or based on amaximum number of TBs that can be multiplexed in any slot (e.g., maximum quantity of TB threshold). To illustrate, the UE may be configured with multiple time and / or frequency hopping schemes and may select one scheme to use based on a DCI indication indicating an amount of TBs for a particular transmission or based on higher layer configured parameter, such as a CBG based re-transmission configuration indicating a maximum quantity of TB threshold.
[0215] Explicit re-ordering operations may include explicitly signaling the CBG positions for all of the CBGs or only for the CBGs with new CBG positions in the re-transmission. For example, the control transmission or DCI which schedules the re-transmission may indicate an order of the TBs and the CBGs may be rearranged according to the TB order, or the control transmission or DCI may indicate to change a position of certain CBGs or certain TBs. Alternatively, the control transmission or DCI can provide an explicit mapping for CBG positions for each CBG and / or TB. In addition to or in the alternative of, the control transmission or DCI which schedules the re-transmission may further provide the mapping for CBGs to the resource grid or provide information for determining the mapping for CBGs to the resource grid such that time and / or frequency hopping is enable for CBGs and / or TBs.
[0216] The TB size information may include or indicate a total size for each TB used in the four transmissions. The total TB size illustrated corresponds to the total size of each CBG of the TB and not the size of the TB for each transmission as only a portion of the CBGs of each TB may be included in a particular transmission. The actually transmitted TB size (size of the included CBGs) may change from transmission to transmission based on reception of particular CBGs associated with the TB.
[0217] The TB size information may include a size for each CBG of the TB and a total size of the TB. The size of each CBG may be indicated by an RE value, a CB value, a K value, an E value, or a combination thereof. The total size of the TB may be indicated by a TBS value. In the example of FIG. 10, the table 1000 provides a TBS value for each TB along with a total RE value and a total E value for each TB. Table 1000 further provides K, RE, CB, and E values for each CBG of the TB.
[0218] In the example of FIG. 10, the values of table 1000 are associated with corresponding transmission parameter settings. As an illustrative example, the number of resource blocks (RBs) is 273, a number of symbols per slot is 14, a number of reference signals per slot is 1 (e.g., or the number of additional DMRS per slot), and the modulation coding scheme is 27.
[0219] In some implementations, a device may calculate a TBS of each TB based on the K values of all CBs mapped to the TB. Additionally, or alternatively, the device may determine a number of resource elements (REs) for each TB based on an amount of coded bits (e.g., an E value) for each CBG mapped to the respective TB. In addition, the device may map CBs to CBGs based on an amount of CRC bits for each CBG of the last TB in some such implementations or in other implementations.
[0220] In some implementations, a K value may be determined or adjusted to keep a CB to CBG mapping the same between re-transmissions. Additionally, or alternately, an E value may be determined or adjusted based on the MCS, the number of REs, or both.
[0221] In some implementations, a device of the network may determine TBS assuming only a single TB is enabled for the DCI and calculate a number of CBs, calculate a number of CBGs, and calculate a K value for each CB of every CBG based on this assumption. Then, the device may calculate, based on valid CBGs (such as determined based on CBGTI) of each TB, K values for each TB (e.g., K values for each valid CBG of the TB) and then calculate a TBS (e.g., total K value) of that TB based on the K values. The device may further account for any new TB multiplexed in the re-transmission by accounting for the TB CRC bits to be included in the new TB by deriving the TBS value for each TB.
[0222] Similarly, a device of the network may calculate a total G value (amount or quantity of transmission bits for the grant associated with the DCI) based on the resources signaled in the DCI. Then, the device of the network may determine transmission bits for the TBs based on the allocated G value. For example, the device may, based on a number of valid CBGs across all TBs associated with the DCI, distribute the transmission bits of the G value across the valid TBs enabled in the slot and then calculate an E value for each TB (e.g., for each CB or CBG of the TB).
[0223] FIG. 11 is a flow diagram illustrating example blocks executed by a wireless communication device (e.g., a UE or base station) configured according to an aspect of the present disclosure. The example blocks will also be described with respect to UE 115 as illustrated in FIG. 13. FIG. 13 is a block diagram illustrating UE 115 configured according to one aspect of the present disclosure. UE 115 includes the structure, hardware, and components as illustrated for UE 115 of FIGS. 2 and / or 4. For example, UE 115 includes controller / processor 280, which operates to execute logic or computer instructions stored in memory 282, as well as controlling the components of UE 115 that provide the features and functionality of UE 115. UE 115, under control ofcontroller / processor 280, transmits and receives signals via wireless radios 1301a-r and antennas 252a-r. Wireless radios 1301a-r includes various components and hardware, as illustrated in FIG. 2 for UE 115, including modulator / demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266. As illustrated in the example of FIG. 13, memory 282 stores CBG logic 1302, TB logic 1303, CBG re-transmission logic 1304, scheduling data 1305, CBG data 1306, CBG re-transmission data 1307, and settings data 1308. The data (1302-1308) stored in the memory 282 may include or correspond to the data (406, 408, 442, and / or 444) stored in the memory 404 of FIG. 4.
[0224] At block 1100, a wireless communication device, such as a UE or a base station, transmits a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB. The first transmission may include or correspond to one or more of the first transmission 452 of FIG. 4, the first PDSCH transmission of FIG. 5, the first PUSCH transmission of FIG. 6, the first PSSCH transmission of FIG. 7, or one of the transmissions of FIG. 8 or 9. The first TB may include or correspond to a TB of the transmissions above, including TB0. For example, the UE 115 may transmit the first transmission 452 to the base station 105 or another UE including a first TB (e.g., TB0). To illustrate, UE 115 transmits a PUSCH or PSSCH via wireless radios 1301a-r and antennas 252a-r and including CBGs for a first TB. As another example, the base station 105 may transmit the first transmission 452 to the UE 115 including a first TB (e.g., TB0). To illustrate, the base station 105 transmits a first PUSCH via wireless radios 1401a-t and antennas 234a-t and including CBGs for a first TB.
[0225] At block 1101, the wireless communication device obtains scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing. The scheduling information may include or correspond to one or more of the scheduling information 406 of FIG. 4 or the scheduling information of one of the control transmissions (e.g., control channel transmission 456), DCIs, or SCIs of FIGS. 4-8. For example, the UE 115 may receive a DCI or SCI including scheduling information or may transmit an SCI including scheduling information as described with reference to FIGS. 4- 8. Additionally, or alternatively, the UE 115 or the base station 105 may generate the scheduling information based on decoding the CBGs of the first transmission or based on received feedback information (e.g., acknowledgement information 408) as described with reference to FIGS. 4-8. As illustrative examples, the scheduling information mayinclude or correspond to one or more resource allocation information, MCS information, CBGTI, CBGFI, new data indicator (NDI) information, redundancy version (RV) information, antenna port information, layer information, codeword information, or a combination thereof.
[0226] At block 1102, the wireless communication device transmits, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB. The second transmission may include or correspond to one or more of the second transmission 458 of FIG. 4, the second PDSCH transmission of FIG. 5, the second PUSCH transmission of FIG. 6, the second PSSCH transmission of FIG. 7, or one of the transmissions of FIG. 8 or 9. The second TB may include or correspond to a multiplexed TB of the transmissions above, including TB1-TB3. For example, the UE 115 may transmit the second transmission 458 to the base station 105 or another UE including at least one CBG of the first TB (e.g., TBO) and at least one CBG of a second TB (e.g., TB1). To illustrate, UE 115 transmits a PUSCH or PSSCH via wireless radios 1301a-r and antennas 252a-r and including CBGs for a first TB and for a second TB where the PDSCH is a re-transmission of another, earlier PDSCH which included CBGs for the first TB. As another example, the base station 105 may transmit the second transmission 458 to the UE 115 including at least one CBG of the first TB (e.g., TBO) and at least one CBG of a second TB (e.g., TB1). To illustrate, the base station 105 transmits a second PUSCH via wireless radios 1401a-t and antennas 234a-t and including CBGs for a first TB and a second TB where the PDSCH is a re-transmission of another, earlier PDSCH which included CBGs for the first TB.
[0227] The wireless communication device (e.g., UE or base station) may execute additional blocks (or the wireless communication device may be configured further perform additional operations) in other implementations. For example, the wireless communication device (e.g., the UE 115) may perform one or more operations described above, such as described with reference to FIGS. 3-10. As another example, the wireless communication device (e.g., the UE 115) may perform one or more aspects as presented below.
[0228] In a first aspect, to obtain the scheduling information the wireless communication device is configured to: receive feedback information for the first transmission, the feedback information indicating acknowledgement information for each CBG of the plurality of CBGs of the first TB of the first transmission; and generate the scheduling informationfor the second transmission based on the feedback information for the first transmission, and the wireless communication device is further is configured to: transmit the scheduling information.
[0229] In a second aspect, alone or in combination with the first aspect, to obtain the scheduling information the wireless communication device is configured to: receive scheduling information for the second transmission, the scheduling information indicating the plurality of second CBGs for the second TB.
[0230] In a third aspect, alone or in combination with one or more of the above aspects, the wireless communication device is further is configured to: determine an amount CBGs of the plurality of second CBGs of the second TB to include in the second transmission based on an amount of received CBGs for the first transmission; and determine a TBS size for the second TB of the second transmission based on an amount of valid code blocks (CBs) mapped to the determined amount CBGs for the second TB and on a CB size of each valid CB.
[0231] In a fourth aspect, alone or in combination with one or more of the above aspects, the scheduling information is included in a group-common DCI, and wherein each TB of the second transmission is associated with a same HARQ process number.
[0232] In a fifth aspect, alone or in combination with one or more of the above aspects, the scheduling information includes signaling information for the second transmission on a per TB basis, and wherein the scheduling information indicates a CBGTI, a CBGFI, a NDI, a RV, an antenna port and a number (e.g., an amount or quantity) of layer for each TB included in the second transmission (e.g., a first CBGTI for first TB and a second CBGTI for second TB).
[0233] In a sixth aspect, alone or in combination with one or more of the above aspects, the scheduling information indicates an MCS for each TB included in the second transmission.
[0234] In a seventh aspect, alone or in combination with one or more of the above aspects, the feedback information indicates an acknowledgment information for each TB on a per CBG basis.
[0235] In an eighth aspect, alone or in combination with one or more of the above aspects, to transmit the second transmission the wireless communication device is configured to: map scheduled CBGs for each to TB of the second transmission to corresponding CBG positions of the second transmission based on a time or frequency hopping scheme, wherein at least one CBG position of second CBG positions for the CBGs of the first TBfor the second transmission corresponds to a different CBG position than at least one CBG position of first CBG positions for the CBGs of the first TB for the first transmission.
[0236] In a ninth aspect, alone or in combination with one or more of the above aspects, to map the scheduled CBGs for each to TB of the second transmission to corresponding CBG positions of the second transmission based on the time or frequency hopping scheme the at least one processor is configured to: map the scheduled CBGs based on resource grid information (e.g., implicit indication via RRC) or based on a dynamic mapping indication (e.g., explicit indication via DCI or SCI).
[0237] In a tenth aspect, alone or in combination with one or more of the above aspects, the at wireless communication device is configured to: determine to enable or disable multiplexing of TBs across CBG based re-transmission based on number of passing CBGs in previous transmission and on one or more operating conditions, wherein the one or more operating conditions include a preemption scenario involving puncturing one or more CBGs with high priority grants, varying colored interference noise across CBGs, sparse CBG failure under highly time varying frequency selectivity channel conditions, or a combination thereof; and transmit or receive a multiplexing of TBs across CBGbased re-transmission indicator based on the determination, wherein the indicator is configured to enable or disable multiplexing of TBs across CBG based re-transmission.
[0238] In an eleventh aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: transmit or receive capability information indicating support for multiplexing TB across CBG based re-transmission, a maximum number of TBs that can be multiplexed across CBG based re-transmission, or both; or transmit or receive configuration information indicating a threshold number of TBs that can be multiplexed across CBG based re-transmission, threshold number of successful or failed CBGs to enable TB multiplexing across CBG based re-transmission, or both.
[0239] In a twelfth aspect, alone or in combination with one or more of the above aspects, more than one code word (CW) is enabled for the second transmission; the second transmission includes more than four layers (e.g., streams per User); or both.
[0240] In a thirteenth aspect, alone or in combination with one or more of the above aspects, to transmit the second transmission the wireless communication device is configured to: determine an amount of received CBGs of the first TB, an amount of not received CBGs of the first TB, or both, based on the scheduling information for the second transmission;determine an amount of available CBGs for the second transmission based on the amount of received CBGs, the amount of not received CBGs, or both; and select the second TB based on the determined amount of available CBGs.
[0241] In a fourteenth aspect, alone or in combination with one or more of the above aspects, the second transmission further includes a transmission of one or more third CBGs of a plurality of third CBGs for a third TB.
[0242] In a fifteenth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: receive second feedback information for the second transmission, the second feedback information indicating second acknowledgement information for the CBGs of the first TB included in the second transmission and for the second CBGs of the second TB included in the second transmission; generate a third transmission based on the second feedback information and based on a third TB; and transmit the third transmission, wherein the third transmission comprises a re-transmission of a portion of the second TB of the second transmission and a transmission of a plurality of third CBGs for the third TB.
[0243] In a sixteenth aspect, alone or in combination with one or more of the above aspects, the third transmission further comprises a re-transmission of the first TB and includes of a portion of the CBGs of the first TB of the second transmission; the third TX further includes a transmission of a plurality of fourth CBGs for a fourth TB; or both.
[0244] In a seventeenth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: receive second feedback information for the second transmission, the second feedback information indicating second acknowledgement information for the CBGs of the first TB of the second transmission and for the second CBGs of the second TB of the second transmission; generate a third transmission based on the second feedback information; and transmit the third transmission, wherein the third transmission comprises a re-transmission of a portion of the first TB of the second transmission and of a portion of the second TB of the second transmission.
[0245] In an eighteenth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: receive a control channel transmission including the scheduling information for the second transmission, wherein the channel transmission is a DCI or SCI, wherein the scheduling information includes MCS, NDI, RV, CBGTI, CBGFI for each TB; and determine that the second transmission includes CBGs for the second TB based on the scheduling information.
[0246] In a nineteenth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: determine to include the second CBGs for the second TB in the second transmission based on received feedback information for the first transmission; and transmit a control channel transmission including scheduling information for the second transmission, the scheduling information indicating the second CBGs for the second TB, wherein the control channel transmission is a DCI or SCI, and wherein the scheduling information includes MCS, NDI, RV, CBGTI, CBGFI for each TB.
[0247] In a twentieth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is further configured to: receive feedback information for the first transmission, the feedback information indicating acknowledgement information for CBGs of the first TB of the first transmission; and determine whether to include the plurality of second CBGs for the second TB in the second transmission based on the feedback information.
[0248] In a twenty-first aspect, alone or in combination with one or more of the above aspects, to determine whether to include the second CBGs for the second TB in the second transmission, the wireless communication device is configured to: determine a number of CBGs that were acknowledged as being received based on the feedback information; determine whether the number of CBGs that were acknowledged as being received is greater than or equal to a threshold number of passing CBGs for multiple TB CBG retransmission; and determine to include the second TB in the second transmission based on the number of CBGs that were acknowledged as being received being greater than or equal to the threshold number of passing CBGs; or determine to not include the second TB in the second transmission based on the number of CBGs that were acknowledged as being received being less than the threshold number of passing CBGs.
[0249] In a twenty-second aspect, alone or in combination with one or more of the above aspects, to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine a number of multiplexed TBs for the first transmission based on the feedback information; determine whether the number of multiplexed TBs for the first transmission is greater than or equal to a threshold number of multiplexed TBs for multiple TB CBG retransmission; and determine to include the second TB in the second transmission based on the number of multiplexed TBs being less than the threshold number of multiplexed TBs; or determineto not include the second TB in the second transmission based on the number of multiplexed TBs being greater than or equal to the threshold number of multiplexed TBs.
[0250] In a twenty-third aspect, alone or in combination with one or more of the above aspects, to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to include the second TB in the second transmission based on: a number of CBGs that were acknowledged as being received being greater than or equal to a threshold number of passing CBGs; and a number of multiplexed TBs being less than the threshold number of multiplexed TBs.
[0251] In a twenty-fourth aspect, alone or in combination with one or more of the above aspects, to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to not include the second TB in the second transmission based on: a number of CBGs that were acknowledged as being received being less than a threshold number of passing CBGs; or a number of multiplexed TBs being greater than or equal to a threshold number of multiplexed TBs.
[0252] In a twenty-fifth aspect, alone or in combination with one or more of the above aspects, only a portion of the CBGs of the first transmission are successfully received by a second network node, and wherein the second transmission comprises a re-transmission of a portion of the first TB of the first transmission multiplexed with at least a portion of the second TB a transmission of a plurality of second CBGs for the second TB.
[0253] In a twenty-sixth aspect, alone or in combination with one or more of the above aspects, the transmissions correspond to uplink transmissions, downlink transmission, or sidelink transmissions.
[0254] In a twenty-seventh aspect, alone or in combination with one or more of the above aspects, the uplink transmissions correspond to PUSCH transmissions, wherein the downlink transmissions correspond to PDSCH transmissions, wherein the sidelink transmissions correspond to PSSCH transmissions, wherein the control channel transmission corresponds to a DCI / PDCCH, wherein the feedback information is included in a UCI / PUCCH, wherein the control channel transmission corresponds to a SCI / PSCCH.
[0255] In a twenty-eighth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: determine an amount of information bits for the one or more second CBGs of the plurality of second CBGs for the second TB based on a number of received CBGs of the first transmission indicated by the feedbackinformation; and, wherein the first TB and the second TB are associated with a same HARQ process.
[0256] Accordingly, wireless communication devices may perform enhanced CBG based retransmission operations for wireless communication devices. By performing enhanced CBG based re-transmission operations, such as with TB multiplexing, throughput can be increased, and latency can be reduced through the reduced transmission of redundant or received CBGs and / or reduced utilization of reduced coding rates.
[0257] FIG. 12 is a flow diagram illustrating example blocks executed wireless communication device (e.g., a UE or network entity, such as a base station) configured according to an aspect of the present disclosure. The example blocks will also be described with respect to base station 105 as illustrated in FIG. 14. FIG. 14 is a block diagram illustrating base station 105 configured according to one aspect of the present disclosure. Base station 105 includes the structure, hardware, and components as illustrated for base station 105 of FIGS. 2 and / or 4. For example, base station 105 includes controller / processor 240, which operates to execute logic or computer instructions stored in memory 242, as well as controlling the components of base station 105 that provide the features and functionality of base station 105. Base station 105, under control of controller / processor 240, transmits and receives signals via wireless radios 1401a-t and antennas 234a-t. Wireless radios 1401a-t includes various components and hardware, as illustrated in FIG. 2 for base station 105, including modulator / demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230. As illustrated in the example of FIG. 14, memory 242 stores CBG logic 1402, TB logic 1403, CBG retransmission logic 1404, scheduling data 1405, CBG data 1406, CBG re-transmission data 1407, and settings data 1408. The data (1402-1408) stored in the memory 242 may include or correspond to the data (406, 408, 442, and / or 444) stored in the memory 432 of FIG. 4.
[0258] At block 1200, a wireless communication device, such as a UE or a network device (e.g., a base station 105), receives a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB. The first transmission may include or correspond to one or more of the first transmission 452 of FIG. 4, the first PDSCH transmission of FIG. 5, the first PUSCH transmission of FIG. 6, the first PSSCH transmission of FIG. 7, or one of the transmissions of FIG. 8 or 9. The first TB may include or correspond to a TB of the transmissions above, including TB0. For example, the UE 115 may receive the firsttransmission 452 from the base station 105 including a first TB (e.g., TBO). To illustrate, UE 115 receives a PDSCH via wireless radios 1301a-r and antennas 252a-r and including CBGs for a first TB. As another example, the base station 105 may receive the first transmission 452 from the UE 115 including a first TB (e.g., TBO). To illustrate, the base station 105 receives a first PUSCH via wireless radios 1401a-t and antennas 234a-t and including CBGs for a first TB.
[0259] At block 1201, the wireless communication device obtains scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing. The scheduling information may include or correspond to one or more of the scheduling information 406 of FIG. 4 or the scheduling information of the control transmissions, DCIs, or SCIs of FIGS. 4-8. For example, the UE 115 may receive a DCI or SCI including scheduling information or may transmit an SCI including scheduling information as described with reference to FIGS. 4-8. Additionally, or alternatively, the UE 115 or the base station 105 may generate the scheduling information based on decoding the CBGs of the first transmission or based on received feedback information (e.g., acknowledgement information 408) as described with reference to FIGS. 4-8. As illustrative examples, the scheduling information may include or correspond to one or more resource allocation information, MCS information, CBGTI, CBGFI, NDI, RV information, antenna port information, layer information, codeword information, or a combination thereof.
[0260] At block 1202, the wireless communication device receives, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB. The second transmission may include or correspond to one or more of the first transmission 452 of FIG. 4, the first PDSCH transmission of FIG. 5, the first PUSCH transmission of FIG. 6, the first PSSCH transmission of FIG. 7, or one of the transmissions of FIG. 8 or 9. The second TB may include or correspond to a multiplexed TB of the transmissions above, including TB1-TB3. For example, the UE 115 may receive the second transmission 458 from the base station 105 including at least one CBG of the first TB (e.g., TBO) and at least one CBG of a second TB (e.g., TB 1). To illustrate, UE 115 receives a PDSCH via wireless radios 1301a-r and antennas 252a-r and including CBGs for a first TB and for a second TB where the PDSCH is a re-transmission of another, earlier PDSCH which included CBGs for the first TB. As another example, the base station 105 may receive the second transmission 458 from the UE 115 including atleast one CBG of the first TB (e.g., TBO) and at least one CBG of a second TB (e.g., TB1). To illustrate, the base station 105 receives a second PUSCH via wireless radios 1401a-t and antennas 234a-t and including CBGs for a first TB and a second TB where the PDSCH is a re-transmission of another, earlier PDSCH which included CBGs for the first TB.
[0261] The wireless communication device (e.g., such as a UE or base station) may execute additional blocks (or the wireless communication device may be configured further perform additional operations) in other implementations. For example, the wireless communication device may perform one or more operations as described with reference to FIGS. 4-10. As another example, the wireless communication device may perform one or more aspects as described above with reference to FIGS. 11 and 13 or one or more aspects as presented below.
[0262] In a first aspect, to obtain the scheduling information the wireless communication device is further configured to: generate the scheduling information based on received CBGs of the first TB of the first transmission; and transmit the scheduling information for the second transmission, the scheduling information indicating the one or more CBGs of the plurality of CBGs for the first TB and the one or more second CBGs of the plurality of second CBGs for the second TB for the second transmission.
[0263] In a second aspect, alone or in combination with the first aspect, to obtain the scheduling information the wireless communication device is configured to: transmit feedback information for the first transmission, the feedback information indicating acknowledgement information for decoded CBGs of the first TB of the first transmission; and receive the scheduling information for the second transmission responsive to transmitting the feedback information (e.g., generated based on) for the first transmission.
[0264] In a third aspect, alone or in combination with one or more of the above aspects, the at wireless communication device is further configured to: determine all valid CBGs of the plurality of CBGs of the first TB for the first transmission based on a CBG transmission information (CBGTI) field of a control channel transmission (e.g., e.g., CBGTI field per TB of scheduling information or a DCI); decode the determined valid CBGs of the first transmission based on the control channel transmission; and generate feedback information for the first transmission based on results of the decoding, wherein a decoded valid CBG is indicated by an ACK and non-decoded CBGs and invalid CBGs are indicated by a NACK.
[0265] In a fourth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is further configured to: determine based on a second control channel transmission, a number of TBs to be decoded; determine based on the second control channel transmission, valid CBGs for each TB of the TBs to be decoded for the second transmission; decode the determined valid CBGs for the second transmission based on the second control channel transmission; and generate second feedback information for the second transmission based on results of the decoding.
[0266] In a fifth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: determine for each TB of the plurality of TBs to be decoded, an amount of bits (e.g., K value) for each code block (CB) for each respective valid CBG based on a total resource allocation of the second control channel transmission; and determine, for each TB of the plurality of TBs to be decoded (e.g., based on per TB signaling of MCS), a modulation coding scheme (MCS) configured for the respective TB, wherein the decoding is performed based on the determined amount of bits for each CB and the determined MCS.
[0267] In a sixth aspect, alone or in combination with one or more of the above aspects, the wireless communication device is configured to: determine whether to schedule the plurality of second CBGs for the second TB in the second transmission based on decoding CBGs of the first transmission, wherein the second transmission comprises a retransmission of at least a portion of the first TB.
[0268] In a seventh aspect, alone or in combination with one or more of the above aspects, to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine a number of CBGs that were received based on the decoded CBGs of the first transmission; determine whether the number of CBGs that were received is greater than or equal to a threshold number of passing CBGs for multiple TB CBG retransmission; and determine to schedule the second TB in the second transmission based on the number of CBGs that were received being greater than or equal to the threshold number of passing CBGs; or determine to not schedule the second TB in the second transmission based on the number of CBGs that were received being less than the threshold number of passing CBGs.
[0269] In an eighth aspect, alone or in combination with one or more of the above aspects, to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine a number of multiplexed TBs for the first transmission based on the decoded CBGs of the firsttransmission; determine whether the number of multiplexed TBs for the first transmission is greater than or equal to a threshold number of multiplexed TBs for multiple TB CBG retransmission; and determine to schedule the second TB in the second transmission based on the number of multiplexed TBs being less than the threshold number of multiplexed TBs; or determine to not schedule the second TB in the second transmission based on the number of multiplexed TBs being greater than or equal to the threshold number of multiplexed TBs.
[0270] In a ninth aspect, alone or in combination with one or more of the above aspects, to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to schedule the second TB in the second transmission based on: a number of CBGs that were received being greater than or equal to a threshold number of passing CBGs; and a number of multiplexed TBs being less than the threshold number of multiplexed TBs.
[0271] In a tenth aspect, alone or in combination with one or more of the above aspects, to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to not schedule the second TB in the second transmission based on: a number of CBGs that were received being less than a threshold number of passing CBGs; or a number of multiplexed TBs being greater than or equal to a threshold number of multiplexed TBs.
[0272] Accordingly, wireless communication devices may perform enhanced CBG based retransmission operations for wireless communication devices. By performing enhanced CBG based re-transmission operations, such as with TB multiplexing, throughput can be increased, and latency can be reduced through the reduced transmission of redundant or received CBGs and / or reduced utilization of reduced coding rates.
[0273] Those of skill in the art would understand that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0274] Components, the functional blocks, and the modules described herein with respect to FIGS. 1-14 include processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, among other examples, or any combination thereof. Software shall be construed broadly to meaninstructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, application, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise. In addition, features discussed herein may be implemented via specialized processor circuitry, via executable instructions, or combinations thereof.
[0275] Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. Skilled artisans will also readily recognize that the order or combination of components, methods, or interactions that are described herein are merely examples and that the components, methods, or interactions of the various aspects of the present disclosure may be combined or performed in ways other than those illustrated and described herein.
[0276] The various illustrative logics, logical blocks, modules, circuits and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. The interchangeability of hardware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0277] The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logicdevice, 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, or, any conventional processor, controller, microcontroller, or state machine. In some implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuitry that is specific to a given function.
[0278] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof. Implementations of the subject matter described in this specification also may be implemented as one or more computer programs, that is one or more modules of computer program instructions, encoded on a computer storage media for execution by, or to control the operation of, data processing apparatus.
[0279] If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein may be implemented in a processor-executable software module which may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that may be enabled to transfer a computer program from one place to another. A storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable readonly memory (EEPROM), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Also, any connection may be properly termed a computer-readable medium. Disk and disc, as used herein, includes compact disc (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 should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codesand instructions on a machine readable medium and computer-readable medium, which may be incorporated into a computer program product.
[0280] Various modifications to the implementations described in this disclosure may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to some other implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.
[0281] Additionally, a person having ordinary skill in the art will readily appreciate, the terms “upper” and “lower” are sometimes used for ease of describing the figures, and indicate relative positions corresponding to the orientation of the figure on a properly oriented page, and may not reflect the proper orientation of any device as implemented.
[0282] Certain features that are described in this specification in the context of separate implementations also may be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also may be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0283] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one or more example processes in the form of a flow diagram. However, other operations that are not depicted may be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims may be performed in a different order and still achieve desirable results.
[0284] As used herein, including in the claims, the term “or,” when used in a list of two or more items, means that any one of the listed items may be employed by itself, or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, or C, the composition may contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination. Also, as used herein, including in the claims, “or” as used in a list of items prefaced by “at least one of’ indicates a disjunctive 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 (that is A and B and C) or any of these in any combination thereof. The term “substantially” is defined as largely but not necessarily wholly what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by a person of ordinary skill in the art. In any disclosed implementations, the term “substantially” may be substituted with “within [a percentage] of’ what is specified, where the percentage includes .1, 1, 5, or 10 percent.
[0285] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
CLAIMSWHAT IS CLAIMED IS:
1. A wireless communication device, comprising: one or more processors; and one or more memories coupled with the one or more processors and storing processor-executable code that, when executed by the one or more processors, is configured to cause the wireless communication device to: transmit a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtain scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and transmit, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
2. The wireless communication device of claim 1, wherein to obtain the scheduling information the wireless communication device is configured to: receive feedback information for the first transmission, the feedback information indicating acknowledgement information for each CBG of the plurality of CBGs of the first TB of the first transmission; and generate the scheduling information for the second transmission based on the feedback information for the first transmission, wherein the wireless communication device is further configured to: transmit the scheduling information.
3. The wireless communication device of claim 1, wherein to obtain the scheduling information the wireless communication device is configured to: receive the scheduling information for the second transmission, the scheduling information indicating the plurality of second CBGs for the second TB.
4. The wireless communication device of claim 1, wherein the wireless communication device is further configured to:determine an amount CBGs of the plurality of second CBGs of the second TB to include in the second transmission based on an amount of received CBGs for the first transmission; and determine a TBS size for the second TB of the second transmission based on an amount of valid code blocks (CBs) mapped to the determined amount CBGs for the second TB and on a CB size of each valid CB.
5. The wireless communication device of claim 1, wherein the scheduling information is included in a group-common DCI, and wherein each TB of the second transmission is associated with a same (HARQ) process number.
6. The wireless communication device of claim 1, wherein the scheduling information includes signaling information for the second transmission on a per TB basis, and wherein the scheduling information indicates CBG transmission information (CBGTI), CBG flushing out information (CBGFI), a new data indicator, a redundancy version (RV), an antenna port, and an amount of layers for each TB included in the second transmission.
7. The wireless communication device of claim 1, wherein the scheduling information indicates a modulation coding scheme (MCS) for each TB included in the second transmission.
8. The wireless communication device of claim 1, wherein to transmit the second transmission the wireless communication device is configured to: map scheduled CBGs for each to TB of the second transmission to corresponding CBG positions of the second transmission based on a time or frequency hopping scheme, wherein at least one CBG position of second CBG positions for the CBGs of the first TB for the second transmission corresponds to a different CBG position than at least one CBG position of first CBG positions for the CBGs of the first TB for the first transmission.
9. The wireless communication device of claim 8, wherein to map the scheduled CBGs for each to TB of the second transmission to corresponding CBGpositions of the second transmission based on the time or frequency hopping scheme the wireless communication device is configured to: map the scheduled CBGs based on resource grid information or based on a dynamic mapping indication.
10. The wireless communication device of claim 1, wherein the wireless communication device is further configured to: transmit or receive capability information indicating support for multiplexing TB across CBG based re-transmission, a maximum amount of TBs that can be multiplexed across CBG based re-transmission, or both; or transmit or receive configuration information indicating a threshold amount of TBs that can be multiplexed across CBG based re-transmission, threshold amount of successful or failed CBGs to enable TB multiplexing across CBG based re-transmission, or both.
11. The wireless communication device of claim 1, wherein to transmit the second transmission the wireless communication device is configured to: determine an amount of received CBGs of the first TB, an amount of not received CBGs of the first TB, or both, based on the scheduling information for the second transmission; determine an amount of available CBGs for the second transmission based on the amount of received CBGs, the amount of not received CBGs, or both; and select the second TB based on the determined amount of available CBGs.
12. The wireless communication device of claim 1, wherein the wireless communication device is further configured to: receive second feedback information for the second transmission, the second feedback information indicating second acknowledgement information for the CBGs of the first TB included in the second transmission and for the second CBGs of the second TB included in the second transmission; generate a third transmission based on the second feedback information and based on a third TB; andtransmit the third transmission, wherein the third transmission comprises a retransmission of a portion of the second TB of the second transmission and a transmission of a plurality of third CBGs for the third TB.
13. The wireless communication device of claim 1, wherein the wireless communication device is further configured to: receive a control channel transmission including the scheduling information for the second transmission, wherein the control channel transmission is downlink control information (DCI) or sidelink control information (SCI), wherein the scheduling information includes a modulation coding scheme (MCS), a new data indicator (NDI), a redundancy version (RV), CBG transmission information (CBGTI), and CBG flushing out information (CBGFI) for each TB; and determine that the second transmission includes CBGs for the second TB based on the scheduling information.
14. The wireless communication device of claim 1, wherein the wireless communication device is further configured to: determine to include the second CBGs for the second TB in the second transmission based on received feedback information for the first transmission; and transmit a control channel transmission including the scheduling information for the second transmission, the scheduling information indicating the second CBGs for the second TB, wherein the control channel transmission is downlink control information (DCI) or sidelink control information (SCI), and wherein the scheduling information includes a modulation coding scheme (MCS), a new data indicator (NDI), a redundancy version (RV), CBG transmission information (CBGTI), and CBG flushing out information (CBGFI) for each TB.
15. The wireless communication device of claim 1, wherein the wireless communication device is further configured to: receive feedback information for the first transmission, the feedback information indicating acknowledgement information for CBGs of the first TB of the first transmission; and determine whether to include the plurality of second CBGs for the second TB in the second transmission based on the feedback information.
16. The wireless communication device of claim 15, wherein to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine an amount of CBGs that were acknowledged as being received based on the feedback information; determine whether the amount of CBGs that were acknowledged as being received is greater than or equal to a threshold amount of passing CBGs for multiple TB CBG retransmission; and determine to include the second TB in the second transmission based on the amount of CBGs that were acknowledged as being received being greater than or equal to the threshold amount of passing CBGs; or determine to not include the second TB in the second transmission based on the amount of CBGs that were acknowledged as being received being less than the threshold amount of passing CBGs.
17. The wireless communication device of claim 15, wherein to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine an amount of multiplexed TBs for the first transmission based on the feedback information; determine whether the amount of multiplexed TBs for the first transmission is greater than or equal to a threshold amount of multiplexed TBs for multiple TB CBG retransmission; and determine to include the second TB in the second transmission based on the amount of multiplexed TBs being less than the threshold amount of multiplexed TBs; or determine to not include the second TB in the second transmission based on the amount of multiplexed TBs being greater than or equal to the threshold amount of multiplexed TBs.
18. The wireless communication device of claim 15, wherein to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to include the second TB in the second transmission based on:an amount of CBGs that were acknowledged as being received being greater than or equal to a threshold amount of passing CBGs; and an amount of multiplexed TBs being less than the threshold amount of multiplexed TBs.
19. The wireless communication device of claim 15, wherein to determine whether to include the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to not include the second TB in the second transmission based on: an amount of CBGs that were acknowledged as being received being less than a threshold amount of passing CBGs; or an amount of multiplexed TBs being greater than or equal to a threshold amount of multiplexed TBs.
20. A wireless communication device for wireless communication, comprising: one or more processors; and one or more memories coupled with the one or more processors and storing processor-executable code that, when executed by the one or more processors, is configured to cause the wireless communication device to: receive a first transmission, the first transmission corresponding to a first transport block (TB) and including a plurality of code block groups (CBGs) for the first TB; obtain scheduling information for a second transmission and indicating a CBG based retransmission with TB multiplexing; and receive, based on the scheduling information, the second transmission including one or more CBGs of the plurality of CBGs for the first TB and one or more second CBGs of a plurality of second CBGs for a second TB.
21. The wireless communication device of claim 20, wherein to obtain the scheduling information the wireless communication device is configured to: generate the scheduling information based on received CBGs of the first TB of the first transmission; andtransmit the scheduling information for the second transmission, the scheduling information indicating the one or more CBGs of the plurality of CBGs for the first TB and the one or more second CBGs of the plurality of second CBGs for the second TB for the second transmission.
22. The wireless communication device of claim 20, wherein to obtain the scheduling information the wireless communication device is configured to: transmit feedback information for the first transmission, the feedback information indicating acknowledgement information for decoded CBGs of the first TB of the first transmission; and receive the scheduling information for the second transmission responsive to transmitting the feedback information for the first transmission.
23. The wireless communication device of claim 20, wherein the wireless communication device is further configured to: determine all valid CBGs of the plurality of CBGs of the first TB for the first transmission based on a CBG transmission information (CBGTI) field of a control channel transmission; decode the determined valid CBGs of the first transmission based on the control channel transmission; and generate feedback information for the first transmission based on results of the decoding, wherein a decoded valid CBG is indicated by a positive acknowledgment (ACK) and non-decoded CBGs and invalid CBGs are indicated by a negative acknowledgment (NACK).
24. The wireless communication device of claim 23, wherein the wireless communication device is further configured to: determine, based on a second control channel transmission, an amount of TBs to be decoded; determine, based on the second control channel transmission, valid CBGs for each TB of the TBs to be decoded for the second transmission; decode the determined valid CBGs for the second transmission based on the second control channel transmission; andgenerate second feedback information for the second transmission based on results of the decoding.
25. The wireless communication device of claim 24, wherein the wireless communication device is further configured to: determine for each TB of a plurality of TBs to be decoded for the second transmission, an amount of bits for each code block (CB) for each respective valid CBG based on a total resource allocation of the second control channel transmission; and determine, for each TB of the plurality of TBs to be decoded, a modulation coding scheme (MCS) configured to for the respective TB, wherein the decoding is performed based on the determined amount of bits for each CB and the determined MCS.
26. The wireless communication device of claim 21, wherein the wireless communication device is further configured to: determine whether to schedule the plurality of second CBGs for the second TB in the second transmission based on decoding CBGs of the first transmission, wherein the second transmission comprises a re-transmission of at least a portion of the first TB.
27. The wireless communication device of claim 26, wherein to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine an amount of CBGs that were received based on the decoded CBGs of the first transmission; determine whether the amount of CBGs that were received is greater than or equal to a threshold amount of passing CBGs for multiple TB CBG retransmission; and determine to schedule the second TB in the second transmission based on the amount of CBGs that were received being greater than or equal to the threshold amount of passing CBGs; or determine to not schedule the second TB in the second transmission based on the amount of CBGs that were received being less than the threshold amount of passing CBGs.
28. The wireless communication device of claim 26, wherein to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine an amount of multiplexed TBs for the first transmission based on the decoded CBGs of the first transmission; determine whether the amount of multiplexed TBs for the first transmission is greater than or equal to a threshold amount of multiplexed TBs for multiple TB CBG retransmission; and determine to schedule the second TB in the second transmission based on the amount of multiplexed TBs being less than the threshold amount of multiplexed TBs; or determine to not schedule the second TB in the second transmission based on the amount of multiplexed TBs being greater than or equal to the threshold amount of multiplexed TBs.
29. The wireless communication device of claim 26, wherein to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to schedule the second TB in the second transmission based on: an amount of CBGs that were received being greater than or equal to a threshold amount of passing CBGs; and an amount of multiplexed TBs being less than the threshold amount of multiplexed TBs.
30. The wireless communication device of claim 26, wherein to determine whether to schedule the second CBGs for the second TB in the second transmission the wireless communication device is configured to: determine to not schedule the second TB in the second transmission based on: an amount of CBGs that were received being less than a threshold amount of passing CBGs; or an amount of multiplexed TBs being greater than or equal to a threshold amount of multiplexed TBs.
Citation Information
Patent Citations
Multiplexing code block group level and transport block level transmission and new data indications
US20190074937A1
User terminal and radio communication method
US20190253204A1
Method for transmitting HARQ-ACK signal in wireless communication system, and apparatus therefor
US20190379489A1
User terminal and radio communication method
US20200014491A1