WO2021114051A1 - 反馈方法、反馈装置及存储介质 - Google Patents

反馈方法、反馈装置及存储介质 Download PDF

Info

Publication number
WO2021114051A1
WO2021114051A1 PCT/CN2019/124123 CN2019124123W WO2021114051A1 WO 2021114051 A1 WO2021114051 A1 WO 2021114051A1 CN 2019124123 W CN2019124123 W CN 2019124123W WO 2021114051 A1 WO2021114051 A1 WO 2021114051A1
Authority
WO
WIPO (PCT)
Prior art keywords
fed back
codebook
terminal
feedback
codebooks
Prior art date
Application number
PCT/CN2019/124123
Other languages
English (en)
French (fr)
Inventor
朱亚军
洪伟
吴佳霖
李勇
Original Assignee
北京小米移动软件有限公司
北京邮电大学
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司, 北京邮电大学 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2019/124123 priority Critical patent/WO2021114051A1/zh
Priority to CN201980003475.7A priority patent/CN111149315B/zh
Publication of WO2021114051A1 publication Critical patent/WO2021114051A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a feedback method, a feedback device, and a storage medium.
  • NR-U NR-based unlicensed frequency band
  • NR-U and License Assisted Access (LAA) based on Long Term Evolution are respectively two network technologies that use NR air interface and LTE air interface in unlicensed frequency bands.
  • LTE Long Term Evolution
  • RAT Radio Access Technology
  • CCA clear channel assessment
  • LBT Listen Before Talk
  • the physical uplink control channel (PUCCH) carrying hybrid automatic repeat request (Hybrid Automatic Repeat request, HARQ) feedback information is not successful by the base station and other network equipment Receiving, if the network device triggers retransmission at this time, resources will be wasted, and the continuous loss of PDCCH will be aggravated. Therefore, in the related technology, the HARQ codebook accumulation feedback mechanism triggered by the network device is introduced, and the information of these feedback failures is merged into the subsequent PUCCH for transmission, which provides multiple transmission opportunities for HARQ.
  • PUCCH physical uplink control channel
  • HARQ Hybrid Automatic Repeat request
  • the HARQ codebook accumulation feedback mechanism triggered by the network device the HARQ codebook that fails to feed back will have a feedback delay.
  • the present disclosure provides a feedback method, a feedback device, and a storage medium.
  • a feedback method which is applied to a terminal, the terminal maintains a codebook to be fed back, and the feedback method includes:
  • the determining the queue of the codebook to be fed back according to the trigger indication sent by the network device includes:
  • the trigger indication is used to indicate that the network device has successfully received the codebook that has been fed back
  • the codebook that has been fed back is deleted from the queue of the codebook to be fed back, and the queue of the codebook to be fed back is obtained. .
  • the determining the queue of the codebook to be fed back according to the trigger indication sent by the network device includes:
  • the current queue of the codebook to be fed back is determined as the queue of the codebook to be fed back.
  • the feedback method further includes:
  • the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back is updated according to the trigger indication.
  • updating the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to the trigger indication includes:
  • the trigger indication is used to indicate that the network device has successfully received the codebook that has been fed back
  • the queue of the codebook to be fed back is not empty
  • the number of codebooks to be fed back is accumulated to obtain DAI representing the number of codebooks to be fed back.
  • Parameter when the queue of the codebook to be fed back is empty, reset the number of codebooks to be fed back to obtain the DAI parameter representing the number of codebooks to be fed back to be reset.
  • updating the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to the trigger indication includes:
  • the trigger indication is used to indicate that the network device has not successfully received the codebook that has been fed back
  • the number of codebooks to be fed back is accumulated to obtain a DAI parameter representing the number of codebooks to be fed back accumulated.
  • the feeding back the codebook to be fed back in the queue of the codebook to be fed back includes:
  • a feedback method which is applied to a network device, and the network device maintains information of a codebook to be fed back by a terminal, and the feedback method includes:
  • the updating the information that the network device maintains the codebook to be fed back by the terminal according to whether the codebook fed back by the terminal is successfully received includes:
  • the information of the received codebook is deleted from the information of the codebook to be fed back by the terminal maintained by the network device.
  • sending a trigger indication for indicating whether the codebook fed back by the terminal is successfully received to the terminal includes:
  • the updating the information that the network device maintains the codebook to be fed back by the terminal according to whether the codebook fed back by the terminal is successfully received includes:
  • sending a trigger indication for indicating whether the codebook fed back by the terminal is successfully received to the terminal includes:
  • the feedback method further includes:
  • the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back is updated.
  • updating the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back includes:
  • the number of codebooks to be fed back is accumulated to obtain the DAI parameter representing the number of codebooks to be fed back to be accumulated,
  • the number of codebooks to be fed back is reset to obtain the DAI parameter representing the number of codebooks to be fed back to be reset.
  • updating the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back includes:
  • the number of codebooks to be fed back is accumulated to obtain the DAI parameter representing the number of codebooks to be fed back accumulated.
  • a feedback device which is applied to a terminal, the terminal maintains a codebook to be fed back, and the feedback device includes:
  • the determining unit is configured to determine the queue of the codebook to be fed back according to the trigger indication sent by the network device, where the trigger indication is used to indicate whether the codebook that has been fed back has been successfully received; the feedback unit is configured to feed back the codebook to be fed back The codebook to be fed back in the codebook queue.
  • the determining unit transfers the feedback codebook from the queue of the codebook currently to be fed back Delete the codebook to get the queue of the codebook to be feedback.
  • the determining unit determines the queue of the codebook to be fed back currently as the queue of the codebook to be fed back.
  • the determining unit is further configured to:
  • the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back is updated according to the trigger indication.
  • the determining unit accumulates the number of codebooks to be fed back when the queue of the codebooks to be fed back is not empty , Obtain the DAI parameter representing the number of codebooks to be fed back, and when the queue of the codebook to be fed back is empty, the determining unit resets the number of codebooks to be fed back to obtain the DAI parameter representing the number of codebooks to be fed back to be reset .
  • the determining unit accumulates the number of codebooks to be fed back to obtain DAI representing the number of codebooks to be fed back. parameter.
  • the feedback unit uploads all the codebooks to be fed back in the queue of the codebooks to be fed back.
  • a feedback device which is applied to a network device, and the network device maintains information of a codebook to be fed back by a terminal, and the feedback device includes:
  • the receiving unit is configured to determine whether the codebook fed back by the terminal is successfully received; the processing unit is configured to update the information of the codebook to be fed back by the terminal maintained by the network device according to whether the codebook fed back by the terminal is successfully received; the sending unit , Is configured to send a trigger indication to the terminal for indicating whether the codebook fed back by the terminal is successfully received.
  • the processing unit deletes the information of the received codebook from the information of the codebook to be fed back by the terminal maintained by the network device.
  • the sending unit sends to the terminal a trigger indication for indicating that the codebook fed back by the terminal is successfully received.
  • the processing unit when the codebook fed back by the terminal is not successfully received, retains information about the codebook that the terminal is not successfully receiving feedback in the information of the codebook to be fed back by the terminal maintained by the network device.
  • the sending unit sends to the terminal a trigger indication for indicating that the codebook fed back by the terminal is not successfully received.
  • the processing unit is further configured to update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the codebook fed back by the terminal is successfully received.
  • the processing unit accumulates the number of codebooks to be fed back when the codebooks to be fed back contained in the queue for recording the codebooks to be fed back are not empty, to obtain The DAI parameter characterizing the accumulated number of codebooks to be fed back.
  • the processing unit resets the number of codebooks to be fed back to obtain the characterizing reset to be fed back code The DAI parameter of this quantity.
  • the processing unit accumulates the number of codebooks to be fed back to obtain a DAI parameter representing the number of codebooks to be fed back accumulated.
  • a feedback device including:
  • Processor a memory used to store executable instructions of the processor
  • the processor is configured to execute the feedback method described in the first aspect or any one of the implementation manners of the first aspect.
  • a feedback device including:
  • Processor a memory used to store executable instructions of the processor
  • the processor is configured to execute the feedback method described in the second aspect or any one of the implementation manners of the second aspect.
  • a non-transitory computer-readable storage medium When instructions in the storage medium are executed by a processor of a mobile terminal, the mobile terminal can execute the first aspect or the first aspect. Aspect any one of the feedback methods described in the implementation manner.
  • a non-transitory computer-readable storage medium When instructions in the storage medium are executed by a processor of a network device, the network device can execute the second aspect or the second aspect. Aspect any one of the feedback methods described in the implementation manner.
  • the network device and the terminal each maintain a codebook to be fed back, and the network device determines a trigger indication (Sequence Update indicator, based on whether the network device successfully receives the codebook that has been fed back) SUI).
  • the trigger indication is used to indicate whether the network device successfully receives the codebook that has been fed back.
  • the network device sends a trigger indication to the terminal, triggers the terminal to determine the queue of the codebook to be fed back, and sends the codebook to be fed back of the queue of the codebook to be fed back, reducing the feedback delay.
  • Fig. 1 is a schematic diagram showing the structure of a communication system according to some exemplary embodiments.
  • Fig. 2 is a schematic diagram showing a codebook feedback according to an exemplary embodiment.
  • Fig. 3 is a flow chart showing a feedback method according to an exemplary embodiment.
  • Fig. 4 is a flow chart showing a feedback method according to an exemplary embodiment.
  • Fig. 5 is a schematic diagram showing a codebook feedback according to an exemplary embodiment.
  • Fig. 6 is a schematic diagram showing a codebook feedback according to an exemplary embodiment.
  • Fig. 7 is a schematic diagram showing a codebook feedback according to an exemplary embodiment.
  • Fig. 8 is a block diagram showing a feedback device according to an exemplary embodiment.
  • Fig. 9 is a block diagram showing a feedback device according to an exemplary embodiment.
  • Fig. 10 is a block diagram showing a device according to an exemplary embodiment.
  • Fig. 11 is a block diagram showing a device according to an exemplary embodiment.
  • the wireless communication system includes a terminal 100 and a network device 200.
  • the terminal 100 is connected to the network device 200 through wireless resources, and transmits and receives data.
  • the wireless communication system shown in FIG. 1 is only for schematic illustration, and the wireless communication system may also include other network equipment, such as core network equipment, wireless relay equipment, and wireless backhaul equipment. Not shown in Figure 1.
  • the embodiments of the present disclosure do not limit the number of network devices and the number of terminals included in the wireless communication system.
  • the wireless communication system in the embodiments of the present disclosure is a network that provides wireless communication functions.
  • Wireless communication systems can use different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA) , Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (Single Carrier FDMA, SC-FDMA), Carrier Sense Multiple access/conflict avoidance (Carrier Sense Multiple Access with Collision Avoidance).
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • TDMA time division multiple access
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • Single Carrier Frequency Division Multiple Access Single Carrier Frequency Division Multiple Access
  • SC-FDMA SC-FDMA
  • Carrier Sense Multiple access/conflict avoidance Carrier Sense Multiple Access with Collision Avoidance
  • the network can be divided into 2G (English: generation) network, 3G network, 4G network or future evolution network, such as 5G network, 5G network can also be called a new wireless network ( New Radio, NR).
  • 2G International: generation
  • 3G network 4G network or future evolution network, such as 5G network
  • 5G network can also be called a new wireless network ( New Radio, NR).
  • New Radio New Radio
  • the wireless communication network is sometimes referred to simply as a network in this disclosure.
  • the network device 200 involved in the present disclosure may also be referred to as a wireless access network device.
  • the wireless access network equipment can be: base station, evolved base station (evolved node B, base station), home base station, access point (AP) in wireless fidelity (WIFI) system, wireless relay Node, wireless backhaul node, transmission point (transmission point, TP), or transmission and reception point (transmission and reception point, TRP), etc., can also be the gNB in the NR system, or can also be a component or part of the equipment constituting the base station Wait.
  • the network device may also be a vehicle-mounted device. It should be understood that, in the embodiments of the present disclosure, the specific technology and specific device form adopted by the network device are not limited.
  • the terminal 100 involved in the present disclosure may also be referred to as terminal equipment, user equipment (UE), mobile station (Mobile Station, MS), mobile terminal (Mobile Terminal, MT), etc., which are a kind of direction
  • the user provides a device with voice and/or data connectivity.
  • the terminal may be a handheld device with a wireless connection function, a vehicle-mounted device, etc.
  • some examples of terminals are: smart phones (Mobile Phone), Pocket Computers (Pocket Personal Computer, PPC), handheld computers, personal digital assistants (Personal Digital Assistant, PDA), notebook computers, tablet computers, wearable devices, or Vehicle equipment, etc.
  • the terminal device when it is a vehicle-to-vehicle (V2X) communication system, the terminal device may also be a vehicle-mounted device. It should be understood that the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal.
  • the terminal 100 communicates with the network device 200, and the process in which the terminal 100 sends data to the network device 200 can be referred to as uplink transmission.
  • the process of the network device 200 sending data to the terminal 100 may be referred to as downlink transmission.
  • a hybrid automatic repeat request (Hybrid Automatic Repeat ReQuest, HARQ) feedback technology is adopted to ensure the reliability of transmission.
  • NR-U NR-based unlicensed frequency bands
  • NR-U and Long Term Evolution (Long Term Evolution, LTE)-based Assisted Access are respectively two network technologies that use NR air interface and LTE air interface in unlicensed frequency bands.
  • LTE Long Term Evolution
  • LAA Long Term Evolution-based Assisted Access
  • RAT Radio Access Technology
  • LAA clear channel assessment
  • LBT Listen Before Talk
  • the physical uplink control channel (PUCCH) that carries the Hybrid Automatic Repeat request (Hybrid Automatic Repeat request, HARQ) feedback information is not blocked by the base station and other network equipment 200 If the reception is successful, if the network device 200 triggers the retransmission at this time, resources will be wasted. Therefore, a mechanism triggered by the network device 200 is introduced in the related art to merge these feedback failure information into the subsequent PUCCH for transmission, so as to provide multiple transmission opportunities for HARQ.
  • PUCCH physical uplink control channel
  • HARQ Hybrid Automatic Repeat request
  • Radio Access Network Radio Access Network 1#ah-1901 meeting
  • it has been reached to support network equipment 200 for the previous channel occupation time (Channel Protocol for triggering HARQ feedback in the physical Downlink Shared channel (PDSCH) or the previous HARQ feedback window in the Occupancy Time (COT) period
  • PDSCH physical Downlink Shared channel
  • COT Occupancy Time
  • the probability of missed detection of the Physical Downlink Control Channel (PDCCH)/PUCCH is very low, and the loss of 4 PDCCHs in a row can be basically ignored.
  • the HARQ codebook accumulation feedback mechanism triggered by the network device 200 is introduced to indicate the accumulated unconfirmed PDSCH, and the Downlink Assignment Index (DAI) bit is extended to allow DAI to continue between different HARQ feedback windows.
  • DAI Downlink Assignment Index
  • the HARQ codebook accumulation feedback mechanism triggered by the network device 200 if the previous HARQ codebook retransmission is triggered in the middle of the current HARQ codebook, there may be differences in the HARQ codebook size and PDSCH codebook size between the network device 200 and the terminal 100.
  • the problem of inconsistent understanding of the corresponding positions in the codebook is the problem of ambiguity in the HARQ codebook between the network device 200 and the terminal 100.
  • the problem of the HARQ codebook ambiguity between the network device and the terminal may be caused, in related technologies, it is proposed to introduce the codebook group number. (Group index, GI) and uplink feedback result confirmation information (New Feedback indicator, NFI) mechanism.
  • GI and NFI are newly added to the downlink control information (DCI), and the problem of ambiguity in the HARQ codebook between network devices and terminals is solved by cross-grouping and continuous accumulation of DAI in the group.
  • DCI downlink control information
  • GI represents the group number of the PDSCH corresponding to the DCI where it is located, for example, it is represented by a different value of 1 bit.
  • the codebooks of the same group will be fed back together.
  • NFI occupies 1 bit, this field is turned over to indicate that the feedback has been received by the network device, and the DAI of the corresponding group is reset.
  • the GI field corresponding to PDSCH#1 and PDSCH#2 is 0.
  • the counted downlink assignment index (C-DAI) field of PDSCH#1 is 00
  • the total downlink assignment index (T-DAI) field is 00
  • the NFI value is 0.
  • the C-DAI field of PDSCH#2 is 00
  • the T-DAI field is 00
  • the NFI value is 0. Since PDSCH#3 is transmitted before codebook 1 (Uplink control information (UCI) #1) is fed back, the network device 200 cannot predict the feedback result of codebook 1 at this time. Therefore, the network device 200 assigns PDSCH#3 to a packet different from PDSCH#1 and PDSCH#2 by setting the GI field of PDSCH#3 to 1, and resetting C-DAI and T-DAI.
  • the network device assigns subsequent PDSCH#4 and PDSCH#5 to group 1, and feeds back the HARQ information of group 1 in codebook 2.
  • PDSCH#6 and PDSCH#7 are transmitted before codebook 2 feedback, so the network device allocates them to group 0, and feeds back all HARQ information in group 0 for the first time and repeated feedback in codebook 3.
  • the feedback information can only be transmitted on the PUCCH corresponding to the group number, and cannot be transmitted immediately in the next uplink transmission, which increases the feedback delay.
  • the HARQ feedback of PDSCH#1 and PDSCH#2 is fed back in codebook 3.
  • there is a gap between the codebook feedback opportunities of codebook 2 with GI 1, which causes a certain delay and increases the feedback delay, which is not good for low-latency scenarios.
  • the embodiments of the present disclosure provide a feedback method.
  • the network device and the terminal each maintain the codebook to be fed back, and the network device determines the trigger indication (Sequence Update indicator, SUI) based on whether the network device successfully receives the codebook that has been fed back. ).
  • the trigger indication is used to indicate whether the network device successfully receives the codebook that has been fed back.
  • the network device sends a trigger indication to the terminal, triggers the terminal to determine the queue of the codebook to be fed back, and sends the codebook to be fed back of the queue of the codebook to be fed back, reducing the feedback delay.
  • Fig. 3 is a flowchart showing a feedback method according to an exemplary embodiment. As shown in Fig. 3, the feedback method is used in a network device, and the network device maintains the information of the codebook to be fed back by the terminal, and includes the following steps.
  • step S11 it is determined whether the codebook fed back by the terminal is successfully received.
  • step S12 according to whether the codebook fed back by the terminal is successfully received, the information of the codebook to be fed back by the terminal maintained by the network device is updated.
  • step S13 a trigger indication for indicating whether the codebook fed back by the terminal is successfully received is sent to the terminal.
  • the codebook is transmitted through Unlicensed Band.
  • the embodiments of the present disclosure do not limit that the trigger indication must be transmitted through an unlicensed band Unlicensed Band.
  • the trigger indication may be transmitted through a licensed band licensed Band.
  • the trigger indication is transmitted through a licensed band.
  • the embodiments of the present disclosure do not limit that the trigger indication must be transmitted through a licensed band.
  • the trigger indication may be transmitted through an unlicensed band.
  • Fig. 4 is a flowchart showing a feedback method according to an exemplary embodiment. As shown in Fig. 4, the feedback method is used in a terminal, and the terminal maintains a codebook to be fed back to a network device, including the following steps.
  • step S21 the queue of the codebook to be fed back is determined according to the trigger instruction sent by the network device.
  • the trigger indication is used to indicate whether the feedback codebook is successfully received.
  • step S22 the codebook to be fed back in the queue of the codebook to be fed back is fed back.
  • the codebook is transmitted through Unlicensed Band.
  • the embodiments of the present disclosure do not limit that the trigger indication must be transmitted through an unlicensed band Unlicensed Band.
  • the trigger indication may be transmitted through a licensed band licensed Band.
  • the trigger indication is transmitted through a licensed band.
  • the embodiments of the present disclosure do not limit that the trigger indication must be transmitted through a licensed band.
  • the trigger indication may be transmitted through an unlicensed band.
  • the network device maintains the information of the codebook to be fed back by the terminal, and updates the information of the maintained codebook to be fed back by the terminal according to whether the codebook fed back by the terminal is successfully received, so that the codebook can be updated in time.
  • the network device sends a trigger instruction to the terminal.
  • the trigger indication is used to indicate whether the codebook fed back by the terminal is successfully received.
  • the terminal determines the queue of the codebook to be fed back based on the trigger instruction sent by the network device, realizes the synchronous update of the codebook, and determines the codebook to be fed back, which can solve the problem of codebook ambiguity between the network device and the terminal.
  • the terminal feeds back the codebook to be fed back in the queue of the codebook to be fed back based on the trigger indication sent by the network device, which can realize the transmission of the codebook to be fed back immediately when there is an uplink transmission opportunity, ensuring Lower feedback delay.
  • the feedback indication may be a bit, and the different value of the bit indicates whether the network device successfully receives the feedback codebook.
  • the first value of the bit indicates that the network device has successfully received the feedback codebook
  • the second value of the bit indicates that the network device has not successfully received the feedback codebook.
  • whether the bit is inverted can be used to indicate whether the network device successfully receives the feedback codebook. For example, bit flipping indicates that the network device successfully received the feedback codebook. If the bit is not inverted, it indicates that the network device has not successfully received the feedback codebook.
  • the feedback indication is expressed by bits, and 1 bit can be used to determine the codebook of the queue to be sent back by the terminal and trigger the transmission, and solve the problem of codebook ambiguity between the network device and the terminal. .
  • the trigger indication in the embodiment of the present disclosure may be sent through DCI.
  • the network device sends a trigger indication through DCI.
  • the terminal obtains the trigger indication by receiving the DCI.
  • the terminal determines whether the network device successfully receives the feedback codebook according to the feedback instruction sent by the network device.
  • the terminal when the feedback indication is used to indicate that the network device successfully receives the feedback codebook, the terminal determines that the network device successfully receives the feedback codebook. When the feedback indication is used to indicate that the network device has not successfully received the feedback codebook, the terminal determines that the network device has not successfully received the feedback codebook.
  • the network device may not send the trigger indication when the feedback codebook is not successfully received.
  • the terminal does not receive the trigger indication, it can be determined that the network device has not successfully received the feedback codebook.
  • the terminal may fail to receive the trigger indication due to a channel failure.
  • the terminal does not receive the trigger indication, it can be determined that the network device has not successfully received the feedback codebook.
  • the network device updates the information that the network device maintains the codebook to be fed back by the terminal according to whether the codebook fed back by the terminal is successfully received.
  • the terminal determines the queue of the codebook to be fed back according to whether the network device successfully receives the feedback codebook.
  • the network device when the network device successfully receives the codebook fed back by the terminal, the information of the received codebook is deleted from the information of the codebook to be fed back by the terminal maintained by the network device, so as to realize the codebook to be fed back. Information update and confirmation.
  • the network device when the network device successfully receives the codebook fed back by the terminal, it sends a trigger indication for indicating that the codebook fed back by the terminal is successfully received to the terminal.
  • the terminal When the terminal receives the trigger instruction sent by the network device, if the trigger instruction is used to indicate that the network device has successfully received the feedback codebook, the feedback codebook is deleted from the queue of the codebook currently to be fed back to obtain the waiting The queue of the feedback codebook is used to update the queue of the codebook to be fed back.
  • deleting the information of the received codebook from the information of the codebook to be fed back by the terminal maintained by the network device does not affect the continued accumulation of the codebook to be fed back during this period.
  • the network device in the embodiment of the present disclosure may update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the codebook fed back by the terminal is successfully received.
  • network equipment and terminals can determine codebook information based on the updated DAI parameters, such as codebook location and codebook size.
  • the network device successfully receives the codebook fed back by the terminal, when the codebook to be fed back contained in the queue that records the codebook to be fed back is not empty, the number of codebooks to be fed back is accumulated , Get the DAI parameter representing the number of codebooks to be fed back, and reset the number of codebooks to be fed back when the number of codebooks to be fed back contained in the queue for recording the codebooks to be fed back is empty, to obtain the number of codebooks to be fed back to represent reset The DAI parameters.
  • the terminal may also update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the network device successfully receives the codebook that has been fed back. For example, the terminal updates the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to the trigger indication.
  • the terminal determines that the network device has successfully received the codebook fed back by the terminal, when the queue of the codebook to be fed back is not empty, the number of codebooks to be fed back is accumulated to obtain the DAI parameter representing the number of codebooks to be fed back accumulated.
  • the queue of codebooks to be fed back is empty, the number of codebooks to be fed back is reset, and the DAI parameter representing the number of codebooks to be fed back to be reset is obtained.
  • the terminal may determine whether the network device successfully receives the feedback codebook based on the trigger indication. Wherein, if the trigger indication is used to indicate that the network device has successfully received the feedback codebook, the terminal determines that the network device has successfully received the feedback codebook.
  • the DAI parameter is updated, when the queue of the codebook to be fed back is not empty, the number of codebooks to be fed back is accumulated to obtain the DAI parameter representing the number of codebooks to be fed back accumulated. When the queue of codebooks to be fed back is empty, the number of codebooks to be fed back is reset, and the DAI parameter representing the number of codebooks to be fed back to be reset is obtained.
  • the network device when the network device fails to successfully receive the codebook fed back by the terminal, the information about the codebook that the terminal fails to receive feedback is retained in the information of the codebook to be fed back by the terminal maintained by the network device, so as to achieve Confirmation and update of the information of the codebook to be fed back.
  • the network device when the network device fails to successfully receive the codebook fed back by the terminal, it sends to the terminal a trigger indication for indicating that the codebook fed back by the terminal is not successfully received.
  • the terminal When the terminal receives the trigger indication sent by the network device, if the trigger indication is used to indicate that the network device has not successfully received the codebook that has been fed back, the current queue of the codebook to be fed back is determined as the queue of the codebook to be fed back, so as to realize the waiting Confirmation and real-time update of the queue of the feedback codebook.
  • the current queue of the codebook to be fed back is determined as the queue of the codebook to be fed back, which does not affect the continued accumulation of the codebook to be fed back during this period. Because there is no deletion, the current queue of the codebook to be fed back is actually The above is the codebook that has been unsuccessfully sent the previous time, and the codebook that has been accumulated during this period.
  • the network device in the embodiment of the present disclosure may update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the codebook fed back by the terminal is successfully received. So that the network equipment and the terminal can determine the codebook information based on the updated DAI parameters, such as the codebook position, the codebook size, etc. simultaneously.
  • the network device if the network device fails to successfully receive the codebook that has been fed back, the network device retains the codebook that has not successfully received feedback from the terminal in the information of the codebook to be fed back by the terminal maintained by the network device. And accumulate the number of codebooks to be fed back to obtain the DAI parameter representing the number of codebooks to be fed back.
  • the terminal may update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the network device successfully receives the codebook fed back by the terminal. For example, the terminal updates the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to the trigger indication.
  • the terminal determines that the network device has not successfully received the codebook that has been fed back, the terminal maintains the codebook to be fed back in the terminal, retains the codebook that has not successfully received the feedback from the terminal, and determines the current queue of the codebook to be fed back as the codebook to be fed back. Queue, and accumulate the number of codebooks to be fed back to obtain the DAI parameter representing the number of codebooks to be fed back.
  • the terminal may determine whether the network device successfully receives the feedback codebook based on the trigger indication. Wherein, if the trigger indication is used to indicate that the network device has not successfully received the feedback codebook, the network device determines that the feedback codebook has not been successfully received, and then the number of codebooks to be fed back is accumulated to obtain DAI representing the number of codebooks to be fed back. parameter.
  • the terminal may also determine the queue of the codebook to be fed back as the queue of the codebook to be fed back, and accumulate the codebook to be fed back. The number, the DAI parameter representing the number of accumulated codebooks to be fed back is obtained.
  • the terminal after receiving the trigger instruction sent by the network device, the terminal determines the queue of the codebook to be fed back, and can feed back the codebook to be fed back in the queue of the codebook to be fed back.
  • the terminal may determine the codebook to be fed back to be uploaded according to the channel resource, for example, upload all the codebooks to be fed back in the queue of the codebook to be fed back, or also It is possible to upload part of the codebooks in the queue of the codebook to be fed back.
  • the network device updates the information of the codebook to be fed back by the terminal maintained by the network device based on whether the feedback codebook is successfully received, and determines and sends a trigger indication for indicating whether the network device successfully receives the feedback codebook.
  • the terminal determines whether the network device successfully receives the feedback codebook and determines the queue of the codebook to be fed back. After receiving the trigger indication, the terminal feeds back the codebook to be fed back at the first opportunity to feed back the codebook to be fed back.
  • the codebook to be fed back in the queue can not only solve the problem of codebook ambiguity between the network device and the terminal, but also provide multiple transmission opportunities for codebook feedback, improve reliability, and ensure low latency.
  • the feedback method mentioned above will be described below in combination with practical applications.
  • the following takes the network equipment as the base station side and the terminal as the user equipment UE side as an example for description.
  • the present disclosure enhances the indication content of the DCI and adds a trigger indication (Sequence Update Indicator, SUI).
  • SUI Sequence Update Indicator
  • the base station side and the UE side each maintain a queue of codebooks to be fed back, and the queue of codebooks to be fed back includes all the codebooks in the feedback queue for each uplink transmission of the user side.
  • SUI is a newly added 1-bit indication field, and the base station uses this field to indicate the UE in the DCI.
  • SUI rollover means that the base station has successfully received the HARQ feedback that has been fed back, that is, the previous HARQ feedback, and the UE will update the queue at this time. On the contrary, if the SUI does not turn over, it means that the base station did not successfully receive the last feedback.
  • the UE will not update the queue, and will start feedback from the beginning of the queue again in the next uplink transmission.
  • SUI the trigger indication
  • DAI adopts the accumulation method across the feedback window to determine the PDSCH corresponding to each bit of the codebook. Therefore, the use of this solution can ensure that the base station and the user end have the same understanding of the size and content of the codebook.
  • the ambiguity of the HARQ feedback codebook between the gNB and the UE is solved with an overhead of 1 bit, which provides a lower delay while increasing the HARQ feedback opportunity.
  • the present disclosure proposes a HARQ cumulative feedback scheme that combines DCI content enhancement and HARQ codebook queue feedback.
  • the changes made by the base station side and the terminal side and the codebook determination method are as follows:
  • Base station side After receiving the HARQ feedback successfully, the base station will flip the SUI in the next DCI, update the queue and check whether the queue is empty after the update, reset DAI if the queue is empty, otherwise continue to accumulate DAI. After the base station fails to receive the HARQ feedback, it does not flip the SUI, does not update the queue, and continues to accumulate DAI.
  • the user side checks the SUI field in the following DCI after feedback. If the SUI is overturned, update the queue and check whether the queue is empty after the update. If the queue is empty, the default DAI has been reset, otherwise the default continues to accumulate DAI. If SUI does not roll over, the queue will not be updated, and DAI will continue to accumulate by default.
  • Codebook determination Both the base station and the user terminal determine the codebook information according to the queue start point and the DAI field.
  • FIG. 5 a schematic diagram of feedback codebook in a sequential feedback scenario.
  • the base station triggers cumulative feedback.
  • the base station will not flip the SUI field, and continue to accumulate the values of C-DAI and T-DAI.
  • the UE receives PDSCH#6 and PDSCH#7, it will check that the SUI field in the DCI is not overturned.
  • the UE will start from the HARQ feedback information of PDSCH#3 to determine the codebook position according to the DAI information and perform feedback. The codebook 3 feedback failed, and the system continues the same processing.
  • Codebook 4 will contain feedback information of PDSCH#3-PDSCH#9. After the codebook 4 is successfully fed back, the base station will flip the SUI field in the DCI of PDSCH#10 and update the queue of the codebook to be fed back. At the same time, it is checked that all the codebooks have reported success at this time, so reset DAI to 0. The user updates the queue while checking the SUI rollover. At this time, it is checked that all codebooks have been successfully fed back, so the default DAI accumulation has been reset.
  • the feedback method provided by the embodiments of the present disclosure will not cause the problem of codebook ambiguity.
  • the codebook 1 is fed back in the middle of the second group of PDSCHs, resulting in PDSCH#3 being unable to predict the feedback result during transmission, so the base station will continue to accumulate the value of DAI when scheduling PDSCH#3. Since the feedback of codebook 1 fails, the base station does not reverse the SUI and continues to accumulate DAI.
  • codebook 2 the user will determine the size of the codebook according to the PDSCH#1 at the head of the team and the HARQ timing information, and determine the information at each position of the codebook according to the DAI field.
  • the SUI is reversed, but at this time PDSCH#6 and PDSCH#7 are not fed back due to the timing relationship, so the team head is updated to PDSCH#6 and the accumulation of DAI will not be reset. Therefore, in codebook 3, the feedback will start from the position of PDSCH#6 at the head of the team.
  • the present invention can still avoid the problem of ambiguity in the HARQ feedback codebook between the base station and the user in the scenario where the entire group of PDSCHs are lost.
  • the codebook 2 corresponding to the missing PDSCH group fails to feed back, and the SUI will not be reversed.
  • the user can obtain the expected feedback result of codebook 1 in the DCI of the next set of downlink data PDSCH#7 and PDSCH#8, and determine the number of lost PDSCHs according to the continuously accumulated DAI, and then determine the feedback codebook 3.
  • the embodiment of the present disclosure also provides a feedback device.
  • the feedback device provided in the embodiments of the present disclosure includes hardware structures and/or software modules corresponding to each function.
  • the embodiments of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered as going beyond the scope of the technical solutions of the embodiments of the present disclosure.
  • Fig. 8 is a block diagram showing a feedback device according to an exemplary embodiment.
  • the feedback device 100 is applied to a terminal 100, and the terminal maintains a codebook to be fed back.
  • the feedback device 100 includes a determining unit 101 and a feedback unit 102.
  • the determining unit 101 is configured to determine a queue of the codebook to be fed back according to a trigger indication sent by a network device, and the trigger indication is used to indicate whether the fed back codebook has been successfully received.
  • the feedback unit 102 is configured to feed back the codebook to be fed back in the queue of the codebook to be fed back.
  • the determining unit 101 deletes the codebook that has been fed back from the queue of the codebook to be fed back, and obtains the codebook to be fed back. queue.
  • the determining unit 101 determines the queue of the codebook to be fed back currently as the queue of the codebook to be fed back.
  • the determining unit 101 is further configured to:
  • the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back is updated according to the trigger indication.
  • the determining unit 101 accumulates the number of codebooks to be fed back when the queue of the codebook to be fed back is not empty, to obtain the characterization accumulation waiting The DAI parameter of the number of codebooks is fed back.
  • the determining unit 101 resets the number of codebooks to be fed back to obtain the DAI parameter representing the number of codebooks to be fed back to be reset.
  • the determining unit 101 accumulates the number of codebooks to be fed back to obtain a DAI parameter representing the number of codebooks to be fed back.
  • the feedback unit 102 uploads all the codebooks to be fed back in the queue of the codebooks to be fed back.
  • Fig. 9 is a block diagram showing a feedback device according to an exemplary embodiment. 9, the feedback device 200 is applied to a network device 200, and the network device 200 maintains information of a codebook to be fed back by a terminal.
  • the feedback device 200 includes a receiving unit 201, a processing unit 202, and a sending unit 203.
  • the receiving unit 201 is configured to determine whether the codebook fed back by the terminal is successfully received.
  • the processing unit 202 is configured to update the information of the codebook to be fed back by the terminal maintained by the network device according to whether the codebook fed back by the terminal is successfully received.
  • the sending unit 203 is configured to send to the terminal a trigger indication for indicating whether the codebook fed back by the terminal is successfully received.
  • the processing unit 202 deletes the information of the received codebook from the information of the codebook to be fed back by the terminal maintained by the network device.
  • the sending unit 203 sends to the terminal a trigger indication for indicating that the codebook fed back by the terminal is successfully received.
  • the processing unit 202 when the codebook fed back by the terminal is not successfully received, the processing unit 202 retains information about the codebook that the terminal is not successfully fed back in the information of the codebook to be fed back by the terminal maintained by the network device.
  • the sending unit 203 sends to the terminal a trigger indication for indicating that the codebook fed back by the terminal is not successfully received.
  • processing unit 202 is further configured to update the DAI parameter used to record the number of codebooks to be fed back contained in the queue of the codebooks to be fed back according to whether the codebook fed back by the terminal is successfully received.
  • the processing unit 202 if the codebook fed back by the terminal is successfully received, the processing unit 202 accumulates the number of codebooks to be fed back when the codebooks to be fed back contained in the queue for recording the codebooks to be fed back are not empty to obtain the characterization
  • the DAI parameter of the number of codebooks to be fed back is accumulated, and when the codebooks to be fed back contained in the queue for recording the codebooks to be fed back are empty, the processing unit 202 resets the number of codebooks to be fed back to obtain the characterization of the number of codebooks to be fed back to be reset The DAI parameters.
  • the processing unit 202 accumulates the number of codebooks to be fed back to obtain a DAI parameter representing the number of codebooks to be fed back accumulated.
  • Fig. 10 is a block diagram showing a device 300 for feedback according to an exemplary embodiment.
  • the device 300 may be a mobile phone, a computer, a digital broadcasting terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.
  • the device 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input/output (I/O) interface 312, a sensor component 314, And the communication component 316.
  • the processing component 302 generally controls the overall operations of the device 300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations.
  • the processing component 302 may include one or more processors 820 to execute instructions to complete all or part of the steps of the foregoing method.
  • the processing component 302 may include one or more modules to facilitate the interaction between the processing component 302 and other components.
  • the processing component 302 may include a multimedia module to facilitate the interaction between the multimedia component 308 and the processing component 302.
  • the memory 304 is configured to store various types of data to support the operation of the device 300. Examples of these data include instructions for any application or method operating on the device 300, contact data, phone book data, messages, pictures, videos, etc.
  • the memory 304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable and Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic Disk or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable and Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic Disk Magnetic Disk or Optical Disk.
  • the power component 306 provides power to various components of the device 300.
  • the power component 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 300.
  • the multimedia component 308 includes a screen that provides an output interface between the device 300 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touch, sliding, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure related to the touch or slide operation.
  • the multimedia component 308 includes a front camera and/or a rear camera. When the device 300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.
  • the audio component 310 is configured to output and/or input audio signals.
  • the audio component 310 includes a microphone (MIC), and when the device 300 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode, the microphone is configured to receive an external audio signal.
  • the received audio signal can be further stored in the memory 304 or sent via the communication component 316.
  • the audio component 310 further includes a speaker for outputting audio signals.
  • the I/O interface 312 provides an interface between the processing component 302 and a peripheral interface module.
  • the above-mentioned peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: home button, volume button, start button, and lock button.
  • the sensor component 314 includes one or more sensors for providing the device 300 with various aspects of status assessment.
  • the sensor component 314 can detect the on/off status of the device 300 and the relative positioning of components.
  • the component is the display and the keypad of the device 300.
  • the sensor component 314 can also detect the position change of the device 300 or a component of the device 300. , The presence or absence of contact between the user and the device 300, the orientation or acceleration/deceleration of the device 300, and the temperature change of the device 300.
  • the sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects when there is no physical contact.
  • the sensor component 314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • the communication component 316 is configured to facilitate wired or wireless communication between the apparatus 300 and other devices.
  • the device 300 can access a wireless network based on a communication standard, such as WiFi, 2G, or 3G, or a combination thereof.
  • the communication component 316 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 316 further includes a near field communication (NFC) module to facilitate short-range communication.
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the apparatus 300 may be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing equipment (DSPD), programmable logic devices (PLD), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic components are implemented to implement the above methods.
  • ASIC application specific integrated circuits
  • DSP digital signal processors
  • DSPD digital signal processing equipment
  • PLD programmable logic devices
  • FPGA field programmable A gate array
  • controller microcontroller, microprocessor, or other electronic components are implemented to implement the above methods.
  • non-transitory computer-readable storage medium including instructions, such as the memory 304 including instructions, and the foregoing instructions may be executed by the processor 820 of the device 300 to complete the foregoing method.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • Fig. 11 is a block diagram showing a device 400 for feedback according to an exemplary embodiment.
  • the apparatus 400 may be provided as a network device.
  • the device 400 includes a processing component 422, which further includes one or more processors, and a memory resource represented by the memory 432, for storing instructions that can be executed by the processing component 422, such as an application program.
  • the application program stored in the memory 432 may include one or more modules each corresponding to a set of instructions.
  • the processing component 422 is configured to execute instructions to perform the above-mentioned method.
  • the device 400 may also include a power supply component 426 configured to perform power management of the device 400, a wired or wireless network interface 450 configured to connect the device 400 to a network, and an input output (I/O) interface 458.
  • the device 400 can operate based on an operating system stored in the memory 432, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.
  • non-transitory computer-readable storage medium including instructions, such as the memory 404 including instructions, and the foregoing instructions may be executed by the processor 420 of the device 400 to complete the foregoing method.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • plural refers to two or more than two, and other quantifiers are similar.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the singular forms “a”, “said” and “the” are also intended to include plural forms, unless the context clearly indicates other meanings.
  • first, second, etc. are used to describe various information, but the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, expressions such as “first” and “second” can be used interchangeably.
  • first information may also be referred to as second information
  • second information may also be referred to as first information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开是关于一种反馈方法、反馈装置及存储介质。应用于终端的反馈方法，所述终端维护有待反馈的码本，包括：根据网络设备发送的触发指示，确定待反馈码本的队列，所述触发指示用于指示是否已经成功接收到已反馈码本；反馈所述待反馈码本的队列中的待反馈码本。应用于网络设备的反馈方法，所述网络设备维护有终端待反馈码本的信息，包括：确定是否成功接收终端反馈的码本；根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新；向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。通过本公开能够降低反馈时延。

Description

反馈方法、反馈装置及存储介质 技术领域
本公开涉及通信技术领域，尤其涉及反馈方法、反馈装置及存储介质。
背景技术
移动设备的增加和移动互联网的飞速发展带来了移动数据爆炸式的增长，对流量密度、网络容量、用户速率、时延等都提出了更高的要求，为了应对挑战，第五代移动通信(5th generation，5G)新空口(New Radio，NR)面向新场景和新频段进行了全新的空口设计。另一方面，频谱资源短缺是移动通信网络面临的越来越严峻的现实。授权频段尤其是价值较高的低频段资源不仅带宽有限，而且正被日益增长的终端群迅速消耗。为了应对频谱短缺的挑战，增大系统容量，提出了对基于NR的非授权频段(NR-U)的研究计划。
NR-U与基于长期演进(Long Term Evolution，LTE)的辅助授权接入(License Assisted Access，LAA)分别为在非授权频段中使用NR空口和LTE空口的两种网络技术。虽然非授权频段带宽资源丰富，但为了保障使用此频段的不同无线接入技术(Radio Access Technology，RAT)之间的公平共存，在LAA中引入了基于空闲信道检测(Clear Channel Assessment，CCA)的先听后说(Listen Before Talk，LBT)技术。将LBT技术同样引入基于NR的非授权频段(NR-U)是保障公平共存的重要方式。
在NR-U系统中，由于LBT失败或强干扰导致携带混合自动重传请求(Hybrid Automatic Repeat request，HARQ)反馈信息的物理上行控制信道(Physical Uplink Control Channel，PUCCH)没有被基站等网络设备成功接收，若此时网络设备触发重传会导致资源浪费，并且连续丢失PDCCH的情况加剧。故，相关技术中，引入由网络设备触发的HARQ码本累加反馈机制，将这些反馈失败的信息融合到后续的PUCCH当中进行传输，为HARQ提供多次传输机会。
然而，由网络设备触发的HARQ码本累加反馈机制，反馈失败的HARQ码本会存在反馈时延。
发明内容
为克服相关技术中存在的问题，本公开提供一种反馈方法、反馈装置及存储介质。
根据本公开实施例的第一方面，提供一种反馈方法，应用于终端，所述终端维护有待 反馈的码本，所述反馈方法包括：
根据网络设备发送的触发指示，确定待反馈码本的队列，所述触发指示用于指示是否已经成功接收到已反馈码本；反馈所述待反馈码本的队列中的待反馈码本。
一种实施方式中，所述根据接收到网络设备发送的触发指示，确定待反馈码本的队列，包括：
若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则将所述已反馈码本从所述当前待反馈的码本的队列中删除，得到待反馈码本的队列。
另一种实施方式中，所述根据接收到网络设备发送的触发指示，确定待反馈码本的队列，包括：
若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则将当前待反馈码本的队列确定为待反馈码本的队列。
又一种实施方式中，所述反馈方法还包括：
根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则在待反馈码本的队列非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在所述待反馈码本的队列为空时，重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
又一种实施方式中，所述反馈所述待反馈码本的队列中的待反馈码本，包括：
将待反馈码本的队列中的所有待反馈码本全部上传。
根据本公开实施例的第二方面，提供一种反馈方法，应用于网络设备，所述网络设备维护有终端待反馈码本的信息，所述反馈方法包括：
确定是否成功接收终端反馈的码本；根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新；向终端发送用于指示是否成功接收到终端反馈 的码本的触发指示。
一种实施方式中，所述根据是否成功接收到终端反馈的码本对网络设备维护有终端待反馈码本的信息进行更新，包括：
当成功接收到终端反馈的码本时，将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除。
另一种实施方式中，向终端发送用于指示是否成功接收到终端反馈的码本的触发指示，包括：
向终端发送用于指示成功接收到终端反馈的码本的触发指示。
又一种实施方式中，所述根据是否成功接收到终端反馈的码本对网络设备维护有终端待反馈码本的信息进行更新，包括：
当未成功接收到终端反馈的码本时，在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息。
又一种实施方式中，向终端发送用于指示是否成功接收到终端反馈的码本的触发指示，包括：
向终端发送用于指示未能成功接收到终端反馈的码本的触发指示。
又一种实施方式中，所述反馈方法还包括：
根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，根据确定是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
若成功接收到终端反馈的码本，则在记录待反馈码本的队列中所包含的待反馈码本非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在记录待反馈码本的队列中所包含的待反馈码本为空时，重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，根据确定是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
若未成功接收到终端反馈的码本，则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
根据本公开实施例第三方面，提供一种反馈装置，应用于终端，所述终端维护有待反馈的码本，所述反馈装置包括：
确定单元，被配置为根据网络设备发送的触发指示，确定待反馈码本的队列，所述触发指示用于指示是否已经成功接收到已反馈码本；反馈单元，被配置为反馈所述待反馈码本的队列中的待反馈码本。
一种实施方式中，若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则所述确定单元将所述已反馈码本从所述当前待反馈的码本的队列中删除，得到待反馈码本的队列。
另一种实施方式中，若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则所述确定单元将当前待反馈码本的队列确定为待反馈码本的队列。
又一种实施方式中，所述确定单元还被配置为：
根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则所述确定单元在待反馈码本的队列非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在所述待反馈码本的队列为空时，所述确定单元重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则所述确定单元累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
又一种实施方式中，所述反馈单元将待反馈码本的队列中的所有待反馈码本全部上传。
根据本公开实施例的第四方面，提供一种反馈装置，应用于网络设备，所述网络设备维护有终端待反馈码本的信息，所述反馈装置包括：
接收单元，被配置为确定是否成功接收终端反馈的码本；处理单元，被配置为根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新；发送单元，被配置为向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。
一种实施方式中，当成功接收到终端反馈的码本时，所述处理单元将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除。
另一种实施方式中，所述发送单元向终端发送用于指示成功接收到终端反馈的码本的触发指示。
又一种实施方式中，当未成功接收到终端反馈的码本时，所述处理单元在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息。
又一种实施方式中，所述发送单元向终端发送用于指示未能成功接收到终端反馈的码本的触发指示。
又一种实施方式中，所述处理单元还用于：根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，若成功接收到终端反馈的码本，则所述处理单元在记录待反馈码本的队列中所包含的待反馈码本非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在记录待反馈码本的队列中所包含的待反馈码本为空时，所述处理单元重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，若未成功接收到终端反馈的码本，则所述处理单元累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
根据本公开实施例的第五方面，提供一种反馈装置，包括：
处理器；用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：执行第一方面或者第一方面任意一种实施方式中所述的反馈方法。
根据本公开实施例的第六方面，提供一种反馈装置，包括：
处理器；用于存储处理器可执行指令的存储器；
其中，所述处理器被配置为：执行第二方面或者第二方面任意一种实施方式中所述的反馈方法。
根据本公开实施例的第七方面，提供一种非临时性计算机可读存储介质，当所述存储介质中的指令由移动终端的处理器执行时，使得移动终端能够执行第一方面或者第一方面任意一种实施方式中所述的反馈方法。
根据本公开实施例的第八方面，提供一种非临时性计算机可读存储介质，当所述存储介质中的指令由网络设备的处理器执行时，使得网络设备能够执行第二方面或者第二方面任意一种实施方式中所述的反馈方法。
本公开的实施例提供的技术方案可以包括以下有益效果：网络设备和终端各自维护待反馈的码本，并且网络设备基于网络设备是否成功接收到已反馈的码本确定触发指示(Sequence Update indicator，SUI)。触发指示用于指示网络设备是否成功接收到已反馈的码本。网络设备将触发指示发送给终端，触发终端确定待反馈码本的队列，并发送待反馈码本的队列的待反馈码本，降低反馈时延。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限 制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
图1是根据部分示例性实施例示出的通信系统构成示意图。
图2是根据一示例性实施例示出的一种码本反馈示意图。
图3是根据一示例性实施例示出的一种反馈方法的流程图。
图4是根据一示例性实施例示出的一种反馈方法的流程图。
图5是据一示例性实施例示出的一种码本反馈示意图。
图6是据一示例性实施例示出的一种码本反馈示意图。
图7是据一示例性实施例示出的一种码本反馈示意图。
图8是根据一示例性实施例示出的一种反馈装置的框图。
图9是根据一示例性实施例示出的一种反馈装置的框图。
图10是根据一示例性实施例示出的一种装置的框图。
图11是根据一示例性实施例示出的一种装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
本公开实施例提供的反馈方法可应用于图1所示的无线通信系统中。参阅图1所示，该无线通信系统中包括终端100和网络设备200。终端100通过无线资源与网络设备200相连接，并进行数据的发送与接收。
可以理解的是，图1所示的无线通信系统仅是进行示意性说明，无线通信系统中还可包括其它网络设备，例如还可以包括核心网设备、无线中继设备和无线回传设备等，在图1中未画出。本公开实施例对该无线通信系统中包括的网络设备数量和终端数量不做限定。
进一步可以理解的是，本公开实施例的无线通信系统，是一种提供无线通信功能的网络。无线通信系统可以采用不同的通信技术，例如码分多址(code division multiple access, CDMA)、宽带码分多址(wideband code division multiple access，WCDMA)、时分多址(time division multiple access，TDMA)、频分多址(frequency division multiple access，FDMA)、正交频分多址(orthogonal frequency-division multiple access，OFDMA)、单载波频分多址(single Carrier FDMA，SC-FDMA)、载波侦听多路访问/冲突避免(Carrier Sense Multiple Access with Collision Avoidance)。根据不同网络的容量、速率、时延等因素可以将网络分为2G(英文：generation)网络、3G网络、4G网络或者未来演进网络，如5G网络，5G网络也可称为是新无线网络(New Radio，NR)。为了方便描述，本公开有时会将无线通信网络简称为网络。
进一步的，本公开中涉及的网络设备200也可以称为无线接入网设备。该无线接入网设备可以是：基站、演进型基站(evolved node B，基站)、家庭基站、无线保真(wireless fidelity，WIFI)系统中的接入点(access point，AP)、无线中继节点、无线回传节点、传输点(transmission point，TP)或者发送接收点(transmission and reception point，TRP)等，还可以为NR系统中的gNB，或者，还可以是构成基站的组件或一部分设备等。当为车联网(V2X)通信系统时，网络设备还可以是车载设备。应理解，本公开的实施例中，对网络设备所采用的具体技术和具体设备形态不做限定。
进一步的，本公开中涉及的终端100，也可以称为终端设备、用户设备(User Equipment，UE)、移动台(Mobile Station，MS)、移动终端(Mobile Terminal，MT)等，是一种向用户提供语音和/或数据连通性的设备，例如，终端可以是具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：智能手机(Mobile Phone)、口袋计算机(Pocket Personal Computer，PPC)、掌上电脑、个人数字助理(Personal Digital Assistant，PDA)、笔记本电脑、平板电脑、可穿戴设备、或者车载设备等。此外，当为车联网(V2X)通信系统时，终端设备还可以是车载设备。应理解，本公开实施例对终端所采用的具体技术和具体设备形态不做限定。
图1中，终端100与网络设备200进行通信，终端100向网络设备200发送数据的过程可称为上行传输。网络设备200向终端100发送数据的过程可称为下行传输。终端100和网络设备200进行上行传输和下行传输过程中，采用混合式自动重传请求(Hybrid Automatic Repeat ReQuest，HARQ)反馈技术，以保证传输的可靠性。
5G网络中，为了应对频谱短缺的挑战，增大系统容量，提出了对基于NR的非授权频段(NR-U)的研究计划。
NR-U与基于长期演进(Long Term Evolution，LTE)的辅助授权接入(License Assisted  Access，LAA)分别为在非授权频段中使用NR空口和LTE空口的两种网络技术。虽然非授权频段带宽资源丰富，但为了保障使用此频段的不同无线接入技术(Radio Access Technology，RAT)之间的公平共存，在LAA中引入了基于空闲信道检测(Clear Channel Assessment，CCA)的先听后说(Listen Before Talk，LBT)技术。将LBT技术同样引入基于NR的非授权频段(NR-U)是保障公平共存的重要方式。
在NR-U系统中，由于LBT失败或强干扰导致携带混合自动重传请求(Hybrid Automatic Repeat request，HARQ)反馈信息的物理上行控制信道(Physical Uplink Control Channel，PUCCH)没有被基站等网络设备200成功接收，若此时网络设备200触发重传会导致资源浪费。因此，相关技术中引入一种由网络设备200触发的机制将这些反馈失败的信息融合到后续的PUCCH当中进行传输，为HARQ提供多次传输机会。例如，在第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)无线接入网络(Radio Access Network，RAN)1#ah-1901次会议中已达成支持网络设备200为上一信道占用时间(Channel Occupancy Time，COT)周期内的物理下行共享信道(Physical Downlink Shared channel，PDSCH)或上一HARQ反馈窗口触发HARQ反馈的协议
在NR系统中，物理下行控制信道(Physical Downlink Control Channel，PDCCH)/PUCCH漏检的概率非常低，并且对于连续丢失4个PDCCH的情况基本可以忽略。然而，在NR-U系统中，由于引入LBT机制，连续丢失PDCCH的情况增加。为此，引入由网络设备200触发的HARQ码本累加反馈机制，指示累积的未确认的PDSCH，并通过扩展下行分配索引(Downlink assignment index，DAI)比特并允许DAI在不同HARQ反馈窗口间的连续计数HARQ码本数量。通过DAI连续计数的码本数量累加值可以确定出HARQ码本信息。
然而，由网络设备200触发的HARQ码本累加反馈机制，若在当前的HARQ码本中间触发先前的HARQ码本重传，可能会出现网络设备200和终端100之间对于HARQ码本大小以及PDSCH在码本中对应位置的理解不一致的问题，即出现网络设备200和终端100之间HARQ码本模糊的问题。
为了解决由网络设备200触发的HARQ码本累加反馈机制并允许为累积的PDSCH使用连续DAI计数可能导致的网络设备和终端之间HARQ码本模糊的问题，相关技术中，提出引入码本组号(Group index，GI)和上行反馈结果确认信息(New Feedback indicator，NFI)的机制。
相关技术中，在下行控制信息(Downlink control information，DCI)中新增GI和NFI 两个指示，并通过交叉分组和组内DAI连续累加的方式解决网络设备和终端之间HARQ码本模糊的问题。其中，GI代表与所在DCI相对应的PDSCH的组号，例如通过1个比特位的不同取值表示。同一组的码本将在一起进行反馈。NFI占用1bit，该字段翻转代表反馈已经被网络设备接收，并重置对应组的DAI。如图2所示，PDSCH#1、PDSCH#2对应的GI字段为0。PDSCH#1的计数下行分配索引(Counter-Downlink assignment index，C-DAI)字段为00，总下行分配索引(Total-Downlink assignment index，T-DAI)字段为00，NFI值为0。PDSCH#2的C-DAI字段为00，T-DAI字段为00，NFI值为0。由于PDSCH#3在码本1(上行控制信息(Uplink control information，UCI)#1)反馈前传输，此时网络设备200无法预知码本1的反馈结果。于是，网络设备200通过令PDSCH#3的GI字段为1，C-DAI和T-DAI重置，将PDSCH#3分配到与PDSCH#1、PDSCH#2不同的分组。码本1反馈失败后，网络设备将后续的PDSCH#4、PDSCH#5分配到组1，并在码本2反馈组1的HARQ信息。同样，PDSCH#6、PDSCH#7在码本2反馈前传输，于是网络设备将其分配到组0，并在码本3中反馈组0中初次反馈和重复反馈的全部HARQ信息。
然而，上述采用交叉分组方式进行反馈信息(码本)的反馈方式，反馈信息只能在对应组号的PUCCH上传输，无法在下一个上行传输时立即传输，增加了反馈时延。例如图2中，PDSCH#1、PDSCH#2的HARQ反馈需要推迟到下一个与PDSCH#1、PDSCH#2的组号相同的码本反馈机会才能进行反馈重传，即，在GI＝0的码本3中反馈PDSCH#1、PDSCH#2的HARQ反馈。此时，间隔了GI＝1的码本2的码本反馈机会，因此造成一定的时延，增加了反馈的时延，对于低时延场景不利。
有鉴于此，本公开实施例提供一种反馈方法，网络设备和终端各自维护待反馈的码本，并且网络设备基于网络设备是否成功接收到已反馈的码本确定触发指示(Sequence Update indicator，SUI)。触发指示用于指示网络设备是否成功接收到已反馈的码本。网络设备将触发指示发送给终端，触发终端确定待反馈码本的队列，并发送待反馈码本的队列的待反馈码本，降低反馈时延。
图3是根据一示例性实施例示出的一种反馈方法的流程图，如图3所示，反馈方法用于网络设备中，网络设备维护终端待反馈的码本的信息，包括以下步骤。
在步骤S11中，确定是否成功接收终端反馈的码本。
在步骤S12中，根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新。
在步骤S13中，向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。
在一些实施例中，所述码本通过非授权频段Unlicensed Band传输。当然，本公开实施例中并不限定该触发指示必须通过非授权频段Unlicensed Band传输，在一些实施例中触发指示可以通过授权频段licensed Band传输。
在一些实施例中，所述触发指示通过授权频段licensed Band传输。当然，本公开实施例中并不限定该触发指示必须通过授权频段licensed Band传输，在一些实施例中触发指示可以通过非授权频段Unlicensed Band传输。
图4是根据一示例性实施例示出的一种反馈方法的流程图，如图4所示，反馈方法用于终端中，终端维护有待反馈给网络设备的码本，包括如下步骤。
在步骤S21中，根据网络设备发送的触发指示，确定待反馈码本的队列。其中，触发指示用于指示是否成功接收到反馈码本。
在步骤S22中，反馈待反馈码本的队列中的待反馈码本。
在一些实施例中，所述码本通过非授权频段Unlicensed Band传输。当然，本公开实施例中并不限定该触发指示必须通过非授权频段Unlicensed Band传输，在一些实施例中触发指示可以通过授权频段licensed Band传输。
在一些实施例中，所述触发指示通过授权频段licensed Band传输。当然，本公开实施例中并不限定该触发指示必须通过授权频段licensed Band传输，在一些实施例中触发指示可以通过非授权频段Unlicensed Band传输。
本公开实施例中，网络设备维护终端待反馈的码本的信息，并根据是否成功接收到终端反馈的码本对维护的终端待反馈码本的信息进行更新，能够实现码本的及时更新。网络设备向终端发送触发指示。触发指示用于指示是否成功接收到终端反馈的码本。终端基于网络设备发送的触发指示，确定待反馈码本的队列，实现码本的同步更新，并确定待反馈的码本，能够解决网络设备与终端之间码本模糊的问题。进一步的，本公开实施例中，终端基于网络设备发送的触发指示反馈待反馈码本的队列中的待反馈码本，可以实现在有上行传输机会时，立即进行待反馈码本的传输，保证更低的反馈时延。
本公开一些实施方式中，本公开实施例中，反馈指示可以是比特位，通过比特位的不同取值指示网络设备是否成功接收到反馈码本。例如，比特位的第一取值指示网络设备成功接收到反馈码本，比特位的第二取值指示网络设备未能成功接收到反馈码本。本公开实施例中也可以通过比特位是否翻转，即比特位的取值是否变化，指示网络设备是否成功接收到反馈码本。例如，比特位翻转，则指示网络设备成功接收到反馈码本。比特位未翻转，则指示网络设备未能成功接收到反馈码本。
其中，本公开实施例中通过比特位表示反馈指示的方式，可以通过1比特，实现对终端发送待反馈队列的码本的确定以及发送的触发，解决网络设备和终端之间码本模糊的问题。
进一步的，本公开实施例中触发指示可以通过DCI发送。网络设备通过DCI发送触发指示。终端通过接收DCI获取到触发指示。
本公开一些实施方式中，终端根据网络设备发送的反馈指示，确定网络设备是否成功接收到反馈码本。
一种实施方式中，本公开实施例中，在反馈指示用于指示网络设备成功接收到反馈码本时，终端确定网络设备成功接收到反馈码本。在反馈指示用于指示网络设备未能成功接收到反馈码本时，终端确定网络设备未能成功接收到反馈码本。
在一些实施方式中，本公开实施例中，网络设备在未成功接收到反馈码本时，也可不发送触发指示。终端在未收到触发指示时，可以确定网络设备未成功接收到反馈码本。
在一些实施方式中，本公开实施例中，可能由于信道故障导致终端未能接收到触发指示。终端在未收到触发指示时，可以确定网络设备未成功接收到反馈码本。
本公开实施例，网络设备根据是否成功接收到终端反馈的码本对网络设备维护有终端待反馈码本的信息进行更新。终端根据网络设备是否成功接收到反馈码本，确定待反馈码本的队列。
本公开实施例中，在网络设备成功接收到终端反馈的码本时，将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除，以实现待反馈码本的信息的更新以及确定。一些实施方式中，网络设备在成功接收到终端反馈的码本时，向终端发送用于指示成功接收到终端反馈的码本的触发指示。终端接收到网络设备发送的触发指示时，若触发指示用于指示所述网络设备已经成功接收到已反馈码本，则将已反馈码本从当前待反馈的码本的队列中删除，得到待反馈码本的队列，以实现待反馈码本的队列的更新。
可以理解的是，本公开实施例中，将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除，并不影响在此期间继续累积待反馈的码本。
一些实施方式中，本公开实施例中网络设备可以根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。以便网络设备和终端基于更新的DAI参数确定码本信息，例如码本位置，码本大小等。
一些实施方式中，本公开实施例中，网络设备若成功接收到终端反馈的码本，则在记录待反馈码本的队列中所包含的待反馈码本非空时，累加待反馈码本数量，得到表征累加 待反馈码本数量的DAI参数，在记录待反馈码本的队列中所包含的待反馈码本为空时，重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
类似的，本公开实施例中，终端也可以根据网络设备是否成功收到已反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。例如，终端根据触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
其中，终端若确定网络设备成功接收到终端反馈的码本，则在待反馈码本的队列非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。在待反馈码本的队列为空时，重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
可以理解的是，本公开实施例中终端可以基于触发指示，确定网络设备是否成功接收到已反馈码本。其中，若触发指示用于指示网络设备已经成功接收到已反馈码本，则终端确定网络设备已经成功接收到已反馈码本。在进行DAI参数更新时，可以是在待反馈码本的队列非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。在待反馈码本的队列为空时，重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
本公开实施例中，在网络设备未能成功接收到终端反馈的码本时，在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息，以实现待反馈码本的信息的确定以及更新。一些实施方式中，网络设备在未能成功接收到终端反馈的码本时，向终端发送用于指示未成功接收到终端反馈的码本的触发指示。终端接收到网络设备发送的触发指示时，若触发指示用于指示网络设备未能成功接收到已反馈码本，则将当前待反馈码本的队列确定为待反馈码本的队列，以实现待反馈码本的队列的确定以及实时更新。
本公开实施例中将当前待反馈码本的队列确定为待反馈码本的队列，并不影响在此期间继续累积待反馈的码本，因为没有删除，所以当前的待反馈码本的队列实际上就是已经包含了前一次没成功发送的码本，以及在此期间又累积上去的码本。
一些实施方式中，本公开实施例中网络设备可以根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。以便网络设备和终端同步基于更新的DAI参数确定码本信息，例如码本位置，码本大小等。
一些实施方式中，本公开实施例中，网络设备若未能成功接收到已反馈码本，网络设备在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息，并累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
类似的，本公开实施例中，终端可以根据网络设备是否成功接收到终端反馈的码本， 更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。例如，终端根据触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
终端若确定网络设备未能成功接收到已反馈码本，终端在终端维护的待反馈，保留未能成功接收到终端反馈的码本，将当前待反馈码本的队列确定为待反馈码本的队列，并累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
可以理解的是，本公开实施例中终端可以基于触发指示，确定网络设备是否成功接收到已反馈码本。其中，若触发指示用于指示网络设备未成功接收到已反馈码本，则网络设备确定未成功接收到已反馈码本，则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。另一种实施方式中，本公开实施例中，终端若未接收到网络设备发送的触发指示，也可以将当前待反馈码本的队列确定为待反馈码本的队列，并累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
进一步的，本公开实施例中，终端接收到网络设备发送的触发指示后，确定待反馈码本的队列后，可以反馈待反馈码本的队列中的待反馈码本。其中，终端在反馈待反馈码本的队列中的待反馈码本时可以根据信道资源确定上传的待反馈码本，例如将待反馈码本的队列中的所有待反馈码本全部上传，或者也可以将待反馈码本的队列中的部分码本上传。
本公开实施例网络设备基于是否成功接收已反馈码本，对网络设备维护的终端待反馈码本的信息进行更新，并确定和发送用于指示网络设备是否成功接收反馈码本的触发指示。终端基于网络设备发送的触发指示确定网络设备是否成功接收反馈码本并确定待反馈码本的队列，并在接收到触发指示后，在首个反馈待反馈码本的时机反馈待反馈码本的队列中的待反馈码本，不仅能够解决网络设备与终端之间码本模糊的问题，还能够为码本反馈提供多次传输机会，提高可靠性，以及保证较低的时延。
本公开实施例以下结合实际应用对上述涉及的反馈方法进行说明。以下以网络设备为基站端，终端为用户设备UE端为例进行说明。
本公开对DCI的指示内容进行增强，新增一个触发指示(Sequence Update Indicator，SUI)。基站端和UE端各自维护一个待反馈码本的队列，待反馈码本的队列中包括用户端每次上行传输反馈队列中全部的码本。其中，SUI为新增的1bit指示字段，基站通过该字段在DCI中指示UE。SUI翻转代表基站成功接收到已反馈的HARQ反馈，即上一次的HARQ反馈，此时UE会更新队列。反之，SUI不翻转代表基站没有成功接收上一次的反馈，此时UE不会更新队列，并且在下一次的上行传输中再次从队列的起点开始反馈。通过新增的触发指示SUI，可以确保基站和用户根据指示同步更新待反馈队列。同时，DAI 采用跨反馈窗口的累加方式，从而确定码本每一位所对应的PDSCH。因此，采用本方案可以确保基站端和用户端对码本的大小和内容的理解是一致的。相比已有方案，以1bit的开销解决了gNB与UE之间HARQ反馈码本的模糊问题，在增大HARQ反馈机会的同时提供了更低的时延。
为了解决基站触发用户HARQ反馈重传造成的gNB和UE之间HARQ反馈码本的模糊性问题，本公开提出一种DCI内容增强与HARQ码本队列式反馈相结合的HARQ累加反馈方案。针对本公开所提方案，基站侧和终端侧所做的改动以及码本确定的方式如下：
基站侧：基站端接收HARQ反馈成功后，在接下来的DCI中翻转SUI，更新队列并检查更新后队列是否为空，队列为空则重置DAI，否则继续累加DAI。基站端接收HARQ反馈失败后，不翻转SUI，不更新队列，并继续累加DAI。
用户端：用户端在反馈后检查接下来的DCI中的SUI字段。SUI翻转，则更新队列并检查更新后队列是否为空，队列为空则默认DAI已重置，否则默认继续累加DAI。SUI不翻转，则不更新队列，并默认继续累加DAI。
码本确定：基站端和用户端均根据队列起点以及DAI字段确定码本信息。
如图5所示，在顺序反馈场景下反馈码本的示意图。图5中，由于码本2的反馈失败，基站触发累加反馈。在PDSCH#6、PDSCH#7的DCI中，基站不会翻转SUI字段，并继续累加C-DAI和T-DAI的值。UE收到PDSCH#6、PDSCH#7时，会检查到DCI中的SUI字段并未翻转。在下一个上行传输时机，UE会从PDSCH#3的HARQ反馈信息开始按照DAI的信息确定码本位置并进行反馈。码本3反馈失败，系统继续同样的处理。在码本4中，会包含PDSCH#3-PDSCH#9的反馈信息。码本4反馈成功后，基站会在PDSCH#10的DCI中翻转SUI字段并更新待反馈码本的队列。同时检查到此时全部的码本已经反馈成功，于是重置DAI为0。用户在检查到SUI翻转的同时更新队列，此时检查到全部码本已经反馈成功，于是默认DAI的累加已经重置。
在先前的HARQ码本重传在当前的HARQ码本中间被触发的场景中，本公开实施例提供的反馈方法也不会产生码本模糊的问题。如图6所示，码本1在第二组PDSCH的中间反馈，导致PDSCH#3在传输时无法预知反馈的结果，于是基站在调度PDSCH#3时会继续累加DAI的值。由于码本1的反馈失败，基站不翻转SUI并继续累加DAI。在码本2中，用户会根据队首位置PDSCH#1和HARQ定时信息，确定码本大小并根据DAI字段确定码本各个位置上的信息。码本2反馈成功后，SUI翻转，但此时PDSCH#6、PDSCH#7由于定时关系并未进行反馈，于是将队首更新到PDSCH#6的同时DAI的累加不会重置。 于是，在码本3中，会从队首PDSCH#6的位置开始反馈。
除上述场景外，本发明在整组PDSCH丢失的场景中，仍然可以避免出现基站和用户之间HARQ反馈码本模糊的问题。如图7所示，丢失的PDSCH组所对应的码本2反馈失败，SUI不会翻转。用户可以在下一组下行数据PDSCH#7、PDSCH#8的DCI中获得期待的码本1的反馈结果，并根据连续累加的DAI确定丢失的PDSCH个数，进而确定反馈码本3。
基于相同的构思，本公开实施例还提供一种反馈装置。
可以理解的是，本公开实施例提供的反馈装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。结合本公开实施例中所公开的各示例的单元及算法步骤，本公开实施例能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以对每个特定的应用来使用不同的方法来实现所描述的功能，但是这种实现不应认为超出本公开实施例的技术方案的范围。
图8是根据一示例性实施例示出的一种反馈装置框图。参照图8，反馈装置100应用于终端100，终端维护有待反馈的码本，反馈装置100包括确定单元101和反馈单元102。
确定单元101，被配置为根据网络设备发送的触发指示，确定待反馈码本的队列，触发指示用于指示是否已经成功接收到已反馈码本。反馈单元102，被配置为反馈待反馈码本的队列中的待反馈码本。
一种实施方式中，若触发指示用于指示网络设备已经成功接收到已反馈码本，则确定单元101将已反馈码本从当前待反馈的码本的队列中删除，得到待反馈码本的队列。
另一种实施方式中，若触发指示用于指示网络设备未成功接收到已反馈码本，则确定单元101将当前待反馈码本的队列确定为待反馈码本的队列。
又一种实施方式中，确定单元101还被配置为：
根据触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，若触发指示用于指示网络设备已经成功接收到已反馈码本，则确定单元101在待反馈码本的队列非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在待反馈码本的队列为空时，确定单元101重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，若触发指示用于指示网络设备未成功接收到已反馈码本，则确定 单元101累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
又一种实施方式中，反馈单元102将待反馈码本的队列中的所有待反馈码本全部上传。
图9是根据一示例性实施例示出的一种反馈装置框图。参照图9，反馈装置200应用于网络设备200，网络设备200维护有终端待反馈码本的信息，反馈装置200包括接收单元201、处理单元202和发送单元203。
接收单元201，被配置为确定是否成功接收终端反馈的码本。处理单元202，被配置为根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新。发送单元203，被配置为向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。
一种实施方式中，当成功接收到终端反馈的码本时，处理单元202将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除。
另一种实施方式中，发送单元203向终端发送用于指示成功接收到终端反馈的码本的触发指示。
又一种实施方式中，当未成功接收到终端反馈的码本时，处理单元202在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息。
又一种实施方式中，发送单元203向终端发送用于指示未能成功接收到终端反馈的码本的触发指示。
又一种实施方式中，处理单元202还用于：根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
又一种实施方式中，若成功接收到终端反馈的码本，则处理单元202在记录待反馈码本的队列中所包含的待反馈码本非空时，累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数，在记录待反馈码本的队列中所包含的待反馈码本为空时，处理单元202重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
又一种实施方式中，若未成功接收到终端反馈的码本，则处理单元202累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
图10是根据一示例性实施例示出的一种用于反馈的装置300的框图。装置300可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备， 健身设备，个人数字助理等。
参照图10，装置300可以包括以下一个或多个组件：处理组件302，存储器304，电力组件306，多媒体组件308，音频组件310，输入/输出(I/O)的接口312，传感器组件314，以及通信组件316。
处理组件302通常控制装置300的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件302可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件302可以包括一个或多个模块，便于处理组件302和其他组件之间的交互。例如，处理组件302可以包括多媒体模块，以方便多媒体组件308和处理组件302之间的交互。
存储器304被配置为存储各种类型的数据以支持在设备300的操作。这些数据的示例包括用于在装置300上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电力组件306为装置300的各种组件提供电力。电力组件306可以包括电源管理系统，一个或多个电源，及其他与为装置300生成、管理和分配电力相关联的组件。
多媒体组件308包括在所述装置300和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件308包括一个前置摄像头和/或后置摄像头。当设备300处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件310被配置为输出和/或输入音频信号。例如，音频组件310包括一个麦克风(MIC)，当装置300处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器304或经由通信组件316发送。在一些实施例中，音频组件310还包括一个扬声器，用于输出音频信号。
I/O接口312为处理组件302和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件314包括一个或多个传感器，用于为装置300提供各个方面的状态评估。例如，传感器组件314可以检测到设备300的打开/关闭状态，组件的相对定位，例如所述组件为装置300的显示器和小键盘，传感器组件314还可以检测装置300或装置300一个组件的位置改变，用户与装置300接触的存在或不存在，装置300方位或加速/减速和装置300的温度变化。传感器组件314可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件314还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，所述传感器组件314还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件316被配置为便于装置300和其他设备之间有线或无线方式的通信。装置300可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件316经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件316还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置300可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器304，上述指令可由装置300的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
图11是根据一示例性实施例示出的一种用于反馈的装置400的框图。例如，装置400可以被提供为一网络设备。参照图8，装置400包括处理组件422，其进一步包括一个或多个处理器，以及由存储器432所代表的存储器资源，用于存储可由处理组件422的执行的指令，例如应用程序。存储器432中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件422被配置为执行指令，以执行上述方法。
装置400还可以包括一个电源组件426被配置为执行装置400的电源管理，一个有线或无线网络接口450被配置为将装置400连接到网络，和一个输入输出(I/O)接口458。装置400可以操作基于存储在存储器432的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM,LinuxTM，FreeBSDTM或类似。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器404，上述指令可由装置400的处理器420执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
进一步可以理解的是，本公开中“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
进一步可以理解的是，术语“第一”、“第二”等用于描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开，并不表示特定的顺序或者重要程度。实际上，“第一”、“第二”等表述完全可以互换使用。例如，在不脱离本公开范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。
进一步可以理解的是，本公开实施例中尽管在附图中以特定的顺序描述操作，但是不应将其理解为要求按照所示的特定顺序或是串行顺序来执行这些操作，或是要求执行全部所示的操作以得到期望的结果。在特定环境中，多任务和并行处理可能是有利的。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
本公开实施例中一些技术可以参考已公开的文献，包括但不限于：
Draft Report of 3GPP TSG RAN WG1 #AH_1901 v0.1.0,Taibei,Taiwan,21th–25th January 2019
https://www.3gpp.org/ftp/Email_Discussions/RAN1/[RAN1％23AH_1901]/；
3GPP R1-1902259,Samsung；2019-02-15；
https://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_96/Docs/；
3GPP R1-1906545,MediaTek Inc；2019-05-04；
https://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_97/Docs/。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (29)

  1. 一种反馈方法，其特征在于，应用于终端，所述终端维护有待反馈的码本，所述反馈方法包括：
    根据网络设备发送的触发指示，确定待反馈码本的队列，所述触发指示用于指示是否已经成功接收到已反馈码本；
    反馈所述待反馈码本的队列中的待反馈码本。
  2. 根据权利要求1所述的反馈方法，其特征在于，所述根据接收到网络设备发送的触发指示，确定待反馈码本的队列，包括：
    若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则将所述已反馈码本从所述当前待反馈的码本的队列中删除，得到待反馈码本的队列。
  3. 根据权利要求1所述的反馈方法，其特征在于，所述根据接收到网络设备发送的触发指示，确定待反馈码本的队列，包括：
    若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则将当前待反馈码本的队列确定为待反馈码本的队列。
  4. 根据权利要求2或3所述的反馈方法，其特征在于，所述反馈方法还包括：
    根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
  5. 根据权利要求4所述的反馈方法，其特征在于，根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
    若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，且待反馈码本的队列非空，则累加待反馈码本数量得到表征累加待反馈码本数量的DAI参数；
    或
    若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，且所述待反馈码本的队列为空，则重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
  6. 根据权利要求4所述的反馈方法，其特征在于，根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
    若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
  7. 根据权利要求1所述的反馈方法，其特征在于，所述反馈所述待反馈码本的队列 中的待反馈码本，包括：
    将待反馈码本的队列中的所有待反馈码本全部上传。
  8. 一种反馈方法，其特征在于，应用于网络设备，所述网络设备维护有终端待反馈码本的信息，所述反馈方法包括：
    确定是否成功接收终端反馈的码本；
    根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新；
    向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。
  9. 根据权利要求8所述的反馈方法，其特征在于，所述根据是否成功接收到终端反馈的码本对网络设备维护有终端待反馈码本的信息进行更新，包括：
    当成功接收到终端反馈的码本时，将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除。
  10. 根据权利要求9所述的反馈方法，其特征在于，向终端发送用于指示是否成功接收到终端反馈的码本的触发指示，包括：
    向终端发送用于指示成功接收到终端反馈的码本的触发指示。
  11. 根据权利要求8所述的反馈方法，其特征在于，所述根据是否成功接收到终端反馈的码本对网络设备维护有终端待反馈码本的信息进行更新，包括：
    当未成功接收到终端反馈的码本时，在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息。
  12. 根据权利要求11所述的反馈方法，其特征在于，向终端发送用于指示是否成功接收到终端反馈的码本的触发指示，包括：
    向终端发送用于指示未能成功接收到终端反馈的码本的触发指示。
  13. 根据权利要求9或11所述的反馈方法，其特征在于，所述反馈方法还包括：
    根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
  14. 根据权利要求13所述的反馈方法，其特征在于，根据确定是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
    若成功接收到终端反馈的码本，且记录待反馈码本的队列中所包含的待反馈码本非空；则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数；
    或
    若成功接收到终端反馈的码本，且记录待反馈码本的队列中所包含的待反馈码本为空，则重置待反馈码本数量，得到表征重置待反馈码本数量的DAI参数。
  15. 根据权利要求13所述的反馈方法，其特征在于，根据确定是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数，包括：
    若未成功接收到终端反馈的码本，则累加待反馈码本数量，得到表征累加待反馈码本数量的DAI参数。
  16. 一种反馈装置，其特征在于，应用于终端，所述终端维护有待反馈的码本，所述反馈装置包括：
    确定单元，被配置为根据网络设备发送的触发指示，确定待反馈码本的队列，所述触发指示用于指示是否已经成功接收到已反馈码本；
    反馈单元，被配置为反馈所述待反馈码本的队列中的待反馈码本。
  17. 根据权利要求16所述的反馈装置，其特征在于，若所述触发指示用于指示所述网络设备已经成功接收到已反馈码本，则所述确定单元将所述已反馈码本从所述当前待反馈的码本的队列中删除，得到待反馈码本的队列。
  18. 根据权利要求16所述的反馈装置，其特征在于，若所述触发指示用于指示所述网络设备未成功接收到已反馈码本，则所述确定单元将当前待反馈码本的队列确定为待反馈码本的队列。
  19. 根据权利要求17或18所述的反馈装置，其特征在于，所述确定单元还被配置为：
    根据所述触发指示更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
  20. 一种反馈装置，其特征在于，应用于网络设备，所述网络设备维护有终端待反馈码本的信息，所述反馈装置包括：
    接收单元，被配置为确定是否成功接收终端反馈的码本；
    处理单元，被配置为根据是否成功接收到终端反馈的码本，对网络设备维护的终端待反馈码本的信息进行更新；
    发送单元，被配置为向终端发送用于指示是否成功接收到终端反馈的码本的触发指示。
  21. 根据权利要求20所述的反馈装置，其特征在于，当成功接收到终端反馈的码本 时，所述处理单元将该接收到的码本的信息从网络设备维护的终端待反馈码本的信息中删除。
  22. 根据权利要求21所述的反馈装置，其特征在于，所述发送单元向终端发送用于指示成功接收到终端反馈的码本的触发指示。
  23. 根据权利要求20所述的反馈装置，其特征在于，当未成功接收到终端反馈的码本时，所述处理单元在网络设备维护的终端待反馈码本的信息中保留未能成功接收到终端反馈的码本的信息。
  24. 根据权利要求23所述的反馈装置，其特征在于，所述发送单元向终端发送用于指示未能成功接收到终端反馈的码本的触发指示。
  25. 根据权利要求21或23所述的反馈装置，其特征在于，所述处理单元还用于：
    根据是否成功接收终端反馈的码本，更新用于记录待反馈码本的队列中所包含的待反馈码本数量的DAI参数。
  26. 一种反馈装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：执行权利要求1至7中任意一项所述的反馈方法。
  27. 一种反馈装置，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为：执行权利要求8至15中任意一项所述的反馈方法。
  28. 一种非临时性计算机可读存储介质，当所述存储介质中的指令由移动终端的处理器执行时，使得移动终端能够执行权利要求1至7中任意一项所述的反馈方法。
  29. 一种非临时性计算机可读存储介质，当所述存储介质中的指令由网络设备的处理器执行时，使得网络设备能够执行权利要求8至15中任意一项所述的反馈方法。
PCT/CN2019/124123 2019-12-09 2019-12-09 反馈方法、反馈装置及存储介质 WO2021114051A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/124123 WO2021114051A1 (zh) 2019-12-09 2019-12-09 反馈方法、反馈装置及存储介质
CN201980003475.7A CN111149315B (zh) 2019-12-09 2019-12-09 反馈方法、反馈装置及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/124123 WO2021114051A1 (zh) 2019-12-09 2019-12-09 反馈方法、反馈装置及存储介质

Publications (1)

Publication Number Publication Date
WO2021114051A1 true WO2021114051A1 (zh) 2021-06-17

Family

ID=70525113

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/124123 WO2021114051A1 (zh) 2019-12-09 2019-12-09 反馈方法、反馈装置及存储介质

Country Status (2)

Country Link
CN (1) CN111149315B (zh)
WO (1) WO2021114051A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230246748A1 (en) * 2020-07-17 2023-08-03 Beijing Xiaomi Mobile Software Co., Ltd., Communication method, communication device, electronic device and computer storage medium
CN112738845B (zh) * 2020-12-21 2022-09-30 北京邮电大学 Nr-u系统中用于harq反馈的单触发指示设计方法
WO2023035246A1 (zh) * 2021-09-10 2023-03-16 北京小米移动软件有限公司 一种码本反馈方法、码本反馈装置及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107332646A (zh) * 2016-04-29 2017-11-07 中兴通讯股份有限公司 Harq-ack的发送方法及装置
WO2019028844A1 (en) * 2017-08-11 2019-02-14 Lenovo (Beijing) Limited HARQ-ACK FEEDBACK RELEASE FOR DOWNLINK CREAM SET
CN109891791A (zh) * 2019-02-01 2019-06-14 北京小米移动软件有限公司 调度混合自动重传的方法及装置
WO2019216816A2 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses for hybrid automatic repeat request (harq)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107332646A (zh) * 2016-04-29 2017-11-07 中兴通讯股份有限公司 Harq-ack的发送方法及装置
WO2019028844A1 (en) * 2017-08-11 2019-02-14 Lenovo (Beijing) Limited HARQ-ACK FEEDBACK RELEASE FOR DOWNLINK CREAM SET
WO2019216816A2 (en) * 2018-05-10 2019-11-14 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses for hybrid automatic repeat request (harq)
CN109891791A (zh) * 2019-02-01 2019-06-14 北京小米移动软件有限公司 调度混合自动重传的方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "HARQ Enhancements in NR Unlicensed", 3GPP TSG RAN WG1 MEETING #96BIS R1-1903930, 12 April 2019 (2019-04-12), XP051691172 *
HUAWEI ET AL.: "HARQ Enhancements in NR Unlicensed", 3GPP TSG RAN WG1 MEETING #96BIS R1-1905648, 12 April 2019 (2019-04-12), XP051707707 *

Also Published As

Publication number Publication date
CN111149315B (zh) 2022-04-15
CN111149315A (zh) 2020-05-12

Similar Documents

Publication Publication Date Title
WO2021088009A1 (zh) 反馈方法、反馈装置及存储介质
WO2021114051A1 (zh) 反馈方法、反馈装置及存储介质
WO2021088010A1 (zh) 反馈方法、反馈装置及存储介质
CN113079709B (zh) Harq-ack处理方法及装置、通信设备及存储介质
WO2022193149A1 (zh) 波束确定方法、波束确定装置及存储介质
WO2021016772A1 (zh) 竞争窗口的确定方法及装置、通信设备及存储介质
CN110832800B (zh) Harq反馈增强的方法及装置、通信设备及存储介质
WO2021114179A1 (zh) Harq-ack信息传输方法及装置、通信设备
WO2019019171A1 (zh) 一种混合自动重传请求结果的反馈方法及装置
WO2021174494A1 (zh) 增强上行覆盖的处理方法、装置及存储介质
CN110809868B (zh) Harq反馈传输方法及装置、通信设备及存储介质
WO2021092732A1 (zh) Harq-ack传输方法及装置、通信设备
WO2021016888A1 (zh) 物理上行控制信道资源确定方法、装置及存储介质
WO2024092853A1 (zh) 一种上行覆盖增强方法、装置及存储介质
WO2023044857A1 (zh) Harq码本处理方法及装置、通信设备及存储介质
EP4228182A1 (en) Pucch resource determination method and apparatus
WO2021164034A1 (zh) 上行传输的处理方法、装置、通信设备及存储介质
WO2022110028A1 (zh) 上行控制信息传输方法、装置及存储介质
WO2021073394A1 (zh) 一种数据传输方法、装置、电子设备及存储介质
CN113169825B (zh) 数据包传输方法及装置
CN113169826B (zh) Harq-ack信息传输方法及装置、通信设备
US20230147839A1 (en) Data transmission method and apparatus, communication device, and storage medium
WO2021109002A1 (zh) 信息处理方法、装置、基站、用户设备及存储介质
WO2021031009A1 (zh) 预配置资源控制方法、数据传输方法、装置及存储介质
WO2022047751A1 (zh) Harq-ack反馈处理方法、装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19955833

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19955833

Country of ref document: EP

Kind code of ref document: A1