Soft harq feedback reporting method in mobile communication and user equipment thereof

Abstract

Various examples are described regarding soft hybrid automatic repeat request (HARQ) feedback reporting density, enabling mechanisms, processing timelines, and codebook construction in mobile communications. An apparatus, which can be implemented in a user equipment (UE), receives one or more transmissions from a network node. The apparatus generates one or more soft HARQ feedbacks corresponding to the one or more transmissions, and then sends the one or more soft HARQ feedbacks to the network node.

Description

[0001] Cross-referencing of related patent applications

[0002] This disclosure is part of a non-provisional application claiming priority to U.S. Patent Application No. 63 / 139,466, filed January 20, 2021, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to the soft hybrid automatic repeat request (HARQ) feedback report density, enabling mechanism, processing timeline and coding construction in mobile communications. Background Technology

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the claims listed below, and are not acknowledged as prior art by virtue of their inclusion in this section.

[0005] In wireless communications, such as mobile communications under the 3rd Generation Partnership Project (3GPP) specification for 5G New Radio (NR), downlink (DL) HARQ typically refers to DL data transmitted on the Physical Downlink Shared Channel (PDSCH) that has a HARQ acknowledgment returned on the Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). When PDSCH decoding is successful, the User Equipment (UE) reports an acknowledgment (ACK) to the base station (e.g., gNB); otherwise, the UE reports a negative acknowledgment (NACK).

[0006] Outer loop link adaptation (OLLA) can be implemented at the gNB to maintain the desired block error ratio (BLER). A typical operation performed by the gNB is to increase the signal-to-noise ratio (SNR) margin by a specific value upon receiving a NACK. This results in a lower effective signal-to-interference-and-noise ratio (SINR) for modulation coding scheme (MCS) selection, leading to a lower MCS selection. The gNB can similarly operate to decrease the SNR margin upon receiving an ACK. The ratio of ACK and NACK adjustments can be varied depending on the desired BLER. OLLA works well for initial transmissions with a target BLER of 0.1 and an error rate target of approximately 10% (e.g., for enhanced mobile broadband (eMBB)). However, in ultra-reliable low-latency communication (URLLC) with low target BLER, there may not be enough NACK events for the outer loop of OLLA to converge. One way to utilize OLLA is to apply the outer loop to events before they cause block errors. This can be achieved by sending soft HARQs. For the number of HARQ feedbacks and OLLA, OLLA performance is acceptable in eMBB because the number of received NACKs is sufficient; however, this is not the case in URLLC because the number of NACKs tends to be very low. For the processing timeline, N1 is defined as the time required for PDSCH decoding and HARQ feedback preparation. However, soft HARQ preparation may require a different processing timeline. Therefore, a solution is needed for the soft HARQ feedback reporting density, enabling mechanism, processing timeline, and coding construction in mobile communications. Summary of the Invention

[0007] The following overview is illustrative only and is not intended to be limiting in any way. That is, it is provided to introduce the concept, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments are further described in the detailed description below. Therefore, the following overview is not intended to identify essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0008] The purpose of this disclosure is to provide solutions or schemes for addressing the problems described herein. More specifically, it is believed that the various schemes proposed in this disclosure provide solutions relating to soft HARQ feedback report density, enabling mechanisms, processing timelines, and coding constructions in mobile communications. For example, since OLLA performance is acceptable in eMBB, a reduced density can be implemented for soft HARQ reports, for example, one soft HARQ report for every M (>1) existing HARQ reports.

[0009] In one aspect, a method may involve receiving one or more transmissions from a network node. The method may also involve generating one or more soft HARQ responses corresponding to the one or more transmissions. The method may further involve sending one or more soft HARQ responses to the network node.

[0010] In another aspect, an apparatus may include a transceiver and a processor coupled to the transceiver. The transceiver may be configured to communicate wirelessly. The processor may be configured to receive one or more transmissions from a network node via the transceiver; generate one or more soft HARQ feedbacks corresponding to the one or more transmissions; and send one or more soft HARQ feedbacks to the network node via the transceiver.

[0011] It is worth noting that while the descriptions provided herein can be implemented in the context of some radio access technologies, networks, and network topologies such as 5G / NR mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of radio access technologies, networks, and network topologies, such as, but not limited to: Long Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-Everything (V2X), and Non-Terrestrial Network (NTN) communications. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0012] The accompanying drawings are included to provide a further understanding of this disclosure and are incorporated in and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that, in order to clearly illustrate the concept of the present disclosure, the drawings are not necessarily to scale and some components may be shown out of proportion to actual dimensions in a practical implementation.

[0013] Figure 1 This is a diagram of an example network environment in which various proposed schemes according to this disclosure can be implemented.

[0014] Figure 2This is a schematic diagram of an example scenario based on the proposed solution according to this disclosure.

[0015] Figure 3 This is a block diagram of an example communication system according to an embodiment of the present disclosure.

[0016] Figure 4 This is a flowchart of an example process according to an embodiment of the present disclosure. Detailed Implementation

[0017] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that the description of this disclosure is thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and technologies may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0018] Overview

[0019] Embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions related to soft HARQ feedback reporting density, activation mechanisms, processing timelines, and coding structures in mobile communications. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described individually below, two or more of these possible solutions may be implemented in one combination or another.

[0020] Figure 1 Example network environment 100 is illustrated, in which various solutions and schemes according to this disclosure can be implemented. (See also...) Figure 1 Network environment 100 may involve a UE 110 that wirelessly communicates with wireless network 120 (e.g., a 5G NR mobile network or another type of network such as NTN). UE 110 may wirelessly communicate with wireless network 120 via a base station or network node 125 (e.g., an eNB, gNB, or a Transmit and Receive Point (TRP)). In network environment 100, UE 110 and wireless network 120 (via network node 125) may implement various schemes related to soft HARQ feedback report density, enabling mechanisms, processing timelines, and coding structures in mobile communications, as described below.

[0021] Under the first proposed scheme according to this disclosure, UE 110 can report to network node 125 a percentage of soft information measured at UE 110. In this disclosure, the term "soft information" refers to information that represents a value or information that is not a binary value but rather a binary value, thereby achieving finer resolution. For example, the raw bit error rate (BER) before recording can be represented by soft information in soft HARQ feedback. Therefore, UE 110 can report the measured or estimated soft information as a percentage value for soft HARQ feedback. Under the proposed scheme, UE 110 can convert a precise soft information value into a percentage soft information value, which is obtained by dividing the measured / estimated soft information value by the maximum value of that soft information. Thereafter, UE 110 can report a precise percentage or a quantized percentage of the soft information, or UE 110 can map the percentage information to soft ACK and / or soft NACK. For example, considering that the soft information is obtained at UE 110 through low-density parity-check (LDPC) decoding iterations equal to 9 iterations, and that the maximum number of LDPC decoding iterations for UE 110 is 12 iterations, UE 110 can determine or calculate the percentage as follows:

[0022]

[0023] The UE 110 can then report a precise (or quantified) percentage information value. Alternatively or additionally, the UE 110 can map this percentage to a soft ACK / soft NACK.

[0024] Under the proposed scheme, different information source options can be defined and utilized. For example, information sources may include, but are not limited to: the number of LDPC decoding iterations, the time required to complete the PDSCH decoding process, the log-likelihood ratio (LLR) value (or amplitude only) and / or variance, the flipped bit, and the original BER.

[0025] Under the second proposed scheme according to this disclosure, UE 110 can reduce soft HARQ based on time. That is, the number of soft HARQ feedbacks reported by UE 110 to network node 125 can be lower than the existing number of HARQ feedbacks. The reduction in soft HARQ feedback reports can be based on reducing the number of soft HARQ feedbacks (N≥1) in a given time period of specific N time units. For example, the granularity of N time units can be sub-slots, time slots, or radio frames. Furthermore, the value of N can be set, applied, or configured through different options. In the first option (option 1), the value of N can be configured / applied / set through higher-layer parameters (e.g., Radio Resource Control (RRC) parameters). In the second option (option 2), the value of N can be pre-configured individually for each downlink control information (DCI) format, and the DCI that selects the PUCCH resources used for PUCCH transmission carrying HARQ can also select the value of N. In the third option (Option 3), the value of N can be pre-configured individually for each HARQ format (e.g., Type 1, Type 2, Type 3), and UE 110 can select the value of N previously configured via RRC for each HARQ format. In the fourth option (Option 4), the value of N can be configured or applied according to the BLER target. In the fifth option (Option 5), the value of N can be configured or applied according to each configured bandwidth part (BWP) and / or configured parameter set (e.g., bandwidth subcarrier spacing). In the sixth option (Option 6), the value of N can be configured or applied according to the UE (e.g., the UE calculates the value of N itself). In the seventh option (Option 7), the value of N can be configured or applied according to codebook priority. In the eighth option (Option 8), different combinations of two or more of the above options can be used, applied, or otherwise configured.

[0026] Under the proposed scheme, the measurement of the soft HARQ feedback report every N time units can be based on factors of different options. In the first option (Option 1), the measurement of the soft HARQ feedback report can be based on N PDSCHs from N sub-slots, N time slots, or N radio frames. In the second option (Option 2), the measurement of the soft HARQ feedback report can be based on a single PDSCH every N time units, where the PDSCH can be selected as the PDSCH with the worst or best decoding performance. In the third option (Option 3), the measurement of the soft HARQ feedback report can be based on multiple PDSCHs from N time units, where the multiple PDSCHs can be selected as the PDSCH with the worst or best decoding performance. In the fourth option (Option 4), the measurement of the soft HARQ feedback report can be based on a successfully decoded PDSCH (e.g., a PDSCH that has passed the cyclic redundancy check (CRC)). In the fifth option (Option 5), the measurement of the soft HARQ feedback report can be based on the PDSCH that was not successfully decoded (e.g., the PDSCH that failed the CRC test).

[0027] Under the third proposed scheme of this disclosure, a new UE processing timeline can be introduced to account for the preparation time required for soft HARQ feedback. That is, a new UE processing timeline can be defined to take into account the soft HARQ preparation period. The new UE processing timeline can be defined to include PDSCH decoding time as well as the preparation time for soft HARQ feedback and existing HARQ feedback. In some embodiments, the new UE processing timeline can be based on UE capabilities and / or parameter sets. In some embodiments, the existing UE processing timeline (e.g., N1) can be extended to accommodate the preparation time required for soft HARQ feedback. For example, the new UE processing timeline can be represented as N1+d, where d represents the extension of the time period required for soft HARQ preparation. In one approach, the processing timeline N1 can be extended without any conditions. For example, a specific time period (e.g., one or two symbols) can be added to N1 to account for the latency required for soft HARQ preparation. In another approach, the N1 processing timeline can be extended under certain conditions. For example, conditional time variables can be added to the processing timeline N1 based on different conditions (e.g., soft HARQ generation method, parameter set, etc.).

[0028] In some implementations, new UE processing timelines can be extended based on different UE capabilities. For example, two processing timeline capabilities can be defined for this purpose. In some implementations, the required processing time can be reported by UE 110 as a UE capability. For example, in the case where the new timeline is N1+d, where d represents the time period extension required for soft HARQ preparation, the value of d can be reported to network node 125 as a UE capability. In some implementations, new UE processing timelines can be extended based on a set of parameters (e.g., subcarrier spacing). In some implementations, new UE processing timelines can be applied, set, or otherwise configured using higher-level parameters (e.g., RRC parameters).

[0029] In some implementations, new UE processing timelines can be applied or configured based on the configuration of the demodulation reference signal (DMRS) location, where the DMRS location configuration can be configured in DMRS-DownlinkConfig. In some implementations, new UE processing timelines can be extended based on the PDSCH mapping type. For example, PDSCH mapping A and PDSCH mapping B can each have different processing timeline durations. In some implementations, new UE processing timelines can be extended based on the type or generation method of soft HARQ feedback. In some implementations, new UE processing timelines can be extended based on the type of soft HARQ feedback or the method of reporting or signaling soft HARQ feedback. In some implementations, new UE processing timelines can be extended based on the soft HARQ feedback reporting granularity. For example, a soft HARQ generated and reported per transport block (TB) can have a different processing timeline duration than another soft HARQ generated and reported per code block group (CBG). In some implementations, new UE processing timelines can be extended based on the soft HARQ feedback reporting density. For example, different options and embodiments in the first proposed scheme can have different processing timeline periods. In some implementations, the new UE processing timeline can be changed according to the number of symbols per PDSCH (e.g., PDSCH size). In some implementations, the new UE processing timeline can be defined, applied, or configured according to the configured BWP size. In some implementations, the new UE processing timeline can start from the end of the last symbol of the PDSCH carrying the acknowledged TB or CBG.

[0030] Under the scheme proposed in the fourth aspect of this disclosure, soft HARQ can be enabled and disabled based on priority. That is, soft HARQ can be enabled and disabled separately for high priority and low priority. In some embodiments, soft HARQ can be enabled / disabled based on the priority of HARQ-ACK feedback. In some embodiments, the priority can be indicated in the DCI or configured in the RRC. In some embodiments, soft HARQ can be configured or enabled for high priority. Alternatively, soft HARQ can be configured or enabled for low priority. In some embodiments, soft HARQ can be configured or enabled for both high priority and low priority.

[0031] Under the scheme proposed in the fifth aspect of this disclosure, soft HARQ can be enabled and disabled based on the PDSCH scheduling mechanism. In some embodiments, soft HARQ can be enabled and disabled separately for dynamic PDSCH scheduling and semi-static PDSCH scheduling. For example, soft HARQ can be enabled only for HARQ-ACK feedback of dynamic PDSCH scheduling. Furthermore, soft HARQ can be enabled only for semi-persistent scheduling (SPS) of PDSCH. In some embodiments, soft HARQ can be enabled and disabled based on the DCI format. In one option, soft HARQ can be enabled and disabled for PDSCH scheduled by DCI 1_0. In another option, soft HARQ can be enabled and disabled for PDSCH scheduled by DCI 1_1. In yet another option, soft HARQ can be enabled and disabled for PDSCH scheduled by DCI 1_2. In yet another option, soft HARQ can be enabled and disabled for PDSCH scheduled by either DCI 1_1 or DCI 1_2. In some implementations, soft HARQ can be enabled and disabled on a per-SPS configuration basis.

[0032] Regarding the codebook generation rules for reporting soft ACK / NACK instead of hard ACK / NACK, the network node 125 can configure the UE 110 to generate soft ACK / NACK bits instead of hard ACK / NACK bits for all bits of the selected codebook or all codebooks. In the proposed scheme below, all codebook formats can be systematically extended from hard ACK / NACK bits to soft ACK / NACK bits.

[0033] Under the sixth scheme proposed according to this disclosure, soft ACK and soft NACK can be encoded using a supplementary set of values ​​based on the same digital representation (e.g., bit width). Specific values ​​for soft NACK can be reserved to indicate unreported PDSCH (e.g., no scheduling detected, or scheduling reported for a different uplink slot or sub-slot ACK / NACK), or this information can be transmitted separately within the same codebook, or transmitted otherwise after the HARQ codebook is sent. It is noteworthy that the UE (e.g., UE 110) can be configured by the network (e.g., via network node 125 from network 120) to generate soft ACK / NACK bits instead of hard ACK / NACK bits for all bits or all codebooks of the selected codebook. Therefore, under the sixth scheme proposed, all codebook formats can be systematically extended from hard ACK / NACK bits to soft ACK / NACK bits. In some embodiments, specific values ​​can be reserved for unreported PDSCH.

[0034] In some implementations, there is no specific value reserved for unreported PDSCH, where the same value is reserved for other failure cases. In some implementations, each soft ACK / NACK feedback may occupy two bits. Of these two bits, three values ​​may indicate that successful reception will be reported in a given codebook, while a fourth value may indicate the opposite: PDSCH failure, or no PDCCH received, or the result reported in a different uplink time slot or sub-time slot (e.g., semi-static HARQ codebook generation). In some implementations, dynamic clearance and SPS transmission may be acknowledged by soft ACK / NACK, and each corresponding hard bit may be replaced by B bits of soft value.

[0035] Under the scheme proposed in the seventh aspect of this disclosure, soft ACK and soft NACK can use 2 n-1 is used for OLLA tracking. The final value can be NACK, which can also be generated when packets / CBG pass through at very low amplitudes. Based on the assumption that NACK is infrequent, supplementary information may be obtained separately. In the first option, the same codebook can provide supplementary information. In the second option, supplementary information can be propagated separately and parsed afterward. Utilizing the fact that network node 125 knows the after-the-fact information, network node 125 can trigger a retransmission (because the joint probability of NACK occurrence plus HARQ codebook loss is very small). For example, supplementary information can be appended to subsequent HARQ codebooks, implicitly increasing their size. As another example, supplementary information can be appended to subsequent aperiodic channel state information (A-CSI) or periodic CSI (P-CSI), implicitly increasing their size. As yet another example, supplementary information can be provided using any other configured transmission opportunity (similar to a scheduling request (SR)). In the third option, information can be split between the first and second options described above. When all options are applied, supplementary information may include the distinction between failure and “near-missing errors” (which can be differentiated across multiple levels), similar information about the PDCCH of the packet that generated the NACK, and any other information related to the cause of failure, such as DMRS-based estimates (e.g., channel, noise, SNR, and Doppler), the number of code blocks (CBs), which CB(s) failed, and so on. When applying the second and third options, supplementary information may carry CSI information measured on the DMRS / data tone of the passed packets. It can be assumed that each HARQ codebook generates at most a single NACK. In the case of two NACKs generated, the information content can be reduced. For example, the same, reduced information can be carried for each NACK. Alternatively, information about the first and / or last NACK can be carried.

[0036] It is worth noting that the threshold can be configured to indicate that an ACK near-miss event is closer to a decoding failure and is used to detect sudden channel degradation (e.g., due to interference). Similar to NACK, the temporal proximity of ACK near-miss events can trigger large jumps and reduce the confidence of previously acquired statistical parameters. Therefore, NACK and ACK near-miss events can have similar effects on OLLA. In the case of ACK near-miss events, although rare, retransmissions are allowed, and NACK and ACK near-misses can be reported with the same value corresponding to NACK. For post-event differentiation between the two events, adding bits to the next codebook will be sufficient. This concept can be extended to post-event reporting of other information, such as the cause of failure (e.g., PDCCH error versus PDSCH error). Scheduling can use a combination of the most pessimistic assumptions until post-event information is available.

[0037] Under the scheme proposed in the eighth aspect of this disclosure, only type 2 and type 3 codebooks can use soft HARQ.

[0038] Under the scheme proposed according to the ninth aspect of this disclosure, when spatial bundling is configured, in the event of decoding failure at any layer, the soft ACK / NACK bits can be bundled by reporting the worst value. In the event of successful decoding of the bundled bits, the minimum or average value representing the reception quality can be used.

[0039] Regarding aggregated measurement reports, UE 110 can be configured to append CSI information to a proposed generated codebook generated using a traditional codebook based on binary ACK / NACK or soft ACK. The appended CSI information can be based on an aggregation of measurements across multiple CBGs, TBs, and / or PDSCHs. The set of PDSCH data packets involved in the aggregated measurement can be: (a) the same set as the data packets acknowledged in the codebook, or (b) the set of most recently received packets in the sequence. One or two reports can be appended based on selective aggregation. In the first option, only successful CBGs / packets can affect the aggregated information. In the second option, only failed CBGs / packets can affect the aggregated information. In the third option, two reports can be appended, one using the first option and the other using the second option. In some implementations, the aggregated value can describe the packet's BER probability distribution (e.g., mean, standard deviation, estimated top 5%, etc.).

[0040] It is worth noting that supplementary information for NACKs (e.g., PDSCH decoding failure or PDCCH error) may be uneconomical to transmit supplementary information for every soft ACK / NACK since NACKs are infrequent. However, it can be assumed that NACK occurs at most once for any HARQ codebook; therefore, the placeholder bits for supplementary information for NACKs in each HARQ codebook only need to be reserved once. To even save placeholder bits, the information can be piggybacked on the next HARQ. Using this technique, similar errors can also be reported as NACKs and subsequently distinguished relative to NACKs based on supplementary information. The aim is to save soft ACK bits and to spend available levels on frequently occurring values.

[0041] Under the scheme proposed in the tenth aspect of this disclosure, supplementary information for NACK is available in the UE (e.g., UE 110). This information may include, for example, the following: (a) failure due to PDCCH error or PDSCH decoding; (b) failure or similar error reported by NACK; (c) DMRS-based information about the failure or data-based quality information (e.g., BLER) about similar errors; and (d) if TB fails, one or more CBs fail, and information about whether this is due to local interference peaks or notch filters in selective fading.

[0042] Under the scheme proposed in eleventh of this disclosure, the supplementary information for the NACK can be transmitted as part of the same HARQ codebook as the NACK. Placeholder bits can be appended to all HARQs, and the placeholder bits are sufficient for a single NACK. In cases where multiple NACKs occur infrequently, or where the information for each NACK is reduced, or where only the last NACK has supplementary information.

[0043] Under the scheme proposed in the twelfth of this disclosure, supplementary information for NACK can be transmitted as part of a HARQ codebook, which is first scheduled after a NACK is reported and has been decoded by the gNB (e.g., network node 125) (as specified in the N1 timeline). Supplementary information can also be appended to multiple NACKs. This proposed scheme can be combined with the scheme proposed in the eleventh, in which case supplementary information can be split between two codebooks. The gNB can apply the worst-case assumption / combination of assumptions for defensive scheduling to NACK until supplementary information is available. For example, retransmission can be performed if the distinction between a NACK event and a near error event awaits supplementary information. As another example, statistics can be reset in both NACK and near error cases. As a variant, post-hoc information can use a single bit to distinguish near errors (e.g., bit = 0) and NACKs (e.g., bit = 1) and can trigger a scheduling request (SR).

[0044] Under the scheme proposed in the thirteenth aspect of this disclosure, on each CB, a single metric or any subset of metrics can be measured from the following set: LDPC iterations, check node (CN) updates, variable node clipping (VC) updates, LDPC processing cycles, toggled bits between the input and output of the LDPC decoder, the history of toggled bits for each cycle of LDPC decoding, the average SNR at the input of the LDPC decoder, mutual information (MI) between LLRs, the raw BER at the input of the derate matcher, the SNR at the input of the derate matcher, and the magnitude and variance of the LLR values ​​after receive combining and / or derate matching. The subset of metrics can be varied by the reported subrange. In some embodiments, padding bits can be excluded from the derate matcher when counting toggled bits. Alternatively, padding bits can be included in the derate matcher with a weight (e.g., 0.5) when counting toggled bits. In some embodiments, toggled bits can be measured relative to the input of the soft combiner, rather than relative to the output of the soft combiner. In some implementations, the flipped bits can be measured only for the information bits. Alternatively, measurements can be performed on all flipped bits. Figure 2An example scenario 200 is illustrated for metric calibration relative to the effective SNR under the scheme proposed in the thirteenth paper. In the case of additive white Gaussian noise (AWGN) and ideal channel estimation (CE) or noise estimation (NE), there is only a 1 dB offset between the antenna-SNR and the post-combining effective SNR. Unlike the original BER and other metrics, the BLER curve is much steeper.

[0045] Under the scheme proposed in section fourteen of this disclosure, with delta-SNR = fnc2(MCS) ref ,BLEP ref ,BLEP) and delta-log-BLER = fnc1(MCS ref ,BLEP ref Reference MCS used together with BLEP) ref It can be either: (a) the latest PDSCH successfully received within the same codebook; or (b) the MCS used by each PDSCH that reported delta-SNR. (Refer to BLER) ref It can be configured separately from the Channel Quality Indicator (CQI) BLER target, and separately for low-priority transmissions and high-priority transmissions, as well as for initial transmissions or retransmissions. See BLER for reference. ref It can be configured separately from the CQI BLER target, and separately for low-priority and high-priority transmissions, as well as for initial transmissions or retransmissions. MCS ref Similar options can be supported.

[0046] Illustrative Implementation

[0047] Figure 3 An example communication system 300 having at least example device 310 and example device 320 according to embodiments of the present disclosure is illustrated. Each of device 310 and device 320 can perform various functions to implement the schemes, techniques, processes, and methods described herein relating to soft HARQ feedback report density, activation mechanisms, processing timelines, and coding structures in mobile communications, including various schemes described with respect to the proposed designs, concepts, schemes, systems, and methods described above. This includes network environment 100 and the processes described below.

[0048] Each of devices 310 and 320 may be part of an electronic device, which may be a network device or a UE (e.g., UE 110) such as a portable or mobile device, a wearable device, a vehicle device or vehicle, a wireless communication device, or a computing device. For example, each of devices 310 and 320 may be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet computer, laptop computer, or notebook computer. Each of devices 310 and 320 may also be part of a machine-type device, which may be an IoT device such as a fixed or stationary device, a home device, a roadside unit (RSU), a wired communication device, or a computing device. For example, each of devices 310 and 320 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. When implemented in or as a network device, device 310 and / or device 320 may be implemented in an eNodeB in an LTE, LTE Advanced, or LTE Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.

[0049] In some embodiments, each of devices 310 and 320 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Complex Instruction Set Computing (CISC) processors, or one or more Reduced Instruction Set Computing (RISC) processors. In the various embodiments described above, each of devices 310 and 320 may be implemented in or as a network device or UE. Each of devices 310 and 320 may include... Figure 3 At least some of the components shown are, for example, processor 312 and processor 322, respectively. Each of devices 310 and 320 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of this disclosure, and therefore, for simplicity and brevity, such components of devices 310 and 320 are not included in the present disclosure. Figure 3 It is shown in the image and not described below.

[0050] In one aspect, each of processors 312 and 322 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term “processor” is used herein to refer to processors 312 and 322, according to this disclosure, in some embodiments each of processors 312 and 322 may include multiple processors, while in other embodiments it may include a single processor. In another aspect, each of processors 312 and 322 may be implemented as hardware (and optionally, firmware) having electronic components, wherein the electronic components include, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes configured and set to implement a particular purpose according to this disclosure. In other words, in at least some embodiments, each of processors 312 and 322 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including tasks related to soft HARQ feedback reporting density, activation mechanisms, processing timelines, and coding structures in mobile communications according to various embodiments of this disclosure.

[0051] In some embodiments, device 310 may further include a transceiver 316 coupled to processor 312. Transceiver 316 is capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 316 is capable of wirelessly communicating with different types of wireless networks using different Radio Access Technologies (RATs). In some embodiments, transceiver 316 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, transceiver 316 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 320 may further include a transceiver 326 coupled to processor 322. Transceiver 326 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 326 is capable of wirelessly communicating with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 326 may be equipped with multiple antenna ports (not shown), for example, four antenna ports. That is, transceiver 326 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0052] In some embodiments, device 310 may further include a memory 314 coupled to and accessible by processor 312 and capable of storing data therein. In some embodiments, device 320 may further include a memory 324 coupled to and accessible by processor 322 and capable of storing data therein. Each of memory 314 and memory 324 may include a random access memory (RAM) type such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively or additionally, each of memory 314 and memory 324 may include a read-only memory (ROM) type such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM). Alternatively or additionally, each of the memories 314 and 324 may include a type of non-volatile random access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0053] Each of devices 310 and 320 may be a communication entity capable of communicating with each other using the various schemes proposed in this disclosure. For illustrative and non-limiting purposes, a description of the capabilities of device 310 as a UE (e.g., UE 110) and device 320 as a network node (e.g., network node 125) of a wireless network (e.g., network 120 as a 5G / NR mobile network) is provided below.

[0054] Under various proposed schemes of this disclosure relating to the soft HARQ feedback reporting density, enabling mechanism, processing timeline, and coding structure in mobile communications, the processor 312 in UE 110 or the apparatus 310 implemented as UE 110 can receive one or more transmissions (e.g., PDSCH transmissions) from a network node of a wireless network (e.g., apparatus 320 as network node 125 of wireless network 120) via transceiver 316. Furthermore, the processor 312 can generate one or more soft HARQ feedbacks corresponding to the one or more transmissions. Additionally, the processor 312 can send one or more soft HARQ feedbacks to the network node via transceiver 316.

[0055] In some implementations, the reports in one or more soft HARQ feedbacks include: measured or estimated soft information in the form of percentage values ​​of one or more soft HARQ feedbacks, where the percentage value may be the ratio of the measured or estimated value of the soft information to the maximum value of the soft information. In some implementations, the soft information may include information about one or more of the following: (a) the number of LDPC decoding iterations; (b) the amount of time required to complete the PDSCH decoding process; (c) the LLC value; (d) the LLR variance; (e) the number of flipped bits; and (f) the raw BER.

[0056] In some implementations, the number of one or more soft HARQ feedbacks can be less than the number of existing HARQ feedbacks, based on the reduction in the number of soft HARQ feedbacks within a time period of N time units. In some implementations, the granularity of N time units can be a sub-slot, a time slot, or a radio frame.

[0057] In some implementations, the measurement of the soft HARQ feedback report every N time units may be based on one of the following: (a) N PDSCHs from N sub-slots, N time slots, or N radio frames; (b) one or more PDSCHs every N time units, wherein the PDSCHs are selected due to having the worst or best decoding performance; (c) one or more PDSCHs that have been successfully decoded; and (d) one or more PDSCHs that have not been successfully decoded.

[0058] In some implementations, the processing timeline associated with preparing one or more soft HARQ feedbacks may be based on one or more of the following: (a) UE capabilities; (b) parameter set; (c) existing UE processing timeline plus extension; (d) DMRS location configuration; (e) PDSCH mapping type; (f) type or method of generating one or more soft HARQ feedbacks; (g) type or method of reporting or signaling one or more soft HARQ feedbacks; (h) soft HARQ feedback reporting granularity; (i) soft HARQ feedback reporting density; (j) number of symbols per PDSCH; (k) configured BWP size; and (l) time period starting from the end of the last symbol of the PDSCH carrying the acknowledged TB or CBG.

[0059] In some implementations, prioritization of HARQ-ACK feedback enables or disables the generation and transmission of one or more soft HARQ feedbacks. In some implementations, the priority can be indicated in the DCI or configured in the RRC signal.

[0060] In some implementations, the generation and transmission of one or more soft HARQ feedbacks can be enabled or disabled based on the PDSCH scheduling mechanism by one or more of the following: (a) enabled for HARQ-ACK feedback or dynamic scheduling of PDSCH; (b) enabled for SPS of PDSCH; (c) enabled or disabled for PDSCH scheduled by DCI format 1_0, 1_1 or 1_2; and (d) enabled or disabled according to SPS configuration.

[0061] In some implementations, one or more soft HARQ feedbacks may include at least one soft ACK or at least one soft NACK, or both soft ACK and soft NACK. In some implementations, the soft ACK and soft NACK may be encoded using a complementary set of values ​​based on the same numerical representation. In some implementations, a specific value in the soft NACK may indicate an unreported PDSCH.

[0062] In some implementations, in generating one or more soft HARQ feedbacks, processor 312 can use 2... for OLLA tracking. n -1 value is used to generate at least one soft ACK, at least one soft NACK, or both soft ACK and soft NACK. In some implementations, n may represent the value of the soft NACK.

[0063] In some implementations, in generating one or more soft HARQ feedbacks, processor 312 may use type-2 or type-3 codebooks to generate one or more soft HARQ feedbacks.

[0064] In some implementations, in generating one or more soft HARQ feedbacks, processor 312 may generate at least one soft ACK or at least one soft NACK, or both soft ACK and soft NACK. In some implementations, the bits of soft ACK and soft NACK may be bundled by reporting the worst-case value in response to spatial bundling being configured and decoding failure occurring. In some implementations, a minimum or average value representing the reception quality may be reported in response to successful bundled decoding.

[0065] In some implementations, during the generation of one or more soft HARQ feedbacks, processor 312 may attach CSIs to a codebook generated using soft ACKs. In some implementations, the attached CSIs may be based on aggregated measurements across multiple CBGs, TBs, or PDSCHs.

[0066] In some implementations, the set of PDSCH data packets involved in the aggregation measurement may be the same as the set of data packets confirmed in the codebook. In some implementations, the set of PDSCH data packets involved in the aggregation measurement may include the set of most recently received packets in the sequence.

[0067] In some implementations, one or more soft HARQ feedbacks may include NACKs with supplemental information indicating one or more of the following: (a) failure due to PDCCH error or PDSCH decoding; (b) decoding failure or similar error; (c) DMRS-based information about the failure or data-based quality information about the similar error; and (d) one or more failed CBs.

[0068] In some implementations, one or more soft HARQ feedbacks may include NACK along with supplemental information for NACK, and the supplemental information is part of the same HARQ codebook as NACK, wherein the codebook has enough placeholder bits to satisfy a single NACK appended to multiple HARQ feedbacks.

[0069] In some implementations, one or more soft HARQ feedbacks may include a NACK along with supplemental information to the NACK, which is part of a HARQ codebook that is first scheduled after the NACK is reported to and decoded by the network node.

[0070] In some implementations, during the generation of one or more soft HARQ feedbacks, processor 312 may measure one or more metrics on each codebook associated with one or more transmissions. In some implementations, one or more metrics may include one or more of the following: (a) one or more LDPC iterations; (b) one or more check node (CN) updates; (c) one or more LDPC processing cycles; (d) one or more bit flips between the input and output of the LDPC decoder; (e) the bit flip history for each cycle of LDPC decoding; (f) the average SNR at the input of the LDPC decoder; (g) the mutual information between LLRs; (h) the raw BER at the input of the derate matcher; (i) the SNR at the input of the derate matcher; and (j) the magnitude and variance of the LLR values ​​after receive combining or derate matching.

[0071] In some implementations, the reference MCS used in generating one or more soft HARQ feedbacks may be the latest PDSCH that was successfully received using the same codebook, or the MCS level of each PDSCH that reported SNR changes (e.g., delta-SNR).

[0072] Example Process

[0073] Figure 4 An example flow 400 according to an embodiment of this disclosure is shown. Flow 400 may represent aspects of implementing the various proposed designs, concepts, schemes, systems, and methods described above, whether partially or completely, including those related to those described above. More specifically, flow 400 may represent an aspect of proposed concepts and schemes related to soft HARQ feedback reporting density, enabling mechanisms, processing timelines, and coding construction in mobile communications. Flow 400 may include one or more operations, actions, or functions as shown in one or more of blocks 410, 420, and 430. Although illustrated as discrete blocks, depending on the desired implementation, the individual blocks of flow 400 may be divided into additional blocks, combined into fewer blocks, or eliminated. Furthermore, the blocks / sub-blocks of flow 400 may be... Figure 4 The process can be executed in the order shown, or alternatively in a different order. Furthermore, one or more blocks / sub-blocks of process 400 can be executed iteratively. Process 400 can be implemented by or within devices 310 and 320 and any variations thereof. For illustrative purposes only and without limitation, process 400 is described below in the context of device 310 as a UE (e.g., UE 110) and device 320 as a communication entity (e.g., a network node or base station of a wireless network (e.g., wireless network 120)). Process 400 may begin at block 410.

[0074] At 410, process 400 may involve the processor 312 of device 310 receiving one or more transmissions (e.g., PDSCH transmissions) from a network node of the wireless network (e.g., device 320 as network node 125 of wireless network 120) via transceiver 316. Process 400 may proceed from 410 to 420.

[0075] At 420, process 400 may involve processor 312 generating one or more soft HARQ feedbacks corresponding to one or more transmissions. Process 400 may proceed from 420 to 430.

[0076] At 430, process 400 may involve processor 312 sending one or more soft HARQ responses to network nodes via transceiver 316.

[0077] In some implementations, the reports in one or more soft HARQ feedbacks include: measured or estimated soft information in the form of percentage values ​​of one or more soft HARQ feedbacks, where the percentage value may be the ratio of the measured or estimated value of the soft information to the maximum value of the soft information. In some implementations, the soft information may include information about one or more of the following: (a) the number of LDPC decoding iterations; (b) the amount of time required to complete the PDSCH decoding process; (c) the LLC value; (d) the LLR variance; (e) the number of flipped bits; and (f) the raw BER.

[0078] In some implementations, the number of one or more soft HARQ feedbacks can be less than the number of existing HARQ feedbacks, based on the reduction in the number of soft HARQ feedbacks within a time period of N time units. In some implementations, the granularity of N time units can be a sub-slot, a time slot, or a radio frame.

[0079] In some implementations, the measurement of the soft HARQ feedback report every N time units may be based on one of the following: (a) N PDSCHs from N sub-slots, N time slots, or N radio frames; (b) one or more PDSCHs every N time units, wherein the PDSCHs are selected due to having the worst or best decoding performance; (c) one or more PDSCHs that have been successfully decoded; and (d) one or more PDSCHs that have not been successfully decoded.

[0080] In some implementations, the processing timeline associated with preparing one or more soft HARQ feedbacks may be based on one or more of the following: (a) UE capabilities; (b) parameter set; (c) existing UE processing timeline plus extension; (d) DMRS location configuration; (e) PDSCH mapping type; (f) type or method of generating one or more soft HARQ feedbacks; (g) type or method of reporting or signaling one or more soft HARQ feedbacks; (h) soft HARQ feedback reporting granularity; (i) soft HARQ feedback reporting density; (j) number of symbols per PDSCH; (k) configured BWP size; and (l) time period starting from the end of the last symbol of the PDSCH carrying the acknowledged TB or CBG.

[0081] In some implementations, the generation and transmission of one or more soft HARQ feedbacks can be enabled or disabled based on the priority of the HARQ-ACK feedback. In some implementations, the priority can be indicated in the DCI or configured in the RRC signal.

[0082] In some implementations, the generation and transmission of one or more soft HARQ feedbacks can be enabled or disabled based on the PDSCH scheduling mechanism by one or more of the following: (a) enabled for HARQ-ACK feedback or dynamic scheduling of PDSCH; (b) enabled for SPS of PDSCH; (c) enabled or disabled for PDSCH scheduled by DCI format 1_0, 1_1 or 1_2; and (d) enabled or disabled according to SPS configuration.

[0083] In some implementations, one or more soft HARQ feedbacks may include at least one soft ACK or at least one soft NACK, or both soft ACK and soft NACK. In some implementations, the soft ACK and soft NACK may be encoded using a complementary set of values ​​based on the same numerical representation. In some implementations, a specific value in the soft NACK may indicate an unreported PDSCH.

[0084] In some implementations, in generating one or more soft HARQ feedbacks, process 400 may involve processor 312 using 2 for OLLA tracking. n -1 value is used to generate at least one soft ACK, at least one soft NACK, or both soft ACK and soft NACK. In some implementations, n may represent the value of the soft NACK.

[0085] In some implementations, in generating one or more soft HARQ feedbacks, process 400 may involve processor 312 using a type-2 or type-3 codebook to generate one or more soft HARQ feedbacks.

[0086] In some implementations, in generating one or more soft HARQ feedbacks, process 400 may involve processor 312 generating at least one soft ACK or at least one soft NACK, or both soft ACK and soft NACK. In some implementations, the bits of soft ACK and soft NACK can be bundled by reporting the worst-case value in response to spatial bundling being configured and decoding failure occurring. In some implementations, a minimum or average value representing the reception quality can be reported in response to successful bundled decoding.

[0087] In some implementations, in generating one or more soft HARQ feedbacks, process 400 may involve processor 312 attaching a CSI to a codebook generated using soft ACK. In some implementations, the attached CSI may be based on aggregated measurements across multiple CBGs, TBs, or PDSCHs.

[0088] In some implementations, the set of PDSCH data packets involved in the aggregation measurement may be the same as the set of data packets confirmed in the codebook. In some implementations, the set of PDSCH data packets involved in the aggregation measurement may include the set of most recently received packets in the sequence.

[0089] In some implementations, one or more soft HARQ feedbacks may include NACKs with supplemental information indicating one or more of the following: (a) a failure due to a PDCCH error or a PDSCH decoding failure; (b) a decoding failure or a similar error; (c) DMRS-based information about the failure or data-based quality information about the similar error; and (d) one or more failed CBs.

[0090] In some implementations, one or more soft HARQ feedbacks may include NACK along with supplementary information, which is part of the same HARQ codebook as NACK, wherein placeholder bits sufficient to satisfy a single NACK are appended to the multiple HARQ feedbacks.

[0091] In some implementations, one or more soft HARQ feedbacks may include NACK along with supplemental information about the NACK and which is part of the HARQ codebook, which is first scheduled after the NACK is reported to the network node and decoded by the network node.

[0092] In some implementations, in generating one or more soft HARQ feedbacks, process 400 may involve processor 312 measuring one or more metrics on each codebook associated with one or more transmissions. In some implementations, one or more metrics may include one or more of the following: (a) one or more LDPC iterations; (b) one or more CN updates; (c) one or more LDPC processing cycles; (d) one or more bit flips between the input and output of the LDPC decoder; (e) the bit flip history for each cycle of LDPC decoding; (f) the average SNR at the input of the LDPC decoder; (g) the mutual information between LLRs; (h) the raw BER at the input of the derate matcher; (i) the SNR at the input of the derate matcher; and (j) the magnitude and variance of the LLR values ​​after receive combining or derate matching.

[0093] In some implementations, the reference MCS used in generating one or more soft HARQ feedbacks may be the latest PDSCH that was successfully received using the same codebook, or the MCS level of each PDSCH that reported SNR changes (e.g., delta-SNR).

[0094] Additional notes

[0095] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that the architectures described are merely examples, and many other architectures with the same functionality can actually be implemented. In a conceptual sense, any arrangement of components that achieve the same functionality is effectively “associated” to achieve the desired functionality. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” with each other to achieve the desired functionality, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operationally connected” or “operationally linked” to each other to achieve the desired functionality, and any two components that can be so associated can also be considered “operationally linked” to each other to achieve the desired functionality. Specific examples of operable connections include, but are not limited to, physically matchable and / or physically interacting components and / or wirelessly interactable and / or logically interacting and / or logically interactable components.

[0096] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0097] Furthermore, those skilled in the art will understand that, in general, the terms used herein, particularly those used in the appended claims, such as the body of the appended claims, are typically intended as “open-ended” terms; for example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “at least having,” and the term “comprising” should be interpreted as “including but not limited to.” Those skilled in the art will further understand that if a specific number of introduced claim statements are desired, such an intent will be explicitly stated in the claims, and without such a statement, such an intent does not exist. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce claim statements. However, the use of such phrases should not be construed as implying that a claim statement introduced by the indefinite article "a" or "an" limits any particular claim containing such a claim statement to an embodiment containing only one such statement, even when the same claim includes the introductory phrase "one or more" or "at least one," and indefinite articles such as "a" or "an," e.g., "an" and / or "an," should be interpreted as meaning "at least one" or "one or more." This also applies to the use of explicit texts introducing claim statements. Furthermore, even if a specific number of the introduced claims is explicitly listed, those skilled in the art will recognize that such a list should be interpreted as meaning at least the number listed; for example, a bare list of "two lists" without other modifiers means at least two lists, or two or more lists. Moreover, in those cases, the convention is similar to "at least one of A, B, and C, etc." Generally, in the conventional sense understood by those skilled in the art, the use of such a construct, such as "a system having at least one of A, B, and C," will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc., in those cases where the convention is similar to "at least one of A, B, or C." Generally, this construct is intended for use in the conventional sense understood by those skilled in the art; for example, "a system having at least one of A, B, or C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together. Those skilled in the art will further understand that any extractive words and / or phrases that actually present two or more alternative terms, whether in the specification, claims, or drawings, should be understood to cover the possibility of including one, any, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B."

[0098] As will be understood from the foregoing, various embodiments of the invention have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of the invention. Therefore, the various embodiments disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the appended claims.

Claims

1. A soft HARQ feedback reporting method in mobile communication, comprising: Receive one or more transmissions from a network node; Generate one or more Soft Hybrid Automatic Repeat Request (HARQ) responses corresponding to the one or more transmissions; as well as Send the one or more soft HARQ responses to the network node. Based on the reduction in the number of one or more soft HARQ feedbacks within a time period of N time units, where the number of one or more soft HARQ feedbacks is less than the number of existing HARQ feedbacks, and where the granularity of the N time units is a sub-slot, a slot, or a radio frame.

2. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The report in the one or more soft HARQ feedbacks includes: measured or estimated soft information in the form of percentage values ​​of the one or more soft HARQ feedbacks, wherein the percentage value is the ratio of the measured or estimated value of the soft information to the maximum value of the soft information.

3. The soft HARQ feedback reporting method in mobile communication according to claim 2, characterized in that, The soft information includes information about one or more of the following: The number of low-density parity-check decoding iterations; The amount of time required to complete the physical downlink shared channel decoding process; Log-likelihood ratio; Log-likelihood is greater than variance; The number of flipped bits; and Raw bit error rate.

4. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The measurement of the soft HARQ feedback report every N time units is based on one of the following: N physical downlink shared channels from N sub-time slots, N time slots, or N radio frames; One or more physical downlink shared channels every N time units, wherein the one or more physical downlink shared channels are selected due to having the worst or best decoding performance; One or more physical downlink shared channels that have been successfully decoded; and One or more physical downlink shared channels that were not successfully decoded.

5. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The processing timeline associated with preparing the one or more soft HARQ feedbacks is based on one or more of the following: User equipment capabilities; Parameter set; Existing user equipment processing timeline plus extension; Configuration of the demodulation reference signal position; Physical downlink shared channel mapping type; The type or method for generating the one or more soft HARQ feedbacks; Report or signal the type or method of the one or more soft HARQ feedbacks; Soft HARQ feedback reporting granularity; Soft HARQ feedback report density; The number of symbols shared by each physical downlink channel; The configured bandwidth portion size; and The time period beginning at the end of the last symbol of the physical downlink shared channel carrying the acknowledged transport block or code block group.

6. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, Priority-based HARQ-ACK feedback enables or disables the generation and transmission of one or more soft HARQ feedbacks, wherein the priority is indicated in downlink control information or configured in radio resource control signals.

7. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, Based on the physical downlink shared channel scheduling mechanism, the generation and transmission of one or more soft HARQ feedbacks are enabled or disabled by one or more of the following: Enabled for HARQ-ACK feedback or dynamic scheduling of physical downlink shared channels; Enabled for semi-static scheduling of the physical downlink shared channel; Enabled or disabled for physical downlink shared channels scheduled by downlink control information formats 1_0, 1_1, or 1_2; and Enabled or disabled based on semi-static scheduling configuration.

8. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The one or more soft HARQ feedbacks include at least one soft ACK or at least one soft NACK or both the soft ACK and the soft NACK, wherein the soft ACK and the soft NACK are encoded using a supplementary set of values ​​based on the same digital representation, and wherein a specific value in the soft NACK indicates an unreported physical downlink shared channel.

9. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The step of generating the one or more soft HARQ feedbacks includes: using 2 for outer loop link adaptive tracking n -1 value to generate at least one soft ACK or at least one soft NACK or both the soft ACK and the soft NACK, where n represents the value of the soft NACK.

10. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The step of generating the one or more soft HARQ feedbacks includes generating the one or more soft HARQ feedbacks using a type-2 or type-3 codebook.

11. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The step of generating one or more soft HARQ feedbacks includes: generating at least one soft ACK or at least one soft NACK, or both the soft ACK and the soft NACK. Specifically, the bits of the soft ACK and soft NACK are bundled by reporting the worst-case value in response to spatial bundling being configured and a decoding failure occurring; or The report indicates the minimum or average received quality in response to successful bundle decoding.

12. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The step of generating the one or more soft HARQ feedbacks includes: appending channel state information to a codebook generated using soft acknowledgments, wherein the appended channel state information is based on aggregated measurements over multiple code block groups, transport blocks, or physical downlink shared channels.

13. The soft HARQ feedback reporting method in mobile communication according to claim 12, characterized in that, The set of physical downlink shared channel data packets involved in the aggregation measurement is the same as the set of data packets confirmed in the codebook.

14. The soft HARQ feedback reporting method in mobile communication according to claim 12, characterized in that, The set of physical downlink shared channel data packets involved in the aggregated measurement includes the set of most recently received packets in the sequence.

15. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The one or more soft HARQ feedbacks include NACKs with supplementary information indicating one or more of the following: Failure due to physical downlink control channel error or physical downlink shared channel decoding failure; Decoding failed or a similar error occurred; Information about failures based on the demodulated reference signal or data-based quality information about similar errors; as well as One or more failed codebooks.

16. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The one or more soft HARQ feedbacks include a NACK along with supplemental information about the NACK, the supplemental information being part of the same HARQ codebook as the NACK, wherein the supplemental information is appended to placeholder bits of the multiple HARQ feedbacks, wherein the placeholder bits are sufficient for a single NACK.

17. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The one or more soft HARQ feedbacks include a NACK along with supplemental information about the NACK, which is part of a HARQ codebook that is first scheduled after the NACK is reported to the network node and decoded by the network node.

18. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The step of generating the one or more soft HARQ feedbacks includes: measuring one or more metrics on each codebook associated with the one or more transmissions, wherein the one or more metrics include one or more of the following: One or more low-density parity check iterations; One or more verification nodes are updated; One or more low-density parity check processing cycles; One or more flipped bits between the input and output of a low-density parity decoder; Bit-flipping history for each cycle of low-density parity-check decoding; The average signal-to-noise ratio at the input of the low-density parity decoder; Mutual information between log-likelihood ratios; The raw bit error rate at the input of the rate matcher; The signal-to-noise ratio at the input of the rate matcher; and The magnitude and variance of the log-likelihood ratio after receiving the merged or derate-matched values.

19. The soft HARQ feedback reporting method in mobile communication according to claim 1, characterized in that, The reference modulation and coding scheme used in generating the one or more soft HARQ feedbacks is either the latest physical downlink shared channel that was successfully received using the same codebook, or the modulation and coding scheme level of each physical downlink shared channel that reported a change in signal-to-noise ratio.

20. A user equipment for soft HARQ feedback reporting in mobile communications, comprising: A processor configured to perform the method of any one of claims 1-19.

Images