A hybrid automatic repeat request acknowledgement communication method and apparatus

Abstract

This application discloses a hybrid automatic repeat request acknowledgment communication method and device. The UE determines a Type-2 dynamic HARQ-ACK codebook and transmits feature information when preset conditions are met. This feature information is used to assist in identifying the cause of NACK information in the codebook. The preset conditions include: the number of demodulation failures for transport block TB reaches the maximum number of transmissions, or a first indication message is received. The network side obtains the codebook, detects the feature information, and determines a scheduling strategy based on the detection result: if detected, upper-layer retransmission is triggered; otherwise, rescheduling is performed at the physical layer. This application enables network devices to identify whether NACK is caused by PDSCH demodulation failure or DCI missed detection without increasing signaling overhead, thereby optimizing the retransmission mechanism and improving transmission efficiency.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a hybrid automatic repeat request acknowledgment communication method and device. Background Technology

[0002] HARQ (Hybrid Automatic Repeat Request) is a key technology in wireless communication systems used to combat time-varying fading and interference. It combines the advantages of Forward Error Correction (FEC) and Automatic Repeat Request (ARQ), minimizing retransmission delay while ensuring reliability. The sending end performs channel coding on the data packet before transmission, and the receiving end decodes and checks for correctness. If correct, it returns an ACK, and the sending end can continue sending new data. If incorrect, it returns a NACK, and the sending end retransmits the data packet.

[0003] HARQ resides at the MAC layer. If HARQ fails after reaching the maximum number of retransmissions, it reports to the upper layer (RLC). The transmitter can maintain multiple independent HARQ processes simultaneously, each running its own stop-and-wait loop. While one process is waiting for feedback, other processes can continue to transmit data using the channel. In DCI (Downlink Control Information), NDI (New Data Indicator) and HPN (HARQ Process Number) are two separate fields. HPN identifies which HARQ process is currently being scheduled. NDI is used to distinguish between new transmissions and retransmissions and needs to be compared with the previous NDI value of the same HPN. If the NDI is different from the previous one, it indicates that the process has started transmitting a new data packet, and the UE should clear the corresponding process's soft buffer. If the NDI is the same as the previous one, it indicates that the current transmission is a retransmission of a previous data packet, and the UE should merge the data with the soft bits of the process in the buffer for decoding.

[0004] The HARQ-ACK codebook is a sequence of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) information bits fed back by the UE on a Physical Uplink Control Channel (PUCCH) or Physical Uplink Shared Channel (PUSCH). The Type-2 dynamic codebook uses the DAI in the DCI to indicate the actual number of scheduled transmissions, allowing the codebook size to dynamically change with transmission. The core of the Type-2 HARQ-ACK dynamic codebook is that the UE dynamically constructs a variable-size feedback sequence based on the Downlink Allocation Index (DAI) carried in the Downlink Control Information (DCI). Specifically, the UE first sorts all scheduled transmissions' DCIs according to the PDCCH listening time and the ascending order of the serving cell index. The counter DAI (C-DAI) carried in each DCI indicates the cumulative sequence number of the current scheduling among all schedulings, while the total DAI (T-DAI) tells the UE the total number of scheduled transmissions within the current listening time. The UE determines the total number of feedbacks based on the T-DAI in the last received DCI, and fills the corresponding ACK / NACK information for each PDSCH into the corresponding positions in the codebook according to the C-DAI, thus forming the HARQ-ACK codebook. When generating the final HARQ-ACK codebook, the UE fills the positions corresponding to the missed DCIs with NACK information to keep the codebook length consistent with the base station's expectations.

[0005] In the existing technology, the NDI / HPN / C-DAI in the DCI sent by the network side in time units 1 to 4 are 0 / X / 1, 0 / Y / 2, 0 / Z / 3, and 0 / Q / 4, respectively. The process of the UE side generating the HARQ-ACK codebook for downlink transmission in time units 1 to 4 is as follows: The UE detects a successful DCI in time unit 1, determines that C-DAI is 1, and the corresponding demodulation scheduling PDSCH-1 is also successful, so the HARQ-ACK codebook is updated with ACK; The UE detects a successful DCI in time unit 2, determines that C-DAI is 2, and the corresponding demodulation scheduling PDSCHHPN-Y fails, so the HARQ-ACK codebook is updated with NACK; The UE detects a failed DCI in time unit 3, but detects a successful DCI in time unit 4. Based on C-DAI=4 in time unit 4 and C-DAI=2 in time unit 2, it is determined that there is one lost PDSCH scheduling, so a NACK is filled into the HARQ-ACK codebook. Furthermore, if the UE successfully detects that the PDSCHHPN-X scheduled by the DCI in time unit 4 is successful, it will fill the HARQ-ACK codebook with an ACK. In summary, the UE side generates the HARQ-ACK codebook for downlink transmissions in time units 1 to 4: ACK, NACK, NACK, ACK.

[0006] When a network device receives a NACK response from a UE, it typically triggers a retransmission mechanism to correct the transmission error. Effective retransmission strategies differ depending on the cause of the NACK. (1) DCI demodulation is successful, but PDSCH scheduled by DCI fails to demodulate: HARQ retransmission is usually initiated. If the current transport block TB has reached the maximum number of transmissions, the network side will trigger upper layer retransmission. (2) DCI demodulation failed, and the PDSCH scheduled by DCI failed to demodulate: Adjust the DCI scheduling policy and reschedule the PDSCH.

[0007] Using the Type-2 HARQ-ACK codebook, the UE provides NACK information bits for either a lost DCI or an erroneous PDSCH. Since the network cannot identify the true cause of the NACK information bits (1) or (2), this negatively impacts the efficient retransmission mechanism. For example, if a network device transmits a downlink transport block using HPN=X, and receives ACK / NACK / NACK / NACK feedback for the four transmissions corresponding to that transport block, the network device is unsure whether the UE did not receive the DCI of the second time unit or detected it, but PDSCH demodulation fails. If the PDSCH cannot be demodulated due to DCI detection failure, even if the network device reduces the PDSCH coding rate, the UE cannot obtain the corresponding DCI scheduling indication and still cannot effectively demodulate the PDSCH.

[0008] Therefore, it is necessary to address the negative impact on the retransmission mechanism caused by the network device's inability to identify the terminal-side data demodulation situation corresponding to the NACK information bits in the application scenario of Type-2 HARQ-ACK codebook. Summary of the Invention

[0009] This application proposes a hybrid automatic retransmission request acknowledgment communication method and device to solve the above-mentioned technical problems, and is particularly suitable for Type-2 dynamic HARQ-ACK codebook scenarios.

[0010] Firstly, this application proposes a hybrid automatic repeat request acknowledgment communication method, comprising the following steps: Determine the HARQ-ACK codebook, which is a Type-2 dynamic codebook; determine preset conditions, and when the preset conditions are met, transmit feature information, which is used to assist in identifying the cause of NACK information in the HARQ-ACK codebook; the preset conditions include at least one of the following: the number of demodulation failures for a transport block TB reaches the maximum number of transmissions; receive a first indication message for triggering the transmission of feature information.

[0011] The method described in any embodiment of the first aspect of this application, used in a network-side device, includes the following steps: The terminal-side device obtains the HARQ-ACK codebook, which is a Type-2 dynamic codebook; determines preset conditions, which include at least one of the following: the demodulation failure count for a transport block TB reaches the maximum number of transmissions; sends a first indication message to trigger the transmission of feature information; and detects the feature information transmitted by the terminal-side device, which is used to assist in identifying the cause of NACK information in the HARQ-ACK codebook.

[0012] The method described in any embodiment of the first aspect of this application, used in a terminal-side device, includes the following steps: The HARQ-ACK codebook is determined, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; preset conditions are determined, wherein the preset conditions include at least one of the following: the number of demodulation failures for a transport block TB reaches the maximum number of transmissions; a first indication message is received from the network-side device; when the preset conditions are met, feature information is sent, wherein the feature information is used to assist the network-side device in identifying the cause of the NACK information in the HARQ-ACK codebook.

[0013] Optionally, the feature information includes at least one of the following: information indicating that the first information in the HARQ-ACK codebook is NACK, and the corresponding TB demodulation failed and the maximum number of transmissions was reached; information for determining a reference value for triggering NACK feedback due to downlink control information (DCI) demodulation failure; and information for determining a reference value for triggering NACK feedback due to physical downlink shared channel (PDSCH) demodulation failure.

[0014] Optionally, the reference value includes at least one of the following: the number of NACKs, the ratio of the number of NACKs to the total number of NACKs in the HARQ-ACK codebook, and whether the number of NACKs exceeds a preset threshold.

[0015] Optionally, the first indication information is dynamic indication information or semi-static configuration information, and the first indication information includes at least one of the following: an indication for triggering the transmission of the feature information, time resources for transmitting the feature information, frequency resources for transmitting the feature information, and content format of the feature information.

[0016] Optionally, the first indication information is dynamic indication information, and the condition for sending the first indication information includes: sending the first indication information after the Nth time the terminal-side device detects NACK feedback for a transport block, where N is the maximum number of transmissions for the transport block.

[0017] Optionally, the first indication information is semi-static configuration information, which is used to configure the terminal-side device to send feature information on preset resources when preset conditions are met.

[0018] Optionally, the cause of the NACK information in the HARQ-ACK codebook is determined to be: a first cause, that physical downlink control information was obtained, but demodulation of the transport block failed according to the indication of the physical downlink control information; or a second cause, that physical downlink control information was not obtained, and missed scheduling information was determined according to the downlink allocation index.

[0019] Optionally, the method for the network-side device further includes: starting a first timer after sending a first indication message; and detecting feature information transmitted by the terminal-side device before the first timer expires.

[0020] Optionally, the method for the network-side device further includes: based on the detection result, performing one of the following operations: if the feature information is detected, determining that the demodulation failure count of the transport block corresponding to the feature information on the terminal-side device has reached the maximum number of transmissions, and triggering upper-layer retransmission; if the feature information is not detected, determining that the demodulation failure count of the transport block corresponding to the feature information on the terminal-side device has not reached the maximum number of transmissions, and rescheduling the transport block at the physical layer.

[0021] Optionally, the content format of the feature information is indicated by the first indication information, including at least one of the following: a format containing the HARQ process number and the number of times the terminal device detects the transport block under the HARQ process number; or a format containing whether the HARQ process number and the number of times the terminal device detects the propagation block under the HARQ process number have reached the maximum number of transmissions.

[0022] Secondly, this application also proposes a network-side device for implementing the method described in any one of the first aspects of this application. At least one module in the network-side device is configured to perform at least one of the following functions: acquiring a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook determined by a terminal-side device, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; determining the preset conditions; detecting feature information transmitted by the terminal-side device, wherein the feature information is used to assist in identifying the cause of NACK information generation in the HARQ-ACK codebook; and sending the first indication information.

[0023] This application also proposes a terminal-side device for implementing the method described in any one of the first aspects of this application. At least one module in the terminal-side device is configured to perform at least one of the following functions: determining a Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) codebook, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; determining the preset condition; responding to the preset condition, sending feature information, wherein the feature information is used to assist the network-side device in identifying the cause of NACK information generation in the HARQ-ACK codebook; receiving first indication information sent by the network-side device; and generating feature information of a corresponding format according to the content format indicated by the first indication information.

[0024] This application also proposes a communication device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method as described in any embodiment of the first aspect of this application.

[0025] This application also proposes a computer-readable medium on which a computer program is stored, which, when executed by a processor, implements the steps of the method as described in any embodiment of the first aspect of this application.

[0026] This application also proposes a mobile communication system comprising at least one network-side device as described in any embodiment of this application and / or at least one terminal-side device as described in any embodiment of this application.

[0027] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects: In this application, the UE feeds back information about when it determines that the number of PDSCH transmissions has reached the maximum and demodulation has failed. This reduces the signaling feedback burden on the UE and makes it easier for the network device to address the transmission reliability issues of DCI and PDSCH, thereby improving the effectiveness and efficiency of HARQ transmission.

[0028] Adding feedback information to the Type-2 HARQ-ACK codebook to represent the demodulation results of DCI and PDSCH respectively results in low feedback burden and efficiency for the UE. This application addresses this by having the UE feed back information about when it determines that the PDSCH transmission count has reached its maximum and demodulation has failed. This reduces the UE's signaling feedback burden and allows the network device to address DCI and PDSCH transmission reliability issues more effectively, thus improving the efficiency and effectiveness of HARQ transmission. Attached Figure Description

[0029] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A schematic diagram illustrating the generation of HARQ-ACK codebooks for each time unit DCI on the network side and the terminal side; Figure 2 A schematic diagram of the response after a network device transmits a downlink transport block using HPN=X; Figure 3 This is a flowchart illustrating an embodiment of the hybrid automatic retransmission request acknowledgment communication method of this application; Figure 4 This is a flowchart illustrating an embodiment of the method of this application used in a network-side device; Figure 5 This is a flowchart illustrating an embodiment of the method of this application used in a terminal-side device; Figure 6 This is a schematic diagram of an embodiment of a network-side device; Figure 7 This is a schematic diagram of an embodiment of the terminal-side device; Figure 8 This is a schematic diagram of the structure of a network-side device according to another embodiment of the present invention; Figure 9 This is a block diagram of a terminal-side device according to another embodiment of the present invention. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0031] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0032] Figure 1 A schematic diagram illustrating the generation of HARQ-ACK codebooks for each time unit (DCI) on the network side and the terminal side. (See diagram below.) Figure 1As shown, the NDI / HPN / C-DAI in the DCIs sent by the network side in time units 1-4 are 0 / X / 1, 0 / Y / 2, 0 / Z / 3, and 0 / Q / 4, respectively. The process of the UE generating the HARQ-ACK codebook for downlink transmissions in time units 1-4 is as follows: If the UE detects a successful DCI in time unit 1, it determines that C-DAI is 1, and the corresponding demodulation scheduling PDSCH-1 is also successful, so the HARQ-ACK codebook corresponds to the feedback ACK; If the UE detects a successful DCI in time unit 2, it determines that C-DAI is 2, and the corresponding demodulation scheduling PDSCH HPN Y fails, so the HARQ-ACK codebook corresponds to the feedback NACK; If the UE detects a failed DCI in time unit 3, but detects a successful DCI in time unit 4, based on C-DAI=4 in time unit 4 and C-DAI=2 in time unit 2, it is determined that there is one lost PDSCH scheduling, so a NACK is filled into the HARQ-ACK codebook. Furthermore, if the UE successfully detects that the PDSCH HPN X scheduled by the DCI in time unit 4 is successful, it will fill the HARQ-ACK codebook with an ACK. In summary, the UE side generates the HARQ-ACK codebook for downlink transmissions in time units 1 to 4: ACK, NACK, NACK, ACK.

[0033] Figure 2 This is a diagram illustrating the response of a network device after transmitting a downlink transport block using HPN X. (Example) Figure 2 As shown, the network device uses HPN X to transmit a downlink transport block. After receiving four HARQ-ACK responses of ACK / NACK / NACK / NACK corresponding to this transport block, the network device is unsure whether the UE did not receive the DCI of the second time unit or detected the DCI of the second time unit, but demodulation of the PDSCH failed. If the PDSCH cannot be demodulated due to the DCI detection failure, the network device can improve DCI performance, attempt to retransmit the transport block to obtain diversity gain, and try its best to complete the transport block demodulation.

[0034] Figure 3 This is a flowchart illustrating an embodiment of the method of this application.

[0035] This application proposes a hybrid automatic repeat request acknowledgment communication method, comprising the following steps 110-130: Step 110: Determine the HARQ-ACK codebook.

[0036] Specifically, the HARQ-ACK codebook is determined, and the HARQ-ACK codebook is a Type-2 dynamic codebook.

[0037] In network deployment, the UE presets the HARQ-ACK codebook type by obtaining the configuration information of the network devices. The system may support at least two types of HARQ-ACK codebooks to adapt to different service requirements and transmission scenarios. Type-1 HARQ-ACK codebook is a semi-static codebook, with its size determined by the semi-static configuration of the RRC higher-layer signaling. The UE predetermines a fixed-size feedback window based on parameters such as the candidate PDSCH reception timing set and HARQ timing. Regardless of whether there is actual data scheduling within the window, the UE generates ACK or NACK for each candidate position (filling with NACK if there is no scheduling). Type-2 HARQ-ACK codebook is a dynamic codebook, with its size dynamically changing according to the actual amount of downlink data scheduled. The base station informs the UE of the current scheduling order and total number through the Downlink Assignment Indicator (DAI) counter in the DCI. Based on the DAI information, the UE only generates HARQ-ACK bits for events such as actually received PDSCH and SPS release, thus constructing a codebook of variable size.

[0038] The HARQ-ACK types in the Type-2 dynamic codebook include ACK and NACK, but not DTX. The NACK information in the Type-2 HARQ-ACK codebook returned by the UE corresponds to two cases: The first reason is that the UE obtains the first physical downlink control information and can determine at least one of the following in the transport block corresponding to the NACK information: "New Data Indicator (NDI)," "Modulation and Coding Scheme (MCS)," "Redundancy Version (RV)," and "HARQ Process Number." The UE demodulates the transport block according to the indication of the first physical downlink control information, and the detection result is NACK.

[0039] The second reason is that the UE did not obtain the first physical downlink control information. Based on the downlink allocation index (DAI) in other physical downlink control information, it determined that there was scheduling information sent by a network device that it had missed, and responded with a NACK for the corresponding scheduling. In this case, the UE does not know the information such as the "New Data Indicator (NDI)," "Modulation and Coding Scheme (MCS)," "Redundancy Version (RV)," and "HARQ Process Number" of the transport block corresponding to the NACK information.

[0040] Step 120: Determine the preset conditions for transmitting feature information.

[0041] The feature information is used to help identify the cause of NACK information in the HARQ-ACK codebook.

[0042] The preset conditions include at least one of the following: the number of demodulation failures for a transport block TB reaches the maximum number of transmissions; a first indication message for triggering the transmission of characteristic information is received.

[0043] It should be noted that the terminal device must first determine the preset conditions before sending feature information according to those conditions. The network device may fall into two categories: first, after receiving the feature information, it determines the actual preset conditions based on the feature information; second, it determines the preset conditions and sends configuration information to inform the terminal of the preset conditions to be executed. Therefore, the meaning and function of "determining preset conditions" will be explained in each embodiment.

[0044] The UE feeds back information indicating that it has reached the maximum number of PDSCH transmissions and failed demodulation, facilitating the network device to initiate upper-layer retransmissions to ensure data transmission reliability. In cases where the UE detects a DCI failure leading to a scheduled PDSCH transmission failure, the network device is allowed to adjust the scheduling information and retransmit, improving the efficiency of the retransmission mechanism and avoiding the signaling burden of the UE always separately reporting detection results for both the DCI and the scheduled PDSCH.

[0045] Step 130: Transmit feature information, which includes indication information or statistical reference values ​​of the cause of NACK, for the network side to identify the cause of NACK in order to optimize the retransmission strategy.

[0046] When the preset conditions are met, feature information is transmitted. The feature information includes at least one of the following: Information used to indicate that the first information in the HARQ-ACK codebook is NACK, and that the corresponding TB demodulation failed and the maximum number of transmissions was reached; Information used to determine the reference value for triggering NACK feedback when downlink control information DCI demodulation failure occurs; Information used to determine the reference value that triggers NACK feedback when the Physical Downlink Shared Channel (PDSCH) demodulation fails.

[0047] The reference values ​​include at least one of the following: the number of NACKs, the ratio of the number of NACKs to the total number of NACKs in the HARQ-ACK codebook, and whether the number of NACKs exceeds a preset threshold.

[0048] The UE can report the ACK / NACK statistics in the Type-2 HARQ-ACK codebook within the reference time period. The cause of the NACK in the HARQ-ACK codebook is either because the UE detected DCI but determined that DCI demodulation failed through C-DAI / T-DAI detection and reported the NACK, or because the UE detected DCI but the PDSCH scheduled by that DCI failed to demodulate.

[0049] Figure 4 This is a flowchart illustrating an embodiment of the method of this application used in a network-side device.

[0050] The method described in any embodiment of the first aspect of this application, used in a network-side device, includes the following steps 210-240: Step 210: Obtain the HARQ-ACK codebook determined by the terminal-side device.

[0051] The HARQ-ACK codebook is a Type-2 dynamic codebook.

[0052] The network device checks the HARQ-ACK codebook and determines that the first piece of information in the HARQ-ACK codebook is NACK. The network device is unsure of the detection status of the transport block corresponding to this NACK information on the UE side. Assume that the maximum number of downlink transport block transmissions is N, and the current result is the UE's feedback for the Mth (M≤N)th transmission. In the previous M transmissions, the UE may have detected the downlink control information scheduling this transport block P times (0≤P≤M), and detected the scheduled downlink transport block according to the instructions of the downlink control information.

[0053] Step 220: Determine the preset conditions.

[0054] The preset conditions include at least one of the following: the number of demodulation failures for a transport block TB reaches the maximum number of transmissions; and a first indication message is sent to trigger the transmission of characteristic information.

[0055] Without UE characteristic information, the network device, as the data scheduler, cannot determine the cause of the NACK information in the Type-2 HARQ-ACK codebook—whether it's due to the ratio of case A to case B. One possible approach in the prior art is to add feedback information to the Type-2 HARQ-ACK codebook to represent the demodulation results of DCI and PDSCH, respectively. For example, if DCI demodulation is successful but the corresponding PDSCH demodulation fails, ACK+NACK is fed back; if DCI demodulation fails and the corresponding PDSCH demodulation fails, NACK+NACK is fed back. However, the success rate of DCI demodulation is very high, and this approach increases the amount of feedback from the UE in most scenarios, placing a burden on the UE.

[0056] In this invention, the network device can send a first indication message to trigger the UE to transmit feature information. Then, it acquires the feature information sent by the UE. If the network device determines that most of the NACK information it acquires is due to the UE detecting DCI but determining through C-DAI / T-DAI that DCI demodulation failed, the network device can improve the robustness of DCI scheduling, ensuring the UE receives scheduling instructions for data and improving data transmission efficiency. If the network device determines that most of the NACK information it acquires is due to the UE detecting DCI, but the PDSCH scheduled for that DCI failed to demodulate, the network device can improve the robustness of PDSCH scheduling, ensuring data transmission reliability and improving data transmission efficiency. Compared to the Type-2 HARQ-ACK codebook, which separately reports whether DCI was detected and whether PDSCH demodulation was successful for each transport block, this reduces the feedback burden on the UE and ensures the efficiency of the Type-2 HARQ-ACK codebook.

[0057] Step 230: Send the first instruction message.

[0058] The first indication information is used to trigger the terminal-side device to transmit feature information.

[0059] The first indication information is dynamic indication information or semi-static configuration information, and the first indication information includes at least one of the following: an indication for triggering the transmission of the feature information, time resources for transmitting the feature information, frequency resources for transmitting the feature information, and content format of the feature information.

[0060] As an optional implementation, the first indication information is dynamic indication information. The condition for sending the first indication information includes: sending the first indication information after the Nth time a NACK feedback from the terminal-side device to a transport block is detected, where N is the maximum number of transmissions for the transport block. When M=N, the network device can send dynamic indication information to trigger the UE to send feature information for that transport block. The first indication information includes the time and resources for the UE to send the feature information. Optionally, the first indication information also includes the content format of the feature information. For example, the content format of the feature information includes the HARQ process number and the number of times the UE has detected the transport block under that HARQ process number. Or the content format of the feature information includes the HARQ process number and whether the number of times the UE has detected the transport block under that HARQ process number has reached the maximum number of transmissions.

[0061] As another optional implementation, the first indication information is semi-static configuration information, which is used to configure the terminal-side device to send feature information on preset resources when preset conditions are met. The network device sends the first indication information to configure the UE to send feature information on preset resources when preset conditions are met. The first indication information also includes the time and resources for the UE to send feature information. The preset condition may be that the UE has responded with N N ACKs for a transport block of a HARQ process. Optionally, the content format of the feature information includes the HARQ process number and the number of times the UE has detected a transport block under that HARQ process number. Alternatively, the content format of the feature information includes the HARQ process number and whether the number of times the UE has detected a transport block under that HARQ process number has reached the maximum number of transmissions.

[0062] Optionally, the method further includes: starting a first timer after sending the first indication information; and detecting feature information transmitted by the terminal-side device before the first timer expires. If the network device sends the first indication information, triggering the UE to send feature information, the network device starts the first timer after sending the first indication information, and detects the UE's feature information before the first timer expires. The timeout value of the first timer is preset. If the network device detects the UE's feature information before the first timer expires, it can be determined that the UE has detected the downlink control information scheduling the transport block N times, and detected the scheduled downlink transport block according to the indication of the downlink control information, but still cannot correctly decode the transport block. In this case, the network device can trigger upper-layer retransmission. If the network device does not detect the UE's feature information before the first timer expires, it can be determined that the UE has not detected the downlink control information scheduling the transport block, or the number of times the downlink transport block has been detected according to the indication of the downlink control information has not reached the maximum. The network device can first solve the DCI correct transmission problem, adjust the DCI scheduling strategy, and reschedule the transport block.

[0063] Step 240: Detect the feature information transmitted by the terminal device and perform corresponding operations based on the detection results.

[0064] The feature information is used to help identify the cause of NACK information in the HARQ-ACK codebook.

[0065] Based on the test results, perform one of the following operations: If the feature information is detected, it is determined that the number of demodulation failures of the transmission block corresponding to the feature information on the terminal side device has reached the maximum number of transmissions, triggering upper layer retransmission; If the feature information is not detected, it is determined that the demodulation failure count of the transport block corresponding to the feature information on the terminal side device has not reached the maximum number of transmissions, and the transport block is rescheduled at the physical layer.

[0066] Alternatively, based on the test results, perform one of the following operations: If the feature information is detected and it is determined that the first value exceeds the first preset threshold, or that the second value does not exceed the second preset threshold, then the encoding rate of the DCI information is reduced. If the feature information is detected and it is determined that the first value does not exceed the first preset threshold, or the second value exceeds the second preset threshold, then the encoding rate of the PDSCH information is reduced. The first value is the ratio of the number of Type I NACKs in the HARQ-ACK codebook to the total number of NACKs in the HARQ-ACK codebook, and the second value is the ratio of the number of Type II NACKs in the HARQ-ACK codebook to the total number of NACKs in the HARQ-ACK codebook. Type I NACKs are the NACKs corresponding to the first reason, and Type II NACKs are the NACKs corresponding to the second reason.

[0067] The first and second preset thresholds are determined by the network device itself.

[0068] As the data scheduler, the network device determines the ratio of cause (case A) to cause (case B) of NACK information in the Type-2 HARQ-ACK codebook based on feature information. By using a first preset threshold and a second preset threshold, if the network device determines that most of the NACK information it acquires is due to the UE detecting DCI but confirming DCI demodulation failure through C-DAI / T-DAI detection, the network device can improve the robustness of DCI scheduling, ensuring the UE receives scheduling instructions for data and improving data transmission efficiency. If the network device determines that most of the NACK information it acquires is due to the UE detecting DCI, but the PDSCH scheduled for that DCI failed to demodulate, the network device can improve the robustness of PDSCH scheduling, ensuring data transmission reliability and improving data transmission efficiency.

[0069] Figure 5 This is a flowchart illustrating an embodiment of the method of this application used in a terminal-side device.

[0070] The method described in any embodiment of the first aspect of this application, used in a terminal-side device, includes the following steps 310-340: Step 310: Determine the HARQ-ACK codebook.

[0071] The HARQ-ACK codebook is a Type-2 dynamic codebook.

[0072] The UE first sorts all scheduled DCIs based on the PDCCH listening time and the ascending order of the serving cell index. Each DCI carries a counter DAI (C-DAI) indicating the cumulative sequence number of the current scheduling among all schedulings, while the total DAI (T-DAI) tells the UE the total number of schedulings within the current listening time. The UE determines the total feedback number based on the T-DAI in the last received DCI and, according to the C-DAI, sequentially fills the ACK / NACK information corresponding to each PDSCH into the corresponding positions in the codebook, thus forming the HARQ-ACK codebook. When generating the final HARQ-ACK codebook, the UE fills in NACK information at the positions corresponding to the missed DCIs to maintain the codebook length consistent with the base station's expectations.

[0073] Step 320: Determine the preset conditions.

[0074] The preset conditions include at least one of the following: the number of demodulation failures for a transport block TB reaches the maximum number of transmissions; or the first indication information is received from the network-side device.

[0075] Based on the UE's determination that the HARQ-ACK codebook type is Type-2 HARQ-ACK codebook, it sends feature information for the NACK information in the Type-2 HARQ-ACK codebook.

[0076] In case A (first cause), the UE can obtain the first physical downlink control information, determine the demodulation count of the transport block, and determine whether the maximum number of transmissions for that transport block has been reached. If the maximum number of transmissions has been reached but demodulation of the transport block is still unsuccessful, the UE sends feature information to the network device. In case B (second cause), the UE does not send back feature information.

[0077] Step 330: When the preset conditions are met, send the feature information.

[0078] The feature information is used to assist network-side devices in identifying the reasons for the generation of NACK information in the HARQ-ACK codebook.

[0079] The UE feeds back information indicating that it has reached the maximum number of PDSCH transmissions and failed demodulation, facilitating the network device to initiate upper-layer retransmissions to ensure data transmission reliability. In cases where the UE detects a DCI failure leading to a scheduled PDSCH transmission failure, the network device is allowed to adjust the scheduling information and retransmit, improving the efficiency of the retransmission mechanism and avoiding the signaling burden of the UE always separately reporting detection results for both the DCI and the scheduled PDSCH.

[0080] Step 340: Receive the first indication information sent by the network-side device, and generate feature information of the corresponding format according to the content format indicated by the first indication information.

[0081] The content format of the feature information is indicated by the first indication information, including at least one of the following: a format containing the HARQ process number and the number of times the terminal device detects the transport block under the HARQ process number; a format containing the HARQ process number and whether the number of times the terminal device detects the transport block under the HARQ process number has reached the maximum number of transmissions.

[0082] After the network device obtains the NACK information in the Type-2 HARQ-ACK codebook fed back by the UE, it cannot determine whether the data it schedules to transmit is in case A or case B on the UE side.

[0083] Based on the UE's determination that the HARQ-ACK codebook type is Type-2 HARQ-ACK codebook, it sends feature information for the NACK information in the Type-2 HARQ-ACK codebook.

[0084] In this application, the UE feeds back information about when it determines that the number of PDSCH transmissions has reached the maximum and demodulation has failed. This reduces the signaling feedback burden on the UE and makes it easier for the network device to address the transmission reliability issues of DCI and PDSCH, thereby improving the effectiveness and efficiency of HARQ transmission.

[0085] Adding feedback information to the Type-2 HARQ-ACK codebook to represent the demodulation results of DCI and PDSCH respectively results in low feedback burden and efficiency for the UE. This application addresses this by having the UE feed back information about when it determines that the PDSCH transmission count has reached its maximum and demodulation has failed. This reduces the UE's signaling feedback burden and allows the network device to address DCI and PDSCH transmission reliability issues more effectively, thus improving the efficiency and effectiveness of HARQ transmission.

[0086] Figure 6 This is a schematic diagram of an embodiment of a network-side device.

[0087] This application also proposes a network-side device 400 for implementing the method of any of the embodiments in this application. The network-side device 400 includes a network transmitting module 401, a network determining module 402, and a network receiving module 403 that are interconnected.

[0088] The network sending module 401 is used to send first indication information, which is used to trigger the terminal-side device to transmit feature information; after sending the first indication information, a first timer is started. For specific implementation, see step 230.

[0089] The network determination module 402 is used to acquire the HARQ-ACK codebook determined by the terminal-side device, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; determine the preset conditions; and detect the feature information transmitted by the terminal-side device, wherein the feature information is used to assist in identifying the cause of NACK information in the HARQ-ACK codebook. For specific implementation details, see steps 210, 220, and 240.

[0090] The network receiving module 403 is used to receive feature information transmitted by the terminal-side device. See step 240 for a detailed implementation.

[0091] The specific methods for implementing the functions of the network sending module, network determining module, and network receiving module are as described in the various method embodiments of this application (e.g., Figure 4 Steps 210-240 of the illustrated embodiment will not be repeated here.

[0092] The network-side equipment described in this application may refer to base station facilities, network-side equipment or servers connected to base stations, systems that provide services for the aforementioned equipment, or any system, subsystem, module, circuit, chip or software operating device that provides information reception, transmission, identification and processing for the aforementioned equipment.

[0093] Figure 7 This is a schematic diagram of an embodiment of the terminal-side device.

[0094] This application also proposes a terminal-side device 500 for implementing the method of any embodiment of this application. The terminal-side device 500 includes a terminal transmitting module 501, a terminal determining module 502, and a terminal receiving module 503 connected to each other.

[0095] The terminal receiving module 503 is used to receive the first indication information sent by the network-side device. See step 340 for a detailed implementation.

[0096] The terminal determination module 502 is used to determine the HARQ-ACK codebook, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; determine the preset conditions; and generate feature information of a corresponding format according to the content format indicated by the first indication information. For specific implementation details, see steps 310, 320, and 340.

[0097] The terminal sending module 501 is used to send feature information in response to the preset condition. The feature information is used to assist the network-side device in identifying the cause of the NACK information in the HARQ-ACK codebook. For specific implementation details, see step 330.

[0098] The specific methods for implementing the functions of the terminal sending module, the terminal determining module, and the terminal receiving module are as described in the various method embodiments of this application (e.g., Figure 5 Steps 310-340 of the illustrated embodiment will not be repeated here.

[0099] The terminal-side equipment described in this application may refer to user equipment (UE), personal mobile terminal, smart terminal, mobile phone, computer with communication function, system that provides services for the above-mentioned equipment, or any system, subsystem, module, circuit, chip or software running device that provides information reception, transmission, identification and processing for the above-mentioned equipment.

[0100] Figure 8 A schematic diagram of a network-side device according to another embodiment of the present invention is shown. As shown, the network-side device 600 includes a processor 601, a wireless interface 602, and a memory 603. The wireless interface may consist of multiple components, including a transmitter and a receiver, providing a unit for communication with various other devices over a transmission medium. The wireless interface implements communication functions with the terminal-side device, processes wireless signals through receiving and transmitting devices, and the data carried by the signals is communicated with the memory or processor via an internal bus structure. The memory 603 contains a computer program that executes any embodiment of this application, and the computer program runs or modifies the processor 601. When the memory, processor, and wireless interface circuit are connected through a bus system, the bus system includes a data bus, a power bus, a control bus, and a status signal bus, which will not be described in detail here.

[0101] Figure 9 This is a block diagram of a terminal-side device according to another embodiment of the present invention. The terminal-side device 700 includes at least one processor 701, a memory 702, a user interface 703, and at least one wireless network interface 704. The various components in the terminal-side device 700 are coupled together via a bus system. The bus system is used to enable communication between these components. The bus system includes a data bus, a power bus, a control bus, and a status signal bus.

[0102] User interface 703 may include a display, keyboard, or clicking device, such as a mouse, trackball, touchpad, or touchscreen.

[0103] The memory 702 stores executable modules or data structures. The memory may store an operating system and application programs. The operating system includes various system programs, such as a framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. The application programs include various applications, such as media players and browsers, used to implement various application functions.

[0104] In an embodiment of the present invention, the memory 702 contains a computer program that executes any embodiment of the present application, the computer program being run on or modified by the processor 701.

[0105] The memory 702 includes a computer-readable storage medium. The processor 701 reads the information in the memory 702 and, in conjunction with its hardware, completes the steps of the above-described method. Specifically, the computer-readable storage medium stores a computer program, which, when executed by the processor 701, implements the steps of the method embodiments described in any of the above embodiments.

[0106] Processors 601 and 701 may be integrated circuit chips with signal processing capabilities. In implementation, each step of the method in this application can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, off-the-shelf programmable gate array or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor.

[0107] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. In a typical configuration, the device of this application includes one or more processors (CPUs), an input / output user interface, a network interface, and memory.

[0108] Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0109] Therefore, this application also proposes a computer-readable medium storing a computer program that, when executed by a processor, implements the steps of the method described in any embodiment of this application. For example, the memory 603, 702 of the present invention may include non-permanent memory in the form of computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM.

[0110] Based on the embodiments of the above-described apparatus in this application, this application also proposes a mobile communication system, including at least one embodiment of any terminal-side device in this application and / or at least one embodiment of any network-side device in this application.

[0111] It should be noted that the specific mobile communication technology described in this invention is not limited, and can be WCDMA, CDMA2000, TD-SCDMA, WiMAX, LTE / LTE-A, LAA, MuLTEfire, 5G NR, and the sixth-generation and Nth-generation mobile communication technologies that may appear in the future.

[0112] The terminal described in this invention refers to a terminal-side product that can support the communication protocols of terrestrial mobile communication systems, and a specially designed wireless modem module that can be integrated into various types of terminal forms such as mobile phones, tablets, and data cards to complete communication functions.

[0113] For ease of description, a fifth-generation mobile communication system is used as an example, where the mobile communication terminal can be represented as UE (User Equipment), and the network-side access equipment can be represented as a base station or access point.

[0114] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0115] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be understood that when a device or component is “connected” to another device or component, it may be directly connected to the other device or component, or there may be an intermediary device or component. Furthermore, the term “connection” as used herein may include partially wireless connections as well as partially wired connections.

[0116] In the description of this application, it should be understood that the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0117] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method of hybrid automatic repeat request acknowledgement communication, characterized by Includes the following steps: Determine the HARQ-ACK codebook, which is a Type-2 dynamic codebook; A preset condition is determined, and when the preset condition is met, feature information is transmitted. The feature information is used to assist in identifying the cause of the NACK information in the HARQ-ACK codebook. The preset conditions include at least one of the following: The demodulation failure count for a transport block TB reaches the maximum number of transmissions; Received the first indication information to trigger the transmission of characteristic information. 2.A method for determining a NACK information generation cause in a hybrid automatic repeat request-acknowledgement codebook, used for a network side device, characterized in that, Includes the following steps: Obtain the HARQ-ACK codebook determined by the terminal-side device, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; determine preset conditions, wherein the preset conditions include at least one of the following: The demodulation failure count for a transport block TB reaches the maximum number of transmissions; Send a first indication message to trigger the transmission of characteristic information; The feature information transmitted by the terminal device is detected, and the feature information is used to help identify the cause of the NACK information in the HARQ-ACK codebook.

3. A method for determining the cause of NACK information generation in a hybrid automatic repeat request acknowledgment book, used in a terminal-side device, characterized in that, Includes the following steps: Determine the HARQ-ACK codebook, which is a Type-2 dynamic codebook; Determine preset conditions, which include at least one of the following: The demodulation failure count for a transport block TB reaches the maximum number of transmissions; Receive the first indication information sent by the network-side device; When the preset conditions are met, feature information is sent, which is used to assist the network-side device in identifying the cause of the NACK information in the HARQ-ACK codebook.

4. The method according to any one of claims 1 to 3, wherein The feature information includes at least one of the following: Information used to indicate that the first information in the HARQ-ACK codebook is NACK, and that the corresponding TB demodulation failed and the maximum number of transmissions was reached; Information used to determine the reference value for triggering NACK feedback when downlink control information DCI demodulation failure occurs; Information used to determine the reference value that triggers NACK feedback when the Physical Downlink Shared Channel (PDSCH) demodulation fails.

5. The method according to any one of claims 1 to 3, characterized in that, The HARQ-ACK types in the Type-2 dynamic codebook include ACK and NACK, but not DTX.

6. The method of claim 4, wherein, The reference value includes at least one of the following: The number of NACKs, the ratio of the number of NACKs to the total number of NACKs in the HARQ-ACK codebook, and whether the number of NACKs exceeds a preset threshold.

7. The method according to any one of claims 1 to 3, characterized in that, The first indication information is dynamic indication information or semi-static configuration information, and the first indication information includes at least one of the following: Instructions for triggering the transmission of the feature information, time resources for transmitting the feature information, frequency resources for transmitting the feature information, and content format of the feature information.

8. The method of claim 7, wherein, The first indication information is dynamic indication information, and the conditions for sending the first indication information include: The first indication information is sent after the Nth time the terminal-side device detects a NACK feedback for a transport block, where N is the maximum number of transmissions for the transport block.

9. The method of claim 7, wherein, The first indication information is semi-static configuration information, which is used to configure the terminal-side device to send feature information on preset resources when preset conditions are met.

10. The method according to any one of claims 1 to 3, characterized in that, The reasons for the generation of NACK information in the HARQ-ACK codebook are determined as follows: First, physical downlink control information was obtained, but demodulation of the transport block failed according to the indication of the physical downlink control information; or, second, physical downlink control information was not obtained, and missed scheduling information was determined according to the downlink allocation index.

11. The method of claim 2, wherein, Also includes: Based on the test results, perform one of the following operations: If the feature information is detected and it is determined that the first value exceeds the first preset threshold, or that the second value does not exceed the second preset threshold, then the encoding rate of the DCI information is reduced. If the feature information is detected and it is determined that the first value does not exceed the first preset threshold, or the second value exceeds the second preset threshold, then the encoding rate of the PDSCH information is reduced. The first value is the ratio of the number of Type I NACKs in the HARQ-ACK codebook to the total number of NACKs in the HARQ-ACK codebook, and the second value is the ratio of the number of Type II NACKs in the HARQ-ACK codebook to the total number of NACKs in the HARQ-ACK codebook. Type I NACKs are the NACKs corresponding to the first reason, and Type II NACKs are the NACKs corresponding to the second reason.

12. The method as described in claim 2, characterized in that, Also includes: After sending the first instruction information, start the first timer; before the first timer expires, detect the feature information transmitted by the terminal device.

13. The method of claim 2, wherein, Also includes: Based on the test results, perform one of the following operations: If the feature information is detected, it is determined that the number of demodulation failures of the transmission block corresponding to the feature information on the terminal side device has reached the maximum number of transmissions, triggering upper layer retransmission; If the feature information is not detected, it is determined that the demodulation failure count of the transport block corresponding to the feature information on the terminal side device has not reached the maximum number of transmissions, and the transport block is rescheduled at the physical layer.

14. The method of any one of claims 1 to 3, wherein, The content format of the feature information is indicated by the first indication information, including at least one of the following: The format includes the HARQ process number and the number of times the terminal device has detected the transport block under that HARQ process number; the format includes the HARQ process number and whether the number of times the terminal device has detected the transport block under that HARQ process number has reached the maximum number of transmissions.

15. A network side device for implementing the method of any one of claims 1 to 14, characterized in that, At least one module in the network-side device is used for at least one of the following functions: Obtain the HARQ-ACK codebook determined by the terminal-side device, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; Determine the preset conditions; The feature information transmitted by the terminal device is detected, and the feature information is used to assist in identifying the cause of the NACK information in the HARQ-ACK codebook. Send the first instruction information.

16. A terminal-side device for implementing the method according to any one of claims 1 to 14, characterized in that, At least one module in the terminal-side device is used for at least one of the following functions: Determine the HARQ-ACK codebook for automatic repeat request acknowledgment, wherein the HARQ-ACK codebook is a Type-2 dynamic codebook; Determine the preset conditions; In response to the preset conditions, feature information is sent, which is used to assist the network-side device in identifying the cause of the NACK information in the HARQ-ACK codebook; Receive first indication information sent by the network-side device; generate feature information of the corresponding format according to the content format indicated by the first indication information.

17. A communication device, characterized by include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 14.

18. A computer-readable medium on which a computer program is stored, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 14.

19. A mobile communication system, characterized in that, It includes at least one network-side device as described in claim 15 and / or at least one terminal-side device as described in claim 16.

Images