A data transmission method and terminal based on HARQ process

Abstract

The embodiment of the present application provides a data transmission method and terminal based on a HARQ process, which relates to communication technology, and can determine the initial state of a HARQ process, and then use a HARQ process in a non-pending state for uplink transmission. The specific scheme includes: the terminal sets one or more HARQ processes associated with a first pre-configured authorized CG configuration on a first bandwidth BWP to a not pending state; wherein the first CG configuration includes one or more CG configurations configured by a network device for the terminal on the first BWP; the first BWP is the BWP currently activated by the terminal; the terminal uses the HARQ process in a not pending state associated with the first CG configuration to send uplink data to the network device.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method and terminal based on a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process. Background Art

[0002] In the NR-based access to unlicensed spectrum (NR-U) technology based on the new radio (NR), the terminal supports multiple pre-configured grant configurations (CG configurations) on an activated partial bandwidth (BWP). The CG configuration represents the resources required for uplink transmission (i.e., transmission of uplink data) pre-configured by the network device for the terminal, and the multiple CG configurations can share the HARQ process (i.e., HARQ process).

[0003] The terminal starts to send uplink data using a HARQ process associated with a certain CG configuration, and starts the configured grant timer (CGT) and the configured grant retransmission timer (CGRT) only when the uplink data is successfully sent using the Listen Before Talk (LBT) mechanism. Among them, CGT is used to limit the total duration of the process of transmitting an uplink data; CGRT is used to limit the transmission interval between retransmissions in the process of transmitting an uplink data. The process of transmitting an uplink data includes new transmission and retransmission for the same uplink data. New transmission refers to the first transmission of uplink data. Retransmission refers to each transmission of uplink data after the new transmission fails. When the uplink data is successfully sent in the new transmission, both CGT and CGRT start timing. When the timing duration of CGRT is equal to the retransmission duration threshold, or the terminal receives negative acknowledgement (NACK) feedback, if it is determined that CGT is still timing, the terminal automatically retransmits using the HARQ process on the CG configuration. Similarly, when the terminal uses the HARQ process for retransmission on the CG configuration, the CGRT is started only when the uplink data is successfully sent using the LBT mechanism. When the CGT timing duration is equal to the transmission duration threshold, or the terminal receives an acknowledgment (ACK) feedback, the CGT is stopped, and the terminal can use the HARQ process to transmit other uplink data.

[0004] It can be known that in the above technology, if LBT fails when the terminal uses the HARQ process to transmit, resulting in failure of uplink data transmission, CGT and CGRT will not be started, and the uplink data will be stored in the cache (HARQ buffer) of the HARQ process. Since CGT is not running, the terminal may use the HARQ process to transmit the next uplink data, and the next uplink data will flush the uplink data in the HARQ buffer. In this case, the medium access control (MAC) layer does not send the uplink data to the network device, nor will it send the uplink data again. In other words, it can only rely on the higher layer to retransmit the uplink data.

[0005] To address this issue, the NR-U system introduces a suspended pending state for the HARQ process. For new transmissions and retransmissions, when uplink data is successfully sent using a HARQ process, the terminal determines that the HARQ process is in a non-suspended not pending state; otherwise, the HARQ process is determined to be in a pending state. Furthermore, after the HARQ process is in the pending state, the pending state of the HARQ process is canceled only when the uplink data is successfully sent or the cache of the HARQ process is cleared. In this way, in order to avoid the uplink data being discarded, the terminal not only determines that the CGRT and CGT stop timing, but also determines that the HARQ process is in a not pending state before using the HARQ process to transmit the next uplink data.

[0006] However, when the HARQ process is initially used, the terminal is not clear about the state of the HARQ process and cannot use the HARQ for new transmission. In other words, the HARQ process lacks an initial state (ie, a non-suspended state), which makes it impossible to use the HARQ process for new transmission. Summary of the invention

[0007] The embodiments of the present application provide a data transmission method and terminal based on a HARQ process, which can determine the initial state of the HARQ process and then use the HARQ process in a non-pending state for new transmission.

[0008] In the first aspect, an embodiment of the present application provides a data transmission method based on a HARQ process. Among them, the terminal can set one or more HARQ processes associated with the first CG configuration on the first part of the bandwidth BWP to a not pending state. Among them, the first CG configuration may include one or more CG configurations configured by the network device for the terminal on the first BWP. The first BWP is the BWP currently activated by the terminal. Then, the terminal can use the HARQ process associated with the first CG configuration and in the not pending state to send uplink data to the network device.

[0009] Through this solution, for the first CG configuration configured by the network device for the terminal on the first BWP, the terminal can set one or more HARQ processes associated with the first CG configuration to the not pending state. In this way, the setting of the initial state (i.e., not pending state) of the one or more HARQ processes is implemented. Among them, the one or more HARQ processes are in the not pending state, indicating that the one or more HARQ processes are available for new transmission. Therefore, the terminal can use one of the one or more HARQ processes for new transmission. In this way, the terminal can use the HARQ process whose initial state is the not pending state for new transmission.

[0010] Specifically, when receiving the first signaling related to the CG configuration, the terminal can set one or more HARQ processes associated with the first CG configuration to a not pending state. The CG configuration indicated by the first signaling is the first CG configuration; the first signaling may include a radio resource control (RRC) signaling and a downlink control information (DCI) activation command. The RRC signaling is used to configure and activate the CG configuration for the terminal. The RRC signaling can also be used to configure only the CG configuration for the terminal. The DCI activation command is used to activate (first activation or reactivation) the CG configuration that has been configured for the terminal.

[0011] Accordingly, the first CG configuration may include all CG configurations configured by the network device for the terminal using RRC signaling, and all CG configurations configured may include activated CG configurations and unactivated CG configurations. The first CG configuration may also include a CG configuration configured and activated by the network device for the terminal using RRC. The first CG configuration may also include a CG configuration activated (first activation or reactivation) by the network device for the terminal using a DCI activation command.

[0012] That is to say, in an embodiment of the present application, after receiving the above-mentioned first signaling from the network device, the terminal can determine the above-mentioned first CG configuration according to the first signaling; and then set one or more HARQ processes associated with the above-mentioned first CG configuration.

[0013] In a possible design of the first aspect, the terminal may receive a DCI activation command from a network device, and the DCI activation command is used to instruct the terminal to activate (activate for the first time or reactivate) a CG configuration, and the activated (activated for the first time or reactivated) CG configuration is the first CG configuration. In response to receiving the DCI activation command, the terminal may set the one or more HARQ processes mentioned above to a not pending state. Specifically, the terminal sets one or more HARQ processes associated with the first CG configuration on the first BWP to a not pending state, including: in response to receiving the DCI activation command from the network device, the terminal sets one or more HARQ processes associated with the first CG configuration to a not pending state.

[0014] It can be understood that the terminal will activate the first CG configuration in response to the DCI activation command, and the activated first CG configuration can be used directly. The uplink data is sent through the available first CG configuration, specifically, the uplink data is sent using a HARQ process associated with the first CG configuration. In order for the terminal to determine the initial state of the HARQ process associated with the currently available first CG configuration, in response to the DCI activation command, the terminal can also set one or more HARQ processes associated with the first CG configuration indicated to be activated by the DCI activation command to a not pending state.

[0015] In another possible design of the first aspect, the terminal may receive RRC signaling from a network device. The RRC signaling may be used to configure and activate the first CG configuration for the terminal, or may be used to configure only the first CG configuration for the terminal (i.e., only configure but do not activate the first CG configuration). In response to receiving the RRC signaling, the terminal may set the one or more HARQ processes mentioned above to a not pending state. Specifically, the terminal sets one or more HARQ processes associated with the first CG configuration on the first BWP to a not pending state, including: in response to receiving RRC signaling from the network device, the terminal may set one or more HARQ processes associated with the first CG configuration to a not pending state.

[0016] It can be understood that the terminal configures and activates the first CG configuration on the currently activated first BWP in response to different RRC signaling, or only configures the first CG configuration. Whether it is a configured and activated first CG configuration or only a configured first CG configuration, it may be used to send uplink data. Sending uplink data through the available first CG configuration specifically means sending uplink data using a HARQ process associated with the first CG configuration. In order for the terminal to determine the initial posture of the HARQ process associated with the currently available first CG configuration, in response to the RRC signaling, the terminal can also set one or more HARQ processes associated with the available first CG configuration to a not pending state.

[0017] In another possible design of the first aspect, the one or more HARQ processes associated with the first CG configuration may include all HARQ processes associated with the first CG configuration. That is, the terminal may set all HARQ processes associated with the first CG configuration to a not pending state.

[0018] In another possible design of the first aspect, the one or more HARQ processes associated with the above-mentioned first CG configuration may include a partial HARQ process associated with the first CG configuration.

[0019] Specifically, the one or more HARQ processes associated with the first CG configuration may include: a HARQ process in a pending state among the HARQ processes associated with the first CG configuration; or, the first HARQ process among the HARQ processes associated with the first CG configuration; or, a HARQ process that is not in use among the HARQ processes associated with the first CG configuration; or, a corresponding HARQ process (i.e., the corresponding HARQ process) among the HARQ processes associated with the first CG configuration.

[0020] Among them, there is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity; there is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity, indicating that the first HARQ process has not been used by the terminal. The above corresponding HARQ process is a HARQ process randomly selected by the terminal.

[0021] In another possible design of the first aspect, if the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, the terminal may clear the cache of all HARQ processes associated with the second CG configuration on the first BWP, or may set all HARQ processes associated with the second CG configuration on the first BWP to a not pending state.

[0022] Wherein, N≥2, N is a positive integer. The second CG configuration includes all CG configurations configured by the network device for the terminal on the first BWP, or the CG configuration activated by the terminal on the first BWP. The second CG configuration may be the same as the first CG configuration, or may be different from the first CG configuration. After the cache of all HARQ processes associated with the second CG configuration is cleared, all HARQ processes associated with the second CG configuration are in the not pending state.

[0023] It is understandable that after the terminal determines that the first BWP has N consecutive uplink LBT failures, it can switch from the first BWP to other BWPs. Any one or more HARQ processes associated with the second CG configuration on the first BWP (i.e., all CG configurations configured by the network device for the terminal on the first BWP or the CG configuration activated for the terminal on the first BWP) may be in a pending state due to a failure to send uplink data. In addition, the CG configuration on other BWPs after switching may also be associated with any one or more HARQ processes that are in a pending state due to a failure to send uplink data.

[0024] In order to avoid that any one or more HARQ processes are still in the pending state, resulting in the inability to use any one or more HARQ processes for new transmission on the CG configuration on other BWPs after switching; in the present application, after determining that the first BWP has experienced N consecutive uplink LBT failures, the terminal can set any one or more HARQ processes associated with the second CG configuration on the first BWP to the not pending state, so that any one or more HARQ processes can be reused for new transmission on other BWPs after switching.

[0025] In this design, after receiving the instruction sent by the network device to instruct the activation of the above-mentioned first BWP, the terminal starts to count the total number of uplink LBT failures that occur on the first BWP. The total number of uplink LBT failures that occur on the first BWP may include the number of uplink LBT failures that occur in all uplink transmissions on the first BWP (i.e., the process of transmitting all uplink data). If the total number is equal to N, the terminal determines that the first BWP has N consecutive uplink LBT failures, triggers a continuous uplink LBT failure state, and clears the cache of the HARQ process associated with the second CG configuration on the first BWP, or sets the HARQ process associated with the second CG configuration on the first BWP to a not pending state.

[0026] In another possible design of the first aspect, the terminal determines that N consecutive uplink LBT failures occur on the first BWP, triggering a continuous uplink LBT failure state. When the terminal sends a medium access control control element (MAC CE) to the network device, it clears the cache of the HARQ process associated with the second CG configuration on the first BWP, or sets the HARQ process associated with the second CG configuration on the first BWP to a not pending state. Among them, the MAC CE includes an LBT failure status indication bit of the service cell where the terminal is located. This design method provides a possible opportunity for the terminal to execute "clear the cache of all HARQ processes associated with the second CG configuration, or set all HARQ processes associated with the second CG configuration to a not pending state".

[0027] In another possible design of the first aspect, when the terminal is located in the primary cell or the primary and secondary cells and actively switches from the first BWP to the second BWP, the cache of all HARQ processes associated with the second CG configuration can be cleared, or all HARQ processes associated with the second CG configuration can be set to a not pending state. The second BWP is a BWP that is configured with physical random access channel (PRACH) resources and has not experienced N consecutive uplink LBT failures, and the second BWP and the first BWP belong to the same service cell. The phrase "no N consecutive uplink LBT failures" can mean "no N consecutive uplink LBT failures have occurred as of the current moment." This design provides a possible opportunity for the terminal to execute "clear the cache of all HARQ processes associated with the second CG configuration, or set all HARQ processes associated with the second CG configuration to a not pending state."

[0028] In another possible design of the first aspect, the terminal may receive a BWP switching instruction from a network device; in response to the BWP switching instruction, the terminal may clear the cache of all HARQ processes associated with the second CG configuration, or set all HARQ processes associated with the second CG configuration to a not pending state. This design provides a possible opportunity for the terminal to execute "clear the cache of all HARQ processes associated with the second CG configuration, or set all HARQ processes associated with the second CG configuration to a not pending state".

[0029] In another possible design of the first aspect, each time the terminal determines whether the HARQ process for sending uplink data is newly transmitted or retransmitted, it determines whether the HARQ process for sending uplink data is in a pending state. If the HARQ process for sending uplink data is in a pending state, the number of pending times recorded by the pending counter is increased by 1; the initial value of the number of pending times recorded by the pending counter is zero. If the number of pending times recorded by the pending counter is equal to a preset number threshold, the terminal clears the cache of the HARQ process for sending uplink data, or sets the HARQ process for sending uplink data to a not pending state. Among them, after the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0030] In this design, the terminal can determine whether the HARQ process used to send the uplink data is in the pending state or the not pending state each time it determines that the HARQ process used to send the uplink data is newly transmitted or retransmitted. If it is in the pending state, the pending number recorded in the suspension counter is increased by 1; if it is in the not pending state, the pending number recorded in the suspension counter is not increased by 1.

[0031] It can be understood that the number of pending times recorded by the suspension counter represents the total number of times the HARQ process used to send uplink data becomes pending during the process of transmitting uplink data. If the total number is equal to the preset number threshold, the HARQ process used to send uplink data is set to not pending state (i.e., the cache of the HARQ process used to send uplink data is cleared or the HARQ process used to send uplink data is set to not pending state). In other words, the HARQ process used to send uplink data can be used to transmit other uplink data. In this way, the problem that the HARQ process used to send uplink data is in pending state for a long time, i.e., occupied for a long time, when the HARQ process used to send uplink data fails to send uplink data multiple times is solved.

[0032] In another possible design of the first aspect, each time the terminal determines that the HARQ process for sending uplink data is newly transmitted or retransmitted, it determines whether the HARQ process for sending uplink data is in a pending state or a not pending state. It is determined that the HARQ process for sending uplink data is in a pending state and the pending timer is not started, and the pending timer is started. It is determined that the HARQ process for sending the uplink data is in a not pending state and the pending timer is in operation, and the pending timer is stopped. If the timing duration of the pending timer is equal to a preset duration threshold, the terminal clears the cache of the HARQ process for sending uplink data, or sets the HARQ process for sending uplink data to a not pending state. The pending timer is used to count the total duration that the HARQ process for sending uplink data is in a pending state during the transmission of uplink data. After the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0033] In this design, the terminal can determine whether the HARQ process used to send the uplink data is in the pending state or the not pending state each time the HARQ process used to send the uplink data is newly transmitted or retransmitted. If it is in the pending state, the suspension timer is started if the suspension timer has not been started, or the suspension timer in operation continues to run. If it is in the not pending state, the suspension timer is not started if the suspension timer has not been started, and the suspension timer is stopped if the suspension timer is in operation.

[0034] It can be understood that since the suspension timer is used to count the total time that the HARQ process for sending uplink data is in the pending state during the process of transmitting uplink data. Then, the timing duration obtained by the terminal through the suspension timer is the total time that the HARQ process for sending uplink data is in the pending state during the process of transmitting uplink data. If the total duration is equal to the preset duration threshold, the HARQ process for sending uplink data is set to the not pending state (i.e., the cache of the HARQ process for sending uplink data is cleared and the HARQ process for sending uplink data is set to the not pending state). In other words, the HARQ process for sending uplink data can be used to transmit other uplink data. In this way, the problem that the HARQ process for sending uplink data is in the pending state for a long time, i.e., it is occupied for a long time, when the HARQ process for sending uplink data fails to send uplink data for multiple consecutive times is solved.

[0035] In a second aspect, an embodiment of the present application provides a terminal, which includes: a state setting unit and a data sending unit. The state setting unit is used to set one or more HARQ processes associated with the first CG configuration on the first BWP to a not pending state; wherein the first CG configuration includes one or more CG configurations configured by the network device for the terminal on the first BWP; the first BWP is the BWP currently activated by the terminal. The data sending unit is used to send uplink data to the network device using the HARQ process associated with the first CG configuration and in the not pending state.

[0036] In a possible design of the second aspect, the state setting unit is specifically used to set one or more HARQ processes associated with the first CG configuration to a notpending state in response to receiving a DCI activation command from a network device. The DCI activation command is used to instruct the terminal to activate the first CG configuration.

[0037] In another possible design of the second aspect, the state setting unit is specifically used to set one or more HARQ processes associated with the first CG configuration to a not pending state in response to receiving an RRC signaling from a network device. The RRC signaling is used to configure and activate the first CG configuration for the terminal, or to configure only the first CG configuration for the terminal.

[0038] In another possible design of the second aspect, the one or more HARQ processes associated with the first CG configuration include: all HARQ processes associated with the first CG configuration; or, a HARQ process in a pending state among the HARQ processes associated with the first CG configuration; or, a first HARQ process among the HARQ processes associated with the first CG configuration; or, a HARQ process that is not in use among the HARQ processes associated with the first CG configuration; or, a corresponding HARQ process among the HARQ processes associated with the first CG configuration. Among them, there is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity; there is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity, indicating that the first HARQ process has not been used by the terminal. The corresponding HARQ process is a HARQ process randomly selected by the terminal.

[0039] In another possible design of the second aspect, the state setting unit is also used to clear the cache of all HARQ processes associated with the second CG configuration on the first BWP, or set all HARQ processes associated with the second CG configuration on the first BWP to a not pending state if it is determined that N consecutive uplink LBT failures have occurred on the first BWP. Wherein N≥2, and N is a positive integer. The second CG configuration includes all CG configurations configured by the network device for the terminal on the first BWP, or the CG configuration activated for the terminal on the first BWP. After the cache of all HARQ processes associated with the second CG configuration is cleared, all HARQ processes associated with the second CG configuration are in a not pending state.

[0040] In another possible design of the second aspect, the state setting unit is specifically used to clear the cache of all HARQ processes associated with the second CG configuration on the first BWP, or set all HARQ processes associated with the second CG configuration on the first BWP to a not pending state when sending a MAC CE to the network device. The MAC CE includes an LBT failure status indication bit of the service cell where the terminal is located.

[0041] In another possible design of the second aspect, the state setting unit is specifically used to clear the cache of all HARQ processes associated with the second CG configuration, or set all HARQ processes associated with the second CG configuration to the not pending state when the terminal is located in the primary cell or the primary and secondary cells and actively switches from the first BWP to the second BWP. The second BWP is a BWP that is configured with PRACH resources and has not experienced N consecutive uplink LBT failures, and the second BWP and the first BWP belong to the same service cell.

[0042] In another possible design of the second aspect, the terminal further includes: a communication unit. The communication unit is used to receive a BWP switching instruction from a network device. A state setting unit is specifically used to clear the cache of all HARQ processes associated with the second CG configuration in response to the BWP switching instruction, or set all HARQ processes associated with the second CG configuration to a not pending state.

[0043] In another possible design of the second aspect, the terminal also includes: a number statistics unit. The number statistics unit is used to determine each time that the HARQ process for sending uplink data is newly transmitted or retransmitted, and to determine whether the HARQ process for sending uplink data is in a pending state; if the HARQ process for sending uplink data is in a pending state, the number of pending times recorded by the suspension counter is increased by 1. The initial value of the number of pending times recorded by the suspension counter is zero. The state setting unit is also used to clear the cache of the HARQ process for sending uplink data, or set the HARQ process for sending uplink data to a not pending state if the number of pending times recorded by the suspension counter is equal to a preset number threshold. Among them, after the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0044] In another possible design of the second aspect, the terminal further includes: a duration statistics unit. The duration statistics unit is used to determine whether the HARQ process for sending uplink data is in a pending state or a not pending state each time the HARQ process for sending uplink data is newly transmitted or retransmitted; determine that the HARQ process for sending uplink data is in a pending state and the suspension timer is not started, and start the suspension timer; determine that the HARQ process for sending uplink data is in a not pending state and the suspension timer is running, and stop the suspension timer. The state setting unit is also used to clear the cache of the HARQ process for sending uplink data, or set the HARQ process for sending uplink data to a not pending state if the timing duration of the suspension timer is equal to a preset duration threshold. The suspension timer is used to count the total duration of the HARQ process for sending uplink data in the pending state during the transmission of uplink data. After the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0045] In a third aspect, an embodiment of the present application provides a terminal, comprising: a processor, a memory, and a communication interface; the memory and the communication interface are coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, and the memory includes a non-volatile storage medium. When the processor executes the computer instructions, the terminal executes the method described in the first aspect and any possible design method thereof.

[0046] In a fourth aspect, an embodiment of the present application provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on a terminal, the terminal executes the method described in the first aspect and any possible design thereof.

[0047] In a fifth aspect, an embodiment of the present application provides a computer program product, which, when executed on a terminal, enables the terminal to execute the method described in the first aspect and any possible design thereof.

[0048] The technical effects brought about by the second aspect of the embodiment of the present application and any possible design thereof, as well as the third, fourth and fifth aspects can refer to the technical effects brought about by the different design methods in the above-mentioned first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A simplified schematic diagram of a system architecture provided in an embodiment of the present application;

[0050] Figure 2 A schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0051] Figure 3 A schematic diagram of the principle of a method for a terminal to send uplink data to a network device provided in an embodiment of the present application;

[0052] Figure 4 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 1 ;

[0053] Figure 5 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 2 ;

[0054] Figure 6 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 3 ;

[0055] Figure 7 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 4 ;

[0056] Figure 8 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 5 ;

[0057] Fig. 9 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 6 ;

[0058] Fig.10 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 7 ;

[0059] Fig.11 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 8 ;

[0060] Fig.12 A process of a data transmission method based on a HARQ process provided in an embodiment of the present application Figure 9 ;

[0061] Fig.13 A schematic diagram of the structure of a terminal provided in an embodiment of the present application Figure 1 ;

[0062] Fig.14 A schematic diagram of the structure of a terminal provided in an embodiment of the present application Figure 2 . DETAILED DESCRIPTION

[0063] The terms "first" and "second" in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects. For example, the first BWP and the second BWP are different BWPs.

[0064] A data transmission method based on a HARQ process provided in an embodiment of the present application can be applied to a process in which a terminal transmits uplink data to a network device.

[0065] Figure 1 This is a schematic diagram of the architecture of a mobile communication system provided in an embodiment of the present application. Figure 1 As shown, the mobile communication system may include: a core network device 110, a wireless access network device 120 and at least one terminal (including a terminal 130 and a terminal 140). Among them, at least one terminal is connected to the wireless access network device 120 by wireless means, and the wireless access network device 120 is connected to the core network device 110 by wireless or wired means. The core network device 110 and the wireless access network device 120 may be independent and different physical devices, or the functions of the core network device 110 and the logical functions of the wireless access network device 120 may be integrated on the same physical device, or a physical device may integrate part of the functions of the core network device 110 and part of the functions of the wireless access network device 120. The terminal 130 or the terminal 140 may be fixed or movable. In the embodiment of the present application, at least one may be 1, 2, 3 or more, and the embodiment of the present application is not limited.

[0066] It should be noted that Figure 1 This is just a schematic diagram. The mobile communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices. Figure 1 The embodiment of the present application does not limit the number of core network devices 110, wireless access network devices 120 and terminals included in the mobile communication system.

[0067] The wireless access network device 120 is an access device for the terminal to access the mobile communication system wirelessly, and may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. The wireless access network device 120 may also be a module or unit that performs some functions of a base station. For example, it may be a centralized unit (CU) or a distributed unit (DU). The embodiment of the present application does not limit the specific technology and specific device form adopted by the wireless access network device 120. In the embodiment of the present application, the wireless access network device 120 is referred to as a network device. If there is no special explanation, the network device refers to the wireless access network device 120.

[0068] In the embodiment of the present application, the device for implementing the function of the wireless access network device 120 may be a network device; or it may be a device capable of supporting the wireless access network device 120 to implement the function, such as a chip system, which may be installed in the wireless access network device 120 or used in conjunction with the wireless access network device 120. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the case where the device for implementing the function of the wireless access network device 120 is a network device as an example.

[0069] The terminals involved in the embodiments of the present application may also be referred to as terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. The terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal, an augmented reality terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote surgery, a wireless terminal in smart grids, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal. As an embodiment, such as Figure 1 As shown, the terminal 130 and the terminal 140 included in the system architecture of the present application are both shown using a mobile phone as an example.

[0070] In the embodiment of the present application, the device for realizing the function of the terminal may be a terminal; or it may be a device capable of supporting the terminal to realize the function, such as a chip system, which may be installed in the terminal or used in combination with the terminal. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for realizing the function of the terminal as an example.

[0071] The network device and terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can be deployed on the water surface; or can be deployed on an airplane, balloon or artificial satellite in the air. The embodiments of the present application do not limit the application scenarios of the network device and terminal.

[0072] In a mobile communication system, a terminal can access a network device and communicate wirelessly with the network device. For example, a network device can manage one or more (for example, 3 or 6, etc.) cells, and a terminal can access the network device in at least one of the one or more cells and communicate with the network device in the cell where the terminal is located.

[0073] Among them, the basis of wireless communication is spectrum resources. Spectrum resources are divided into authorized spectrum and unlicensed spectrum. Among them, the authorized spectrum can only be used by a specific operator in a certain place, while the unlicensed spectrum can be used by any operator and is a shared spectrum resource. The network device and the terminal can communicate through the authorized spectrum, can communicate through the unlicensed spectrum, or can communicate through the authorized spectrum and the unlicensed spectrum. For example, the network device and the terminal can communicate through the spectrum below 6 gigahertz (GHz), can communicate through the spectrum above 6 GHz, or can use the spectrum below 6 GHz and the spectrum above 6 GHz. The embodiments of the present application are mainly aimed at the situation where the terminal uses the unlicensed spectrum to communicate with the network device.

[0074] For example, the present application embodiment takes the interaction between the wireless access network device (network device) 120 and the terminal 130 as an example. Figure 1 The wireless access network device 120 and the terminal 130 in the system architecture are introduced.

[0075] The wireless access network device 120 activates the first BWP for the terminal 130, and configures at least one CG configuration and a HARQ process associated with the at least one CG configuration on the first BWP for the terminal 130. Then, the terminal 130 can use the HARQ process associated with an activated CG configuration on the first BWP to send uplink data to the wireless access network device 120. If the uplink data fails to be sent, the terminal 130 continues to use the HARQ process to send the uplink data; if the uplink data is successfully sent, wait for feedback from the wireless access network device 120. If ACK feedback is received from the wireless access network device 120, the terminal 130 determines that the uplink data is successfully transmitted to the wireless access network device 120; if NACK feedback is received from the wireless access network device 120, the terminal 130 determines that the uplink data is failed to be transmitted to the wireless access network device 120, and can continue to use the HARQ process to send the uplink data.

[0076] Figure 2 The hardware structure diagram of a terminal provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the terminal may include at least one processor 21 , a memory 22 , a communication interface 23 and a bus 24 .

[0077] Combine the following Figure 2 The following is a detailed introduction to the various components of the terminal:

[0078] The processor 21 may be a processor or a collective term for multiple processing elements. For example, the processor 21 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application, such as one or more microprocessors (Digital Signal Processor, DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, FPGA).

[0079] The processor 21 can execute various functions of the terminal by running or executing software programs stored in the memory 22 and calling data stored in the memory 22.

[0080] In a specific implementation, as an embodiment, the processor 21 may include one or more CPUs. Figure 2 As shown, the processor 21 includes CPU0 and CPU1.

[0081] In a specific implementation, as an embodiment, the terminal may include multiple processors. Figure 2 As shown, it includes processor 21 and processor 25. Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor here can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0082] The memory 22 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 22 may exist independently and be connected to the processor 21 via a bus 24. The memory 22 may also be integrated with the processor 21. Among them, the memory 22 is used to store the software program that executes the solution of the present application, and the execution is controlled by the processor 21.

[0083] The communication interface 23 is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc. The communication interface 23 may include a receiving unit to implement a receiving function, and a sending unit to implement a sending function.

[0084] The bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 2 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0085] Figure 2The device structure shown in the figure does not constitute a limitation on the terminal, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. Although not shown, the terminal may also include a battery, a camera, a Bluetooth module, a global positioning system (GPS) module, a display screen, etc., which will not be repeated here.

[0086] The following is an introduction to the terms involved in the embodiments of the present application:

[0087] (1) LBT channel contention access technology: refers to monitoring the channel occupancy of the unlicensed spectrum before data transmission. The channel can be used only when the channel is idle. Since the unlicensed spectrum is a shared spectrum, many air interface technologies use the unlicensed spectrum, such as WiFi, License Assisted Access (LAA) based on Long Term Evolution (LTE), and MulteFire technology. In order to ensure the coexistence of multiple air interface technologies on the unlicensed spectrum, the LBT mechanism is used to avoid mutual interference between multiple air interface technologies.

[0088] Among them, LBT failure means that the channel cannot be successfully occupied due to the busy channel, and the signal (for example, data, command) cannot be transmitted. LBT success means that the channel is successfully occupied and data is transmitted. According to different signal transmission directions, the transmission signal is divided into uplink transmission and downlink transmission. Among them, uplink transmission refers to the transmission of signals from the terminal to the network device through the channel; the channel used for uplink transmission is called an uplink channel; the signal of uplink transmission is called an uplink signal (for example, uplink data, uplink command). Downlink transmission refers to the transmission of signals from the network device to the terminal through the channel; the channel used for downlink transmission is called a downlink channel; the signal of downlink transmission is called a downlink signal (for example, downlink data, downlink command). Accordingly, LBT is divided into uplink LBT and downlink LBT, the uplink LBT refers to the terminal monitoring the channel occupancy of the unlicensed spectrum before the uplink transmission, and the downlink LBT refers to the network device monitoring the channel occupancy of the unlicensed spectrum before the downlink transmission.

[0089] The channel access process using LBT is divided into two categories: the first category is energy detection based on a fixed duration, where the transmitter (terminal or network device) detects the signal strength of the channel of the unlicensed spectrum; if the signal strength is greater than the preset threshold, the channel is considered busy, otherwise the channel is considered idle. The second category is energy detection based on a backoff mechanism, where the transmitter (terminal or network device) randomly selects a value A from a range of values ​​(for example, a window [min, max], where min is a minimum value and max is a maximum value). If at least A idle energy detection time slots are detected on the channel of the unlicensed spectrum, the channel is considered idle, otherwise the channel is considered busy. Among them, each idle energy detection time slot is a time slot when the signal strength of the channel is not greater than the preset threshold. The transmitter (terminal or network device) can use the channel to transmit data only when it believes that the channel is idle.

[0090] An LBT counter (LBT counter) and an LBT timer (LBT timer) are introduced in the NR-U technology. The LBT counter is used to record the number of uplink LBT failures (i.e., the uplink channel cannot be successfully occupied due to busy uplink channels). The LBT timer is used to time the duration of detecting continuous uplink LBT failures. Each time an uplink LBT failure occurs, the LBT counter is incremented by 1, and the LBT timer is started or restarted. When the number of uplink LBT failures recorded by the LBT counter is equal to the preset failure number threshold, it is considered that continuous uplink LBT failures have occurred. If the timing duration of the LBT timer is equal to the preset failure duration threshold, the LBT counter is reset.

[0091] (2) BWP: With the development of communication technology, the available spectrum bandwidth is getting wider and wider, especially the spectrum bandwidth used by NR is very wide. In order to use the spectrum more flexibly, NR introduces BWP technology, that is, configuring a portion of the available spectrum bandwidth BWP for the terminal. Among them, the network device can activate a suitable BWP for the terminal according to its own load and the service needs of the terminal. For example, the network speed device determines that the terminal processes a large amount of data services and activates a wider BWP for the terminal. The network device finds that the load of the BWP currently activated by the terminal is heavy, and activates another relatively idle BWP for the terminal.

[0092] Specifically, the existing NR protocol stipulates that after the terminal accesses the service cell of the network device (for example, the primary cell, the secondary cell, the primary and secondary cell), the network device configures a dedicated BWP for the terminal according to its own load and the service needs of the terminal, and configures up to 4 dedicated BWPs. Then select and activate one of the configured BWPs. In addition, the network device can only activate one BWP for any terminal in a service cell where the terminal is located.

[0093] When N consecutive uplink LBT failures (or called continuous uplink LBT failures) occur on the currently activated BWP of the service cell where the terminal is located, the terminal triggers a MAC CE (i.e., LBT failure MAC CE) to report to the network device. The MAC CE is in the form of a bitmap, which is used to indicate whether N consecutive uplink LBT failures occur in the corresponding service cell. If the terminal successfully sends the MACCE, the terminal cancels the N consecutive uplink LBT failure status of the corresponding service cell. In addition, the terminal can also cancel the N consecutive uplink LBT failure status of the corresponding service cell at other times. For example, the network device sends a BWP switching instruction to the terminal, instructing the service cell where the terminal is located to switch from the currently activated BWP to other BWPs; or when the service cell where the terminal is located is deactivated, the service cell is no longer used. The embodiment of the present application does not limit the timing of canceling the N consecutive uplink LBT failure status of the corresponding service cell.

[0094] It should be noted that, when the serving cell where the terminal is located is a secondary cell, since the terminal cannot actively switch BWP in the secondary cell, the terminal needs to send the MAC CE through other serving cells that have not experienced N consecutive uplink LBT failures. In addition, the MAC CE in the embodiment of the present application is an LBT failure MAC CE.

[0095] When the service cell where the terminal is located is a primary cell (PCell) or a primary secondary cell (PScell), if N consecutive uplink LBT failures are detected on the currently activated BWP of the service cell, the terminal can actively switch from the currently activated BWP to the second BWP. The second BWP is a BWP that is configured with PRACH resources on the service cell and has not experienced N consecutive uplink LBT failures. Then, the terminal initiates a RACH random access process to complete LBT failure recovery (that is, the terminal uses the switched BWP to send and receive data with the network device). The RACH random access process includes: interacting with the network device to inform the network device of the terminal and its switched BWP. The switched BWP is used to send and receive data between the network device and the terminal.

[0096] (3) HARQ process: refers to the data transmission process using HARQ technology. The HARQ technology combines the forward error correction (EFC) technology with the automatic repeat request (ARQ) technology. Among them, the EFC technology can increase the credibility of communication. However, in a unidirectional communication channel (such as the FDD system of LTE), when the receiving end receives a data packet (for example, uplink data) sent by the sending end, if the receiving end detects an error that cannot be corrected, the receiving end cannot request the sending end to retransmit the data packet. In the HARQ technology, the receiving end can request the sending end to retransmit the data packet through the ARQ mechanism. Specifically, the receiving end can detect whether the received data packet is erroneous through the cyclic redundancy check (CRC); if the data packet is not erroneous, the receiving end returns ACK feedback of the data packet to the sending end; if the data packet is erroneous, the receiving end sends NACK feedback of the data packet to the sending end; after receiving the NACK feedback of the data packet, the receiving end retransmits the data packet to the receiving end.

[0097] Taking the transmission of uplink data as an example, the network device (i.e., the receiving end) receives the terminal (i.e., the transmitting end) using the HARQ process to send uplink data on the resources indicated by the uplink grant (UL grant). If the network device correctly receives the uplink data, the state of the HARQ feedback performed by the network device on the downlink is ACK (i.e., the network device feeds back the ACK feedback of the uplink data to the terminal). If the network device does not correctly receive the uplink data, the state of the HARQ feedback performed by the network device on the downlink is NACK (i.e., the network device feeds back the NACK feedback of the uplink data to the terminal). In other words, HARQ feedback of ACK is used to indicate that the network device correctly receives the uplink data; HARQ feedback of NACK is used to indicate that the network device does not correctly receive the uplink data. Then, if the terminal receives the NACK fed back by the network device, it retransmits the uplink data to the network device, so that the network device can perform HARQ merger of the retransmitted uplink data and the uplink data that was not correctly received.

[0098] Typically, a terminal can use a HARQ process to perform uplink transmission on the resources indicated by a UL grant. For example, the uplink grant associated with the HARQ process is delivered to the HARQ entity of the terminal so that uplink data is sent on the resources indicated by the uplink grant associated with the HARQ process. The uplink grant can be a dynamic grant (dynamic grant, DG) dynamically scheduled by the network terminal, or it can be a pre-configured grant CG of the network terminal. A HARQ entity of the terminal can maintain multiple parallel HARQ processes, each of which has a HARQ identity number (identity, ID), and different HARQ processes can be distinguished by the HARQID.

[0099] (4) CG configuration: refers to the resources required for uplink transmission pre-configured by the network equipment in NR-U for the terminal. Among them, the resources required for pre-configured uplink transmission can be called CG configuration, or pre-configured uplink authorization configuration. The terminal can perform uplink transmission on the CG configuration without dynamic scheduling of the network equipment. CG configuration includes but is not limited to the two pre-configured authorization resources adopted by the fifth-generation mobile communication technology (5th-Generation, 5G). The two pre-configured authorization resources adopted by 5G are obtained through two authorization methods, which include configured authorization method 1 (configured granttype1) and configured authorization method 2 (configured grant type2).

[0100] Among them, configuration authorization mode 1 means that the network device pre-configures the resources required for uplink transmission (CG configuration) for the terminal through a semi-static configuration method, that is, the CG configuration activated by periodic configuration, and the terminal does not need to obtain the uplink authorization of the CG configuration from the network device every time before sending uplink data. For example, the network device can configure the CG configuration for uplink transmission for the terminal through RRC signaling, and the RRC signaling can also include the period of the CG configuration.

[0101] Configuration authorization mode 2 means that the network device can configure some information for uplink transmission for the terminal through RRC signaling, such as the period of CG configuration for uplink transmission. Then, the network device activates the CG configuration through physical layer signaling carrying the CG configuration for uplink transmission, so that the terminal can perform uplink transmission under the CG configuration. The physical layer signaling includes DCI.

[0102] It should be noted that the naming of the above two authorization methods is not limited to configuration authorization method 1 and configuration authorization method 2, and there may be other names. The embodiments of this application do not limit the naming of these two authorization methods. In addition to the 5G communication system, the communication system to which the above two authorization methods are applicable may also be an LTE communication system or other communication systems. The embodiments of this application do not limit the communication system to which these two authorization methods are applicable.

[0103] The NR-U system supports multiple CG configurations, that is, the terminal can support multiple CG configurations on the currently activated BWP at the same time, and multiple different CG configurations can share the HARQ process. When the terminal transmits uplink data through any CG configuration, it randomly selects a HARQ process from the (supported) HARQ process associated with the CG configuration. Then, the terminal uses this HARQ process on the CG configuration to send uplink data. If the uplink LBT is successful, it means that the uplink data is sent successfully. Otherwise, the uplink data fails to be sent and the uplink data is resent. Among them, the process of transmitting an uplink data includes new transmission and retransmission for the same uplink data. The first transmission of uplink data in the process of transmitting an uplink data is called a new transmission, and the new transmission can also be called an initial transmission. After the new transmission is successfully sent, if the network device does not correctly receive the uplink data, it means that the new transmission has failed. The terminal can retransmit the uplink data until the transmission is successful or the maximum transmission duration is reached. Among them, each transmission of uplink data after the new transmission fails in the process of transmitting an uplink data is called a retransmission.

[0104] In addition, the NR-U system also supports retransmission across CG configurations, as long as the UE selects the same HARQ process in different CG configurations and the different CG configurations have the same transport block size (TBS).

[0105] A preconfigured authorization timer CGT is defined in the NR system. CGT is used to limit the total duration of the transmission process. The CGT corresponds to a transmission duration threshold. Since the NR-U system uses the mechanism of the NR system, the NR-U system can use CGT, and in order to limit the retransmission interval, a preconfigured authorization retransmission timer CGRT is newly defined in the NR-U system. The CGRT is used to limit the transmission interval between the new transmission and retransmission during the transmission process, as well as the transmission interval between two retransmissions. The CGRT corresponds to a retransmission duration threshold. Among them, the retransmission duration threshold is less than the transmission duration threshold. In the NR-U system, the terminal can use CGRT and CGT to control new transmissions and retransmissions.

[0106] Specifically, the terminal uses a HARQ process associated with a CG configuration for new transmission. If the uplink LBT is successful, it means that the uplink data is sent successfully, and CGT and CGRT are started; otherwise, CGT and CGRT are not started. After starting CGT and CGRT, during the CGT timing, if the timing duration of CGRT is equal to the retransmission duration threshold or NACK feedback is received from the network device, the terminal stops CGRT and uses the HARQ process to automatically retransmit. The terminal uses the HARQ process to retransmit. If the uplink LBT is successful, it means that the retransmission of the uplink data is successful, and CGRT is restarted; otherwise, CGRT is not restarted, and the HARQ process continues to be retransmitted. If the timing duration of CGT is equal to the transmission duration threshold or ACK feedback is received from the network device, CGT and CGRT are stopped. At this time, the terminal can use the HARQ process to transmit other uplink data.

[0107] Among them, the terminal automatically retransmits, only restarting CGRT, not CGT. If ACK feedback is received from the network device, it means that the network device correctly receives the uplink data. The terminal will not stop CGT when receiving NACK feedback, but will stop CGT when receiving ACK feedback.

[0108] It is understandable that during the CGT timing of the HARQ process, the terminal cannot use the HARQ process to transmit other uplink data, so as to avoid other uplink data from flushing out the uplink data in the HARQ buffer of the HARQ process, causing packet loss.

[0109] For example, Figure 3 As shown, the process of transmitting uplink data using a HARQ process associated with a CG configuration by the terminal can be divided into multiple time units in the time domain, and the multiple time units include t1, t2, t3, t4, t5, t6, ..., tm in chronological order, where m is a positive integer. Among them, the multiple time units can be continuous or timed in intervals, which is not specifically limited in the embodiments of the present application. The length of a time unit can be set arbitrarily, which is not specifically limited in the embodiments of the present application. For example, a time unit may include one or more subframes; or, a time unit may include one or more time slots. In addition, the timing duration of CGRT is equal to the retransmission duration threshold, and the receipt of NACK feedback can be considered as a CGRT timeout. The timing duration of CGT is equal to the transmission duration threshold, and the receipt of ACK feedback from the network device can be considered as a CGT timeout.

[0110] On this basis, the process of the terminal using the HARQ process to transmit the uplink data may include: the terminal transmits a new transmission at t1, and the uplink LBT succeeds, then starts CGT and CGRT, and waits for the network device to receive the uplink data. After t2 and t3, the CGRT times out, the terminal stops CGRT, and automatically retransmits using the HARQ process at t4. At t4, the uplink LBT fails, and the CGRT is not restarted, and the HARQ process continues to be used to retransmit at t5. The terminal retransmits at t5, and the uplink LBT succeeds, restarts CGRT, and waits for the network device to receive the uplink data. At tm, the CGT times out, and the terminal stops CGT and CGRT. At this point, the terminal can use the HARQ process to transmit other uplink data.

[0111] It is understandable that in the above technology, if the terminal fails to send uplink data when starting a new transmission with the HARQ process, CGT and CGRT will not be started, and retransmission is impossible, and the uplink data will be stored in the HARQ buffer of the HARQ process. Since CGT is not started, if other mechanisms are not introduced, the terminal may use the HARQ process to newly transmit other uplink data, and the other uplink data will flush the uplink data in the HARQ buffer. In this case, the uplink data is not sent to the network device, and the HARQ process will no longer be used to send the uplink data. In other words, the uplink data is discarded and can only rely on the higher layer to retransmit the uplink data.

[0112] To address this issue, the NR-U system introduces a suspended pending state for a HARQ process. For new transmissions and retransmissions, when a HARQ process is used to successfully send uplink data (i.e., uplink LBT is successful), the terminal determines that the HARQ process is in a non-suspended not pending state; otherwise, the HARQ process is determined to be in a pending state. Secondly, after the HARQ process is in the pending state, the pending state of the HARQ process is canceled only after the uplink data is successfully sent or the HARQ buffer of the HARQ process is cleared. Alternatively, the HARQ process is set to a not pending state when the CGT times out. In other words, when the terminal determines whether a HARQ process can be newly transmitted, it must not only determine whether the CGRT and CCT have stopped timing, but also determine whether the HARQ process is in a not pending state. Only when it is determined that the CGRT and CCT have stopped timing and the HARQ process is in a not pending state, the HARQ process is used for new transmission, otherwise, the HARQ process is used for retransmission. This can avoid the situation where uplink data is discarded due to uplink LBT failure in new transmission and CGT not being started, and the terminal uses the HARQ process to newly transmit other uplink data.

[0113] However, the above scheme is to determine whether the HARQ process is in pending state or not pending state according to whether the uplink LBT succeeds or fails in the new transmission after the HARQ process is used for new transmission. Then, when the HARQ process is initially used, the terminal is not clear about the state of the HARQ process and cannot use the HARQ for new transmission. In other words, the HARQ process lacks an initial state (i.e., not pending state), which makes it impossible to use the HARQ process for new transmission.

[0114] Furthermore, during the transmission of the HARQ process associated with one or more CG configurations on the currently activated BWP, the terminal determines that N consecutive uplink LBT failures have occurred on the currently activated BWP of the serving cell, and the HARQ process being used may be in a pending state. If the serving cell is a primary cell or a primary-secondary cell, the terminal can switch the BWP, and the CG configuration on the switched BWP may also be associated with the HARQ process in the pending state.

[0115] Since the HARQ processes associated with one or more CG configurations on the BWP before the switch may be in the pending state, these HARQ processes cannot be used for new transmission on the BWP after the switch. In other words, the above-mentioned solution using the suspended pending state still has the problem of unclear handling of the pending state of the HARQ processes associated with one or more CG configurations on the BWP before the switch when the terminal switches the BWP, which results in the inability to use these HARQ processes normally on the BWP after the switch.

[0116] Finally, if multiple uplink LBT failures occur in succession before CGT and CGRT are started during the transmission of uplink data, the HARQ process will remain in the pending state. In addition, since the uplink LBT failures occur before CGT and CGRT are started, the terminal cannot determine the duration of the multiple uplink LBT failures, and thus cannot solve the problem of the uplink data transmission process occupying the HARQ process for a long time.

[0117] In response to the above-mentioned problems, an embodiment of the present application provides a data transmission method based on the HARQ process, which can determine the initial state of the HARQ process, and then use the HARQ process in the not pending state for uplink transmission. It can also solve the problem of unclear handling of the pending state of the HARQ process associated with one or more CG configurations on the BWP before the switch when switching the BWP, so that these HARQ processes can be used normally on the BWP after the switch. In addition, it can also avoid the problem of long-term occupation of the HARQ process in the transmission process of uplink data due to multiple consecutive uplink LBT failures before starting CGT and CGRT.

[0118] The present application embodiment provides a data transmission method based on a HARQ process, such as Figure 4 As shown, the data transmission method based on the HARQ process includes S401-S402.

[0119] S401. The terminal sets one or more HARQ processes associated with a first pre-configured grant CG configuration on a first bandwidth BWP to a not pending state.

[0120] The first CG configuration includes one or more CG configurations configured by the network device for the terminal on the first BWP. The first BWP is the BWP currently activated by the terminal.

[0121] Exemplarily, the above-mentioned first BWP belongs to a plurality of dedicated BWPs configured by the network device for the terminal on the service cell where the terminal is located. The first BWP may be a BWP activated by the network device for the terminal. The network device may also configure a first CG configuration for the first BWP. The first CG configuration includes a HARQ process associated with the first CG configuration. The terminal may receive the configuration of the network device, and may set one or more HARQ processes associated with the first CG configuration to a not pending state.

[0122] It should be noted that the terminal in any embodiment of the present application sets the above one or more HARQ processes to the not pending state, which is implemented internally by the terminal. The "the terminal sets one or more HARQ processes to the not pending state" in any embodiment of the present application can be replaced by "the terminal considers that one or more HARQ processes are in the not pending state" or "the terminal considers that one or more HARQ processes are in the not pending state".

[0123] The first CG configuration may be a partial CG configuration or all CG configurations configured by the network device for the terminal on the first BWP. The one or more HARQ processes associated with the first CG configuration may be all HARQ processes or a partial HARQ process associated with the first CG configuration.

[0124] In some embodiments, the one or more HARQ processes associated with the first CG configuration may include at least any one of the following six HARQ processes:

[0125] (1): All HARQ processes associated with the first CG configuration.

[0126] (2): The HARQ process in the HARQ process associated with the first CG configuration and in the pending state.

[0127] (3): The HARQ process associated with the first CG configuration that is not in the not pending state.

[0128] (4): The first HARQ process in the HARQ process associated with the first CG configuration. Among them, there is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity. There is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity, indicating that the first HARQ process has not been used by the terminal.

[0129] (5): The HARQ process that is not in use among the HARQ processes associated with the first CG configuration.

[0130] (6): The corresponding HARQ process (corresponding HARQ process) in the HARQ process associated with the first CG configuration. The corresponding HARQ process is a HARQ process randomly selected by the terminal.

[0131] Among them, the uplink grant currently submitted to the HARQ entity of the terminal (i.e., the uplink grant currently processed by the HARQ entity of the terminal) are all uplink grants associated with the HARQ process submitted to the HARQ entity before the current moment. There is no uplink grant associated with the first HARQ process in the uplink grant currently submitted to the HARQ entity, indicating that the terminal has not used the first HARQ process before the current moment. The above-mentioned corresponding HARQ process can be used to send the uplink data, and the terminal internally implements random selection of the corresponding HARQ process.

[0132] It should be noted that, since different CG configurations can share the HARQ process, when the terminal transmits uplink data through any CG configuration (including the first CG configuration), it can randomly select a HARQ process from the HARQ process associated with the first CG configuration. Therefore, some HARQ processes in the first CG configuration may have been used by other CG configurations or are being used by other CG configurations. Other CG configurations are CG configurations other than the first CG configuration. Since the network device can dynamically schedule any HARQ process through DG, some HARQ processes in the first CG configuration may also have been scheduled by DG or are being scheduled by DG. The above "not used" may mean that it has not been used by any CG configuration and DG of the terminal. The above "not being used" may mean that it is not being used by other CG configurations and / or DG (the terminal is transmitting data through this HARQ process on other CG configurations).

[0133] It is understandable that the terminal can set the unused HARQ process associated with the first CG configuration because if a HARQ process has been used, it indicates that the transmission has been performed (transmission has been performed). According to the existing communication protocol, the HARQ process is already in the not pending state, and there is no problem of lack of initial state. In addition, the terminal can also set the unused HARQ process associated with the first CG configuration to the not pending state because if a HARQ process is being used, the state of the HARQ process cannot be changed at will before the transmission is completed, otherwise the uplink data being transmitted may be discarded (i.e., packet loss), so only the unused HARQ process associated with the first CG configuration is set.

[0134] In some embodiments, the one or more HARQ processes associated with the first CG configuration may also include: the first HARQ process among the HARQ processes associated with the first CG configuration, and the HARQ processes that are not in use among the HARQ processes associated with the first CG configuration.

[0135] S402. The terminal uses the HARQ process in the not pending state that is associated with the first CG configuration to send uplink data to the network device.

[0136] When the terminal needs to send uplink data, it can select a HARQ process from one or more HARQ processes associated with the first CG configuration and set to the not pending state. Since the HARQ process is in the not pending state, the terminal can use the HARQ process to send the uplink data.

[0137] In the data transmission method based on the HARQ process provided in the embodiment of the present application, the terminal can set one or more HARQ processes associated with the first CG configuration configured by the network device to the not pending state when receiving the configuration of the network device. In this way, the setting of the initial state (i.e., not pending state) of the one or more HARQ processes is realized. Before being used for uplink transmission, the one or more HARQ processes associated with the first CG configuration are already in the not pending state, that is, the one or more HARQ processes associated with the first CG configuration can be used for uplink transmission, or the one or more HARQ processes associated with the first CG configuration can be used for new transmission. Therefore, the terminal can use one of the one or more HARQ processes to send uplink data (or newly transmitted uplink data). In this way, the terminal can use the HARQ process whose initial state is the not pending state for uplink transmission (or new transmission).

[0138] In some embodiments, the network device may use different configuration methods to configure the CG configuration for the terminal on the first BWP. The first CG configuration obtained by using different configuration methods is also different. Among them, the configuration method used by the network device may include the above-mentioned configuration authorization method 1 and the above-mentioned configuration authorization method 2.

[0139] In the case where the network device uses RRC signaling (i.e., uses configuration authorization mode 1 or the above configuration authorization mode 2), the first CG configuration includes all CG configurations that the network device configures and activates for the terminal on the first BWP using configuration authorization mode 1; or, the first CG configuration includes all CG configurations that the network device only configures (i.e., only configures but does not activate) for the terminal on the first BWP using configuration authorization mode 2. Specifically, the above S401 may include S501. For example, Figure 5 As shown, the method provided in the embodiment of the present application includes S501-S502.

[0140] S501. In response to receiving an RRC signaling from a network device, the terminal sets one or more HARQ processes associated with the first CG configuration to a not pending state. The RRC signaling is used to configure and activate the first CG configuration for the terminal, or to configure only the first CG configuration for the terminal.

[0141] It should be noted that for a detailed description of one or more HARQ processes associated with the first CG configuration described in S501, reference can be made to the introduction of one or more HARQ processes associated with the first CG configuration described in S401 in the above embodiment, which will not be repeated here in the embodiments of the present application.

[0142] Among them, after the terminal receives the RRC signaling from the network device, it can set one or more HARQ processes associated with the first CG configuration indicated by the RRC signaling to the not pending state.

[0143] Among them, the RRC signaling in configuration authorization method 1 is used to configure and activate the first CG configuration for the terminal. The RRC signaling in configuration authorization method 2 is used to configure only the first CG configuration for the terminal.

[0144] S502. The terminal uses the HARQ process in the not pending state that is associated with the first CG configuration to send uplink data to the network device.

[0145] It should be noted that the implementation process of step S502 is the same as the implementation process of step S402, which will not be repeated here.

[0146] In the data transmission method based on the HARQ process provided in the embodiment of the present application, when receiving the first CG configuration configured by the network device, the terminal can set one or more HARQ processes associated with the first CG configuration to the not pending state. In this way, the one or more HARQ processes associated with the first CG configuration are in the not pending state before being used for uplink transmission, indicating that the one or more HARQ processes can be used for new transmission.

[0147] When the DCI activation command is used (i.e., configuration authorization mode 2 is used), the first CG configuration may be a CG configuration activated by the DCI activation command. Specifically, the above S401 may also include S601. For example, Figure 6 As shown, an embodiment of the present application provides a data transmission method based on a HARQ process including S601-S602.

[0148] S601. In response to receiving a DCI activation command from a network device, a terminal sets one or more HARQ processes associated with a first CG configuration to a not pending state, wherein the DCI activation command is used to instruct the terminal to activate the first CG configuration.

[0149] It should be noted that for a detailed description of one or more HARQ processes associated with the first CG configuration described in S601, reference can be made to the introduction of one or more HARQ processes associated with the first CG configuration described in S401 in the above embodiment, which will not be repeated here in the embodiments of the present application.

[0150] Before using the DCI activation command, the network device first uses the RRC signaling in the configuration authorization method 2 to configure only one or more CG configurations on the first BWP for the terminal, and then uses the DCI activation command to activate (first activation or reactivation) one of the one or more CG configurations, which is the first CG configuration. When the terminal receives the DCI activation command from the network device, it sets one or more HARQ processes associated with the first CG configuration to the notpending state. The DCI activation command can be a first activation command or a reactivation command.

[0151] The first CG configuration activated by the network device using the DCI activation command may be the first CG configuration activated for the first time using the DCI activation command; in this case, the DCI activation command may also be referred to as the first activation command. The first CG configuration activated by the network device using the DCI activation command may also be the first CG configuration reactivated using the DCI activation command; in this case, the DCI activation command may also be referred to as the reactivation command.

[0152] S602. The terminal uses the HARQ process in the not pending state that is associated with the first CG configuration to send uplink data to the network device.

[0153] It should be noted that the implementation process of step S602 is the same as the implementation process of step S402, which will not be repeated here.

[0154] In the data transmission method based on the HARQ process provided in the embodiment of the present application, when the terminal receives the DCI activation command for the first CG configuration from the network device, the terminal can set one or more HARQ processes associated with the first CG configuration currently to be activated to the not pending state. In this way, the one or more HARQ processes associated with the first CG configuration currently to be activated are in the not pending state, indicating that the one or more HARQ processes can be used for new transmission.

[0155] It should be noted that, in addition to the first opportunity mentioned above (i.e., in response to receiving RRC signaling from the network device, or in response to receiving a DCI activation command from the network device), the terminal sets one or more HARQ processes associated with the first CG configuration to the not pending state. One or more HARQ processes associated with the first CG configuration may also be set to the not pending state at other times other than the first opportunity, which is not limited in the embodiments of the present application.

[0156] Exemplarily, for the above-mentioned first HARQ process, the above-mentioned S401 may also include: when the terminal processes an authorization (grant) configuration associated with an activated CG configuration, the activated CG configuration is the first CG configuration, and a first HARQ process is determined in all HARQ processes associated with the first CG configuration. If there is no uplink authorization associated with the first HARQ process in the uplink authorization currently submitted to the HARQ entity, the terminal device considers that the state of the first HARQ process is a non-suspended not pending state (that is, the state of the first HARQ process is set to a not pending state). Among them, the grant configuration associated with an activated CG configuration may appear according to a preset period, and the preset period may be specified by the RRC signaling adopted by the above-mentioned configuration authorization method 1 or the above-mentioned configuration authorization method 2.

[0157] In some embodiments, after setting one or more HARQ processes associated with the above-mentioned first CG to the notpending state (for example, after the above-mentioned step S401, step S501 or step S601), the terminal also detects whether N consecutive uplink LBT failures occur on the currently activated first BWP.

[0158] Taking steps S401-S402 as an example, Figure 7 As shown, the data transmission method based on the HARQ process provided in the embodiment of the present application further includes steps S701-S702 after step S401.

[0159] S701. The terminal counts the total number of uplink LBT failures occurring on the first BWP, and compares whether the total number of uplink LBT failures is equal to a preset LBT failure number threshold N.

[0160] The total number of uplink LBT failures occurring on the first BWP includes: the number of uplink LBT failures occurring when the terminal performs uplink data transmission on the first BWP.

[0161] S702: If the total number of uplink LBT failures is equal to the preset LBT failure number threshold N, the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP; otherwise, it determines that N consecutive uplink LBT failures have not occurred on the first BWP.

[0162] The terminal determines that N consecutive uplink LBT failures occur on the first BWP, triggering a continuous uplink LBT failure state.

[0163] It should be noted that Figure 7 Steps S701-S702 and step S402 in are parallel, Figure 7The execution order of steps S701-S702 and step S402 is only an exemplary description. Step S701 can be to count the number of uplink LBT failures during the execution of step S402, or can be to count the number of uplink LBT failures during the execution of step S402 and the subsequent execution of sending other uplink data.

[0164] Furthermore, if Figure 8 As shown, after step S702, the data transmission method based on the HARQ process further includes step S703.

[0165] Step S703: If the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, it clears the cache of all HARQ processes associated with the second CG configuration on the first BWP, or sets all HARQ processes associated with the second CG configuration on the first BWP to not pending state.

[0166] The second CG configuration includes all CG configurations configured by the network device for the terminal on the first BWP, or the CG configuration activated by the terminal on the first BWP; after the cache of all HARQ processes associated with the second CG configuration is cleared, all HARQ processes associated with the second CG configuration are in the not pending state.

[0167] If the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, it directly triggers the clearing of the cache of all HARQ processes associated with the second CG configuration on the first BWP, or directly triggers the setting of all HARQ processes associated with the second CG configuration on the first BWP to not pending state.

[0168] It should be noted that the second CG configuration and the first CG configuration may be the same or different.

[0169] In an embodiment of the present application, during the transmission of the HARQ process associated with one or more CG configurations on the first BWP (i.e., the BWP before switching), the terminal determines that N consecutive uplink LBT failures occur on the first BWP, indicating that the HARQ process being used on the first BWP may be in a pending state. At this time, the terminal sets all HARQ processes associated with the second CG configuration on the first BWP to a not pending state. Among them, the terminal can set all HARQ processes associated with the first CG configuration on the first BWP to a not pending state by clearing the cache of all HARQ processes associated with the second CG configuration on the first BWP, or setting all HARQ processes associated with the second CG configuration to a not pending state. It can be understood that all HARQ processes associated with the above-mentioned second CG configuration may include HARQ processes in a pending state on the first BWP. Therefore, clearing the cache of all HARQ processes associated with the second CG configuration on the first BWP, or setting all HARQ processes associated with the second CG configuration to a not pending state, can achieve setting all HARQ processes associated with the first CG configuration on the first BWP to a not pending state.

[0170] In this way, the problem of not processing the status of the HARQ process in the pending state on the first BWP (i.e., the BWP before the switch) when the terminal switches BWP is solved. Furthermore, the CG configuration of the terminal on the second BWP (i.e., the BWP after the switch) may be associated with the HARQ process in the pending state on the first BWP. Since the HARQ process in the pending state on the first BWP has been set to the not pending state, these HARQ processes can be used for new transmission on the BWP after the switch.

[0171] In some embodiments, if the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, when sending a MAC CE to the network device, the cache of all HARQ processes associated with the second CG configuration on the first BWP is cleared, or all HARQ processes associated with the second CG configuration on the first BWP are set to a not pending state. The MAC CE includes an LBT failure status indication bit of the serving cell where the terminal is located.

[0172] The above-mentioned sending of the control element MAC CE of media access control to the network device may refer to the terminal successfully sending the MAC CE. Specifically, if the terminal receives the LBT success indication of the physical layer (PHY) regarding the MAC CE, indicating that the MAC CE can be successfully sent, then it is considered that the MAC CE is successfully sent. In addition, it is also possible to only look at it from the MAC layer, that is, regardless of whether the LBT regarding the MAC CE fails or succeeds, the MAC layer triggers the sending of the MAC CE and it is considered that the sending is successful, that is, it is considered that the MAC CE is successfully sent.

[0173] In some embodiments, the service cell where the terminal is located may include a primary cell, a primary secondary cell, and a secondary cell. If the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, when the terminal is located in the primary cell or the primary secondary cell, it actively switches from the first BWP to the second BWP, clears the cache of all HARQ processes associated with the second CG configuration on the first BWP, or sets all HARQ processes associated with the second CG configuration on the first BWP to the not pending state. The second BWP is a BWP that is configured with a physical random access channel PRACH resource and has not experienced N consecutive uplink LBT failures, and the second BWP and the first BWP belong to the same service cell.

[0174] In some embodiments, if the terminal determines that N consecutive uplink LBT failures have occurred on the first BWP, in the case of any type of cell (i.e., primary cell, primary secondary cell, or secondary cell) in the serving cell, the terminal receives a BWP switching instruction from a network device. In response to the BWP switching instruction, the terminal clears the cache of all HARQ processes associated with the second CG configuration on the first BWP, or sets all HARQ processes associated with the second CG configuration on the first BWP to a not pending state. The BWP switching instruction is used to instruct the terminal to switch from the first BWP to a third BWP. The BWP switching instruction may be RRC signaling or DCI. The third BWP may be the same as or different from the second BWP.

[0175] It should be noted that, in addition to executing "clearing the cache of all HARQ processes associated with the second CG configuration on the first BWP, or setting all HARQ processes associated with the second CG configuration on the first BWP to a not pending state" at the second opportunity mentioned above (i.e., when sending a MAC CE to the network device, actively switching from the first BWP to the second BWP, or responding to a BWP switching instruction), the terminal may also execute "clearing the cache of all HARQ processes associated with the second CG configuration on the first BWP, or setting all HARQ processes associated with the second CG configuration on the first BWP to a not pending state" at other times except the second opportunity, and the embodiments of the present application do not impose any restrictions thereon.

[0176] In order to more accurately control the duration of an uplink data transmission process occupying a HARQ process, after setting one or more HARQ processes associated with the first CG to the not pending state (for example, after the above step S401, step S501 or step S601), the terminal records the total duration of a HARQ process used in an uplink data transmission process being in the pending state, or the number of times the HARQ process used in the transmission process enters the pending state, while sending uplink data to the network device. The total duration or the number of times the HARQ process enters the pending state can be used to more accurately control the duration of an uplink data transmission process occupying a HARQ process.

[0177] The terminal can more accurately control the duration of the HARQ process occupied by an uplink data transmission process by recording the number of times the HARQ process used in the uplink data transmission process enters the pending state. Fig. 9 As shown, the HARQ process-based data transmission method provided in an embodiment of the present application may include steps S901-S902 after step S401.

[0178] Step S901: The terminal counts the number of pending times that a HARQ process for sending uplink data enters a pending state during the process of transmitting uplink data.

[0179] The pending times include: the times that the HARQ process for sending uplink data enters the pending state during new transmission and retransmission.

[0180] The terminal can define a pending counter, which is used to record the number of pending times. The initial value of the pending number recorded by the pending counter is zero. The preset number threshold corresponding to the pending counter can be configured by the network device or preset by the protocol. The preset number threshold can be carried in the configuration information of the CG configuration, and the preset number thresholds in the configuration information of different CG configurations can be the same or different. This pending counter can be maintained by each HARQ process, that is, the number of times each HARQ process enters the pending state is recorded.

[0181] Furthermore, during each new transmission or retransmission of uplink data, the terminal determines whether the HARQ process used to send the uplink data is in a pending state. If it is in a pending state, the pending counter is incremented by 1 (i.e., the number of pending times is incremented by 1); otherwise, it is not incremented by 1 (i.e., the number of pending times is not incremented by 1). It is also determined whether the number of pending times recorded by the pending counter is equal to a preset number threshold. If the number of pending times is equal to the preset number threshold, step S902 is executed; if the number of pending times is less than the preset number threshold, the number of pending times continues to be counted.

[0182] Step S902: If the pending number is equal to the preset number threshold, the terminal clears the cache of the HARQ process used to send uplink data, or sets the HARQ process used to send uplink data to a not pending state.

[0183] After the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0184] It should be noted that Fig. 9 Steps S901-S902 and step S402 are in parallel, and step S901 can be executed at the same time as step S402 is started.

[0185] In an embodiment of the present application, the number of pending times that a HARQ process used in an uplink data transmission process enters a pending state is counted. The pending number not only includes the number of times the HARQ process enters a pending state due to uplink LBT failures that occur after the CGRT and CGT are started, but also includes the number of times the HARQ process enters a pending state due to multiple consecutive uplink LBT failures that occur in this uplink transmission before the CGRT and CGT are started. In other words, the pending number more accurately records the number of times the HARQ process enters a pending state in this uplink transmission. Then, it is determined that the pending number is equal to the preset number threshold, and the cache of the HARQ process is cleared or the HARQ process is set to a notpending state. By counting the pending number, the occupancy time of an uplink data transmission process for the HARQ process is more accurately controlled, thereby avoiding the situation where an uplink data transmission process occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before the CGT and CGRT are started.

[0186] For example, the terminal can record the number of times the HARQ process used in the transmission process of uplink data enters the pending state, thereby solving the problem that the transmission process of uplink data occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before starting CGT and CGRT. Fig.10 As shown, the HARQ process-based data transmission method provided in the embodiment of the present application may further include steps S1001-S1003 after step S401.

[0187] Step S1001: Each time the terminal determines whether a HARQ process for sending uplink data is newly transmitted or retransmitted, it determines whether the HARQ process for sending uplink data is in a pending state.

[0188] During the transmission of uplink data, the terminal determines whether the HARQ process used to send the uplink data is in the pending state each time a new transmission or retransmission is started. If it is in the pending state, the pending counter is incremented by 1 (i.e., step S1002 is executed); otherwise, it is not incremented by 1 (i.e., the number of pending times recorded by the pending counter remains unchanged).

[0189] Among them, when the terminal determines that it is in the pending state, if the pending counter has not started counting (i.e., not started), the pending counter is used to start counting (i.e., start the pending counter), and the pending counter is increased by 1; if the pending counter is already counting, the pending counter is directly increased by 1 (i.e., the number of pending times is increased by 1). When the terminal determines that it is not in the pending state, if the pending counter has not started counting, the pending counter is not used to start counting or the pending counter is not started, and the pending counter is not increased by 1; if the pending counter is already counting, the pending counter is reset (i.e., the number of pending times recorded by the pending counter is set to 0), and the pending counter is not increased by 1.

[0190] Step S1002: If the HARQ process for sending uplink data is in a pending state, the pending number recorded by the pending counter is increased by 1; the initial value of the pending number recorded by the pending counter is zero.

[0191] After the pending times are incremented by 1, the terminal further determines whether the pending times are equal to the preset times threshold. If the pending times are equal to the preset times threshold, step S1003 is executed; if the pending times are less than the preset times threshold, step S1001 is continued.

[0192] Step S1003: If the pending number recorded by the pending counter is equal to the preset number threshold, the terminal clears the cache of the HARQ process used to send uplink data, or sets the HARQ process used to send uplink data to a notpending state.

[0193] After the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0194] It should be noted that Fig.10 Steps S1001-S1003 and step S402 are in parallel, and step S1001 can be executed at the same time as step S402 is started.

[0195] In an embodiment of the present application, the number of times a HARQ process used in an uplink data transmission process continuously enters a pending state is counted. The HARQ process continuously entering the pending state means that after an uplink LBT failure occurs in a new transmission or retransmission of the HARQ process, an uplink LBT failure still occurs in the next retransmission. The pending number may include the number of times the HARQ process enters the pending state due to multiple consecutive uplink LBT failures before starting CGRT and CGT in this uplink transmission. Then, it is determined that the pending number is equal to a preset number threshold, and the cache of the HARQ process is cleared or the HARQ process is set to a not pending state. Through the pending number, the situation in which an uplink data transmission process occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before starting CGT and CGRT is avoided.

[0196] The terminal can also more accurately control the duration of the HARQ process occupied by an uplink data transmission process by recording the total duration of the HARQ process in the pending state. Fig.11 As shown, the HARQ process-based data transmission method provided in an embodiment of the present application may include steps S1101-S1102 after step S401.

[0197] Step S1101: The terminal counts the total time duration in which the HARQ process used to send uplink data is in a pending state during the process of transmitting uplink data.

[0198] The terminal can define a pending timer, which is used to record the total duration. The preset duration threshold corresponding to the pending timer can be configured by the network device or preset by the protocol. The preset duration threshold can be carried in the configuration information of the CG configuration, and the preset duration thresholds in the configuration information of different CG configurations can be the same or different. This pending timer can be maintained by each HARQ process, that is, the total duration that each HARQ process is in the pending state is recorded.

[0199] Furthermore, during the transmission of uplink data, the terminal determines whether the HARQ process used for this uplink transmission is in a pending state. If it is in a pending state, the terminal starts a pending timer, otherwise it stops the pending timer. During the pending timer timing, it is also determined whether the total duration of the HARQ process in the pending state recorded by the pending timer is equal to a preset duration threshold. If the total duration is equal to the preset duration threshold, step S1102 is executed, otherwise, the total duration continues to be counted.

[0200] Specifically, during each new transmission or retransmission of an uplink data transmission process, the terminal determines whether the HARQ process used to send the uplink data is in a pending state. If it is in a pending state and the pending timer has not started (i.e., not started), the terminal starts the pending timer; if it is in a pending state and the pending timer is already timing, the pending timer continues to time. If it is not in a pending state and the pending timer has not started (i.e., not started), the pending timer is not started (i.e., the pending timer is not used for timing); if it is not in a pending state and the pending timer is already timing, the pending timer is stopped (i.e., the pending timer stops timing).

[0201] Step S1102: If the total duration is equal to the preset duration threshold, the terminal clears the cache of the HARQ process used to send uplink data, or sets the HARQ process used to send uplink data to a not pending state.

[0202] After the cache of the HARQ process for sending uplink data is cleared, the HARQ process for sending uplink data is in a not pending state.

[0203] It should be noted that Fig.11 Steps S1101-S1102 and step S402 are in parallel, and step S1101 can be executed at the same time as step S402 is started.

[0204] In an embodiment of the present application, the total duration of a HARQ process used in an uplink data transmission process in a pending state is counted. The total duration not only includes the duration of the HARQ process in a pending state due to an uplink LBT failure that occurs after the CGRT and CGT are started, but also includes the duration of the HARQ process in a pending state due to multiple consecutive uplink LBT failures that occur in this uplink transmission before the CGRT and CGT are started. In other words, the total duration more accurately records the duration of the HARQ process in a pending state in this uplink transmission. Then, it is determined that the total duration is equal to a preset duration threshold, and the cache of the HARQ process is cleared or the HARQ process is set to a not pending state. The total duration is used to more accurately control the duration of the HARQ process occupied by an uplink data transmission process, thereby avoiding the situation where an uplink data transmission process occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before the CGT and CGRT are started.

[0205] For example, the terminal can also record the total time that the HARQ process used in the transmission process of uplink data is in the pending state, thereby solving the problem that the transmission process of uplink data occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before starting CGT and CGRT. Fig.12 As shown, the HARQ process-based data transmission method provided in the embodiment of the present application may further include steps S1201-S1204 after step S401.

[0206] Step S1201: Each time the terminal determines whether a HARQ process for sending uplink data is newly transmitted or retransmitted, it determines whether the HARQ process for sending uplink data is in a pending state or a not pending state.

[0207] The terminal can determine whether the HARQ process used to send uplink data is in the pending state or the not pending state each time a new transmission or retransmission starts during the transmission of uplink data. If it is in the pending state, if the pending timer is not started, step S1202 is executed; if the pending timer is running (i.e., timing), the pending timer continues to run (i.e., continues timing). If it is in the not pending state, if the pending timer is not started, the pending timer is not started; if the pending timer is running, step S1203 is executed.

[0208] Step S1202: The terminal determines that the HARQ process for sending uplink data is in a pending state and the pending timer is not started, and starts the pending timer.

[0209] The pending timer is used to count the total time that the HARQ process used to send uplink data is in the pending state during the process of transmitting uplink data.

[0210] During the transmission of uplink data, the terminal further determines whether the timing duration recorded by the pending timer (i.e., the total duration of the HARQ process in the pending state) is equal to a preset duration threshold when the pending timer is in operation (i.e., timing). If the timing duration is equal to the preset duration threshold, step S1204 is executed; otherwise, step S1201 is continued.

[0211] Step S1203: The terminal determines that the HARQ process for sending uplink data is in the not pending state and the pending timer is running, and stops the pending timer.

[0212] During the transmission of uplink data, the terminal further determines whether the timing duration recorded by the pending timer (i.e., the total duration of the HARQ process in the pending state) is equal to a preset duration threshold when the pending timer is in operation (i.e., timing). If the timing duration is equal to the preset duration threshold, step S1204 is executed; otherwise, step S1201 is continued.

[0213] Step S1204: If the timing duration of the pending timer is equal to the preset duration threshold, the terminal clears the cache of the HARQ process used to send uplink data, or sets the HARQ process used to send uplink data to a not pending state.

[0214] After the cache of the HARQ process used to send uplink data is cleared, the HARQ process used to send uplink data is in a not pending state.

[0215] In an embodiment of the present application, the total duration of a HARQ process used in an uplink data transmission process being in a pending state is counted. The HARQ process being in a pending state continuously means that the HARQ process has an uplink LBT failure and is in a pending state during a new transmission or retransmission, and the uplink LBT failure still occurs in the next retransmission and is in a pending state. The total duration may include the duration of the HARQ process being in a pending state due to multiple consecutive uplink LBT failures in this uplink transmission before the CGRT and CGT are started. Then determine that the total duration is equal to the preset duration threshold, clear the cache of the HARQ process or set the HARQ process to a not pending state. Through this total duration, the situation in which an uplink data transmission process occupies the HARQ process for a long time due to multiple consecutive uplink LBT failures before the CGT and CGRT are started is avoided.

[0216] It is understandable that, in order to realize the above functions, the above-mentioned terminals etc. include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0217] The embodiment of the present application can divide the functional modules of the above-mentioned terminal etc. according to the above-mentioned method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0218] In the case of dividing each functional module into corresponding functional modules, such as Fig.13 As shown, an embodiment of the present application provides a terminal 1300 , which includes: a state setting unit 1301 and a data sending unit 1302 .

[0219] The state setting unit 1301 is used to support the terminal 1300 to execute S401, S501, S601, S703, S902, S1003, S1102, S1204 in the above method embodiments, and / or other processes for the technology described in this document; the data sending unit 1302 is used to support the terminal 1300 to execute S402, S502, S602 in the above method embodiments, and / or other processes for the technology described in this document.

[0220] Furthermore, the terminal 1300 may further include: a communication unit 1303. The communication unit 1303 is used to support the terminal 1300 to execute "receiving a BWP switching instruction from a network device" in the above method embodiment, and / or other processes of the technology described herein.

[0221] Furthermore, the terminal 1300 may further include: a times counting unit 1304. The times counting unit 1304 is used to support the terminal 1300 to execute S901, S1001-S1002 in the above method embodiment, and / or other processes for the technology described herein.

[0222] Furthermore, the terminal 1300 may further include: a duration statistics unit 1305. The duration statistics unit 1305

[0223] Used to support the terminal 1300 to execute S1001, S1201-S1203 in the above method embodiment, and / or other processes for the technology described in this document.

[0224] Of course, the terminal 1300 includes but is not limited to the unit modules listed above. For example, the terminal 1300 may also include a storage unit for saving the non-suspended not pending state of the HARQ process. In addition, the specific functions that can be implemented by the above functional units also include but are not limited to the functions corresponding to the method steps described in the above examples. The detailed description of other units of the terminal 1300 can refer to the detailed description of the corresponding method steps, and the embodiments of the present application will not be repeated here.

[0225] In the case of using an integrated unit, the above-mentioned state setting unit 1301, communication unit 1303, number statistics unit 1304 and duration statistics unit 1305 can be integrated into one processing module, the above-mentioned data sending unit 1302 and communication unit 1303 can be the communication circuit of the terminal, and the above-mentioned storage unit can be the storage module of the terminal.

[0226] Fig.14 A possible structural diagram of a terminal involved in the above embodiment is shown. The terminal 1400 includes: a processing module 1401 , a storage module 1402 and a communication module 1403 .

[0227] The processing module 1401 is used to control and manage the terminal 1400. The storage module 1402 is used to store the program code and data of the terminal 1400. The communication module 1403 is used to communicate with other devices. For example, the communication module is used to receive or send data to other devices.

[0228] Among them, the processing module 1401 can be a processor or a controller, for example, it can be a CPU, a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application-Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic boxes, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements a computing function, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication module 1403 can be a transceiver, a transceiver circuit or a communication interface, etc. The storage module 1402 can be a memory.

[0229] When the processing module 1401 is a processor (such as Figure 2 The processor 21 and processor 25 shown in FIG. 14 ), the communication module 1403 is a communication circuit (such as Figure 2 The communication interface 23 shown in FIG. 14 ), the storage module 1402 is a memory (such as Figure 2 The terminal provided by the present application can be Figure 2 The terminal shown in the figure. The processor, communication interface and memory mentioned above can be coupled together via a bus.

[0230] The embodiment of the present application further provides a computer storage medium in which a computer program code is stored. When the processor executes the computer program code, the terminal executes Figure 4-12 The relevant method steps in any of the accompanying drawings implement the method in the above embodiment.

[0231] The present application also provides a computer program product, which, when executed on a terminal, enables the terminal to execute Figure 4-12 The relevant method steps in any of the accompanying drawings implement the method in the above embodiment.

[0232] Among them, the terminal 1300, terminal 1400, computer storage medium or computer program product provided in this application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0233] Through the description of the above implementation methods, technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0234] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0235] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0236] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0237] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art, or all or part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: flash memory, mobile hard disk, read-only memory, random access memory, disk or optical disk, and other media that can store program codes.

[0238] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A data transmission method based on a hybrid automatic repeat request HARQ process, characterized in that: The method is applied to a terminal or a chip in the terminal, and includes: In response to a downlink control information DCI activation command or a radio resource control RRC signaling of a network device, one or more HARQ processes associated with a first pre-configured authorization CG configuration on a first bandwidth BWP are set to a not-pending state; wherein the first CG configuration includes one or more CG configurations configured by the network device for the terminal on the first BWP; the first BWP is a BWP currently activated by the terminal; If it is determined that N consecutive uplink listen-before-talk LBT failures occur on the first BWP, at the first moment or when a BWP switching instruction is received from the network device, at least one of the following is performed: Clear the cache of all HARQ processes associated with the second CG configuration on the first BWP, or set all HARQ processes associated with the second CG configuration on the first BWP to the not pending state; Wherein, N≥2, N is a positive integer; the second CG configuration includes all CG configurations configured by the network device for the terminal on the first BWP, or CG configurations activated for the terminal on the first BWP; after the caches of all HARQ processes associated with the second CG configuration are cleared, all HARQ processes associated with the second CG configuration are in the not pending state; The first moment includes one of the following: The moment of sending a media access control control element MAC CE to the network device, wherein the MAC CE includes an LBT failure status indication bit of the serving cell where the terminal is located; At the moment of actively switching from the first BWP to the second BWP, the terminal is located in the primary cell or the primary and secondary cells, the second BWP is a BWP configured with physical random access channel PRACH resources and has not experienced N consecutive uplink LBT failures, and the second BWP and the first BWP belong to the same service cell.

2. The method according to claim 1, characterized in that The DCI activation command is used to instruct the terminal to activate the first CG configuration.

3. The method according to claim 1, characterized in that The RRC signaling is used to configure and activate the first CG configuration for the terminal, or to configure only the first CG configuration for the terminal.

4. The method according to any one of claims 1 to 3, characterized in that The one or more HARQ processes associated with the first CG configuration include: All HARQ processes associated with the first CG configuration; Or, a HARQ process in a pending state among the HARQ processes associated with the first CG configuration; Or, a HARQ process that is not in a not pending state among the HARQ processes associated with the first CG configuration; or, a first HARQ process in the HARQ process associated with the first CG configuration; wherein, the uplink grant currently delivered to the HARQ entity does not contain an uplink grant associated with the first HARQ process; and the uplink grant currently delivered to the HARQ entity does not contain an uplink grant associated with the first HARQ process, indicating that the first HARQ process has not been used by the terminal; Or, a HARQ process that is not in use among the HARQ processes associated with the first CG configuration; Alternatively, the corresponding HARQ process in the HARQ process associated with the first CG configuration; the corresponding HARQ process is a HARQ process randomly selected by the terminal.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: each time determining whether a HARQ process for sending the uplink data is newly transmitted or retransmitted, determining whether the HARQ process for sending the uplink data is in a pending state; If the HARQ process for sending the uplink data is in the pending state, the number of pending times recorded by the suspension counter is increased by 1; the initial value of the number of pending times recorded by the suspension counter is zero; If the number of pending times recorded by the suspension counter is equal to a preset number threshold, the cache of the HARQ process used to send the uplink data is cleared, or the HARQ process used to send the uplink data is set to the not pending state; wherein, after the cache of the HARQ process used to send the uplink data is cleared, the HARQ process used to send the uplink data is in the not pending state.

6. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Each time determining whether a HARQ process for sending uplink data is newly transmitted or retransmitted, determining whether the HARQ process for sending uplink data is in a pending state or in the not pending state; Determining that the HARQ process for sending the uplink data is in the pending state and the suspension timer is not started, and starting the suspension timer; the suspension timer is used to count the total time length of the HARQ process for sending the uplink data being in the pending state during the process of transmitting the uplink data; Determining that the HARQ process for sending the uplink data is in the not pending state and the suspension timer is running, and stopping the suspension timer; If the timing duration of the suspension timer is equal to the preset duration threshold, the cache of the HARQ process used to send the uplink data is cleared, or the HARQ process used to send the uplink data is set to the not pending state; wherein, after the cache of the HARQ process used to send the uplink data is cleared, the HARQ process used to send the uplink data is in the not pending state.

7. A communication device, characterized in that: The communication device comprises: a state setting unit and a data sending unit; The state setting unit is used to set one or more HARQ processes associated with the first pre-configured authorized CG configuration on the first bandwidth BWP to a non-suspended not pending state in response to a downlink control information DCI activation command or a radio resource control RRC signaling of the network device; wherein the first CG configuration includes one or more CG configurations configured by the network device for the communication device on the first BWP; the first BWP is the BWP currently activated by the communication device; The state setting unit is further configured to, if it is determined that N consecutive uplink listen-before-talk LBT failures occur on the first BWP, at a first moment or when a BWP switching instruction is received from the network device, perform at least one of the following: clearing the cache of all HARQ processes associated with the second CG configuration on the first BWP, or setting all HARQ processes associated with the second CG configuration on the first BWP to the not pending state; Wherein, N≥2, N is a positive integer; the second CG configuration includes all CG configurations configured by the network device for the communication device on the first BWP, or the CG configuration activated for the communication device on the first BWP; after the caches of all HARQ processes associated with the second CG configuration are cleared, all HARQ processes associated with the second CG configuration are in the not pending state; The first moment includes one of the following: The moment of sending a media access control control element MAC CE to the network device, wherein the MAC CE includes an LBT failure status indication bit of the serving cell where the communication device is located; At the moment of actively switching from the first BWP to the second BWP, the communication device is located in the primary cell or the primary and secondary cells, the second BWP is a BWP configured with physical random access channel PRACH resources and has not experienced N consecutive uplink LBT failures, and the second BWP and the first BWP belong to the same service cell.

8. The communication device according to claim 7, characterized in that: The DCI activation command is used to instruct the communication device to activate the first CG configuration.

9. The communication device according to claim 7, characterized in that: The RRC signaling is used to configure and activate the first CG configuration for the communication device, or to configure only the first CG configuration for the communication device.

10. The communication device according to any one of claims 7 to 9, characterized in that: The one or more HARQ processes associated with the first CG configuration include: All HARQ processes associated with the first CG configuration; Or, a HARQ process in a pending state among the HARQ processes associated with the first CG configuration; Or, a HARQ process that is not in a not pending state among the HARQ processes associated with the first CG configuration; or, a first HARQ process in the HARQ process associated with the first CG configuration; wherein, the uplink grant currently delivered to the HARQ entity does not contain an uplink grant associated with the first HARQ process; and the uplink grant currently delivered to the HARQ entity does not contain an uplink grant associated with the first HARQ process, indicating that the first HARQ process has not been used by the communication device; Or, a HARQ process that is not in use among the HARQ processes associated with the first CG configuration; Alternatively, the corresponding HARQ process in the HARQ process associated with the first CG configuration; the corresponding HARQ process is a HARQ process randomly selected by the communication device.

11. The communication device according to any one of claims 7 to 9, characterized in that: The communication device further comprises: a number statistics unit; The number counting unit is used to determine each time whether the HARQ process used to send the uplink data is newly transmitted or retransmitted, and to judge whether the HARQ process used to send the uplink data is in a pending state; If the HARQ process for sending the uplink data is in the pending state, the number of pending times recorded by the suspension counter is increased by 1; the initial value of the number of pending times recorded by the suspension counter is zero; The state setting unit is also used to clear the cache of the HARQ process used to send the uplink data, or set the HARQ process used to send the uplink data to the not pending state if the number of pending times recorded by the suspension counter is equal to a preset number threshold; wherein, after the cache of the HARQ process used to send the uplink data is cleared, the HARQ process used to send the uplink data is in the not pending state.

12. The communication device according to any one of claims 7 to 9, characterized in that: The communication device further comprises: a duration statistics unit; The duration statistics unit is used to determine each time whether the HARQ process for sending uplink data is newly transmitted or retransmitted, and to judge whether the HARQ process for sending uplink data is in the pending state or the not pending state; Determining that the HARQ process for sending the uplink data is in the pending state and the suspension timer is not started, and starting the suspension timer; the suspension timer is used to count the total time length of the HARQ process for sending the uplink data being in the pending state during the process of transmitting the uplink data; Determining that the HARQ process for sending the uplink data is in the not pending state and the suspension timer is running, and stopping the suspension timer; The state setting unit is also used to clear the cache of the HARQ process used to send the uplink data, or set the HARQ process used to send the uplink data to the not pending state if the timing duration of the suspension timer is equal to a preset duration threshold; wherein, after the cache of the HARQ process used to send the uplink data is cleared, the HARQ process used to send the uplink data is in the not pending state.

13. A terminal, characterized in that: The terminal comprises: a processor, a memory and a communication interface; the memory and the communication interface are coupled to the processor, the memory is used to store computer program code, and the computer program code comprises computer instructions; wherein, when the processor executes the computer instructions, the terminal executes the method as described in any one of claims 1 to 6 above.

14. A computer storage medium, characterized in that: The computer storage medium comprises computer instructions, and when the computer instructions are executed on a terminal, the terminal is caused to execute the method according to any one of claims 1 to 6.

15. A computer program product, characterized in that When the computer program product is executed on a terminal, the terminal is enabled to execute the method according to any one of claims 1 to 6.

Images