Wireless data transmission using parity blocks

Abstract

[0006] Methods, systems, and apparatuses for wireless communication are described. In one exemplary aspect, a wireless communication method is disclosed. One exemplary method of wireless communication includes receiving, by a wireless device from a network device, a first message comprising one or more parameters related to error correction coding, and transmitting, by the wireless device to the network device, a data transmission using the error correction coding and in accordance with the one or more parameters.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This patent document is a continuation of International Patent Application No. PCT / CN2020 / 096098, filed June 15, 2020. The entire contents of the aforementioned patent application are incorporated by reference as part of the disclosure of this application.

[0002] This document generally relates to wireless communications. [Background technology]

[0003] Wireless communication technologies are moving the world towards an increasingly connected and networked society. The rapid growth of wireless communication and technological advances are leading to further demands for capacity and connectivity. Other aspects such as energy consumption, device cost, spectrum efficiency, and latency are also important to meet the needs of various communication scenarios. Compared to existing wireless networks such as LTE wireless networks, next generation systems and wireless communication techniques need to provide support for an increased number of users and devices. Summary of the Invention [Means for solving the problem]

[0004] This document relates to methods, systems, and devices for monitoring schemes for downlink control signals in mobile communication technologies, including fifth generation (5G) and new radio (NR) communication systems.

[0005] In one example aspect, a wireless communication method is disclosed that includes receiving, by a wireless device, from a network device a first message comprising one or more parameters related to error correction coding, and transmitting, by the wireless device, a data transmission to the network device using the error correction coding and in accordance with the one or more parameters.

[0006] In another example aspect, a wireless communication method is disclosed that includes transmitting, by a network device to a wireless device, a first message comprising one or more parameters related to error correction coding, and transmitting, after transmission of the first message, by the network device to the wireless device a data transmission using the error correction coding and in accordance with the one or more parameters.

[0007] In another example aspect, a wireless communication method is disclosed that includes receiving, by a wireless device from a network device, a first message comprising one or more parameters related to error correction coding, and receiving, by the wireless device from the network device, a data transmission using the error correction coding and in accordance with the one or more parameters.

[0008] In another example aspect, a wireless communication method is disclosed that includes transmitting, by a network device, a first message to a wireless device, the first message comprising one or more parameters related to error correction coding, and receiving, after transmission of the first message, by the network device from the wireless device a data transmission using the error correction coding and in accordance with the one or more parameters.

[0009] In another example aspect, a wireless communication method is disclosed that includes: generating, by a first wireless device, a plurality of code blocks including at least one redundancy parity block from data bits to be transmitted, partitioning the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to permitted puncturing bit locations, rate matching the code blocks according to the permitted puncturing bit locations by puncturing, and transmitting a result of the rate matching to a second wireless device.

[0010] In another example aspect, a wireless communication method is disclosed that includes receiving, by a first wireless device, a data transmission comprising rate-matched data, the rate-matched data being generated by partitioning a plurality of code blocks, including at least one redundancy parity block, into a first group of code blocks and a second group of code blocks according to permitted puncturing locations and puncturing the first and second groups of code blocks according to the permitted puncturing locations, and determining from the data transmission data bits encoded in the data transmission.

[0011] In another example aspect, a wireless communication method is disclosed that includes: generating, by a first wireless device, a plurality of code blocks including at least one redundancy parity block from data bits to be transmitted, dividing the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to permitted puncturing locations, rate matching the plurality of code blocks by puncturing according to a puncturing pattern, where the puncturing pattern defines locations of bits permitted to be punctured for each code block in the plurality of code blocks, and transmitting a result of the rate matching to a second wireless device.

[0012] In another example aspect, a wireless communication method is disclosed that includes receiving, by a first wireless communication device, a data transmission comprising a plurality of code blocks including at least one redundancy parity block, the plurality of code blocks being rate matched according to a puncturing pattern that defines locations of bits allowed to be punctured for each code block in the plurality of code blocks, and determining data bits encoded in the data transmission based on the puncturing pattern.

[0013] In yet another exemplary aspect, the methods described above are embodied in the form of processor executable code and stored in a computer readable program medium.

[0014] In yet another exemplary embodiment, a device configured or operable to perform the methods described above is disclosed.

[0015] These and other aspects and their implementations are described in more detail in the drawings, description, and claims. The present invention provides, for example, the following: (Item 1) 1. A method implemented by a wireless device, comprising: receiving, by the wireless device, a first message from the network device, the first message comprising one or more parameters related to error correction coding; transmitting, by the wireless device, a data transmission to the network device using the error correction coding in accordance with the one or more parameters. A method comprising: (Item 2) 1. A method implemented by a wireless device, comprising: transmitting, by the network device to the wireless device, a first message comprising one or more parameters related to error correction coding; transmitting, by the network device after transmission of the first message, a data transmission to the wireless device using the error correction coding and in accordance with the one or more parameters. A method comprising: (Item 3) 1. A method implemented by a wireless device, comprising: receiving, by the wireless device, a first message from the network device, the first message comprising one or more parameters related to error correction coding; receiving, by the wireless device, a data transmission from the network device using the error correction coding in accordance with the one or more parameters; A method comprising: (Item 4) 1. A method implemented by a wireless device, comprising: transmitting, by the network device to the wireless device, a first message comprising one or more parameters related to error correction coding; receiving, by the network device after transmitting the first message, a data transmission from the wireless device using the error correction coding and in accordance with the one or more parameters. A method comprising: (Item 5) 1. A wireless communication method, comprising: generating, by the first wireless device, a plurality of code blocks from data bits to be transmitted, the code blocks including at least one redundancy parity block; partitioning the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to allowed puncturing bit locations; rate matching the code block according to the allowed puncturing bit locations by puncturing; transmitting a result of the rate matching to a second wireless device; A method comprising: (Item 6) 1. A wireless communication method, comprising: receiving, by a first wireless device, a data transmission comprising rate-matched data, the rate-matched data being generated by partitioning a plurality of code blocks, including at least one redundancy parity block, into a first group of code blocks and a second group of code blocks according to permitted puncturing locations, and puncturing the first and second groups of code blocks according to the permitted puncturing locations; determining from the data transmission data bits encoded within the data transmission; A method comprising: (Item 7) 1. A wireless communication method, comprising: generating, by the first wireless device, a plurality of code blocks from data bits to be transmitted, the code blocks including at least one redundancy parity block; partitioning the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to permitted puncturing locations; rate matching the plurality of code blocks by puncturing according to a puncturing pattern, the puncturing pattern defining locations of bits that are allowed to be punctured for each code block in the plurality of code blocks; transmitting a result of the rate matching to a second wireless device; A method comprising: (Item 8) 1. A wireless communication method, comprising: receiving, by a first wireless device, a data transmission comprising a plurality of code blocks including at least one redundancy parity block, the plurality of code blocks being rate matched according to a puncturing pattern that defines locations of bits that are allowed to be punctured for each code block in the plurality of code blocks; determining data bits encoded within the data transmission based on the puncturing pattern; and A method comprising: (Item 9) 5. The method according to any of items 1-4, wherein the first message is a radio resource control (RRC) signaling, and the parameters of the first message are related to a redundancy parity block transmission. (Item 10) 10. The method according to any of items 1-4 or 9, wherein the first message is transmitted as downlink control information (DCI) having a predefined format type. (Item 11) 11. The method of any one of items 1-4, 9 or 10, wherein the data transmission includes a redundancy parity block transmission. (Item 12) 12. The method according to any of items 1-4 or 9-11, wherein the redundancy parity block included in the data transmission does not include information bits of a transport block and is obtained by at least a plurality of code blocks of the transport block and a generation sequence. (Item 13) 13. The method of any of items 1-4 or 9-12, wherein a cyclic redundancy check (CRC) of the first message is scrambled by a specific radio network identifier (RNTI). (Item 14) The DCI comprises the following parameters: an identifier for redundancy parity block transmission; a number of code blocks associated with the redundant parity block transmission; a generating sequence for the redundant parity block transmission; Number of redundant parity blocks, an index of a code block associated with said redundancy parity block; Rate matching bit pattern, HARQ processor number, or A bitmap of the code block group a plurality of fields configurable to indicate at least one of: the generation sequence is used to generate the redundancy parity blocks; the rate matching bit pattern is used to determine puncturing bit locations of the plurality of code blocks for the data transmission. 13. The method according to any one of items 1 to 12. (Item 15) 15. The method of claim 12 or 14, wherein the generated sequence is determinable from at least one of a number of the plurality of code blocks associated with the redundancy parity block and a number of code block groups for the transport block. (Item 16) Item 15. The method of item 14, wherein the rate matching bit pattern includes a number of puncturing bits or corresponding puncturing bit locations of the multiple code blocks for the data transmission. (Item 17) 15. The method of any of items 1-12 or 14, wherein one or more fields in the DCI are configured according to higher layer parameters that configure the redundancy parity block transmission. (Item 18) 5. The method of any of items 1-12 or 14, wherein one or more fields in the DCI are configured based on higher layer parameters reported by the wireless device indicating that the wireless device is capable of performing the redundancy parity block transmission. (Item 19) 15. The method of claim 12 or 14, wherein the generated sequence is indicated as an index into the list from which it originates. (Item 20) 20. The method of claim 19, wherein the generated sequence is derived from a list constructed by higher layer parameters. (Item 21) Item 15. The method of item 14, wherein the number of the plurality of code blocks associated with the redundancy parity block is indicated as a bitmap of a total number of plurality of code blocks of the transport block. (Item 22) Item 15. The method according to item 14, wherein the bit width of the redundancy version is less than 2. (Item 23) The DCI format is as follows: DCI Format 0-1, DCI format 1-1, DCI formats 0-2, DCI Format 1-2, or Specific DCI format 15. The method according to any one of items 1-12 or 14, wherein at least one of (Item 24) 24. The method of any of items 14 or 23, wherein at least one of a first type field in the DCI format 0-1, DCI format 1-1, DCI format 0-2, DCI format 1-2, or a specific DCI format is interpreted as indicating information related to the redundancy parity block transmission if at least one of a second type field of the DCI is set to a predetermined value. (Item 25) The first type of field is: Career indicators, Bandwidth fraction indicator, Frequency domain resource allocation; Time domain resource allocation, Rate matching indicator, HARQ process number, Downlink Allocation Index, Antenna port, A first downlink allocation index; A second downlink allocation index for DCI formats 0-1; ChannelAccess-CPext for DCI format 0-1 or DCI format 1-1, Transmission configuration indication, CBG Transmission Information (CBGTI), CBG Flash Out Information (CBGFI) in DCI format 1-1, Modulation and coding schemes, New data indicators, or Redundancy version for transport block 1 of DCI format 1-1 25. The method according to item 24, comprising at least one of the following: (Item 26) The second type of field in the DCI format 0-1, DCI format 1-1, DCI format 0-2, DCI format 1-2, or specific DCI format may be as follows: Frequency domain resource allocation; Redundancy version, UL-SCH indicator, CSI request, Modulation and coding schemes, New data indicators, Redundancy version, Modulation and coding scheme for transport block 2 in DCI format 1-1, a new data indicator for the transport block 2 in DCI format 1-1, or Redundancy version for the transport block 2 in DCI format 1-1 25. The method according to item 24, comprising at least one of the following: (Item 27) 27. The method of claim 24, wherein the second type field is used to identify a transmission type of the redundancy parity block transmission. (Item 28) The transmission type of the redundancy parity block transmission is as follows: The number of scheduled redundancy parity blocks, or the time of scheduled data transmission of said transport block; 28. The method according to item 27, wherein the concentration is determined by at least one of the following: (Item 29) Item 15. The method of item 14, wherein a number of puncturing bits for each of a plurality of code blocks for the transport block is less than or equal to a number of puncturing bits for the redundancy parity block. (Item 30) The redundancy parity blocks included in the data transmission are the following quantities reported by the wireless device within a range of values: a number of code blocks of the transport block; a number of code blocks of the transport block that are not successfully received by the wireless device; a maximum number of transmissions for the transport block; or The most recent L1-SINR value reported by the wireless device 15. The method of any of items 1-12 or 14, wherein the schedule is based on at least one of the following: (Item 31) 31. The method of claim 30, wherein the value range is configured by a higher layer parameter. (Item 32) 24. The method according to claim 14 or 23, wherein if there is an initial transmission of the transport block, a number of fields related to a redundancy parity code block are not included in the DCI format, and if there is a retransmission of the transport block, a number of fields related to the redundancy parity code block are included in the DCI format. (Item 33) 7. The method of any of items 5 or 6, wherein the allowed puncturing locations of the first group of the code block correspond to a leading edge. (Item 34) 7. The method of any of items 5 or 6, wherein the second group of allowed puncturing locations of the code block correspond to a tail end. (Item 35) Item 15. The method according to any of items 1-12 or 14, wherein puncturing bit locations of a plurality of code blocks of a first type for the transport block are overlapped and located at the beginning of each of the plurality of code blocks, and puncturing bit locations of a plurality of code blocks of a second type for the transport block are overlapped and located at the end of each of the plurality of code blocks. (Item 36) 7. The method according to any of items 5 or 6, wherein the indices of the first type of code blocks are odd numbers and the indices of the second type of code blocks are even numbers. (Item 37) 7. The method according to any of items 5 or 6, wherein the indices of the first type of code blocks are even numbers and the indices of the second type of code blocks are odd numbers. (Item 38) 9. The method of claim 7, wherein the puncturing pattern comprises non-overlapping locations for the multiple code blocks. (Item 39) Item 1-38. The method of any of items 1-38, wherein the wireless device is a user equipment (UE). (Item 40) 9. The method of any of items 1-8, further comprising receiving an acknowledgement of the data transmission. (Item 41) An apparatus for wireless communication comprising a memory and a processor, the processor reading code from the memory and implementing a method according to any of items 1-40. (Item 42) A computer-readable program storage medium having code stored thereon that, when executed by a processor, causes the processor to implement a method according to any of items 1-40. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 illustrates an embodiment of a base station (BS) and user equipment (UE) in wireless communication.

[0017] [Diagram 2] FIG. 2 illustrates an example of rate matching of one of a number of code blocks.

[0018] [Diagram 3] FIG. 3 illustrates an all-ones generating sequence and low-density parity check (LDPC)-based code inter-block parity bits generated by modulo-2 arithmetic.

[0019] [Figure 4] FIG. 4 illustrates a downlink control information (DCI) procedure indicating verification of redundancy parity bit scheduling release of redundancy parity bit scheduling.

[0020] [Diagram 5] 5A and 5B illustrate identical puncturing bit locations per code block within a group.

[0021] [Figure 6] FIG. 6 illustrates puncturing bit locations between code blocks in different groups that contain non-overlapping, redundancy parity blocks.

[0022] [Figure 7] 7A and 7B illustrate puncturing bit locations for all code blocks, including non-overlapping, redundancy parity blocks.

[0023] [Figure 8] FIG. 8 illustrates an element distribution of basis graph 1 for LDPC coding in a fifth generation (5G) new radio (NR) communication system.

[0024] [Figure 9]FIG. 9 illustrates an example of a punctured pattern for a system code block for basis graph 1.

[0025] [Figure 10] FIG. 10 illustrates an example of a punctured pattern for a system code block for basis graph 2.

[0026] [Figure 11] 11A and 11B illustrate puncturing bit locations for all code blocks, including non-overlapping, redundancy parity blocks.

[0027] [Figure 12] FIG. 12 illustrates an example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0028] [Figure 13] FIG. 13 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0029] [Figure 14] FIG. 14 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0030] [Figure 15] FIG. 15 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0031] [Figure 16] FIG. 16 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0032] [Figure 17]FIG. 17 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0033] [Figure 18] FIG. 18 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0034] [Figure 19] FIG. 19 illustrates another example of a process for wireless communication in accordance with some exemplary embodiments of the disclosed technology.

[0035] [Figure 20] 20A and 20B are flowcharts for a downlink data transmission scheduling procedure including redundancy parity blocks for user equipment and gNodeB, and FIGS. 20C and 20D are flowcharts for an uplink data transmission scheduling procedure including redundancy parity blocks for user equipment and gNodeB.

[0036] [Figure 21] 21A and 21B are flow charts of rate matching for a data transmission that includes redundant parity blocks.

[0037] [Figure 22] FIG. 22 is a block diagram representation of a portion of an apparatus that may be used to implement the methods and / or techniques of the disclosed technology. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] Detailed Description Certain features are described using examples of fifth generation (5G) wireless protocols, however, applicability of the disclosed techniques is not limited to only 5G wireless systems.

[0039] In 5G and new radio (NR) communication systems, there are three distinct classes of use cases: enhanced Multi-Bandwidth (eMBB), multiple simultaneous connections (mMTC), and ultra-reliable low latency (URLLC). Each use case corresponds to its own requirements for technical specifications. For example, enhanced Multi-Bandwidth (eMBB) aims to enable larger data volumes and support higher end-user data rates. For multiple simultaneous connections (mMTC), high data rates are less important. Rather, it aims to support a large number of devices with very low device cost and very low device energy consumption. For ultra-reliable low latency (URLLC), very low latency and extremely high reliability are required. These requirements are artificial, but can also be used for further mobile communication, such as augmented reality / virtual reality (AR / VR) applications, which require higher peak data rates (e.g., 300 Mbps).

[0040] With the requirement to support higher data rates and extremely high reliability, it is difficult to achieve the target high data rates and low error rates without channel coding with good error correction performance and effective decoding methods. In 5G NR, low-density parity check (LDPC) coding is used for data transmission in the uplink / downlink (UL / DL) data channel. The target block error rate for LDPC coding is β, and the error probability of each code block is assumed to be independent. Thus, for a transport block (TB) with a TB size (TBS) divided into n code blocks, the error probability of the entire TBS is 1-(1-β) n It can be derived as follows: TBS error rate is increased with an increase in the number of code blocks, and is reduced with a decrease in the target block error rate. Generally, the number of code blocks is increased with an increase in TBS. Therefore, if the target block error rate can be reduced by an improved coding method, the requirement of enabling larger data volume and extremely high reliability can be achieved.

[0041] In addition, from the viewpoint of power saving, the higher frequency of retransmissions of the TB may lead to a larger amount of power consumption. Therefore, in order to reduce the power consumption, it is useful to reduce the number of retransmissions for the TB and improve the reliability of each transmission.

[0042] Disclosed herein are techniques for controlling redundancy parity block transmission, including scheduling, generation, and transmission of additional redundancy parity blocks, which may be applied for initial transmission or retransmissions to improve reliability and reduce the number of retransmissions.

[0043] This document uses headings and subheadings to facilitate easy understanding, but not to limit the scope of the disclosed techniques and embodiments to a certain section. Thus, the embodiments disclosed in different sections can be used together with each other. Furthermore, this document uses examples from only 3GPP NR network architecture and 5G protocols to facilitate understanding, but the disclosed techniques and embodiments may be practiced in other wireless systems using communication protocols different from 3GPP protocols. A brief explanation

[0044] In a 5G NR communication system, there are multiple available modulation and coding scheme (MCS) tables for a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH) serving user equipment (UE). The UE selects the number of resource elements (N MCS) obtained according to resource allocation information configured by higher layer parameters or indicated by downlink control information (DCI). RE ), modulation order (Q m), code rate (R), and layer (v) parameters to determine the TBS. DCI transports downlink control information carried by the physical downlink control channel (PDCCH) with a cyclic redundancy check (CRC) scrambled by the radio network temporary identifier (RNTI). Currently, there are 15 types of DCI formats, which are denoted as DCI formats 0-0 / 1-0 / 0-1 / 1-1 / 0-2 / 1-2 / 2-0 / 2-1 / 2-2 / 2-3 / 2-4 / 2-5 / 2-6 / 3-0 / 3-1. Each DCI format can be used to indicate information regarding specific usage. For example, DCI format 1-1 is used for scheduling PDSCH in one cell and / or triggering one-shot HARQ-ACK codebook feedback. DCI bits for the same DCI format with different types of RNTI can have different usage and interpretation.

[0045] The information transmitted using the DCI format with the CRC scrambled by the RNTI may be divided into multiple fields based on the usage or meaning of the information. For example, the "Frequency Domain Resource Allocation" field in the DCI format 1-1 with the CRC scrambled by the cell RNTI (C-RNTI) is used to indicate the frequency domain resource allocation for scheduling data transmission. The fields defined in the DCI format are information bits a0-a1, A-1 Each field is mapped in the order in which it appears in the description, including zero padding bits, if applicable, with the first field mapped to the least significant information bit, a0, and each successive field mapped to a higher order information bit. The most significant bit of each field is mapped to the least significant information bit for that field. For example, the most significant bit of the first field is mapped to a0.

[0046] An exemplary implementation of the LDPC coding procedure is as follows. 1) Code Block Segmentation: Two basis graphs for NR-LDPC, namely, basis graph 1 (BG1) and basis graph 2 (BG2), are used to obtain a parity check matrix. For example, the UE may select one of the two basis graphs according to the rules shown in Table 1. For BG1, the maximum code block size is K cb = 8448, and for BG2, the maximum code block size is K cb = 3840. For TB, the total number of bits after CRC is TBS + L TB_CRC However, L TB_CRC =24 bits. TBS+L TB_CRC But, K cb If not, the number of code blocks is 1 and L CB_CRC No additional CRC sequence of 24 bits is added to the code block. Otherwise, the total number of code blocks is C=ceil((TBS+L TB_CRC ) / (K cb -L CB_CRC The total number of bits in each code block is determined by K'=(TBS+L TB_CRC +C×L CB_CRC ) / C. [Table 1] 2) Check matrix generation: The check matrix is ​​determined by the basis graph and lifting size (Zc). The number of columns used to encode the system information bits is K for BG1. b = 22Zc, and for BG2, K b = 10Zc. The lifting size is Zc ≧ K' / K b The base graph matrix H BG is the set index i of Zc LS and a table of elements of each base graph corresponding to the set index as shown in Table 3 and Table 4. The base graph matrix H BGAfter obtaining the values ​​of and Zc, the check matrix H is transformed into H BG is obtained by replacing each element of with a Zc × Zc matrix. H BG Each element in with value 0 is replaced by an all-zero matrix of size Zc by Zc. H BG Each element of value 1 in is a cyclic permutation matrix I(P i,j ), where i and j are the row and column indices of the element, and I(P i,j ) is a unit matrix I of size Zc × Zc to the right P i,j It is obtained by cyclic shifting P i,j The value of P i,j =mod(V i,j , Zc) is given by V i,j The value of is the set index i LS and the LDPC basis graph is given by a table of elements of the basis graph. For example, basis graph 1 for NR-LDPC is shown in Table 3. 3) Encoding: After completing the above operations, the matrix H is used to encode the information bit sequence of each code block. 4) Rate Matching and Bit Interleaving: After the encoding process, the encoded bit sequence of each code block may be selected and a portion of the encoded bit sequence may be removed to match the code rate shown in Figure 2. To further improve the error correction performance, the bit sequence is interleaved into a new bit sequence after rate matching. The resulting rate-matched bit sequence is applied to modulate and generate the transmission waveform. [Table 2] [Table 3] [Table 4]

[0047] The encoded code block may include system bits and parity bits. The system bits are the original information bits, which are part of the TB. The NR LDPC code is one example of a system code. Parity bit transmission between code blocks based on NR-LDPC

[0048] In some embodiments, the LDPC encoding process utilizes a parity check matrix H and the input bit sequence of each code block to generate a codeword that is orthogonal to H. The LDPC code is a linear block code. For example, the size check matrix H is m×n, and the encoded bit sequences of two code blocks with CBS=l are A=[a1, a2,...,a1], respectively. T and B = [b1, b2, ..., bl] T It is assumed that

[0049] According to the characteristics of the check matrix for LDPC, it can be shown that H×A=0 and H×B=0. Therefore, if A and B are added into C by modulo 2 arithmetic, H×C=0 can be derived by the equation of H×(A+B)=0. Thus, the bit sequence C can be decoded and checked by the matrix H and denoted as an encoded code block. Each bit of C is the sum of the corresponding bits of A and B by modulo 2 arithmetic, so that each bit of C can be used as a parity bit of the corresponding bits of A and B. That is, the bit sequence C can provide A and B, which includes system information bits, with additional soft-decoded information to improve the bit error correction performance of NR-LDPC. In general, multiple code blocks (e.g., CB 1,..., CB N), the generation procedure of C by using an all-ones generation sequence is shown in FIG.

[0050] The conversion relationship between the system code block and the redundancy parity block may be defined as a generating sequence. For example, the generating sequence may be an all-ones sequence. In this case, the redundancy parity block Pr is (CB1+CB2+...+CB N ) modulo 2. In addition, the generated sequence of the inter-code block parity blocks, denoted as redundancy parity block Pr, can also be in other forms than the all-one generated sequence. For example, there may be only some errored code blocks, so that for retransmission, the redundancy parity block can be generated by the errored code blocks, e.g., CB2 and CB3 fail to be received among a total of five code blocks, and the generated sequence should be

[1100] . Thus, the redundancy parity block is obtained by (CB2+CB3).

[0051] However, for the initial transmission, some additional number of bits of each code block may be punctured to match the target rate for the case of supporting redundancy parity block transmission. A redundancy parity bit transmission scheduling method indicated by layer 1 (L1) signaling (e.g., DCI) is described in embodiment example 1. A rate matching method for redundancy parity block transmission is described in embodiment example 2. Higher layer parameters related to redundancy parity block transmission are described in embodiment example 3.

[0052] In the following description, the code block containing TB information bits is denoted as the system code block, and the additional code block obtained by modulo 2 operations within the code block is denoted as the redundancy parity block.

[0053] In some embodiments, a specific RNTI, described below, may be used to scramble the CRC of the DCI and may be associated only with redundancy parity bit transmission.

[0054] It should be noted that the various methods described herein may be used for both UL and DL data transmission procedures.

[0055] For UL data transmission, the UE may first receive downlink control signaling indicating a number of parameters transmitted by a gNodeB (gNB). The parameters may be related to scheduling UL data transmission. The UE may then transmit data to the gNB based on the number of parameters. If the gNB does not receive data transmitted by the UE corresponding to the downlink control signaling, the gNB may transmit another downlink control signaling to schedule the same UL data transmission to the UE.

[0056] For DL ​​data transmission, the UE may first receive downlink control signaling indicating a number of parameters transmitted by the gNB. The parameters may relate to the scheduled DL data transmission. The UE may then receive the data transmitted by the gNB based on the number of parameters and report HARQ-ACK information on whether the DL data is successfully received. Example embodiment 1: Redundancy parity block transmission scheduled by control signaling

[0057] In these embodiments, various redundancy parity block transmission scheduling methods are described. The indication information for scheduling the redundancy parity block transmission may include at least one of the following: 1) an identifier for the redundancy parity block transmission, 2) a number of code blocks associated with the redundancy parity block transmission, 3) a number of code block groups of a transport block, 4) a generating sequence, 5) a rate matching bit pattern, 6) a hybrid automatic repeat request (HARQ) processor number, 7) a redundancy version, 8) a frequency domain resource allocation, 9) a time domain resource allocation, 10) a spatial domain resource allocation, 11) a modulation, or (12) a coding scheme.

[0058] In some embodiments, the modulation and coding scheme may be used to determine the rate, modulation order, and spectral efficiency.

[0059] In some embodiments, a rate matching bit pattern may be used to determine the number of puncturing bits and the puncturing bit locations per code block.

[0060] The indication information can be indicated by control signaling.

[0061] In some embodiments, the control signaling may be PDCCH-based signaling.

[0062] In some embodiments, the control signaling may be radio resource control (RRC) signaling.

[0063] In some embodiments, the PDCCH-based signaling may be DCI, and the indication information may be information decoded by the UE from the received DCI.

[0064] The DCI may include multiple fields, and each field may indicate corresponding indication information. For example, the "identifier for redundancy parity block transmission" field in the DCI represents a field used to indicate information on whether a redundancy parity block is scheduled.

[0065] In some embodiments, the DCI format for scheduling redundancy parity block transmissions may be at least one of the following DCI formats: 1) DCI format 0-1, 2) DCI format 0-2, 3) DCI Format 1-1, or 4)DCI Format 1-2. Example 1-1: L1 signaling indication design Method 1-1-1:

[0066] Information related to redundancy parity block transmission can be indicated by multiple fields in the DCI that can be interpreted differently by legacy user devices as compared to devices implementing the disclosed techniques.

[0067] Two types of fields in the existing (legacy) DCI can be used to schedule redundancy parity block transmissions.

[0068] In some embodiments, the bit information of the first type field can be interpreted as resource information related to redundancy parity block transmission, and the bit information of the second type field can be used to identify whether the DCI indicates redundancy parity block transmission.

[0069] When the UE receives the DCI and the second type field is set to a predetermined state, the first type field may be interpreted as information related to a scheduled redundancy parity block transmission. In some embodiments, the predetermined state may be when all bits of the field are set to "0" or "1".

[0070] If the DCI format is DCI format 0-1 or DCI format 0-2 with CRC scrambled by at least one of the following: 1) C-RNTI, 2) configured scheduling RNTI (CS-RNTI), 3) semi-persistent CSI RNTI (SP-CSI-RNTI), 4) modulation coding scheme cell RNTI (MCS-C-RNTI), or 5) specific RNTI, the first type field may include at least one of the following: 1) Uplink / Complementary Uplink (UL / SUL) indicator; 2) Bandwidth portion indicator; 3) Frequency domain resource allocation; 4) Time domain resource allocation; 5) modulation and coding schemes; 6) New data indicators, 7) Redundancy version, 8) HARQ process number, 9) Transmit power control (TPC) commands for scheduled PUSCH; 10) Precoding information and number of layers; 11) Antenna port, or 12) Demodulation Reference Signal (DMRS) sequence initialization.

[0071] The first type field may also be a first downlink allocation index and a second downlink allocation index of DCI format 0-1.

[0072] The second type of field may include at least one of the following: 1) Uplink Shared Channel (UL-SCH) indicator; 2) CSI request, 3) Frequency domain resource allocation; 4) modulation and coding schemes; 5) New data indicators, or 6) Redundancy version.

[0073] The predetermined state of the second type field may include at least one of the following: 1) An Uplink Shared Channel (UL-SCH) indicator of "0", 2) An all-zero CSI request; 3) either an all-zero frequency domain resource allocation with a resource allocation type, or an all-one frequency domain resource allocation with a resource allocation type; 4) an all-zero modulation and coding scheme; 5) A new data indicator of "0", or 6) All-zero redundancy version.

[0074] For example, a UE may receive DCI formats 0-1 with a CRC scrambled by the C-RNTI, MCS-C-RNTI, or CS-RNTI. If the predefined state of the second type field includes a UL-SCH indicator of '0' and a CSI request of all zeros, all other fields may be used to indicate information related to redundancy parity block transmission.

[0075] For example, a UE may receive DCI formats 0-1 with a CRC scrambled by the SP-CSI-RNTI. If the predefined states of the second type field include 1) a UL-SCH indicator of "0", 2) a CSI request of all zeros, and 3) a frequency domain resource allocation of all zeros with resource allocation type 0 or resource allocation type 2, or a frequency domain resource allocation of all ones with resource allocation type 1 or resource allocation type 2, then all other fields may be used to indicate information related to redundancy parity block transmission.

[0076] If the DCI format is DCI format 1-1 or DCI format 1-2 with a CRC scrambled by at least one of the following: 1) C-RNTI, 2) CS-RNTI, or 3) MCS-C-RNTI, the first type field may include at least one of the following: 1) Bandwidth portion indicator, 2) Frequency domain resource allocation; 3) Time domain resource allocation; 4) a rate matching indicator; 5) modulation and coding schemes; 6) New data indicators, 7) Redundancy version, 8) HARQ process number, 9) Downlink Allocation Index; 10) TPC commands for scheduled PUSCH; 11) PDSCH group index, 12) New feedback indicators, 13) the number of PDSCH groups requested; 14) Antenna port, 15) Code Block Group (CBG) Transmission Information (CBGTI); 16) CBG Flash Out Information (CBGFI), or 17) DMRS sequence initialization.

[0077] The first type of field may also be the modulation and coding scheme, new data indicator, and redundancy version for transport block 2 of DCI format 1-1.

[0078] The second type of field may include at least one of the following: 1) UL-SCH indicator, 2) CSI request, 3) Frequency domain resource allocation; 4) modulation and coding schemes; 5) New data indicators, 6) Redundancy version, or 7) HARQ process number.

[0079] The state of the second type of field may include at least one of the following: 1) UL-SCH indicator of "0", 2) An all-zero CSI request; 3) either an all-zero frequency domain resource allocation with a resource allocation type, or an all-one frequency domain resource allocation with a resource allocation type; 4) an all-zero modulation and coding scheme; 5) New data indicator of "0", 6) An all-zero redundancy version, or 7) HARQ process number of all zeros.

[0080] Using the L1 signaling indication can reduce the overhead of higher layer signaling and enable redundant parity block transmission.

[0081] For example, a UE may receive DCI format 1-1 with a CRC scrambled by the C-RNTI. If the state of the second type field includes 1) a UL-SCH indicator of '0', 2) a CSI request of all zeros, and 3) a frequency domain resource allocation of all zeros with resource allocation type 0 or a frequency domain resource allocation of all ones with resource allocation type 1, then all other fields may be used to indicate information related to redundancy parity block transmission.

[0082] For example, the UE may receive DCI format 1-1 with a CRC scrambled by the CS-RNTI. If the state of the second type field includes 1) a UL-SCH indicator of '0', 2) a CSI request of all zeros, or 3) a frequency domain resource allocation of all zeros with resource allocation type 0 or a frequency domain resource allocation of all ones with resource allocation type 1, then all other fields may be used to indicate information related to redundancy parity block transmission. Method 1-1-2:

[0083] Information related to redundancy parity block transmission can be indicated by a two-level DCI signaling scheme, in which some fields of the legacy DCI will be interpreted differently by embodiments implementing the disclosed techniques as compared to legacy devices.

[0084] In some implementations, the UE receives the DCI with a CRC scrambled by at least one of the following RNTIs: 1) C-RNTI, 2) MCS-C-RNTI, 3) CS-RNTI, 4) SP-CSI-RNIT, or 5) specific RNTI, and only the second type field is available. Different states of the second type field can indicate different redundancy parity bit scheduling types. This DCI can be indicated as a first level DCI.

[0085] After detecting a DCI indicating a second type field with a status indicating verification of a DCI format in which the UE is capable of scheduling a redundancy parity block transmission, the UE may assume that the next received DCI schedules a redundancy parity block transmission. The scheduling DCI in which the UE is capable of scheduling a redundancy parity block transmission may be indicated as a second level DCI.

[0086] If the UE detects a DCI in slot n indicating a second type field with a status indicating the release of the DCI format in which redundancy parity block transmission can be scheduled, the UE may assume that the received DCI after slot n indicates normal data transmission without redundancy parity blocks.

[0087] The scrambled RNTIs for the first and second level DCI may be different.

[0088] For example, FIG. 4 shows a procedure of DCI, from verification of redundancy parity bit scheduling to release of redundancy parity bit scheduling. Method 1-1-3:

[0089] Information related to redundancy parity block transmission may be indicated by one or more fields in the DCI.

[0090] In some embodiments, these fields may be concrete fields, which may be reserved solely for indicating information related to redundancy parity block transmission.

[0091] In some embodiments, the DCI format may be different from the current 15 types of DCI formats defined in NR, and the RNTI may be a specific RNTI that is dedicated for use as described herein. In some embodiments, the specific RNTI may be different from any of the well-known RNTIs, such as RNTIs currently defined in the NR documentation, including at least the C-RNTI, MCS-C-RNTI, CS-RNIT, or SP-CSI-RNTI. In some embodiments, the specific RNTI may relate only to DCIs that schedule redundancy parity bit transmissions.

[0092] In some embodiments, the DCI format may be a new DCI format used only for UEs that support NR Release 16 or later release versions.

[0093] In some embodiments, the DCI format may be at least one of DCI format 0-1, DCI format 0-2, DCI format 1-1, or DCI format 1-2, and the RNTI for scrambling the CRC of the DCI may be a specific RNTI, which may be different from the C-RNTI, MCS-C-RNTI, CS-RNIT, SP-CSI-RNTI, and may be associated with redundancy parity block scheduling.

[0094] In some embodiments, the UE may not expect to receive / transmit a redundancy parity block transmission when a transport block is split into one code block.

[0095] In some embodiments, the UE may not expect to calculate a TBS if a scheduled data transmission, including a redundancy parity block transmission, is a retransmission for a transport block.

[0096] In some embodiments, the UE may be required to calculate the TBS when a scheduled data transmission, including a redundancy parity block transmission, is an initial or first transmission for a transport block.

[0097] For redundancy parity block transmission and initial transmission of a transport block, the UE may assume that a resource allocation is used for both the transport block and redundancy parity block transmissions, and the UE may determine the TBS based on an indication of the resource allocation related to the TBS decision in the DCI. Such implicit understanding by the UE may avoid wasting resources to transmit additional bits of the redundancy parity block.

[0098] For redundancy parity block transmission and initial transmission of a transport block, the UE may assume that the resource allocations used for the transport block and redundancy parity block transmissions are indicated by different fields in the same DCI or by the same field in different DCIs, and the UE may determine the TBS based on the indication of the resource allocation associated with the transport block in the DCI. Such implicit understanding by the UE may provide clear resource allocations for the transport block and redundancy parity block when rate matching bit patterns for the system code block and redundancy parity block are not present, providing better coding gain.

[0099] In some embodiments, for a first transmission, the field related to the redundancy parity block may not be present. In some embodiments, for a retransmission, the field related to the redundancy parity block may be present. Other details

[0100] The redundancy parity block transmission may be transmitted on the PUSCH and the PDSCH.

[0101] In some embodiments, the redundancy parity blocks may be scheduled for transmission within an active UL or DL ​​bandwidth portion (BWP) on a secondary serving cell (SCell).

[0102] In some embodiments, the redundancy parity blocks may be scheduled for transmission within an active UL or DL ​​BWP on a primary serving cell (PCell).

[0103] In some embodiments, the redundancy parity blocks may be scheduled for transmission within an active UL or DL ​​BWP on a cell or cell group if a cell group is configured.

[0104] In some embodiments, the redundancy parity blocks may be scheduled for the case of a carrier aggregation / dual connectivity (CA / DC) configuration.

[0105] In some embodiments, redundancy parity bit scheduling may not be used for the case of a cross-slot scheduling configuration.

[0106] The fields of the DCI used to indicate resource allocation for redundancy parity block transmission may include at least one of the following: 1) frequency domain resource allocation, 2) time domain resource allocation, 3) modulation and coding scheme, 4) new data indicator, 5) redundancy version, 6) HARQ process number, 7) CBG transmission information (CBGTI), or 8) antenna port.

[0107] In some embodiments, the bit width of a resource allocation field in the DCI associated with a redundancy parity block for transmission may not be larger than that of a system code block of a transport block.

[0108] For methods 1-1-1, 1-1-2, and 1-1-3, indication information related to redundancy parity block transmission of a first or second type field in the DCI may be available for the UE when the UE supports redundancy parity block transmission.

[0109] In some embodiments, if the redundancy parity block is scheduled by DCI along with the transport block, the coded redundancy parity block may be concatenated immediately after the coded bits of the transport block. Other details for uplink data transmission

[0110] If the HARQ-ACK bit is transmitted on the PUSCH or PUCCH, an additional bit to indicate the number of erroneous system code blocks of the most recent transmission of the same TB may be transmitted immediately after the existing HARQ-ACK bit. Otherwise, the redundancy parity block transmission may be transmitted based on the reported HARQ-ACK bit, which is a bitmap of each code block group for the same TB.

[0111] If specific higher layer parameters or L1 signaling configures that the UE should receive or transmit redundancy parity blocks, the corresponding reported quantities associated with the redundancy parity blocks can be multiplexed with the HARQ-ACK bits of the same TB. The reported quantities can include the number of erroneous system code blocks, CSI, L1 signal / noise and interference ratio (L1-SINR), or L1 reference signal received power (L1-RSRP). Example 1-2: Generated sequence indication

[0112] The generated sequence may be determined by the number of code blocks and the number of code block groups for the transport block.

[0113] In some embodiments, the generated sequence can be represented as an index into a generated sequence list, which can be configured by higher layer parameters.

[0114] In some embodiments, the generated sequence can be obtained by the index of the code block that is associated with the redundancy parity block.

[0115] In some embodiments, the generated sequence can be configured by higher layer parameters, which may be communicated by radio resource control (RRC) signaling, for example.

[0116] In some embodiments, the higher layer parameters can configure multiple generated sequence lists. The higher layer parameters can select multiple indices of the generated sequence from multiple generated sequences. In this specification, the higher layer parameters are radio resource control signaling, and the higher layer parameters are medium access control (MAC) signaling.

[0117] In some embodiments, the higher layer parameters can configure multiple generated sequence lists, the higher layer parameters can select multiple indices of the generated sequence from multiple generated sequences, and the DCI can indicate one generated sequence among the multiple generated sequences.

[0118] For example, a transport block can be divided into N code blocks. The total number of generated sequences for redundancy parity block transmission is M=A N N -C N 0 -C N 1 It can be. [Table 5]

[0119] In some embodiments, the generating sequence for the redundancy parity block transmission can be associated with a code block group configuration.

[0120] For CBG based transmission, the number of transmitted redundancy parity blocks may be determined by the higher layer parameter maxCodeBlockGroupsPerTransportBlock for PUSCH or the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for PDSCH.

[0121] For example, the total number of code blocks divided by the transport block size can be C=10, and the maximum number of CBGs per transport block, configured by the higher layer parameter maxCodeBlockGroupsPerTransportBlock in PUSCH-ServingCellConfig, can be N=4. Thus, the number of CBGs can be M=min(4,10). The index of the code block of each group can be {

[0012] ,

[0345] ,

[67] ,

[89] }. Thus, the maximum number of redundancy parity blocks for this transport block can be equal to M+1, and the generation sequence of the redundancy code blocks can be shown as in Table 6. [Table 6]

[0122] In one embodiment, for the first transmission, the gNB may transmit a DCI indicating a data transmission, including a redundancy parity block transmission, with an index of the generated sequence as 5.

[0123] In another embodiment, if after the first transmission the gNB receives a bitmap of HARQ-ACK information for a CBG-based PDSCH transmission indicating that at least one of the code blocks of the first CBG and the third CBG is not successfully received, the gNB may transmit a DCI indicating a redundancy parity block transmission with indices of the generated sequence as 1 and 3, respectively.

[0124] In yet another embodiment, if after the first transmission the gNB receives a bitmap of HARQ-ACK information for a CBG-based PDSCH transmission indicating that at least one of the code blocks of each CBG is not successfully received, the gNB may transmit a DCI indicating a redundancy parity block transmission with an index of the generated sequence as 5.

[0125] In some embodiments, if there is more than one redundancy parity block transmission, the generated sequence for the redundancy parity block can be indicated as a bitmap. Each generated sequence indication for a redundancy parity block can have the same bit width. Example 2: Rate-matching bit pattern for redundancy parity block transmission

[0126] In these embodiments, a method for determining a rate-matching bit pattern for redundancy parity block transmission is described.

[0127] In some embodiments, the rate matching bit pattern is determined by the following predetermined function or procedure.

[0128] In some embodiments, the rate matching bit pattern is configured by higher layer parameters, for example through RRC signaling or MAC signaling.

[0129] In some embodiments, the rate matching bit pattern can be used to indicate the number of puncturing bits and the corresponding puncturing bit locations of a code block for data transmission, including redundancy parity blocks.

[0130] The indication of the rate matching bit pattern can be used to determine the number of puncturing bits and the puncturing bit locations of a code block for data transmission, including a number of scheduled redundancy parity bits.

[0131] In some embodiments, the rate matching bit pattern for the redundancy parity block transmission may be determined by at least one of the following factors for the transport block: 1) the total number of transmitted bits in each system code block; 2) The number of code blocks in the transport block; 3) the system code block size, or 4) Lifting size (Zc) value.

[0132] In some embodiments, the rate matching bit pattern for the redundancy parity block transmission may be determined by at least one of the following parameters for the transport block: 1) Transport block size, 2) The number of code blocks associated with one redundancy parity block, or 3) Lifting size (Zc) value.

[0133] These parameters may be indicated or determined by the DCI that schedules the redundancy parity bit transmission.

[0134] In this embodiment, the puncturing bit locations for multiple code blocks cannot be overlapped, and the puncturing bit locations for other multiple code blocks can be overlapped. A code block may represent the total number of code blocks for scheduled redundancy parity block transmission.

[0135] For the first transmission, the number of puncturing bits per code block may be determined by the number of transmitted bits of the number of code blocks, which may be equal to the number of scheduled redundancy parity blocks.

[0136] For the first transmission, the UE may not request puncturing of additional bits for each code block if certain conditions are met, such as at least one of the following events: 1) The code rate is within the value range, 2) TBS is within the value range; 3) The modulation order is within the value range, or 4) The scheduled data transmission is a retransmission for a transport block.

[0137] In some embodiments, the value range of the code rate may be within the range of 1 / 4 to 5 / 6. In some embodiments, the value range of the TBS may be within the range of 3840 to 10 6 In some embodiments, the value range of the modulation order may be included in the range of 2 to 6. Embodiment 2-1: Puncturing bit locations are not overlapped among code blocks of different groups

[0138] When a redundancy parity block is transmitted along with its corresponding system code block, additional puncturing may be required for every code block that contains a redundancy parity block in order to accommodate the channel capacity. This additional puncturing can usually be computed after conventional rate matching, as described in the previous section. The calculation of the number of punctured bits per code block is described herein.

[0139] In some embodiments, the elements of the vector Punct_set may represent the number of punctured bits for multiple system code blocks for a TB. [ka] where L is the bit length of each code block after NR-LDPC rate matching, N is the number of code blocks used to generate the redundancy parity block, and Zc is the lifting size.

[0140] All code blocks including redundancy parity blocks can be divided into several groups. For code blocks in each group, the punctured bit locations can be the same. For code blocks in different groups, the punctured bit locations can be different. In some embodiments, code blocks including redundancy parity blocks can be divided into M groups, where M is an integer equal to or greater than 1. In some embodiments, the additional punctured bits of each code block in a group can be located at the end of the code block after LDPC rate matching. In some embodiments, the additional punctured bits of each code block in a group can be located at the beginning of each code block after NR-LDPC rate matching.

[0141] For example, there may be 10 code blocks (e.g., CB0, CB1, ..., CB9) including redundancy parity blocks for TB. The 10 code blocks may be divided into one group. The bit sequence of each code block may be the code block after LDPC rate matching. That is, the location of the punctured bits in all of the code blocks may be the same. For example, the punctured bits may be located at the end or beginning of each code block, as shown in Figures 5A and 5B, respectively.

[0142] In some embodiments, the punctured bit locations in the code blocks within a group may be identical.

[0143] For example, there may be 10 code blocks (e.g., CB0, CB1, ..., CB9) including redundancy parity blocks for TB. As shown in FIG. 6, the 10 code blocks may be divided into two groups, with each group including 5 code blocks. In the first group, the indices of the code blocks may be {0, 2, ..., 8}. In the second group, the indices of the code blocks may be {1, 3, ..., 9}. The punctured bits of each code block in the first group may be punctured from the end of each code block after rate matching, and the punctured bits of each code block in the second group may be punctured from the beginning of each code block after rate matching.

[0144] In some embodiments, the punctured bit locations among code blocks in different groups may be non-overlapping.

[0145] For example, there may be 10 code blocks (e.g., CB0, CB1, ..., CB9) that include redundancy parity blocks for TB. The 10 code blocks may be divided into 10 groups. The punctured bit locations in all of the code blocks may be non-overlapping.

[0146] The punctured bit locations of the first code block may be punctured from the end or the beginning of the first code block after rate matching, as shown in FIGS. 7A and 7B, respectively.

[0147] For other code blocks, the punctured bit locations may be immediately adjacent to the punctured bit locations of the previous code block.

[0148] In some embodiments, the punctured bit locations among code blocks in different groups may be non-overlapping.

[0149] In some embodiments, the additional punctured bit locations of the system code block cannot overlap with those of the punctured 2×Zc bits located at the beginning of each code block after LDPC rate matching for transmission with redundancy parity blocks.

[0150] In some embodiments, the additional punctured bit locations of the redundancy parity block cannot overlap with those of the punctured 2×Zc bits located at the beginning of each code block after LDPC rate matching for transmission involving the redundancy parity block.

[0151] In some embodiments, the additional punctured bit locations of the system code block and the redundancy parity block cannot overlap with those of the punctured 2×Zc bits located at the beginning of each code block after LDPC rate matching for transmission involving the redundancy parity block. Embodiment 2-2: Fixed total puncturing number of bits in specific bit locations for code blocks other than redundancy parity blocks

[0152] In this embodiment, the total number of punctured bits (Ls) and the punctured bit locations for all system code blocks of a TB can be determined in advance. According to the determination of the total number of punctured bits for all system code blocks, the number of punctured bits for a redundancy parity block can be obtained by (L-Ls), where L represents the length of the code block after LDPC rate matching.

[0153] All Ls of the system code block and the punctured bit locations are associated with the redundancy parity block, and are expressed as the column index (S p ), lifting size (Zc), lifting size set index (i LS ), and / or the number of system code blocks (C s ) can be predefined.

[0154] The column index (S p ) is the rate R allocated by the DCI, the system code block size (CBS), and the number of system code blocks (C s ), and / or S p The threshold thr1 representing the number of elements in a column can be determined.

[0155] Sp The elements in can be the index of the column with the number of elements in the selected basis graph that are greater than the threshold thr1.

[0156] The total number of punctured bits (Ls) is a multiple of the lifting size (Zc) and the number of system code blocks (C s ) and S p The total number of elements in (N e ).

[0157] Column indexes 1 and 2 are p cannot be contained within

[0158] In some embodiments, S p The column indexes in may be sorted in order from largest to smallest column index.

[0159] For example, for the ground graph 1 shown in Fig. 8, S p contains at least one of the elements in the set {4, 5, 8, 11, 12, 13, 14, 15, 17, 18, 19, 22, 23}. p may contain at least one of the elements in the set {3, 6, 8, 11, 12, 13, 14}.

[0160] In some embodiments, the punctured sequence is S p The first min(C s , N e ) element indices.

[0161] In some embodiments, the punctured sequence is S p The last min(C s , N e ) element indices.

[0162] In another embodiment, S pThe column indices in can be sorted in order of the number of elements in each column from largest to smallest.

[0163] For example, for ground graph 1, S p contains at least one of the elements in the set {19, 23, 13, 11, 8, 22, 14, 4, 18, 17, 15, 12, 5}. p may contain at least one of the elements in the set {12, 6, 8, 14, 3, 13, 11}.

[0164] Cr may be the number of redundant parity blocks. Cr may not be greater than the value of floor(Cs / 2).

[0165] For example, for base graph 1, R=2 / 3, Cs=10, Cr=1, Q m = 2, L = 12300, and Zc = 384. The elements of base graph 1 are shown in Figure 8. The black dots represent the elements of base graph 1 that correspond to concrete integers.

[0166] Except for the first two columns, if thr1 is equal to 8, the punctured column index (S p ) can be {4, 5, 8, 11, 12, 13, 14, 15, 17, 18, 19, 22, 23}. S p The total number of elements in is N, excluding indexes 1 and 2. e = 13. Each column index in a given set can represent a corresponding Zc punctured bit location. The total number of punctured bits is Zc × min(Cs, N e ) = 384 × 10 = 3840. The puncturing column index can be S as {4, 5, 7, 8, 9, 11, 12, 13, 14, 15}. p The puncturing patterns for all system code blocks are shown in FIG.

[0167] For base graph 2, R=1 / 4, Cs=5, Cr=1, Q m = 2, L = 14784, and Zc = 384. Except for the first two columns, if thr1 is equal to 8, the punctured column index (S p ) can be {3,6,8,11,12,13,14}. S p The total number of elements in is N, excluding indexes 1 and 2. e = 7. Each column index in a given set can represent a corresponding Zc punctured bit location. The total number of punctured bits is Zc × min(Cr, N e ) = 384 × 5 = 1920. The puncturing column index can be S as {3, 6, 8, 11, 12}. p The punctured bit locations for all system code blocks are shown in FIG.

[0168] When a redundancy parity block is transmitted along with its corresponding system code block, the total additional number of punctured bits for all of the code blocks, including the redundancy parity block, can be equal to the length of the redundancy parity block after the LDPC rate matching operation.

[0169] thr1 can be an integer equal to or greater than 8. The number of punctured bits in each code block other than the redundancy parity block cannot be greater than Zc. The number of punctured bits in each code block other than the redundancy parity block cannot be greater than that of the redundancy parity block. The total number of punctured bits in all system code blocks cannot be greater than Cs × Zc.

[0170] In some embodiments, the puncturing pattern for each system code block may reuse the puncturing method as disclosed in embodiment 1.

[0171] In some embodiments, for a TB, the punctured bit locations in all of its code blocks may be different and / or non-overlapping.

[0172] A first method for calculating the number of punctured bits per code block is shown as follows. [ka] However, Lw is α w × Zc, where α w is the number of elements > H BG where L is the number of columns with thr1 in LDPC rate matching, L is the bit length of each code block after LDPC rate matching, N is the number of code blocks used to generate the redundancy parity block, and Zc is the lifting size.

[0173] A second method for calculating the number of punctured bits per code block is shown as follows. [ka] However, Lw is α w × Zc, where α w Column weight > H BG where L is the number of columns with w in , L is the bit length of each code block after NR-LDPC rate matching, N is the number of code blocks used to generate the redundancy parity block, and Zc is the lifting size.

[0174] For example, there may be 10 code blocks, including the redundant parity block for TB (i.e., C s =9, C r= 1), the code rate can be 2 / 3, the lifting size Zc can be 320, and the number of bits in each code block after LDPC rate matching can be 9804. Assuming thr1 = 10, S p The column indexes in may be {4, 8, 11, 13, 14, 19, 22, 23}. Then, for the system code block, the punctured bits may be {284, 284, 284, 284, 284, 285, 285, 285, 285} based on the second method of calculating the number of punctured bits. For the redundancy parity block, the punctured bits may be 7244. The punctured bit locations for each code block may be punctured from the beginning or end of the code block, as shown in Figures 11A and 11B, respectively. Embodiment 2-3: No additional punctured bits for all of the system code blocks of TB for redundancy parity block transmission

[0175] In this embodiment, there may be no additional punctured bits for the system code block and the associated redundancy parity block. The number of transmitted bits of the redundancy parity block may be equal to or smaller than the number of bits of the system code block after LDPC rate matching. Therefore, the target code rate R for TB with additional redundancy parity block transmission may be reduced.

[0176] For example, if a redundancy parity block with the same size as the system code block is transmitted, the rate for TB is R×C s / (C s +C r ), except that C s is the number of system code blocks, C r is the number of redundant parity blocks.

[0177] The redundancy parity block transmission can be triggered by certain conditions.

[0178] The number of transmitted bits of the redundancy parity block can be determined by a set of parameters.

[0179] For transmission, the predefined conditions are: 1) the HARQ process number indicated by the DCI is not less than or equal to a threshold h1; 2) the redundancy version indicated by the DCI is greater than or equal to a threshold h2; 3) the scheduling DCI format, such as DCI format 0-1 / 1-1 and / or DCI format 0-2 / 1-2; 4) the code rate R of the TB indicated by the DCI is not less than h3; 5) the modulation order Q of the TB indicated by the DCI. m 1) the number of system code blocks for TB is not less than h4, 2) the number of system code blocks for TB is not less than h5 or the number of system code blocks for TBS is not greater than h8, 3) the number of system code blocks for TB is not less than h6 or the number of system code blocks for TBS is not greater than h9, 4) the number of system code blocks for TB is not less than h10 or the number of system code blocks for TBS is not greater than h10, 5) the number of system code blocks for TB is not less than h20 or the number of system code blocks for TBS is not greater than h3, 6) the associated feedback parameters include a number of error code blocks received by the UE for the most recent transmission that is not greater than a threshold h4, or 7) reported quantities related to channel conditions or beam measurements, such as a CSI-RS resource indicator (CRI), a channel quality indicator (CQI), an RSRP, and an SINR, are not less than a threshold h5.

[0180] The relevant feedback parameters may be configured by higher layer parameters and reported by the UE.

[0181] For example, a redundant parity block for a TB (e.g., C s There may be 9 code blocks, including h5=5 (=9), where h5=5 is greater than 5. The code rate may be 2 / 3, which is greater than h3=1 / 3, the lifting size Zc may be 320, and the number of bits in each code block after LDPC rate matching may be 9804.

[0182] If there is a first or initial transmission, the redundancy parity block cannot be transmitted for the next transmission of the TB. The transmitted bits of the redundancy parity block can be zero.

[0183] For retransmission, if the number of error code blocks received by the UE for TB is not greater than h6=9, the redundancy parity block may be transmitted for the next transmission of TB. The number of transmitted bits of the redundancy parity block may be 9804.

[0184] In another embodiment, a redundant parity block for TB (e.g., C s There may be 9 code blocks, including h5=5 (=9), where h5=5 is greater than 5. The code rate may be 2 / 3, which is greater than h3=1 / 3, the lifting size Zc may be 320, and the number of bits in each code block after LDPC rate matching may be 9804.

[0185] If there is a first or initial transmission, the redundancy parity block may be transmitted for the next transmission of the TB. The transmitted bits of the redundancy parity block may be 9804.

[0186] For the first retransmission, if the number of error code blocks received by the UE of TB is not greater than h6=10, the redundancy parity block may be transmitted for the next transmission of TB. The number of transmitted bits of the redundancy parity block may be 9804.

[0187] For another retransmission, if the number of error code blocks received by the UE for TB is not greater than h6=9, the redundancy parity block may be transmitted for the next transmission of TB. The number of transmitted bits of the redundancy parity block may be 9804.

[0188] The set of parameters can include or be determined by at least one of the following: 1) the number of information bits in each system code block (CBS); 2) the number of bits in each system code block; 3) the number of system code blocks; 4) the redundancy version and its corresponding start position for LDPC coding in Release 16; 5) the redundancy version and new corresponding start position for redundancy parity blocks only; or 6) a predefined set of scaling factors.

[0189] The predetermined set of scaling factors used to modify the number of transmitted bits of the redundancy parity block may be determined by the number of system code blocks, the rate of the TB without the redundancy parity block, the modulation order, and / or a set of thresholds for predetermined conditions.

[0190] The maximum value of an element in a given set of scaling factors cannot be greater than one.

[0191] The minimum value of any element in a given set of scaling factors cannot be less than zero.

[0192] The number of elements in the predetermined set of scaling coefficients cannot be greater than 6. The elements in the predetermined set of scaling coefficients cannot be less than 0 and greater than 1. For example, the predetermined set of scaling coefficients may include at least one of the following values: {0, 1 / 4, 1 / 3, 2 / 3, 4 / 5, 1}. For example, the predetermined set of scaling coefficients may include at least one of the following values: {0, 1 / 4, 1 / 2, 3 / 4, 1}.

[0193] In some embodiments, the available values ​​of the predetermined set of scaling factors may be at least one of the following: [0.125, 0.25, 0.375, 0.5, 0.625, 0.75, 0.875, 1].

[0194] In some embodiments, the product of the length of each encoded code block and the scaling factor may be an integer.

[0195] In some embodiments, the scaling factor may be determined by information indicated by L1 signaling or higher layer signaling. In some embodiments, the scaling factor may be reported by the UE.

[0196] For example, a redundant parity block for a TB (e.g., C s There can be nine code blocks greater than h5=5, including h5=1 / 3 (=9). The code rate can be 2 / 3, which is greater than h3=1 / 3, and the modulation order Q m may be 2, the lifting size Zc may be 320, and the number of bits in each code block after LDPC rate matching may be 9804. The set of scaling coefficients may be {1 / 2, 1, 1, 1}.

[0197] If there is a first or initial transmission, the redundancy parity block may be transmitted for the next transmission of the TB. The transmitted bits of the redundancy parity block are func(func(9804×1 / 2) / Q m )×Q m where func() represents rounding down, rounding up, or rounding.

[0198] For retransmission, if the number of error code blocks received by the UE for TB is not greater than h6=9, the redundancy parity block may be transmitted for the next transmission of TB. The number of transmitted bits of the redundancy parity block may be 9804.

[0199] In some embodiments, the redundant parity block transmission may be determined by a combination of a set of predetermined conditions and parameters.

[0200] In some embodiments, h3 cannot be greater than 2 / 3. In some embodiments, h4 cannot be greater than 4. In some embodiments, h5 cannot be greater than 10. In some embodiments, h8 cannot be greater than 38240 bits for BG2 and 84240 bits for BG1. In some embodiments, h6 cannot be less than the number of system code blocks associated with the redundancy parity block minus 1.

[0201] In some embodiments, C2 cannot be less than 35. In some embodiments, h3 cannot be less than 0.95. In some embodiments, h4 cannot be less than 8. In some embodiments, h8 cannot be less than 1 million bits for BG2 and 10 million bits for BG1.

[0202] In the above description, a system code block may be a code block associated with a redundancy parity block to be transmitted. In some embodiments, the total code blocks of a TB may be divided into more than one code block group (CBG) based on a CBG-based PDSCH transmission. In some embodiments, there may be only one redundancy parity block associated with all the code blocks in all of the groups. In some embodiments, there may be more than one redundancy parity block, and each redundancy parity block may be associated with all the code blocks in a corresponding code block group. The number of redundancy parity blocks may be equal to or less than the number of code block groups. Embodiment 2-4: Redundancy parity blocks used for retransmission

[0203] In some embodiments, a redundancy parity block may be used for the first transmission, and the additional puncturing method is described in embodiment 2-1 and embodiment 2-2 above.

[0204] In some embodiments, the redundancy parity block can be used for specific transmission of the TB if the redefined condition is satisfied, and the transmission method is described in embodiment 2-3 above.

[0205] As described in embodiments 2-4 of the present specification, for retransmission, the redundancy parity block can also be used to reduce the total resource requirement. For example, the number of resource elements used by all of the transmissions for the UE to successfully receive the TB can be reduced by the redundancy parity block transmission by reducing either the amount of scheduling resources for each transmission or the total number of transmissions required.

[0206] The redundancy parity block may be transmitted based on a predetermined event. The predetermined event for transmission may be at least one of the following: 1) The number of erroneous system code blocks not successfully received by the UE is less than or equal to a threshold; 2) The number of code block groups, which contain code blocks that are not successfully received by the UE for CBG-based transmission, is less than or equal to a threshold value; 3) the value of the current time of transmissions for the same TB, counted from the first or initial transmission, is less than or equal to a threshold value and greater than another threshold value; 4) The SINR value reported before or after the most recent transmission of the TB is less than or equal to a threshold and greater than another threshold; 5) Reported quantities defined in Release 16 from the most recent CSI / synchronization signal block (CSI / SSB) measurement; 6) The bit error rate (BER) or block error rate (BLER) assessed by the UE is greater than the target BLER or greater than the target BLER × 0.01; 7) The average absolute value of the likelihood log ratio (LLR) of each error code block, 8) A reported quantity related to the Likelihood Log-Ratio (LLR) of a transmitted bit that is new for Release 16; 9) BER of the most recent transmitted redundant parity block of the TB; 10) The most recent transmitted redundancy parity block of the TB is not received correctly. 11) The reduced number of error system code blocks after receiving the most recently transmitted redundancy parity block of the TB is greater than a threshold value; 12) The rate R of the system code block of TB is greater than a threshold. 13) The number of system code blocks in TB is greater than a threshold, or 14) The number of erroneous system code blocks in recent transmissions is less than a threshold.

[0207] An errored code block may refer to a code block that does not pass a code block (CB) CRC check or is not received correctly.

[0208] An errored code block may refer to a code block that does not pass a transport block (TB) CRC check or is not received correctly.

[0209] The BER can represent the bit error rate of the TB. The BER can also represent the number of erroneous information bits divided by the total number of transmitted bits. The BLER can represent the block error rate of the TB. The BLER can also represent the number of erroneous code blocks divided by the total number of code blocks of the TB.

[0210] For example, when the UE or gNB meets an event in which the number of system code blocks reported by the UE that are not successfully received by the UE is less than or equal to a threshold, the UE or gNB may assume that a redundancy parity block may be transmitted. Various specific applications of this event definition may be as follows: 1) For the first retransmission, ie the second transmission, the event applies such that the number of erroneous code blocks in the first or initial transmission is not less than Ce1. 2) For the second retransmission, ie the third transmission, the event applies such that the number of erroneous code blocks in the second transmission is not less than Ce2. 3) For the third retransmission, ie, the fourth transmission, the event applies such that the number of errored code blocks in the third transmission is not less than Ce3.

[0211] In some embodiments, Ce1 can be an integer not less than the value of floor(C×0.9). In some embodiments, Ce2 can be an integer not greater than the value of floor(C×0.9). In some embodiments, Ce3 can be an integer not greater than the value of floor(C×0.9).

[0212] For other subsequent retransmissions of a TB, the conditions that trigger a redundancy parity block transmission may be similar to the previous transmission of the same TB.

[0213] In some embodiments, the number of error blocks of the TB for the current transmission may be reported by the UE. In some embodiments, the number of error blocks of the TB for the current transmission reported by the UE may be transmitted in the PUCCH. In some embodiments, the number of error blocks of the TB for the current transmission reported by the UE may be transmitted in the PUSCH. In some embodiments, the number of error blocks of the TB for the current transmission may be multiplexed.

[0214] In some embodiments, the redundancy parity block may be used for the first retransmission or the second transmission if the most recent SINR reported or measured by the UE is not less than S1.

[0215] In some embodiments, the redundancy parity block may be used for the second retransmission or the third transmission if the most recent SINR reported or measured by the UE is not less than S2.

[0216] In some embodiments, the redundancy parity block may be used for the third retransmission or the fourth transmission if the most recent SINR reported or measured by the UE is not less than S3.

[0217] In some embodiments, S1 can be the SNR at the target BLER=10% for the MCS of the initial transmission plus Δ1. In some embodiments, S2 can be the SNR at the target BLER=10% for the MCS of the initial transmission plus Δ2. In some embodiments, S3 can be the SNR at the target BLER=10% for the MCS of the initial transmission plus Δ3.

[0218] In some embodiments, the values ​​of Δ1, Δ2, and Δ3 may be configured by higher layer parameters.

[0219] In some embodiments, the values ​​of Δ1, Δ2, and Δ3 can be at least one of the following: [3, 6, 9, 12] dB.

[0220] In some embodiments, the values ​​of Δ1, Δ2, and Δ3 can be different from one another. Embodiment 3: Higher layer parameters related to redundancy parity block transmission

[0221] The higher layer parameters related to redundancy parity block transmission may include two types: 1) related UE features or capabilities reported by the UE; and 2) higher layer parameters related to resource configuration for redundancy parity block transmission.

[0222] As described herein, UE features associated with redundancy parity block transmission are disclosed.

[0223] The UE characteristics may include at least one of the following: 1) Features for determining the number of transmitted redundancy parity blocks for a TB; 2) features for determining HARQ-ACK information associated with a redundancy parity block; 3) Features for determining that the UE is capable of processing redundancy parity block transmissions; 4) A feature for determining the size of the redundancy parity block to be transmitted, or 5) A feature for determining the frequency domain resources used to transmit the redundancy parity blocks.

[0224] The higher layer parameters related to the resource configuration for redundancy parity block transmission may include at least one of the following: 1) enable redundant parity block transmission for TB; 2) a generated sequence candidate list or decision procedure; 3) A specific resource configuration for redundant parity block transmission; or 4) A search space set and CORESET configuration used to monitor the PDCCH for scheduling redundancy parity block transmissions.

[0225] In some embodiments, higher layer parameters related to resource configuration for redundancy parity block transmission may be included within radio resource control (RRC) signaling.

[0226] In the above description, TBS may represent the total number of information bits that are transmitted within the resources allocated by the DCI or higher layer parameters.

[0227] In some embodiments, a transport block (TB) can be transmitted over a normal cyclic prefix (CP) within 14 consecutive symbol durations, or over an extended cyclic prefix, ending with the last symbol of the most recent PDSCH transmission within an active BWP on the serving cell, within 12 consecutive symbol durations.

[0228] In some embodiments, the allocated resources may be contiguous in the time and frequency domains.

[0229] In the above description, each encoded code block of the TB may include an information bit portion and a parity bit portion. In some embodiments, each code block carrying the information bits of the TB may be a system code block. In some embodiments, the encoder may be named a system encoder.

[0230] Some embodiments may preferably incorporate the following solutions as described herein.

[0231] 1. A method (e.g., method 1200 shown in FIG. 12) implemented by a wireless device, comprising: receiving, by the wireless device, a first message from a network device, the first message having one or more parameters related to error correction coding (1210); and transmitting, by the wireless device, a data transmission to the network device using the error correction coding and in accordance with the one or more parameters (1220).

[0232] 2. A method implemented by a wireless device (e.g., method 1300 shown in FIG. 13), comprising transmitting, by the network device, a first message to the wireless device, the first message comprising one or more parameters related to error correction coding (1310), and, after transmission of the first message, transmitting, by the network device, a data transmission to the wireless device using the error correction coding and in accordance with the one or more parameters (1320).

[0233] 3. A method implemented by a wireless device (e.g., method 1400 shown in FIG. 14), comprising: receiving, by the wireless device, a first message from a network device, the first message having one or more parameters related to error correction coding (1410); and receiving, by the wireless device, a data transmission from the network device using the error correction coding and in accordance with the one or more parameters (1420).

[0234] 4. A method implemented by a wireless device (e.g., method 1500 shown in FIG. 15), comprising transmitting, by the network device, a first message to the wireless device, the first message comprising one or more parameters related to error correction coding (1510), and receiving, after transmission of the first message, by the network device from the wireless device, a data transmission using the error correction coding and in accordance with the one or more parameters (1520).

[0235] A wireless communication method (e.g., method 1600 shown in FIG. 16 ), comprising: generating, by a first wireless device, a plurality of code blocks including at least one redundancy parity block from data bits to be transmitted (1610); partitioning the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to allowed puncturing bit locations (1620); rate matching the code blocks according to the allowed puncturing bit locations by puncturing (1630); and transmitting a result of the rate matching to a second wireless device (1640).

[0236] 6. A wireless communication method (e.g., method 1700 shown in FIG. 17), comprising: receiving, by a first wireless device, a data transmission comprising rate-matched data (1740), the rate-matched data being generated by partitioning a plurality of code blocks, including at least one redundancy parity block, into a first group of code blocks and a second group of code blocks in accordance with allowed puncturing locations, and puncturing the first and second groups of code blocks in accordance with the allowed puncturing locations; and determining from the data transmission data bits encoded within the data transmission (1720).

[0237] 7. A wireless communication method (e.g., method 1800 shown in FIG. 18), comprising: generating, by a first wireless device, a plurality of code blocks including at least one redundancy parity block from data bits to be transmitted (1810); dividing the plurality of code blocks into at least a first group of code blocks and a second group of code blocks according to permitted puncturing locations (1820); rate matching the plurality of code blocks by puncturing according to a puncturing pattern (1830), where the puncturing pattern defines locations of bits permitted to be punctured for each code block in the plurality of code blocks; and transmitting a result of the rate matching to a second wireless device (1840).

[0238] 8. A wireless communication method (e.g., method 1900 shown in FIG. 19), comprising: receiving, by a first wireless device, a data transmission comprising a plurality of code blocks including at least one redundancy parity block (1910), wherein the plurality of code blocks are rate matched according to a puncturing pattern that defines locations of bits allowed to be punctured for each code block in the plurality of code blocks; and determining data bits encoded in the data transmission based on the puncturing pattern (1920).

[0239] 9. A method according to any of Solutions 1-4, wherein the first message is radio resource control (RRC) signaling, and the parameters of the first message are related to redundancy parity block transmission.

[0240] 10. The method according to any of Solutions 1-4 or 9, wherein the first message is transmitted as downlink control information (DCI) having a predefined format type.

[0241] 11. The method according to any of solutions 1-4, 9 or 10, wherein the data transmission includes a redundancy parity block transmission.

[0242] 12. A method according to any of solutions 1-4 or 9-11, wherein the redundancy parity block included in the data transmission does not include information bits of the transport block and is obtained by at least a plurality of code blocks of the transport block and a generation sequence.

[0243] 13. The method of any of Solutions 1-4 or 9-12, wherein a cyclic redundancy check (CRC) of the first message is scrambled by a specific radio network identifier (RNTI).

[0244] 14. DCI will consider the following parameters, namely:

[0245] an identifier for redundancy parity block transmission;

[0246] the number of code blocks associated with the redundancy parity block transmission;

[0247] Generating sequences for redundancy parity block transmission,

[0248] Number of redundant parity blocks,

[0249] the index of the code block associated with the redundancy parity block;

[0250] Rate matching bit pattern,

[0251] HARQ processor number, or

[0252] A bitmap of the code block group, a plurality of fields configurable to indicate at least one of:

[0253] The generation sequence is used to generate the redundancy parity blocks,

[0254] The rate matching bit pattern is used to determine puncturing bit locations of a plurality of code blocks for data transmission; The method described in any of solutions 1-12.

[0255] 15. The method according to solution 14, wherein the generating sequence is determinable from at least one of a number of multiple code blocks associated with the redundancy parity block and a number of code block groups for the transport block.

[0256] 16. The method according to solution 14, wherein the rate matching bit pattern includes a number of puncturing bits or corresponding puncturing bit locations of a plurality of code blocks for data transmission.

[0257] 17. The method of any of Solutions 1-12 or 14, wherein one or more fields in the DCI are configured in accordance with higher layer parameters that configure a redundancy parity block transmission.

[0258] 18. A method according to any of Solutions 1-12 or 14, wherein one or more fields in the DCI are configured based on higher layer parameters reported by the wireless device indicating that the wireless device is capable of performing redundancy parity block transmission.

[0259] 19. The method according to solution 14, where the generating sequence is denoted as an index into the list from which the generating sequence originates.

[0260] 20. The method of solution 19, in which the generated sequence is derived from a list constructed by certain higher layer parameters.

[0261] 21. The method according to solution 14, wherein the number of multiple code blocks associated with the redundancy parity block is indicated as a bitmap of the total number of multiple code blocks in the transport block.

[0262] 22. The method according to solution 14, wherein the bit width of the redundancy version is less than 2.

[0263] 23. The DCI format is as follows:

[0264] DCI Format 0-1,

[0265] DCI format 1-1,

[0266] DCI formats 0-2,

[0267] DCI Format 1-2, or

[0268] Specifically DCI format, The method according to any of Solutions 1-12 or 14, wherein the method is at least one of:

[0269] 24. A method according to any of Solutions 14 or 23, wherein at least one of the first type fields in DCI Format 0-1, DCI Format 1-1, DCI Format 0-2, DCI Format 1-2, or a specific DCI format, is interpreted as indicating information related to redundancy parity block transmission if at least one of the second type fields of the DCI is set to a predetermined value.

[0270] 25. The first type of field is the following, namely:

[0271] Career indicators,

[0272] Bandwidth fraction indicator,

[0273] Frequency domain resource allocation;

[0274] Time domain resource allocation,

[0275] Rate matching indicator,

[0276] HARQ process number,

[0277] Downlink Allocation Index,

[0278] Antenna port,

[0279] A first downlink allocation index;

[0280] A second downlink allocation index for DCI formats 0-1;

[0281] ChannelAccess-CPext for DCI format 0-1 or DCI format 1-1,

[0282] Transmission configuration indication,

[0283] CBG Transmission Information (CBGTI),

[0284] CBG Flash Out Information (CBGFI) in DCI format 1-1,

[0285] Modulation and coding schemes,

[0286] New data indicators, or

[0287] Redundancy version for transport block 1 of DCI format 1-1, The method according to Solution 24, comprising at least one of the following:

[0288] 26. A second type of field in DCI format 0-1, DCI format 1-1, DCI format 0-2, DCI format 1-2, or a specific DCI format, is as follows:

[0289] Frequency domain resource allocation;

[0290] Redundancy version,

[0291] UL-SCH indicator,

[0292] CSI request,

[0293] Modulation and coding schemes,

[0294] New data indicators,

[0295] Redundancy version,

[0296] Modulation and coding scheme for transport block 2 in DCI format 1-1,

[0297] A new data indicator for transport block 2 in DCI format 1-1, or

[0298] Redundancy version for transport block 2 in DCI format 1-1, The method according to Solution 24, comprising at least one of the following:

[0299] 27. The method according to any of Solutions 24 or 26, wherein the second type field is used to identify the transmission type of the redundancy parity block transmission.

[0300] 28. The transmission types for redundancy parity block transmission are as follows:

[0301] The number of scheduled redundancy parity blocks, or

[0302] the time of scheduled data transmission of the transport block; 28. The method according to solution 27, wherein the method is determined by at least one of the following:

[0303] 29. The method according to solution 14, wherein the number of puncturing bits for each of the plurality of code blocks for the transport block is less than or equal to the number of puncturing bits for the redundancy parity block.

[0304] 30. The redundancy parity blocks included in the data transmission are reported by the wireless device within a range of values, the following quantities:

[0305] the number of code blocks in the transport block;

[0306] a number of code blocks of a transport block that are not successfully received by the wireless device;

[0307] the maximum number of transmissions for a transport block, or

[0308] The most recent L1-SINR value reported by the wireless device, The method according to any one of Solutions 1-12 or 14, wherein the scheduling is based on at least one of the following:

[0309] 31. The method according to solution 30, wherein the value range is configured by a higher layer parameter.

[0310] 32. A method according to any one of Solutions 14 or 23, wherein when there is an initial transmission of a transport block, the multiple fields related to the redundancy parity code block are not included in the DCI format, and when there is a retransmission of the transport block, the multiple fields related to the redundancy parity code block are included in the DCI format.

[0311] 33. The method according to any of solutions 5 or 6, wherein the permitted puncturing locations of the first group of the code block correspond to the leading edge.

[0312] 34. The method according to any of solutions 5 or 6, wherein the allowed puncturing locations of the second group of code blocks correspond to the tail ends.

[0313] 35. The method according to any of Solutions 1-12 or 14, wherein the puncturing bit locations of the plurality of code blocks of a first type for the transport block are overlapped and located at the beginning of each of the plurality of code blocks, and the puncturing bit locations of the plurality of code blocks of a second type for the transport block are overlapped and located at the end of each of the plurality of code blocks.

[0314] 36. The method according to any of solutions 5 or 6, wherein the indices of the first type of multiple code blocks are odd numbers and the indices of the second type of multiple code blocks are even numbers.

[0315] 37. The method according to any of solutions 5 or 6, wherein the indices of the first type of multiple code blocks are even numbers and the indices of the second type of multiple code blocks are odd numbers.

[0316] 38. The method of any of Solutions 7 or 8, wherein the puncturing pattern comprises non-overlapping locations for multiple code blocks.

[0317] 39. A method according to any of solutions 1-38, wherein the wireless device is user equipment (UE).

[0318] 40. A method according to any of Solutions 1-8, further comprising receiving an acknowledgment of the data transmission.

[0319] 41. An apparatus for wireless communication comprising a memory and a processor, the processor reading code from the memory and implementing a method recited in any of solutions 1-40.

[0320] 42. A computer-readable program storage medium having code stored thereon, the code, when executed by a processor, causing the processor to implement a method recited in any of Solutions 1-40.

[0321] 20A and 20B are flowcharts for a downlink data transmission scheduling procedure including redundancy parity blocks for a wireless device (e.g., UE) and a network device (e.g., gNB). For example, as described with respect to FIG. 12-15 and shown in FIG. 20A, in some embodiments, a user device may receive a DCI scheduling a DL data transmission, followed by receiving a data transmission according to the schedule received in the DCI on a PDSCH, followed by reporting a hybrid automatic repeat request (HARQ) acknowledgement for the received data transmission to the network device. Conversely, as described with respect to FIG. 12-15 and shown in FIG. 20B, a network device may transmit a DCI scheduling a DL data transmission, followed by the network device transmitting data in a PDSCH according to the schedule, followed by receiving a HARQ-ACK from the receiving wireless device.

[0322] 20C and 20D are flowcharts for an uplink data transmission scheduling procedure including redundancy parity blocks for a UE and a gNB. For example, as described with respect to FIGS. 12-15 and further shown in FIG. 20C, in some embodiments, a wireless device may receive a DCI that schedules an uplink transmission for the wireless device. The wireless device then transmits a data transmission on a physical uplink shared channel (PUSCH) according to the schedule.

[0323] As described with respect to Figures 12-15 and further shown in Figure 20D, in some embodiments, the gNB may transmit DCI providing a schedule for uplink UL transmissions and subsequently receive data transmissions on the PUSCH in accordance with the schedule.

[0324] 21A and 21B are flow charts of rate matching for data transmission including redundancy parity blocks. For example, in some embodiments, a UE may generate multiple code blocks including redundancy parity blocks from data bits to be transmitted according to a DCI. The data bits may be punctured according to a rate matching pattern that defines the location of the data bits for each code block within the multiple code blocks that are allowed to be punctured.

[0325] FIG. 22 is a block diagram representation of a portion of an apparatus according to some embodiments of the disclosed technology. An apparatus 2205, such as a base station, a network device, or a wireless device (or UE), can include a processor electronics 2210, such as a microprocessor, that implements one or more of the techniques presented herein. The apparatus 2205 can include transceiver electronics 2215 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as an antenna 2220. The apparatus 2205 can also include other communication interfaces for transmitting and receiving data. The apparatus 2205 can include one or more memories (not explicitly shown) configured to store information, such as data and / or instructions. In some implementations, the processor electronics 2210 can include at least a portion of the transceiver electronics 2215. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using the apparatus 2205.

[0326] Some of the embodiments described herein are described in the general context of a method or process, which in one embodiment may be implemented by a computer program product embodied in a computer-readable medium including computer-executable instructions, such as program code, executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including, but not limited to, read-only memory (ROM), random access memory (RAM), compact discs (CDs), digital versatile discs (DVDs), and the like. Thus, the computer-readable medium may include non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. Computer or processor executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps or processes.

[0327] Some of the disclosed embodiments can be implemented as devices or modules using hardware circuits, software, or a combination thereof. For example, hardware circuit implementations can include discrete analog and / or digital components integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as application specific integrated circuits (ASICs) and / or as field programmable gate array (FPGA) devices. Some implementations may additionally or alternatively include digital signal processors (DSPs), which are specialized microprocessors with architectures optimized for the needs of digital signal processing operations associated with the disclosed functionality of the present application. Similarly, various components or subcomponents within each module may be implemented in software, hardware, or firmware. Connectivity between modules and / or components within a module may be provided using any one of the connectivity methods and mediums known in the art, including, but not limited to, communication via the Internet, wired, or wireless networks using appropriate protocols.

[0328] Although this document contains many details, these should not be construed as limitations on the scope of the claimed invention or what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Also, although features may be described above as acting in a combination and may be initially claimed as such, one or more features from the claimed combination may, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination. Similarly, although operations are illustrated in the figures in a particular order, it is understood that such operations are not required to be performed in the particular order or sequential order shown, or that all of the illustrated operations be performed, to achieve desired results.

[0329] Only some implementations and examples have been described; other implementations, enhancements, and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. 1. A method performed by a wireless device, comprising: communicating a first message between a wireless device and a network device, the first message comprising one or more parameters related to error correction coding; communicating a data transmission between the wireless device and the network device using the error correction coding in accordance with the one or more parameters, wherein a redundancy parity block included in the data transmission does not include information bits of a transport block and is obtained by at least a plurality of code blocks of the transport block and a generating sequence, the generating sequence being determinable from at least one of a number of the plurality of code blocks associated with the redundancy parity block and a number of code block groups for the transport block; A method comprising:

2. The method of claim 1 , wherein the first message is transmitted as downlink control information (DCI) having a predefined format type.

3. The DCI is an identifier for redundancy parity block transmission; a number of code blocks associated with the redundant parity block transmission; the generating sequence for the redundant parity block transmission; Number of redundant parity blocks, an index of a code block associated with said redundancy parity block; Rate matching bit pattern, HARQ processor number, or A bitmap of the code block group a plurality of fields configurable to indicate at least one of: the generation sequence is used to generate the redundancy parity blocks; The method of claim 2 , wherein the rate matching bit pattern is used to determine puncturing bit locations of the plurality of code blocks for the data transmission.

4. The method of claim 3, wherein the rate matching bit pattern includes a number of puncturing bits or corresponding puncturing bit locations of the multiple code blocks for the data transmission.

5. The generated sequence is denoted as an index into the list from which it originates; The method of claim 2 , wherein the generated sequence is derived from a list configured by higher layer parameters.

6. The DCI format is DCI format 0-1, DCI format 1-1, DCI formats 0-2, or DCI Format 1-2 At least one of 3. The method of claim 2, wherein at least one of the first type fields in the DCI format 0-1, DCI format 1-1, DCI format 0-2, or DCI format 1-2 is interpreted as indicating information related to redundancy parity block transmission in response to at least one of the second type fields of the DCI being set to a predetermined value.

7. in response to there being an initial transmission of the transport block, a number of fields associated with a redundancy parity code block are not included in the DCI format; The method of claim 3 , wherein in response to there being a retransmission of the transport block, a number of fields related to redundancy parity code blocks are included within the DCI format.

8. puncturing bit locations of a first type of code block for the transport block are overlapped and placed at the beginning of each of the code blocks; 3. The method of claim 2, wherein puncturing bit locations of a plurality of code blocks of a second type for the transport block are overlapped and located at an end of each of the plurality of code blocks.

9. An apparatus for wireless communication, the apparatus comprising a memory and a processor, the processor reading from the memory and executing code for performing each step of the method according to any one of claims 1 to 8.

10. A computer readable program storage medium having stored thereon code which, when executed by a processor, causes the processor to perform a method according to any one of claims 1 to 8.

Images