Wireless data transmission using parity check blocks

Abstract

Describes methods, systems, and devices for wireless communication. An example method of wireless communication includes receiving, by a wireless device, a first message from a network device, the first message including 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 based on the one or more parameters.

Description

[0001] Cross - reference to related applications

[0002] This patent document is a continuation of International Patent Application No. PCT / CN2020 / 096098, filed on June 15, 2020. The entire content of the above - mentioned patent application is incorporated herein by reference as part of the disclosure of this application. Technical field

[0003] This document generally relates to wireless communication. Background art

[0004] Wireless communication technologies are moving the world towards an increasingly interconnected and networked society. The rapid growth of wireless communication and technological progress has led to a greater demand for capacity and connectivity. Other aspects, such as energy consumption, device cost, spectral efficiency, and latency, are also important for meeting the requirements of various communication scenarios. Compared with existing wireless networks (such as LTE wireless networks), next - generation systems and wireless communication technologies need to support an increasing number of users and devices. Summary of the invention

[0005] This document relates to methods, systems, and devices for monitoring schemes of downlink control signals in mobile communication technologies, including fifth - generation (5G) and New Radio (NR) communication systems.

[0006] In one exemplary aspect, a wireless communication method is disclosed. The method includes: receiving, by a wireless device, a first message from a network device, the first message including one or more parameters related to error - correction coding; and transmitting, by the wireless device, a data transmission to the network device using error - correction coding based on the one or more parameters.

[0007] In another exemplary aspect, a wireless communication method is disclosed. The method includes: transmitting, by a network device, a first message to a wireless device, the first message including one or more parameters related to error - correction coding; and after transmitting the first message, transmitting, by the network device, a data transmission to the wireless device using error - correction coding based on the one or more parameters.

[0008] In another exemplary aspect, a wireless communication method is disclosed. The method includes: receiving, by a wireless device, a first message from a network device, the first message including one or more parameters related to error - correction coding; and receiving, by the wireless device, a data transmission from the network device using error - correction coding based on the one or more parameters.

[0009] In another exemplary aspect, a wireless communication method is disclosed. The method includes: transmitting, by a network device, a first message to a wireless device, the first message including one or more parameters related to error correction coding; and after transmitting the first message, receiving, by the network device, a data transmission from the wireless device using error correction coding according to the one or more parameters.

[0010] In another exemplary aspect, a wireless communication method is disclosed. The method includes: generating, by a first wireless device, a plurality of code blocks from data bits to be transmitted, including at least one redundant parity check block; dividing the plurality of code blocks into at least a first set of code blocks and a second set of code blocks according to allowed puncturing bit positions; rate matching the code blocks by puncturing according to the allowed puncturing bit positions; and transmitting the result of the rate matching to a second wireless device.

[0011] In another exemplary aspect, a wireless communication method is disclosed. The method includes: receiving, by a first wireless device, a data transmission including rate-matched data, wherein the rate-matched data is generated by dividing a plurality of code blocks including at least one redundant parity check block into a first set of code blocks and a second set of code blocks according to allowed puncturing positions and puncturing the first set and the second set of code blocks according to the allowed puncturing positions; and determining, from the data transmission, the data bits encoded in the data transmission.

[0012] In another exemplary aspect, a wireless communication method is disclosed. The method includes: generating, by a first wireless device, a plurality of code blocks from data bits to be transmitted, including at least one redundant parity check block; dividing the plurality of code blocks into at least a first set of code blocks and a second set of code blocks according to allowed puncturing positions; rate matching the plurality of code blocks by puncturing according to a puncturing pattern, wherein the puncturing pattern defines the allowed puncturing bit positions for each of the plurality of code blocks; and transmitting the result of the rate matching to a second wireless device.

[0013] In another exemplary aspect, a wireless communication method is disclosed. The method includes: receiving, by a first wireless device, a data transmission including a plurality of code blocks, the plurality of code blocks including at least one redundant parity check block, wherein the plurality of code blocks are rate matched according to a puncturing pattern, the puncturing pattern defining the allowed puncturing bit positions for each of the plurality of code blocks; and determining the data bits encoded in the data transmission based on the puncturing pattern.

[0014] In yet another exemplary aspect, the above method is embodied in processor-executable code and stored in a computer-readable program medium.

[0015] In yet another exemplary embodiment, a device configured to or operable to execute the above method is disclosed.

[0016] The above aspects and other aspects and their implementations are described in more detail in the drawings, the specification and the claims. Description of the Drawings

[0017] Figure 1 Examples of a base station (BS) and a user equipment (UE) in wireless communication are shown.

[0018] Figure 2 An example of rate matching of one of a plurality of code blocks is shown.

[0019] Figure 3 Parity check bits between LDPC-based code blocks generated by an all ones generation sequence and a modulo2 operation are shown.

[0020] Figure 4 A process of downlink control information (DCI) indicating verification of scheduling from redundant parity check bits to release of scheduling of redundant parity check bits is shown.

[0021] Figure 5A and 5B The same puncture bit positions of each code block in a group are shown.

[0022] Figure 6 It is shown that the puncture bit positions between code blocks in different groups including redundant parity check blocks do not overlap.

[0023] Figure 7A and 7B It is shown that the puncture bit positions of all code blocks including redundant parity check blocks do not overlap.

[0024] Figure 8 Elements distribution for LDPC coding in a fifth generation (5G) new radio (NR) communication system is shown Figure 1 for the basic

[0025] Figure 9 Examples of a puncturing pattern of a systematic code block of the basic Figure 1 are shown.

[0026] Figure 10 Examples of a puncturing pattern of a systematic code block of the basic Figure 2 are shown.

[0027] Figure 11A and 11B It is shown that the puncture bit positions of all code blocks including redundant parity check blocks do not overlap.

[0028] Figure 12 Shows an example of a wireless communication process based on some example embodiments of the disclosed technology.

[0029] Figure 13 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0030] Figure 14 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0031] Figure 15 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0032] Figure 16 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0033] Figure 17 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0034] Figure 18 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0035] Figure 19 Shows another example of a wireless communication process based on some example embodiments of the disclosed technology.

[0036] Figure 20A and 20B is a flowchart of a downlink data transmission scheduling process (including redundant parity check blocks for user equipment and gNodeB); Figure 20C and 20D is a flowchart of an uplink data transmission scheduler (including redundant parity check blocks for user equipment and gNodeB).

[0037] Figure 21A and 21B is a flowchart of rate matching for data transmission including redundant parity check blocks.

[0038] Figure 22 is a block diagram representation of a part of an apparatus that can be used to implement the methods and / or techniques of the current disclosure. Detailed Description

[0039] Some features are described using examples of fifth-generation (5G) wireless protocols. However, the applicability of the disclosed technology is not limited to only 5G wireless systems.

[0040] In 5G and New Radio (NR) communication systems, there are three different types of use cases: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low-latency communication (URLLC). Each use case corresponds to its own technical specification requirements. For example, enhanced mobile broadband (eMBB) aims to enable larger amounts of data and support higher end-user data rates. For massive machine type communication (mMTC), high data rates are not important. Instead, it aims to support a large number of devices at very low device costs and very low device power consumption. For ultra-reliable low-latency communication (URLLC), very low latency and extremely high reliability are required. Although these requirements are artificial, they can also be used for further mobile communications, such as augmented reality / virtual reality (AR / VR) applications that require higher peak data rates (e.g., 300 Mbps).

[0041] In the case of supporting requirements for 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 channels. Assume that the target block error rate of LDPC coding is β, and the error probability of each code block is independent. Therefore, for a transport block (TB) whose transport block size (TBS) is divided into n code blocks, the error probability of the entire TBS can be derived as 1-(1-β) n . The TBS error rate increases with the increase in the number of code blocks and decreases with the decrease in the target block error rate. Generally, the number of code blocks increases with the increase in TBS. Therefore, if the target block error rate can be reduced by an enhanced coding method, the requirements for enabling larger amounts of data and extremely high reliability can be achieved.

[0042] In addition, from the perspective of power saving, a higher retransmission frequency of the TB may result in a larger amount of power consumption. Therefore, it is useful to reduce the number of retransmissions of the TB and improve the reliability of each transmission to reduce power consumption.

[0043] This document discloses techniques for controlling the transmission of redundant parity check blocks, including scheduling, generating, and transmitting additional redundant parity check blocks, which are applied to initial transmissions or retransmissions to improve reliability and reduce the number of retransmissions.

[0044] This document uses section headings and subheadings for ease of understanding, rather than limiting the scope of the disclosed technology and embodiments to certain sections. Thus, the embodiments disclosed in different sections can be used interchangeably. Additionally, this document only uses examples from the 3GPP NR network architecture and 5G protocols to facilitate understanding, and the disclosed technology and embodiments can be practiced in other wireless systems using communication protocols different from the 3GPP protocols.

[0045] Brief Discussion

[0046] In a 5G NR communication system, there are multiple available modulation and coding scheme (MCS) tables for providing the physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) of a user equipment (UE). The UE determines the transport block size (TBS) based on the number of resource elements (N RE ), modulation order (Q m ), code rate (R), and layer (v) parameters obtained according to the resource allocation information configured by higher layer parameters or indicated by downlink control information (DCI). The DCI transmits the downlink control information carried by the physical downlink control channel (PDCCH) using a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI). Currently, there are 15 DCI formats, which are denoted as DCI format 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 for a specific purpose. For example, DCI format 1-1 is used to schedule the PDSCH in a cell and / or trigger single-shot HARQ-ACK codebook feedback. The DCI bits of the same DCI format with different types of RNTIs can have different uses and interpretations.

[0047] The information transmitted through a DCI format with a CRC scrambled by an RNTI can be divided into multiple fields based on the use or meaning of the information. For example, the "frequency domain resource allocation" field in DCI format 1-1 with a 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 mapped to the information bits a0 to a A-1 . Each field is mapped in the order in which it appears in the specification, including one or more zero-padding bits (if any), where the first field is mapped to the lowest-order information bit a0, and each consecutive field is mapped to a higher-order information bit. The most significant bit of each field is mapped to the lowest-order information bit of that field. For example, the most significant bit of the first field is mapped to a0.

[0048] An example implementation of the LDPC encoding steps is as follows:

[0049] 1) Code block segmentation: Obtain two base graphs for NR-LDPC for the parity-check matrix, the base Figure 1 (BG1) and the base Figure 2 (BG2). For example, the UE can select one of the two base 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 the TB, the total number of bits after CRC attachment is TBS + L TB_CRC , where L TB_CRC = 24 bits. If TBS + L TB_CRC is not greater than K cb , then the number of code blocks is 1, and the additional CRC sequence with L CB_CRC = 24 bits is not attached to the code block; otherwise, the total number of code blocks is determined by C = ceil((TBS + L TB_CRC ) / (K cb – L CB_CRC ). The total number of bits for each code block is K' = (TBS + L TB_CRC + C * L CB_CRC ) / C.

[0050] Table 1 Base graph selection for NR-LDPC

[0051]

[0052]

[0053] 2) Parity-check matrix generation: The parity-check matrix is determined by the base graph and the lifting size (Zc). The number of columns for encoding system information bits is K b = 22Zc for BG1 and K b = 10Zc for BG2. The lifting size is the minimum value in a set of lifting sizes, as shown in Table 2, satisfying Zc ≥ K' / K b . As shown in Tables 3 and 4, the base graph matrix H LS is obtained based on the set index i BG of Zc and the element table of each base graph corresponding to the set index. After obtaining the base graph matrix H BG and the Zc value, the parity-check matrix H is obtained by replacing each element of H BG with a Zc * Zc matrix according to the following steps:

[0054] - H BGEach element with a median value of 0 is replaced by a zero matrix of size Zc*Zc; and

[0055] -H BG Each element with a median value of 1 is replaced by a circulant permutation matrix I(P i,j ) of size Zc*Zc, where i and j are the row index and column index of the element, and I(P i,j ) is obtained by cyclically shifting the identity matrix I of size Zc*Zc to the right by P i,j times. The value of P i,j is given by P i,j = mod(V i,j , Zc). The value of V i,j is given by the element table of the base graph according to the set index i LS and the LDPC base graph. For example, the base Figure 1 of NR-LDPC is shown in Table 3.

[0056] 3) Encoding: After completing the above operations, the matrix H is used to encode the information bit sequence of each code block.

[0057] 4) Rate matching and bit interleaving: After the encoding process, the encoded bit sequence of each code block is selected, and a part of the encoded bit sequence can be deleted to match the indicated code rate, as Figure 2 shown. To further improve the error correction performance, after rate matching, the bit sequence is interleaved into a new bit sequence. The resulting rate-matched bit sequence is used for modulation and generating the transmission waveform.

[0058] Table 2: Set z of LDPC lifting value sizes

[0059]

[0060]

[0061] Table 3: LDPC BG1 and its parity check matrix (V i,j )

[0062]

[0063] Table 4: LDPC BG2 and its parity check matrix (V i,j )

[0064]

[0065] The encoded code block may include systematic bits and parity check bits. The systematic bits are the original information bits and are part of the TB. The NR LDPC code is an example of a systematic code.

[0066] Inter - block Parity Check Bit Transmission Based on NR - LDPC

[0067] 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 orthogonal to H. LDPC codes are linear block codes. For example, assume that the size of the parity check matrix H is m×n, and the encoded bit sequences of two code blocks with CBS = l are A = [a1, a2,..., al] T and B = [b1, b2,..., bl] T .

[0068] According to the characteristics of the parity check matrix of LDPC, it can be seen that H*A = 0 and H*B = 0. Therefore, if A and B are added by modulo 2 operation to obtain C, then H*(A + B) = 0 can be derived from the equation H*C = 0. Therefore, the bit sequence C can be decoded and verified by the matrix H and represented as an encoded code block. Each bit of C is the sum of the corresponding bits of A and B by modulo 2 operation, so that each bit of C can be used as the parity check bit of the corresponding bits of A and B. That is to say, the bit sequence C can provide additional soft decoding information to A and B including system information bits to improve the bit error correction performance of NR-LDPC. Generally, for a transport block size (TBS) divided into multiple code blocks (e.g., CB1,..., CB N ), Figure 3 The process of generating C by using an all-1 generation sequence is shown in

[0069] The conversion relationship between the system code block and the redundant parity check block can be defined as a generation sequence. For example, the generation sequence can be an all-1 sequence. In this case, the redundant parity check block Pr is obtained by (CB1 + CB2 +... + CB N ) modulo 2. In addition, the generation sequence of the inter-block parity check block (denoted as the redundant parity check block Pr) can also be other forms than the all-1 generation sequence. For example, for retransmission, there may be only a few error code blocks, so that the redundant parity check block can be generated by the error code blocks. For example, CB2 and CB3 may not be received among a total of five code blocks, and the generation sequence should be [0 11 0 0]. Therefore, the redundant parity check block is obtained by (CB2 + CB3).

[0070] However, for the initial transmission, for the case where the transmission of the redundant parity check block is supported, some additional number of bits of each code block can be punctured to match the target rate. The method for scheduling the transmission of redundant parity check bits indicated by layer 1 (L1) signaling (e.g., DCI) is described in Example 1 of the embodiment. The rate matching method for the transmission of the redundant parity check block is described in Example 2 of the embodiment. The higher layer parameters related to the transmission of the redundant parity check block are described in Embodiment 3.

[0071] In the following description, a code block including information bits of TB is represented as a system code block, and an additional code block obtained by modulo-2 operation in the code block is represented as a redundant parity check block.

[0072] In some embodiments, a specific RNTI as described below can be used to scramble the CRC of DCI and is only associated with the transmission of redundant parity check bits.

[0073] Note that the various methods described herein can be used for both UL data transmission procedures and DL data transmission procedures.

[0074] For UL data transmission, the UE can first receive downlink control signaling indicating multiple parameters transmitted by the gNodeB (gNB). The multiple parameters can be related to scheduling UL data transmission. Next, the UE can transmit data to the gNB based on the multiple parameters. If the gNB does not receive the data transmitted by the UE corresponding to the downlink control signaling, the gNB can transmit another downlink control signaling to schedule the same UL data transmission to the UE.

[0075] For DL data transmission, the UE can first receive downlink control signaling indicating multiple parameters transmitted by the gNB. The multiple parameters can be related to scheduling DL data transmission. Next, the UE can receive the data transmitted by the gNB based on the multiple parameters and report HARQ-ACK information on whether the DL data is successfully received.

[0076] Example 1 of Embodiment: Transmission of Redundant Parity Check Blocks Scheduled by Control Signaling

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

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

[0079] In some embodiments, the rate matching bit pattern can be used to determine the number and positions of puncturing bits for each code block.

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

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

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

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

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

[0085] In some embodiments, the DCI format for scheduling redundant parity check block transmission may be at least one of the following DCI formats:

[0086] 1) DCI format 0-1;

[0087] 2) DCI format 0-2;

[0088] 3) DCI format 1-1; or

[0089] 4) DCI format 1-2.

[0090] Example 1 - 1 of Embodiment: L1 Signaling Indication Design

[0091] Method 1-1-1:

[0092] The information related to redundant parity check block transmission may be indicated by multiple fields in the DCI, and a traditional user equipment may interpret these fields differently compared to the device implementing the disclosed technology.

[0093] Two types of fields in the existing (traditional) DCI can be used for scheduling redundant parity check block transmission.

[0094] In some embodiments, the bit information of the first type of field may be interpreted as resource information related to redundant parity check block transmission. The bit information of the second type of field can be used to identify whether the DCI indicates redundant parity check block transmission.

[0095] If the UE receives a DCI and the second type of field is set to a predefined state, the first type of field may be interpreted as information related to scheduling redundant parity check block transmission. In some embodiments, the predefined state may be that all bits of the field are set to "0" or "1".

[0096] If the DCI format is DCI format 0-1 or DCI format 0-2, where the CRC is 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 and coding scheme cell RNTI (MCS-C-RNTI), or 5) specific RNTI, then the first type field may include at least one of the following:

[0097] 1) Uplink / supplementary uplink (UL / SUL) indication;

[0098] 2) Bandwidth part indication;

[0099] 3) Frequency domain resource allocation;

[0100] 4) Time domain resource allocation;

[0101] 5) Modulation and coding scheme;

[0102] 6) New data indication;

[0103] 7) Redundancy version;

[0104] 8) HARQ process number;

[0105] 9) Transmit power control (TPC) command for scheduling PUSCH;

[0106] 10) Precoding information and number of layers;

[0107] 11) Antenna port; or

[0108] 12) Demodulation reference signal (DMRS) sequence initialization.

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

[0110] The second type field may include at least one of the following:

[0111] 1) Uplink shared channel (UL-SCH) indication;

[0112] 2) CSI request;

[0113] 3) Frequency domain resource allocation;

[0114] 4) Modulation and coding scheme;

[0115] 5) New data indication; or

[0116] 6) Redundancy version.

[0117] The predefined states of the second type field may include at least one of the following:

[0118] 1) The uplink shared channel (UL-SCH) indication is "0";

[0119] 2) A CSI request of all 0s;

[0120] 3) A frequency-domain resource allocation of all 0s with a resource allocation type or a frequency-domain resource allocation of all 1s with a resource allocation type;

[0121] 4) A modulation and coding scheme of all 0s;

[0122] 5) The new data indication is "0"; or

[0123] 6) A redundancy version of all 0s.

[0124] For example, the UE may receive DCI format 0-1, where the CRC is scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI. If the predefined state of the second type field includes that the UL-SCH indication is "0" and a CSI request of all 0s, then the other fields can all be used to indicate information related to the redundant parity check block transmission.

[0125] For example, the UE may receive DCI format 0-1, where the CRC is scrambled by SP-CSI-RNTI. If the predefined state of the second type field includes: 1) the UL-SCH indication is "0", 2) a CSI request of all 0s, and 3) a frequency-domain resource allocation of all 0s with resource allocation type 0 or resource allocation type 2, or a frequency-domain resource allocation of all 1s with resource allocation type 1 or resource allocation type 2, then the other fields can all be used to indicate information related to the redundant parity check block transmission.

[0126] If the DCI format is DCI format 1-1 or DCI format 1-2, where the CRC is scrambled by at least one of the following: 1) C-RNTI, 2) CS-RNTI, or 3) MCS-C-RNTI, then the first type field may include at least one of the following:

[0127] 1) Bandwidth part indication;

[0128] 2) Frequency-domain resource allocation;

[0129] 3) Time-domain resource allocation;

[0130] 4) Rate matching indication;

[0131] 5) Modulation and coding scheme;

[0132] 6) New data indication;

[0133] 7) Redundancy version;

[0134] 8) HARQ process number;

[0135] 9) Downlink allocation index;

[0136] 10) TPC command for scheduling PUSCH;

[0137] 11) PDSCH group index;

[0138] 12) New feedback indication;

[0139] 13) Number of requested PDSCH groups;

[0140] 14) Antenna port;

[0141] 15) Code block group (CBG) transmission information (CBGTI);

[0142] 16) CBG clearing information (CBGFI); or

[0143] 17) DMRS sequence initialization.

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

[0145] The second type of field may include at least one of the following:

[0146] 1) UL-SCH indication;

[0147] 2) CSI request;

[0148] 3) Frequency domain resource allocation;

[0149] 4) Modulation and coding scheme;

[0150] 5) New data indication;

[0151] 6) Redundancy version; or

[0152] 7) HARQ process number.

[0153] The status of the second type of field may include at least one of the following:

[0154] 1) UL-SCH indication is "0";

[0155] 2) All-0 CSI request;

[0156] 3) All-0 frequency domain resource allocation with a resource allocation type, or all-1 frequency domain resource allocation with a resource allocation type;

[0157] 4) All-0 modulation and coding scheme;

[0158] 5) The new data is indicated as "0";

[0159] 6) A redundant version of all 0s; or

[0160] 7) A HARQ process number of all 0s.

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

[0162] For example, the UE may receive DCI format 1-1, where the CRC is scrambled by C-RNTI. If the status of the second type field includes: 1) the UL-SCH is indicated as "0", 2) a CSI request of all 0s, and 3) a frequency domain resource allocation of all 0s with resource allocation type 0, or a frequency domain resource allocation of all 1s with resource allocation type 1, then the other fields can all be used to indicate information related to redundant parity block transmission.

[0163] For example, the UE may receive DCI format 1-1, where the CRC is scrambled by CS-RNTI. If the status of the second type field includes: 1) the UL-SCH is indicated as "0", 2) a CSI request of all 0s, or 3) a frequency domain resource allocation of all 0s with resource allocation type 0, or a frequency domain resource allocation of all 1s with resource allocation type 1, then the other fields can all be used to indicate information related to redundant parity block transmission.

[0164] Method 1-1-2:

[0165] Information related to redundant parity block transmission can be indicated by a two-level DCI signaling scheme, where some fields of the traditional DCI will be differently interpreted by embodiments implementing the disclosed technology compared to traditional devices.

[0166] In some embodiments, the UE receives DCI, where the CRC is 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) a specific RNTI, and only the second type field is available. Different states of the second type field can indicate different redundant parity bit scheduling types. This DCI can be represented as the first-level DCI.

[0167] The UE may assume that: after the UE detects a DCI of the second type field indicating verification of a DCI format whose status indicates the ability to schedule redundant parity block transmission, the next received DCI schedules redundant parity block transmission. The scheduling DCI capable of scheduling redundant parity block transmission can be represented as the second-level DCI.

[0168] If the UE detects DCI at time slot n, and the DCI indicates a second type field of the release of a DCI format whose state represents the ability to schedule redundant parity block transmission, the UE may assume that the DCI received after time slot n indicates normal data transmission without redundant parity blocks.

[0169] The scrambling RNTIs of the first-level DCI and the second-level DCI may be different.

[0170] For example, Figure 4 Illustrates the DCI indication process from the scheduling verification of redundant parity bits to the release of redundant parity bit scheduling.

[0171] Method 1-1-3:

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

[0173] In some embodiments, these fields may be specific fields that can only be reserved to indicate information related to redundant parity block transmission.

[0174] In some embodiments, the DCI format may be different from the current 15 DCI formats defined in NR, and the RNTI may be a specific RNTI dedicated to the uses described herein. In some embodiments, the specific RNTI may be different from any known RNTI, such as the RNTIs currently formulated in the NR document, including at least C-RNTI, MCS-C-RNTI, CS-RNIT, or SP-CSI-RNTI. In some embodiments, the specific RNTI may be related only to the DCI that schedules redundant parity bit transmission.

[0175] In some embodiments, the DCI format may be a new DCI format only for supporting UEs after NR Release 16.

[0176] 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 that scrambles the CRC of the DCI may be a specific RNTI. The specific RNTI may be different from C-RNTI, MCS-C-RNTI, CS-RNIT, SP-CSI-RNTI, and may be related to redundant parity block scheduling.

[0177] In some embodiments, if the transport block is divided into one code block, the UE may not expect to receive / send redundant parity block transmission.

[0178] In some embodiments, if the scheduled data transmission including the redundant parity check block transmission is a retransmission of a transport block, the UE may not expect to calculate the TBS.

[0179] In some embodiments, if the scheduled data transmission including the redundant parity check block transmission is an initial transmission or a first transmission of a transport block, the UE may need to calculate the TBS.

[0180] For the redundant parity check block transmission and the initial transmission of a transport block, the UE may assume that the resource allocation is for the transport block and the redundant parity check block transmission, and the UE may determine the TBS based on the indication of the resource allocation related to the TBS determination in the DCI. This implicit understanding of the UE can avoid wasting resources for additional bits used to transmit the redundant parity check block.

[0181] For the redundant parity check block transmission and the initial transmission of a transport block, the UE may assume that the resource allocation for the transport block and the redundant parity check block transmission is indicated by different fields in the same DCI or by the same field in different DCIs; the UE may determine the TBS based on the indication of the resource allocation related to the transport block in the DCI. This implicit understanding of the UE can provide a clear resource allocation for the transport block and the redundant parity check block, and provide a better coding gain when the system code block and the redundant parity check block do not have a rate-matched bit pattern.

[0182] In some embodiments, for the first transmission, there may be no field related to the redundant parity check block. In some embodiments, for the retransmission, there may be a field related to the redundant parity check block.

[0183] Other Detailed Descriptions

[0184] The redundant parity check block transmission may be transmitted on the PUSCH and the PDSCH.

[0185] In some embodiments, the redundant parity check block may be scheduled to be transmitted in the active UL or DL bandwidth part (BWP) on a secondary serving cell (SCell).

[0186] In some embodiments, the redundant parity check block may be scheduled to be transmitted in the active UL or DL BWP on a primary serving cell (PCell).

[0187] In some embodiments, if a cell group is configured, the redundant parity check block may be scheduled to be transmitted in the active UL or DL BWP on a cell or a cell group.

[0188] In some embodiments, the redundant parity check block may be scheduled for the case of carrier aggregation / dual connectivity (CA / DC) configuration.

[0189] In some embodiments, redundant parity bit scheduling cannot be used for cases of cross-slot scheduling configurations.

[0190] Fields of DCI for indicating resource allocation for redundant 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 indication, 5) redundancy version, 6) HARQ process number, 7) CBG transmission information (CBGTI), or 8) one or more antenna ports.

[0191] In some embodiments, the bit width of the resource allocation field in DCI related to the redundant parity block for transmission cannot be greater than the bit width of the system code block of the transport block.

[0192] For methods 1-1-1, 1-1-2, and 1-1-3, when the UE supports redundant parity block transmission, indication information related to the redundant parity block transmission of the first type field or the second type field in DCI can be used by the UE.

[0193] In some embodiments, if the redundant parity block is scheduled by DCI together with the transport block, the encoded redundant parity block can be concatenated after the encoded bits of the transport block.

[0194] Other Detailed Descriptions of Uplink Data Transmission

[0195] If the HARQ-ACK bit is transmitted on the PUSCH or PUCCH, additional bits for indicating the number of erroneous system code blocks of the most recent transmission of the same TB can be transmitted immediately after the existing HARQ-ACK bit. Otherwise, the redundant parity block transmission can be based on the reported HARQ-ACK bits, which are a bitmap of each code block group of the same TB.

[0196] If a specific higher layer parameter or L1 signaling configures that the UE should receive or transmit redundant parity blocks, the corresponding reporting quantity associated with the redundant parity block can be multiplexed with the HARQ-ACK bits of the same TB. The reported quantity can include the number of erroneous system code blocks, CSI, L1 signal-to-interference-plus-noise ratio (L1-SINR), or L1 reference signal received power (L1-RSRP).

[0197] Example 1 - 2 of Embodiment: Generation Sequence Indication

[0198] The generation sequence can be determined by the number of code blocks of the transport block and the number of code block groups.

[0199] In some embodiments, the generation sequence can be indicated as an index of a generation sequence list. The generation sequence list can be configured by a higher layer parameter.

[0200] In some embodiments, the generation sequence may be obtained by the indices of code blocks associated with redundant parity check blocks.

[0201] In some embodiments, the generation sequence may be configured by higher layer parameters. For example, the higher layer parameters may be transmitted via Radio Resource Control (RRC) signaling.

[0202] In some embodiments, the higher layer parameters may configure multiple generation sequence lists. The higher layer parameters may select multiple indices of generation sequences from multiple generation sequences. Here, the higher layer parameters are Radio Resource Control signaling, and the higher layer parameters are Medium Access Control (MAC) signaling.

[0203] In some embodiments, the higher layer parameters may configure multiple generation sequence lists. The higher layer parameters may select multiple indices of generation sequences from multiple generation sequences. The DCI may indicate one generation sequence among the multiple generation sequences.

[0204] For example, a transport block may be divided into N code blocks. The total number of generation sequences for redundant parity check block transmission may be as shown in Table 5.

[0205] Table 5

[0206]

[0207]

[0208] In some embodiments, the generation sequence for redundant parity check block transmission may be associated with code block group configuration.

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

[0210] 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. Therefore, the number of CBGs can be M = min(4, 10). The index of each group of code blocks can be {[0 1 2], [3 4 5], [6 7], [8 9]}. Therefore, the maximum number of redundant parity check blocks for this transport block can be equal to M + 1, and the generation sequence of the redundant code blocks can be as shown in Table 6.

[0211] Table 6

[0212]

[0213]

[0214] In one embodiment, for the first transmission, the gNB may send a DCI indicating data transmission (including the transmission of the redundant parity check block with the generation sequence index 5).

[0215] In another embodiment, after the first transmission, if the gNB receives a bitmap of the HARQ-ACK information for the CBG-based PDSCH transmission indicating that at least one of the code blocks in the first CBG and the third CBG is not successfully received, the gNB may send a DCI indicating the transmission of the redundant parity check blocks with the generation sequence indices 1 and 3, respectively.

[0216] In yet another embodiment, after the first transmission, if the gNB receives a bitmap of the HARQ-ACK information for the CBG-based PDSCH transmission indicating that at least one of the code blocks in each CBG is not successfully received, the gNB may send a DCI indicating the transmission of the redundant parity check block with the generation sequence index 5.

[0217] In some embodiments, if there are more than one redundant parity check block transmissions, the generation sequence of the redundant parity check blocks may be indicated as a bitmap. Each generation sequence indication of the redundant parity check blocks may have the same bit width.

[0218] Example 2 of Embodiment: Rate - Matching Bit Pattern for Redundant Parity Check Block Transmission

[0219] In these embodiments, a method for determining the rate matching bit pattern of the redundant parity check block transmission is described.

[0220] In some embodiments, the rate matching bit pattern is determined by the following predefined function or process.

[0221] In some embodiments, the rate matching bit pattern is configured by higher layer parameters, e.g., configured by RRC signaling or MAC signaling.

[0222] In some embodiments, the rate matching bit pattern can be used to indicate the number of puncturing bits and the corresponding puncturing bit positions of code blocks for data transmission including redundant parity check blocks.

[0223] The indication of the rate matching bit pattern can be used to determine the number of puncturing bits and the puncturing bit positions of code blocks for data transmission including multiple scheduled redundant parity check bits.

[0224] In some embodiments, the rate matching bit pattern for redundant parity check block transmission can be determined by at least one of the following factors of the transport block:

[0225] 1) The total number of transmission bits of each system code block;

[0226] 2) The number of code blocks of the transport block;

[0227] 3) The system code block size; or

[0228] 4) The cyclic shift value (Zc);

[0229] In some embodiments, the rate matching bit pattern for redundant parity check block transmission can be determined by at least one of the following parameters of the transport block:

[0230] 1) The transport block size;

[0231] 2) The number of code blocks related to one redundant parity check block; or

[0232] 3) The cyclic shift value (Zc);

[0233] These parameters can be indicated or determined by the DCI scheduling the redundant parity check bit transmission.

[0234] In this embodiment, the puncturing bit positions of multiple code blocks do not overlap, while the puncturing bit positions of another multiple code blocks can overlap. The code blocks can represent the total number of code blocks for the scheduled redundant parity check block transmission.

[0235] For the first transmission, the number of puncturing bits of each code block can be determined by the number of transmission bits of multiple code blocks. The number of code blocks can be equal to the number of scheduled redundant parity check blocks.

[0236] For the first transmission, if some conditions satisfy at least one of the following events, the UE cannot request puncturing of additional bits for each code block:

[0237] 1) The code rate is within a numerical range;

[0238] 2) The TBS is within the numerical range;

[0239] 3) The modulation order is within the numerical range; or

[0240] 4) The scheduled data transmission is a retransmission of a transport block.

[0241] In some embodiments, the numerical range of the code rate may include the range from 1 / 4 to 5 / 6. In some embodiments, the numerical range of the TBS may include the range from 3840 to 10 6 within the range. In some embodiments, the numerical range of the modulation order may include the range from 2 to 6.

[0242] Example 2 - 1 of Embodiment: The Punching Bit Positions Do Not Overlap in Different Groups of Code Blocks

[0243] When the redundant parity check block is transmitted together with its corresponding systematic code block, additional puncturing may be required for all code blocks including the redundant parity check block to adapt to the channel capacity. As described in the previous section, this additional puncturing can typically be performed after the traditional rate matching. The calculation of the number of puncturing bits for each code block is described here.

[0244] In some embodiments, the elements of the vector Punct_set may represent the number of puncturing bits of multiple systematic code blocks of the TB.

[0245] If L / (N + 1)>Zc

[0246] Punct0 = Zc;

[0247] Punct1 = L – Zc×N;

[0248] Punct_set = [Punct0×ones(1,N),Punct1];

[0249] else

[0250] Punct0 = floor(L / (N + 1));

[0251] Punct1 = Punct0 + 1;

[0252] N1 = mod(L,(N + 1));

[0253] N0 = N + 1 – N1;

[0254] Punct_set = [Punct0×ones(1,N0),(Punct1)×ones(1,N1)];

[0255] end

[0256] Wherein, L is the bit length of each code block after NR-LDPC rate matching, N is the number of code blocks for generating redundant parity check blocks, and Zc is the magnitude of the lifting value.

[0257] All code blocks including redundant parity check blocks can be divided into several groups. For the code blocks in each group, the puncturing bit positions can be the same. For the code blocks in different groups, the puncturing bit positions can be different. In some embodiments, the code blocks including redundant parity check blocks can be divided into M groups, where M is an integer not less than 1. In some embodiments, the additional puncturing bits of each code block in a group can be located at the tail of the code block after LDPC rate matching. In some embodiments, the additional puncturing bits of each code block in a group can be located at the beginning of each code block after NR-LDPC rate matching.

[0258] For example, there can be ten code blocks (e.g., CB0, CB1, …, CB9), including the redundant parity check block of the TB. These ten code blocks can be divided into one group. The bit sequence of each code block can be the code block after LDPC rate matching. That is, the positions of the puncturing bits in all code blocks can be the same. For example, the puncturing bits can be located at the tail or head of each code block, as shown in Figure 5A and 5B respectively.

[0259] In some embodiments, the puncturing bit positions among the code blocks in a group can be the same.

[0260] For example, there can be ten code blocks (e.g., CB0, CB1, …, CB9), including the redundant parity check block of the TB. As shown in Figure 6 these ten code blocks can be divided into two groups, with each group including 5 code blocks. In the first group, the indexes of the code blocks can be {0, 2, …, 8}. In the second group, the indexes of the code blocks can be {1, 3, …, 9}. The puncturing bits of each code block in the first group can be punctured from the tail of each code block after rate matching, while the puncturing bits of each code block in the second group can be punctured from the head of each code block after rate matching.

[0261] In some embodiments, the puncturing bit positions among the code blocks in different groups can be non-overlapping.

[0262] For example, there can be ten code blocks (e.g., CB0, CB1, …, CB9), including the redundant parity check block of the TB. These ten code blocks can be divided into ten groups. The puncturing bit positions in all code blocks can be non-overlapping.

[0263] The puncturing bit position of the first code block can be punctured from the tail or head of the first code block after rate matching, as shown in Figure 7A and7B as shown

[0264] For other code blocks, the puncturing bit positions can be adjacent to the puncturing bit positions of the previous code block.

[0265] In some embodiments, the puncturing bit positions between code blocks in different groups may not overlap.

[0266] In some embodiments, the additional puncturing bit positions of the systematic code blocks cannot overlap with the positions of the 2*Zc bits punctured at the head of each code block after LDPC rate matching for the transmission of the redundant parity check blocks.

[0267] In some embodiments, the additional puncturing bit positions of the redundant parity check blocks cannot overlap with the positions of the 2*Zc bits punctured at the head of each code block after LDPC rate matching for the transmission of the redundant parity check blocks.

[0268] In some embodiments, the additional puncturing bit positions of the systematic code blocks and the redundant parity check blocks cannot overlap with the positions of the 2*Zc bits punctured at the head of each code block after LDPC rate matching for the transmission of the redundant parity check blocks.

[0269] Example 2 - 2 of Embodiment: Fixed Total Number of Bits at Specific Bit Positions for Code Blocks Other Than Redundant Parity Check Blocks Punching Quantity

[0270] In this embodiment, the total number of puncturing bits (Ls) and the puncturing bit positions of all systematic code blocks of the TB can be determined in advance. Once the total number of puncturing bits of all systematic code blocks is determined, the number of puncturing bits of the redundant parity check blocks can be obtained by (L – Ls), where L represents the code block length after LDPC rate matching.

[0271] The Ls and the puncturing bit positions of all systematic code blocks can be determined in advance by the predefined column index set (S p ) of the selected base graph, the lifting value size (Zc), the lifting value size set index (i LS ) and / or the number of systematic code blocks (C s ) associated with the redundant parity check blocks.

[0272] The predefined column index set (S p ) of the selected base graph for determining the puncturing bit positions can be determined by the rate R allocated by the DCI, the systematic code block size (CBS), the number of systematic code blocks (C s ) and / or the threshold thr1 representing the number of column elements in S p .

[0273] S p The elements in can be the indexes of the columns in the selected base graph with the number of elements greater than the threshold thr1.

[0274] The total number of puncturing bits (Ls) can be equal to the minimum value between the lifting value size (Zc) and the number of systematic code blocks (C s ) and a multiple of the total number of elements (N p ) in S e .

[0275] Column indices 1 and 2 cannot be included in S p .

[0276] In some embodiments, the column indices in S p can be stored in descending order of the column indices.

[0277] For example, for the basic Figure 8 shown, S Figure 1 can include at least one element from the set {4, 5, 8, 11, 12, 13, 14, 15, 17, 18, 19, 22, 23}. For the basic p Figure 2 , S p can include at least one element from the set {3, 6, 8, 11, 12, 13, 14}.

[0278] In some embodiments, the puncturing columns can be the columns in S p whose indices are the first min(C s , N e ) elements.

[0279] In some embodiments, the puncturing columns can be the columns in S p whose indices are the last min(C s , N e ) elements.

[0280] In another embodiment, the column indices in S p can be stored in descending order of the number of elements in each column.

[0281] Figure 1 For example, for the basic Figure 2 , S p can include at least one element from the set {19, 23, 13, 11, 8, 22, 14, 4, 18, 17, 15, 12, 5}. For the basic

[0282] , S p can include at least one element from the set {12, 6, 8, 14, 3, 13, 11}. Cr can be the number of redundant parity check blocks. Cr cannot be greater than the value of floor(Cs / 2).

[0283] Figure 1 For example, for the basic Figure 1, R = 2 / 3, Cs = 10, Cr = 1, Q m = 2, L = 12300 and Zc = 384. The basic Figure 1 elements are as Figure 8 shown. The black dots represent the basic Figure 1 elements corresponding to specific integers.

[0284] Except for the first two columns, if thr1 equals 8, the predefined set of puncturing column indices (S Figure 1 ) of the basic p can be {4, 5, 8, 11, 12, 13, 14, 15, 17, 18, 19, 22, 23}. The total number of elements in S p can be N e = 13, excluding indices 1 and 2. Each column index in the predefined set can represent the corresponding Zc puncturing bit position. The total number of puncturing bits can be Zc * min(Cs, N e ) = 384 * 10 = 3840. The puncturing column indices can be the first ten elements in S p , such as {4, 5, 7, 8, 9, 11, 12, 13, 14, 15}. Figure 9 The puncturing patterns of all system code blocks are shown.

[0285] For the basic Figure 2 , R = 1 / 4, Cs = 5, Cr = 1, Q m = 2, L = 14784 and Zc = 384. Except for the first two columns, if thr1 equals 8, the predefined set of puncturing column indices (S Figure 2 ) of the basic p can be {3, 6, 8, 11, 12, 13, 14}. The total number of elements in S p can be N e = 7, excluding indices 1 and 2. Each column index in the predefined set can represent the corresponding Zc puncturing bit position. The total number of puncturing bits can be Zc * min(Cr, N e ) = 384 * 5 = 1920. The puncturing column indices can be the first ten elements in S p , such as {3, 6, 8, 11, 12}. Figure 10 The puncturing bit positions of all system code blocks are shown.

[0286] When the redundant parity check block is transmitted together with its corresponding system code block, the total additional number of puncturing bits of all code blocks including the redundant parity check block can be equal to the length of the redundant parity check block after the LDPC rate matching operation.

[0287] thr1 can be an integer not less than 8. The number of punctured bits of each code block except the redundant parity check blocks can be no greater than Zc. The number of punctured bits of each code block except the redundant parity check blocks can be no greater than the number of redundant parity check blocks. The total number of punctured bits of all system code blocks can be no greater than Cs * Zc.

[0288] In some embodiments, the puncturing pattern of each system code block can reuse the puncturing method disclosed in Embodiment 1.

[0289] In some embodiments, for a TB, the positions of the punctured bits in all its code blocks can be different and / or non-overlapping.

[0290] The first method for calculating the number of punctured bits of each code block is as follows.

[0291] If Lw / N > Zc

[0292] Punct0 = Zc;

[0293] Punct1 = L – Zc × N;

[0294] else

[0295] Punct0 = floor(Lw / N);

[0296] Punct1 = L – Punct0 × N;

[0297] end

[0298] Punct_set = [Punct0 × ones(1, N), Punct1];

[0299] Where Lw is the total bit length of α w * Zc, and α w is the number of columns of H BG whose number of elements > thr1,

[0300] and where L is the bit length of each code block after LDPC rate matching, N is the number of code blocks used to generate the redundant parity check blocks, and Zc is the value of the lifting size.

[0301] The second method for calculating the number of punctured bits of each code block is as follows:

[0302] If Lw / N > Zc

[0303] Punct0 = Zc;

[0304] Punct1 = L – Zc × N;

[0305] Punct_set = [Punct0 * ones(1, N), Punct1];

[0306] else

[0307] Punct0 = floor(Lw / N);

[0308] Punct1 = Punct0 + 1;

[0309] N1 = mod(Lw, N);

[0310] N0 = N - N1;

[0311] Punct2 = L - Lw;

[0312] Punct_set = [Punct0 * ones(1, N0), (Punct1) * ones(1, N1), Punct2];

[0313] end

[0314] Among them, Lw is the total bit length of α w *Zc, and α w is the number of columns of H BG whose column weight > w, and among them, L is the bit length of each code block after NR-LDPC rate matching, N is the number of code blocks used to generate redundant parity check blocks, and Zc is the lifting value size.

[0315] For example, there can be ten code blocks, including the redundant parity check block of the TB (i.e., C s = 9, C r = 1), the code rate can be 2 / 3, the lifting value size Zc can be 320, and the number of bits of each code block after LDPC rate matching can be 9804. Assuming thr1 = 10, then the column indices in S p can be {4, 8, 11, 13, 14, 19, 22, 23}. Then, for the systematic code block, based on the second method of calculating the number of puncturing bits, the puncturing bits can be {284, 284, 284, 284, 284, 285, 285, 285, 285}. For the redundant parity check block, the puncturing bits can be 7244. The puncturing bit positions of each code block can be punctured from the head or tail of the code block, as shown in Figure 11A and 11B respectively.

[0316] Example 2 - 3 of Embodiment: No Additional Punching Bits for All System Code Blocks of TB Used for Redundant Parity Check Block Transmission Bits

[0317] In this embodiment, for the system code block and the associated redundant parity check block, there may be no additional puncturing bits. The number of transmission bits of the redundant parity check block may be equal to or less than the number of bits of the system code block after LDPC rate matching. Therefore, the target code rate R of the TB with additional redundant parity check block transmission can be reduced.

[0318] For example, if a redundant parity check block of the same size as the system code block is transmitted, the rate of the TB can be reduced to R*C s / (C s +C r ), where C s is the number of system code blocks, and C r is the number of redundant parity check blocks.

[0319] The transmission of the redundant parity check block can be triggered by a predefined condition.

[0320] The number of transmission bits of the redundant parity check block can be determined by a set of parameters.

[0321] For transmission, the predefined condition may include at least one of the following: 1) the HARQ process number indicated by the DCI is not less than or equal to the threshold h1, 2) the redundancy version indicated by the DCI is greater than or equal to the threshold h2, 3) the scheduled 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 m of the TB indicated by the DCI is not less than h4, 5) the number of system code blocks for the TB is not less than h5 or the TBS is not greater than h8, 6) the relevant feedback parameter includes the number of error code blocks not greater than the threshold h6 received by the UE for the most recent transmission, or 7) the reported quantity related to the channel state or beam measurement is not less than the threshold h7, such as CSI-RS resource indication (CRI), channel quality indication (CQI), RSRP, and SINR, etc.

[0322] The relevant feedback parameter can be configured by a higher layer parameter and reported by the UE.

[0323] For example, there may be 9 code blocks greater than h5 = 5, including the redundant parity check block of the TB (e.g., C s = 9). The code rate can be 2 / 3 greater than h3 = 1 / 3, the boost value size Zc can be 320, and the number of bits of each code block after LDPC rate matching can be 9804.

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

[0325] For retransmission, if the number of error code blocks of the TB received by the UE is no greater than h6 = 9, the redundant parity check blocks can be transmitted for the next transmission of the TB. The number of transmission bits of the redundant parity check blocks can be 9804.

[0326] In another example, there can be 9 code blocks greater than h5 = 5, including the redundant parity check blocks of the TB (e.g., C s = 9). The code rate can be 2 / 3 greater than h3 = 1 / 3, the boosting value size Zc can be 320, and the number of bits of each code block after LDPC rate matching can be 9804.

[0327] If there is a first or initial transmission, the redundant parity check blocks cannot be transmitted for the next transmission of the TB. The transmission bits of the redundant parity check blocks can be 9804.

[0328] For the first retransmission, if the number of error code blocks of the TB received by the UE is no greater than h6 = 10, the redundant parity check blocks can be transmitted for the next transmission of the TB. The number of transmission bits of the redundant parity check blocks can be 9804.

[0329] For other retransmissions, if the number of error code blocks of the TB received by the UE is no greater than h6 = 9, the redundant parity check blocks can be transmitted for the next transmission of the TB. The number of transmission bits of the redundant parity check blocks can be 9804.

[0330] A set of parameters can include at least one of the following or be determined by at least one of the following: 1) the number of information bits of each system code block (CBS), 2) the number of bits of each system code block, 3) the number of system code blocks, 4) the redundant version of LDPC coding in Rel-16 and its corresponding initial position, 5) the redundant version of only the redundant parity check blocks and the new corresponding initial position, or 6) a set of predetermined scaling factors.

[0331] The set of predetermined scaling factors for modifying the number of transmission bits of the redundant parity check blocks can be determined by the number of system code blocks, the rate of the TB without redundant parity check blocks, the modulation order, and / or a set of thresholds of predefined conditions.

[0332] The maximum value of the elements in the set of predetermined scaling factors cannot be greater than 1.

[0333] The minimum value of the elements in the set of predetermined scaling factors cannot be less than 0.

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

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

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

[0337] 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.

[0338] For example, there may be 9 code blocks greater than h5 = 5, including the redundant parity check blocks of the TB (e.g., C s = 9). The code rate may be 2 / 3 greater than h3 = 1 / 3, the modulation order Q m may be 2, the uplift value size Zc may be 320, and the number of bits of each code block after LDPC rate matching may be 9804. The scaling factor set may be {1 / 2, 1, 1, 1}.

[0339] If there is a first or initial transmission, the redundant parity check blocks may be transmitted for the next transmission of the TB. The number of transmitted bits of the redundant parity check blocks may be func(func(9804 * 1 / 2) / Q m ) * Q m , where func() represents rounding down, rounding up, or rounding.

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

[0341] In some embodiments, the redundant parity check block transmission may be determined by a combination of predefined conditions and parameter sets.

[0342] 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, for BG2, h8 cannot be greater than 38240 bits, and for BG1, h8 cannot be greater than 84240 bits. In some embodiments, h6 cannot be less than the number of system code blocks associated with the redundant parity check block minus 1.

[0343] 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, for BG2, h8 cannot be less than 1 million bits, and for BG1, h8 cannot be less than 10 million bits.

[0344] In the above description, the system code block can be a code block associated with the transmitted redundant parity check block. In some embodiments, according to the CBG-based PDSCH transmission, the total code blocks of the TB can be divided into more than one code block group (CBG). In some embodiments, there can be only one redundant parity check block associated with the total code blocks in all groups. In some embodiments, there can be more than one redundant parity check block, and each redundant parity check block can be associated with the total code blocks in the corresponding code block group. The number of redundant parity check blocks can be equal to or less than the number of code block groups.

[0345] Example 2 - 4 of Embodiment: Redundant Parity Check Blocks for Retransmission

[0346] In some embodiments, the redundant parity check block can be used for the first transmission, and an additional puncturing method is described in the above Embodiments 2-1 and 2-2.

[0347] In some embodiments, under the condition of meeting the redefined conditions, the redundant parity check block can be used for a specific transmission of the TB, and the transmission method is described in the above Embodiment 2-3.

[0348] As described in Embodiment 2-4, for retransmission, the redundant parity check block can also be used to reduce the total required resources. For example, the number of resource elements used for all transmissions in which the UE successfully receives the TB can be reduced via redundant parity check block transmission by reducing the amount of scheduled resources per transmission or the total number of required transmissions.

[0349] The redundant parity check block can be transmitted based on a predefined event. The predefined event for transmission can be at least one of the following:

[0350] 1) The number of error system code blocks that the UE fails to successfully receive is less than or equal to a threshold;

[0351] 2) The number of code block groups containing the code blocks for CBG-based transmission that the UE fails to successfully receive is less than or equal to a threshold;

[0352] 3) The current time value of the transmission for the same TB, counted from the first or initial transmission, is less than or equal to a threshold and greater than another threshold;

[0353] 4) The SINR value reported before or after the most recent TB transmission is less than or equal to a threshold and greater than another threshold;

[0354] 5) Report the reporting quantity defined in Rel-16 according to the most recent CSI / synchronization signal block (CSI / SSB) measurement;

[0355] 6) The bit error rate (BER) or block error rate (BLER) evaluated by the UE is greater than the target BLER or greater than the target BLER * 0.01;

[0356] 7) The average value of the absolute value of the log-likelihood ratio (LLR) of each error code block;

[0357] 8) A new reporting quantity related to the log-likelihood ratio (LLR) of the transmitted bits relative to Rel-16;

[0358] 9) The BER of the redundant parity check block of the most recent transmission of the TB;

[0359] 10) The redundant parity check block of the most recent transmission of the TB was not successfully received;

[0360] 11) The reduced number of error systematic code blocks after receiving the redundant parity check block of the most recent transmission of the TB is greater than a threshold;

[0361] 12) The rate R of the systematic code blocks of the TB is greater than a threshold;

[0362] 13) The number of systematic code blocks of the TB is greater than a threshold; or

[0363] 14) The number of error systematic code blocks of the most recent transmission is less than a threshold.

[0364] The error code block can represent a code block that fails the code block (CB) CRC check or is not successfully received.

[0365] The error code block can represent a code block that fails the transmission block (TB) CRC check or is not successfully received.

[0366] The BER can represent the bit error rate of the TB. The BER can also represent the number of error 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 error code blocks divided by the total number of code blocks of the TB.

[0367] For example, when the UE or gNB encounters an event where the number of system codeblocks that the UE reports as not successfully received is less than or equal to a threshold, the UE or gNB may assume that the redundant parity check blocks can be transmitted. The various specific applications defined by this event are as follows:

[0368] 1) For the first retransmission, i.e., the second transmission, the event application is when the number of error codeblocks in the first or initial transmission is not less than Ce1.

[0369] 2) For the second retransmission, i.e., the third transmission, the event application is when the number of error codeblocks in the second transmission is not less than Ce2.

[0370] 3) For the third retransmission, i.e., the fourth transmission, the event application is when the number of error codeblocks in the third transmission is not less than Ce3.

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

[0372] For other next retransmissions of the TB, the condition for triggering the transmission of the redundant parity check blocks may be similar to the previous transmission of the same TB.

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

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

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

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

[0377] In some embodiments, S1 can be the addition of the SNR and Δ1 when the target BLER of the MCS for the initial transmission is 10%. In some embodiments, S2 can be the addition of the SNR and Δ2 when the target BLER of the MCS for the initial transmission is 10%. In some embodiments, S3 can be the addition of the SNR and Δ3 when the target BLER of the MCS for the initial transmission is 10%.

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

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

[0380] In some embodiments, the values of Δ1, Δ2, and Δ3 can be different from each other.

[0381] Example 3 of Embodiment: Higher - Layer Parameters Related to Redundant Parity Check Block Transmission

[0382] Higher layer parameters related to redundant parity check block transmission can include the following two types: 1) relevant UE characteristics or capabilities reported by the UE; and 2) higher layer parameters related to the resource configuration of redundant parity check block transmission.

[0383] As described herein, UE characteristics related to redundant parity check block transmission are disclosed.

[0384] UE characteristics can include at least one of the following:

[0385] 1) Characteristics for determining the number of redundant parity check blocks for transmitting the TB;

[0386] 2) Characteristics for determining the HARQ-ACK information associated with the redundant parity check block;

[0387] 3) Characteristics for determining that the UE can handle redundant parity check block transmission;

[0388] 4) Characteristics for determining the size of the transmitted redundant parity check block; or

[0389] 5) Characteristics for determining the frequency domain resources for transmitting the redundant parity check block.

[0390] Higher layer parameters related to the resource configuration for redundant parity check block transmission can include at least one of the following:

[0391] 1) Enable redundant parity check block transmission of the TB;

[0392] 2) Generate a sequence candidate list or determination process;

[0393] 3) Specific resource configuration for redundant parity check block transmission; or

[0394] 4) Search space set and CORESET configuration of PDCCH for detecting the transmission of scheduling redundant parity check blocks.

[0395] In some embodiments, high-layer parameters related to the resource configuration of redundant parity check block transmission may be included in radio resource control (RRC) signaling.

[0396] In the above description, TBS may represent the total number of information bits transmitted in the resources allocated by DCI or high-layer parameters.

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

[0398] In some embodiments, the allocated resources may be continuous in the time domain and the frequency domain.

[0399] In the above description, each coded code block of the TB may include an information bit part and a parity check bit part. In some embodiments, each code block carrying the information bits of the TB may be a systematic code block. In some embodiments, the encoder may be named a systematic encoder.

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

[0401] 1. A method performed by a wireless device (e.g., Figure 12 method 1200 shown in), comprising: receiving (1210) by the wireless device from a network device a first message that includes one or more parameters related to error correction coding; and transmitting (1220) by the wireless device to the network device a data transmission using error correction coding based on the one or more parameters.

[0402] 2. A method performed by a wireless device (e.g., Figure 13 method 1300 shown in), comprising: transmitting (1310) by the network device to the wireless device a first message that includes one or more parameters related to error correction coding; and transmitting (1320) by the network device to the wireless device a data transmission using error correction coding based on the one or more parameters after transmitting the first message.

[0403] 3. A method performed by a wireless device (e.g., Figure 14A method (e.g., method 1400 shown in []) includes: receiving (1410) by a wireless device from a network device a first message that includes one or more parameters related to error correction coding; and receiving (1420) by the wireless device from the network device a data transmission using error correction coding based on the one or more parameters.

[0404] 4. A method performed by a wireless device (e.g., Figure 15 method 1500 shown in []) includes: transmitting (1510) by a network device to the wireless device a first message that includes one or more parameters related to error correction coding; and receiving (1520) by the network device from the wireless device a data transmission using error correction coding based on the one or more parameters after transmitting the first message.

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

[0406] 6. A wireless communication method (e.g., Figure 17 method 1700 shown in []) includes: receiving (1740) by a first wireless device a data transmission including rate-matched data, wherein the rate-matched data is generated by partitioning a plurality of code blocks including at least one redundant parity check block into a first set of code blocks and a second set of code blocks according to allowed puncturing bit positions and puncturing the first set of code blocks and the second set of code blocks according to the allowed puncturing bit positions; and determining (1720) from the data transmission the data bits encoded in the data transmission.

[0407] 7. A wireless communication method (e.g., Figure 18 method 1800 shown in []) includes: generating (1810) by a first wireless device from data bits to be transmitted a plurality of code blocks including at least one redundant parity check block; partitioning (1820) the plurality of code blocks into at least a first set of code blocks and a second set of code blocks according to allowed puncturing bit positions; rate matching the plurality of code blocks by puncturing according to a puncturing pattern (1830), wherein the puncturing pattern defines the allowed puncturing bit positions for each of the plurality of code blocks; and transmitting (1840) the result of the rate matching to a second wireless device.

[0408] 8. A wireless communication method (e.g., Figure 19The method shown in (1900) includes: receiving (1910) at a first wireless device a data transmission including a plurality of code blocks, the plurality of code blocks including at least one redundant parity check block, wherein the plurality of code blocks are rate matched according to a puncturing pattern that defines allowed puncturing bit positions for each of the plurality of code blocks; and determining (1920) encoded data bits in the data transmission based on the puncturing pattern.

[0409] 9. The method according to any one of Solutions 1 - 4, wherein the first message is radio resource control (RRC) signaling, and a plurality of parameters of the first message are related to redundant parity check block transmission.

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

[0411] 11. The method according to any one of Solutions 1 - 4, 9 or 10, wherein the data transmission includes redundant parity check block transmission.

[0412] 12. The method according to any one of Solutions 1 - 4 or 9 - 11, wherein the redundant parity check blocks included in the data transmission do not include information bits of the transport block and are obtained at least through a plurality of code blocks of the transport block and a generation sequence.

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

[0414] 14. The method according to any one of Solutions 1 - 12, wherein the DCI includes a plurality of fields configured to indicate at least one of the following parameters:

[0415] An identifier for redundant parity check block transmission;

[0416] The number of a plurality of code blocks related to redundant parity check block transmission;

[0417] A generation sequence for redundant parity check block transmission;

[0418] The number of redundant parity check blocks;

[0419] A code block index related to the redundant parity check block;

[0420] A rate matching bit pattern;

[0421] The HARQ process number; or

[0422] A bitmap of the code block group

[0423] wherein the generation sequence is used to generate redundant parity check blocks, and

[0424] wherein the rate matching bit pattern is used to determine the puncturing bit positions of multiple code blocks for data transmission.

[0425] 15. The method according to solution 14, wherein the generation sequence can be determined according to at least one of the number of multiple code blocks related to the redundant parity check blocks and the number of code block groups for transmission blocks.

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

[0427] 17. The method according to any one of solutions 1 - 12 or 14, wherein one or more fields in the DCI are configured according to the high - layer parameters configuring the redundant parity check block transmission.

[0428] 18. The method according to any one of solutions 1 - 12 or 14, wherein one or more fields in the DCI are configured based on the high - layer parameters reported by the wireless device, and the high - layer parameters indicate that the wireless device is capable of performing redundant parity check block transmission.

[0429] 19. The method according to solution 14, wherein the generation sequence is indicated as the index of the list from which the generation sequence comes.

[0430] 20. The method according to solution 19, wherein the generation sequence comes from a list configured by high - layer parameters.

[0431] 21. The method according to solution 14, wherein the number of multiple code blocks related to the redundant parity check blocks is indicated as a bitmap of the total number of multiple code blocks of the transmission block.

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

[0433] 23. The method according to any one of solutions 1 - 12 or 14, wherein the DCI format is at least one of the following:

[0434] DCI format 0 - 1;

[0435] DCI format 1 - 1;

[0436] DCI format 0 - 2;

[0437] DCI format 1 - 2; or

[0438] a specific DCI format.

[0439] 24. The method according to any one of Solutions 14 or 23, wherein if at least one of the second type fields in the DCI is set to a predefined value, 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 redundant parity check block transmission.

[0440] 25. The method according to Solution 24, wherein the first type field includes at least one of the following:

[0441] Carrier indication;

[0442] Bandwidth part indication;

[0443] Frequency domain resource allocation;

[0444] Time domain resource allocation;

[0445] Rate matching indication;

[0446] HARQ process number;

[0447] Downlink allocation index;

[0448] One or more antenna ports;

[0449] First downlink allocation index;

[0450] Second downlink allocation index of DCI format 0-1;

[0451] ChannelAccess-CPext of DCI format 0-1 or DCI format 1-1;

[0452] Transmission configuration indication;

[0453] CBG transmission information (CBGTI);

[0454] CBG clearing information (CBGFI) of DCI format 1-1;

[0455] Modulation and coding scheme;

[0456] New data indication; or

[0457] Redundancy version of transmission block 1 of DCI format 1-1.

[0458] 26. The method according to Solution 24, wherein the second type field in DCI format 0-1, DCI format 1-1, DCI format 0-2, DCI format 1-2 or a specific DCI format includes at least one of the following:

[0459] Frequency domain resource allocation;

[0460] Redundancy version;

[0461] UL-SCH indication;

[0462] CSI request;

[0463] Modulation and coding scheme;

[0464] New data indication;

[0465] Redundancy version;

[0466] Modulation and coding scheme of transport block 2 in DCI format 1-1;

[0467] New data indication of transport block 2 in DCI format 1-1; or

[0468] Redundancy version of transport block 2 in DCI format 1-1.

[0469] 27. The method according to any one of solutions 24 or 26, wherein a second type field is used to identify the transmission type of the redundant parity check block transmission.

[0470] 28. The method according to solution 27, wherein the transmission type of the redundant parity check block transmission is determined by at least one of the following:

[0471] The number of scheduled redundant parity check blocks; or

[0472] The number of times of scheduled data transmission for the transport block.

[0473] 29. The method according to solution 14, wherein the number of puncturing bits of each code block among the multiple code blocks of the transport block is not greater than the number of puncturing bits of the redundant parity check block.

[0474] 30. The method according to any one of solutions 1-12 or 14, wherein the redundant parity check blocks included in the data transmission are scheduled based on at least one of the following quantities reported by the wireless device within a numerical range:

[0475] The number of code blocks of the transport block;

[0476] The number of code blocks of the transport block that the wireless device has not successfully received;

[0477] The maximum number of transmissions for the transport block; or

[0478] The most recent L1-SINR value reported by the wireless device.

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

[0480] 32. The method according to any one of Solutions 14 or 23, wherein, if there is an initial transmission of a transport block, a plurality of fields related to the redundant parity check code block are not included in the DCI format, and wherein, if there is a retransmission of the transport block, the plurality of fields related to the redundant parity check code block are included in the DCI format.

[0481] 33. The method according to any one of Solutions 5 or 6, wherein the allowed puncturing bit positions of the first set of code blocks correspond to the head end.

[0482] 34. The method according to any one of Solutions 5 or 6, wherein the allowed puncturing bit positions of the second set of code blocks correspond to the tail end.

[0483] 35. The method according to any one of Solutions 1-12 or 14, wherein the puncturing bit positions of the plurality of code blocks for the first type of transport block are overlapping and are located at the head of each of the plurality of code blocks, and wherein the puncturing bit positions of the plurality of code blocks for the second type of transport block are overlapping and are located at the tail of each of the plurality of code blocks.

[0484] 36. The method according to any one of Solutions 5 or 6, wherein the indices of the plurality of code blocks of the first type are odd numbers, and the indices of the plurality of code blocks of the second type are even numbers.

[0485] 37. The method according to any one of Solutions 5 or 6, wherein the indices of the plurality of code blocks of the first type are even numbers, and the indices of the plurality of code blocks of the second type are odd numbers.

[0486] 38. The method according to any one of Solutions 7 or 8, wherein the puncturing pattern includes non-overlapping positions of a plurality of code blocks.

[0487] 39. The method according to any one of Solutions 1-38, wherein the wireless device is a user equipment (UE).

[0488] 40. The method according to any one of Solutions 1-8, further comprising receiving an acknowledgement of the data transmission.

[0489] 41. A wireless communication device, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method according to any one of Solutions 1 to 40.

[0490] 42. A computer-readable program storage medium, on which code is stored, which, when executed by a processor, causes the processor to implement the method according to any one of Solutions 1 to 40.

[0491] Figure 20A and20B is a flowchart of a downlink data transmission scheduling process including redundant parity check blocks for wireless devices (e.g., UEs) and network devices (e.g., gNBs). For example, as described with respect to Figures 12 - 15 and as shown in Figure 20A , in some embodiments, a user equipment may receive DCI scheduling a DL data transmission, then receive the data transmission according to the scheduling received in the DCI on the PDSCH, and subsequently report a hybrid automatic repeat request (HARQ) acknowledgement for the received data transmission to the network device. Conversely, as described with respect to Figures 12 - 15 and Figure 20B , the network device transmits DCI scheduling a DL data transmission, after which the network device transmits data in the PDSCH according to the scheduling, and subsequently receives a HARQ-ACK from the receiving wireless device.

[0492] Figure 20C and 20D are flowcharts of an uplink data transmission scheduling process including redundant parity check blocks for UEs and gNBs. For example, as described with respect to Figures 12 - 15 and further shown in Figure 20C , in some embodiments, a wireless device may receive DCI scheduling an uplink transmission for the wireless device. The wireless device then transmits a data transmission on the physical uplink shared channel (PUSCH) according to the scheduling.

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

[0494] Figure 21A and 21B are flowcharts of rate matching for data transmission including redundant parity check blocks. For example, in some embodiments, a UE may generate multiple code blocks from data bits to be transmitted according to DCI, including redundant parity check blocks. The data bits may be punctured according to a rate matching pattern that defines allowed punctured data bit positions for each of the multiple code blocks.

[0495] Figure 22A block diagram representation of a part of an apparatus according to some embodiments of the presently disclosed technology. An apparatus 2205, such as a base station, a network device, or a wireless device (or UE), may include processor electronics 2210, such as a microprocessor implementing one or more of the techniques presented in this document. The apparatus 2205 may include transceiver electronics 2215 for transmitting and / or receiving wireless signals over one or more communication interfaces, such as one or more antennas 2220. The apparatus 2205 may include other communication interfaces for sending and receiving data. The apparatus 2205 may 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 may include at least a portion of the transceiver electronics 2215. In some embodiments, the disclosed techniques, modules, or functions are implemented using the apparatus 2205.

[0496] Some embodiments described herein are described in the general context of methods or processes, which may be implemented in one embodiment by a computer program product embodied in a computer-readable medium and including computer-executable instructions, such as program code, for execution by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices including, by way of example and not limitation, read only memory (ROM), random access memory (RAM), compact disc (CD), digital versatile disc (DVD), etc. Thus, the computer-readable medium may include non-transitory storage media. Generally, program modules may include routines, programs, objects, components, data structures, etc. 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 the steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents an example of corresponding acts for implementing the functions described in these steps or processes.

[0497] Some disclosed embodiments can be implemented as a device or module using hardware circuitry, software, or a combination thereof. For example, a hardware circuitry implementation may include discrete analog and / or digital components, which are, for example, integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as an application specific integrated circuit (ASIC) and / or be implemented as a field programmable gate array (FPGA) device. Some embodiments may additionally or alternatively include a digital signal processor (DSP), which is a specialized microprocessor having an architecture optimized for the operational requirements of digital signal processing associated with the disclosed functions of the present application. Similarly, the various components or sub-components within each module can be implemented in software, hardware, or firmware. Connectivity between modules and / or components within a module can be provided using any of the connection methods and media known in the art, including but not limited to communication via the Internet, wired or wireless networks using appropriate protocols.

[0498] Although this document contains many details, these details should not be construed as limiting the scope of the claimed invention or of an invention that may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described in the context of separate embodiments in this document may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. Moreover, although the features may be described above as acting in certain combinations and even initially claimed as such, in some cases one or more features from a claimed combination may be excised from the combination, and the claimed combination may be directed to a sub-combination or a variation of a sub-combination. Similarly, although the operations are depicted in the drawings in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in a sequential order, or that all of the illustrated operations be performed to achieve a desired result.

[0499] Only some embodiments and examples have been described, and other embodiments, enhancements, and variations can be implemented based on what is described and shown in this disclosure.

Claims

1. A method performed by a wireless device, comprising: Transmitting a first message between the wireless device and a network device, the first message including one or more parameters related to error correction coding; And Transmitting a data transmission between the wireless device and the network device using the error correction coding according to the one or more parameters, Wherein, the redundant parity check blocks included in the data transmission do not include the information bits of the transport block and are obtained at least through a plurality of code blocks of the transport block and a generation sequence, and Wherein, the generation sequence can be determined according to at least one of the number of code blocks related to the redundant parity check block and the number of code block groups for the transport block.

2. The method according to claim 1, wherein The first message is transmitted as downlink control information DCI having a predefined format type.

3. The method according to claim 2, wherein The DCI includes a plurality of fields configurable to indicate at least one of the following parameters: An identifier for redundant parity check block transmission; The number of code blocks related to the redundant parity check block transmission; A generation sequence for the redundant parity check block transmission; The number of redundant parity check blocks; A code block index related to the redundant parity check block; A rate matching bit pattern; A HARQ process number; or A bitmap of code block groups, Wherein the generation sequence is used to generate the redundant parity check block, and Wherein the rate matching bit pattern is used to determine the puncturing bit positions of a plurality of code blocks for the data transmission.

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

5. The method according to claim 3, wherein The generation sequence is indicated as an index of a list from which the generation sequence is derived.

6. The method according to claim 5, wherein The generation sequence comes from a list configured by a higher layer parameter.

7. The method according to any one of claims 1-3, wherein The DCI format is at least one of the following: DCI format 0-1; DCI format 1-1; DCI format 0-2; or DCI format 1-2.

8. The method according to claim 7, wherein In response to at least one of the second type fields of the DCI being set to a predefined value, at least one of the first type fields in DCI format 0-1, DCI format 1-1, DCI format 0-2 or DCI format 1-2 is interpreted as indicating information related to redundant parity check block transmission.

9. The method according to claim 7, wherein In response to the existence of an initial transmission of the transport block, a plurality of fields related to the redundant parity check code block are not included in the DCI format, and wherein, in response to the existence of a retransmission of the transport block, a plurality of fields related to the redundant parity check code block are included in the DCI format.

10. The method according to any one of claims 1-3, wherein, The puncturing bit positions of a plurality of code blocks of the first type for the transport block are overlapping and located at the head of each of the plurality of code blocks, and wherein, the puncturing bit positions of a plurality of code blocks of the second type for the transport block are overlapping and located at the tail of each of the plurality of code blocks.

11. A method performed by a network device, comprising: Transmitting a first message between the wireless device and the network device, the first message including one or more parameters related to error correction coding; And Transmitting a data transmission between the wireless device and the network device using the error correction coding according to the one or more parameters, Among them, the redundant parity check blocks included in the data transmission do not include the information bits of the transport block, and are obtained at least through a plurality of code blocks of the transport block and a generation sequence, and Among them, the generation sequence can be determined according to at least one of the number of a plurality of code blocks related to the redundant parity check block and the number of code block groups for the transport block.

12. The method according to claim 11, wherein, The first message is transmitted as downlink control information DCI with a predefined format type.

13. The method according to claim 12, wherein, The DCI includes a plurality of fields configurable to indicate at least one of the following parameters: An identifier for redundant parity check block transmission; The number of a plurality of code blocks related to the redundant parity check block transmission; A generation sequence for the redundant parity check block transmission; The number of redundant parity check blocks; A code block index related to the redundant parity check block; A rate matching bit pattern; A HARQ process number; or A bitmap of code block groups, wherein the generation sequence is used to generate the redundant parity check block, and wherein the rate matching bit pattern is used to determine the puncturing bit positions of a plurality of code blocks for the data transmission.

14. The method according to claim 13, wherein, The rate matching bit pattern includes the number of puncturing bits or corresponding puncturing bit positions of a plurality of code blocks for the data transmission.

15. The method according to claim 13, wherein, The generation sequence is indicated as an index of a list from which the generation sequence is derived.

16. The method according to claim 15, wherein, The generation sequence comes from a list configured by a high-layer parameter.

17. The method according to any one of claims 11-13, wherein, The DCI format is at least one of the following: DCI format 0-1; DCI format 1-1; DCI format 0-2; or DCI format 1-2.

18. The method according to claim 17, wherein, In response to at least one of the second type fields of the DCI being set to a predefined value, at least one of the first type fields in DCI format 0-1, DCI format 1-1, DCI format 0-2, or DCI format 1-2 is interpreted as indicating information related to redundant parity check block transmission.

19. The method according to claim 17, wherein In response to the existence of an initial transmission of the transport block, a plurality of fields related to the redundant parity check code block are not included in the DCI format, and wherein, in response to the existence of a retransmission of the transport block, a plurality of fields related to the redundant parity check code block are included in the DCI format.

20. The method according to any one of claims 11-13, wherein The puncturing bit positions of a plurality of code blocks of the first class for the transport block are overlapping and located at the head of each of the plurality of code blocks, and wherein the puncturing bit positions of a plurality of code blocks of the second class for the transport block are overlapping and located at the tail of each of the plurality of code blocks.

21. A wireless communication device, comprising a memory and a processor, wherein, The processor reads the code from the memory and implements the method according to any one of claims 1 to 20.

22. A computer-readable program storage medium, on which code is stored, and the code, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 20.

Images