Methods for DCI configuration in case of mixed tb

Abstract

An apparatus including at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a new data indicator bit has toggled; based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

Description

M ETHODS FOR DCI CONFIGURATION I N CASE OF MIXED TBRELATED APPLICATION

[0001] This application claims priority to US provisional Application No. 63 / 698912 filed September 25, 2024, which is incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] The example and non-limiting embodiments relate generally to a downlink control information configuration and, more particularly, to re-transmission of a code block.BRIEF DESCRIPTION OF PRIOR DEVELOPMENTS

[0003] Use of a HARQ process for re-transmission of a group of code blocks is known.SUMMARY OF THE INVENTION

[0004] The following summary is merely intended to be an example. The summary is not intended to limit the scope of the claims.

[0005] In accordance with one aspect, an example apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a new data indicator bit has toggled; based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0006] In accordance with another aspect, an example method is provided comprising: determining whether a new data indicator bit has toggled; and based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0007] In accordance with another aspect, an example apparatus is provided comprising: means for determining whether a new data indicator bit has toggled; and means for, based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0008] In accordance with another aspect, an example apparatus is provided with a non- transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether a new data indicator bit has toggled; and based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0009] In accordance with another aspect, an example apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

[0010] In accordance with another aspect, an example method is provided comprising: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

[0011] In accordance with another aspect, an example apparatus is provided comprising: means for determining whether to toggle a new data indicator bit; means for determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code blockgroup comprises at least one of retransmitted data or new data; and means for transmitting the data to a user equipment.

[0012] In accordance with another aspect, an example apparatus is provided with a non- transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

[0013] In accordance with another aspect, an example apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and receiving the scheduled data channel based, at least partially, on the downlink control information.

[0014] In accordance with another aspect, an example method is provided comprising: receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and receiving the scheduled data channel based, at least partially, on the downlink control information.

[0015] In accordance with another aspect, an example apparatus is provided comprising: means for receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and means for receiving the scheduled data channel based, at least partially, on the downlink control information.

[0016] In accordance with another aspect, an example apparatus is provided with a non- transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: receiving a downlinkcontrol information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and receiving the scheduled data channel based, at least partially, on the downlink control information.

[0017] In accordance with another aspect, an example apparatus is provided comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and sending the scheduled data channel based, at least partially, on the downlink control information.

[0018] In accordance with another aspect, an example method is provided comprising: sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and sending the scheduled data channel based, at least partially, on the downlink control information.

[0019] In accordance with another aspect, an example apparatus is provided comprising: means for sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and means for sending the scheduled data channel based, at least partially, on the downlink control information.

[0020] In accordance with another aspect, an example apparatus is provided with a non- transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and sending the scheduled data channel based, at least partially, on the downlink control information.

[0021] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are provided in subject matter of the dependent claims.BRIEF DESCRIPTION OF DRAWINGS

[0022] The foregoing aspects and other features are explained in the following description, taken in connection with the accompanying drawings, wherein:

[0023] FIG. 1 is a block diagram of one possible and non-limiting example system in which the example embodiments may be practiced;

[0024] FIG. 2 is a diagram illustrating an example of a HARQ operation scenario of a homogeneous TB (initial Tx or Re-Tx) transmission per HARQ process (a legacy scheme);

[0025] FIG. 3 is a diagram illustrating a process for a DCI field (including NDI and CBGTI) configuration for support of the mixed TB transmission;

[0026] FIG. 3A is an example of an interpretation of HARQ-related DCI fields depicted in the form of pseudo code and with associated text explanation;

[0027] FIG. 4 is a diagram illustrating an example of a HARQ operation scenario of a mixed (heterogeneous) TB transmission per HARQ process comprising features as described herein;

[0028] FIG. 5 is an example of a HARQ state transition diagram for mixed TB support comprising features as described herein;

[0029] FIG. 6 is a diagram illustrating an example of a HARQ operation scenario of a mixed (heterogeneous) TB transmission per HARQ process comprising features as described herein;

[0030] FIG. 7 is a diagram illustrating an example method;

[0031] FIG. 8 is a diagram illustrating an example method;

[0032] FIG. 9 is a diagram illustrating an example method; and

[0033] FIG. 10 is a diagram illustrating an example method.DETAILED DESCRIPTION

[0034] The following abbreviations that may be found in the specification and / or the drawing figures are defined as follows:3GPP third generation partnership project5G fifth generation5GC 5G core network6G sixth generation6G PHY sixth generation physical layerACK acknowledgementAMF access and mobility management functionCBG code block groupCB(G)s code block groupsCBGTI CBG transmission informationCRC cyclic redundancy checkCU central unitDCI downlink control informationDL downlinkDU distributed unit eNB (or eNodeB) evolved Node B (e.g., an LTE base station)EN-DC E-UTRA-NR dual connectivity en-gNB or En-gNB node providing NR user plane and control plane protocol terminations towards the UE, and acting as secondary node in EN-DCE-UTRA evolved universal terrestrial radio access, i.e., the LTE radio access technology gNB (or gNodeB) base station for 5G / NR, i.e., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GCHARQ hybrid automatic repeat request)I / F interfaceLDPC low density parity checkLTE long term evolutionMAC medium access controlMCS modulation and coding schemeMME mobility management entityNACK negative acknowledgementNDI new data indicator ng or NG next generation ng-eNB or NG-eNB next generation eNBNR new radioN / W or NW networkPDCCH physical downlink control channelPDCP packet data convergence protocolPDSCH physical data shared channelPDU packet data unitPHY physical layerPRB physical resource blockPUSCH physical uplink shared channelPxSCH physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH)RAN radio access networkRel releaseRe-Tx re-transmission (such as of the previously unsuccessfully transmitted CB(G) for example)RLC radio link controlRRH remote radio headRRC radio resource controlRU radio unitRV redundancy versionRx receiverSDAP service data adaptation protocolSGW serving gatewaySMF session management functionTB transport blockTBS transport block sizeTS technical specificationTx transmitterUE user equipment (e.g., a wireless, typically mobile device)UL uplinkUPF user plane function

[0035] Turning to FIG. 1 , this figure shows a block diagram of one possible and non-limiting example in which the examples may be practiced. A user equipment (UE) 110, radio access network (RAN) node 170, and network element(s) 190 are illustrated. Examples of network equipment, network device, or a network entity might be understood to include, at least part of, a transmission reception point or a cell or a gNB or node for example. In the example of FIG. 1, the user equipment (UE) 110 is in wireless communication with a wireless network 100. A UE is a wireless device that can access the wireless network 100. The UE 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected through one or more buses 127. Each of the one or more transceivers 130 includes a receiver, Rx, 132 and a transmitter, Tx, 133. The one or more buses 127 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, and the like. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. The UE 110 includes a module 140, comprising one of or both parts 140-1 and / or 140-2, which may be implemented in a number of ways. The module 140 may be implemented in hardware as module 140-1, such as being implemented as part of the one or more processors 120. The module 140-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and isexecuted by the one or more processors 120. For instance, the one or more memories 125 and the computer program code 123 may be configured to, with the one or more processors 120, cause the user equipment 110 to perform one or more of the operations as described herein. The UE 110 communicates with RAN node 170 via a wireless link 111.

[0036] The RAN node 170 in this example is a base station that provides access by wireless devices such as the UE 110 to the wireless network 100. The RAN node 170 may be, for example, a base station for 5G, also called New Radio (NR). In 5G, the RAN node 170 may be a NG-RAN node, which is defined as either a gNB or a ng-eNB. A gNB is a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to a 5GC (such as, for example, the network element(s) 190). The ng-eNB is a node providing E-UTRA user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. The NG-RAN node may include multiple gNBs, which may also include a central unit (CU) (gNB-CU) 196 and distributed unit(s) (DUs) (gNB-DUs), of which DU 195 is shown. Note that the DU may include or be coupled to and control a radio unit (RU). The gNB-CU is a logical node hosting RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU. The Fl interface is illustrated as reference 198, although reference 198 also illustrates a link between remote elements of the RAN node 170 and centralized elements of the RAN node 170, such as between the gNB-CU 196 and the gNB-DU 195. The gNB-DU is a logical node hosting RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by gNB-CU. One gNB-CU supports one or multiple cells. One cell is supported by only one gNB- DU. The gNB-DU terminates the Fl interface 198 connected with the gNB-CU. Note that the DU 195 is considered to include the transceiver 160, e.g., as part of a RU, but some examples of this may have the transceiver 160 as part of a separate RU, e.g., under control of and connected to the DU 195. The RAN node 170 may also be an eNB (evolved NodeB) base station, for LTE (long term evolution), or any other suitable base station or node.

[0037] The RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / W I / F(s)) 161, and one or more transceivers 160 interconnected through one or more buses 157. Each of the one or more transceivers 160includes a receiver, Rx, 162 and a transmitter, Tx, 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. The CU 196 may include the processor(s) 152, memories 155, and network interfaces 161. Note that the DU 195 may also contain its own memory / memories and processor(s), and / or other hardware, but these are not shown.

[0038] The RAN node 170 includes a module 150, comprising one of or both parts 150-1 and / or 150-2, which may be implemented in a number of ways. The module 150 may be implemented in hardware as module 150-1, such as being implemented as part of the one or more processors 152. The module 150-1 may be implemented also as an integrated circuit or through other hardware such as a programmable gate array. In another example, the module 150 may be implemented as module 150-2, which is implemented as computer program code 153 and is executed by the one or more processors 152. For instance, the one or more memories 155 and the computer program code 153 are configured to, with the one or more processors 152, cause the RAN node 170 to perform one or more of the operations as described herein. Note that the functionality of the module 150 may be distributed, such as being distributed between the DU 195 and the CU 196, or be implemented solely in the DU 195.

[0039] The one or more network interfaces 161 communicate over a network such as via the links 176 and 131. Two or more gNBs 170 may communicate using, e.g., link 176. The link 176 may be wired or wireless or both and may implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interface for other standards.

[0040] The one or more buses 157 may be address, data, or control buses, and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers 160 may be implemented as a remote radio head (RRH) 195 for LTE or a distributed unit (DU) 195 for gNB implementation for 5G, with the other elements of the RAN node 170 possibly being physically in a different location from the RRH / DU, and the one or more buses 157 could be implemented in part as, for example, fiber optic cable or other suitable network connection to connect the other elements (e.g., a centralunit (CU), gNB-CU) of the RAN node 170 to the RRH / DU 195. Reference 198 also indicates those suitable network link(s).

[0041] It is noted that description herein indicates that “cells” perform functions, but it should be clear that equipment which forms the cell will perform the functions. The cell makes up part of a base station. That is, there can be multiple cells per base station. For example, there could be three cells for a single carrier frequency and associated bandwidth, each cell covering one- third of a 360 degree area so that the single base station’ s coverage area covers an approximate oval or circle. Furthermore, each cell can correspond to a single carrier and a base station may use multiple carriers. So if there are three 120 degree cells per carrier and two carriers, then the base station has a total of 6 cells.

[0042] The wireless network 100 may include a network element or elements 190 that may include core network functionality, and which provides connectivity via a link or links 181 with a further network, such as a telephone network and / or a data communications network (e.g., the Internet). Such core network functionality for 5G may include access and mobility management function(s) (AMF(S)) and / or user plane functions (UPF(s)) and / or session management function(s) (SMF(s)). Such core network functionality for LTE may include MME (Mobility Management Entity ) / SGW (Serving Gateway) functionality. These are merely exemplary functions that may be supported by the network element(s) 190, and note that both 5G and LTE functions might be supported. The RAN node 170 is coupled via a link 131 to a network element 190. The link 131 may be implemented as, e.g., an NG interface for 5G, or an SI interface for LTE, or other suitable interface for other standards. The network element 190 includes one or more processors 175, one or more memories 171, and one or more network interfaces (N / W I / F(s)) 180, interconnected through one or more buses 185. The one or more memories 171 include computer program code 173. The one or more memories 171 and the computer program code 173 are configured to, with the one or more processors 175, cause the network element 190 to perform one or more operations.

[0043] The wireless network 100 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involvesplatform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors 152 or 175 and memories 155 and 171, and also such virtualized entities create technical effects.

[0044] The computer readable memories 125, 155, and 171 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The computer readable memories 125, 155, and 171 may be means for performing storage functions. The processors 120, 152, and 175 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The processors 120, 152, and 175 may be means for performing functions, such as controlling the UE 110, RAN node 170, and other functions as described herein.

[0045] In general, the various embodiments of the user equipment 110 can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digital cameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0046] As is generally known, CBGTI is a mechanism used in wireless communication systems, including 5G, LTE, and WiMAX for example. In wireless communication, data is divided into smaller chunks called code blocks. These code blocks are grouped together intocode block groups (CBGs). CBGs allow for more efficient handling during transmission and retransmission. CBGTI helps to facilitate the transmission of data between a network node (such as a base station for example) and a user equipment, with the grouping of code blocks for efficient data transmission. CBG-based transmission involves sending data in the form of CBGs. A transport block (TB) can be made up of one or more CBGs. The UE may receive CBG-based transmissions based on higher layer configuration parameters. For an initial transmission, the UE may assume that all CBGs are present. For retransmission, the UE may use the CBGTI field in the scheduling DCI (Downlink Control Information) to determine which CBGs are present in the transmission. Each bit in the CBGTI field may indicate whether a specific CBG is transmitted (indicated by a first value, for example, value of “1”) or not transmitted (indicated by a second value, for example, value of “0”). Additionally, a CBG flushing out information (CBGFI) field may indicate whether earlier received instances of the same CBGs are combinable with the retransmitted CBGs. CBGs impact the generation of HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgment) feedback. HARQ-ACK feedback is generated per CBG, balancing the number of feedback bits and retransmission efficiency.

[0047] After a transport block size (TBS) is determined, information bits are generated, and cyclic redundancy check (CRC) is attached to them. This bit sequence is then passed to the code block segmentation block, wherein the bit sequence is segmented into one or more code blocks based on its length. For example, for low density parity check (LDPC) base graph 1 , the maximum code block size is 8448 and, if the input bit sequence (information + CRC) length is larger than this number, it is segmented in multiple code blocks and code block CRC is attached to each of the code blocks. Further details on code block segmentation for LDPC coding can be found in Section 5.2.2 of 3GPP TS 38.212. Each generated code block is subsequently LDPC encoded to generate a codeword, and each codeword is finally rate matched to the number of resources allocated for each code block. It should be noted that although a codeword may comprise single code block, a codeword corresponds to a coded TB which may comprising one or more code blocks. It is interesting to notice here that, in case of re-transmissions, if a certain code block is not scheduled for the re-transmission, the length of the rate matching output is set to zero (0). In other words, in case the code block is not retransmitted, the generated codeword for the code block is completely punctured.

[0048] In 5G NR, each TB transmission is associated with a specific HARQ process number which, in case of failed initial transmission, is re-transmitted until all the code blocks associated to the TB are successfully received. 5G NR introduced the possibility of code block specific re-transmissions, via a specific CBGTI field in the DCI, which contains a bitmap indicating the code block groups (i.e. a group of code block) that are being re-transmitted for the HARQ process. More details are in TS 38.214 including the following excerpt on HARQ-related DCI configurations (NDI, CBGTI):This, however, also means that even if only one code block is failing to be received, the HARQ process gets stuck in re-transmission of the code block and cannot be used for transmission of new data.

[0049] It is proposed transmitting a mixed TB (which may also be referred to as a heterogeneous TB) in a single and same PxSCH transmission, wherein part of the code blocks are re-transmitted code blocks and the other part of the code blocks belong to a new transmission. The approach of a mixed TB would allow full utilization of the HARQ processes, but also presents challenges as, for example, for backward-compatible DCI configuration for signaling of the mixed TB. Care needs to be taken for the term “mixed TB”. According to thecurrent 3GPP NR specification, 1 or 2 transport block(s) is / are supported. The 2nd transport block (TB) is present only if more than four layers of spatial multiplexing are supported in DCI format 1_1. Each TB is processed independently with its own dedicated MCS, NDI, and RV. The term “mixed TB” as used herein should not be interpreted as concatenation of TB 1 and TB 2 (as in current specifications), but rather as a mixture, in a single transmission, of a new data transmission and a re-transmission of a previously unsuccessful transmission. The mixed TB in this context is associated with a common information field in DCI and is processed at both the transmitter and receiver physical layer as a single TB (composed of different CBs possibly containing both new data and re-transmissions) regardless of the mapping of such TB at higher layers.

[0050] In current specifications, NDI being toggled is interpreted as all new data transmission. However, with features as described herein (and as further described below) an NDI being toggled may be interpreted as 1. new data transmission of a 1st data batch, or 2. new data transmission of a 2nd data batch, or 3. new data transmission of the 2nd data batch plus re-Tx of at least part of the 1st data batch. Therefore, with features as described herein, a new feature may be provided for determining that data in a code block group is retransmitted data with a NDI being toggled. Then, in addition, the CBGTI may indicate whether a set of CGBs comprises a retransmission of the 1st data batch or new data of the 2nd data batch (new interpretation of elements being ‘0’).

[0051] For the sake of simplicity of the concept, a group of CB(G)s is designated for the initial transmission as the 1st data batch, whereas another group of CB(G)s is designated for new data transmission to be mixed with a re-transmission of CB(G)s belonging to the 1st data batch as the 2nd data batch hereafter. Note here that current 3GPP NR specifications do not support dedicated information fields of NDI and CBGTI for different data batches. Current 3GPP NR specifications do not support a mixed TB mode of operation.

[0052] In a case of a mixed TB transmission (in other words, multiplexing of multiple different data batches on single PDSCH) support as noted above, a method for indication of the mixed TB needs to be defined in a backward-compatible fashion. It would be beneficialand convenient, such as with 6G for example, to use a same format of the fields as in 5G NR, since CB(G)-based operation is anticipated to be supported in 6G as well. This may comprise:• The relevant DCI fields, i.e., NDI and CBGTI, do not necessarily need be modified in their size nor their interpretation from their current mode of operation in 5G.• Interpretation of these DCI fields of NDI and / or CBGTI can be extended to facilitate support of a mixed TB transmission use case so that the legacy (current) mode of operation is not affected.

[0053] One possible example of a legacy HARQ operation is depicted in FIG. 2; an example of a HARQ operation scenario of a homogeneous TB (initial Tx or Re-Tx) transmission per HARQ process (legacy scheme). Here, the selected HARQ-related DCI fields, i.e., NDI and CGBTI, follow the relevant 3GPP specification (Section 5.1.7 of TS 38.214) with NTB=1, and N=4 and N=2 being considered, where NTB is the maximum number of codewords (TBs) scheduled by DCI and N is the maximum number of CBGs per transport block. In this particular case, two TBs are transmitted sequentially. In this example, the 1st TB consists of 4 CB(G)s, whereas the 2nd TB consists of two CB(G)s. Strictly speaking, CB-wise retransmission (Re-Tx) is not supported by current 3GPP NR specification, but support of this is relatively straightforward. As used herein, to render forward compatible (such as 6G relevance for example), CB or CBG wise HARQ and associated Re-Tx is used interchangeably. CB(G) to resource mapping is assumed to follow a first-to-last fashion, i.e., position of the CB(G) in the coded bits follows the position of the CB(G) in all of the active buffers (frequency-first time-later order, meaning starting from northwest corner first going south, then jump to northeast corner followed by going south again), where the active buffers are buffers that are not yet completed (i.e. not all CBs at the buffer were successfully received). UE reserves soft buffer equivalent to 4 CB(G)s for the 1st TB, then it reserves that for 2 CB(G)s for the 2nd TB. For ACK’ed (successfully received confirmed by CRC success) CB(G)s, the corresponding soft buffers are “flushed out” to MAC layer (indicated by downward chevron in FIG. 2, tagged with “Soft buffer @UE”), whereas NACK’ed (CRC failed) CB(G)s are being kept in the buffer for soft combining with (anticipated) next upcoming Re-Tx’ ed CB(G). In the illustrated example, the 1st TB requires 3 transmissions (1 initial Tx with two Re-Txes), and the 2nd TBrequires 2 transmissions (1 initial Tx with 1 Re-Tx), leading to 5 transmissions altogether. As illustrated with this example, some portions of the reserved resources are not utilized (indicated by empty (white) slots at the middle lane figures under “DL reception @UE”) during Re-Tx phases until the completion of the associated TB and HARQ process. This example showcases the technical problem of the current 3GPP NR HARQ procedure. Even if only one code block is failing to be received, the HARQ process gets stuck in re-transmission of the code block and cannot be used for transmission of new data.

[0054] Features as described herein may be used to facilitate faster CB(G) transmissions by streamlining HARQ procedure via allowing transmission of a heterogeneous / mixed TBs, such as Re-Tx as well as new data transmission for example, without having to change structure of the relevant DCI fields (NDI, CBGTI). This is achieved by introducing an extension of the interpretation of the existing DCI fields and additional HARQ operation states (FIG. 5) in a backward-compatible manner such as, for example, by leaving the relevant DCI fields a same size as currently in 5G NR. FIG. 3 illustrates an example of introducing an extension of the interpretation of the existing DCI fields; DCI field (NDI, CBGTI) configuration for support of the mixed TB transmission. FIG. 5 illustrates an example of additional HARQ operation states; a HARQ state transition diagram of an example scheme for mixed TB support.

[0055] Features as described herein may be used in regard to a method for indication of a mixed TB via extension of the existing conventional DCI (NDI and CBGTI) configuration, but which satisfies a backward-compatibility requirement; with an attached condition that the TBS of the mixed TB may always be the same as a TBS of a previous transmission.

[0056] Herein we introduce a term “data batches”, which indicates data groups with or without different reliability requirements which can be multiplexed in a same slot with a common HARQ process number, a common NDI and a common CBGTI. This is a logical concept which can be mapped to MAC sub PDU group, if deems beneficial, but not limited to. Multiple numbers of data batches can be supported, when piggybacked new data transmission come from a single data batch. For illustrative purposes only, two data batches are described herein. However, more than two data batches may be provided.

[0057] An example embodiment may be provided comprising the following features:e-Tx with piggybacked new data A method may be provided for indication of Re-Tx’ed CB(G) of a 1st data batch together with a piggybacked new data transmission (initial Tx) of a 2nd data batch. In one example embodiment, NDI is toggled indicating a new data transmission while individual CBGTI element(s) corresponding to previously successfully transmitted CB(G)s is / are assigned with a zero (‘0’). i. According to the current legacy 3GPP specification, when NDI is toggled for initial transmission of a TB (“(all CBGs are) new data”), the UE may assume that all CBGs are present. For enabling this feature, that assumption may be modified so that if any element of CBGTI is non-‘l ’ (meaning zero ‘0’) with NDI being toggled, then this should be interpreted by the UE as a “Re-Tx with piggybacked new data” case rather than an error case. In this case, resources associated with CBGTI element being ‘0’ may be repurposed for a new data transmission of the 2nd data batch in order not to waste resources. Re-Tx only with heterogeneous / mixed TB A method may be provided for indication of Re-Tx’ed CB(G) of a 1st data batch together with a Re-Tx’ed CB(G) of a 2nd data batch. In one example embodiment, NDI is not toggled while individual CBGTI element(s) corresponding to previously failed CB(G)s of a 2nd data batch is / are assigned with ‘1’. It is assumed here that individual CBGTI element(s) corresponding to previously failed CB(G)s of the 1st data batch is / are assigned with ‘ 1’ as per legacy. i. The UE may keep track of CBGTI history such that it may be able to identify CBGTI elements belonging to the 1st or 2nd data batch. In short, if the CBGTI element(s) corresponding to the second data batch is / are marked as ‘1’ at the occasion with NDI being not toggled (“Re-Tx only”), interpretation should be as follows: “Those corresponding CBGTI elements have been re-purposed for the 2nd data batch CB(G) transmission and they are failed.”ii. Note here that previously assigned resources for CB(G)s belonging to the 1st data batch can be efficiently used for Re-Tx of CB(G)s belonging to the 2nd data batch, via re-interpretation of the bitmap elements of CBGTI without having to extend / change CBGTI structure. In other words, the CBGTI structure implementing this feature may be the same as a conventional 5G CBGTI structure.As described above, the proposed methods support indication of the mixed TB transmission while keeping the size of the legacy signaling intact, by providing a novel means of interpretation of the previously undefined combination of NDI and CBGTI. .

[0058]

[0059] An example of an overall mechanism of HARQ-related DCI configuration is illustrated in FIG. 3. At step 310 it is determined if a transmission includes new data, such as a transmission with only new data for example. At step 320 it is determined if a transmission includes a re-transmission of previously transmitted data, such as a transmission with only retransmitted data for example. If the transmission comprises new data then, as illustrated with box 301, the DCI configuration may comprise a toggle of the NDI. The portion “Set CBGTI(i) = 1 for all i G {CBG index of scheduled TB}” in box 301 is different from a conventional practice. Currently in 5G NR, whenever NDI is toggled, there is no need for the UE to check CBGTI. Hence, the gNB does not care about configuration of CBGTI either. With features as described herein, a UE may check CBGTI to determine if it is a “new data only transmission” case when all CBGTI elements are ‘ 1’ . Accordingly, the gNB may care for configuration of CBGTI for this example proposed case. If the transmission comprises new re-transmitted data then, as illustrated with box 302, the DCI configuration does not comprise a toggle of the NDI, with setting CBGTI (i) = T for all i G {index of NACK'ed CBGs belonging to the 1stdata batch}, and with setting CBGTI (j) = T for all j G {index of NACK'ed CBGs belonging to the 2nd data batch}. If, at 320 it is determined that the transmission does not comprise retransmitted data then, as illustrated with box 304, the DCI configuration comprises a toggle of the NDI, with setting CBGTI (i) = T for all i G {index of NACK'ed CBGs belonging to the 1stdata batch}, and with setting CBGTI (j) = 'O' for all j G {index of ACK'ed CBGs belonging to the 1stdata batch}.

[0060] As noted above, FIG. 3 illustrates DCI field (NDI, CBGTI) configuration at a network equipment (such as a gNB for example) for support of a mixed TB transmission. A Re-Tx only transmission case is extended to support Re-Tx of a 2nd data batch as well as Re-Tx of a 1st data batch. A new mode of operation, i.e., Re-Tx (of the 1st data batch) with piggybacked new data transmission (of the 2nd data batch), is introduced. These two extended / newly proposed modes are designed to incorporate initial transmission or Re-Tx of the 2nd data batch, which bring about efficient usage of the physical resources.

[0061] The counterpart operation at the UE-side, i.e., interpretation of HARQ-related DCI fields, is depicted in the form of pseudo code, and associated text explanation is provided below and also shown in FIG. 3A.% UE-side NDI, CBGTI interpretation for mixed TB caseCheck(NDI); if (is_NDI_toggled)%% new data CBG existsCheck(CBGTI); if (are_all_CBGTI_elements_ 1 _for_scheduled_TB )%%% initial Tx of the 1stdata batch case = “new data only transmission”; else%%% Re-Tx of NACK’ed CBG(s) of 1stdata batch together with initial Tx of the 2nddata batch case = “Re-Tx with piggybacked new data”; else%% no new data CBGCheck(CBGTI); case = “Re-Tx only transmission”; endNote that for the sake of simplicity, it is assumed that the proposed mixed TB HARQ operation can be handled under the same HARQ process, but the overall concept can be extended to generic cases as well.

[0062] The following illustrate examples based upon whether the NDI is toggled or not toggled.

[0063] In case of NDI being toggled, o When the NDI is toggled (verses the NDI in a previous DO transmission), it means that there is new data transmission.■ New data transmission of the 1stdata batch, or■ New data transmission of the 2nddata batch (as a piggyback) together with Re-Tx of the (previously NACK’ed) 1stdata batch.It is to be noted that although 1stdata batch refers to the very initial transmission for the HARQ process, 2nddata batch refers to any subsequent data batch transmission (with new data) piggybacked in a re-transmission of the HARQ process. o [Introduced new interpretation] In case of all the CBGTI elements being ‘1’: this corresponds to an initial transmission of the 1stdata batch only. o [introduced new case] In case of any element of CBGTI being ‘O’: this corresponds to piggybacked (new data) initial transmission of the 2nddata batch. Assumption here is that all the CBGs at 0 will be occupied by new data of the 2nddata batch.■ Piggybacked new data belonging to the 2nddata batch may be found, in one example implementation, concatenated (appended or linked with) with the re-transmitted data of the 1stdata batch.• Such an implementation simplifies UE tracking of the CBGs belonging to each 1stor 2nddata batch. Since, in this exampleembodiment, new data is always appended (i.e. concatenated) to the re-transmitted data, the UE will always know that retransmitted data is in the 1stdata batch and is always transmitted in front of the new data of the 2ndbatch. In other words, the location of the retransmitted data versus the location of the new piggybacked data will always be set or predetermined.■ This method may be used such that all the resources corresponding to the previously successfully transmitted CB(G)s of the 1stdata batch may be re-purposed for transmission of CB(G)s of the 2nddata batch. This feature will become move clear with review of the examples in FIGs. 4 and 6.

[0064] In case of NDI not toggled (same as the previous NDI) o When the NDI is not toggled (verses the NDI in a previous DCI transmission), it means that there is no new data transmission (that it is a Re-Tx only). This may comprise:■ Re-Tx of the 1stdata batch, or■ Re-Tx of the 2nddata batch, or■ Re-Tx of the 1stdata batch and the 2nddata batch o In case of any previously ACK’ed CB(G)s (per ACK / NACK corresponding to the initial transmission of the 1stdata batch) being ‘1’: Re-Tx only transmission including Re-Tx of the 2nddata batchCan be entirely the 2nddata batch or be with Re-Tx of the 1stdata batch as well (heterogeneous / mixed TB)o In case of all the previously ACK’ed CB(G)s (per ACK7NACK corresponding to the initial transmission of the 1stdata batch) being ‘0’ or all the initial CB(G)s being NACK’ed: Re-Tx (of the 1stdata batch) only transmission

[0065] One example operation scenario of the proposed scheme is illustrated in FIG. 4. To provide a good comparison with the legacy scheme, the example shown in FIG. 4 is assumed with the same use case as in FIG. 2. One conceptual difference lies in that each individual TB from the legacy example is now mapped to the individual data batch. In other words, the example method shown in FIG. 4 assumes that one TB can be split into two data batches; depending on its individual reliability requirement for example. The first data batch comprises the CB(G)s 401, 402, 403, 404.

[0066] Note in FIG. 4, triangle symbol with “!” Inside indicates “CRC fail”, meaning not successfully decoded CB(G), which may be NACK’ed by UE. After the 1st initial transmission 451, the NW is informed as indicated with arrow 461 of the NACK’ed CB(G)s and the ACK’ed CB(G)s. In the example shown in FIG. 4 there are two NACK’ed CB(G)s; the 2nd and 3rd CB(G)s 402, 403 (belonging to the 1st data batch, by definition). In the example shown in FIG. 4 there are two ACK’ed CB(G)s as well; the 1st and 4th CB(G)s 401, 404. Because there exists ACK’ed CB(G)s as well, the reserved resources for these CB(G)s can be re-purposed for the initial transmission of CB(G)s belonging to the 2nd data batch. In this example, for the second transmission 452 the number of ACK’ed CB(G)s401, 404 of the 1st data batch is two (2);. Hence, the NW may prepare two (2) CB(G)s 411 and 412 of the 2nd data batch for “piggyback” of new data.

[0067] At the 2nd transmission 452 (which includes the 1st Re-Tx of 402 and 403), predetermined RV for the previously NACK’ed CB(G)s 402, 403 of the 1st data batch are transmitted as 402’ and 403’ shown in FIG. 4, together with new data 411, 412 of two CB(G)s of the 2nd data batch, by filling up the otherwise empty resources 401’, 404’. Note here that from UE-side, it is not required to secure larger soft buffer memory than the legacy case. The UE can make use of the reserved soft buffer memory for the previously ACK’ed CB(G)s 401, 404, since those must have been flushed out to MAC thanks to successful transmission, as illustrated in the bottom lane of FIG. 4, noted as “Soft buffer @UE (memory-optimized)”. Atthis stage (on occasion of the reception of the 2nd transmission), the UE may take note of the bitmap position of CBGTI being equal to ‘0’ as piggybacked new data positions (CB(G)s of the 2nd MAC sub-PDU group data batch), in the illustrated example the 1st and 4th CBGTI elements. In other words, empty resources 401’, 404’ may be used for the new data 411 and 412. In the example shown in FIG. 4, on occasion of the 2nd transmission 462, there has been determined to have been two CRC failures as noted with the CRC fail triangles 421, 422, i.e., the 3rd CB(G) 403’ of the 1st data batch and the 2nd CB(G) 412 of the 2nd data batch.

[0068] At the 3rd transmission 453, the 3rd bit of CBGTI is marked as ‘1’ for indication of Re-Tx of the 3rd CB(G) 403” of the 1st data batch whereas the 4th bit of CBGTI is marked as ‘1’ for indication of Re-Tx of the 2nd CB(G) 412’ of the 2nd data batch. The UE may keep track of bitmap positions of the piggybacked CB(G)s belonging to the 2nd data batch and, thus, interpretation of CBGTI should be clear to UE. As illustrated in FIG. 4, the overall procedure takes three (3) transmissions 451, 452, 453, which is two transmissions less than the five (5) transmissions in the corresponding legacy case depicted in FIG. 2. It should be noted that in another example, Re-Tx’ed CB(G) may belong to the second batch as well.

[0069] Another example implementation is shown in FIG. 6, which is very similar to the example of FIG. 4, except for the CBGTI usage and interpretation in the 3rd transmission 653. Herein indeed, the CBGTI field (= [0 1 0 1]) refers to the CBG structure in the last transmission where the NDI was toggled (i.e. 2nd transmission 652 in the example), where the 2nd CBG 403’ and 4th CBG 412 failed and are in need of re-transmission. In other words, in this example compared to the one in FIG. 4, every time the NDI field is toggled, the UE changes its reference in terms of data batch location within the CBGs while keeping track of which CBGs belong to which data batch. For example, in this case, at 3rd transmission 653 the 2nd CBG is retransmitted, which belongs to the first data batch and was originally within the 3rd CBG of the TB. Thus, with the example shown in FIG. 6, the CBGTI in the 3rdtransmission 653 is

[0101] rather than the CBGTI in the 3rd transmission 453 shown in FIG. 4 which is

[0011] . This is aligned similar with legacy behavior wherein UE resets its mapping data-to-CBG position every time the NDI field is toggled, with the addition of UE needing to track the data batch each CBG belongs to.

[0070] An example of a complete extended state transition diagram including the novel proposed states as described herein can be found in FIG. 5. The example in FIG. 4 follows the sequence of the initial transmission of CBG_1 (refer to the legends in FIG. 5), Re-Tx with piggybacked new data transmission, and Re-Tx only transmission of CBG_1 and CBG_2. In FIG. 5, the ovals outlined with dotted lines are new steps. CBG_1 generally corresponds to CB(G)s which belong to the 1stdata batch, and CBG_2 generally corresponds to CB(G)s which belong to the 2nddata batch. Close examination of FIG. 5 reveals the fact that the UE should be capable of handling the mixed TB case by keeping track of (storing and comparing) state transition history while identifying bitmap segments for CBG_1 and CBG_2 via bookkeeping of CRC check history of individual CB(G)s. Oval “0” corresponds to an initial Tx regarding CBG_1, oval “1” corresponds to a Re-Tx only regarding CBG_1, oval “2” corresponds to both Re-Tx with piggybacked new data Tx regarding CBG_1 and CBG_2, oval “3” corresponds to Re-Tx regarding both CBG_1 and CBG_2, and oval “4” corresponds to Re-Tx regarding only CBG_2. This is merely one example presented for understanding of an example embodiment and method.

[0071] Features as described herein may be used with a backward-compatible DCI configuration for a TB of retransmitted CBs and newly transmitted CBs. In one type of example, the UE may have previously communicated to the gNB regarding the UE’s capability to support the new type of DCI configuration as described herein. Thus, the gNB will know whether to use a conventional DCI configuration or the new type of DCI configuration when communicating with the UE. Both the UE and the gNB may use historical information regarding previously received and sent DCIs to interpret and configure future DCIs, including CBGTI locations and NACK information. As noted above, in some situations the UE may also be configured to UE ignore all or part of a field.

[0072] In one example embodiment, the size of the 1stdata batch relative to the 2nddata batch may be fixed or predetermined. Thus, the UE would not need to determine the size of the 1stdata batch relative to the 2nddata batch; the size may be assumed based upon the predetermined fixed size. The size may be assumed to be the fixed size. This similarly applies for the gNB. In an alternative example, the size might not be a predetermined fixed size, but may be variable. However, the UE would then need to be able to determine the size of the 1stdata batch relativeto the 2nddata batch, such as with use of additional signaling from the gNB for example. As seen in the examples in FIGs. 4 and 6, the size of the bits for PDSCH mapping may be 4 bits or 2 bits in those examples.

[0073] An alternative option may comprise new signaling to convey this information, but at a cost of increased overhead. This may be, for example, a new field comprising a new mapping rule or information indicative of the mapping, or a first configuration information (i.e CBGTI_1) for retransmitted CBs and a second configuration information (i.e. CBGTI_2) for newly transmitted CBs for the mixed TB etc.

[0074] The new field may comprise, in one example, a flag indicating whether new data is transmitted (for example, piggybacked) within some of the CB(G)s of the scheduled PDSCH. If the flag is toggled, new data piggybacking is assumed by the UE. For example, the UE may interpret the entries of the CBGTI field set to 0 as carrying new data. Differently than the NDI field, this flag might be used only to indicate whether new data is piggybacked in re-transmitted data.

[0075] Alternatively, or additionally, a second configuration information (CBGTI_2) for newly transmitted CB(G)s may be present in the DCI, in addition to a first configuration information CBGTI_1 for retransmitted CB(G)s, such as, for example:• CBGTI_2 has a size equal to the size of CBGTI_1• CBGTI_2 contains a maximum number of Is equal to the number of 0s in CBGTI_1. If the number of Is is larger than the number of 0s, UE ignores all or part of the field.• In one example implementation, CBGTI_1 and CBGTI_2 might become interchangeable after the first re-transmission, in the sense that a CBGTI field might be linked to a certain data batch until the whole data batch is successfully transmitted and piggybacked new data could be then indicated by the “available” CBGTI_1 or CBGTI_2. o For example, in first re-transmission of a PDSCH, the new data piggybacking flag is toggled, meaning that information on the new data CBGs is in CBGTI_2.In second re-transmission of the PDSCH, the new data piggybacking flag is toggled again, meaning that information on the new data CBGs is in a different CBGTI compared to last toggling, i.e. CBGTI_1.• CBGTI_2 might be ignored by the UE if the flag indicating new data piggybacking (if present) indicates that no new data is present.

[0076] With this type of example, there would not be a “common" CBGTI (a non-common CBGTI) because there is a “dedicated" CBGTI for newly transmitted CB(G)s.

[0077] Features as described herein may be used to provide a method to decrease the number of possible HARQ processes and enable transmission of a mixed transport block, comprising a mixture of new data transmission and re-transmission of the previously unsuccessful transmission, in a single PxSCH transmission. This may provide a backward-compatible DCI configuration for a TB of retransmitted CBs and newly transmitted CBs. This may be used in regard to current specifications where a transport block can only contain a newly transmitted data or HARQ retransmitted data.

[0078] A device may receive, from a network node, a downlink control information message indicative of scheduling information of at least one transport block (TB) using one hybrid automatic repeat request (HARQ) process comprising at least a transport block level new data indicator (NDI) and a code block group transmission information (CBGTI) associated with at least a first code block with data for retransmission and a second code block with data for initial transmission. The device may determine scheduling information for a downlink data transmission based on the downlink control information. Thus, new signaling may be provided to convey this information at a cost of increased overhead (i.e., not relying on 5G NR parameters).

[0079] The NDI may indicate whether new data is transmitted associated with at least the first code block or a second code block (i.e. NDI is toggled). The CBGTI may indicate whether a set of CGBs comprises a retransmission of the first code block based on the determination that new data is transmitted associated with at least the second code block (i.e. NDI is toggled, CGBTI 0 corresponds to new data transmission of second batch). The CBGTI may indicatewhether a set of CGBs comprises a retransmission of the first code block or a retransmission of the second code block based on the determination that no new data is transmitted associated with the first code block or the second code block (i.e. NDI is not toggled, CGBTI 1 corresponds to retransmission of the first or the second batch based on CBGTI history). The determination that new data is transmitted associated with first code block or a second code block may be based on the NDI being toggled. The determination that no new data is transmitted associated with first code block or a second code block may be based on the NDI not being toggled.

[0080] Features as described herein may provide:• Faster CB(G) transmissions. Streamlined HARQ procedure• Enabling mix TBs transmission in a backward-compatible manner• Decreased overhead and complexity by reusing same format of the fields as in 5G NR

[0081] In one type of example embodiment there may be a mixed TB transmission of: 1. a mixture of new data transmission and re-transmission or 2. re-transmission from a 1st data batch and a re-transmission from the 2nd data batch. This may be done based on a new interpretation of existing NR parameters: 1. a new interpretation of a new data indicator bit being toggled and 2. a new interpretation of the code block group transmission information set to 0 or 1 (new data or retransmitted data). This may include a case of new interpretation when NDI is toggled, CGBTI 0 corresponds to new data transmission, a new interpretation when NDI is not toggled, and CGBTI 1 may correspond to retransmission of the first or the second batch based on CBGTI history.

[0082] In another type of example embodiment new parameters may be signaled by the network and not a new interpretation of existing NR parameters is not needed. This may be, for example, a new field comprising a new mapping rule or information indicative of the mapping, or a first configuration information (i.e CBGTI_1) for retransmitted CBs and a second configuration information (i.e CBGTI_2) for newly transmitted CBs for the mixed TB.

[0083] An example embodiment may be provided with an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a new data indicator bit has toggled; based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that or whether data in at least one code block group comprises: retransmitted data, or new data.

[0084] The determining that or whether data in at least one code block group comprises retransmitted data or new data may comprise at least one of: based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 0, determining that data in the at least one code block group comprises new data, or based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 1 , determining that data in the at least one code block group comprises retransmitted data. The determining whether the new data indicator bit has toggled may comprise determining that that there has been a change of the new data indicator bit relative to a previously received new data indicator bit. The instructions, when executed with the at least one processor, may cause the apparatus to perform: receiving a downlink control information comprising the new data indicator bit and the code block group transmission information; and where the determining that data in the at least one code block group is retransmitted data or new data comprises using the downlink control information for determining whether data in a first code block group of a physical data shared channel comprises retransmitted data and whether data in a second code block group of the physical data shared channel comprises new data. The instructions, when executed with the at least one processor, may cause the apparatus to perform: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are ”l”s, determining that a transmission comprises only new data. The instructions, when executed with the at least one processor, may cause the apparatus to perform: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are not ”l”s, determining that a transmission comprises both new data and retransmitted data. The instructions, when executed with the at least one processor,may cause the apparatus to perform at least one of: based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 0, determining that data in the at least one code block group comprises no data; and based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 1, determining that data in at least one code block group comprises retransmitted data. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining that at least one first element of the code block group transmission information is for a first data, and determining that at least one second element of the code block group transmission information is for a second data. The instructions, when executed with the at least one processor, may cause the apparatus to perform at least one of: determining, based at least partially on a first type of indicator of the at least one first element, that the first data is new data, or determining, based at least partially on a second type of indicator of the at least one second element, that the second data is retransmitted data. The first type of indicator may be a “0” and the second type of indicator may be a “1”. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining that new data is linked with re-transmitted data in a physical data shared channel.

[0085] Referring also to FIG. 7, an example embodiment may be provided with a method comprising: determining whether a new data indicator bit has toggled as illustrated with block 702; and based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that or whether data in at least one code block group comprises: retransmitted data, or new data as illustrated with block 704. The determining that or whether data in at least one code block group comprises retransmitted data or new data may comprise at least one of: based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 0, determining that data in the at least one code block group comprises new data, or based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 1 , determining that data in the at least one code block group comprises retransmitted data. The determiningwhether the new data indicator bit has toggled may comprise determining that that there has been a change of the new data indicator bit relative to a previously received new data indicator bit. The method may comprise receiving a downlink control information comprising the new data indicator bit and the code block group transmission information; and where the determining that or whether data in the at least one code block group is retransmitted data or new data comprises using the downlink control information for determining whether data in a first code block group of a physical data shared channel comprises retransmitted data and whether data in a second code block group of the physical data shared channel comprises new data. The method may comprise, based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are ”l”s, determining that a transmission comprises only new data. The method may comprise, based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are not ”l”s, determining that a transmission comprises both new data and retransmitted data. The method may comprise at least one of: based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 0, determining that data in the at least one code block group comprises no data; or based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 1 , determining that data in at least one code block group comprises retransmitted data. The method may comprise determining that at least one first element of the code block group transmission information is for a first data, and determining that at least one second element of the code block group transmission information is for a second data. The method may comprise determining, based at least partially on a first type of indicator of the at least one first element, that the first data is new data, or determining, based at least partially on a second type of indicator of the at least one second element, that the second data is retransmitted data. The first type of indicator may be a “0” and the second type of indicator may be a “1”. The method may comprise determining that new data is linked with re-transmitted data in a physical data shared channel.

[0086] An example embodiment may be provided with apparatus comprising: means for determining whether a new data indicator bit has toggled; and means for, based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0087] An example embodiment may be provided with a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether a new data indicator bit has toggled; and based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

[0088] An example embodiment may be provided with an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment. The determining of the code block group transmission information may comprise at least one of: based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating new data, or based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data. The transmitting of the data to the user equipment may comprise concatenating retransmitted data and new data in a physical downlink shared channel. The determining of the code block group transmission information may be based, at least partially, on receiving an acknowledgement or negative acknowledgment from the user equipment. The determining of the code block group transmission information may comprise indicating that data in a code block group is retransmitted data or new data. The instructions, when executed with the at least one processor, may cause the apparatus to perform:based on determining to toggle the new data indicator bit, causing the new data indicator bit to change relative to a previously sent new data indicator bit. The determining of the code block group transmission information may comprise at least one of: based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating no data, or based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

[0089] Referring also to FIG. 8, an example embodiment may be provided with a method comprising: determining whether to toggle a new data indicator bit as illustrated with block 802; determining a code block group transmission information as illustrated with block 804, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment as illustrated with block 806. The determining of the code block group transmission information may comprise at least one of: based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating new data, or based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data. The transmitting of the data to the user equipment may comprise concatenating retransmitted data and new data in a physical downlink shared channel. The determining of the code block group transmission information may be based, at least partially, on receiving an acknowledgement or negative acknowledgment from the user equipment. The determining of the code block group transmission information may comprise indicating that data in a code block group is retransmitted data or new data. The method may comprise based on determining to toggle the new data indicator bit, causing the new data indicator bit to change relative to a previously sent new data indicator bit. The determining of the code block group transmission information may comprise at least one of: based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating nodata, or based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

[0090] An example embodiment may be provided with an apparatus comprising: means for determining whether to toggle a new data indicator bit; means for determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and means for transmitting the data to a user equipment.

[0091] An example embodiment may be provided with a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

[0092] An example embodiment may be provided with an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and receiving the scheduled data channel based, at least partially, on the downlink control information. The information comprises a flag, where the flag being toggle indicates that the at least one new code block group is transmitted with the at least one retransmitted code block group in the scheduled data channel. The downlink control information may comprise a first code block group transmission information, and where the instructions, when executed with the at least one processor, cause the apparatus to perform: using the first code block group transmission information for determining whether a code block group in the scheduled data channel is a new code block group or a retransmitted code block group. Using the first code block grouptransmission information may comprise: when the flag is toggled and corresponding element of the first code block group transmission information associated with the code block group is set to value of 0, determining the code block group in the scheduled data channel is a new code block group, or when the flag is toggled and corresponding element of the first code block group transmission information associated with the code block group is set to value of 1, determining the code block group in the scheduled data channel is a retransmitted code block group. The information may comprise a second code block group transmission information. The second code block group transmission information may comprise a same size as the first block group transmission information. The information may comprise a flag, when the flag is toggled, the instructions, when executed with the at least one processor, cause the apparatus to perform at least one of: determining a code block group in the scheduled data channel is a retransmitted code block group based on the first code block group transmission information, or determining a code block group in the scheduled data channel is a new code block group based on the second code block group transmission information. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining to ignore at least part of a field of the second code block group transmission information based on comparing a maximum number of “l”s relative to “0”s in the first code block group transmission information. The instructions, when executed with the at least one processor, may cause the apparatus to perform at least one of: determining to ignore at least part of a field of the second code block group transmission information based on determining no new data is present in a physical data shared channel.

[0093] Referring also to FIG. 9, an example embodiment may be provided with a method comprising: receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel as illustrated with block 902; and receiving the scheduled data channel based, at least partially, on the downlink control information as illustrated with block 904. The information may comprise a flag, where the flag being toggled indicates that the at least one new code block group is transmitted with the at least one retransmitted code block group in the scheduled data channel. The downlink control information may comprise a first code block group transmission information, and the method comprises: using the first code block group transmission information for determining whethera code block group in the scheduled data channel is a new code block group or a retransmitted code block group. Using the first code block group transmission information may comprise: when the flag is toggled and corresponding element of the first code block group transmission information associated with the code block group is set to value of 0, determining the code block group in the scheduled data channel is a new code block group, or when the flag is toggled and corresponding element of the first code block group transmission information associated with the code block group is set to value of 1 , determining the code block group in the scheduled data channel is a retransmitted code block group. The information may comprise a second code block group transmission information. The second code block group transmission information may be a same size as the first block group transmission information. The information may comprise a flag, when the flag is toggle, the method comprises: determining a code block group in the scheduled data channel is a retransmitted code block group based on the first code block group transmission information, or determining a code block group in the scheduled data channel is a new code block group based on the second code block group transmission information. The method may comprise determining to ignore at least part of a field of the second code block group transmission information based on comparing a maximum number of “l”s relative to “0”s in the first code block group transmission information. The method may comprise determining to ignore at least part of a field of the second code block group transmission information based on determining no new data is present in a physical data shared channel.

[0094] An example embodiment may be provided with an apparatus comprising: means for receiving a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and means for receiving the scheduled data channel based, at least partially, on the downlink control information.

[0095] An example embodiment may be provided with a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: receiving a downlink control information comprising information indicating whether at least one new code block group is transmittedwith at least one retransmitted code block group in a scheduled data channel; and receiving the scheduled data channel based, at least partially, on the downlink control information.

[0096] An example embodiment may be provided with an apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: sending a downlink control information comprising information indicating whether a new code block group is transmitted with a retransmitted code block group in a scheduled data channel; and sending the scheduled data channel based, at least partially, on the downlink control information. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining how to indicate with the downlink control information that data in a code block group is retransmitted data or new data comprising use of a code block group transmission information of the downlink control information with the information for determining whether the data in the code block group is retransmitted data or new data. The information may comprise a flag, where the flag being toggle indicates that the at least one new code block group is transmitted with the at least one retransmitted code block group in the scheduled data channel. The downlink control information may comprise a first code block group transmission information, and where the instructions, when executed with the at least one processor, cause the apparatus to perform: providing the first code block group transmission information for determining whether a code block group in the scheduled data channel is a new code block group or a retransmitted code block group. Providing the first code block group transmission information may comprise: toggling the flag and providing a corresponding element of the first code block group transmission information associated with the code block group set to a value of 0, for determining that the code block group in the scheduled data channel is a new code block group, or toggling the flag and providing a corresponding element of the first code block group transmission information associated with the code block group set to value of 1 , for determining that the code block group in the scheduled data channel is a retransmitted code block group. The information may comprise a second code block group transmission information. The second code block group transmission information may have a same size as the first block group transmission information. The information may comprise a flag for at least one of: determining that a code block group in the scheduled data channel is a retransmitted code block group based on the first code block group transmission information, or determining that a codeblock group in the scheduled data channel is a new code block group based on the second code block group transmission information.

[0097] Referring also to FIG. 10, an example embodiment may be provided with a method comprising: sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel as illustrated with block 1002; and sending the scheduled data channel based, at least partially, on the downlink control information as illustrated with block 1004. The method may comprise determining how to indicate with the downlink control information that data in a code block group is retransmitted data or new data comprising use of a code block group transmission information of the downlink control information with the information for determining whether the data in the code block group is retransmitted data or new data. The information may comprise a flag, where the flag being toggle indicates that the at least one new code block group is transmitted with the at least one retransmitted code block group in the scheduled data channel. The downlink control information may comprise a first code block group transmission information, and where the method comprises: providing the first code block group transmission information for determining whether a code block group in the scheduled data channel is a new code block group or a retransmitted code block group. The providing of the first code block group transmission information may comprise: toggling the flag and providing a corresponding element of the first code block group transmission information associated with the code block group set to a value of 0, for determining that the code block group in the scheduled data channel is a new code block group, or toggling the flag and providing a corresponding element of the first code block group transmission information associated with the code block group set to value of 1, for determining that the code block group in the scheduled data channel is a retransmitted code block group. The information may comprise a second code block group transmission information. The second code block group transmission information may have a same size as the first block group transmission information. The information may comprise a flag for at least one of: determining that a code block group in the scheduled data channel is a retransmitted code block group based on the first code block group transmission information, or determining that a code block group in the scheduled data channel is a new code block group based on the second code block group transmission information.

[0098] An example embodiment may be provided with an apparatus comprising: means for sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and means for sending the scheduled data channel based, at least partially, on the downlink control information.

[0099] An example embodiment may be provided with a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: sending a downlink control information comprising information indicating whether at least one new code block group is transmitted with at least one retransmitted code block group in a scheduled data channel; and sending the scheduled data channel based, at least partially, on the downlink control information.

[0100] In accordance with one example embodiment, an example apparatus may be provided comprising at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a new data indicator has changed; based on determining that the new data indicator has changed and on information in a code block group transmission information, determining whether data in at least one code block group is: retransmitted data, or new data; and based on determining that the new data indicator has not changed and on information in a code block group transmission information, determining that data in at least one code block group is retransmitted data.

[0101] In accordance with one example embodiment, an example apparatus may be provide comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: based at least partially on receiving a negative acknowledgement, determining whether to change a new data indicator relative to a previously sent new data indicator; and determining, based on the determination of whether to change the new data indicator, values of a code block group transmission information to be sent to a user equipment for indicating whether that data in a code block group is: retransmitted data, or new data.

[0102] The new data indicator bit may comprise a single bit.

[0103] In accordance with one example embodiment, an example apparatus may be provide comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: based at least partially on receiving a negative acknowledgement, determining whether to toggle a new data indicator bit relative to a previously sent new data indicator bit; and determining, based on the determination of whether to toggle the new data indicator bit, values of a code block group transmission information to be sent to a user equipment for indicating that data in a code block group is: retransmitted data, or new data.

[0104] The determining of the values of a code block group transmission information to be sent to a user equipment may comprise: based on determining to toggle the new data indicator bit, setting the code block group transmission information to a value of 0 for indicating new data, or based on determining to toggle the new data indicator bit, setting the code block group transmission information to a value of 1 for indicating retransmitted data. The instructions, when executed with the at least one processor, may cause the apparatus to perform combining retransmitted data and new data in a physical downlink shared channel. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining location of the retransmitted data relative to the new data in the physical downlink shared channel based, at least partially, on the receiving of the negative acknowledgement. The determining of the values of the code block group transmission information to be sent to the user equipment may comprise indicating that data in a code block group is retransmitted data and new data. The instructions, when executed with the at least one processor, may cause the apparatus to perform: based on determining to toggle the new data indicator bit relative to the previously sent new data indicator bit, causing the new data indicator bit to change relative to the previously sent new data indicator bit. The instructions, when executed with the at least one processor, may cause the apparatus to perform: organizing the retransmitted data in a first data batch of a physical data shared channel, and the new data in a second data batch of the physical data shared channel. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining location of the first data batch relative to the second data batch. The determining of the location of the first data batch relative to the second data batch may comprise: determining that the first data batch is before the second data batch, where the first data batch comprises the retransmitted data and the second data batch comprisesthe new data, or determining that the first data batch is after the second data batch, where the first data batch comprises the retransmitted data and the second data batch comprises the new data. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining a size of the first data batch relative to the second data batch. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining a size of a second code block group transmission information relative to a size of a first code block group transmission information. The determining of the values of a code block group transmission information to be sent to a user equipment may comprise: determining values of a code block group transmission information previously sent to the user equipment. The instructions, when executed with the at least one processor, may cause the apparatus to perform: changing the new data indicator bit based on new data to be sent to the user equipment with a physical downlink shared channel, and not changing the new data indicator bit based on no new data to be sent to the user equipment with the physical downlink shared channel.

[0105] The instructions, when executed with the at least one processor, may cause the apparatus to perform: storing at least part of the first data, and storing at least part of the second data, and sending a negative acknowledgement regarding at least one of the first code block group or the second code block group of the physical data shared channel.

[0106] The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining a size of the first data batch relative to the second data batch. The determining of the size of the first data batch relative to the second data batch may comprise assuming that the first and second data batch sizes are the same. The instructions, when executed with the at least one processor, may cause the apparatus to perform: determining a size of a second code block group transmission information relative to a size of a first code block group transmission information.

[0107] In accordance with one example embodiment, an example apparatus may be provide comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: receiving a downlink control information, where the downlink control information comprises a new data indicatorand a code block group transmission information, where the downlink control information indicates that a code block group in a scheduled data channel is a retransmitted code block group or a new code block group; and receiving a scheduled data channel based, at least partially, on the downlink control information.

[0108] In accordance with one example embodiment, an example apparatus may be provide comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: based at least partially on receiving a negative acknowledgement, determining whether to change a new data indicator for a downlink control information relative to a previously sent new data indicator; based at least partially on the receiving of the negative acknowledgement, determining values of a code block group transmission information for the downlink control information; and based at least partially on whether to change the new data indicator and the determined values of the code block group transmission information, determining how to indicate with the downlink control information that data in a code block group is retransmitted data or new data.

[0109] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0110] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(iii) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0111] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0112] It should be understood that the foregoing description is only illustrative. Various alternatives and modifications can be devised by those skilled in the art. For example, features recited in the various dependent claims could be combined with each other in any suitable combination(s). In addition, features from different embodiments described above could be selectively combined into a new embodiment. Accordingly, the description is intended to embrace all such alternatives, modifications and variances which fall within the scope of the appended claims.

Claims

CLAI MSWhat is claimed is:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether a new data indicator bit has toggled; based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

2. The apparatus of claim 1, wherein the determining that data in at least one code block group comprises retransmitted data or new data comprises at least one of: based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 0, determining that data in the at least one code block group comprises new data, or based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 1 , determining that data in the at least one code block group comprises retransmitted data.

3. The apparatus as claimed in any one of claims 1-2 where the determining whether the new data indicator bit has toggled comprises determining that that there has been a change of the new data indicator bit relative to a previously received new data indicator bit.

4. The apparatus as claimed in any one of claims 1-3 where the instructions, when executed with the at least one processor, cause the apparatus to perform: receiving a downlink control information comprising the new data indicator bit and the code block group transmission information; and where the determining that data in the at least one code block group is retransmitted data or new data comprises using the downlink control information for determining whether data in a first code block group of a physical data shared channel comprises retransmitted data and whether data in a second code block group of the physical data shared channel comprises new data.

5. The apparatus as claimed in any one of claims 1-4 where the instructions, when executed with the at least one processor, cause the apparatus to perform: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are ”l”s, determining that a transmission comprises only new data.

6. The apparatus as claimed in any one of claims 1-5 where the instructions, when executed with the at least one processor, cause the apparatus to perform: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are not ”l”s, determining that a transmission comprises both new data and retransmitted data.

7. The apparatus as claimed in claim 1 where the instructions, when executed with the at least one processor, cause the apparatus to perform at least one of:based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 0, determining that data in the at least one code block group comprises no data; and based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 1 , determining that data in at least one code block group comprises retransmitted data.

8. The apparatus as claimed in any one of claims 1-7 where the instructions, when executed with the at least one processor, cause the apparatus to perform: determining that at least one first element of the code block group transmission information is for a first data, and determining that at least one second element of the code block group transmission information is for a second data.

9. The apparatus as claimed in claim 8 where the instructions, when executed with the at least one processor, cause the apparatus to perform at least one of: determining, based at least partially on a first type of indicator of the at least one first element, that the first data is new data, or determining, based at least partially on a second type of indicator of the at least one second element, that the second data is retransmitted data.

10. The apparatus as claimed in claim 9 where the first type of indicator is a “0” and where the second type of indicator is a “1”.

11. The apparatus as claimed in any one of claims 1-10 where the instructions, when executed with the at least one processor, cause the apparatus to perform:determining that new data is linked with re-transmitted data in a physical data shared channel.

12. A method comprising: determining whether a new data indicator bit has toggled; and based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

13. The method as claimed in claim 12 wherein the determining that data in at least one code block group comprises retransmitted data or new data comprises at least one of: based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 0, determining that data in the at least one code block group comprises new data, or based on determining that the new data indicator bit has toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to value of 1 , determining that data in the at least one code block group comprises retransmitted data.

14. The method as claimed in any one of claims 12-13 where the determining whether the new data indicator bit has toggled comprises determining that that there has been a change of the new data indicator bit relative to a previously received new data indicator bit.

15. The method as claimed in any one of claims 12-14 comprising: receiving a downlink control information comprising the new data indicator bit and the code block group transmission information; andwhere the determining that data in the at least one code block group is retransmitted data or new data comprises using the downlink control information for determining whether data in a first code block group of a physical data shared channel comprises retransmitted data and whether data in a second code block group of the physical data shared channel comprises new data.

16. The method as claimed in any one of claims 12-15 comprising: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are ”l”s, determining that a transmission comprises only new data.

17. The method as claimed in any one of claims 12-16 comprising: based on determining that the new data indicator bit has toggled and based on determining that all elements of the code block group transmission information are not ”l”s, determining that a transmission comprises both new data and retransmitted data.

18. The method as claimed in claim 12 comprising at least one of: based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 0, determining that data in the at least one code block group comprises no data; and based on determining that the new data indicator bit has not toggled and corresponding element of the code block group transmission information associated with the at least one code block group is set to a value of 1 , determining that data in at least one code block group comprises retransmitted data.

19. The method as claimed in any one of claims 12-18 comprising: determining that at least one first element of the code block group transmission information is for a first data, anddetermining that at least one second element of the code block group transmission information is for a second data.

20. The method as claimed in claim 19 comprising: determining, based at least partially on a first type of indicator of the at least one first element, that the first data is new data, or determining, based at least partially on a second type of indicator of the at least one second element, that the second data is retransmitted data.

21. The method as claimed in claim 20 where the first type of indicator is a “0” and where the second type of indicator is a “1”.

22. The method as claimed in any one of claims 12-21 comprising: determining that new data is linked with re-transmitted data in a physical data shared channel.

23. An apparatus comprising: means for determining whether a new data indicator bit has toggled; and means for, based on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

24. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether a new data indicator bit has toggled; andbased on determining that the new data indicator bit has toggled and on information in a code block group transmission information, determining that data in at least one code block group comprises: retransmitted data, or new data.

25. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed with the at least one processor, cause the apparatus to perform: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

26. The apparatus as claimed in claim 25 where the determining of the code block group transmission information comprises at least one of: based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating new data, or based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

27. The apparatus as claimed in any one of claims 25-26 where the transmitting of the data to the user equipment comprises: concatenating retransmitted data and new data in a physical downlink shared channel.

28. The apparatus as claimed in claim 27 where the determining of the code block group transmission information is based, at least partially, on receiving an acknowledgement or negative acknowledgment from the user equipment.

29. The apparatus as claimed in any one of claims 25-28 where the determining of the code block group transmission information comprises indicating that data in a code block group is retransmitted data or new data.

30. The apparatus as claimed in any one of claims 25-29 where the instructions, when executed with the at least one processor, cause the apparatus to perform: based on determining to toggle the new data indicator bit, causing the new data indicator bit to change relative to a previously sent new data indicator bit.

31. The apparatus as claimed in claim 25, where the determining of the code block group transmission information comprises at least one of: based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating no data, or based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

32. A method comprising: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicateswhether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

33. The method as claimed in claim 32 where the determining of the code block group transmission information comprises at least one of: based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating new data, or based on determining to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

34. The method as claimed in any one of claims 32-33 where the transmitting of the data to the user equipment comprises: concatenating retransmitted data and new data in a physical downlink shared channel.

35. The method as claimed in claim 34 where the determining of the code block group transmission information is based, at least partially, on receiving an acknowledgement or negative acknowledgment from the user equipment.

36. The method as claimed in any one of claims 32-35 where the determining of the code block group transmission information comprises indicating that data in a code block group is retransmitted data or new data.

37. The method as claimed in any one of claims 32-36 comprising: based on determining to toggle the new data indicator bit, causing the new data indicator bit to change relative to a previously sent new data indicator bit.

38. The method as claimed in claim 32, where the determining of the code block group transmission information comprises at least one of:based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 0 for indicating no data, or based on determining not to toggle the new data indicator bit, setting corresponding element of the code block group transmission information associated with the at least one code block group to a value of 1 for indicating retransmitted data.

39. An apparatus comprising: means for determining whether to toggle a new data indicator bit; means for determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and means for transmitting the data to a user equipment.

40. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: determining whether to toggle a new data indicator bit; determining a code block group transmission information, wherein when the new data indicator bit is toggled, the code block group transmission information indicates whether data in at least one code block group comprises at least one of retransmitted data or new data; and transmitting the data to a user equipment.

Images