[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024220068A1 - Sub-codeblock group based operation for single codeword scheduling - Google Patents

Sub-codeblock group based operation for single codeword scheduling Download PDF

Info

Publication number
WO2024220068A1
WO2024220068A1 PCT/US2023/018833 US2023018833W WO2024220068A1 WO 2024220068 A1 WO2024220068 A1 WO 2024220068A1 US 2023018833 W US2023018833 W US 2023018833W WO 2024220068 A1 WO2024220068 A1 WO 2024220068A1
Authority
WO
WIPO (PCT)
Prior art keywords
data channel
shared data
groups
codeblock
scheduled
Prior art date
Application number
PCT/US2023/018833
Other languages
French (fr)
Inventor
Klaus Hugl
Karri Markus Ranta-Aho
Original Assignee
Nokia Technologies Oy
Nokia Of America Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy, Nokia Of America Corporation filed Critical Nokia Technologies Oy
Priority to PCT/US2023/018833 priority Critical patent/WO2024220068A1/en
Publication of WO2024220068A1 publication Critical patent/WO2024220068A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1854Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • H04L1/1614Details of the supervisory signal using bitmaps
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1861Physical mapping arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling

Definitions

  • Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or other communications systems.
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR new radio
  • certain example embodiments may relate to sub-codeblock group based operation for single codeword scheduling.
  • Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE- A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology.
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Long Term Evolution
  • E-UTRAN Evolved UTRAN
  • LTE- A LTE- Advanced
  • MulteFire LTE- A Pro
  • LTE- A Pro new radio
  • Fifth generation (5G) wireless systems refer to the next generation (NG) of radio systems and network architecture.
  • 5G network technology is mostly based on new radio (NR) technology, but the 5G (or NG) network can also build on E-UTRAN radio.
  • NR may provide bitrates on the order of 10-20 Gbit/s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC).
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable low-latency communication
  • mMTC massive machine-type communication
  • NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (loT).
  • LoT Internet of Things
  • Various exemplary embodiments may provide a method including determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel, and generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the method may also include providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Some exemplary embodiments may provide a method including decoding, by a user equipment, a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the method may also include determining, by the user equipment, based on the scheduling information, that the user equipment is scheduled with a single codeword or transport block on the shared data channel, and determining, by the user equipment, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Certain exemplary embodiments may provide a method including decoding, by a user equipment, a control channel scheduling the user equipment for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the method may also include determining, by the user equipment, that the user equipment is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the method may also include providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Various exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions.
  • the instructions when executed by the at least one processor, may cause the apparatus at least to determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel and generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Certain exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions.
  • the instructions when executed by the at least one processor, may cause the apparatus at least to decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the apparatus may also be caused to determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel, and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Various exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions.
  • the instructions when executed by the at least one processor, may cause the apparatus at least to decode a control channel scheduling the apparatus for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the apparatus may also be caused to determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception and generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may further be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Some exemplary embodiments may provide an apparatus including means for determining that the apparatus is scheduled with a single codeword or transport block for a shared data channel and means for generating a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may also include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Various exemplary embodiments may provide an apparatus including means for decoding a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the apparatus may also include means for determining based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel, and means for determining, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Certain exemplary embodiments may provide an apparatus including means for decoding a control channel scheduling the apparatus for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the apparatus may also include means for determining that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and means for generating a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may further include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Various exemplary embodiments may provide a non- transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel and generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Some exemplary embodiments may provide a non-transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the apparatus may also be caused to determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Various exemplary embodiments may provide a non-transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to decode a control channel scheduling the apparatus for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the apparatus may also be caused to determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception and generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may further be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Various exemplary embodiments may provide one or more computer programs including instructions stored thereon for performing one or more of the methods described herein. Some exemplary embodiments may also provide one or more apparatuses including one or more circuitry configured to perform one or more of the methods described herein.
  • FIG. 1 illustrates an example of a diagram of a codeblock group transmission information, according to various exemplary embodiments
  • FIG. 2 illustrates an example of a diagram of feedback implementation, according to various exemplary embodiments
  • FIG. 3 illustrates a diagram showing a configuration, according to various exemplary embodiments
  • FIG. 4 illustrates an example of a flow diagram of a method, according to certain exemplary embodiments
  • FIG. 5 illustrates an example of a flow diagram of another method, according to certain exemplary embodiments.
  • FIG. 6 illustrates an example of a flow diagram of a further method, according to certain exemplary embodiments.
  • FIG. 7 illustrates a set of apparatuses, according to various exemplary embodiments.
  • CodeBlock group (CBG) based hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback for physical downlink shard channel (PDSCH) and CBG-based physical uplink shared channel (PUSCH) and/or PDSCH scheduling may allow for a finer granularity of HARQ-feedback for PDSCH and finer retransmission granularity for PDSCH & PUSCH.
  • HARQ hybrid automatic repeat request
  • PUSCH physical uplink shared channel
  • PDSCH scheduling may allow for a finer granularity of HARQ-feedback for PDSCH and finer retransmission granularity for PDSCH & PUSCH.
  • TB transport block
  • CBG-based HARQ may avoid unnecessarily retransmitting all the correctly decoded CBs in the event that one or more erroneous CBs and one or more correctly decoded CBs exist in a TB.
  • each CB may have its own HARQ- ACK bit, and in retransmission, each CB may be separately indicated to be either present or absent, and omitting a CB from a retransmission may be due to the CB being already correctly delivered/decoded after a previous transmission attempt.
  • a potential deficiency with separately evaluating the HARQ- ACK bit of each CB may be that it causes a high overhead or high processing burden due to the potentially large number of CBs in a TB. To aid in addressing this deficiency, the concept of grouping the CBs into CBGs was adopted in certain situations.
  • the CBs of a single TB and/or CodeWord may be grouped in multiple CBGs with substantially similar or equal sizes.
  • the maximum number of CBGs N for PDSCH and/or PUSCH may be configured by a radio resource control (RRC) message using a parameter maxCodeBlockGroupsPerTransportBlock with possible values of ⁇ 2, 4, 6, 8 ⁇ .
  • the number of CBs C may be assigned to the up to N CBG groups.
  • N may be defined as the maximum number of CBGs per TB as configured by maxCodeBlockGroupsPerTransportBlock for PDSCH and C may be the number of CBs in the TB.
  • a HARQ-ACK bit for each of the individual CBGs may be fed back for the overall TB.
  • CBG-based scheduling for PDSCH.
  • the CBGs of the TB that are to be transmitted or retransmitted may be indicated in scheduling downlink control information (DCI) for the PDSCH and/or PUSCH.
  • DCI downlink control information
  • a separate field for CBG transmission indication may be included to indicate one or more CBGs that may be part of the scheduled PUSCH/PDSCH transmission.
  • the CBGTI field may include one bit for each CBG to allow per CBG presence indication of the scheduled PDSCH / PUSCH.
  • all CBGs may be scheduled. For example, a full TB may be scheduled for the first transmission.
  • the CBGTI field may apply equally to PUSCH and/or PDSCH transmissions.
  • CBG-based HARQ and scheduling operation there may be some inefficiencies in the CBG-based HARQ and scheduling operation, such as when there are multiple (e.g., 2) transport block and/or CodeWord operations for PDSCH operation, which may be configured with maxNrofCodeWordsScheduledByDCI.
  • multiple transport block and/or CodeWord operations for PDSCH operation which may be configured with maxNrofCodeWordsScheduledByDCI.
  • HARQ-ACK feedback operation only the HARQ-ACK bits for a first number of CBGs M out of a total of 2*N may be used.
  • the parameter maxNrofCodeWordsScheduledByDCI may indicate reception of up to two TBs, when the UE receives a PDSCH with one TB or a semi-persistent scheduling (SPS) PDSCH release or a transmission configuration indicator (TCI) state update.
  • the HARQ-ACK information may be associated with a first TB and the UE may generate a non- acknowledgement (NACK) for a second (not present) TB if the parameter harq-ACKSpatialBundlingPUCCH is not provided.
  • the UE may also generate HARQ- ACK information with a value of ACK for the second (not present) TB when the parameter harq-ACK-SpatialBundlingPUCCH is provided. In both cases, the transmitter may know that there was no second TB and may ignore the bit in the HARQ- ACK codebook related to the second TB.
  • a PDCCH monitoring occasion may be provided with a DCI format scheduling PDSCH reception or with associated HARQ-ACK information without scheduling the PDSCH reception.
  • a UE may receive a PDSCH with one transport block or detect a DCI format having associated HARQ-ACK information without scheduling PDSCH reception.
  • a value of the parameter maxNrofCodeWordsScheduledByDCI may be set at 2 and the HARQ-ACK information may be associated with a first transport block.
  • the UE may generate a NACK for a second transport block when the parameter harq-ACKSpatialBundlingPUCCH is not provided and may generate HARQ-ACK information with a value of ACK for the second transport block when the parameter harq-ACK-SpatialBundlingPUCCH is provided.
  • CBGTI information may be in a DCI format 1 1 for scheduling CBG-based PDSCH.
  • a UE may be configured to receive CBG-based transmissions by receiving the higher layer parameter codeBlockGroupTransmission for PDSCH.
  • the CBGTI field of the DCI format 1 1 may have a length N TB ⁇ N bits, where N TB may be defined as the value of the higher layer parameter maxNrofCodeWordsScheduledByDCI.
  • N TB 2
  • the CBGTI field bits may be mapped such that a first set of N bits starting from a most significant bit (MSB) that may correspond to the first TB while a second set of N bits may correspond to a second TB when scheduled.
  • the first M bits of each set of N bits in the CBGTI field may have an in-order one-to- one mapping with the CBGs of the TB with the MSB mapped to CBG#0.
  • the UE may assume that all the CBGs of the TB are present.
  • the CBGTI field of the scheduling DCI may indicate which CBGs of the TB are present in the transmission.
  • a bit value of '0' in the CBGTI field may indicate that a corresponding CBG is not transmitted and T indicates that the corresponding CBG is transmitted.
  • the UE may assume that when a 'CBG flushing out information' (CBGFI) field of the scheduling DCI is present, the CBGFI set to '0' may indicate that earlier received instances of the same CBGs being transmitted may be corrupted, and the CBGFI set to T may indicate that the CBGs being retransmitted are combinable with the earlier received instances of the same CBGs.
  • CBGFI flushing out information'
  • the UE may also assume that a CBG contains the same CBs during retransmission as in the initial transmission of the TB.
  • the CBGTI field may be set to a size of 0 bit when the higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, the CBGTI field size may be set to 2, 4, 6, or 8 bits based on the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.
  • a UE may be configured for dual-codeword, or 2 TB operation (maxNrofCodeWordsScheduledByDCI set to 2) and configured with 4 CBGs (maxCodeBlockGroupsPerTransportBlock set to ‘n4’).
  • the UE may be configured for single TB scheduling with a TB size of 22 CBs.
  • the 22 CBs of the scheduled transmission may be assigned to 4 CBGs, such as, for example, CBG#0: CB #0..#5, CBG#1: CB #6..#11, CBG#2: CB #12..#16, CBG#3: CB #17..#21.
  • the CBGTI may be as follows: ⁇ CBG#0 TB1, CBG#1 TB1, CBG#2 TB1, CBG#3 TB1, 0,0, 0,0 ⁇ .
  • the first 4 bits may have useful HARQ-ACK information for the first, scheduled TB, and the second 4 bits of the HARQ- ACK information may not due to being associated with the second nonscheduled TB, which may be set to NACK or 0.
  • the HARQ- ACK feedback information may be as follows: ⁇ HARQ-ACK CBG#0 TB1, HARQ-ACK CBG#1 TB1, HARQ-ACK CBG#2 TB1, HARQ-ACK CBG#3 TB1, ‘NACK’, ‘NACK’, ‘NACK’, ‘NACK’ ⁇ .
  • Various exemplary embodiments may provide advantages to aid in resolving the deficiencies discussed above. For example, certain exemplary embodiments may provide one or more procedures to optimize a CBG-based scheduling operation in which two transport blocks may be capable of being scheduled for the UE, but only a single transport block has been scheduled. Various exemplary embodiments may advantageously provide for doubling the HARQ-ACK feedback and/or scheduling granularity without any additional UL or DL control signaling overhead.
  • Certain exemplary embodiments may provide one or more procedures for a situation in which a single TB is scheduled, the feedback granularity may be doubled to 2* maxCodeBlockGroupsPerTransportBlock to use all of the available CBGTI/HARQ-ACK feedback bits for the single scheduled transport block. This may eliminate setting the CBGTI bits to 0 and the HARQ- ACK feedback bits to NACK for the second non-scheduled transport block.
  • An example according to various exemplary embodiments may set 4 CBGs per TB with dual-codeword or 2 transport block operation for single transport block scheduling and a transport block size of 22 CBs.
  • the 22 CBs of the scheduled transmission may be assigned to 4 CBGs, such as CBG#0: CB #0..#5, CBG#1: CB #6..#11, CBG#2: CB #12..#16, CBG#3: CB #17..#21.
  • FIG. 1 illustrates an example of a diagram of a CBGTI implementation for this example, according to various exemplary embodiments.
  • the CBGTI may be 8-bit information.
  • the legacy behaviour may be shown in an upper row including ‘0’s for the second non-scheduled TB and a lower row of the diagram may show that each of the CBGs may be split into two sub-CBGs with approximately double the granularity.
  • Each CBG #X may be split in two sub-CBGs, CGB #XA and #XB, with approximately equal size.
  • the exemplary embodiments are not limited to this example of FIG. 1.
  • any maximum number of codewords and/or transport blocks may be used by splitting each original CBG into maxNrofCodeWordsScheduledByDCI sub-CBGs.
  • the double number of CBGs for the single TB/CW scheduled PDSCH may be assumed, such as, for example, assuming 2*N CBGs or maxNrofCodeWordsScheduledByDCI * maxCodeBlockGroupsPerTransportBlock CBGs.
  • the CBs for a single CW transmission may be paired with a set of other CBs in a sub-CBG not contained in the same CBG in dual (or multi-) CW transmission, which may limit the usage for re-transmission operation of mixed single or dual CW operation.
  • FIG. 2 illustrates an example of a diagram of a HARQ feedback implementation, according to various exemplary embodiments.
  • FIG. 2 shows an example of 8-bit HARQ-ACK information, in which the upper row shows the legacy implementation including ‘NACK’ i.e. ‘0’s for the last 4 bits for the second non-scheduled PDSCH transport block for comparison with the lower row, which shows the HARQ feedback for one or more procedures according to various exemplary embodiments.
  • all of the 8-bit HARQ-ACK feedback information may be used for a single scheduled PDSCH transport block with approximately double the granularity and half the CBG size.
  • the CBGs may be split into the same CBGs as for the CBGTI (e.g., CBG #XA & CBG #XB), by applying a CB to CBG association pseudo code within a CBG to create the maxNrofCodeWordsScheduledByDCI sub-CBGs A/B.
  • K + (m — Mi) • K 2 + k, k 0,1, ... , K 2 — 1 .
  • the CB to CBG association may be reused assuming 2*N CBGs or maxNrofCode WordsScheduledByDCI* maxCodeBlockGroupsPerTransportBlock CBGs.
  • Certain exemplary embodiments may provide HARQ-ACK feedback.
  • a UE may provide HARQ-ACK feedback information when the UE is configured for multi-CW PDSCH reception on a serving cell, such as a base station, gNB, and the like, with a maximum of L CWs when using maxNrofCodeWordsScheduledByDCI and CBG-based HARQ-ACK feedback with N CBGs when using maxCodeBlockGroupsPerTransportBlock.
  • the UE may be scheduled with multi-codeword PDSCH reception and the legacy procedures/behavior may be applied in which N HARQ-ACK bits may be provided for the N CBGs per transport block.
  • the UE may be scheduled with singlecodeword and/or a transport block and may provide a HARQ-ACK feedback granularity of up to N*L sub-CBGs for the single scheduled CW and/or TB by using all the HARQ bits for the single transport block and/or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs.
  • the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying a CB to CBG mapping procedure by using N*L (sub- CBGs) instead of N (CBGs).
  • the single codeword PDSCH may be scheduled by: (1) DCI formats supporting single codeword PDSCH scheduling, such as DCI formats 1 0 or 1 2, or DCI formats that may be able to schedule multi-codeword PDSCH, such as DCI formats 1 0 or 1 2, (2) and/or by DCI formats supporting or not supporting CBG-based PDSCH scheduling, such as DCI format including or not including CBGTI information.
  • the single codeword PDSCH may be scheduled by a semi- persistent scheduling (SPS) grant.
  • SPS semi- persistent scheduling
  • Some exemplary embodiments may provide an operation that is applicable to HARQ-ACK feedback reporting for reception of an initial PDSCH transmission as well as for reception of a PDSCH re-transmission.
  • the above-described example refers to CBG-based PDSCH HARQ-ACK feedback
  • the procedures may be equally applicable to CBG- based PUSCH HARQ-ACK feedback operation.
  • Various exemplary embodiments may provide CBG-based scheduling.
  • a UE may be configured for multi-CW PDSCH reception on a serving cell with a maximum of L codewords when using maxNrofCodeWordsScheduledByDCI and CBG-based HARQ-ACK feedback with N CBGs when using maxCodeBlockGroupsPerTransportBlock).
  • the CBGTI in a scheduling DCI may be applied when the UE may be scheduled with multi-codework PDSCH reception and the legacy procedures ⁇ behavior may be applied in which 1 bit scheduling information is provided per CBG and per transport block.
  • Certain exemplary embodiments may provide that the UE may be scheduled with a single-codeword and/or transport block.
  • the CBG-based PDSCH scheduling granularity of up to N*L sub-CBGs may be applied for the single scheduled CW and/or TB by using all the CBGTI bits for the single transport block and/or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs.
  • the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
  • the single CW PDSCH may be either scheduled by DCI formats only supporting single codeword PDSCH scheduling where DCI formats 1 0 or 1 2, or DCI formats may be able to schedule multi-CW PDSCH with DCI formats 1 0 or 1 2, as long as the single CW PDSCH contains the CBG transmission indication information.
  • the one or more exemplary procedures described herein may be applicable to PDSCH reception of an initial PDSCH transmission as well as for reception of a PDSCH re-transmission.
  • FIG. 3 illustrates a diagram showing one CBGTI bit may correspond to a pair of CBGs when two TBs are scheduled and to a single CBG when one TB is scheduled, according to various exemplary embodiments.
  • FIG. 3 may be another manner of illustrating the examples shown in FIGs. 1 and 2. Substantially the same result may be achieved in FIG. 3 by bundling CBGs of single-TB PUSCH to CBG pairs for dual-TB PDSCH instead of splitting CBGs to sub-CBGs. This way the CBG generation would be unchanged, but the bundling of CBs to CB pairs for CBGTI/HARQ-ACK would need to be introduced when two TBs are scheduled.
  • the one or more procedures described herein for downlink PDSCH may be applied for uplink PUSCH transmission, except for HARQ-ACK.
  • a network entity such as a gNB, may determine in the PUSCH decoding process whether there is decoding success for each CB (and consecutively each CBG), and may schedule the PUSCH retransmission to only include the CBGs with erroneous CBs.
  • Generating HARQ-ACK feedback and transmitting the HARQ-ACK feedback may not be needed as decoding an uplink TB and scheduling its retransmission is internal to the network entity (e.g., gNB).
  • the procedures described herein for CBG based HARQ-ACK feedback for PDSCH may be equally applied to CBG based HARQ-ACK feedback for PUSCH when supported.
  • Various exemplary embodiments may provide one or more procedures for HARQ-ACK feedback.
  • the UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling, such as RRC, for multi-CW PDSCH scheduling of up to L CWs and a CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell).
  • the UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format or based on semi-persistent scheduling, which may include reception of initial PDSCH transmissions or PDSCH re-transmissions.
  • the one or more procedures may further include the UE decoding the scheduled PDSCH.
  • the UE may generate or prepare the HARQ-ACK information for the PDSCH based on wherein the UE is scheduled for a single-codeword or transport block, or for multi-codework PDSCH reception.
  • 1 HARQ-ACK bit may be provided per CBG and per transport block, such that N HARQ-ACK bits for the N CBGs per transport block may be provided for multi-CW PDSCH transmissions.
  • the UE may provide a HARQ-ACK feedback granularity of up to N*L sub-CBGs for the single scheduled CW or TB by using all of the HARQ-ACK bits for the single transport block or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi- CW PDSCH operation into L sub-CBGs.
  • the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying the CB to CBG mapping procedure according to various exemplary embodiments using N*L (sub-CBGs) instead ofN (CBGs).
  • the UE may transmit the N*L HARQ-ACK feedback bits for the scheduled PDSCH as part a HARQ-ACK codebook on a PUCCH or PUSCH to the gNB.
  • the N*L HARQ-ACK feedback bits may include, for example, a Type 1, Type 2, and/or Type 3 HARQ-ACK codebook.
  • the gNB may receive the provided HARQ-ACK information for the scheduled PDSCH on the cell.
  • the HARQ-ACK information bits may be associated with 1 HARQ-ACK bit per CBG and per transport block, such as N HARQ-ACK bits for the N CBGs per transport block, for multi-codeword PDSCH transmissions.
  • the HARQ-ACK information bits of the PDSCH may be interpreted with 1 HARQ-ACK bit per sub-CBG of the single scheduled PDSCH codeword and/or transport block.
  • N*L sub-CBGs of smaller size/higher granularity may be achieved as compared to the CBG size of a maximum of N CBGs.
  • the sub-CBG definition may be defined by splitting each CBG of multicodeword PDSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure to assign the CBs of a CBG to the L sub-CBGs or may be defined by applying the CB to CBG mapping procedure using N*L (sub- CBGs) instead of N (CBGs).
  • Various exemplary embodiments may provide one or more procedures for CBGTI transmission.
  • the one or more procedures may provide that a UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling (e.g., RRC) for multi-CW PDSCH scheduling of up to L codewords and CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell).
  • the UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format providing CBGTI, which may include reception of initial PDSCH transmissions or PDSCH retransmissions.
  • the UE may decode the scheduled PDSCH based on a scheduling assumption provided by CBGTI.
  • An example of the scheduling assumption may be when the UE is scheduled with multi-codework PDSCH reception, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1’ for each CBG transmitted and/or ‘0’ for each CBG not transmitted for the N CBGs per transport block are provided, for multi-CW PDSCH transmission.
  • the CBGTI field may provide a PDSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
  • Various exemplary embodiments may provide one or more procedures for CBGTI transmission.
  • the one or more procedures may provide that a UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling (e.g., RRC) for multi-CW PUSCH scheduling of up to L codewords and CBG-based operation with up to N CBGs per transport block on a serving cell (or UL BWP of the serving cell).
  • the UE may be scheduled for PUSCH transmission by the gNB using DCI format providing CBGTI, which may include transmission of initial PUSCH transmissions or PUSCH retransmissions.
  • the UE may transmit the scheduled PUSCH based on a scheduling assumption provided by CBGTI.
  • An example of the scheduling assumption may be when the UE is scheduled with multi-codework PUSCH transmission, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1 ’ for each CBG to be transmitted and/or ‘0’ for each CBG not to be transmitted for the N CBGs per transport block are provided, for multi-CW PUSCH transmission.
  • the CBGTI field may provide a PUSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi-codeword PUSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
  • Certain exemplary embodiments may provide one or more procedures for a combination of HARQ-ACK feedback and CBGTI transmission.
  • the one or more procedures may provide that the UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling, such as RRC, for multi-CW PDSCH scheduling of up to L CWs and a CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell).
  • the UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format providing CBGTI, which may include reception of initial PDSCH transmissions or PDSCH re-transmissions.
  • the UE may decode the scheduled PDSCH based on a scheduling assumption provided by CBGTI.
  • An example of the scheduling assumption may be when the UE is scheduled with multi-codework PDSCH reception, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1’ for each CBG transmitted and/or ‘0’ for each CBG not transmitted for the N CBGs per transport block are provided, for multi-CW PDSCH transmission.
  • the CBGTI field may provide a PDSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW.
  • the sub-CBGs may be defined by splitting each CBG of multi-CW PDSCH operation into L sub-CBGs.
  • the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs.
  • the sub-CBGs may be created by applying the CB to CBG mapping procedure according to various exemplary embodiments using N*L (sub-CBGs) instead of N (CBGs).
  • the UE may transmit the N*L HARQ-ACK feedback bits for the scheduled PDSCH as part a HARQ-ACK codebook on a PUCCH or PUSCH to the gNB.
  • the N*L HARQ-ACK feedback bits may include, for example, a Type 1, Type 2, and/or Type 3 HARQ-ACK codebook.
  • the gNB may receive the provided HARQ-ACK information for the scheduled PDSCH on the cell.
  • the HARQ-ACK information bits may be associated with 1 HARQ-ACK bit per CBG and per transport block, such as N HARQ-ACK bits for the N CBGs per transport block, for multi-codeword PDSCH transmissions.
  • the HARQ-ACK information bits of the PDSCH may be interpreted with 1 HARQ-ACK bit per sub-CBG of the single scheduled PDSCH codeword and/or transport block.
  • N*L sub-CBGs of smaller size/higher granularity may be achieved as compared to the CBG size of a maximum of N CBGs.
  • FIG. 4 illustrates an example flow diagram of a method, according to certain exemplary embodiments.
  • the method of FIG. 4 may be performed by a network element, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR.
  • the method of FIG. 4 may be performed by a user equipment, user device, or mobile device connected to the network, such as a UE similar to apparatus 710 illustrated in FIG. 7.
  • the method of FIG. 4 may include, at 410, determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel.
  • the method may further include generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the method may also include, at 430, providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • each of the plurality of codeblock groups may be split by the maximum number of codewords to form the plurality of sub-groups.
  • Certain exemplary embodiments may provide that the plurality of sub-groups may be formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
  • the feedback may be provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
  • the single codeword or transport block on the shared data channel may be either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel, or based on a semi-persistent shared data channel transmission, or based on a configured-grant shared data channel transmission.
  • the hybrid automatic repeat request acknowledgement feedback operation may be activated by higher layer signalling.
  • the higher layer signalling may be a radio resource control message.
  • FIG. 5 illustrates an example flow diagram of another method, according to certain exemplary embodiments. In an example embodiment, the method of FIG.
  • FIG. 5 may be performed by a network element, or a group of multiple network elements in a 3 GPP system, such as LTE or 5G-NR.
  • the method of FIG. 5 may be performed by a user equipment, user device, or mobile device connected to the network, such as another example of a UE similar to apparatus 710 illustrated in FIG. 7.
  • the method of FIG. 5 may include, at 510, decoding, by a user equipment, a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information.
  • the method may also include determining, by the user equipment, based on the scheduling information, that the user equipment is scheduled with a single codeword or transport block on the shared data channel.
  • the method may further include, at 530, determining, by the user equipment, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Some exemplary embodiments may provide that each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups. Certain exemplary embodiments may provide the plurality of sub-groups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
  • the scheduling information may be provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block.
  • the single codeword or transport block on the shared data channel may be scheduled by a downlink control information on a downlink control channel.
  • the downlink control information format may be configured to schedule at least one codeword or transport block for the shared data channel.
  • the shared data channel operation may be activated by higher layer signalling.
  • the higher layer signalling may be a radio resource control message.
  • FIG. 6 illustrates an example flow diagram of a further method, according to certain exemplary embodiments.
  • the method of FIG. 6 may be performed by a network element, or a group of multiple network elements in a 3 GPP system, such as LTE or 5G-NR.
  • the method of FIG. 6 may be performed by a user equipment, user device, or mobile device connected to the network, such as a further example of a UE similar to apparatus 710 illustrated in FIG. 7.
  • the method of FIG. 6 may include, at 610, decoding, by a user equipment, a control channel scheduling the user equipment for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the method may include determining, by the user equipment, that the user equipment is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and at 630, generating, by the user equipment, a hybrid automatic repeat request generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the method may also include, at 640, providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • FIG. 7 illustrates a set of apparatuses 710 and 720 according to various exemplary embodiments.
  • the apparatus 710 may be an element in a communications network or associated with such a network, such as a UE, RedCap UE, SL UE, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, or other device.
  • the UE according to various exemplary embodiments discussed above may be an example of apparatus 710. It should be noted that one of ordinary skill in the art would understand that apparatus 710 may include components or features not shown in FIG. 7.
  • apparatus 720 may be a network, network entity, element of the core network, or element in a communications network or associated with such a network, such as a base station, an NE, or a gNB.
  • the gNB according to various exemplary embodiments as discussed above may be an example of apparatus 720. It should be noted that one of ordinary skill in the art would understand that apparatus 720 may include components or features not shown in FIG. 7. It should be noted that one of ordinary skill in the art would understand that apparatus 720 may include components or features not shown in FIG. 7.
  • the apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7.
  • the memory may store instructions that, when executed by the processor, cause the apparatus 710 to determine that the apparatus 710 is scheduled with a single codeword or transport block for a shared data channel, and to generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus 710 may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • a variation of the apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7.
  • the memory may store instructions that, when executed by the processor, cause the apparatus 710 to decode a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the apparatus 710 may also be caused to determine, based on the scheduling information, that the apparatus 710 may be scheduled with a single codeword or transport block on the shared data channel.
  • the apparatus 710 may further be caused to determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7.
  • the memory may store instructions that, when executed by the processor, cause the apparatus 710 to decode a control channel scheduling the user equipment for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the apparatus may also be caused to generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus 710 may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Various exemplary embodiments described above may provide several technical improvements, enhancements, and/or advantages. For instance, some exemplary embodiments may provide advantages of one or more procedures to provide a higher granularity of CBG-based PDSCH HARQ-ACK feedback and PDSCH/PUSCH CBG-based scheduling granularity for single codeword PDSCH/PUSCH when configured with multi-CW PDSCH/PUSCH operation without additional DL/UL control overhead. Certain exemplary embodiments may advantageously provide that re-using unused bits in the HARQ-ACK feedback or the CBGTI field of the not scheduled TBs/ CWs for the single scheduled TB/CW.
  • apparatuses 710 and/or 720 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface.
  • apparatuses 710 and/or 720 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies.
  • apparatuses 710 and/or 720 may include or be coupled to processors 712 and 722, respectively, for processing information and executing instructions or operations.
  • processors 712 and 722 may be any type of general or specific purpose processor.
  • processors 712 and 722 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 712 (and 722) for each of apparatuses 710 and/or 720 is shown in FIG. 7, multiple processors may be utilized according to other example embodiments.
  • apparatuses 710 and/or 720 may include two or more processors that may form a multiprocessor system (for example, in this case processors 712 and 722 may represent a multiprocessor) that may support multiprocessing.
  • the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster).
  • Processors 712 and 722 may perform functions associated with the operation of apparatuses 710 and/or 720, respectively, including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 710 and/or 720, including processes illustrated in FIGs. 1-6.
  • Apparatuses 710 and/or 720 may further include or be coupled to memory 714 and/or 724 (internal or external), respectively, which may be coupled to processors 712 and 722, respectively, for storing information and instructions that may be executed by processors 712 and 722.
  • Memory 714 (and memory 724) may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory.
  • memory 714 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media.
  • RAM random access memory
  • ROM read only memory
  • HDD hard disk drive
  • the instructions stored in memory 714 and memory 724 may include program instructions or computer program code that, when executed by processors 712 and 722, enable the apparatuses 710 and/or 720 to perform tasks as described herein.
  • apparatuses 710 and/or 720 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium.
  • an external computer readable storage medium such as an optical disc, USB drive, flash drive, or any other storage medium.
  • the external computer readable storage medium may store a computer program or software for execution by processors 712 and 722 and/or apparatuses 710 and/or 720 to perform any of the methods illustrated in FIGs. 1-6.
  • apparatuses 710 and/or 720 may also include or be coupled to one or more antennas 715 and 725 for receiving a downlink signal and for transmitting via an uplink from apparatus 710 and apparatus 720, respectively.
  • Apparatuses 710 and/or 720 may further include transceivers 716 and 726, respectively, configured to transmit and receive information.
  • the transceiver 716 and 726 may also include a radio interface that may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, or the like.
  • the radio interface may include other components, such as filters, converters (for example, digital-to-analog converters or the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, or the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
  • filters for example, digital-to-analog converters or the like
  • symbol demappers for example, digital-to-analog converters or the like
  • signal shaping components for example, an Inverse Fast Fourier Transform (IFFT) module, or the like
  • IFFT Inverse Fast Fourier Transform
  • transceivers 716 and 726 may be respectively configured to modulate information on to a carrier waveform for transmission, and demodulate received information for further processing by other elements of apparatuses 710 and/or 720.
  • transceivers 716 and 726 may be capable of transmitting and receiving signals or data directly.
  • apparatuses 710 and/or 720 may include an input and/or output device (I/O device).
  • apparatuses 710 and/or 720 may further include a user interface, such as a graphical user interface or touchscreen.
  • memory 714 and memory 724 store software modules that provide functionality when executed by processors 712 and 722, respectively.
  • the modules may include, for example, an operating system that provides operating system functionality for apparatuses 710 and/or 720.
  • the memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 710 and/or 720.
  • the components of apparatuses 710 and/or 720 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 710 may optionally be configured to communicate with apparatus 720 via a wireless or wired communications link 730 according to any radio access technology, such as NR.
  • processors 712 and 722, and memory 714 and 724 may be included in or may form a part of processing circuitry or control circuitry.
  • transceivers 716 and 726 may be included in or may form a part of transceiving circuitry.
  • an apparatus may include means for performing a method, a process, or any of the variants discussed herein.
  • the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.
  • Certain exemplary embodiments may be directed to an apparatus that includes means for determining that the apparatus may be scheduled with a single codeword or transport block for a shared data channel, and means for generating a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may also include means for providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • Some exemplary embodiments may be directed to another apparatus that includes means for decoding a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission.
  • the shared data channel reception or transmission may be based on codeblock group transmission information.
  • the apparatus may also include means for determining, based on the scheduling information, that the apparatus may be scheduled with a single codeword or transport block on the shared data channel.
  • the apparatus may also include means for determining, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission.
  • the codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • Various exemplary embodiments may be directed to a further apparatus that includes means for decoding a control channel scheduling the user equipment for a physical downlink shared data channel reception.
  • the physical downlink shared data channel reception may be based on codeblock group transmission information.
  • the apparatus may also include means for determining that the apparatus may be scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and means for generating a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of subgroups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
  • the apparatus may further include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
  • the term “circuitry” may refer to hardware-only circuitry implementations (for example, analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software, including digital signal processors, that work together to cause an apparatus (for example, apparatus 710 and/or 720) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation.
  • circuitry may also cover an implementation of merely a hardware circuit or processor or multiple processors, or portion of a hardware circuit or processor, and the accompanying software and/or firmware.
  • the term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
  • a computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments.
  • the one or more computerexecutable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.
  • software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the computer readable medium or computer readable storage medium may be a non- transitory medium.
  • the functionality may be performed by hardware or circuitry included in an apparatus (for example, apparatuses 710 and/or 720), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.
  • an apparatus such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Abstract

Sub-codeblock group based operation for single codeword scheduling is provided. A method for sub-codeblock group based operation for single codeword scheduling may include determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel, and generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The method may also include providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.

Description

TITLE:
SUB-CODEBLOCK GROUP BASED OPERATION FOR SINGLE CODEWORD SCHEDULING
TECHNICAL FIELD:
[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or other communications systems. For example, certain example embodiments may relate to sub-codeblock group based operation for single codeword scheduling.
BACKGROUND:
[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE- A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. Fifth generation (5G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G network technology is mostly based on new radio (NR) technology, but the 5G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit/s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (loT).
SUMMARY:
[0003] Various exemplary embodiments may provide a method including determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel, and generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The method may also include providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0004] Some exemplary embodiments may provide a method including decoding, by a user equipment, a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The method may also include determining, by the user equipment, based on the scheduling information, that the user equipment is scheduled with a single codeword or transport block on the shared data channel, and determining, by the user equipment, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0005] Certain exemplary embodiments may provide a method including decoding, by a user equipment, a control channel scheduling the user equipment for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The method may also include determining, by the user equipment, that the user equipment is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The method may also include providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0006] Various exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus at least to determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel and generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0007] Certain exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus at least to decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The apparatus may also be caused to determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel, and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0008] Various exemplary embodiments may provide an apparatus including at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, may cause the apparatus at least to decode a control channel scheduling the apparatus for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The apparatus may also be caused to determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception and generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may further be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0009] Some exemplary embodiments may provide an apparatus including means for determining that the apparatus is scheduled with a single codeword or transport block for a shared data channel and means for generating a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may also include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0010] Various exemplary embodiments may provide an apparatus including means for decoding a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The apparatus may also include means for determining based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel, and means for determining, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0011] Certain exemplary embodiments may provide an apparatus including means for decoding a control channel scheduling the apparatus for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The apparatus may also include means for determining that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and means for generating a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may further include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0012] Various exemplary embodiments may provide a non- transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel and generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0013] Some exemplary embodiments may provide a non-transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The apparatus may also be caused to determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0014] Various exemplary embodiments may provide a non-transitory computer readable medium including program instructions that, when executed by an apparatus, cause the apparatus at least to decode a control channel scheduling the apparatus for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The apparatus may also be caused to determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception and generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may further be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0015] Various exemplary embodiments may provide one or more computer programs including instructions stored thereon for performing one or more of the methods described herein. Some exemplary embodiments may also provide one or more apparatuses including one or more circuitry configured to perform one or more of the methods described herein.
BRIEF DESCRIPTION OF THE DRAWINGS:
[0016] For proper understanding of example embodiments, reference should be made to the accompanying drawings, as follows:
[0017] FIG. 1 illustrates an example of a diagram of a codeblock group transmission information, according to various exemplary embodiments;
[0018] FIG. 2 illustrates an example of a diagram of feedback implementation, according to various exemplary embodiments;
[0019] FIG. 3 illustrates a diagram showing a configuration, according to various exemplary embodiments;
[0020] FIG. 4 illustrates an example of a flow diagram of a method, according to certain exemplary embodiments;
[0021] FIG. 5 illustrates an example of a flow diagram of another method, according to certain exemplary embodiments;
[0022] FIG. 6 illustrates an example of a flow diagram of a further method, according to certain exemplary embodiments; and
[0023] FIG. 7 illustrates a set of apparatuses, according to various exemplary embodiments. DETAILED DESCRIPTION:
[0024] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some exemplary embodiments of systems, methods, apparatuses, and non- transitory computer program products for sub-codeblock group based operation for single codeword scheduling. Although the devices discussed below and shown in the figures refer to 5G or Next Generation NodeB (gNB) devices and user equipment (UE), this disclosure is not limited to only gNBs and UEs. For example, the following description may also apply to any type of network access node or entity and UE or mobile device.
[0025] Additionally, if desired, the different functions or procedures discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.
[0026] In 5G/NR technology, CodeBlock group (CBG) based hybrid automatic repeat request (HARQ) acknowledgement (ACK) feedback for physical downlink shard channel (PDSCH) and CBG-based physical uplink shared channel (PUSCH) and/or PDSCH scheduling may allow for a finer granularity of HARQ-feedback for PDSCH and finer retransmission granularity for PDSCH & PUSCH. In transport block (TB)- based HARQ, a single HARQ- ACK bit may be provided per TB. When one code block (CB) in the TB is in error, such as the CB was decoded erroneously, the entire TB that may consist of a large number of CBs may be indicated as being erroneous regardless of how many CBs of the TB were decoded correctly. [0027] CBG-based HARQ may avoid unnecessarily retransmitting all the correctly decoded CBs in the event that one or more erroneous CBs and one or more correctly decoded CBs exist in a TB. To avoid unnecessarily retransmitting correctly decoded CBs, each CB may have its own HARQ- ACK bit, and in retransmission, each CB may be separately indicated to be either present or absent, and omitting a CB from a retransmission may be due to the CB being already correctly delivered/decoded after a previous transmission attempt. A potential deficiency with separately evaluating the HARQ- ACK bit of each CB may be that it causes a high overhead or high processing burden due to the potentially large number of CBs in a TB. To aid in addressing this deficiency, the concept of grouping the CBs into CBGs was adopted in certain situations.
[0028] During CBG based transmission, the CBs of a single TB and/or CodeWord (CW) may be grouped in multiple CBGs with substantially similar or equal sizes. The maximum number of CBGs N for PDSCH and/or PUSCH may be configured by a radio resource control (RRC) message using a parameter maxCodeBlockGroupsPerTransportBlock with possible values of {2, 4, 6, 8}. The number of CBs C may be assigned to the up to N CBG groups. When a UE is configured to receive CBG-based transmissions by receiving a higher layer parameter of codeBlockGroupTransmission for PDSCH, the UE may determine the number of CBGs M for a TB reception as M = min (N, C). N may be defined as the maximum number of CBGs per TB as configured by maxCodeBlockGroupsPerTransportBlock for PDSCH and C may be the number of CBs in the TB. The CBGs may be defined using pseudo code c c defining
Figure imgf000011_0001
= mod(C, M), K = [— ], and K2 = [— ]. Applying the pseudo code, the CBs assigned to the CBGs may be determined by:
Figure imgf000011_0002
> 0, CBG m, m = 0,1,
Figure imgf000011_0003
may be formed of code blocks with indices m - K + k, k = 0,1,
Figure imgf000011_0004
CBG m, m = M1, M1 + 1, . . . , M - 1 may be formed of code blocks with indices
Figure imgf000011_0005
+ (m — MQ • K2 + k,k = 0,1, ... , K2 - 1. [0029] In CBG-based HARQ-ACK feedback indication for PDSCH, a HARQ-ACK bit for each of the individual CBGs may be fed back for the overall TB. By being able to determine the correct reception of parts of the overall TB may allow for DL data scheduling to re-transmit part of the overall TB instead of the full TB, which is denoted here as ‘CBG-based scheduling’ for PDSCH.
[0030] For CBG-based PDSCH and/or PUSCH scheduling, the CBGs of the TB that are to be transmitted or retransmitted may be indicated in scheduling downlink control information (DCI) for the PDSCH and/or PUSCH. For NR DCI formats 0 1 (scheduling PUSCH) and DCI format 1 1 (scheduling PDSCH), a separate field for CBG transmission indication (CBGTI) may be included to indicate one or more CBGs that may be part of the scheduled PUSCH/PDSCH transmission. The CBGTI field may include one bit for each CBG to allow per CBG presence indication of the scheduled PDSCH / PUSCH. For the initial transmission, all CBGs may be scheduled. For example, a full TB may be scheduled for the first transmission. The CBGTI field may apply equally to PUSCH and/or PDSCH transmissions.
[0031] There may be some inefficiencies in the CBG-based HARQ and scheduling operation, such as when there are multiple (e.g., 2) transport block and/or CodeWord operations for PDSCH operation, which may be configured with maxNrofCodeWordsScheduledByDCI. For example, when a single TB is scheduled, half of the CBG-based HARQ-ACK bits and half of the CBGTI bits may be unused. For HARQ-ACK feedback operation, only the HARQ-ACK bits for a first number of CBGs M out of a total of 2*N may be used. In an example for Type-1 HARQ-ACK code book, the parameter maxNrofCodeWordsScheduledByDCI may indicate reception of up to two TBs, when the UE receives a PDSCH with one TB or a semi-persistent scheduling (SPS) PDSCH release or a transmission configuration indicator (TCI) state update. The HARQ-ACK information may be associated with a first TB and the UE may generate a non- acknowledgement (NACK) for a second (not present) TB if the parameter harq-ACKSpatialBundlingPUCCH is not provided. The UE may also generate HARQ- ACK information with a value of ACK for the second (not present) TB when the parameter harq-ACK-SpatialBundlingPUCCH is provided. In both cases, the transmitter may know that there was no second TB and may ignore the bit in the HARQ- ACK codebook related to the second TB.
[0032] In an example for Type-2 HARQ-ACK code book, a PDCCH monitoring occasion may be provided with a DCI format scheduling PDSCH reception or with associated HARQ-ACK information without scheduling the PDSCH reception. During an active DL bandwidth part (BWP) of a serving cell, a UE may receive a PDSCH with one transport block or detect a DCI format having associated HARQ-ACK information without scheduling PDSCH reception. A value of the parameter maxNrofCodeWordsScheduledByDCI may be set at 2 and the HARQ-ACK information may be associated with a first transport block. As such, the UE may generate a NACK for a second transport block when the parameter harq-ACKSpatialBundlingPUCCH is not provided and may generate HARQ-ACK information with a value of ACK for the second transport block when the parameter harq-ACK-SpatialBundlingPUCCH is provided. [0033] CBGTI information may be in a DCI format 1 1 for scheduling CBG-based PDSCH. A UE may be configured to receive CBG-based transmissions by receiving the higher layer parameter codeBlockGroupTransmission for PDSCH. In this case, the CBGTI field of the DCI format 1 1 may have a length NTB ■ N bits, where NTB may be defined as the value of the higher layer parameter maxNrofCodeWordsScheduledByDCI. When NTB = 2 , the CBGTI field bits may be mapped such that a first set of N bits starting from a most significant bit (MSB) that may correspond to the first TB while a second set of N bits may correspond to a second TB when scheduled. The first M bits of each set of N bits in the CBGTI field may have an in-order one-to- one mapping with the CBGs of the TB with the MSB mapped to CBG#0. [0034] For an initial transmission of a TB, which may be indicated by a 'New Data Indicator' field of the scheduling DCI, the UE may assume that all the CBGs of the TB are present. For a retransmission of a TB, which may also be indicated by the 'New Data Indicator' field of the scheduling DCI, the UE may assume that the CBGTI field of the scheduling DCI may indicate which CBGs of the TB are present in the transmission. A bit value of '0' in the CBGTI field may indicate that a corresponding CBG is not transmitted and T indicates that the corresponding CBG is transmitted. Further, the UE may assume that when a 'CBG flushing out information' (CBGFI) field of the scheduling DCI is present, the CBGFI set to '0' may indicate that earlier received instances of the same CBGs being transmitted may be corrupted, and the CBGFI set to T may indicate that the CBGs being retransmitted are combinable with the earlier received instances of the same CBGs. The UE may also assume that a CBG contains the same CBs during retransmission as in the initial transmission of the TB.
[0035] When only one TB is transmitted when the parameter maxNrofCodeWordsScheduledByDCI is set to 2, then half of the CBGTI bits in the DCI may be wasted. The CBGTI field may be set to a size of 0 bit when the higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, the CBGTI field size may be set to 2, 4, 6, or 8 bits based on the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.
[0036] As an example, a UE may be configured for dual-codeword, or 2 TB operation (maxNrofCodeWordsScheduledByDCI set to 2) and configured with 4 CBGs (maxCodeBlockGroupsPerTransportBlock set to ‘n4’). The UE may be configured for single TB scheduling with a TB size of 22 CBs. The 22 CBs of the scheduled transmission may be assigned to 4 CBGs, such as, for example, CBG#0: CB #0..#5, CBG#1: CB #6..#11, CBG#2: CB #12..#16, CBG#3: CB #17..#21. An 8-bit CBGTI information (N*N_TB=4*2=8) may provide scheduling information for the scheduled TB, with a value of “0” provided for the CBGTI bits associated with a second non-scheduled TB. For example, the CBGTI may be as follows: {CBG#0 TB1, CBG#1 TB1, CBG#2 TB1, CBG#3 TB1, 0,0, 0,0}. In a received HARQ-ACK feedback with a total of 8 HARQ-ACK bits for the PDSCH scheduled, the first 4 bits may have useful HARQ-ACK information for the first, scheduled TB, and the second 4 bits of the HARQ- ACK information may not due to being associated with the second nonscheduled TB, which may be set to NACK or 0. For example, the HARQ- ACK feedback information may be as follows: {HARQ-ACK CBG#0 TB1, HARQ-ACK CBG#1 TB1, HARQ-ACK CBG#2 TB1, HARQ-ACK CBG#3 TB1, ‘NACK’, ‘NACK’, ‘NACK’, ‘NACK’}.
[0037] Various exemplary embodiments may provide advantages to aid in resolving the deficiencies discussed above. For example, certain exemplary embodiments may provide one or more procedures to optimize a CBG-based scheduling operation in which two transport blocks may be capable of being scheduled for the UE, but only a single transport block has been scheduled. Various exemplary embodiments may advantageously provide for doubling the HARQ-ACK feedback and/or scheduling granularity without any additional UL or DL control signaling overhead.
[0038] Certain exemplary embodiments may provide one or more procedures for a situation in which a single TB is scheduled, the feedback granularity may be doubled to 2* maxCodeBlockGroupsPerTransportBlock to use all of the available CBGTI/HARQ-ACK feedback bits for the single scheduled transport block. This may eliminate setting the CBGTI bits to 0 and the HARQ- ACK feedback bits to NACK for the second non-scheduled transport block.
[0039] An example according to various exemplary embodiments may set 4 CBGs per TB with dual-codeword or 2 transport block operation for single transport block scheduling and a transport block size of 22 CBs. The 22 CBs of the scheduled transmission may be assigned to 4 CBGs, such as CBG#0: CB #0..#5, CBG#1: CB #6..#11, CBG#2: CB #12..#16, CBG#3: CB #17..#21.
[0040] FIG. 1 illustrates an example of a diagram of a CBGTI implementation for this example, according to various exemplary embodiments. The CBGTI may be 8-bit information. In the diagram of FIG. 1, the legacy behaviour may be shown in an upper row including ‘0’s for the second non-scheduled TB and a lower row of the diagram may show that each of the CBGs may be split into two sub-CBGs with approximately double the granularity. Each CBG #X may be split in two sub-CBGs, CGB #XA and #XB, with approximately equal size. The size association may be used by having the size of CBG #XA >= the size of CBG #XB. The exemplary embodiments are not limited to this example of FIG. 1. Any maximum number of codewords and/or transport blocks may be used by splitting each original CBG into maxNrofCodeWordsScheduledByDCI sub-CBGs. Alternatively, the double number of CBGs for the single TB/CW scheduled PDSCH may be assumed, such as, for example, assuming 2*N CBGs or maxNrofCodeWordsScheduledByDCI * maxCodeBlockGroupsPerTransportBlock CBGs. In this alternative, the CBs for a single CW transmission may be paired with a set of other CBs in a sub-CBG not contained in the same CBG in dual (or multi-) CW transmission, which may limit the usage for re-transmission operation of mixed single or dual CW operation.
[0041] FIG. 2 illustrates an example of a diagram of a HARQ feedback implementation, according to various exemplary embodiments. FIG. 2 shows an example of 8-bit HARQ-ACK information, in which the upper row shows the legacy implementation including ‘NACK’ i.e. ‘0’s for the last 4 bits for the second non-scheduled PDSCH transport block for comparison with the lower row, which shows the HARQ feedback for one or more procedures according to various exemplary embodiments. In the various exemplary embodiments, all of the 8-bit HARQ-ACK feedback information may be used for a single scheduled PDSCH transport block with approximately double the granularity and half the CBG size. The CBGs may be split into the same CBGs as for the CBGTI (e.g., CBG #XA & CBG #XB), by applying a CB to CBG association pseudo code within a CBG to create the maxNrofCodeWordsScheduledByDCI sub-CBGs A/B. c
The pseudo code may define that
Figure imgf000017_0001
= mod(C, M), K = [— ], and /Q = c
[— ] . Applying the pseudo code, the CBs assigned to the CBGs may be determined by:
Figure imgf000017_0002
> 0, CBG m, m = 0,1,
Figure imgf000017_0003
— 1, may be formed of code blocks with indices m • K1 + k, k = 0,1, . . . , K1 — 1. CBG m, m = M1, M1 +
Figure imgf000017_0004
— 1 may be formed of code blocks with indices
Figure imgf000017_0005
K + (m — Mi) • K2 + k, k = 0,1, ... , K2 — 1 . Alternatively, the CB to CBG association may be reused assuming 2*N CBGs or maxNrofCode WordsScheduledByDCI* maxCodeBlockGroupsPerTransportBlock CBGs.
[0042] Certain exemplary embodiments may provide HARQ-ACK feedback. A UE may provide HARQ-ACK feedback information when the UE is configured for multi-CW PDSCH reception on a serving cell, such as a base station, gNB, and the like, with a maximum of L CWs when using maxNrofCodeWordsScheduledByDCI and CBG-based HARQ-ACK feedback with N CBGs when using maxCodeBlockGroupsPerTransportBlock. The UE may be scheduled with multi-codeword PDSCH reception and the legacy procedures/behavior may be applied in which N HARQ-ACK bits may be provided for the N CBGs per transport block. Various exemplary embodiments may provide that the UE may be scheduled with singlecodeword and/or a transport block and may provide a HARQ-ACK feedback granularity of up to N*L sub-CBGs for the single scheduled CW and/or TB by using all the HARQ bits for the single transport block and/or CW. [0043] As an exemplary implementation, the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs. The CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. As another example, the sub-CBGs may be created by applying a CB to CBG mapping procedure by using N*L (sub- CBGs) instead of N (CBGs).
[0044] The single codeword PDSCH may be scheduled by: (1) DCI formats supporting single codeword PDSCH scheduling, such as DCI formats 1 0 or 1 2, or DCI formats that may be able to schedule multi-codeword PDSCH, such as DCI formats 1 0 or 1 2, (2) and/or by DCI formats supporting or not supporting CBG-based PDSCH scheduling, such as DCI format including or not including CBGTI information. In addition, or alternatively, the single codeword PDSCH may be scheduled by a semi- persistent scheduling (SPS) grant.
[0045] Some exemplary embodiments may provide an operation that is applicable to HARQ-ACK feedback reporting for reception of an initial PDSCH transmission as well as for reception of a PDSCH re-transmission. Although the above-described example refers to CBG-based PDSCH HARQ-ACK feedback, the procedures may be equally applicable to CBG- based PUSCH HARQ-ACK feedback operation.
[0046] Various exemplary embodiments may provide CBG-based scheduling. A UE may be configured for multi-CW PDSCH reception on a serving cell with a maximum of L codewords when using maxNrofCodeWordsScheduledByDCI and CBG-based HARQ-ACK feedback with N CBGs when using maxCodeBlockGroupsPerTransportBlock). The CBGTI in a scheduling DCI may be applied when the UE may be scheduled with multi-codework PDSCH reception and the legacy procedures\behavior may be applied in which 1 bit scheduling information is provided per CBG and per transport block. Certain exemplary embodiments may provide that the UE may be scheduled with a single-codeword and/or transport block. The CBG-based PDSCH scheduling granularity of up to N*L sub-CBGs may be applied for the single scheduled CW and/or TB by using all the CBGTI bits for the single transport block and/or CW.
[0047] As an example, the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs. The CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. As another example, the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
[0048] According to various exemplary embodiments, the single CW PDSCH may be either scheduled by DCI formats only supporting single codeword PDSCH scheduling where DCI formats 1 0 or 1 2, or DCI formats may be able to schedule multi-CW PDSCH with DCI formats 1 0 or 1 2, as long as the single CW PDSCH contains the CBG transmission indication information. The one or more exemplary procedures described herein may be applicable to PDSCH reception of an initial PDSCH transmission as well as for reception of a PDSCH re-transmission.
[0049] FIG. 3 illustrates a diagram showing one CBGTI bit may correspond to a pair of CBGs when two TBs are scheduled and to a single CBG when one TB is scheduled, according to various exemplary embodiments. FIG. 3 may be another manner of illustrating the examples shown in FIGs. 1 and 2. Substantially the same result may be achieved in FIG. 3 by bundling CBGs of single-TB PUSCH to CBG pairs for dual-TB PDSCH instead of splitting CBGs to sub-CBGs. This way the CBG generation would be unchanged, but the bundling of CBs to CB pairs for CBGTI/HARQ-ACK would need to be introduced when two TBs are scheduled.
[0050] The one or more procedures described herein for downlink PDSCH may be applied for uplink PUSCH transmission, except for HARQ-ACK. In uplink, a network entity, such as a gNB, may determine in the PUSCH decoding process whether there is decoding success for each CB (and consecutively each CBG), and may schedule the PUSCH retransmission to only include the CBGs with erroneous CBs. Generating HARQ-ACK feedback and transmitting the HARQ-ACK feedback may not be needed as decoding an uplink TB and scheduling its retransmission is internal to the network entity (e.g., gNB). The procedures described herein for CBG based HARQ-ACK feedback for PDSCH may be equally applied to CBG based HARQ-ACK feedback for PUSCH when supported.
[0051] Various exemplary embodiments may provide one or more procedures for HARQ-ACK feedback. The UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling, such as RRC, for multi-CW PDSCH scheduling of up to L CWs and a CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell). The UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format or based on semi-persistent scheduling, which may include reception of initial PDSCH transmissions or PDSCH re-transmissions.
[0052] According to certain exemplary embodiments, the one or more procedures may further include the UE decoding the scheduled PDSCH. The UE may generate or prepare the HARQ-ACK information for the PDSCH based on wherein the UE is scheduled for a single-codeword or transport block, or for multi-codework PDSCH reception. When the UE is scheduled with multi-codework PDSCH reception, 1 HARQ-ACK bit may be provided per CBG and per transport block, such that N HARQ-ACK bits for the N CBGs per transport block may be provided for multi-CW PDSCH transmissions. When the UE is scheduled with a single-codeword or transport block, the UE may provide a HARQ-ACK feedback granularity of up to N*L sub-CBGs for the single scheduled CW or TB by using all of the HARQ-ACK bits for the single transport block or CW. For example, the sub-CBGs may be defined by splitting each CBG of multi- CW PDSCH operation into L sub-CBGs. The CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. In another example, the sub-CBGs may be created by applying the CB to CBG mapping procedure according to various exemplary embodiments using N*L (sub-CBGs) instead ofN (CBGs).
[0053] The UE may transmit the N*L HARQ-ACK feedback bits for the scheduled PDSCH as part a HARQ-ACK codebook on a PUCCH or PUSCH to the gNB. The N*L HARQ-ACK feedback bits may include, for example, a Type 1, Type 2, and/or Type 3 HARQ-ACK codebook. The gNB may receive the provided HARQ-ACK information for the scheduled PDSCH on the cell. For the HARQ-ACK feedback of multi-CW PDSCH transmission, the HARQ-ACK information bits may be associated with 1 HARQ-ACK bit per CBG and per transport block, such as N HARQ-ACK bits for the N CBGs per transport block, for multi-codeword PDSCH transmissions. For the HARQ-ACK feedback of single codework and/or transport block PDSCH transmissions on the serving cell, the HARQ-ACK information bits of the PDSCH may be interpreted with 1 HARQ-ACK bit per sub-CBG of the single scheduled PDSCH codeword and/or transport block. Up to N*L sub-CBGs of smaller size/higher granularity may be achieved as compared to the CBG size of a maximum of N CBGs. The sub-CBG definition may be defined by splitting each CBG of multicodeword PDSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure to assign the CBs of a CBG to the L sub-CBGs or may be defined by applying the CB to CBG mapping procedure using N*L (sub- CBGs) instead of N (CBGs).
[0054] Various exemplary embodiments may provide one or more procedures for CBGTI transmission. The one or more procedures may provide that a UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling (e.g., RRC) for multi-CW PDSCH scheduling of up to L codewords and CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell). The UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format providing CBGTI, which may include reception of initial PDSCH transmissions or PDSCH retransmissions.
[0055] The UE may decode the scheduled PDSCH based on a scheduling assumption provided by CBGTI. An example of the scheduling assumption may be when the UE is scheduled with multi-codework PDSCH reception, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1’ for each CBG transmitted and/or ‘0’ for each CBG not transmitted for the N CBGs per transport block are provided, for multi-CW PDSCH transmission. Another example of the scheduling assumption may be when the UE is scheduled with a single-CW and/or TB, the CBGTI field may provide a PDSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW. As an exemplary implementation, the sub-CBGs may be defined by splitting each CBG of multi-codeword PDSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. As another exemplary implementation, the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
[0056] Various exemplary embodiments may provide one or more procedures for CBGTI transmission. The one or more procedures may provide that a UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling (e.g., RRC) for multi-CW PUSCH scheduling of up to L codewords and CBG-based operation with up to N CBGs per transport block on a serving cell (or UL BWP of the serving cell). The UE may be scheduled for PUSCH transmission by the gNB using DCI format providing CBGTI, which may include transmission of initial PUSCH transmissions or PUSCH retransmissions.
[0057] The UE may transmit the scheduled PUSCH based on a scheduling assumption provided by CBGTI. An example of the scheduling assumption may be when the UE is scheduled with multi-codework PUSCH transmission, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1 ’ for each CBG to be transmitted and/or ‘0’ for each CBG not to be transmitted for the N CBGs per transport block are provided, for multi-CW PUSCH transmission. Another example of the scheduling assumption may be when the UE is scheduled with a single-CW and/or TB, the CBGTI field may provide a PUSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW. As an exemplary implementation, the sub-CBGs may be defined by splitting each CBG of multi-codeword PUSCH operation into L sub-CBGs, such as the CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. As another exemplary implementation, the sub-CBGs may be created by applying the CB to CBG mapping procedure by using N*L (sub-CBGs) instead of N (CBGs).
[0058] Certain exemplary embodiments may provide one or more procedures for a combination of HARQ-ACK feedback and CBGTI transmission. The one or more procedures may provide that the UE may be configured by a network entity, such as a base station, gNB, and the like, using higher layer signaling, such as RRC, for multi-CW PDSCH scheduling of up to L CWs and a CBG-based operation with up to N CBGs per transport block on a serving cell (or DL BWP of the serving cell). The UE may be scheduled for PDSCH reception on the serving cell by the gNB using DCI format providing CBGTI, which may include reception of initial PDSCH transmissions or PDSCH re-transmissions.
[0059] The UE may decode the scheduled PDSCH based on a scheduling assumption provided by CBGTI. An example of the scheduling assumption may be when the UE is scheduled with multi-codework PDSCH reception, 1 CBGTI bit may be provided per CBG and per transport block, such as N CBGTI bits indicating ‘ 1’ for each CBG transmitted and/or ‘0’ for each CBG not transmitted for the N CBGs per transport block are provided, for multi-CW PDSCH transmission. Another example of the scheduling assumption may be when the UE is scheduled with a single-CW and/or TB, the CBGTI field may provide a PDSCH scheduling granularity of up to N*L sub-CBGs for the single scheduled CW/TB by using all the CBGTI bits for the single TB or CW.
[0060] For example, the sub-CBGs may be defined by splitting each CBG of multi-CW PDSCH operation into L sub-CBGs. The CB to CBG mapping procedure may be applied to assign the CBs of a CBG to the L sub-CBGs. In another example, the sub-CBGs may be created by applying the CB to CBG mapping procedure according to various exemplary embodiments using N*L (sub-CBGs) instead of N (CBGs).
[0061] The UE may transmit the N*L HARQ-ACK feedback bits for the scheduled PDSCH as part a HARQ-ACK codebook on a PUCCH or PUSCH to the gNB. The N*L HARQ-ACK feedback bits may include, for example, a Type 1, Type 2, and/or Type 3 HARQ-ACK codebook. The gNB may receive the provided HARQ-ACK information for the scheduled PDSCH on the cell. For the HARQ-ACK feedback of multi-CW PDSCH transmission, the HARQ-ACK information bits may be associated with 1 HARQ-ACK bit per CBG and per transport block, such as N HARQ-ACK bits for the N CBGs per transport block, for multi-codeword PDSCH transmissions. For the HARQ-ACK feedback of single codeword and/or transport block PDSCH transmissions on the serving cell, the HARQ-ACK information bits of the PDSCH may be interpreted with 1 HARQ-ACK bit per sub-CBG of the single scheduled PDSCH codeword and/or transport block. Up to N*L sub-CBGs of smaller size/higher granularity may be achieved as compared to the CBG size of a maximum of N CBGs.
[0062] FIG. 4 illustrates an example flow diagram of a method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 4 may be performed by a network element, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an exemplary embodiment, the method of FIG. 4 may be performed by a user equipment, user device, or mobile device connected to the network, such as a UE similar to apparatus 710 illustrated in FIG. 7. [0063] According to various exemplary embodiments, the method of FIG. 4 may include, at 410, determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel. At 420, the method may further include generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The method may also include, at 430, providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0064] Various exemplary embodiments may provide that each of the plurality of codeblock groups may be split by the maximum number of codewords to form the plurality of sub-groups. Certain exemplary embodiments may provide that the plurality of sub-groups may be formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords. The feedback may be provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
[0065] Some exemplary embodiments may provide that the single codeword or transport block on the shared data channel may be either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel, or based on a semi-persistent shared data channel transmission, or based on a configured-grant shared data channel transmission. The hybrid automatic repeat request acknowledgement feedback operation may be activated by higher layer signalling. The higher layer signalling may be a radio resource control message. [0066] FIG. 5 illustrates an example flow diagram of another method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 5 may be performed by a network element, or a group of multiple network elements in a 3 GPP system, such as LTE or 5G-NR. For instance, in an exemplary embodiment, the method of FIG. 5 may be performed by a user equipment, user device, or mobile device connected to the network, such as another example of a UE similar to apparatus 710 illustrated in FIG. 7.
[0067] According to various exemplary embodiments, the method of FIG. 5 may include, at 510, decoding, by a user equipment, a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information. At 520, the method may also include determining, by the user equipment, based on the scheduling information, that the user equipment is scheduled with a single codeword or transport block on the shared data channel. The method may further include, at 530, determining, by the user equipment, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0068] Some exemplary embodiments may provide that each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups. Certain exemplary embodiments may provide the plurality of sub-groups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
[0069] Various exemplary embodiments may provide that the scheduling information may be provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block. The single codeword or transport block on the shared data channel may be scheduled by a downlink control information on a downlink control channel. The downlink control information format may be configured to schedule at least one codeword or transport block for the shared data channel. The shared data channel operation may be activated by higher layer signalling. The higher layer signalling may be a radio resource control message.
[0070] FIG. 6 illustrates an example flow diagram of a further method, according to certain exemplary embodiments. In an example embodiment, the method of FIG. 6 may be performed by a network element, or a group of multiple network elements in a 3 GPP system, such as LTE or 5G-NR. For instance, in an exemplary embodiment, the method of FIG. 6 may be performed by a user equipment, user device, or mobile device connected to the network, such as a further example of a UE similar to apparatus 710 illustrated in FIG. 7.
[0071] According to various exemplary embodiments, the method of FIG. 6 may include, at 610, decoding, by a user equipment, a control channel scheduling the user equipment for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. At 620, the method may include determining, by the user equipment, that the user equipment is scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and at 630, generating, by the user equipment, a hybrid automatic repeat request generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The method may also include, at 640, providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0072] FIG. 7 illustrates a set of apparatuses 710 and 720 according to various exemplary embodiments. In the various exemplary embodiments, the apparatus 710 may be an element in a communications network or associated with such a network, such as a UE, RedCap UE, SL UE, mobile equipment (ME), mobile station, mobile device, stationary device, loT device, or other device. For example, the UE according to various exemplary embodiments discussed above may be an example of apparatus 710. It should be noted that one of ordinary skill in the art would understand that apparatus 710 may include components or features not shown in FIG. 7. In addition, apparatus 720 may be a network, network entity, element of the core network, or element in a communications network or associated with such a network, such as a base station, an NE, or a gNB. For example, the gNB according to various exemplary embodiments as discussed above may be an example of apparatus 720. It should be noted that one of ordinary skill in the art would understand that apparatus 720 may include components or features not shown in FIG. 7. It should be noted that one of ordinary skill in the art would understand that apparatus 720 may include components or features not shown in FIG. 7.
[0073] According to various exemplary embodiments, the apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7. The memory may store instructions that, when executed by the processor, cause the apparatus 710 to determine that the apparatus 710 is scheduled with a single codeword or transport block for a shared data channel, and to generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus 710 may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0074] According to some exemplary embodiments, a variation of the apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7. The memory may store instructions that, when executed by the processor, cause the apparatus 710 to decode a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The apparatus 710 may also be caused to determine, based on the scheduling information, that the apparatus 710 may be scheduled with a single codeword or transport block on the shared data channel. The apparatus 710 may further be caused to determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0075] According to some exemplary embodiments, another variation of apparatus 710 may include at least one processor, and at least one memory, as shown in FIG. 7. The memory may store instructions that, when executed by the processor, cause the apparatus 710 to decode a control channel scheduling the user equipment for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The apparatus may also be caused to generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus 710 may also be caused to provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity. [0076] Various exemplary embodiments described above may provide several technical improvements, enhancements, and/or advantages. For instance, some exemplary embodiments may provide advantages of one or more procedures to provide a higher granularity of CBG-based PDSCH HARQ-ACK feedback and PDSCH/PUSCH CBG-based scheduling granularity for single codeword PDSCH/PUSCH when configured with multi-CW PDSCH/PUSCH operation without additional DL/UL control overhead. Certain exemplary embodiments may advantageously provide that re-using unused bits in the HARQ-ACK feedback or the CBGTI field of the not scheduled TBs/ CWs for the single scheduled TB/CW.
[0077] In some example embodiments, apparatuses 710 and/or 720 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and/or a user interface. In some example embodiments, apparatuses 710 and/or 720 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and/or any other radio access technologies.
[0078] As illustrated in the example of FIG. 7, apparatuses 710 and/or 720 may include or be coupled to processors 712 and 722, respectively, for processing information and executing instructions or operations. Processors 712 and 722 may be any type of general or specific purpose processor. In fact, processors 712 and 722 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 712 (and 722) for each of apparatuses 710 and/or 720 is shown in FIG. 7, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 710 and/or 720 may include two or more processors that may form a multiprocessor system (for example, in this case processors 712 and 722 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster).
[0079] Processors 712 and 722 may perform functions associated with the operation of apparatuses 710 and/or 720, respectively, including, as some examples, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 710 and/or 720, including processes illustrated in FIGs. 1-6.
[0080] Apparatuses 710 and/or 720 may further include or be coupled to memory 714 and/or 724 (internal or external), respectively, which may be coupled to processors 712 and 722, respectively, for storing information and instructions that may be executed by processors 712 and 722. Memory 714 (and memory 724) may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 714 (and memory 724) can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media. The instructions stored in memory 714 and memory 724 may include program instructions or computer program code that, when executed by processors 712 and 722, enable the apparatuses 710 and/or 720 to perform tasks as described herein.
[0081] In certain example embodiments, apparatuses 710 and/or 720 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 712 and 722 and/or apparatuses 710 and/or 720 to perform any of the methods illustrated in FIGs. 1-6.
[0082] In some exemplary embodiments, apparatuses 710 and/or 720 may also include or be coupled to one or more antennas 715 and 725 for receiving a downlink signal and for transmitting via an uplink from apparatus 710 and apparatus 720, respectively. Apparatuses 710 and/or 720 may further include transceivers 716 and 726, respectively, configured to transmit and receive information. The transceiver 716 and 726 may also include a radio interface that may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, or the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters or the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, or the like, to process symbols, such as OFDMA symbols, carried by a downlink or an uplink.
[0083] For instance, transceivers 716 and 726 may be respectively configured to modulate information on to a carrier waveform for transmission, and demodulate received information for further processing by other elements of apparatuses 710 and/or 720. In other example embodiments, transceivers 716 and 726 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatuses 710 and/or 720 may include an input and/or output device (I/O device). In certain example embodiments, apparatuses 710 and/or 720 may further include a user interface, such as a graphical user interface or touchscreen.
[0084] In certain example embodiments, memory 714 and memory 724 store software modules that provide functionality when executed by processors 712 and 722, respectively. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 710 and/or 720. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 710 and/or 720. The components of apparatuses 710 and/or 720 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatus 710 may optionally be configured to communicate with apparatus 720 via a wireless or wired communications link 730 according to any radio access technology, such as NR.
[0085] According to certain example embodiments, processors 712 and 722, and memory 714 and 724 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 716 and 726 may be included in or may form a part of transceiving circuitry.
[0086] In some exemplary embodiments, an apparatus (e.g., apparatus 710 and/or apparatus 720) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and/or computer program code for causing the performance of the operations.
[0087] Certain exemplary embodiments may be directed to an apparatus that includes means for determining that the apparatus may be scheduled with a single codeword or transport block for a shared data channel, and means for generating a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may also include means for providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
[0088] Some exemplary embodiments may be directed to another apparatus that includes means for decoding a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission. The shared data channel reception or transmission may be based on codeblock group transmission information. The apparatus may also include means for determining, based on the scheduling information, that the apparatus may be scheduled with a single codeword or transport block on the shared data channel. The apparatus may also include means for determining, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission. The codeblock group transmission information may map to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
[0089] Various exemplary embodiments may be directed to a further apparatus that includes means for decoding a control channel scheduling the user equipment for a physical downlink shared data channel reception. The physical downlink shared data channel reception may be based on codeblock group transmission information. The apparatus may also include means for determining that the apparatus may be scheduled with a single codeword or transport block for the physical downlink shared data channel reception, and means for generating a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of subgroups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation. The apparatus may further include means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity. [0090] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (for example, analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software, including digital signal processors, that work together to cause an apparatus (for example, apparatus 710 and/or 720) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor or multiple processors, or portion of a hardware circuit or processor, and the accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
[0091] A computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments. The one or more computerexecutable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.
[0092] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non- transitory medium.
[0093] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (for example, apparatuses 710 and/or 720), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.
[0094] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.
[0095] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. Further, the terms “cell”, “node”, “gNB”, or other similar language throughout this specification may be used interchangeably.
[0096] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.
[0097] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and/or fourth generation (4G) technology.
[0098] Partial Glossary:
[0099] 3GPP 3rd Generation Partnership Project
[0100] 5G 5 th Generation
[0101] ACK Acknowledgement
[0102] AL Aggregation Level
[0103] BW Bandwidth
[0104] BWP Bandwidth Part
[0105] CB CodeBlock
[0106] CBG CodeBlock Group
[0107] CBGTI CBG Transmission Information
[0108] CW Codeword
[0109] DCI Downlink Control Information [0110] DL Downlink
[0111] EMBB Enhanced Mobile Broadband
[0112] gNB 5G or Next Generation NodeB
[0113] HARQ Hybrid Automatic Repeat Request
[0114] LTE Long Term Evolution
[0115] MAC Medium Access Control
[0116] NACK N on- acknowledgement
[0117] NR New Radio
[0118] PDCCH Physical Downlink Control Channel
[0119] PDSCH Physical Downlink Shared Channel
[0120] PRB Physical Recourse Block
[0121] PSS Primary Synchronization Signal
[0122] PUCCH Physical Uplink Control Channel
[0123] PUSCH Physical Uplink Shared Channel
[0124] RAN Radio Access Network
[0125] RF Radio Frequency
[0126] RRC Radio Resource Control
[0127] SCS Subcarrier Spacing
[0128] TB Transport Block
[0129] TBS Transport Block Size
[0130] TCI Transmission Configuration Indicator
[0131] UE User Equipment
[0132] UL Uplink
[0133] URLLC Ultra Reliable Low Latency Communication

Claims

WE CLAIM:
1. A method, comprising: determining, by a user equipment, that the user equipment is scheduled with a single codeword or transport block for a shared data channel; generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
2. The method according to claim 1, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
3. The method according to claim 1, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
4. The method according to any one of claims 1-3, wherein the feedback is provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
5. The method according to any one of claims 1-4, wherein the single codeword or transport block on the shared data channel is either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel; or based on a semi-persistent shared data channel transmission; or based on a configured-grant shared data channel transmission.
6. The method according to any one of the claims 1-5, wherein the hybrid automatic repeat request acknowledgement feedback operation is activated by higher layer signalling.
7. The method according to claim 6, wherein the higher layer signalling is a radio resource control message.
8. A method, comprising: decoding, by a user equipment, a control channel scheduling the user equipment for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information; determining, by the user equipment, based on the scheduling information, that the user equipment is scheduled with a single codeword or transport block on the shared data channel; and determining, by the user equipment, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
9. The method according to claim 8, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
10. The method according to claim 8, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
11. The method according to any one of claims 8-10, wherein the scheduling information is provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block.
12. The method according to any one of claims 8-11, wherein the single codeword or transport block on the shared data channel is scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel.
13. The method according to any one of the claims 8-12, wherein the shared data channel operation is activated by higher layer signalling.
14. The method according to claim 13, wherein the higher layer signalling is a radio resource control message.
15. A method, comprising: decoding, by a user equipment, a control channel scheduling the user equipment for a physical downlink shared data channel reception, wherein the physical downlink shared data channel reception is based on codeblock group transmission information; determining, by the user equipment, that the user equipment is scheduled with a single codeword or transport block for the physical downlink shared data channel reception; generating, by the user equipment, a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of subgroups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and providing, by the user equipment to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
16. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel; generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
17. The apparatus according to claim 16, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
18. The apparatus according to claim 16, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
19. The apparatus according to any one of claims 16-18, wherein the feedback is provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
20. The apparatus according to any one of claims 16-19, wherein the single codeword or transport block on the shared data channel is either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel; or based on a semi-persistent shared data channel transmission; or based on a configured-grant shared data channel transmission.
21. The apparatus according to any one of the claims 16-20, wherein the hybrid automatic repeat request acknowledgement feedback operation is activated by higher layer signalling.
22. The apparatus according to claim 21 , wherein the higher layer signalling is a radio resource control message.
23. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information; determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel; and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
24. The apparatus according to claim 23, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
25. The apparatus according to claim 23, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
26. The apparatus according to any one of claims 23-25, wherein the scheduling information is provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block.
27. The apparatus according to any one of claims 23-26, wherein the single codeword or transport block on the shared data channel is scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel.
28. The apparatus according to any one of the claims 23-27, wherein the shared data channel operation is activated by higher layer signalling.
29. The apparatus according to claim 28, wherein the higher layer signalling is a radio resource control message.
30. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: decode a control channel scheduling the apparatus for a physical downlink shared data channel reception, wherein the physical downlink shared data channel reception is based on codeblock group transmission information; determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception; generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
31. An apparatus, comprising: means for determining that the apparatus is scheduled with a single codeword or transport block for a shared data channel; means for generating a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
32. The apparatus according to claim 31 , wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
33. The apparatus according to claim 31, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
34. The apparatus according to any one of claims 31-33, wherein the feedback is provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
35. The apparatus according to any one of claims 31-34, wherein the single codeword or transport block on the shared data channel is either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel; or based on a semi-persistent shared data channel transmission; or based on a configured-grant shared data channel transmission.
36. The apparatus according to any one of the claims 31-35, wherein the hybrid automatic repeat request acknowledgement feedback operation is activated by higher layer signalling.
37. The apparatus according to claim 36, wherein the higher layer signalling is a radio resource control message.
38. An apparatus, comprising: means for decoding a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information; means for determining based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel; and means for determining, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
39. The apparatus according to claim 38, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
40. The apparatus according to claim 38, wherein the plurality of subgroups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
41. The apparatus according to any one of claims 38-40, wherein the scheduling information is provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block.
42. The apparatus according to any one of claims 38-41, wherein the single codeword or transport block on the shared data channel is scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel.
43. The apparatus according to any one of the claims 38-42, wherein the shared data channel operation is activated by higher layer signalling.
44. The apparatus according to claim 43, wherein the higher layer signalling is a radio resource control message.
45. An apparatus, comprising: means for decoding a control channel scheduling the apparatus for a physical downlink shared data channel reception, wherein the physical downlink shared data channel reception is based on codeblock group transmission information; means for determining that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception; means for generating a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and means for providing, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
46. A non- transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus at least to: determine that the apparatus is scheduled with a single codeword or transport block for a shared data channel; generate a hybrid automatic repeat request acknowledgement feedback for the shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
47. The non- transitory computer readable medium according to claim 46, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
48. The non- transitory computer readable medium according to claim 46, wherein the plurality of sub-groups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
49. The non- transitory computer readable medium according to any one of claims 46-48, wherein the feedback is provided for the plurality of sub-groups using all feedback bits for the single scheduled codeword or transport block.
50. The non-transitory computer readable medium according to any one of claims 46-49, wherein the single codeword or transport block on the shared data channel is either: scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel; or based on a semi-persistent shared data channel transmission; or based on a configured-grant shared data channel transmission.
51. The non-transitory computer readable medium according to any one of the claims 46-50, wherein the hybrid automatic repeat request acknowledgement feedback operation is activated by higher layer signalling.
52. The non-transitory computer readable medium according to claim 51 , wherein the higher layer signalling is a radio resource control message.
53. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus at least to: decode a control channel scheduling the apparatus for a shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on codeblock group transmission information; determine based on the scheduling information, that the apparatus is scheduled with a single codeword or transport block on the shared data channel; and determine, based on a field entry of the decoded codeblock group transmission information included in downlink control information, scheduled codeblocks for shared data channel reception or transmission, wherein the codeblock group transmission information maps to each of a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation.
54. The non- transitory computer readable medium according to claim 53, wherein each of the plurality of codeblock groups is split by the maximum number of codewords to form the plurality of sub-groups.
55. The non-transitory computer readable medium according to claim 53, wherein the plurality of sub-groups are formed based on a mapping procedure using the number of the plurality of codeblock groups multiplied by the maximum number of codewords.
56. The non-transitory computer readable medium according to any one of claims 53-55, wherein the scheduling information is provided for the plurality of sub-groups using all bits of the codeblock group transmission information for the single scheduled codeword or transport block.
57. The non-transitory computer readable medium according to any one of claims 53-56, wherein the single codeword or transport block on the shared data channel is scheduled by a downlink control information on a downlink control channel, wherein the downlink control information format is configured to schedule at least one codeword or transport block for the shared data channel.
58. The non-transitory computer readable medium according to any one of the claims 53-57, wherein the shared data channel operation is activated by higher layer signalling.
59. The non-transitory computer readable medium according to claim 58, wherein the higher layer signalling is a radio resource control message.
60. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus at least to: decode a control channel scheduling the apparatus for a physical downlink shared data channel reception, wherein the physical downlink shared data channel reception is based on codeblock group transmission information; determine that the apparatus is scheduled with a single codeword or transport block for the physical downlink shared data channel reception; generate a hybrid automatic repeat request acknowledgement feedback for a physical downlink shared data channel based on assigning a plurality of codeblocks to a plurality of sub-groups of a plurality of codeblock groups based on a maximum number of codewords available for shared data channel operation; and provide, to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.
61. A computer program comprising instructions stored thereon for performing at least the method of claim 1.
62. A computer program comprising instructions stored thereon for performing at least the method of claim 8.
63. A computer program comprising instructions stored thereon for performing at least the method of claim 15.
64. An apparatus comprising one or more circuitry configured to perform the method of claim 1.
65. An apparatus comprising one or more circuitry configured to perform the method of claim 8.
66. An apparatus comprising one or more circuitry configured to perform the method of claim 15.
PCT/US2023/018833 2023-04-17 2023-04-17 Sub-codeblock group based operation for single codeword scheduling WO2024220068A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2023/018833 WO2024220068A1 (en) 2023-04-17 2023-04-17 Sub-codeblock group based operation for single codeword scheduling

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2023/018833 WO2024220068A1 (en) 2023-04-17 2023-04-17 Sub-codeblock group based operation for single codeword scheduling

Publications (1)

Publication Number Publication Date
WO2024220068A1 true WO2024220068A1 (en) 2024-10-24

Family

ID=86329942

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/018833 WO2024220068A1 (en) 2023-04-17 2023-04-17 Sub-codeblock group based operation for single codeword scheduling

Country Status (1)

Country Link
WO (1) WO2024220068A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022151139A1 (en) * 2021-01-14 2022-07-21 Lenovo (Beijing) Limited Downlink control information feedback

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022151139A1 (en) * 2021-01-14 2022-07-21 Lenovo (Beijing) Limited Downlink control information feedback

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "CBG-Based DL/UL Retransmissions", vol. RAN WG1, no. Prague, CZ; 20171009 - 20171013, 8 October 2017 (2017-10-08), XP051340849, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN1/Docs/> [retrieved on 20171008] *
SAMSUNG: "Corrections on CBG-Based UL/DL Retransmissions", vol. RAN WG1, no. Vancouver, Canada; 20170122 - 20170126, 12 January 2018 (2018-01-12), XP051384338, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5FAH/NR%5FAH%5F1801/Docs/> [retrieved on 20180112] *
VIVO: "Remaining issues on CBG-based (re)transmission", vol. RAN WG1, no. Reno, USA; 20171127 - 20171201, 18 November 2017 (2017-11-18), XP051369538, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F91/Docs/> [retrieved on 20171118] *

Similar Documents

Publication Publication Date Title
AU2021212111B2 (en) Uplink transmission method and corresponding equipment
CN111727649B (en) Method and apparatus for communication of data and control information in a wireless communication system
EP3375125B1 (en) Systems and methods for uplink control information reporting with license-assisted access (laa) uplink transmissions
CN108293253B (en) Information bit encapsulation
US9853779B2 (en) Systems and methods for carrier aggregation
RU2543490C2 (en) Transmission of feedback information for data transmission on multiple carriers
US9749094B2 (en) Devices for sending and receiving feedback information
US12088531B2 (en) Method and device for determining uplink data and control signal transmission timing in wireless communication system
US10681682B2 (en) Uplink control information transmission method and apparatus
CN106559878B (en) Uplink control information UCI sending and acquiring method and device
CN111937316A (en) Codebook determination for HARQ-ACK multiplexing with fallback Downlink Control Information (DCI) and Code Block Group (CBG) configuration
US20150043394A1 (en) Downlink control signalling transmission method and device
US9819451B2 (en) Method and apparatus for determining resource index information
US20200092047A1 (en) Method and apparatus for data transmission in wireless cellular communication system
US11375478B2 (en) Resource signaling for PUCCH
JP2020523841A (en) Feedback information transmission/reception method, apparatus and communication system
US20230028762A1 (en) Method and device for repeatedly transmitting uplink control channel in wireless cellular communication system
WO2018233705A1 (en) Data transmission method, data transmission feedback method, and related device
US20140198730A1 (en) Devices for sending and receiving feedback information
US11463222B2 (en) Method and device for transmitting or receiving uplink control channel in wireless communication system
US20230319843A1 (en) Method and apparatus for harq-ack codebook determination for multi-carrier scheduling
EP4268398A1 (en) Enhanced sidelink hybrid automatic repeat request with integrated user equipment-to-user equipment relay
US10524248B2 (en) Method and apparatus for detecting downlink control signal in wireless communication system
EP4131820A1 (en) Harq-ack bundling for type 1 codebook with multi-slot scheduling
WO2024220068A1 (en) Sub-codeblock group based operation for single codeword scheduling