Abstract: The present application provides a data transmission method and an apparatus therefor, and a communication system. The method comprises: determining that a first timer is running and a second timer is not running, sending retransmission data according to a configured grant corresponding to a first hybrid automatic repeat request (HARQ) process, and activating the second timer; or, determining that the first timer is not running, sending new data according to a configured grant corresponding to the first HARQ process, and activating the first timer and the second timer.
Title of Invention: Method and device for data transmission, and communication system
technical field
[0001]
The embodiments of the present application relate to the technical field of wireless communication.
Background technique
[0002]
The traditional cellular wireless network serving the public can only use the licensed spectrum, and the unlicensed or shared spectrum, such as the 5GHz frequency band and the 2.4GHz frequency band, is the frequency band used by enterprise or personal wifi, Bluetooth and other wireless devices. As technology has advanced, the deployment of cellular wireless networks has expanded into unlicensed frequency bands.
[0003]
The traditional uplink scheduling is based on the dynamic grant of the Physical Downlink Control Channel (PDCCH). The network device sends PDCCH signaling carrying the uplink resource grant to the terminal device for each uplink transmission, and the terminal device sends uplink data on the authorized resources.
[0004]
The current communication standard also supports the Configured Grant (CG) technology. In the configuration grant technology, the network device can configure a periodic uplink grant for the terminal device through Radio Resource Control (RRC) signaling, and the terminal device can appear in the periodic The data is sent on the uplink resources of the Configured Grant (CG) without receiving the PDCCH signaling sent by the network device in advance.
[0005]
It should be noted that the above description of the technical background is only for the convenience of clearly and completely describing the technical solutions of the present application and facilitating the understanding of those skilled in the art. It should not be assumed that the above-mentioned technical solutions are known to those skilled in the art simply because these solutions are described in the background section of this application.
[0006]
SUMMARY OF THE INVENTION
[0007]
The current communication standard supports the terminal device to send new data on the uplink resource of the Configured Grant (CG), and uses the dynamic grant method to schedule the retransmission of the uplink CG data.
[0008]
The inventor of the present application has found that since the network device needs to perform channel access detection when sending scheduling signaling, using the dynamic authorization method to schedule the uplink CG data retransmission will greatly increase the transmission delay and reduce the transmission efficiency. When retransmitting data is sent on the authorized uplink resources, there may be a problem that the terminal device cannot determine whether to send new data or retransmit data on the CG resource.
[0009]
Embodiments of the present application provide a data transmission method, device, and communication system, which determine whether to send new data on a CG resource or to send new data on a CG resource according to a timer and/or a state of a hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process. By retransmitting the data, the retransmitted data can be sent by using the uplink resources assigned by the configuration, thereby improving the transmission efficiency of the data.
[0010]
According to a first aspect of the embodiments of the present application, there is provided a data transmission method, which is applied to a terminal device. The method includes: determining that the first timer is running and the second timer is not running, requesting the configuration corresponding to the (HARQ) process to authorize sending retransmission data, and starting the second timer; or, determining that the first timer is not running, and sending new data according to the configuration authorizing corresponding to the first HARQ process, The first timer and the second timer are started.
[0011]
According to a second aspect of the embodiments of the present application, a data transmission method is provided, which is applied to a terminal device. The method includes: determining a process state of a first HARQ process to be a second state (ACK), The configuration corresponding to the HARQ process authorizes the sending of new data, setting the process state corresponding to the first HARQ process to the first state (NACK), and starting the first timer and the second timer; or, determining the first HARQ process The state of the process is the first state (NACK) and the second timer is not running, and according to the configuration corresponding to the first HARQ process, the retransmission data is authorized to be sent, and the second timer is started.
[0012]
According to a third aspect of the embodiments of the present application, a data transmission method is provided, applied to a network device, the method includes: receiving data of a first HARQ process sent by a terminal device on a configuration authorized resource; and receiving the received data The uplink control information (UCI) sent by the terminal device and used to indicate the configuration authorization information of the first HARQ process, wherein the UCI includes the process identifier of the first HARQ process and the network identifier of the terminal device, and redundancy version (RV) information of the first HARQ process transport block.
[0013]
According to a fourth aspect of the embodiments of the present application, a data transmission apparatus is provided, which is applied to a terminal device, and the apparatus executes the data transmission method of the first aspect of the embodiments of the present application.
[0014]
According to a fifth aspect of the embodiments of the present application, there is provided a data transmission apparatus, which is applied to a terminal device, and the apparatus executes the data transmission method of the second aspect of the embodiments of the present application.
[0015]
According to a sixth aspect of the embodiments of the present application, a data transmission apparatus is provided, which is applied to a network device, and the apparatus executes the data transmission method of the third aspect of the embodiments of the present application.
[0016]
According to a seventh aspect of the embodiments of the present application, a terminal device is provided, which has the apparatus for data transmission described in the fourth aspect or the fifth aspect of the embodiments of the present application.
[0017]
According to an eighth aspect of the embodiments of the present application, there is provided a network device having the apparatus for data transmission described in the sixth aspect of the embodiments of the present application.
[0018]
According to a ninth aspect of the embodiments of the present application, a communication system is provided, which includes the terminal device described in the seventh aspect of the embodiments of the present application and the network device described in the eighth aspect.
[0019]
According to a tenth aspect of the embodiments of the present application, a computer-readable program is provided, wherein when the program is executed in an apparatus or terminal device for data transmission, the program causes the apparatus or terminal device for data transmission to execute The data transmission method described in the first aspect or the second aspect of the embodiments of the present application.
[0020]
According to an eleventh aspect of the embodiments of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables a data transmission apparatus or terminal device to execute the first aspect or the terminal device of the embodiments of the present application. The method for data transmission described in the second aspect.
[0021]
According to a twelfth aspect of the embodiments of the present application, a computer-readable program is provided, wherein when the program is executed in a data transmission apparatus or network device, the program causes the data transmission apparatus or network device The method for data transmission described in the third aspect of the embodiments of the present application is performed.
[0022]
According to a thirteenth aspect of the embodiments of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program enables a data transmission apparatus or a network device to execute the third aspect of the embodiments of the present application. method of data transfer.
[0023]
The beneficial effect of the embodiments of the present application is that: whether to send new data or retransmit data on the CG resource is determined according to the status of the timer and/or the Hybrid Automatic Repeat reQuest (HARQ) process. Configure authorized uplink resources to send retransmitted data, thereby improving data transmission efficiency.
[0024]
With reference to the following description and drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application may be employed. It should be understood that the embodiments of the present application are not thereby limited in scope. Embodiments of the present application include numerous changes, modifications and equivalents within the scope of the terms of the appended claims.
[0025]
Features described and/or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, in combination with, or instead of features in other embodiments .
[0026]
It should be emphasized that the term "comprising/comprising" when used herein refers to the presence of a feature, integer, step or component, but does not exclude the presence or addition of one or more other features, integers, steps or components.
Description of drawings
[0027]
Elements and features described in one figure or embodiment of the present application may be combined with elements and features shown in one or more other figures or embodiments. Furthermore, in the figures, like reference numerals refer to corresponding parts throughout the several figures, and may be used to designate corresponding parts that are used in more than one embodiment.
[0028]
The accompanying drawings, which are included to provide a further understanding of the embodiments of the present application, constitute a part of the specification, are used to illustrate the embodiments of the present application, and together with the written description, serve to explain the principles of the present application. Obviously, the drawings in the following description are only some embodiments of the present application, and for those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort. In the attached image:
[0029]
1 is a schematic diagram of a communication system according to an embodiment of the present application;
[0030]
Fig. 2 is a schematic diagram of the data transmission method of the first aspect of the embodiment of the present application;
[0031]
3 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 1 of the first aspect of the embodiments of the present application;
[0032]
4 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 1 of the first aspect of the embodiments of the present application;
[0033]
5 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 2 of the first aspect of the embodiments of the present application;
[0034]
6 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the first aspect of the embodiments of the present application;
[0035]
7 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the first aspect of the embodiments of the present application;
[0036]
8 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the first aspect of the embodiments of the present application;
[0037]
9 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the first aspect of the embodiments of the present application;
[0038]
10 is a schematic diagram of the data transmission method of the second aspect of the embodiment of the present application;
[0039]
11 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 1 of the second aspect of the embodiments of the present application;
[0040]
12 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 1 of the second aspect of the embodiments of the present application;
[0041]
13 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 2 of the second aspect of the embodiments of the present application;
[0042]
14 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the second aspect of the embodiments of the present application;
[0043]
15 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the second aspect of the embodiments of the present application;
[0044]
16 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the second aspect of the embodiments of the present application;
[0045]
17 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the second aspect of the embodiments of the present application;
[0046]
18 is a schematic diagram of a data transmission method according to a third aspect of an embodiment of the present application;
[0047]
19 is a schematic diagram of the apparatus for data transmission according to the fourth aspect of the embodiment of the present application;
[0048]
20 is a schematic diagram of the apparatus for data transmission according to the fifth aspect of the embodiment of the present application;
[0049]
21 is a schematic diagram of the apparatus for data transmission according to the sixth aspect of the embodiment of the present application;
[0050]
22 is a schematic block diagram of a system configuration of a terminal device according to a seventh aspect of an embodiment of the present application;
[0051]
FIG. 23 is a schematic structural diagram of a network device according to an eighth aspect of an embodiment of the present application.
Detailed ways
[0052]
The foregoing and other features of the present application will become apparent from the following description with reference to the accompanying drawings. In the specification and drawings, specific embodiments of the present application are specifically disclosed, which are indicative of some embodiments in which the principles of the present application may be employed, it being understood that the present application is not limited to the described embodiments, on the contrary, the present The application includes all modifications, variations and equivalents falling within the scope of the appended claims. Various embodiments of the present application will be described below with reference to the accompanying drawings. These embodiments are exemplary only, not limiting of the present application.
[0053]
In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements in terms of appellation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted. The term "and/or" includes any and all combinations of one or more of the associated listed items. The terms "comprising", "including", "having", etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
[0054]
In the embodiments of the present application, the singular forms "a", "the", etc. include the plural forms, and should be broadly understood as "a" or "a class" rather than being limited to the meaning of "an"; in addition, the term "the" "" is understood to include both the singular and the plural, unless the context clearly dictates otherwise. In addition, the term "based on" should be understood as "at least in part based on..." and the term "based on" should be understood as "based at least in part on..." unless the context clearly dictates otherwise.
[0055]
In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network conforming to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access) and so on.
[0056]
Moreover, the communication between devices in the communication system can be carried out according to communication protocols at any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other communication protocols currently known or to be developed in the future.
[0057]
In this embodiment of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device. Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateway, server, Radio Network Controller (RNC, Radio Network Controller), Base Station Controller (BSC, Base Station Controller) and so on.
[0058]
The base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femto, pico, etc.). And the term "base station" may include some or all of their functions, each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and/or its coverage area, depending on the context in which the term is used.
[0059]
In the embodiments of this application, the term "User Equipment" (UE, User Equipment) or "Terminal Equipment" (TE, Terminal Equipment), for example, refers to a device that accesses a communication network through a network device and receives network services. User equipment may be fixed or mobile, and may also be referred to as a Mobile Station (MS, Mobile Station), a terminal, a Subscriber Station (SS, Subscriber Station), an Access Terminal (AT, Access Terminal), a station, and the like.
[0060]
Wherein, the user equipment may include, but is not limited to, the following devices: cellular phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
[0061]
For another example, in scenarios such as the Internet of Things (IoT, Internet of Things), the user equipment may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
[0062]
The following describes the scenarios of the embodiments of the present application by using examples, but the present application is not limited thereto.
[0063]
FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application, which schematically illustrates the case of a terminal device and a network device as an example. As shown in FIG. 1 , a communication system 100 may include a network device 101 and a terminal device 102 (for simplicity) For the sake of illustration, FIG. 1 only takes one terminal device as an example).
[0064]
In this embodiment of the present application, an existing service or a service that can be implemented in the future may be performed between the network device 101 and the terminal device 102 . For example, these services include but are not limited to: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra-Reliable and Low-Latency Communication (URLLC) Latency Communication), etc.
[0065]
Wherein, the terminal device 102 may send data to the network device 101, for example, using an authorization-free transmission mode. The network device 101 may receive data sent by one or more terminal devices 102, and feed back information (such as ACK/NACK) information to the terminal device 102, and the terminal device 102 may confirm the end of the transmission process according to the feedback information, or may A new data transmission is made, or a data retransmission can be made.
[0066]
The following description is given by taking the network device in the communication system as the receiving end and the terminal device as the sending end as an example, but the present application is not limited to this, and the sending end and/or the receiving end may also be other devices. For example, the present application is not only applicable to uplink license-free transmission between a network device and a terminal device, but also applicable to side-link license-free transmission between two terminal devices.
[0067]
In various aspects of the following embodiments of the present application, the meaning of starting the first timer is: when the first timer is in a state of stopping running or running overtime, the first timer is started; When in the running state, the first timer is restarted, ie restarted.
[0068]
In various aspects of the following embodiments of the present application, the meaning of starting the second timer is: when the second timer is in a state of stopping running or running overtime, the second timer is started; or, when the second timer When in the running state, the second timer is restarted, ie restarted.
[0069]
In various aspects of the following embodiments of the present application, sending new data on a Configured Grant (CG) resource is determined according to a timer and/or a state of a Hybrid Automatic Repeat reQuest (HARQ) process The data is still retransmitted. Therefore, the retransmitted data can be sent using the configured uplink resources, thereby improving the data transmission efficiency; in addition, the problem that the terminal device is difficult to determine whether to send new data or retransmit data on the CG resource can be avoided.
[0070]
first aspect of the embodiment
[0071]
The first aspect of the embodiments of the present application relates to a data transmission method, which is applied to a terminal device, such as the terminal device 102 .
[0072]
FIG. 2 is a schematic diagram of the data transmission method according to the first aspect of the embodiment of the present application. As shown in FIG. 2 , the data transmission method 200 may include at least one of the following operations 201 and 202:
[0073]
Operation 201: Determine that the process state of the first HARQ process is the second state (ACK), authorize sending new data according to the configuration corresponding to the first hybrid automatic repeat request (HARQ) process, and set the process state corresponding to the first HARQ process is the first state (NACK), and starts the first timer and the second timer;
[0074]
Operation 202: Determine that the process state of the first HARQ process is the first state (NACK) and the second timer is not running, authorize sending retransmission data according to the configuration corresponding to the first HARQ process, and start the second timer.
[0075]
According to the first aspect of the embodiments of the present application, in operation 201 or operation 202, according to the status of the timer and the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process, sending on the configured grant (Configured Grant, CG) resource New data or retransmitted data, thus, the retransmitted data can be sent by using the uplink resources authorized by the configuration, thereby improving the data transmission efficiency; in addition, it can avoid the problem that the terminal device is difficult to determine whether to send new data or retransmitted data on the CG resource .
[0076]
In the first aspect of the embodiment of the present application, the first timer may be a configuration grant (Configured Grant, CG) timer, and the second timer may be a configured grant (Configured Grant, CG) retransmission timer.
[0077]
In the first aspect of the embodiment of the present application, the first HARQ process is an HARQ process configured by the network device for the terminal device and capable of performing uplink configuration authorization transmission; the first HARQ process may correspond to the first timer and the second timer, For example, each first HARQ process can maintain a first timer and a second timer; the first HARQ process corresponds to a process state, for example, each first HARQ process can maintain a process state, the initial process state The value is the second state (ACK).
[0078]
In at least one embodiment, in operation 201 and operation 202, the process state of the first HARQ process may be set to the second state (ACK) if the first timer expires.
[0079]
In at least one embodiment, in operation 202, the fact that the second timer is not running includes: the second timer is not started, the second timer is stopped after timeout, or the terminal device 102 receives the first HARQ corresponding to the first HARQ sent by the network device 101. stop the second timer when the downlink feedback information is received.
[0080]
In at least one embodiment, the length of the second timer may be smaller than the length of the first timer, thereby avoiding the situation that the HARQ process retransmission data can never be sent.
[0081]
In at least one embodiment, in operation 201, the operation of setting the process state corresponding to the first HARQ process to the first state according to the configuration corresponding to the first HARQ process authorizes to send new data, for example, may be: determining the first HARQ process The state of the New Data Indication (NDI) of the process is flipped, a new data transport block of the first HARQ process is generated at the medium access control (MAC) layer, and the state corresponding to the first HARQ process is set to the first state (NACK), and send the new data transport block.
[0082]
In at least one embodiment, in operation 201, start the second timer and start the operation of the first timer, for example, it may be determined that the new data is successfully sent, then start the second timer and start the first timer device.
[0083]
In at least one embodiment, in operation 202, the transmission of retransmission data is authorized according to the configuration corresponding to the first HARQ process. For example, it may be determined that there is a transport block in the buffer of the first HARQ process, and the buffer of the first HARQ process is sent. in the transport block. In addition, the retransmission data may be sent when it is determined that the state of the New Data Indication (NDI) of the first HARQ process is not inverted.
[0084]
In at least one embodiment, in operation 202, the retransmission data is authorized to be sent according to the configuration corresponding to the first HARQ process, and the operation of starting the second timer, for example, may be: determining a new data indication (New data indication) of the first HARQ process. The state of the Data Indication, NDI) is not flipped, then retransmission data is sent, it is determined that the retransmission data is successfully sent, and a second timer is started.
[0085]
In at least one embodiment, as shown in FIG. 2 , operation 202 may further include the following operation: it is determined that the retransmission data is successfully sent for the first time, and a first timer is started. Thus, in operation 202, in a case where it is determined that the retransmission data is successfully transmitted for the first time, both the second timer and the first timer are started.
[0086]
In at least one embodiment, in addition to sending the HARQ data transmitted by the CG on the CG resource, the terminal device 101 can also actively schedule new data or retransmission data of the CG HARQ process, that is, the terminal device can The dynamically scheduled uplink resources send CG HARQ process data.
[0087]
In order to avoid that the terminal device 102 sends data of the same HARQ process on the CG resource while the network device 101 dynamically schedules the CG HARQ process, which may cause confusion in HARQ process management, in at least one embodiment, after the network device 101 dynamically schedules the CG HARQ process, the terminal The device 102 cannot send the data of the HARQ process on the CG resource, and cannot send the new data of the HARQ process on the CG resource, that is, after determining that there is no dynamic authorization corresponding to the HARQ process to send data, and has not received the network device 101 Under the premise of the sent command to dynamically authorize the HARQ process to send data, the terminal device 102 may send new data or retransmit data on the CG resource corresponding to HARQ (unless the process status is ACK). Therefore, after the network device 101 dynamically schedules the CG HARQ process, the terminal device 102 does not start the HARQ CG retransmission timer.
[0088]
For example, in operations 201 and 202, according to the configuration corresponding to the first HARQ process, the authorization to send new data or the retransmission of data has the following premise: it is determined that there is no dynamic authorization to send data corresponding to the first HARQ process, and there is no dynamic authorization to send data in the first HARQ process. A command to dynamically authorize the first HARQ process to send data sent by the network device 101 is received.
[0089]
In at least one embodiment, as shown in FIG. 2, the data transmission method 200 further includes:
[0090]
Operation 203: Stop the second timer when receiving downlink feedback information (Downlink Feedback Information, DFI) sent by the network device 101 indicating that the network device 101 fails to receive the first HARQ process data; or
[0091]
Operation 204: Stop the first timer when the downlink feedback information (DFI) sent by the network device 101 indicates that the network device 101 has correctly received the first HARQ process data.
[0092]
In operation 203, when the DFI indicates that the network device 101 fails to receive the first HARQ process data, the DFI may be, for example, HARQ-NACK information.
[0093]
In operation 204, when the DFI indicates that the first HARQ process data is correctly received by the network device 101, the DFI may be, for example, HARQ-ACK information.
[0094]
Through the above operation 203 or operation 204, the terminal device 102 can stop the corresponding timer in time according to the downlink feedback information sent by the network device 102, so that the data can be re-restored before the first timer or the second timer times out. transmission or new transmission, thereby reducing the delay of data transmission.
[0095]
In at least one embodiment, as shown in FIG. 2 , operation 203 may further include the following operation: setting the process state of the first HARQ process to the first state (NACK). Operation 204 may further include the following operation: setting the process state of the first HARQ process to the second state (ACK). Therefore, the process state of the first HARQ process can be set in time according to the downlink feedback information in operations 203 and 204, so as to facilitate the next data transmission in time, thereby reducing the delay of data transmission.
[0096]
In at least one embodiment, as shown in FIG. 2 , the method 200 for data transmission may further include one of the following operations 205 and 206:
[0097]
Operation 205, after sending new data according to the dynamic authorization corresponding to the first HARQ process, start a first timer;
[0098]
In operation 206, a command for dynamically authorizing the first HARQ process to send new data sent by the network device 101 is received, and a first timer is started.
[0099]
According to operation 205 or operation 206, in the case that the network device dynamically schedules the CG HARQ process to transmit new data, the first timer can also be started at an appropriate timing.
[0100]
In at least one embodiment, in operation 205, after sending new data according to the dynamic authorization corresponding to the first HARQ process, the step of starting the first timer may, for example, include: sending new data according to the dynamic authorization corresponding to the first HARQ process, In a case where it is determined that the new data has been successfully transmitted, a first timer is started.
[0101]
In at least one embodiment, as shown in FIG. 2 , the method 200 for data transmission may further include one of the following operations 207 and 208:
[0102]
Operation 207: Start the first timer after sending the retransmission data according to the dynamic authorization corresponding to the first HARQ process;
[0103]
In operation 208, a command for dynamically authorizing the first HARQ process to send retransmission data sent by the network device 101 is received, and a first timer is started.
[0104]
According to operation 207 or operation 208, in the case that the network device dynamically schedules the CG HARQ process to transmit retransmission data, the first timer can also be started at an appropriate timing.
[0105]
In at least one embodiment, in operation 207, after sending new data according to the dynamic authorization corresponding to the first HARQ process, the step of starting the first timer may include, for example: sending retransmission data according to the dynamic authorization corresponding to the first HARQ process , and in the case that it is determined that the retransmission data is successfully sent, the first timer is started.
[0106]
In at least one embodiment, as shown in FIG. 2 , the method 200 for data transmission may further include:
[0107]
Operation 209: Send uplink control information (Uplink Control Information, UCI) for indicating the configuration grant information of the first HARQ process to the network device 101 .
[0108]
In operation 209, the uplink control information (UCI) may include: a network identifier of the terminal device 102, for example, a Cell-Radio Network Temporary Identifier (C-RNTI) of the terminal device 102 or a configuration scheduling radio network temporary identifier Identifier (Configured Scheduling-Radio Network Temporary Identifier, CS-RNTI), wherein the C-RNTI or CS-RNTI may be 16 bits (bits).
[0109]
In at least one embodiment, the network identification of the terminal device 102 in the uplink control information (UCI) may indicate to the network device 101 that the configuration grant data is the new data or retransmission data of the first HARQ process, for example, the The C-RNTI may be used to indicate new data of the first HARQ process, and the CS-RNTI of the terminal device 102 may be used to indicate retransmission data of the first HARQ process.
[0110]
In operation 209, the uplink control information (UCI) may further include: information of New Data Indication (NDI) of the first HARQ process.
[0111]
In at least one embodiment, the configuration grant data may be indicated as new data or retransmission of the first HARQ process through the information of New Data Indication (NDI) of the first HARQ process in the uplink control information (UCI). data, for example, if the new data indication (NDI) is the same as the new data indication (NDI) of the previous HARQ process, that is, the new data indication (NDI) is not inverted, indicating that the configuration grant data is the retransmission data of the first HARQ process, If the new data indication (NDI) is different from the new data indication (NDI) of the previous HARQ process, that is, the new data indication (NDI) is reversed, it means that the configuration grant data is the new data of the first HARQ process.
[0112]
In at least one embodiment, the uplink control information (UCI) in operation 209 may further include: a process identifier of the first HARQ process, for example, a process ID (HARQ ID) of the first HARQ process; and, the first HARQ process Redundancy version (RV) information for transport blocks.
[0113]
In at least one embodiment, in operation 209, when the configuration authorization data of the first HARQ process is never successfully sent, the UCI indicates that the configuration authorization data is new data, otherwise, the UCI indicates that the configuration authorization data is retransmission data.
[0114]
In at least one embodiment, as shown in FIG. 2 , the method 200 for data transmission further includes:
[0115]
Operation 210: Receive downlink control information (DCI) sent by the network device for dynamically authorizing the first HARQ process.
[0116]
In operation 210, downlink control information (DCI) includes a process ID (HARQ ID) of the first HARQ process and redundancy version (RV) information of a transport block of the first HARQ process, wherein the downlink control information (DCI) can be used with The network identifier of the terminal device 102 is scrambled, and the network identifier of the terminal device 102 is, for example, C-RNTI or CS-RNTI.
[0117]
In at least one embodiment, the network identifier of the terminal device 102 in the downlink control information (DCI) may be used to indicate that the dynamically authorized data is the new data or retransmission data of the first HARQ process, for example, the C- The RNTI may be used to indicate the new data of the first HARQ process, and the CS-RNTI of the terminal device 102 may be used to indicate the retransmission data of the first HARQ process.
[0118]
In at least one embodiment, the downlink control information (DCI) further includes new data indication (NDI, new data indication) information of the first HARQ process. Wherein, the new data indication information in the downlink control information (DCI) is used to indicate that the dynamically authorized data of the terminal device 102 is the new data or retransmission data of the first HARQ process, for example, if the new data in the downlink control information (DCI) The data indication (NDI) is the same as the new data indication (NDI) of the previous HARQ process, that is, the new data indication (NDI) is not reversed, indicating that the dynamic grant data is the retransmission data of the first HARQ process, if the new data indication (NDI) ) is different from the new data indication (NDI) of the previous HARQ process, that is, the new data indication (NDI) is inverted, indicating that the dynamic grant data is the new data of the first HARQ process.
[0119]
In at least one embodiment, as shown in FIG. 2 , the method 200 for data transmission further includes:
[0120]
Operation 211: Receive configuration grant (CG) resource configuration information sent by the network device 101, and the configuration grant resource configuration information is used to configure the configuration grant uplink resource location used by the terminal device 102 and configure the process number of the first HARQ process.
[0121]
In operation 211, the CG resource configuration information may include: a period for configuring the authorized uplink resources; a duration for configuring the authorized uplink resources; and, configuring an offset of the authorized uplink resources within the period. For example, the period, duration and offset are in units of Orthogonal Frequency Division Multiplexing (OFDM) symbols, slots or subframes, for example.
[0122]
The terminal device 102 may send data on the periodically occurring CG (configured grant) uplink resource without receiving the PDCCH signaling sent by the network device 101 in advance. Send new data or retransmit data on the uplink resources authorized by the corresponding configuration.
[0123]
According to the first aspect of the embodiments of the present application, in operation 201 or operation 202, according to the status of the timer and the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) process, sending on the configured grant (Configured Grant, CG) resource New data or retransmitted data, thus, the retransmitted data can be sent by using the uplink resources authorized by the configuration, thereby improving the data transmission efficiency; in addition, it can avoid the problem that the terminal device is difficult to determine whether to send new data or retransmitted data on the CG resource .
[0124]
In addition, according to the first aspect of the embodiments of the present application, in the case where the terminal device 102 operates in an unlicensed frequency band, if the physical layer successfully performs Listen Before Talk (LBT), the terminal device 102 can send data. The layer fails to perform LBT, and the terminal device 102 cannot send data. In the case of LBT failure, although the MAC layer of the terminal device 102 has generated the data of the first HARQ process, the data of the first HARQ process still exists in the HARQ data cache .
[0125]
In the case of physical layer LBT failure, since the data is not actually sent, neither the first timer nor the second timer is started; the MAC layer HARQ process of the terminal device 102 requests to send new data or retransmission on the CG resource After the data, the second timer is started only when the physical layer LBT is successful (ie, after the data is successfully sent), and after the terminal device 102 successfully sends new data on the CG resource (ie, the HARQ data is successfully sent for the first time) time), the first timer is started. The terminal device 102 starts the first timer only after successfully sending new data or retransmitting data on the uplink resource of the HARQ process dynamically scheduled by the network device. In addition, if sending HARQ data on the CG resource fails (ie, LBT fails), continue sending on the next CG resource, and the uplink control information (UCI) transmitted with the data can be the same as the data transmission when the last LBT failed. UCI or different UCI, eg same RV or different RV from last data transfer.
[0126]
In addition, after the MAC layer of the terminal device 102 sends new data in the HARQ process, regardless of whether the physical layer LBT is successful, the first HARQ process state is set to the first state (NACK), thereby preventing successful transmission in the physical layer. Before the HARQ data, the HARQ entity of the MAC layer requests to send a new data on the CG resource, overwriting the data in the original HARQ cache that was not successfully sent due to LBT failure.
[0127]
It is worth noting that the above FIG. 2 only schematically illustrates the first aspect of the embodiment of the present application, but the present application is not limited thereto. For example, the execution order of the various operations can be adjusted appropriately, and other operations can be added or some of the operations can be reduced. Those skilled in the art can make appropriate modifications according to the above content, and are not limited to the description of the above-mentioned FIG. 2 .
[0128]
The above embodiments merely illustrate the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can also be made on the basis of the above embodiments. For example, each of the above-described embodiments may be used alone, or one or more of the above-described embodiments may be combined.
[0129]
Hereinafter, the first aspect of the embodiments of the present application will be exemplarily described by taking several specific implementation manners as examples. In the following specific implementation manners: the HARQ process is the first HARQ process, and each HARQ process maintains a first timer and a second timer, wherein the first timer is, for example, a CG timer, and the second timer is, for example, a CG Retransmission timer; the first state of the HARQ process is the NACK state, and the second state of the HARQ process is the ACK state.
[0130]
Embodiment 1
[0131]
In this embodiment, after the new data of the HARQ process is sent on the CG resource, the CG timer is started, thereby preventing the terminal device from not receiving the downlink feedback information (DFI) sent by the network device after sending the new data on the CG resource. and cannot send new data.
[0132]
The terminal device 101 starts the CG retransmission timer after sending the new data or retransmission data of the HARQ process on the CG resource.
[0133]
The terminal device 101 performs the following operations:
[0134]
For each periodically occurring CG resource,
[0135]
When the CG retransmission timer of the HARQ process is not running and the process status of the HARQ process is NACK, the terminal device 102 sends the retransmission data of the HARQ process on the CG resource, and starts the CG retransmission timer;
[0136]
When the process status of the HARQ process is ACK, the terminal device 102 sends the newly transmitted data of the HARQ process on the CG resource, sets the process status of the HARQ process to NACK, and starts the CG timer and the CG retransmission timer.
[0137]
When the CG timer of the HARQ process expires, the terminal device 102 sets the process status of the HARQ process to ACK.
[0138]
The UCI transmitted with the data on the CG resource can indicate the HARQ process information to the network device 101. The UCI contains the HARQ process identifier, the network identifier of the terminal device, and the redundancy version (RV) information of the HARQ process transport block. The UCI can be used for Indicates to the network device 101 whether the data is new data or retransmission data of the HARQ process.
[0139]
After receiving the HARQ data sent by the terminal device 102 on the CG resource, the network device 101 sends downlink feedback information (Downlink Feedback Information) to the terminal device 102 to indicate whether the HARQ data is correctly received by the network device 101. For example, the feedback information is HARQ-ACK indicates that the HARQ data is correctly received by the network device 101 , and the feedback information is HARQ-NACK indicates that the HARQ data is not correctly received by the network device 101 .
[0140]
If the terminal device 102 receives the HARQ-NACK, the terminal device 102 can stop the CG retransmission timer that the HARQ process is running, and can also set the process status of the HARQ process to NACK; if the terminal device receives the HARQ-ACK, The terminal device sets the process status to ACK and stops the running CG timer of the HARQ process.
[0141]
FIG. 3 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 1 of the first aspect of the embodiments of the present application.
[0142]
As shown in FIG. 3 , after the terminal device 102 sends the new data of the HARQ process on the CG resource 301, the process state is set to the NACK state. For example, if a HARQ new data transmission is triggered, the MAC layer of the terminal device 102 sets the state of the HARQ process to the NACK state.
[0143]
As shown in FIG. 3 , after the terminal device 102 sends new HARQ data on the CG resource, it starts the CG timer and the CG retransmission timer. On the first CG resource 302 after sending new data, the CG retransmission timer of the HARQ process is not running (has expired) and the state is NACK, so the terminal device can initiate HARQ data retransmission, and start CG after data retransmission Retransmission timer.
[0144]
As shown in FIG. 3 , after sending the retransmitted data, the terminal device 102 receives the HARQ-NACK feedback from the network device 101 for the retransmitted data, and the terminal device stops the CG retransmission timer. In addition, the HARQ state can also be set to the NACK state. . On the second CG resource 303 for sending new data, the CG retransmission timer of the HARQ process is not running (stopped) and the state of the HARQ process is NACK state, so the terminal device can initiate HARQ data retransmission and start CG retransmission timer. After the second retransmission data is sent, the CG timer expires, and the terminal device sets the HARQ state to the ACK state.
[0145]
As shown in FIG. 3 , on the third CG resource 304 after sending the new data, the state of the HARQ process is ACK, so the terminal device can initiate HARQ new data transmission.
[0146]
In this embodiment, if the HARQ data fails to be sent on the CG resource (for example, the LBT fails), the HARQ data will continue to be sent on the next CG resource, and the UCI transmitted with the data can be the same as the data when the LBT failed last time. The same UCI or a different UCI is transmitted, eg, the same RV or a different RV from the last data transmission. If a transport block has never been successfully sent, the UCI transmitted with the transport block indicates that the transport block is new data. After a transport block is successfully sent, the CG retransmission timer is started; if it is the first time that a transport block is successfully sent, the CG timer is started in addition to the CG retransmission timer.
[0147]
FIG. 4 is another schematic diagram of the process state of the timer and the HARQ process in Embodiment 1 of the first aspect of the embodiment of the present application. FIG. 4 illustrates that when the MAC layer generates a new transport block, regardless of whether the physical layer LBT is successful or not, the The status of the HARQ process is set to NACK to prevent the MAC layer HARQ entity from requesting to send a new data on the CG resource before the HARQ data is successfully sent, overwriting the data in the original HARQ cache that was not successfully sent due to LBT failure.
[0148]
As shown in FIG. 4 , on the CG resource 401 , after the MAC layer HARQ entity of the terminal device 102 triggers the new data transmission of the HARQ process, the process state of the HARQ process is set to the NACK state. In the case of physical layer LBT failure, the new HARQ data is stored in the HARQ transmission buffer, and the CG timer and CG retransmission timer are not started at this time.
[0149]
On the next CG resource 402, since the CG retransmission timer of the HARQ process is not running (not started) and the process state of the HARQ process is the NACK state, the terminal device 102 can initiate HARQ data retransmission, and the physical layer LBT is successful. After completing the data transmission on the CG resource, start the CG retransmission timer; since this transmission block is successfully transmitted for the first time, the terminal device 102 also needs to start the CG timer; because the previous transmission of the data has never been successful (due to LBT failure), The UCI transmitted with the data indicates that the data is a new HARQ process transport block.
[0150]
As shown in Figure 4, the CG retransmission timer expires, the HARQ process status is NACK on the next CG resource 403 and the CG retransmission timer is not running (has expired), the terminal device can trigger data retransmission, but HARQ is caused by LBT failure. If data retransmission fails, the CG retransmission timer is not started at this time. On the next CG resource 404, the retransmission data is successfully sent, and the CG retransmission timer is started.
[0151]
As shown in FIG. 4 , when the CG timer expires, the terminal device sets the HARQ state to the ACK state. On the first CG resource 405 after that, the state of the HARQ process is ACK, so the terminal device can initiate HARQ new data transmission. Similar operation: on the CG resource 405, the MAC layer HARQ entity of the terminal device triggers the new data transmission of the HARQ process, and sets the process state to the NACK state, but the physical layer LBT fails during transmission, and the new HARQ data is stored in the HARQ transmission buffer. At this time, the CG timer and CG retransmission timer are not started; on the next CG resource 406, the CG retransmission timer of the HARQ process is not running (not started) and the state is NACK state, so the terminal device can initiate HARQ data retransmission If the physical layer LBT is successful, the CG retransmission timer is started after the data transmission is completed on the CG resource; since this transmission block is the first successful transmission, the terminal device 102 also needs to start the CG timer; Unsuccessful (LBT failure), the UCI transmitted with the data indicates that the data is a new HARQ process transport block.
[0152]
Embodiment 2
[0153]
In this embodiment, after the new data of the HARQ process is sent on the CG resource, the CG timer is started, thereby preventing the terminal device from not receiving the downlink feedback information (DFI) sent by the network device after sending the new data on the CG resource. and cannot send new data. In this embodiment, after the terminal device 102 sends data on the uplink resource on which the network device 101 dynamically schedules the HARQ process, the CG timer is not started.
[0154]
In this embodiment, the terminal device 102 starts the CG retransmission timer after sending new HARQ process data or retransmission data on the CG resource.
[0155]
The terminal device 102 has the following operations: for each periodically occurring CG resource, when the CG retransmission timer of the HARQ process is not running and the HARQ process status is NACK, the terminal device 102 sends a retransmission of the HARQ process on the CG resource data, start the CG retransmission timer;
[0156]
When the state of the HARQ process is ACK, the terminal device 102 sends the newly transmitted data of the HARQ process on the CG resource, sets the process state to ACK, and starts the CG timer and the CG retransmission timer.
[0157]
When the CG timer of the HARQ process expires, the terminal device 102 sets the state of the process to ACK.
[0158]
After receiving the HARQ data sent by the terminal device 102 on the CG resource, the network device 101 can send downlink feedback information (Downlink Feedback Information) to the terminal device 102, including HARQ-ACK or HARQ-NACK information, to indicate whether the HARQ data is The network device 101 receives it correctly.
[0159]
If the terminal device 102 receives the HARQ-NACK, the terminal device 102 can stop the CG retransmission timer that the HARQ process is running, and can also set the process state to NACK; if the terminal device 102 receives the HARQ-ACK, the terminal device 102 sets the process status to ACK and stops the running CG timer of the HARQ process.
[0160]
FIG. 5 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 2 of the first aspect of the embodiments of the present application.
[0161]
As shown in the figure, after the terminal device 102 sends the new data of the HARQ process on the CG resource 601, the process state of the HARQ process is set to the NACK state, and the CG timer and the CG retransmission timer are started.
[0162]
On the first CG resource 602 after sending new data, the CG retransmission timer of the HARQ process is not running (has timed out) and the process state of the HARQ process is in the NACK state, so the terminal device 102 can initiate HARQ data retransmission, the data Start the CG retransmission timer after retransmission. After sending the retransmitted data, the terminal device 102 receives the HARQ-NACK feedback from the network device 101 for the retransmitted data, and the terminal device 102 stops the CG retransmission timer (or may also set the HARQ state to the NACK state).
[0163]
On the second CG resource 603 after sending new data, the CG retransmission timer of the HARQ process is not running (stopped) and the process state of the HARQ process is NACK state, so the terminal device 102 can initiate HARQ data retransmission again , start the CG retransmission timer. After the second retransmission data is sent on the CG resource 603 , the terminal device 102 receives the dynamic scheduling command for the HARQ process sent by the network device 101 , and the dynamic scheduling command instructs the terminal device 102 to send the HARQ retransmission on the uplink resource 604 data.
[0164]
After the dynamically scheduled HARQ retransmission data is sent on resource 604, for CG resource 605, although the CG retransmission timer is not running (timed out) and the HARQ status is NACK, in order to avoid HARQ process management confusion, the terminal device 102 cannot The retransmission data is sent on the CG resource 605 .
[0165]
As shown in FIG. 5, after the dynamically scheduled HARQ retransmission data is sent on resource 604, the terminal device 102 does not receive the HARQ-ACK feedback sent by the network device 101 until the CG timer expires and the HARQ process state is set to ACK. On the first CG resource 606 after the CG timer expires, the terminal device 102 may initiate new data transmission, start the CG timer and the CG retransmission timer, and set the process state of the HARQ process to NACK.
[0166]
Embodiment 3
[0167]
In Embodiment 3, after the terminal device 102 sends the new data of the HARQ process on the CG resource, the CG timer is started, and when the terminal device 102 sends the new data on the uplink resource of the HARQ process dynamically scheduled by the network device 101 or receives The CG timer is also started when the network device 101 is instructed to dynamically schedule new data of the HARQ process. In this way, it can not only prevent the terminal device 102 from sending new data on the CG resource, but not receive the downlink feedback information (DFI) sent by the network device 101 and thus cannot send new data, but also prevent the network device 101 from dynamically scheduling the terminal. After the CG HARQ process of the device 102, the terminal device 102 cannot receive the ACK feedback from the network device 101 and can never send new data.
[0168]
In this embodiment, the terminal device 102 starts the CG retransmission timer after sending new HARQ process data or retransmission data on the CG resource.
[0169]
In this embodiment, the terminal device 102 may perform the following operations:
[0170]
For each periodically occurring CG resource, when the CG retransmission timer of the HARQ process is not running and the HARQ process status is NACK, the terminal device 102 sends the retransmission data of the HARQ process on the CG resource, and starts the CG retransmission timing. device;
[0171]
When the state of the HARQ process is ACK, the terminal device 102 sends the newly transmitted data of the HARQ process on the CG resource, sets the process state to NACK, and starts the CG timer and the CG retransmission timer;
[0172]
When the CG timer of the HARQ process expires, the terminal device 102 sets the state of the process to ACK.
[0173]
After receiving the HARQ data sent by the terminal device 102 on the CG resource, the network device 101 can send downlink feedback information (Downlink Feedback Information) to the terminal device 102, including HARQ-ACK/HARQ-NACK information, to indicate whether the HARQ data is The network device 101 receives it correctly. If the terminal device 102 receives the HARQ-NACK, the terminal device 102 can stop the CG retransmission timer that the HARQ process is running, and can also set the process state to NACK; if the terminal device 102 receives the HARQ-ACK, the terminal device 102 sets the process status to ACK and stops the running CG timer of the HARQ process.
[0174]
FIG. 6 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the first aspect of the embodiments of the present application.
[0175]
As shown in FIG. 6 , after sending the new data of the HARQ process on the CG resource 701, the terminal device 102 sets the process state of the HARQ process to the NACK state, and starts the CG timer and the CG retransmission timer.
[0176]
When the terminal device 102 receives the HARQ-NACK feedback for the retransmitted data from the network device 101, the terminal device 102 stops the CG retransmission timer, and can also set the HARQ state to the NACK state.
[0177]
As shown in FIG. 6 , on the first CG resource 702 after sending new data, the CG retransmission timer of the HARQ process is not running (stopped) and the process state of the HARQ process is NACK state, so the terminal device 102 can initiate The HARQ data is retransmitted, and the CG retransmission timer is started after the data is retransmitted. On the CG resource 702 described in FIG. 6, retransmission data can still be sent even if the CG timer is running.
[0178]
After the retransmission data is sent on the CG resource 702, the terminal device 102 receives the dynamic scheduling command for the HARQ process sent by the network device 101, and instructs the terminal device 102 to send new HARQ data. The terminal device 102 restarts the CG timer after sending the dynamically scheduled new data on the uplink resource 703 .
[0179]
As shown in FIG. 6 , the terminal device 102 does not start the CG retransmission timer after sending the dynamically scheduled new data on the uplink resource 703 . As shown in FIG. 6 , the terminal device 102 does not stop the CG retransmission timer after sending the dynamically scheduled new data on the uplink resource 703 , but this embodiment may not be limited to this. For example, the terminal device 102 sends the dynamic schedule on the uplink resource 703 . The CG retransmission timer may be stopped after new data is scheduled.
[0180]
In addition, as shown in FIG. 6 , after the terminal device 102 sends the dynamically scheduled new data on the uplink resource 703, the terminal device 102 receives the dynamic scheduling command for the HARQ process sent by the network device 101, and instructs the terminal device 102 to send the HARQ reconfiguration command. transmit data. Terminal device 102 sends dynamically scheduled retransmission data on uplink resource 705 .
[0181]
On the 2 CG resources 704 and 706 after the dynamically scheduled HARQ new data is sent, although the CG retransmission timer is not running (timed out) and the process status of the HARQ process is NACK, in order to avoid confusion in HARQ process management, the terminal device 102 Cannot send retransmission data. When the terminal device 102 receives the HARQ-ACK feedback sent by the network device 101, it sets the HARQ process state to ACK and stops the CG timer of the HARQ process.
[0182]
On the first CG resource 707 after the process state is set to ACK, the terminal device 102 may initiate new data transmission, start the CG timer and the CG retransmission timer, and set the process state of the HARQ process to NACK.
[0183]
FIG. 7 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 3 of the first aspect of the embodiments of the present application.
[0184]
As shown in FIG. 7 , in order that the HARQ transmission of the CG does not conflict with the HARQ scheduled by the network device 101, the terminal device 102 cannot send the retransmission data of the HARQ process indicated by the dynamic scheduling after receiving the dynamic scheduling command from the network device 101, for example , the retransmission data of the HARQ process indicated by the dynamic scheduling is not sent on the CG resources 803 and 805 .
[0185]
As shown in FIG. 7 , when the terminal device 102 receives the command from the network device 101 to dynamically schedule the new data of the HARQ process, it starts the CG timer to prevent the terminal device 102 from sending the CG resource between the dynamic scheduling command and the dynamically scheduled uplink resource. retransmission data.
[0186]
As shown in FIG. 7 , for each periodically occurring CG resource, when the CG retransmission timer of the HARQ process is not running, the CG timer is not running, and the dynamic scheduling command from the network device 101 is not received, the terminal device 102 Only retransmission data or new data of the HARQ process can be sent on CG resources (eg, CG resources 801, 806).
[0187]
Embodiment 4
[0188]
In Embodiment 4, after the terminal device 102 sends the new data of the HARQ process on the CG resource, the CG timer is started, and when the terminal device 102 sends the data (including the new data) on the uplink resource of the HARQ process dynamically scheduled by the network device 101 The CG timer is also started after receiving a command from the network device 101 to dynamically schedule HARQ process data (including new data and retransmitted data).
[0189]
In this way, it can not only prevent the terminal device 102 from sending new data on the CG resource, but not receive the downlink feedback information (DFI) sent by the network device 101 and thus cannot send new data, but also prevent the network device 101 from dynamically scheduling the terminal. After the CG HARQ process of the device 102, the terminal device 102 cannot receive the ACK feedback from the network device 101 and can never send new data. Furthermore, for each dynamically scheduled transmission, the terminal device 102 can have the same maximum ACK feedback latency and support multiple actively scheduled retransmissions by the network device.
[0190]
In this embodiment, in order to avoid conflict between the HARQ transmission of the CG and the HARQ scheduled by the network device 101, the terminal device 102 cannot send the retransmission data of the HARQ process indicated by the dynamic scheduling after receiving the dynamic scheduling command from the network device 101. When the terminal device 102 sends data (including new data and retransmission data) on the uplink resources where the network device 101 dynamically schedules the HARQ process, or receives a command from the network device 101 to dynamically schedule the HARQ process data (including new data and retransmission data) When the CG timer is started, the terminal device 102 is prevented from sending retransmission data on the CG resource between the dynamic scheduling command and the dynamically scheduled uplink resource. For each periodically occurring CG resource, when the CG retransmission timer of the HARQ process is not running, the CG timer is not running, and the dynamic scheduling command from the network device 101 has not been received, the terminal device 102 can send on the CG resource. Retransmission data for the HARQ process.
[0191]
FIG. 8 is a schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the first aspect of the embodiments of the present application.
[0192]
The difference between FIG. 8 and FIG. 6 is that in FIG. 6, the terminal device 102 does not start the CG timer after sending the retransmission data on the uplink resource 705 of the HARQ process dynamically scheduled by the network device 101; while in FIG. 8, the terminal device 102 does not start the CG timer. The device 102 starts the CG timer after sending the retransmission data on the uplink resource 905 where the network device 101 dynamically schedules the HARQ process. In addition, in FIG. 6 and FIG. 8 , after the terminal device 102 sends new data on the uplink resource 703 or 903 in which the network device 101 dynamically schedules the HARQ process, both start the CG timer.
[0193]
FIG. 9 is another schematic diagram of a timer and a process state of a HARQ process in Embodiment 4 of the first aspect of the embodiments of the present application.
[0194]
The difference between FIG. 9 and FIG. 7 is that the terminal device 102 starts the CG timer when receiving the command from the network device 101 to dynamically schedule the newly transmitted data of the HARQ process. For example, in FIG. 7 , before the CG resource 803 When receiving the command from the network device 101 to dynamically schedule the newly transmitted data of the HARQ process shown in Figure 9, the CG timer is started; in FIG. , start the CG timer.
[0195]
In addition, in FIG. 9 , the terminal device 102 starts a CG timer when receiving a command from the network device 101 to dynamically schedule the HARQ process to retransmit data (eg, before the CG resource 1004 in FIG. 9 ).
[0196]
second aspect of the embodiment
[0197]
The second aspect of the embodiments of the present application relates to a data transmission method, which is applied to a terminal device, such as the terminal device 102 .
[0198]
FIG. 10 is a schematic diagram of the data transmission method according to the second aspect of the embodiment of the present application. As shown in FIG. 10 , the data transmission method 1100 may include at least one of the following operations 1101 and 1102:
[0199]
Operation 1101: Determine that the first timer is running and the second timer is not running, authorize sending retransmission data according to the configuration corresponding to the first hybrid automatic repeat request (HARQ) process, and start the second timer;
[0200]
Operation 1102: Determine that the first timer is not running, authorize sending new data according to the configuration corresponding to the first HARQ process, and start the first timer and the second timer.
[0201]
According to the second aspect of the embodiment of the present application, in operation 1101 or operation 1102, according to the running states of the two timers, new data or retransmission data is sent on the Configured Grant (CG) resource, so that it is possible to The retransmission data is sent by using the configured and authorized uplink resources, thereby improving the data transmission efficiency; in addition, the problem that it is difficult for the terminal device to determine whether to send new data or retransmit data on the CG resource can be avoided.
claims
[Claim 1]
An apparatus for data transmission, set in a terminal device, the apparatus includes a first sending unit, the first sending unit: determining that a process state of a first hybrid automatic repeat request (HARQ) process is a second state (ACK) , according to the configuration authorization corresponding to the first HARQ process to send new data, set the process state corresponding to the first HARQ process to the first state (NACK), and start the first timer and the second timer; or, Determine that the process state of the first HARQ process is the first state (NACK) and the second timer is not running, authorize sending retransmission data according to the configuration corresponding to the first HARQ process, and start the second HARQ process timer.
[Claim 2]
The apparatus of claim 1, wherein the first sending unit further: sets the process state to a second state (ACK) when the first timer expires.
[Claim 3]
The apparatus according to claim 1, wherein the first sending unit further: when receiving downlink feedback information sent by the network device indicating that the network device fails to receive the first HARQ process data, stop the a second timer; or stop the first timer when receiving the downlink feedback information sent by the network device indicating that the network device has correctly received the first HARQ process data.
[Claim 4]
The apparatus for data transmission according to claim 1, wherein it is determined that there is no dynamic authorization to send data corresponding to the first HARQ process, or that the first HARQ process does not receive a dynamic authorization to send data sent by the network device command, the first sending unit authorizes sending new data or retransmitting data according to the configuration corresponding to the first HARQ process.
[Claim 5]
The apparatus for data transmission according to claim 1, wherein, according to the configuration authorization corresponding to the first HARQ process to send new data, and setting the process state corresponding to the first HARQ process to the first state, comprising: determining The NDI state of the first HARQ process is inverted, a new data transport block of the first HARQ process is generated at the medium access control (MAC) layer, and the state corresponding to the first HARQ process is set to the first state, and send the new data transport block.
[Claim 6]
The apparatus for data transmission according to claim 1, wherein starting the second timer and starting the first timer comprises: determining that the new data is successfully sent, starting the second timer, and starting the first timer a timer.
[Claim 7]
The apparatus according to claim 1, wherein the first sending unit further: starts the first timer after sending new data according to the dynamic authorization corresponding to the first HARQ process; or, receives the network When the device sends a command to dynamically authorize the first HARQ process to send new data, the first timer is started.
[Claim 8]
The apparatus for data transmission according to claim 1, wherein the first sending unit further: sends, to the network device, uplink control information (UCI) for indicating configuration grant information of the first HARQ process, wherein , the UCI includes the process identifier of the first HARQ process, the network identifier of the terminal device, and the redundancy version (RV) information of the transport block of the first HARQ process.
[claim 9]
The apparatus for data transmission according to claim 8, wherein, when the configuration authorization data is never successfully sent, the UCI indicates that the configuration authorization data is new data; otherwise, the UCI indicates the configuration authorization data to retransmit data.
[claim 10]
The apparatus according to claim 8, wherein the configuration authorization data is indicated to the network device through the network identifier of the terminal device in the UCI as new data or retransmission data of the first HARQ process.
[claim 11]
An apparatus for data transmission, set in a terminal device, the apparatus includes a second sending unit, the second sending unit: determining that the first timer is running and the second timer is not running, according to the mixed automatic retransmission with the first requesting the configuration corresponding to the (HARQ) process to authorize sending retransmission data, and starting the second timer; or, determining that the first timer is not running, and authorizing sending new data according to the configuration corresponding to the first HARQ process, The first timer and the second timer are started.
[claim 12]
The apparatus according to claim 11, wherein the second sending unit further: stops the second timer when receiving downlink feedback information sent by the network device indicating that the network device fails to receive the first HARQ process data or, when receiving downlink feedback information sent by a network device indicating that the network device has correctly received the first HARQ process data, stop the first timer.
[claim 13]
The apparatus for data transmission according to claim 11, wherein the second sending unit further: determines that there is no dynamic authorization corresponding to the first HARQ process to send data, or does not receive a dynamic authorization sent by the network device The command for sending data by the first HARQ process authorizes sending new data or retransmitting data according to the configuration corresponding to the first HARQ process.
[claim 14]
The apparatus for data transmission according to claim 11, wherein the authorizing to send new data according to the configuration corresponding to the first HARQ process comprises: determining that the transport block in the buffer corresponding to the first HARQ process has been successfully sent After or it is determined that the first timer has been started for the transport block, and it is determined that the state of the new data indication of the first HARQ process is reversed, and the medium access control (MAC) layer generates a new data transport block. The configuration corresponding to the first HARQ process authorizes sending the new data transport block.
[claim 15]
The apparatus for data transmission according to claim 14, wherein starting the first timer and starting the second timer comprises: determining that the new data transmission block is successfully sent, starting the first timer, and starting the second timer.
[claim 16]
The apparatus for data transmission according to claim 11, wherein the second sending unit further: determines that the first timer is not running, and determines that the transmission block in the buffer corresponding to the first HARQ process has never succeeded Sending or determining that the first timer has never been started for the transport block authorizes retransmission of the transport block according to a configuration corresponding to the first HARQ process.
[claim 17]
The apparatus for data transmission according to claim 11, wherein the second sending unit further: sends, to the network device, uplink control information (UCI) for indicating configuration grant information of the first HARQ process, wherein , the UCI includes the process identifier of the first HARQ process, the network identifier of the terminal device, and the redundancy version (RV) information of the transport block of the first HARQ process.
[claim 18]
The apparatus for data transmission according to claim 17, wherein, when the configuration authorization data is never successfully sent, the UCI indicates that the configuration authorization data is new data, otherwise, the UCI indicates the configuration authorization data to retransmit data.
[claim 19]
The apparatus for data transmission according to claim 17, wherein the configuration authorization data is indicated to the network device by the identifier of the terminal device in the UCI as new data or a new data of the first HARQ process. transmit data.
[claim 20]
A communication system, comprising: a network device; and a terminal device having the apparatus for data transmission according to any one of claims 1-19.
| # | Name | Date |
|---|---|---|
| 1 | 202237005765.pdf | 2022-02-03 |
| 2 | 202237005765-STATEMENT OF UNDERTAKING (FORM 3) [03-02-2022(online)].pdf | 2022-02-03 |
| 3 | 202237005765-PROOF OF RIGHT [03-02-2022(online)].pdf | 2022-02-03 |
| 4 | 202237005765-POWER OF AUTHORITY [03-02-2022(online)].pdf | 2022-02-03 |
| 5 | 202237005765-FORM 1 [03-02-2022(online)].pdf | 2022-02-03 |
| 6 | 202237005765-FIGURE OF ABSTRACT [03-02-2022(online)].pdf | 2022-02-03 |
| 7 | 202237005765-DRAWINGS [03-02-2022(online)].pdf | 2022-02-03 |
| 8 | 202237005765-DECLARATION OF INVENTORSHIP (FORM 5) [03-02-2022(online)].pdf | 2022-02-03 |
| 9 | 202237005765-COMPLETE SPECIFICATION [03-02-2022(online)].pdf | 2022-02-03 |
| 10 | 202237005765-certified copy of translation [03-02-2022(online)].pdf | 2022-02-03 |
| 11 | 202237005765-MARKED COPIES OF AMENDEMENTS [04-02-2022(online)].pdf | 2022-02-04 |
| 12 | 202237005765-FORM 13 [04-02-2022(online)].pdf | 2022-02-04 |
| 13 | 202237005765-AMMENDED DOCUMENTS [04-02-2022(online)].pdf | 2022-02-04 |
| 14 | 202237005765-FORM 18 [07-02-2022(online)].pdf | 2022-02-07 |
| 15 | 202237005765-Information under section 8(2) [21-03-2022(online)].pdf | 2022-03-21 |
| 16 | 202237005765-FER.pdf | 2022-07-07 |
| 17 | 202237005765-FORM 3 [11-07-2022(online)].pdf | 2022-07-11 |
| 18 | 202237005765-Information under section 8(2) [05-01-2023(online)].pdf | 2023-01-05 |
| 19 | 202237005765-FORM 3 [05-01-2023(online)].pdf | 2023-01-05 |
| 20 | 202237005765-OTHERS [06-01-2023(online)].pdf | 2023-01-06 |
| 21 | 202237005765-FER_SER_REPLY [06-01-2023(online)].pdf | 2023-01-06 |
| 22 | 202237005765-DRAWING [06-01-2023(online)].pdf | 2023-01-06 |
| 23 | 202237005765-COMPLETE SPECIFICATION [06-01-2023(online)].pdf | 2023-01-06 |
| 24 | 202237005765-CLAIMS [06-01-2023(online)].pdf | 2023-01-06 |
| 25 | 202237005765-ABSTRACT [06-01-2023(online)].pdf | 2023-01-06 |
| 26 | 202237005765-FORM 3 [25-10-2023(online)].pdf | 2023-10-25 |
| 27 | 202237005765-US(14)-HearingNotice-(HearingDate-12-03-2025).pdf | 2025-02-12 |
| 28 | 202237005765-FORM-26 [28-02-2025(online)].pdf | 2025-02-28 |
| 29 | 202237005765-Correspondence to notify the Controller [28-02-2025(online)].pdf | 2025-02-28 |
| 30 | 202237005765-US(14)-ExtendedHearingNotice-(HearingDate-13-03-2025)-1100.pdf | 2025-03-11 |
| 31 | 202237005765-FORM-26 [12-03-2025(online)].pdf | 2025-03-12 |
| 32 | 202237005765-NOTARIZED AND STAMPED COPY OF GPA-(13-03-2025).pdf | 2025-03-13 |
| 33 | 202237005765-HEARING NOTICE-(13-03-2025).pdf | 2025-03-13 |
| 34 | 202237005765-US(14)-ExtendedHearingNotice-(HearingDate-25-03-2025)-1200.pdf | 2025-03-17 |
| 35 | 202237005765-FORM 3 [18-03-2025(online)].pdf | 2025-03-18 |
| 36 | 202237005765-Correspondence to notify the Controller [21-03-2025(online)].pdf | 2025-03-21 |
| 37 | 202237005765-Written submissions and relevant documents [09-04-2025(online)].pdf | 2025-04-09 |
| 38 | 202237005765-Annexure [09-04-2025(online)].pdf | 2025-04-09 |
| 39 | 202237005765-PatentCertificate10-10-2025.pdf | 2025-10-10 |
| 40 | 202237005765-IntimationOfGrant10-10-2025.pdf | 2025-10-10 |
| 1 | 202237005765SearchstdE_06-07-2022.pdf |