Sub-code block group based operations for single codeword scheduling

Abstract

Sub-code block group based operations for single codeword scheduling are provided. A method for sub-code block group-based operation scheduled for a single codeword 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 allocating the plurality of code blocks to a plurality of subgroups of the plurality of code block groups according to a maximum number of codewords available for the shared data channel operation. The method may also include providing, by the user equipment, a hybrid automatic repeat request acknowledgement to the network entity, the hybrid automatic repeat request acknowledgement indicating feedback to the network entity.

Description

TECHNICAL FIELD

[0001] Some example embodiments can generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or Fifth Generation (5G) New Radio (NR) access technologies, or beyond 5G technologies, or other communications systems. For example, certain example embodiments can relate to sub-code block group based operations for single codeword scheduling. BACKGROUND

[0002] Examples of mobile or wireless telecommunication systems can include the Universal Mobile Telecommunication System (UMTS), the Land Mobile Radio (LMR) communications system, Terrestrial Trunked Radio (TETRA), the Global System for Mobile Communications (GSM), the General Packet Radio Service (GPRS), the Enhanced Data Rates for Global Evolution (EDGE), the Wideband Code Division Multiple Access (WCDMA), the Long Term Evolution (LTE) system, the LTE-Advanced (LTE-A) system, the MulteFire, the LTE-A Pro, and / or the Fifth Generation (5G) system or the New Radio Access Technology (NR). The Fifth Generation (5G) wireless systems refer to the next generation (NG) of radio systems and network architecture. The 5G network technologies are mostly based on the New Radio (NR) technology but 5G (or NG) networks can also be implemented on top of the E-UTRA radio. It is estimated that NR can provide bitrates of approximately 10-20 Gbit / s or higher, and can support services and devices with different requirements for data rate, latency, and reliability. The NR can be implemented in frequency regions below 1 GHz, approximately 1 GHz to 6 GHz, above 6 GHz up to 60 GHz, and beyond 60 GHz. The former frequency regions can be referred to as Sub-6 GHz, Mid-band, and High-band, respectively. The 5G network can also be multiplexed with the Long Term Evolution (LTE) network. SUMMARY

[0003] Various example embodiments can provide 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; and generating, by the user equipment, hybrid automatic repeat request acknowledgement feedback for the shared data channel based on allocating a plurality of code blocks to a plurality of sub-groups of a plurality of code block groups according to a maximum number of codewords available for shared data channel operation. The method can further comprise providing, by the user equipment, a hybrid automatic repeat request acknowledgement to a network entity, the hybrid automatic repeat request acknowledgement indicating the feedback to the network entity.

[0004] Some example embodiments can provide a method comprising decoding, by a user device, a control channel scheduling the user device for shared data channel reception or shared data channel transmission. The shared data channel reception or transmission can be based on code block group transmission information. The method can further comprise determining, by the user device, based on the scheduling information, that the user device is scheduled with a single codeword or transport block on the shared data channel; and determining, by the user device, based on a field entry of the decoded code block group transmission information included in the downlink control information, a scheduled code block for the shared data channel reception or transmission. The code block group transmission information can be mapped to each of a plurality of subgroups of a plurality of code block groups based on a maximum number of codewords available for shared data channel operation.

[0005] Certain example embodiments can provide a method comprising decoding, by a user device, a control channel scheduling the user device for physical downlink shared data channel reception. The physical downlink shared data channel reception can be based on code block group transmission information. The method can further comprise determining, by the user device, that the user device is scheduled with a single codeword or transport block for the physical downlink shared data channel reception; and generating, by the user device, hybrid automatic repeat request acknowledgement feedback for the physical downlink shared data channel based on allocating a plurality of code blocks to a plurality of subgroups of a plurality of code block groups according to a maximum number of codewords available for shared data channel operation. The method can further comprise providing, by the user device, a hybrid automatic repeat request acknowledgement to a network entity indicating feedback to the network entity.

[0006] Various example embodiments can provide an apparatus comprising at least one processor and at least one memory storing instructions. The instructions, when executed by the at least one processor, can 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 hybrid automatic repeat request acknowledgement feedback for the shared data channel based on allocating a plurality of code blocks to a plurality of subgroups of a plurality of code block groups according to a maximum number of codewords available for shared data channel operation. The apparatus can also be caused to provide a hybrid automatic repeat request acknowledgement to a network entity indicating feedback to the network entity.

[0007] Some exemplary embodiments may provide an apparatus including: at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions may cause the apparatus to decode a control channel of a scheduling apparatus, at least for shared data channel reception or shared data channel transmission. Shared data channel reception or transmission may be based on block group transmission information. The apparatus may also determine, based on scheduling information, whether it is scheduled to utilize a single codeword or transport block on the shared data channel, and based on field entries of the decoded block group transmission information included in downlink control information, whether the scheduled block is for shared data channel reception or transmission. The block group transmission information may be mapped to each of multiple subgroups of multiple block groups based on a maximum number of codewords available for shared data channel operation.

[0008] Various exemplary embodiments may provide an apparatus comprising: at least one processor and at least one memory storing instructions. When executed by the at least one processor, the instructions may cause the apparatus to decode a control channel of a scheduling apparatus at least for physical downlink shared data channel reception. Physical downlink shared data channel reception may be based on code block group transmission information. The apparatus may also determine that it is scheduled using a single codeword or transport block for physical downlink shared data channel reception, and generate a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to a maximum number of codewords available for shared data channel operation. The apparatus may also provide a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0009] Some exemplary embodiments may provide an apparatus including: means for determining whether the apparatus is scheduled to utilize a single codeword or transport block for a shared data channel; and means for generating a hybrid automatic repeat request acknowledgment feedback for the shared data channel by allocating multiple code blocks to multiple subgroups of multiple code block groups based on a maximum number of codewords available for operation of the shared data channel. The apparatus may further include means for providing a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0010] Various exemplary embodiments may provide an apparatus including: components for decoding a control channel of a scheduling means for shared data channel reception or shared data channel transmission. Shared data channel reception or transmission may be based on code block group transmission information. The apparatus may further include: components for determining, based on scheduling information, whether the means is scheduled to utilize a single codeword or transport block on the shared data channel; and components for determining, based on field entries of decoded code block group transmission information included in downlink control information, the scheduled code blocks for shared data channel reception or transmission. The code block group transmission information may be mapped to each of multiple subgroups of multiple code block groups based on a maximum number of codewords available for shared data channel operation.

[0011] Certain exemplary embodiments may provide an apparatus including components for decoding a control channel of a scheduling apparatus for reception of a physical downlink shared data channel. The physical downlink shared data channel reception may be based on block group transmission information. The apparatus may further include: components for determining whether the apparatus is scheduled using a single codeword or transport block for reception of the physical downlink shared data channel; and components for generating a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel based on allocating multiple code blocks to multiple subgroups of multiple block groups according to a maximum number of codewords available for shared data channel operation. The apparatus may further include components for providing a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0012] Various exemplary embodiments may provide a non-transitory computer-readable medium including program instructions that, when executed by a means, cause the means to at least: determine that the means is scheduled to utilize a single codeword or transport block for a shared data channel; and generate a hybrid automatic repeat request acknowledgment feedback for a shared data channel based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to a maximum number of codewords available for operation on the shared data channel. The means may also be caused to provide a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0013] Some exemplary embodiments may provide a non-transitory computer-readable medium including program instructions that, when executed by a device, cause the device to decode a control channel of a scheduling device, at least for shared data channel reception or shared data channel transmission. Shared data channel reception or transmission may be based on block group transmission information. The device may also determine, based on scheduling information, whether it is scheduled to utilize a single codeword or transport block on the shared data channel, and determine the scheduled code blocks for shared data channel reception or transmission based on field entries of the decoded block group transmission information included in downlink control information. The block group transmission information may be mapped to each of multiple subgroups of multiple block 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 a device, cause the device to decode a control channel of a scheduling device, at least for physical downlink shared data channel reception. Physical downlink shared data channel reception may be based on code block group transmission information. The device may also determine that it is scheduled using a single codeword or transport block for physical downlink shared data channel reception, and generate a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel by allocating multiple code blocks to multiple subgroups within multiple code block groups based on a maximum number of codewords available for shared data channel operation. The device may also provide a hybrid automatic repeat request acknowledgment to a network entity, indicating 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 circuits, configured to perform one or more of the methods described herein. Attached Figure Description

[0016] To correctly understand the exemplary embodiments, reference should be made to the accompanying drawings, as follows: Figure 1 Examples of diagrams illustrating the transmission of code block groups of information according to various exemplary embodiments are shown; Figure 2 Examples of graphs implementing feedback according to various exemplary embodiments are shown; Figure 3 A diagram illustrating configurations according to various exemplary embodiments is shown; Figure 4 An example of a flowchart illustrating a method according to certain exemplary embodiments is shown; Figure 5An example flowchart of another method according to certain exemplary embodiments is shown; Figure 6 An example of a flowchart illustrating another method according to certain exemplary embodiments is shown; and Figure 7 A set of apparatuses according to various exemplary embodiments is shown. Detailed Implementation

[0017] It will be readily understood that, as generally described and illustrated in the accompanying drawings, components of certain example embodiments may be arranged and designed in a 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 operation based on sub-block groups of single codeword scheduling. Although the devices discussed below and illustrated in the drawings relate to 5G or next-generation Node B (gNB) devices and user equipment (UEs), this disclosure is not limited to gNBs and UEs only. For example, the following description can also be applied to any type of network access node or entity, as well as UEs or mobile devices.

[0018] Additionally, if desired, the different functions or processes discussed herein may be executed in different orders and / or simultaneously with each other. Furthermore, if desired, one or more of the described functions or processes may be optional or may be combined. Therefore, the following description should be considered as an illustration of the principles and teachings of certain exemplary embodiments, and not as a limitation thereof.

[0019] In 5G / NR technology, hybrid Automatic Repeat Request (HARQ) acknowledgment (ACK) feedback based on code block groups (CBGs) for the Physical Downlink Shared Channel (PDSCH) and scheduling of the Physical Uplink Shared Channel (PUSCH) and / or PDSCH based on CBGs allow for finer-grained HARQ feedback for PDSCH and finer-grained retransmission granularity for both PDSCH and PUSCH. In transport block (TB) based HARQ, each TB can be provided with a single HARQ-ACK bit. When a code block (CB) in a TB is erroneous (e.g., a CB is incorrectly decoded), the entire TB, which can consist of a large number of CBs, can be indicated as erroneous, regardless of how many CBs in the TB are correctly decoded.

[0020] In a data block (TB) containing one or more faulty CBs and one or more correctly decoded CBs, CBG-based HARQ can avoid unnecessary retransmission of all correctly decoded CBs. To avoid unnecessary retransmission of correctly decoded CBs, each CB can have its own HARQ-ACK bit, and in retransmissions, each CB can be individually indicated as present or absent, and CBs omitted from retransmissions can be due to CBs having been correctly delivered / decoded after previous transmission attempts. The potential drawback of individually evaluating the HARQ-ACK bit of each CB can be high overhead or processing burden due to the potentially large number of CBs in the TB. To help address this drawback, in some cases, the concept of grouping CBs into CBGs is employed.

[0021] During CBG-based transmission, a single TB and / or codeword (CW) CB can be grouped into multiple CBGs of substantially similar or equal size. The maximum number N of CBGs for PDSCH and / or PUSCH can be determined by the Radio Resource Control (RRC) message using a parameter with possible values ​​of {2, 4, 6, 8}. maxCodeBlockGroupsPerTransportBlock To configure. The number C of CBs can be assigned to up to N CBG groups. The UE is configured to receive signals via PDSCH. codeBlockGroupTransmission When using higher-layer parameters to receive CBG-based transmissions, the UE can determine the number M of CBGs received for TB. N can be defined as being derived from the PDSCH. maxCodeBlockGroups PerTransportBlock The maximum number of CBGs per TB is configured, and C can be the number of CBs in the TB. CBGs can be defined using... , ,and The pseudocode is used to define it. Applying the pseudocode, the CB assigned to CBG can be determined in the following way: if... Then CBG m( ) can be obtained by having an index as The code block is formed. CBG m ( ) can be obtained by having an index as The code blocks are formed.

[0022] In the CBG-based HARQ-ACK feedback indication for PDSCH, HARQ-ACK bits for each individual CBG can be fed back for the entire TB. By being able to determine the correct reception of a portion of the entire TB, it is possible to allow DL data scheduling to retransmit portions of the entire TB instead of the complete TB, which is referred to here as "CBG-based scheduling" for PDSCH.

[0023] For CBG-based PDSCH and / or PUSCH scheduling, the CBG of a TB to be transmitted or retransmitted can be indicated in the scheduling downlink control information (DCI) for PDSCH and / or PUSCH. For NR DCI format 0_1 ​​(scheduling PUSCH) and DCI format 1_1 (scheduling PDSCH), a separate field for the CBG Transport Indication (CBGTI) can be included to indicate one or more CBGs that may be part of a scheduled PUSCH / PDSCH transmission. The CBGTI field can include one bit for each CBG to allow for the presence of an indication for each CBG in the scheduled PDSCH / PUSCH. For the initial transmission, all CBGs can be scheduled. For example, a complete TB can be scheduled for the first transmission. The CBGTI field can be applied equally to PUSCH and / or PDSCH transmissions.

[0024] There may be some inefficiencies in CBG-based HARQ and scheduling operations, such as when there are multiple (e.g., 2) transport blocks and / or codeword operations for the PDSCH operation, which can be configured with... maxNrofCodeWordsSchedudByDCI For example, when a single TB is scheduled, half of the CBG-based HARQ-ACK bits and half of the CBGTI bits may not be used. For HARQ-ACK feedback operations, only a total of 2 bits can be used. The first number M of the CBG's HARQ-ACK bits of N. In the example for a type 1 HARQ-ACK codebook, when the UE receives a PDSCH release or Transmission Configuration Indicator (TCI) state update with a PDSCH of one TB or a semi-persistent scheduling (SPS), the parameter maxNrofCodeWordsScheduedByDCI It can indicate reception of up to two TBs. HARQ-ACK information can be associated with the first TB, and if no parameters are provided... harq-ACKSpatialBundlingPUCCH Then the UE can generate a negative acknowledgment (NACK) for the second (non-existent) TB. When the parameter harq-ACK-SpatialBundlingPUCCH is provided, the UE can also generate HARQ-ACK information with an ACK value for the second (non-existent) TB. In both cases, the transmitter knows that the second TB does not exist and can ignore the bits associated with the second TB in the HARQ-ACK codebook.

[0025] In the example for a Type 2 HARQ-ACK codebook, the PDCCH monitoring timing can be provided with a DCI format that schedules PDSCH reception or with associated HARQ-ACK information without scheduling PDSCH reception. During the active DL bandwidth portion (BWP) of the serving cell, the UE can receive a PDSCH with one transport block, or detect a DCI format with associated HARQ-ACK information without scheduling PDSCH reception. Parameters can be set. maxNrofCodeWordsScheduedByDCI The value is set to 2, and the HARQ-ACK information can be associated with the first transport block. Thus, in the parameter... harq-ACKSpatialBundlingPUCCH If not provided, the UE can generate a NACK for the second transport block, and in the parameters harq-ACKSpatialBundlingPUCCH When provided, the UE can generate HARQ-ACK information with an ACK value for the second transport block.

[0026] CBGTI information can be used in DCI format 1_1 for scheduling CBG-based PDSCH. The UE can be configured to receive higher-layer parameters for PDSCH. codeBlockGroupTransmission To receive CBG-based transmissions. In this case, the CBGTI field of DCI format 1_1 can have a length bits, of which It can be defined as a high-level parameter maxNrofCodeWordsSchedudByDCI The value of . When the MSB is mapped to CBG#0, the CBGTI field bits can be mapped such that the first group of N bits starts from the most significant bit corresponding to the first TB, and the second group of N bits can correspond to the second TB when scheduled. When the MSB is mapped to CBG#0, the first M bits of each group of N bits in the CBGTI field can have an ordered one-to-one mapping to the M CBGs of the TB.

[0027] For those that can be scheduled by DCI, New Data Indicator "The field indicates the initial transmission of the TB, and the UE can assume that all CBGs of the TB are present. This can also be addressed by scheduling the DCI." New Data IndicatorRegarding the retransmission of a TB indicated by the field, the UE may assume that the CBGTI field of the scheduling DCI can indicate which CBGs of the TB are present in the transmission. A bit value of "0" in the CBGTI field can indicate that the corresponding CBG is not transmitted, and "1" indicates that the corresponding CBG is transmitted. Furthermore, the UE may assume that when the "CBG Clear Information" (CBGFI) field of the scheduling DCI is present, a CBGFI set to "0" can indicate that an earlier received instance of the same CBG being transmitted may be corrupted, and a CBGFI set to "1" can indicate that the CBG being retransmitted can be combined with an earlier received instance of the same CBG. The UE may also assume that the CBG contains the same CBs as in the initial transmission of the TB during the retransmission.

[0028] In parameters maxNrofCodeWordsSchedudByDCI When set to 2, if only one TB is transmitted, half of the CBGTI bits in the DCI may be wasted. (This is related to higher-level parameters for PDSCH.) codeBlockGroupTransmission When not configured, the CBGTI field can be set to a size of 0 bits; otherwise, it is based on the higher-level parameters for PDSCH. maxC odeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI The CBGTI field size can be set to 2, 4, 6, or 8 bits.

[0029] As an example, the UE can be configured for dual-codeword or 2 TB operation ( maxNrofCodeWordsScheduldByDCI Set to 2), and configured with 4 CBGs ( maxCodeBlockGroups PerTransportBlock Set to "n4"). The UE can be configured for single TB scheduling with a TB size of 22 CBs. The 22 CBs of the scheduled transmission can be allocated 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. 8 bits of CBGTI information (N N_TB = 4 (2=8) can provide scheduling information for the scheduled TB, where the CBGTI bit associated with the second unscheduled TB is given the value "0". For example, the CBGTI can be as follows: {CBG#0 TB1, CBG#1 TB1, CBG#2 TB1, CBG#3 TB1, 0,0,0,0}. In the received HARQ-ACK feedback with a total of 8 HARQ-ACK bits for the PDSCH used for scheduling, the first 4 bits can have useful HARQ-ACK information for the first scheduled TB, and the second 4th bit of the HARQ-ACK information may not be due to association with the second unscheduled TB (which can be set to NACK or 0). For example, the HARQ-ACK feedback information can be as follows: {HARQ-ACKCBG#0 TB1, HARQ-ACK CBG#1 TB1, HARQ-ACK CBG#2 TB1, HARQ-ACK CBG#3 TB1, 'NACK', 'NACK', 'NACK', 'NACK'}.

[0030] Various exemplary embodiments can provide advantages to help address the aforementioned drawbacks. For example, some exemplary embodiments can provide one or more procedures to optimize CBG-based scheduling operations, where two transport blocks may be able to be scheduled for the UE, but only a single transport block has been scheduled. Various exemplary embodiments can advantageously provide HARQ-ACK feedback and / or doubling of scheduling granularity without any additional UL or DL ​​control signaling overhead.

[0031] Some exemplary embodiments may provide one or more processes for the case where a single TB is scheduled, and the feedback granularity may be doubled to 2. maxCodeBlockGroupPerTransportBlock This allows the use of all available CBGTI / HARQ-ACK feedback bits for a single scheduled transport block. This eliminates the need to set the CBGTI bit to 0 and the HARQ-ACK feedback bit to NACK for a second unscheduled transport block.

[0032] Examples of various exemplary embodiments may include 4 CBGs per TB, where double codewords or 2 transport block operations are used for a single transport block scheduling and a transport block size of 22 CBs. The 22 CBs of the scheduled transport can be allocated 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.

[0033] Figure 1 An example diagram illustrating a CBGTI implementation for this example according to various exemplary embodiments is shown. CBGTI can be 8-bit information. Figure 1In the diagram, conventional behavior can be shown in the upper row including "0" for the second non-scheduled TB, and the lower row of the diagram can show that each CBG in the CBG can be divided into two sub-CBGs with approximately twice the granularity. Each CBG#X can be divided into two sub-CBGs (CGB#XA and CGB#XB) of approximately equal size. Size association can be used by making the size of CBG#XA >= the size of CBG#XB. Exemplary embodiments are not limited to... Figure 1 This example. By dividing each original CBG into maxNrofCodeWordsSchedudByDCI Sub-CBGs, any maximum number of codewords and / or transport blocks can be used. Alternatively, double the number of CBGs for a single TB / CW schedule can be assumed, such as, for example, assumption 2. N CBG or maxNrofCodeWordsSchedudByDCI maxCodeBlockGroups PerTransportBlock One CBG. In this alternative, a CB for a single CW transmission can be paired with a set of other CBs in a sub-CBG of the same CBG that are not included in a dual (or multi) CW transmission, which can limit the use of retransmission operations for mixed single or dual CW operations.

[0034] Figure 2 Examples of diagrams illustrating HARQ feedback implementations according to various exemplary embodiments are shown. Figure 2 An example of 8-bit HARQ-ACK information is shown, where the upper line illustrates a conventional implementation including "NACK" (i.e., "0" for the last 4 bits of the second unscheduled PDSCH transport block) for comparison with the lower line, which illustrates HARQ feedback according to one or more processes under various exemplary embodiments. In these exemplary embodiments, all 8 bits of HARQ-ACK feedback information can be used for a single-scheduled PDSCH transport block with approximately twice the granularity and half the CBG size. This is achieved by applying the CBG-associated pseudocode within the CBG to create... maxNrofCodeWordsScheduedByDCI Sub-CBGs A / B can be divided into CBGs that are identical to CBGTI (e.g., CBG#XA and CBG#XB). Pseudocode can be defined as follows: , ,and Applying pseudocode, the CB assigned to CBG can be determined by the following: if Then CBG m( ) can be indexed The code block is formed. CBG m ( ) can be indexed The code block is formed. Alternatively, assume 2. N CBG ormaxNrofCodeWordsSchedudByDCI maxCodeBlockGroupsPerTransportBlock Each CBG (Contains a CB group), and the associations between CBGs can be reused.

[0035] Certain exemplary embodiments may provide HARQ-ACK feedback. When the UE is configured for multi-CW PDSCH reception on a serving cell (such as a base station, gNB, etc.), the UE may provide HARQ-ACK feedback information. maxNrofCodeWordsScheduedByDCI It has a maximum of L CWs, and when using maxCodeBlockGroupsPer TransportBlock The UE can utilize multi-codeword PDSCH reception for scheduling, and conventional procedures / behaviors can be applied, where N HARQ-ACK bits can be provided to N CBGs for each transport block. Various exemplary embodiments can provide that the UE can utilize a single codeword and / or transport block for scheduling, and can provide up to N HARQ-ACK bits for a single scheduled CW and / or TB by using all HARQ bits for a single transport block and / or CW. HARQ-ACK feedback granularity of L sub-CBGs.

[0036] As an exemplary implementation, a sub-CBG can be defined by dividing each CBG of a multi-codeword PDSCH operation into L sub-CBGs. The CB-to-CBG mapping process can be applied to assign the CBs of a CBG to the L sub-CBGs. As another example, this can be achieved by using N... Instead of N (CBG), L (sub-CBG) is used to apply the CB-to-CBG mapping process to create the sub-CBG.

[0037] A single codeword PDSCH can be scheduled by: (1) a DCI format that supports single codeword PDSCH scheduling, such as DCI format 1_0 or 1_2, or a DCI format that can schedule multiple codeword PDSCHs, such as DCI format 1_0 or 1_2; (2) and / or by a DCI format that supports or does not support CBG-based PDSCH scheduling, such as a DCI format that includes or does not include CBGTI information. Additionally or alternatively, a single codeword PDSCH can be scheduled by semi-persistent scheduling (SPS) permission.

[0038] Some exemplary embodiments may provide operations suitable for HARQ-ACK feedback reporting to receive initial PDSCH transmissions and receive PDSCH retransmissions. Although the above examples relate to CBG-based PDSCH HARQ-ACK feedback, the procedures are equally applicable to CBG-based PUSCH HARQ-ACK feedback operations.

[0039] Various exemplary embodiments can provide CBG-based scheduling. When using maxNrofCodeWordsScheduldByDCI When using, the UE can be configured for multi-CW PDSCH reception on a serving cell with a maximum of L codewords, and when using maxCodeBlockGroupsPerTransportBlock At this time, the UE can be configured for CBG-based HARQ-ACK feedback with N CBGs. When the UE can be scheduled using multi-codebook PDSCH reception, the CBGTI in the scheduling DCI can be applied, and conventional procedures / behaviors can be applied, where 1 bit of scheduling information is provided per CBG and per transport block. Some exemplary embodiments may provide that the UE can be scheduled using a single codeword and / or transport block. By using all CBGTI bits for a single transport block and / or CW, up to N The CBG-based PDSCH scheduling granularity of L sub-CBGs can be applied to the CW and / or TB of a single schedule.

[0040] As an example, a sub-CBG can be defined by dividing each CBG of a multi-codeword PDSCH operation into L sub-CBGs. A CB-to-CBG mapping process can be applied to assign the CBs of a CBG to L sub-CBGs. As another example, a sub-CBG can be defined by using N... Instead of N (CBG), L (sub-CBG) is used to apply the CB-to-CBG mapping process to create it.

[0041] According to various exemplary embodiments, a single CW PDSCH can be scheduled by a DCI format that only supports single codeword PDSCH scheduling of DCI format 1_0 or 1_2, or the DCI format can be able to schedule multiple CW PDSCHs with DCI format 1_0 or 1_2, provided that the single CW PDSCH contains CBG transmission indication information. One or more exemplary procedures described herein can be applied to the reception of PDSCHs during initial PDSCH transmissions and the reception of PDSCH retransmissions.

[0042] Figure 3 A diagram is shown illustrating that a CBGTI bit can correspond to a pair of CBGs when two TBs are scheduled and to a single CBG when one TB is scheduled. Figure 3 It can be Figure 1 and Figure 2 Another way to illustrate the example shown. In Figure 3 The same result can be achieved by bundling the CBG of a single TB PUSCH into a CBG pair for a dual TB PDSCH instead of splitting the CBG into sub-CBGs. This way, CBG generation remains unchanged, but when two TBs are scheduled, a CB-to-CB pair bundling for CBGTI / HARQ-ACK will be required.

[0043] In addition to HARQ-ACK, one or more procedures for downlink PDSCH described herein can be applied to uplink PUSCH transmissions. In the uplink, a network entity (such as a gNB) can determine during PUSCH decoding whether decoding success exists for each CB (and consecutively for each CBG), and can schedule PUSCH retransmissions to include only CBGs with erroneous CBs. Generating and sending HARQ-ACK feedback may not be necessary, as decoding the uplink TB and scheduling its retransmissions are performed within the network entity (e.g., the gNB). The procedures for CBG-based HARQ-ACK feedback for PDSCH described herein can be equally applied to CBG-based HARQ-ACK feedback for PUSCH, when supported.

[0044] Various exemplary embodiments may provide one or more procedures for HARQ-ACK feedback. The UE may be configured by network entities (such as base stations, gNBs, etc.) using higher-layer signaling (such as RRC) for multi-CW PDSCH scheduling and CBG-based operation over up to L CWs, where each transport block on the serving cell (or the serving cell's DL BWP) has up to N CBGs. The UE may be scheduled by the gNB for PDSCH reception on the serving cell using DCI format or based on semi-persistent scheduling, which may include reception of initial PDSCH transmissions or PDSCH retransmissions.

[0045] According to certain exemplary embodiments, one or more processes may further include the UE decoding the scheduled PDSCH. The UE may generate or prepare HARQ-ACK information for the PDSCH based on whether the UE is scheduled for single codeword or transport block or for multi-codeword PDSCH reception. When the UE is scheduled for multi-codeword PDSCH reception, one HARQ-ACK bit may be provided for each CBG and each transport block, such that N HARQ-ACK bits for N CBGs for each transport block can be provided for multi-CW PDSCH transmission. When the UE is scheduled for a single codeword or transport block, the UE may provide up to N HARQ-ACK bits for a single scheduled CW or TB by using all HARQ-ACK bits for a single transport block or CW. The HARQ-ACK feedback granularity is L sub-CBGs. For example, a sub-CBG can be defined by dividing each CBG of a multi-CW PDSCH operation into L sub-CBGs. A CB-to-CBG mapping process can be applied to assign the CBs of a CBG to L sub-CBGs. In another example, sub-CBGs can be defined by using N... Various exemplary embodiments of L (sub-CBG) instead of N (CBG) were created to apply the CB to CBG mapping process.

[0046] The UE can transmit N for the scheduled PDSCH on either PUCCH or PUSCH. L HARQ-ACK feedback bits are sent to the gNB as part of the HARQ-ACK codebook. N The L HARQ-ACK feedback bits can include, for example, type 1, type 2, and / or type 3 HARQ-ACK codebooks. The gNB can receive HARQ-ACK information for the scheduled PDSCH on the provided cell. For HARQ-ACK feedback of multi-CW PDSCH transmissions, for multi-codeword PDSCH transmissions, the HARQ-ACK information bits can be associated with one HARQ-ACK bit for each CBG and each transport block, such as N HARQ-ACK bits for N CBGs per transport block. For HARQ-ACK feedback of a single codeword and / or transport block PDSCH transmission on the serving cell, the HARQ-ACK information bits of the PDSCH can be interpreted using one HARQ-ACK bit for each sub-CBG of a single scheduled PDSCH codeword and / or transport block. Up to N CBGs can be implemented compared to a maximum CBG size of N CBGs. L smaller / higher-granularity sub-CBGs. Sub-CBG definitions can be defined by dividing each CBG of a multi-codeword PDSCH operation into L sub-CBGs (such as a CB-to-CBG mapping process to assign the CBs of a CBG to L sub-CBGs), or by using N... Instead of N (CBGs), L (sub-CBGs) are used to define the CB to CBG mapping process.

[0047] Various exemplary embodiments may provide one or more procedures for CBGTI transmissions. One or more procedures may specify that the UE can be configured by a network entity (such as a base station, gNB, etc.) using higher-layer signaling (e.g., RRC) for multi-CW PDSCH scheduling and CBG-based operation of up to L codewords, where each transport block on the serving cell (or the serving cell's DL BWP) has up to N CBGs. The UE can be scheduled for PDSCH reception on the serving cell by the gNB using the DCI format providing the CBGTI, which may include reception of initial PDSCH transmissions or PDSCH retransmissions.

[0048] The UE can decode the scheduled PDSCH based on scheduling assumptions provided by the CBGTI. An example of a scheduling assumption is that when the UE is scheduled to receive a multi-codeword PDSCH, for a multi-CW PDSCH transmission, one CBGTI bit can be provided for each CBG and each transport block, such as providing N CBGTI bits, where each CBG indicates "1" for every CBG sent in the N CBGs of each transport block and / or indicates "0" for every CBG not sent in the N CBGs of each transport block. Another example of a scheduling assumption is that when the UE is scheduled to receive a single CW and / or TB, the CBGTI field can provide up to N CBGTI bits for the single scheduled CW / TB by using all CBGTI bits for the single TB or CW. The PDSCH scheduling granularity is L sub-CBGs. As an exemplary implementation, a sub-CBG can be defined by dividing each CBG of a multi-codeword PDSCH operation into L sub-CBGs; a CB-to-CBG mapping process can be applied to assign CBs of a CBG to L sub-CBGs. As another exemplary implementation, a sub-CBG can be defined by using N... L (sub-CBG) is created instead of N (CBG) to apply the CB to CBG mapping process.

[0049] Various exemplary embodiments may provide one or more procedures for CBGTI transmissions. One or more procedures may specify that the UE can be configured by a network entity (such as a base station, gNB, etc.) using higher-layer signaling (e.g., RRC) for multi-CW PUSCH scheduling and CBG-based operation of up to L codewords, where each transport block on the serving cell (or the UL BWP of the serving cell) has up to N CBGs. The UE can be scheduled for PUSCH transmissions by the gNB using a DCI format that provides the CBGTI, which may include initial PUSCH transmissions or PUSCH retransmissions.

[0050] The UE can transmit scheduled PUSCHs based on scheduling assumptions provided by the CBGTI. An example of a scheduling assumption is that when the UE is scheduled to transmit a multi-codeword PUSCH, for a multi-CW PUSCH transmission, one CBGTI bit can be provided for each CBG and each transport block, such as providing N CBGTI bits, where each CBG sent for each of the N CBGs in each transport block indicates "1" and / or each CBG not sent for each of the N CBGs in each transport block indicates "0". Another example of a scheduling assumption is that when the UE is scheduled to transmit a single CW and / or TB, the CBGTI field can provide up to N CBGTI bits for the single scheduled CW / TB by using all CBGTI bits for the single TB or CW. The PUSCH scheduling granularity is L sub-CBGs. As an exemplary implementation, a sub-CBG can be defined by dividing each CBG of a multi-codeword PUSCH operation into L sub-CBGs; a CB-to-CBG mapping process can be applied to assign CBs of a CBG to L sub-CBGs. As another exemplary implementation, a sub-CBG can be defined by using N... L (sub-CBG) is created instead of N (CBG) to apply the CB to CBG mapping process.

[0051] Certain exemplary embodiments may provide one or more procedures for a combination of HARQ-ACK feedback and CBGTI transmission. One or more procedures may specify that the UE can be configured by a network entity (such as a base station, gNB, etc.) using higher-layer signaling (such as RRC) for multi-CW PDSCH scheduling and CBG-based operation over up to L CWs, where each transport block on the serving cell (or the serving cell's DL BWP) has up to N CBGs. The UE can be scheduled for PDSCH reception on the serving cell by the gNB using a DCI format that provides CBGTI, which may include reception of initial PDSCH transmissions or PDSCH retransmissions.

[0052] The UE can decode the scheduled PDSCH based on scheduling assumptions provided by the CBGTI. An example of a scheduling assumption is that when the UE is scheduled to receive a multi-codeword PDSCH, for a multi-CW PDSCH transmission, one CBGTI bit can be provided for each CBG and each transport block, such as providing N CBGTI bits, where each CBG indicates "1" for every CBG sent in the N CBGs of each transport block and / or indicates "0" for every CBG not sent in the N CBGs of each transport block. Another example of a scheduling assumption is that when the UE is scheduled to receive a single CW and / or TB, the CBGTI field can provide up to N CBGTI bits for the single scheduled CW / TB by using all CBGTI bits for the single TB or CW. PDSCH scheduling granularity of L sub-CBGs.

[0053] For example, a sub-CBG can be defined by dividing each CBG of a multi-CW PDSCH operation into L sub-CBGs. A CB-to-CBG mapping process can be applied to assign the CBs of a CBG to L sub-CBGs. In another example, a sub-CBG can be defined by using N... Various exemplary embodiments of L (sub-CBG) instead of N (CBG) were created to apply the CB to CBG mapping process.

[0054] The UE can transmit N for the scheduled PDSCH on either PUCCH or PUSCH. L HARQ-ACK feedback bits are sent to the gNB as part of the HARQ-ACK codebook. N The L HARQ-ACK feedback bits can include, for example, type 1, type 2, and / or type 3 HARQ-ACK codebooks. The gNB can receive HARQ-ACK information for the scheduled PDSCH on the provided cell. For HARQ-ACK feedback of multi-CW PDSCH transmissions, for multi-codeword PDSCH transmissions, the HARQ-ACK information bits can be associated with one HARQ-ACK bit for each CBG and each transport block, such as N HARQ-ACK bits for N CBGs per transport block. For HARQ-ACK feedback of a single codeword and / or transport block PDSCH transmission on the serving cell, the HARQ-ACK information bits of the PDSCH can be interpreted using one HARQ-ACK bit for each sub-CBG of a single scheduled PDSCH codeword and / or transport block. Up to N CBGs can be implemented compared to a maximum CBG size of N CBGs. L smaller / higher granularity sub-CBGs.

[0055] Figure 4 An example flowchart of a method according to certain exemplary embodiments is shown. In the example embodiment, Figure 4 The method can be performed by a network element or a group of network elements in a 3GPP system (such as LTE or 5G-NR). For example, in an exemplary embodiment, Figure 4 The method can be performed by user equipment, user devices, or mobile devices connected to the network, such as similar Figure 7 The UE of device 710 shown in the figure.

[0056] According to various exemplary embodiments, Figure 4 The method may include: at 410, the user equipment determining that it is scheduled to utilize a single codeword or transport block for the shared data channel. At 420, the method may further include: the user equipment assigning multiple code blocks to multiple subgroups of multiple code block groups based on a maximum number of codewords available for operation on the shared data channel, to generate a hybrid automatic repeat request acknowledgment feedback for the shared data channel. At 430, the method may further include the user equipment providing a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0057] Various exemplary embodiments may specify that each of the multiple code block groups can be divided into multiple subgroups by a maximum number of codewords. Some exemplary embodiments may specify that the multiple subgroups can be formed based on a mapping process using the number of multiple code block groups multiplied by the maximum number of codewords. Feedback may be provided to the multiple subgroups using a single scheduled codeword or all feedback bits of a transport block.

[0058] Some exemplary embodiments may specify that a single codeword or transport block on a shared data channel may be: scheduled by 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 transmitted based on a semi-persistent shared data channel, or transmitted based on a configured-permitted shared data channel. Hybrid automatic repeat request acknowledgment feedback operation may be activated by higher-layer signaling. Higher-layer signaling may be a radio resource control message.

[0059] Figure 5 An example flowchart of another method according to certain exemplary embodiments is shown. In the example embodiment, Figure 5 The method can be performed by a network element or a group of network elements in a 3GPP system (such as LTE or 5G-NR). For example, in an exemplary embodiment, Figure 5 The method can be performed by user equipment, user devices, or mobile devices connected to the network, such as similar Figure 7 Another example of the UE of device 710 shown in the figure.

[0060] According to various exemplary embodiments, Figure 5 The method may include, at 510, decoding the control channel of the user equipment for shared data channel reception or transmission, wherein the shared data channel reception or transmission is based on code block group transmission information. At 520, the method may further include, at 530, determining whether the user equipment is scheduled to utilize a single codeword or transport block on the shared data channel based on scheduling information. The method may further include, at 530, determining, based on field entries of the decoded code block group transmission information included in the downlink control information, the scheduled code block for shared data channel reception or transmission, wherein the code block group transmission information is mapped to each of multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation.

[0061] Some exemplary embodiments may specify that each of the multiple code block groups is divided into multiple subgroups by the maximum number of codewords. Some exemplary embodiments may provide that the multiple subgroups are formed based on a mapping process using the number of multiple code block groups multiplied by the maximum number of codewords.

[0062] Various exemplary embodiments may specify that scheduling information may be provided to multiple subgroups using all bits of a codeword or transport block group for a single scheduling. A single codeword or transport block on a shared data channel may be scheduled by 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. Shared data channel operation may be activated by higher-layer signaling. Higher-layer signaling may be a radio resource control message.

[0063] Figure 6 An example flowchart of another method according to certain exemplary embodiments is shown. In the example embodiment, Figure 6 The method can be performed by a network element or a group of network elements in a 3GPP system (such as LTE or 5G-NR). For example, in an exemplary embodiment, Figure 6 The method can be performed by user equipment, user devices, or mobile devices connected to the network, such as similar Figure 7 Another example of a UE for device 710 shown in the figure.

[0064] According to various exemplary embodiments, Figure 6 The method may include, at 610, decoding the control channel of the user equipment (UE) for reception of the physical downlink shared data channel. The physical downlink shared data channel reception may be based on code block group transmission information. At 620, the method may include determining that the UE is scheduled using a single codeword or transport block for reception of the physical downlink shared data channel, and at 630, generating a hybrid automatic repeat request (HRP) acknowledgment feedback for the physical downlink shared data channel by the UE assigning multiple code blocks to multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation. The method may further include, at 640, providing a HRP acknowledgment to a network entity, the HRP acknowledgment indicating the feedback to the network entity.

[0065] Figure 7 A collection of devices 710 and 720 according to various exemplary embodiments is illustrated. In various exemplary embodiments, device 710 may be an element in or associated with a communication network, such as a UE, RedCap UE, SLUE, mobile device (ME), mobile station, mobile equipment, fixed device, IoT device, or other device. For example, a UE according to the various exemplary embodiments described above may be an example of device 710. It should be noted that those skilled in the art will understand that device 710 may include... Figure 7Components or features not shown. Additionally, device 720 may be a network, network entity, core network unit, or element in or associated with such a communication network, such as a base station, NE, or gNB. For example, a gNB according to the various exemplary embodiments described above may be an example of device 720. It should be noted that those skilled in the art will understand that device 720 may include... Figure 7 Components or features not shown. It should be noted that those skilled in the art will understand that device 720 may include... Figure 7 Components or features not shown in the diagram.

[0066] According to various exemplary embodiments, device 710 may include at least one processor and at least one memory, such as Figure 7 As shown. The memory can store instructions that, when executed by a processor, cause device 710 to: determine whether device 710 is scheduled to utilize a single codeword or transport block for a shared data channel; and, based on the maximum number of codewords available for operation on the shared data channel, allocate multiple code blocks to multiple subgroups within multiple code block groups to generate a hybrid automatic repeat request acknowledgment feedback for the shared data channel. Device 710 can also be caused to provide a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0067] According to some exemplary embodiments, variations of device 710 may include at least one processor and at least one memory, such as Figure 7 As shown. The memory can store instructions that, when executed by the processor, cause device 710 to decode the control channel for scheduling user equipment for shared data channel reception or transmission. Shared data channel reception or transmission can be based on block group transmission information. Device 710 can also determine, based on scheduling information, whether it can be scheduled using a single codeword or transport block on the shared data channel. Device 710 can also determine the scheduled code block for shared data channel reception or transmission based on field entries of the decoded block group transmission information included in the downlink control information. The block group transmission information can be mapped to each of multiple subgroups of multiple block groups based on the maximum number of codewords available for shared data channel operation.

[0068] According to some exemplary embodiments, another variation of the device 710 may include at least one processor and at least one memory, such as Figure 7As shown. The memory can store instructions that, when executed by the processor, cause the device 710 to decode the control channel of the scheduling user equipment for physical downlink shared data channel reception. Physical downlink shared data channel reception can be based on code block group transmission information. The device can also generate a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel by allocating multiple code blocks to multiple subgroups in multiple code block groups based on the maximum number of codewords available for shared data channel operation. The device 710 can also provide a hybrid automatic repeat request acknowledgment to the network entity, indicating feedback to the network entity.

[0069] The various exemplary embodiments described above can provide several technical improvements, enhancements, and / or advantages. For example, some exemplary embodiments can provide advantages in one or more processes to provide higher granularity CBG-based PDSCH HARQ-ACK feedback and PDSCH / PUSCH CBG-based scheduling granularity for a single codeword PDSCH / PUSCH when configured with multiple CW PDSCH / PUSCH operations without additional DL / UL control overhead. Some exemplary embodiments can advantageously provide reuse of HARQ-ACK feedback for a single scheduled TB / CW or unused bits in the CBGTI field of an unscheduled TB / CW.

[0070] In some example embodiments, device 710 and / or 720 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some example embodiments, device 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 technology).

[0071] like Figure 7 As shown in the example, device 710 and / or device 720 may include or be coupled to processor 712 and processor 722, respectively, for processing information and executing instructions or operations. Processor 712 and processor 722 can be any type of general-purpose or special-purpose processor. In practice, processor 712 and processor 722 may include one or more of the following as examples: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and processor based on a multi-core processor architecture. Although in Figure 7The diagram illustrates a single processor 712 (and processor 722) for each of devices 710 and / or 720, but multiple processors may be utilized according to other example embodiments. For example, it should be understood that in some example embodiments, devices 710 and / or 720 may include two or more processors that can form a multiprocessor system capable of supporting multiple processing (e.g., in this case, processors 712 and 722 may represent multiple processors). According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled to, for example, form a computer cluster.

[0072] Processors 712 and 722 can respectively perform functions associated with the operation of devices 710 and / or 720, 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 devices 710 and / or 720, including... Figures 1 to 6 The process is shown in the figure.

[0073] Devices 710 and / or 720 may also include or be coupled to memory 714 and / or memory 724 (internal or external), respectively. Memory 714 and / or memory 724 may be coupled to processor 712 and processor 722, respectively, for storing information and instructions executable by processor 712 and processor 722. Memory 714 (and memory 724) may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, memory 714 (and memory 724) may include random access memory (RAM), read-only memory (ROM), static storage devices such as magnetic disks or optical disks, hard disk drives (HDDs), or any combination of any other type of non-transitory machine or computer-readable medium. The instructions stored in memory 714 and memory 724 may include program instructions or computer program code that, when executed by processor 712 and processor 722, enable device 710 and / or device 720 to perform the tasks described herein.

[0074] In some example embodiments, device 710 and / or device 720 may also include or be coupled to (internal or external) a drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage medium may store computer programs or software for execution by processor 712 and processor 722 and / or device 710 and / or device 720 to perform... Figures 1 to 6 Any of the methods shown.

[0075] In some exemplary embodiments, device 710 and / or device 720 may further include or be coupled to one or more antennas 715 and 725 for receiving downlink signals from device 710 and device 720 and transmitting signals via uplink, respectively. Device 710 and / or device 720 may also include transceivers 716 and 726 configured to transmit and receive information, respectively. Transceivers 716 and 726 may also include radio interfaces that may correspond to multiple radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0076] For example, transceiver 716 and transceiver 726 may be configured to modulate information onto a carrier waveform for transmission and demodulate received information for further processing by other elements of device 710 and / or device 720. In other example embodiments, transceivers 716 and 726 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some example embodiments, device 710 and / or 720 may include input and / or output devices (I / O devices). In some example embodiments, device 710 and / or device 720 may also include a user interface, such as a graphical user interface or a touchscreen.

[0077] In some example embodiments, memories 714 and 724 store software modules that provide functionality when executed by processors 712 and 722, respectively. These modules may include, for example, an operating system that provides operating system functionality for device 710 and / or device 720. The memories may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 710 and / or device 720. Components of device 710 and / or device 720 may be implemented in hardware or as any suitable combination of hardware and software. According to some example embodiments, device 710 may optionally be configured to communicate with device 720 via a wireless or wired communication link 730 according to any radio access technology, such as NR.

[0078] According to some example embodiments, processors 712 and 722, and memories 714 and 724 may be included in or form part of processing or control circuitry. Additionally, in some example embodiments, transceivers 716 and 726 may be included in or form part of transceiver circuitry.

[0079] In some exemplary embodiments, the apparatus (e.g., apparatus 710 and / or apparatus 720) may include components for performing the methods, processes, or any variations discussed herein. Examples of components may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for inducing the execution of operations.

[0080] Certain exemplary embodiments may point to an apparatus comprising: means for determining that the apparatus may be scheduled using a single codeword or transport block for a shared data channel; and means for generating a hybrid automatic repeat request acknowledgment feedback for the shared data channel by allocating multiple code blocks to multiple subgroups of multiple code block groups based on a maximum number of codewords available for operation of the shared data channel. The apparatus may further include means for providing a hybrid automatic repeat request acknowledgment by a user equipment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0081] Some exemplary embodiments may be directed to another apparatus, which includes components for decoding a control channel of a scheduled user equipment for shared data channel reception or transmission. Shared data channel reception or transmission may be based on code block group transmission information. The apparatus may further include components for determining, based on scheduling information, whether the apparatus may be scheduled to utilize a single codeword or transport block on the shared data channel. The apparatus may further include components for determining the scheduled code block for shared data channel reception or transmission based on field entries of the decoded code block group transmission information included in downlink control information. The code block group transmission information may be mapped to each of multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation.

[0082] Various exemplary embodiments may be directed to another apparatus including components for decoding a control channel of a scheduled user equipment for physical downlink shared data channel reception. Physical downlink shared data channel reception may be based on code block group transmission information. The apparatus may further include: components for determining that the apparatus may be scheduled using a single codeword or transport block for the physical downlink shared data channel reception; and components for generating a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to a maximum number of codewords available for shared data channel operation. The apparatus may further include components for providing a hybrid automatic repeat request acknowledgment to a network entity, the hybrid automatic repeat request acknowledgment indicating feedback to the network entity.

[0083] As used herein, the term "circuit" can refer to a hardware circuit implementation only (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry with software / firmware, any portion of a hardware processor(s) having software (including digital signal processors) that works together to enable a device (e.g., device 710 and / or device 720) to perform various functions, and / or a hardware circuit(s) and / or a processor(s), or portions thereof, that use software for operation, but the software may be absent when it is not required for operation. As another example, as used herein, the term "circuit" can also encompass a hardware circuit or processor(s) only, or a portion of a hardware circuit or processor, along with accompanying software and / or firmware. The term "circuit" can also encompass baseband integrated circuits, such as those in servers, cellular network nodes or devices, or other computing or networking devices.

[0084] A computer program product may include one or more computer-executable components configured to perform some example embodiments during program runtime. The one or more computer-executable components may be at least one piece of software code or a portion thereof. Modifications and configurations required to implement the functionality of some example embodiments may be executed as routines(s), which(s) may be implemented as added or updated software routines(s). The software routines(s) may be downloaded to the device.

[0085] As an example, software or computer program code, or portions thereof, may be in the form of source code, object code, or some intermediate form, and may be stored on some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Such a carrier may include, for example, recording media, computer memory, read-only memory, photoelectric and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the required processing power, the computer program may execute in a single electronic digital computer or may be distributed across multiple computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0086] In other example embodiments, the function may be performed by hardware or circuitry included in the device (e.g., device 710 and / or device 720), for example by using 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 function may be implemented as a signal, a non-tangible component that can be carried by an electromagnetic signal downloaded from the Internet or other networks.

[0087] According to certain example embodiments, an apparatus (such as a node, device, or corresponding component) may be configured as a circuit, a computer, or a microprocessor (such as a single-chip computer element) or a chipset, the apparatus including at least a memory for providing storage capacity for arithmetic operations and an arithmetic processor for performing arithmetic operations.

[0088] The features, structures, or characteristics of the exemplary embodiments described throughout this specification can be combined in any suitable manner in one or more exemplary embodiments. For example, the use of phrases such as "certain embodiments," "exemplary embodiments," "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 can be included in at least one embodiment. Therefore, the appearance of phrases such as "in some embodiments," "exemplary embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics can be combined in any suitable manner in one or more exemplary embodiments. Furthermore, the terms "cell," "node," "gNB," or other similar language throughout this specification are used interchangeably.

[0089] As used herein, “at least one of the following: ” and “at least one of ” and similar expressions, wherein a list of two or more elements connected by “and” or “or” means at least one of these elements, or any two or more of these elements, or at least all of these elements.

[0090] It will be readily understood by those skilled in the art that the disclosure described above can be practiced using processes of different sequences and / or hardware components with configurations different from those disclosed. Therefore, although this disclosure has been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be readily apparent while remaining within the spirit and scope of the exemplary embodiments. While the above embodiments relate to 5G NR and LTE technologies, the above embodiments can also be applied to any other current or future 3GPP technologies, such as Advanced LTE and / or fourth-generation (4G) technologies.

[0091] Partial vocabulary list: 3GPP Third Generation Partnership Project 5G fifth generation ACK confirmation AL aggregation level BW bandwidth BWP bandwidth portion CB code block CBG code block group CBGTI CBG transmission information CW code DCI downlink control information DL downlink EMBB Enhanced Mobile Broadband gNB 5G or next-generation node B HARQ Hybrid Automatic Repeat Request LTE Long Term Evolution MAC Media Access Control NACK (Negative Confirmation) NR New Radio PDCCH Physical Downlink Control Channel PDSCH Physical Downlink Shared Channel PRB Physical Resource Block PSS master synchronization signal PUCCH (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel RAN Radio Access Network RF radio frequency RRC Radio Resource Control SCS subcarrier spacing TB transport block TBS transport block size TCI Transport Configuration Indicator UE User Equipment UL uplink URLLC Ultra-Reliable Low-Latency Communication

Claims

1. A method comprising: The user equipment determines whether it is scheduled using a single codeword or transport block for a shared data channel; The user equipment generates a hybrid automatic repeat request acknowledgment feedback for the shared data channel by allocating multiple code blocks to multiple subgroups of multiple code block groups based on the maximum number of codewords available for operation of the shared data channel. as well as The user equipment provides the hybrid automatic repeat request acknowledgment to the network entity, and the hybrid automatic repeat request acknowledgment indicates the feedback to the network entity.

2. The method of claim 1, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

3. The method of claim 1, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

4. The method according to any one of claims 1 to 3, wherein the feedback is provided to the plurality of subgroups using all feedback bits for the codeword or transport block of the single schedule.

5. The method according to any one of claims 1 to 4, wherein the single codeword or transport block on the shared data channel is: Scheduled by 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 semi-persistent shared data channel transmission; or Transmission is based on a shared data channel that has been configured and permitted.

6. The method according to any one of claims 1 to 5, wherein the hybrid automatic repeat request acknowledgment feedback operation is activated by higher-layer signaling.

7. The method of claim 6, wherein the higher-layer signaling is a radio resource control message.

8. A method comprising: The control channel of the user equipment is decoded by the user equipment for receiving or transmitting data through the shared data channel, wherein the receiving or transmitting of the shared data channel is based on code block group transmission information. The user equipment determines, based on the scheduling information, whether it is scheduled using a single codeword or transport block on the shared data channel; as well as The user equipment determines the scheduled code blocks for shared data channel reception or transmission based on field entries of the decoded code block group transmission information included in the downlink control information, wherein the code block group transmission information is mapped to each of the multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation.

9. The method of claim 8, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

10. The method of claim 8, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

11. The method according to any one of claims 8 to 10, wherein the scheduling information is provided to the plurality of subgroups by providing all bits of the code block group transmission information using the codeword or transport block for the single scheduling.

12. The method according to any one of claims 8 to 11, wherein the single codeword or transport block on the shared data channel is scheduled by downlink control information on the 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 claims 8 to 12, wherein the shared data channel operation is activated by higher-layer signaling.

14. The method of claim 13, wherein the higher-layer signaling is a radio resource control message.

15. A method comprising: The user equipment decodes the control channel that schedules the user equipment for receiving physical downlink shared data channel information, wherein the physical downlink shared data channel reception is based on code block group transmission information; The user equipment determines whether it is scheduled using a single codeword or transport block received for the physical downlink shared data channel; The user equipment (UE) generates a hybrid automatic repeat request (HRP) acknowledgment feedback for the physical downlink shared data channel by allocating multiple code blocks to multiple subgroups of multiple code block groups based on the maximum number of codewords available for operation on the shared data channel; and The user equipment provides the hybrid automatic repeat request acknowledgment to the network entity, and the hybrid automatic repeat request acknowledgment indicates the feedback to the network entity.

16. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: It is determined that the device is scheduled using a single codeword or transport block for a shared data channel; Based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to the maximum number of codewords available for operation on the shared data channel, a hybrid automatic repeat request acknowledgment feedback for the shared data channel is generated; and The Hybrid Automatic Repeat Request Acknowledgment is provided to the network entity, and the Hybrid Automatic Repeat Request Acknowledgment indicates the feedback to the network entity.

17. The apparatus of claim 16, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

18. The apparatus of claim 16, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

19. The apparatus according to any one of claims 16 to 18, wherein the feedback is provided to the plurality of subgroups using all feedback bits for the codeword or transport block of the single schedule.

20. The apparatus according to any one of claims 16 to 19, wherein the single codeword or transport block on the shared data channel is: Scheduled by 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 semi-persistent shared data channel transmission; or Transmission is based on a shared data channel that has been configured and permitted.

21. The apparatus according to any one of claims 16 to 20, wherein the hybrid automatic repeat request acknowledgment feedback operation is activated by higher-layer signaling.

22. The apparatus of claim 21, wherein the higher-layer signaling is a radio resource control message.

23. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The control channel of the device is decoded for shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on code block group transmission information; Based on the scheduling information, it is determined that the device is scheduled to utilize a single codeword or transport block on the shared data channel; as well as Based on field entries of the decoded code block group transmission information included in the downlink control information, scheduled code blocks for shared data channel reception or transmission are determined, wherein the code block group transmission information is mapped to each of multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation.

24. The apparatus of claim 23, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

25. The apparatus of claim 23, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

26. The apparatus according to any one of claims 23 to 25, wherein the scheduling information is provided to the plurality of subgroups by providing all bits of the code block group transmission information using codewords or transport blocks for the single scheduling.

27. The apparatus according to any one of claims 23 to 26, wherein the individual codeword or transport block on the shared data channel is scheduled by downlink control information on the 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 claims 23 to 27, wherein the shared data channel operation is activated by higher-layer signaling.

29. The apparatus of claim 28, wherein the higher-layer signaling is a radio resource control message.

30. An apparatus comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: The control channel of the device is decoded for receiving physical downlink shared data channel information, wherein the physical downlink shared data channel reception is based on code block group transmission information; It is determined that the device is scheduled using a single codeword or transport block received for the physical downlink shared data channel; Based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to the maximum number of codewords available for operation on the shared data channel, a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel is generated; and The Hybrid Automatic Repeat Request Acknowledgment is provided to the network entity, and the Hybrid Automatic Repeat Request Acknowledgment indicates the feedback to the network entity.

31. An apparatus comprising: Components used to confirm that the device is scheduled using a single codeword or transport block for a shared data channel; A component for generating a hybrid automatic repeat request acknowledgment feedback for the shared data channel by assigning multiple code blocks to multiple subgroups of multiple code block groups based on the maximum number of codewords available for operation of the shared data channel. as well as A component for providing a Hybrid Automatic Repeat Request acknowledgment to a network entity, the Hybrid Automatic Repeat Request acknowledgment indicating the feedback to the network entity.

32. The apparatus of claim 31, wherein each of the plurality of code block groups is divided into the plurality of subgroups by a maximum number of codewords.

33. The apparatus of claim 31, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

34. The apparatus according to any one of claims 31 to 33, wherein the feedback is provided to the plurality of subgroups using all feedback bits for the codeword or transport block of the single schedule.

35. The apparatus according to any one of claims 31 to 34, wherein the single codeword or transport block on the shared data channel is: Scheduled by 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 semi-persistent shared data channel transmission; or Transmission is based on a shared data channel that has been configured and permitted.

36. The apparatus according to any one of claims 31 to 35, wherein the hybrid automatic repeat request acknowledgment feedback operation is activated by higher-layer signaling.

37. The apparatus of claim 36, wherein the higher-layer signaling is a radio resource control message.

38. An apparatus comprising: A component for decoding the control channel of the device for scheduling the shared data channel reception or transmission, wherein the shared data channel reception or transmission is based on code block group transmission information; Components used to determine, based on the scheduling information, whether the device is scheduled to utilize a single codeword or transport block on the shared data channel; as well as A component for determining scheduled code blocks for shared data channel reception or transmission based on field entries of the decoded code block group transmission information included in downlink control information, wherein the code block group transmission information is mapped to each of multiple subgroups of multiple code block groups based on a maximum number of codewords available for shared data channel operation.

39. The apparatus of claim 38, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

40. The apparatus of claim 38, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

41. The apparatus according to any one of claims 38 to 40, wherein the scheduling information is provided to the plurality of subgroups by providing all bits of the code block group transmission information using codewords or transport blocks for the single scheduling.

42. The apparatus according to any one of claims 38 to 41, wherein the individual codeword or transport block on the shared data channel is scheduled by downlink control information on the 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 claims 38 to 42, wherein the shared data channel operation is activated by higher-layer signaling.

44. The apparatus of claim 43, wherein the higher-layer signaling is a radio resource control message.

45. An apparatus comprising: A component for decoding the control channel of the device for scheduling the physical downlink shared data channel reception, wherein the physical downlink shared data channel reception is based on code block group transmission information; The component used to determine whether the device is scheduled using a single codeword or transport block received for a physical downlink shared data channel; A component for generating hybrid automatic repeat request acknowledgment feedback for a physical downlink shared data channel by allocating multiple code blocks to multiple subgroups of multiple code block groups based on the maximum number of codewords available for operation of the shared data channel. as well as A component for providing a Hybrid Automatic Repeat Request acknowledgment to a network entity, the Hybrid Automatic Repeat Request acknowledgment indicating the feedback to the network entity.

46. ​​A non-transitory computer-readable medium comprising program instructions, which, when executed by a device, cause the device to at least: It is determined that the device is scheduled using a single codeword or transport block for a shared data channel; Based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to the maximum number of codewords available for operation on the shared data channel, a hybrid automatic repeat request acknowledgment feedback for the shared data channel is generated; and The Hybrid Automatic Repeat Request Acknowledgment is provided to the network entity, and the Hybrid Automatic Repeat Request Acknowledgment indicates the feedback to the network entity.

47. The non-transitory computer-readable medium of claim 46, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

48. The non-transitory computer-readable medium of claim 46, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

49. The non-transitory computer-readable medium according to any one of claims 46 to 48, wherein the feedback is provided to the plurality of subgroups using all feedback bits for the codeword or transport block of the single schedule.

50. The non-transitory computer-readable medium according to any one of claims 46 to 49, wherein the single codeword or transport block on the shared data channel is: Scheduled by 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 semi-persistent shared data channel transmission; or Transmission is based on a shared data channel that has been configured and permitted.

51. The non-transitory computer-readable medium according to any one of claims 46 to 50, wherein the hybrid automatic repeat request acknowledgment feedback operation is activated by higher-layer signaling.

52. The non-transitory computer-readable medium of claim 51, wherein the higher-layer signaling is a radio resource control message.

53. A non-transitory computer-readable medium comprising program instructions, which, when executed by a means, cause the means to at least: The control channel of the device is decoded for shared data channel reception or shared data channel transmission, wherein the shared data channel reception or transmission is based on code block group transmission information; Based on the scheduling information, it is determined that the device is scheduled to utilize a single codeword or transport block on the shared data channel; as well as Based on field entries of the decoded code block group transmission information included in the downlink control information, scheduled code blocks for shared data channel reception or transmission are determined, wherein the code block group transmission information is mapped to each of multiple subgroups of multiple code block groups based on the maximum number of codewords available for shared data channel operation.

54. The non-transitory computer-readable medium of claim 53, wherein each of the plurality of code block groups is divided into the plurality of subgroups by the maximum number of codewords.

55. The non-transitory computer-readable medium of claim 53, wherein the plurality of subgroups are formed based on a mapping process using the number of the plurality of code block groups multiplied by the maximum number of codewords.

56. The non-transitory computer-readable medium according to any one of claims 53 to 55, wherein the scheduling information is provided to the plurality of subgroups by providing all bits of the code block group transmission information using codewords or transport blocks for the single scheduling.

57. The non-transitory computer-readable medium according to any one of claims 53 to 56, wherein the individual codeword or transport block on the shared data channel is scheduled by downlink control information on the downlink control channel, wherein the downlink control information is formatted 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 claims 53 to 57, wherein the shared data channel operation is activated by higher-layer signaling.

59. The non-transitory computer-readable medium of claim 58, wherein the higher-layer signaling is a radio resource control message.

60. A non-transitory computer-readable medium comprising program instructions, which, when executed by a means, cause the means to at least: The control channel of the device is decoded for receiving physical downlink shared data channel information, wherein the physical downlink shared data channel reception is based on code block group transmission information; It is determined that the device is scheduled using a single codeword or transport block received for the physical downlink shared data channel; Based on allocating multiple code blocks to multiple subgroups of multiple code block groups according to the maximum number of codewords available for operation on the shared data channel, a hybrid automatic repeat request acknowledgment feedback for the physical downlink shared data channel is generated; and The Hybrid Automatic Repeat Request Acknowledgment is provided to the network entity, and the Hybrid Automatic Repeat Request Acknowledgment indicates the feedback to the network entity.

61. A computer program comprising instructions stored thereon for performing at least the method according to claim 1.

62. A computer program comprising instructions stored thereon for performing at least the method according to claim 8.

63. A computer program comprising instructions stored thereon for performing at least the method according to claim 15.

64. An apparatus comprising one or more circuits configured to perform the method according to claim 1.

65. An apparatus comprising one or more circuits configured to perform the method of claim 8.

66. An apparatus comprising one or more circuits configured to perform the method of claim 15.

Images