Patent Description:
In the New Radio (NR) system, there are two services, Ultra-Reliable Low Latency (URLLC) and Enhanced Mobile Broadband (eMBB), with different scheduling timings. The eMBB transmission is not sensitive to delay requirements, and therefore the interval between data transmission and detection feedback, or the interval between scheduling signaling and data transmission, can be configured to be relatively large. However, the URLLC transmission is delay-sensitive, and therefore the interval between data transmission and detection feedback, or the interval between scheduling signaling and data transmission, is typically configured to be relatively small.

Terminal devices adopt single-process, sequential processing. That is, a terminal device has to complete processing of one data service before it can process the next data service. Therefore, when the terminal device is processing an eMBB service transmission, the terminal device will not be configured with any URLLC transmission. As a result, the URLLC service may not to be scheduled or transmitted in time, which increases the transmission delay of the URLLC service. <CIT> discloses some embodiments in which low latency and latency tolerant communications coexist in the same time-frequency resources, and some embodiments in which a latency tolerant transmission is postponed to free resources to send a low latency transmission. <CIT> discloses that a wireless transmit/receive unit (WTRU) may receive a configuration message that includes scheduled resources to communicate a scheduling request (SR) for uplink (UL) transmission during a configured downlink (DL) slot for enhanced mobile broadband (eMBB) communication. <CIT> discloses an uplink control information transmission method which can provide special protection for transmission of a URLLC UCI, and ensure the high reliability of a URLC service.

The embodiments of the present disclosure provide a data transmission method, a terminal device, and a network device, capable of improving transmission efficiency of low latency services.

In a first aspect, a data transmission method is provided. The method includes: receiving, by a terminal device, first downlink information and second downlink information transmitted by a network device, first downlink information having a time domain position earlier than a time domain position of the second downlink information; and determining, by the terminal device, to process first data corresponding to the first downlink information and/or second data corresponding to the second downlink information, and transmitting first uplink information corresponding to the first downlink information and/or second uplink information corresponding to the second downlink information to the network device based on a result of the processing. Here, the first uplink information corresponding to the first downlink information has a time domain position later than a time domain position of the second uplink information corresponding to the second downlink information.

In a second aspect, a data transmission method is provided. The method includes: transmitting, by a network device, first downlink information and second downlink information to a terminal device, the first downlink information having a time domain position earlier than a time domain position of the second downlink information; and determining, by the network device, whether to receive first uplink information corresponding to the first downlink information and/or second uplink information corresponding to the second downlink information that is transmitted by the terminal device. Here, the first uplink information corresponding to the first downlink information has a time domain position later than a time domain position of the second uplink information corresponding to the second downlink information.

In a third aspect, a terminal device is provided. The terminal device includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and execute the computer program stored in the memory to perform the method according to the above first aspect or any implementation thereof.

In a fourth aspect, a network device is provided. The network device includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to invoke and execute the computer program stored in the memory to perform the method according to the above second aspect or any implementation thereof.

With the above solutions, for some uplink or downlink data transmission process (e.g., Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH)), its corresponding processing time interval is typically much larger than a processing time of a terminal device which is corresponding to a specific processing capability. For example, there may be typically redundant, idle time within the processing time interval for PDSCH/PUSCH corresponding to an eMBB service. Thus, other data, such as a delay-sensitive URLLC service, can be processed within the time interval. In this way, the low-latency scheduling requirements can be satisfied without significantly increasing the complexity of the terminal device.

The technical solutions in the embodiments of the present disclosure will be described below with reference to the figures in the embodiments of the present disclosure. Obviously, the described embodiments are only some embodiments, rather than all embodiments, of the present disclosure.

The technical solutions according to the embodiments of the present disclosure can be applied to various communication systems, including for example: Global System of Mobile Communication (GSM), Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, or the <NUM>th Generation (<NUM>) communication system.

A communication system <NUM> where an embodiment of the present disclosure can be applied is illustratively shown in <FIG>. The communication system <NUM> may include a network device <NUM>. The network device <NUM> may be a device that can communicate with a terminal device (or referred to as communication terminal or terminal) <NUM>. The network device <NUM> may provide communication coverage for a particular geographic area, and may communicate with terminal devices located in the coverage area. Optionally, the network device <NUM> may be a base station such as Base Transceiver Station (BTS) in a GSM system or a CDMA system, a base station such as NodeB (NB) in a WCDMA system, a base station such as Evolutional Node (eNB or eNodeB) in an LTE system, or a radio controller in a Cloud Radio Access Network (CRAN). Alternatively, the network device may be a mobile switch center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a network bridge, a router, a network side device in a <NUM> network, or a network device in a future evolved Public Land Mobile Network (PLMN).

The communication system <NUM> further includes at least one terminal device <NUM> located within the coverage of the network device <NUM>. As used herein, the term "terminal device" may include, but not limited to, an apparatus connected via a wired line, e.g., via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, or a direct cable connection, and/or via another data connection/network, and/or via a wireless interface, e.g., for a cellular network, a Wireless Local Area Network (WLAN), a digital TV network such as a DVB-H network, a satellite network, an Amplitude Modulation (AM)-Frequency Modulation (FM) broadcast transmitter, and/or another terminal device, and configured to receive/transmit communication signals, and/or an Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", a "wireless terminal", or a "mobile terminal". Examples of the mobile terminal may include, but not limited to, a satellite or cellular phone, a Personal Communications System (PCS) terminal combining cellular radio phone with data processing, fax, and data communication capabilities, a PDA including a radio phone, a pager, Internet/intranet access, a Web browser, a memo pad, a calendar, and/or a Global Positioning System (GPS) receiver, or a conventional laptop and/or palmtop receiver or another electronic device including a radio telephone transceiver. The terminal device may be an access terminal, a User Equipment (UE), a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. Alternatively, the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device or a computing device having a wireless communication function, another processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a <NUM> network, or a terminal devices in a future evolved PLMN, etc..

Optionally, direct communication, such as Device to Device (D2D) communication, may be performed between the terminal devices <NUM>.

Optionally, the <NUM> system or network may also be referred to as a New Radio (NR) system or network.

<FIG> exemplarily shows one network device and two terminal devices. Optionally, the communication system <NUM> may include a plurality of network devices and the coverage of each network device may include a different number of terminal devices. The embodiment of the present disclosure is not limited to any of these examples.

Optionally, the communication system <NUM> may further include other network entities such as a network controller and a mobility management entity, and the embodiment of the present disclosure is not limited to any of these examples.

It can be appreciated that, in the embodiment of the present disclosure, a device with a communication function in a network/system may be referred to as a communication device. For the communication system <NUM> shown in <FIG> as an example, communication devices may include the network device <NUM> and the terminal devices <NUM>, each having a communication function. The network device <NUM> and the terminal devices <NUM> may be e.g., any of the specific devices described above, and details thereof will be omitted here. The communication device may also include other devices in the communication system <NUM>, such as a network controller, a mobility management entity, and other network entities, and the embodiment of the present disclosure is not limited to any of these examples.

It is to be noted that the terms "system" and "network" are often used interchangeably herein. The term "and/or" as used herein only represents a relationship between correlated objects, including three relationships. For example, "A and/or B" may mean A only, B only, or both A and B. In addition, the symbol "/" as used herein represents an "or" relationship between the correlated objects preceding and succeeding the symbol.

In the NR system, there are two services, URLLC and eMBB, with different scheduling timings. The eMBB transmission is not sensitive to delay requirements, and therefore the interval between data transmission and detection feedback, or the interval between scheduling signaling and data transmission, can be configured to be relatively large. However, the URLLC transmission is delay-sensitive, and therefore the interval between data transmission and detection feedback, or the interval between scheduling signaling and data transmission, is typically configured to be relatively small.

For example, <FIG> shows a schematic diagram of data transmission and detection feedback. As shown in <FIG>, a Physical Downlink Shared Channel (PDSCH) is used for downlink data transmission between a network device and a terminal device. For example, the data in PDSCH <NUM> in <FIG> may be for an eMBB service, and the data in PDSCH <NUM> may be for a URLLC service. Correspondingly, a Physical Uplink Control Channel (PUCCH) transmitted by the terminal device is used to carry a Hybrid Automatic Repeat reQuest (HARQ) Acknowledgement (ACK) to feed back a reception status of the PDSCH to the network device. For example, HARQ-ACK <NUM> in <FIG> is used to feed back a reception status of PDSCH <NUM>, and HARQ-ACK <NUM> is used to feed back a reception status of PDSCH <NUM>. As shown in <FIG>, since the eMBB service transmission is not sensitive to delay requirements, the time interval between PDSCH <NUM> and HARQ-ACK <NUM> can be relatively large, while the URLLC service transmission is sensitive to delay requirements, and accordingly the time interval between PDSCH <NUM> and HARQ-ACK <NUM> is relatively small.

As another example, <FIG> shows a schematic diagram of scheduling signaling and data transmission. As shown in <FIG>, a network device transmits uplink resource indication information to a terminal device, i.e., uplink grant (UL grant), for scheduling uplink resources for the terminal device. Here, UL grant <NUM> and UL grant <NUM> are used to schedule different uplink resources. Correspondingly, the terminal device uses the uplink resources scheduled by the network device to transmit a Physical Uplink Shared Channel (PUSCH) to the network device. The PUSCH is used to carry uplink data. For example, the data in PUSCH <NUM> in <FIG> may be for an eMBB service, and the data in PUSCH <NUM> may be for a URLLC service. In addition, as shown in <FIG>, since the eMBB service transmission is not sensitive to delay requirements, the time interval between UL grant <NUM> and PUSCH <NUM> can be relatively large; while the URLLC service transmission is sensitive to delay requirements, and accordingly the time interval between UL grant <NUM> and PUSCH <NUM> is relatively small.

However, in the current protocol, terminal devices adopt single-process, sequential processing. That is, a terminal device has to complete processing of one PDSCH/PUSCH before it can process the next PDSCH/PUSCH, so as to avoid cross-scheduling, i.e., to avoid the PDSCH2/PUSCH2 transmission shown in <FIG>. As a result, the URLLC service may not be scheduled or transmitted immediately, which increases the transmission delay of the URLLC service.

Therefore, an embodiment of the present disclosure provides a data transmission method. Since a URLLC service requires immediate scheduling, in order to avoid waiting time that consumes the delay budget, the scheduling of PDSCH <NUM> in <FIG> and the scheduling of PUSCH <NUM> in <FIG> are allowed. In this way, out-of-order data can be processed and the transmission efficiency of the system can be improved.

<FIG> is a schematic flowchart of a data transmission method <NUM> according to an embodiment of the present disclosure. The method <NUM> may be performed by a terminal device and a network device. For example, the terminal device may be the terminal device as shown in <FIG>, and the network device may be the network device as shown in <FIG>.

As shown in <FIG>, the method <NUM> includes: at S210, transmitting first downlink information. That is, the network device transmits first downlink information to the terminal device. The first downlink information corresponds to first uplink information.

For example, the first downlink information may be first uplink resource indication information, and correspondingly, the first uplink information may be a first PUSCH. Here, the first uplink resource indication information may indicate a resource occupied by the first PUSCH, and the first PUSCH may carry first data.

In another example, alternatively, the first downlink information may be a first PDSCH, and correspondingly, the first uplink information may be a first PUCCH. Here, the first PDSCH may carry first data, and the first PUCCH may carry feedback information for the first data.

As shown in <FIG>, the method <NUM> further includes: at S220, transmitting second downlink information. That is, the network device transmits second downlink information to the terminal device. The second downlink information corresponds to second uplink information.

For example, the second downlink information may be second uplink resource indication information, and correspondingly, the second uplink information may be a second PUSCH. Here, the second uplink resource indication information may indicate a resource occupied by the second PUSCH, and the second PUSCH may carry second data.

In another example, alternatively, the second downlink information may be a second PDSCH, and correspondingly, the second uplink information may be a second PUCCH. Here, the second PDSCH may carry second data, and the second PUCCH may carry feedback information for the second data.

It is to be understood that the transmission of the first downlink information and the transmission of the second downlink information by the network device to the terminal device are cross-transmission, or out-of-order transmission of data. That is, a time domain position of the first downlink information is earlier than a time domain position of the second downlink information, and a time domain position of the first uplink information is later than a time domain position of the second uplink information. For example, <FIG> is a schematic diagram showing time domain positions of various information in an embodiment of the present disclosure. As shown in <FIG>, the time domain position of the first downlink information is before the time domain position of the second downlink information, and the time domain position of the first uplink information is after the time domain position of the second uplink information.

Optionally, in an embodiment of the present disclosure, the time domain position of the first downlink information may refer to any time point in the time domain resource occupied by the first downlink information, or in other words, any time point in a process during which the terminal device is receiving the first downlink information. Similarly, the time domain position of the second downlink information may refer to any time point in the time domain resource occupied by the second downlink information, or in other words, any time point in a process during which the terminal device is receiving the second downlink information. For example, the time domain position of the first downlink information may be start time or end time for the terminal device to receive the first downlink information. The time domain position of the second downlink information may be start time or end time for the terminal device to receive the second downlink information. However, the embodiment of the present disclosure is not limited to any of these examples.

Similarly, in an embodiment of the present disclosure, the time domain position of the first uplink information may refer to any time point in the time domain resource occupied by the first uplink information. Similarly, the time domain position of the second uplink information may refer to any time point in the time domain resource occupied by the second uplink information. For example, the time domain position of the first uplink information may be start time or end time of the time domain resource occupied by the first uplink information. The time domain position of the second uplink information may be start time or end time of the time domain resource occupied by the second uplink information. However, the embodiment of the present disclosure is not limited to any of these examples.

In an embodiment of the present disclosure, since each of the time domain position of the first downlink information and the time domain position of the second downlink information may represent any time point, correspondingly, the time domain position of the first downlink information being earlier than the time domain position of the second downlink information may mean that the start time for the terminal device to receive the first downlink information is earlier than the start time for the terminal device to receive the second downlink data, or the end time for the terminal device to receive the first downlink information is earlier than the end time for the terminal device to receive the second downlink data, or the end time for the terminal device to receive the first downlink information is earlier than the start time for the terminal device to receive the second downlink data. However, the embodiment of the present disclosure is not limited to any of these examples.

Similarly, since each of the time domain position of the first uplink information and the time domain position of the second uplink information may represent any time point, correspondingly, the time domain position of the first uplink information being later than the time domain position of the second uplink information may mean that the start position of the time domain resource occupied by the first uplink information is later than the start position of the time domain resource occupied by the second uplink information, or the start position of the time domain resource occupied by the first uplink information is later than the end position of the time domain resource occupied by the second uplink information. However, the embodiment of the present disclosure is not limited to any of these examples.

As shown in <FIG>, the method <NUM> further includes: at S230, determining whether to process the first data and/or the second data. That is, the terminal device may determine whether to process the first data corresponding to the first downlink information, and may also determine whether to process the second data corresponding to the second downlink information.

As shown in <FIG>, the method <NUM> further includes: at S240, transmitting the first uplink information and/or the second uplink information. That is, the terminal device transmits the first uplink information and/or the second uplink information to the network device according to the processing result in S230.

Since the terminal device receives the second downlink information after receiving the first downlink information and before it needs to transmit the first uplink information to the network device, and the second uplink information scheduled by the second downlink information is earlier than the first uplink information, which forms a cross-transmission or out-of-sequence transmission. Therefore, the terminal device needs to determine whether to process the first data and/or the second data. For example, the terminal device can determine whether to process the first data and/or the second data based on time required for processing the first data and time required for processing the second data. Alternatively, the terminal device can determine whether to process the first data and/or the second data based on a priority of the first data and a priority of the second data. The terminal device can also determine whether to process the first data and/or the second data based further on other conditions. Correspondingly, the terminal device can transmit the corresponding first uplink information and/or second downlink information to the network device based on the processing result(s) of the first data and/or the second data.

The steps S230 and S240 in the method <NUM> will be described in detail below with reference to two specific embodiments.

Optionally, as a first embodiment, the step S230 in the method <NUM> may include: determining, by the terminal device, to process the first data and/or the second data based on processing time for the first data and/or processing time for the second data.

For the purpose of illustration, here, several time periods are defined first for the respective time domain positions of the first downlink information, the second downlink information, the first uplink information, and the second uplink information. First, a time interval between the time domain position of the first downlink information and the time domain position of the second downlink information is defined as a first time length. For example, the first time length may specifically be the time interval from the end time of the time domain position occupied by the first downlink information to the end time of the time domain position occupied by the second downlink information, i.e., GAP <NUM> as shown in <FIG>. Alternatively, the first time length may be the time interval between the end time of the time domain position occupied by the first downlink information and the start time of the time domain position occupied by the second downlink information, or the time interval between the start time of the time domain position occupied by the first downlink information and the start time of the time domain position occupied by the second downlink information. However, the embodiment of the present disclosure is not limited to any of these examples.

Second, a time interval from the time domain position of the second uplink information to the time domain position of the first uplink information is defined as a second time length. For example, the second time length may specifically be the time interval from the start time of the time domain resource occupied by the second uplink information to the start time of the time domain position occupied by the first uplink information, i.e., GAP <NUM> as shown in <FIG>. Alternatively, the second time length may be the time interval between the end time of the time domain resource occupied by the second uplink information and the start time of the time domain position occupied by the first uplink information. However, the embodiment of the present disclosure is not limited to any of these examples.

Third, a time interval from the time domain position of the second downlink information to the time domain position of the second uplink information is defined as a third time length. For example, the third time length may specifically be the time interval between the end time of the time domain resource occupied by the second downlink information and the start time of the time domain resource occupied by the second uplink information, i.e., GAP <NUM> as shown in <FIG>. Alternatively, the third time length may be the time interval from the start time of the time domain resource occupied by the second downlink information to the start time of the time domain resource occupied by the second uplink information. However, the embodiment of the present disclosure is not limited to any of these examples.

Fourth, a time interval from the time domain position of the first downlink information to the time domain position of the first uplink information is defined as a fourth time length. For example, the fourth time length may specifically be the time interval between the end time of the time domain resource occupied by the first downlink information and the start time of the time domain resource occupied by the first uplink information, i.e., GAP <NUM> as shown in <FIG>. Alternatively, the fourth time length may be the time interval from the start time of the time domain resource occupied by the first downlink information to the start time of the time domain resource occupied by the first uplink information. However, the embodiment of the present disclosure is not limited to any of these examples.

In an embodiment of the present disclosure, the terminal device can determine whether to process the first data and/or the second data based on the first time length to the fourth time length as defined above, the time required for processing the first data, and the time required for processing the second data.

Optionally, the terminal device may determine whether to process the first data based on the first time length and/or the second time length. In particular, if the first time length and/or the second time length are greater than or equal to a first predetermined time length, the terminal device can determine to process the first data, and then transmit the first uplink information to the network device based on the processing result of the first data.

In particular, if the first time length is greater than or equal to the first predetermined time length, the terminal device can process the first data. For example, the terminal device may process the first data within the first time length and transmit the first uplink information to the network device. On the other hand, if the first time length is smaller than the first predetermined time length, the terminal device may determine not to process the first data, or skip or stop processing the first data. Alternatively, the terminal device may determine whether to process the first data according to other conditions. For example, the terminal device may determine whether to process the first data based on to the value of the second time length.

Similarly, if the second time length is greater than or equal to the first predetermined time length, the terminal device can process the first data. For example, the terminal device can process the first data within the second time length and transmit the first uplink information to the network device. On the other hand, if the second time length is smaller than the first predetermined time length, the terminal device may determine not to process the first data, or skip or stop processing the first data. Alternatively, the terminal device may determine whether to process the first data according to other conditions. For example, the terminal device may determine whether to process the first data based on the value of the first time length.

Optionally, if the terminal device determines not to process the first data, the terminal device may not transmit the first uplink information to the network device. Accordingly, the network device does not receive the first uplink information on the corresponding resource. The network device may also use the resource position corresponding to the first uplink information for transmission of other data. Alternatively, when the terminal device determines not to process the first data, the terminal device may also transmit the first uplink information to the network device, and the first uplink information indicates to the network device that the terminal device does not process the first data.

It can be appreciated that, in an embodiment of the present disclosure, the first predetermined time length may include the processing time for the first data, that is, the time required for the terminal device to process the first data. Alternatively, the first predetermined time length may further include conversion time for the terminal device between the first data and the second data. For example, the first predetermined time length may include the conversion time for converting from processing the second data to processing the first data, and/or the conversion time for converting from processing the first data to processing the second data.

In the process of converting from the out-of-order transmission to in-order transmission, or in the process of converting from one data processing to another data processing, there may be processes such as storing intermediate processing results, processing decisions, and switching processes. Therefore, the terminal device needs to take the processing time of the conversion process into consideration. That is, when deciding whether the terminal device can process the out-of-order data, the first predetermined time length needs to include not only the time for processing the data to be processed (i.e., the first data), which is corresponding to a specific processing capability, but also the conversion time. Alternatively, the conversion time can also be directly incorporated in the processing time for the first data. That is, the time required for processing the first data as described above may include the processing time of the terminal device which is corresponding to a specific processing capability, and the conversion time. However, non-ideal factors can be added on the basis of the existing data processing capability. Since the existing processing capability has a certain margin, the conversion time can also be ignored. The embodiment of the present disclosure is not limited to any of these examples.

For example, <FIG> is a schematic diagram showing scheduling signaling and data transmission in an embodiment of the present disclosure. As shown in <FIG>, it is assumed that the first downlink information is UL grant <NUM>, and the first uplink information is PUSCH <NUM> scheduled by UL grant <NUM>; the second downlink information is UL grant <NUM>, and the second uplink information is PUSCH <NUM> scheduled by UL grant <NUM>. In particular, it is assumed that the terminal device receives UL grant <NUM> in time slot n, and its scheduled PUSCH <NUM> is in time slot n+<NUM>; the terminal device also receives UL grant <NUM> in time slot n, and its scheduled PUSCH <NUM> is in time slot n+<NUM>. Here, the time domain position of UL grant <NUM> is before that of UL grant <NUM>. For example, the end time of the time domain resource occupied by UL grant <NUM> can be compared with the end time of the time domain resource occupied by UL grant <NUM>, and UL grant <NUM> is earlier than UL grant <NUM>. PUSCH <NUM> is before PUSCH <NUM>. For example, the start time of the time domain resource occupied by PUSCH <NUM> can be compared with the start time of the time domain resource occupied by PUSCH <NUM>, and PUSCH <NUM> is earlier than PUSCH <NUM>. In addition, it is also assumed that the first predetermined time length is equal to <NUM> symbols, including <NUM> symbols as processing time for PUSCH <NUM> and <NUM> symbols as conversion time; the second predetermined time length is also <NUM> symbols, including <NUM> symbols as processing time for PUSCH <NUM> and <NUM> symbols as conversion time.

As shown in <FIG>, the first time length is GAP <NUM> in <FIG> and is assumed to be <NUM> symbols, then the first time length is smaller than the processing time of PUSCH <NUM> (<NUM> symbols), and the terminal device does not process the first data within the first time length. Alternatively, if the terminal device has already started processing the first data within the first time length, it will skip or stop processing the first data after receiving UL grant <NUM>.

In addition, the second time length is GAP <NUM> in <FIG> and is assumed to be <NUM> symbols. That is, the second time length is longer than the first predetermined time length (<NUM> symbols), then the terminal device determines to process the first data within the second time length, and transmits PUSCH <NUM> to the network device at the time domain position of PUSCH <NUM>. PUSCH <NUM> is used to carry the first data.

It can be appreciated that, in <FIG>, when at least one of the first time length and the second time length is greater than or equal to the first predetermined time length, the terminal device may determine to process the first data. Alternatively, the terminal device may determine whether to process the first data based only on the first time length. In particular, as shown in <FIG>, similar to <FIG>, it is also assumed that the terminal device receives UL grant <NUM> in time slot n, and its scheduled PUSCH <NUM> is in time slot n+<NUM>; the terminal device also receives UL grant <NUM> in time slot n, and its scheduled PUSCH <NUM> is in time slot n+<NUM>.

As shown in <FIG>, the first time length is GAP <NUM> in <FIG> and is assumed to be <NUM> symbols, then the first time length is smaller than the processing time of PUSCH <NUM> (<NUM> symbols), and the terminal device determines not to process the first data. Alternatively, if the terminal device has already started processing the first data within the first time length, it will skip or stop processing the first data after receiving UL grant <NUM>.

In another example, <FIG> is a schematic diagram showing data transmission and detection feedback in an embodiment of the present disclosure. As shown in <FIG>, it is assumed that the first downlink information is PDSCH <NUM>, which is used to carry the first data, and accordingly, the first uplink information is PUCCH <NUM>, which includes feedback information for the first data. Similarly, it is assumed that the second downlink information is PDSCH <NUM>, which is used to carry the second data, and accordingly, the second uplink information is PUCCH <NUM>, which includes feedback information for the second data. In particular, it is assumed that the terminal device receives PDSCH <NUM> in time slot n, and its corresponding PUCCH <NUM> is in time slot n+<NUM>; the terminal device also receives PDSCH <NUM> in time slot n+<NUM>, and its scheduled PUCCH <NUM> is in time slot n+ <NUM>. Here, PDSCH <NUM> is after PDSCH <NUM>. For example, as shown in <FIG>, the end time of the time domain resource occupied by PDSCH <NUM> can be compared with the end time of the time domain resource occupied by PDSCH <NUM>. PDSCH <NUM> is earlier than PDSCH <NUM>. In addition, PUCCH <NUM> is before PUCCH <NUM>. For example, as shown in <FIG>, the start time of the time domain resource occupied by PUCCH <NUM> can be compared with the start time of the time domain resource occupied by PUCCH <NUM>, and PUCCH <NUM> is later than PUCCH <NUM>. In addition, it is also assumed that the first predetermined time length is equal to <NUM> symbols, including <NUM> symbols as processing time for PDSCH <NUM> and <NUM> symbols as conversion time; the second predetermined time length is also <NUM> symbols, including <NUM> symbols as processing time for PDSCH <NUM> and <NUM> symbols as conversion time.

As shown in <FIG>, the first time length is GAP <NUM> in <FIG> and is assumed to be <NUM> symbols, which is equal to the first predetermined time length (<NUM> symbols), i.e., greater than the time for processing PDSCH <NUM> (<NUM> symbols), and the terminal device determines to process the first data within the first time length, and transmits PUCCH <NUM> to the network device at the time domain position of PUCCH <NUM>. PUCCH <NUM> is used to feed back a reception status of the first data to the network device.

In an embodiment of the present disclosure, for the second data, the terminal device may determine whether to process the second data based on the third time length. In particular, if the third time length is greater than or equal to a second predetermined time length, the terminal device can process the second data. For example, the terminal device can process the second data within the third time length; and then transmit the second uplink information to the network device based on the processing result of the second data. On the other hand, if the third time length is smaller than the second predetermined time length, the terminal device does not expect such scheduling. That is, the network device should avoid the situation where the third time length is smaller than the second predetermined time length. Alternatively, if the third time length is smaller than the second predetermined time length, the terminal device can determine to skip or stop processing the second data, and do not transmit the second uplink information to the network device. Accordingly, the network device does not receive the second uplink information on the corresponding resource. The network device may further use the resource position corresponding to the second uplink information for the transmission of other data. Alternatively, the second uplink information transmitted by the terminal device to the network device may indicate that the terminal device has not completed processing of the second data.

It can be appreciated that, in an embodiment of the present disclosure, the second predetermined time length may include the processing time for the second data, i.e., the time required for the terminal device to process the second data. Alternatively, the second predetermined time length may further include conversion time for the terminal device to convert from processing the first data to processing the second data. Similar to the first predetermined time length, in the process of converting from the out-of-order transmission to in-order transmission, or in the process of converting from processing the first data to processing the second data, there may be processes such as storing intermediate processing results, processing decisions, and switching processes. Therefore, the terminal device needs to take the processing time of the conversion process into consideration. That is, when deciding whether the terminal device can process the out-of-order data, the second predetermined time length needs to include not only the processing time for the data to be processed (i.e., the second data), but also the conversion time. Alternatively, the conversion time can also be directly incorporated in the processing time for the second data. That is, the time required for processing the second data as described above may include the processing time of the terminal device and the conversion time. However, non-ideal factors can be added on the basis of the existing data processing capability. Since the existing processing capability has a certain margin, the conversion time can also be ignored. The embodiment of the present disclosure is not limited to any of these examples.

For example, referring to <FIG> and <FIG> again, as shown in <FIG> and <FIG>, the third time length is GAP3 in <FIG> and <FIG> and is assumed to be <NUM> symbols, which is equal to the second predetermined time length, or greater than the time required for processing the second data (<NUM> symbols). Therefore, the terminal device can process the second data within the third time length, and transmit PUSCH <NUM> to the network device at the time domain position of PUSCH <NUM>. PUSCH <NUM> is used to carry the second data.

In another example, referring to <FIG>, the third time length is GAP <NUM> as shown in <FIG> and is assumed to be <NUM> symbols, which is equal to the second predetermined time length, or greater than the time required for processing the second data (<NUM> symbols). Therefore, the terminal device can process the second data within the third time length, i.e., to receive and parse the data carried by PDSCH <NUM>, and transmit PUCCH <NUM> to the network device at the time domain position of PUCCH <NUM>. PUCCH <NUM> is used to feed back a reception status of the second data to the network device.

It can be appreciated that in the case shown in <FIG>, if the terminal device determines not to process the first data or the second data, the terminal device may not transmit the corresponding PUCCH <NUM> and/or PUCCH <NUM> to the network device, or may transmit PUCCH <NUM> carrying a Negative Acknowledgement (NACK) and PUCCH <NUM> carrying a NACK. For example, assuming that the first time length is smaller than the first predetermined time length, the terminal device may determine not to process the first data, i.e., not to process PDSCH <NUM>, then the terminal device may not transmit the corresponding PUCCH <NUM> to the network device, or may transmit PUCCH <NUM> carrying a NACK to the network device.

It can be appreciated that if the terminal device can support the capability to store intermediate data, serial processing can also be used to solve the problem of out-of-order transmission. In particular, if the fourth time length is greater than or equal to the sum of the first predetermined time length and the second predetermined time length, the terminal device can process the first data and the second data, and transmit the first uplink information and the second uplink information to the network device. That is, the terminal device can start processing the first data when the first downlink information is received, and if the second downlink information is received when the processing of the first data has not been completed, the second data corresponding to the second downlink information can be processed. For the first data that has already been processed partially, the processing of the first data can be suspended, and the processed data can be saved. When the terminal device completes the processing of the second data, it can resume the processing of the first data. Here, it can be ensured that both the first data and the second data can be processed, and correspondingly the first uplink information and the second uplink information can be transmitted to the network device.

On the other hand, if the fourth time length is smaller than the sum of the first predetermined time length and the second predetermined time length, the terminal device can determine to skip or stop processing the first data and/or the second data. For example, the terminal device may determine whether to process the first data or the second data according to other conditions. For example, if the priority of the first data is higher than the priority of the second data, the first data will be processed within the fourth time length. If the priority of the second data is higher than the priority of the first data, the second data will be processed with the fourth time length. However, the embodiment of the present disclosure is not limited to any of these examples.

In addition, in an embodiment of the present disclosure, if the terminal device does not support the above capability to store intermediate data, if the first time length and the second time length are both smaller than the first predetermined time length, the terminal device does not expect such scheduling. That is, the network device should avoid the situation where the first time length and the second time length are both smaller than the first predetermined time length. Alternatively, if the first time length and the second time length are both smaller than the first predetermined time length, the terminal device can determine to skip or stop processing the first data and do not transmit the first uplink information to the network device. Accordingly, the network device does not receive the first uplink information on the corresponding resource. The network device can also use the resource position corresponding to the first uplink information for transmission of other data. Alternatively, the first uplink information transmitted by the terminal device to the network device may also be used to indicate that the terminal device has not completed the processing of the first data.

Therefore, in the first embodiment, according to the time intervals between the first downlink information, the second downlink information, the second uplink information, and the first uplink information, the order in which the first data and/or the second data is processed can be properly arranged, and the out-of-order transmission is treated equivalent to in-order transmission, such that the processing time of the first data and the processing time of the second data have as little impact as possible on each other, which can satisfy the low-latency scheduling requirements without significantly increasing the complexity of the terminal device.

Optionally, as a second embodiment, the step S230 in the method <NUM> may include: determining, by the terminal device, to process the first data and/or the second data based on a priority of the first data and a priority of the second data.

It is to be understood that the definitions of the first time length to the fourth time length as used in the second embodiment are consistent with those in the first embodiment, and the first predetermined time length and the second predetermined time length in the second embodiment are also consistent with those described in the first embodiment, and details thereof will be omitted here.

Optionally, the terminal device may first determine the priority of the first data and the priority of the second data. For example, the priority of the first data and/or the priority of the second data may be configured by the network device, or may be specified by the protocol, or may be determined by the terminal device based on other conditions. For example, the method <NUM> may further include: determining, by the terminal device, the priority of the first data based on the first downlink information; and/or determining, by the terminal device, the priority of the second data based on the second downlink information.

For example, if the first downlink information is UL Grant <NUM> and the second downlink information is UL Grant <NUM>, the priority of the first data and the priority of the second data can be determined based on UL Grant <NUM> and UL Grant <NUM>, respectively.

In another example, if the first downlink information is PDSCH <NUM> and the second downlink information is PDSCH <NUM>, the priority of the first data in PUCCH <NUM> can be determined based on resource indication information for scheduling PDSCH <NUM>, and the priority of the second data in PUCCH <NUM> can be determined based on resource indication information for scheduling PDSCH <NUM>.

In particular, if the priority of the first data is lower than the priority of the second data, the terminal device can process the second data and transmit the second uplink information to the network device, and accordingly the terminal device may determine to skip or stop processing the first data. Alternatively, the terminal device may further determine whether to process the first data based on other conditions. If the terminal device determines not to process the first data, the terminal device may not transmit the first uplink information to the network device, and accordingly the network device does not receive the first uplink information on the corresponding resource. The network device may also use the resource position corresponding to the first uplink information for transmission of other data. Alternatively, if the terminal device determines not to process the first data, the terminal device may transmit the first uplink information to the network device, and the first uplink information indicates to the network device that the terminal device does not process the first data.

For example, referring to <FIG> again, as shown in <FIG>, it is assumed that the priority of the first data carried by PUSCH <NUM> is lower than the priority of the second data carried by PUSCH <NUM>, or in other words, the priority of the resource scheduled by UL Grant <NUM> is lower than the priority of the resource scheduled by UL Grant <NUM>, then the terminal device determines to process the second data. For example, the terminal device can process the second data within the third time length, and transmit PUSCH <NUM> to the network device at the time domain position of PUSCH <NUM>. The PUSCH <NUM> is used to carry the second data.

Since the priority of the second data is higher, the terminal device can process the second data within the third time length. Accordingly, the third time length should be greater than or equal to the second predetermined time length. If the third time length is smaller than the second predetermined time length, the terminal device does not expect such scheduling, i.e., the network device should avoid the situation where the third time length is smaller than the second predetermined time length. Alternatively, if the third time length is smaller than the second predetermined time length, the terminal device may determine to skip or stop processing the second data, and do not transmit the second uplink information to the network device, or transmit the second uplink information to the network device, indicating that the terminal device has not completed the processing of the second data.

On the other hand, as shown in <FIG>, for the first data with the lower priority, the terminal device may determine not to process the first data. Accordingly, the terminal device may not transmit PUSCH <NUM> to the network device, and the network device will not detect PUSCH <NUM> at the time domain position of PUSCH <NUM>. In addition, the network device may also use the time domain position of PUSCH <NUM> for transmission of other data. For example, this part of resource can be allocated to other terminal devices.

Alternatively, for the first data with the lower priority, the terminal device may further determine whether to process the first data based on a first predetermined time length. In particular, since the priority of the second data is higher, the terminal device can process the second data first, or in other words, the terminal device needs to guarantee the processing of the second data. As for the first data, the terminal device may further determine whether to process the first data based on at least one of the first time length, the second time length, and the fourth time length.

It can be appreciated that, the process of determining whether to process the first data based on at least one of the first time length, the second time length, and the fourth time length is similar to that described in the above first embodiment, and details thereof will be omitted here.

For example, the determination as to whether to process the first data based on the first time length and the second time length will be taken as an example. As shown in <FIG>, it is assumed that the first time length is smaller than the first predetermined time length. That is, the processing of the first data cannot be completed within the first time length. Since the second data has the higher priority, the processing of the second data needs to be completed. After the second data is processed, that is, within the second time length GAP <NUM>, if the second time length is greater than or equal to the first predetermined time length, the terminal device may further process the first data and transmit the first uplink information, i.e., PUSCH <NUM>, to the network device.

In another example, if the first time length is greater than or equal to the first predetermined time length, the terminal device may process the first data within the first time length, that is, to complete the processing of the first data before processing the second data.

Optionally, if the priority of the first data is higher than the priority of the second data, the terminal device can process the first data and transmit the first uplink information to the network device, and accordingly the terminal device may determine to skip or stop processing the second data. Alternatively, the terminal device may further determine whether to process the second data based on other conditions. If the terminal device determines not to process the second data, the terminal device may not transmit the second uplink information to the network device, and accordingly the network device does not receive the second uplink information on the corresponding resource. The network device may also use the resource position corresponding to the second uplink information for transmission of other data. Alternatively, if the terminal device determines not to process the second data, the terminal device may also transmit the second uplink information to the network device, indicating to the network device that the terminal device does not process the second data.

For example, <FIG> is a schematic diagram showing data transmission and detection feedback in an embodiment of the present disclosure. As shown in <FIG>, similar to <FIG>, it is also assumed that the first downlink information is PDSCH <NUM>, which is used to carry the first data, and correspondingly, the first uplink information is PUCCH <NUM>, which includes feedback information for the first data. Similarly, it is assumed that the second downlink information is PDSCH <NUM>, which is used to carry the second data, and correspondingly, the second uplink information is PUCCH <NUM>, which includes feedback information for the second data. In particular, it is assumed that the terminal device receives PDSCH <NUM> in time slot n, and its corresponding PUCCH <NUM> is in time slot n+<NUM>; the terminal device also receives PDSCH <NUM> in time slot n+<NUM>, and its scheduled PUCCH <NUM> is in time slot n+<NUM>. Here, PDSCH <NUM> is after PDSCH <NUM>, and PUCCH <NUM> is before PUCCH <NUM>. In addition, it is also assumed that the first predetermined time length is equal to <NUM> symbols, including <NUM> symbols as processing time for PDSCH <NUM> and <NUM> symbols as conversion time; and the second predetermined time length is also <NUM> symbols, including <NUM> symbols as processing time for PDSCH <NUM> and <NUM> symbols as conversion time.

As shown in <FIG>, it is assumed that the priority of the first data carried by PUSCH <NUM> is higher than the priority of the second data carried by PUSCH <NUM>, or in other words, the priority of the resource scheduled by UL Grant <NUM> is higher than the priority of the resource scheduled by UL Grant <NUM>. The terminal device determines to process the first data. For example, the terminal device can, according to the scheduling of UL Grant <NUM>, process the first data within the fourth time length and transmit PUSCH <NUM>, which is used to carry the first data, to the network device at the time domain position of PUSCH <NUM>.

Since the first data has the higher priority, the terminal device can process the first data within the fourth time length. Accordingly, the fourth time length should be greater than or equal to the first predetermined time length. If the fourth time length is smaller than the first predetermined time length, that is, smaller than the time required for the terminal device to process the first data, the terminal device does not expect such scheduling. That is, the network device should avoid the situation where the fourth time length is smaller than the first predetermined time length. Alternatively, if the fourth time length is smaller than the first predetermined time length, the terminal device may determine to skip or stop processing the first data, and do not transmit the first uplink information to the network device, or transmit the first uplink information to the network device, indicating that the terminal device has not completed the processing of the first data.

On the other hand, as shown in <FIG>, for the second data with the lower priority, the terminal device may determine not to process the second data. Accordingly, the terminal device may not transmit PUSCH <NUM> to the network device, and the network device will not detect PUSCH <NUM> at the time domain position of PUSCH <NUM>. In addition, the network device can also use the time domain position of PUSCH <NUM> for transmission of other data. For example, this part of resource can be allocated to other terminal devices. Alternatively, for the second data with the lower priority, the terminal device may further determine whether to process the second data based on other conditions, for example, according to whether the third time length is greater than, equal to, or smaller than the second predetermined time length.

Therefore, in the second embodiment, the processing order can be selected based on the priority of the data, and the high-priority data can be processed first. The processing flow can be changed from processing the low-priority data to processing the high-priority data, which can satisfy the scheduling requirements of low-latency services.

Therefore, in the data transmission method according to the embodiment of the present disclosure, considering the HARQ-ACK feedback efficiency and system scheduling efficiency, the processing time interval corresponding to some PDSCH/PUSCH is typically much larger than the processing time of the terminal device of a processing capability. For example, there may be typically redundant, idle time within the PDSCH/PDSCH processing interval corresponding to an eMBB service. Thus, other data, such as a delay-sensitive URLLC service, can be processed within the time interval. In particular, the processing of high-priority data can be guaranteed according to the priority of the data, or the processing order can be properly arranged according to the processing time length of the data, so as to satisfy the low-latency scheduling requirements without significantly increasing the complexity of the terminal.

It can be appreciated that in various embodiments of the present disclosure, the values of the sequence numbers of the above processes do not mean the order of execution. The execution order of the processes should be determined by their functions and internal logics. The implementation of the embodiment of the present disclosure is not limited to any specific execution order.

The data transmission methods according to the embodiments of the present disclosure has been described in detail above with reference to <FIG>. A terminal device and a network device according to the embodiments of the present disclosure will be described below in conjunction with <FIG> to <NUM>.

As shown in <FIG>, the terminal device <NUM> according to the embodiment of the present disclosure includes a processing unit <NUM> and a transceiving unit <NUM>. In particular, the transceiving unit <NUM> is configured to: receive first downlink information and second downlink information transmitted by a network device, the first downlink information having a time domain position earlier than a time domain position of the second downlink information, and first uplink information corresponding to the first downlink information having a time domain position later than a time domain position of second uplink information corresponding to the second downlink information. The processing unit <NUM> is configured to: determine to process first data corresponding to the first downlink information and/or second data corresponding to the second downlink information, and transmit the first uplink information and/or the second uplink information to the network device via the transceiving unit <NUM> based on a result of the processing.

Optionally, as an embodiment, the processing unit <NUM> may be configured to: determine to process the first data and/or the second data based on processing time for the first data and/or processing time for the second data.

Optionally, as an embodiment, the processing unit <NUM> may be configured to perform at least one of: process the first data and transmit the first uplink information to the network device via the transceiving unit <NUM>, when a first time length between the time domain position of the first downlink information and the time domain position of the second downlink information is greater than or equal to a first predetermined time length, the first predetermined time length including the processing time for the first data; process the first data and transmit the first uplink information to the network device via the transceiving unit <NUM>, when a second time length between the time domain position of the second uplink information and the time domain position of the first uplink information is greater than or equal to the first predetermined time length; determine to skip or stop processing the first data, when the first time length is smaller than the first predetermined time length and/or the second time length is smaller than the first predetermined time length; process the second data and transmit the second uplink information to the network device via the transceiving unit <NUM>, when a third time length between the time domain position of the second downlink information and the time domain position of the second uplink information is greater than or equal to a second predetermined time length, the second predetermined time length including the processing time for the second data; determine to skip or stop processing the second data, when the third time length is smaller than the second predetermined time length; process the first data and the second data, and transmit the first uplink information and the second uplink information to the network device via the transceiving unit <NUM>, when a fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information is greater than or equal to a sum of the first predetermined time length and the second predetermined time length; and determine to skip or stop processing the first data and/or the second data, when the fourth time length is smaller than the sum of the first predetermined time length and the second predetermined time length.

Optionally, as an embodiment, the processing unit <NUM> is configured to determine to process the first data and/or the second data according to the priority of the first data and the second data.

Optionally, as an embodiment, the processing unit <NUM> may be further configured to: determine the priority of the first data based on the first downlink information; and/or determine the priority of the second data based on the second downlink information.

Optionally, as an embodiment, the processing unit <NUM> may be configured to perform at least one of: process the first data and transmit the first uplink information to the network device via the transceiving unit <NUM>, when the priority of the first data is higher than the priority of the second data; determine to skip or stop processing the second data, when the priority of the first data is higher than the priority of the second data; process the second data and transmit the second uplink information to the network device via the transceiving unit <NUM>, when the priority of the first data is lower than the priority of the second data; determine to skip or stop processing the first data, or to process the first data based on processing time for the first data, when the priority of the first data is lower than the priority of the second data.

Optionally, as an embodiment, the processing unit <NUM> may be further configured to perform at least one of: process the first data and transmit the first uplink information to the network device via the transceiving unit <NUM>, when a first time length between the time domain position of the first downlink information and the time domain position of the second downlink information is greater than or equal to a first predetermined time length, the first predetermined time length including the processing time for the first data; process the first data and transmit the first uplink information to the network device via the transceiving unit <NUM>, when a second time length between the time domain position of the second uplink information and the time domain position of the first uplink information is greater than or equal to the first predetermined time length; determine to skip or stop processing the first data, when the first time length is smaller than the first predetermined time length, and/or the second time length is smaller than the first predetermined time length; and process the first data and the second data, and transmit the first uplink information and the second uplink information to the network device via the transceiving unit <NUM>, when a fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information is greater than or equal to a sum of the first predetermined time length and a second predetermined time length, the second predetermined time length including processing time for the second data.

Optionally, as an embodiment, the fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information may be greater than or equal to the first predetermined time length, and the first predetermined time length may include the processing time for the first data; and/or, the third time length between the time domain position of the second downlink information and the time domain position of the second uplink information may be greater than or equal to the second predetermined time length, and the second predetermined time length may include the processing time for the second data.

Optionally, as an embodiment, the first predetermined time length may further include conversion time for the processing unit <NUM> to convert from processing the second data to processing the first data, and/or conversion time for the processing unit to convert from processing the first data to processing the second data, and/or the second predetermined time length may further include conversion time for the processing unit <NUM> to convert from processing the first data to processing the second data.

Optionally, as an embodiment, the first downlink information, the second downlink information, the first uplink information, and the second uplink information may satisfy at least one of the following conditions: the time domain position of the first downlink information being start time or end time for the transceiving unit <NUM> to receive the first downlink information; the time domain position of the second downlink information being start time or end time for the transceiving unit <NUM> to receive the second downlink information; the time domain position of the first uplink information being start time or end time of a time domain resource occupied by the first uplink information; and the time domain position of the second uplink information being start time or end time of a time domain resource occupied by the second uplink information.

Optionally, as an embodiment, the first time length to the fourth time length may satisfy at least one of the following conditions: the first time length being from end time for the transceiving unit <NUM> to receive the first downlink information to end time for the transceiving unit <NUM> to receive the second downlink information; the second time length being from start time of a time domain resource occupied by the second uplink information to start time of a time domain resource occupied by the first uplink information; the third time length being from end time for the transceiving unit <NUM> to receive the second downlink information to the start time of the time domain resource occupied by the second uplink information; and the fourth time length being from the end time for the transceiving unit <NUM> to receive the first downlink information to the start time of the time domain resource occupied by the first uplink information.

Optionally, as an embodiment, the first downlink information may be first uplink resource indication information, and the first uplink information may be a first physical uplink shared channel. The first uplink resource indication information may indicate a resource occupied by the first physical uplink shared channel, and the first physical uplink shared channel may carry the first data. The second downlink information may be second uplink resource indication information, and the second uplink information may be a second physical uplink shared channel. The second uplink resource indication information may indicate a resource occupied by the second physical uplink shared channel, and the second physical uplink shared channel may carry the second data.

Optionally, as an embodiment, the first downlink information may be a first physical downlink shared channel, and the first uplink information may be a first physical uplink control channel. The first physical downlink shared channel may carry the first data, and the first physical uplink control channel may carry feedback information for the first data. The second downlink information may be a second physical downlink shared channel, and the second uplink information may be a second physical uplink control channel. The second physical downlink shared channel may carry the second data, and the second physical uplink control channel may carry feedback information for the second data.

It can be appreciated that the above and other operations and/or functions of the respective units in the terminal device <NUM> according to the embodiment of the present disclosure can implement the corresponding processes performed by the terminal device in the method <NUM> as shown in <FIG>, and details thereof will be omitted here.

Therefore, in the terminal device according to the embodiment of the present disclosure, considering the HARQ-ACK feedback efficiency and system scheduling efficiency, the processing time interval corresponding to some PDSCH/PUSCH is typically much larger than the processing time of the terminal device of a processing capability. For example, there may be typically redundant, idle time within the PDSCH/PDSCH processing interval corresponding to an eMBB service. Thus, other data, such as a delay-sensitive URLLC service, can be processed within the time interval. In particular, the processing of high-priority data can be guaranteed according to the priority of the data, or the processing order can be properly arranged according to the processing time length of the data, so as to satisfy the low-latency scheduling requirements without significantly increasing the complexity of the terminal.

As shown in <FIG>, the network device <NUM> according to the embodiment of the present disclosure includes a processing unit <NUM> and a transceiving unit <NUM>. In particular, the transceiving unit <NUM> is configured to transmit first downlink information and second downlink information to a terminal device, the first downlink information having a time domain position earlier than a time domain position of the second downlink information, and first uplink information corresponding to the first downlink information having a time domain position later than a time domain position of second uplink information corresponding to the second downlink information. The processing unit <NUM> is configured to determine whether to receive the first uplink information and/or the second uplink information transmitted by the terminal device via the transceiving unit <NUM>.

Optionally, as an embodiment, the processing unit <NUM> may be further configured to: determine whether to receive the first uplink information and/or the second uplink information via the transceiving unit <NUM> based on time for the terminal device to process first data corresponding to the first downlink information and/or time for the terminal device to process second data corresponding to the second downlink information.

Optionally, as an embodiment, the processing unit <NUM> may be configured to perform at least one of: receive the first uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a first time length between the time domain position of the first downlink information and the time domain position of the second downlink information is greater than or equal to a first predetermined time length, the first predetermined time length including the time for the terminal device to process the first data; receive the first uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a second time length between the time domain position of the second uplink information and the time domain position of the first uplink information is greater than or equal to the first predetermined time length; determine that the terminal device skips or stops processing the first data, and/or determine not to receive the first uplink information at the time domain position of the first uplink information, when the first time length is smaller than the first predetermined time length and/or the second time length is smaller than the first predetermined time length; receive the second uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a third time length between the time domain position of the second downlink information and the time domain position of the second uplink information is greater than or equal to a second predetermined time length, the second predetermined time length including the time for the terminal device to process the second data; determine that the terminal device skips or stops processing the second data, and/or determine not to receive the second uplink information at the time domain position of the second uplink information, when the third time length is smaller than the second predetermined time length; receive the first uplink information and the second uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information is greater than or equal to a sum of the first predetermined time length and the second predetermined time length; and determine that the terminal device skips or stops processing the first data and/or the second data, when the fourth time length is smaller than the sum of the first predetermined time length and the second predetermined time length.

Optionally, as an embodiment, the processing unit <NUM> may be further configured to: determine whether to receive the first uplink information and/or the second uplink information via the transceiving unit <NUM> based on a priority of first data corresponding to the first downlink information and a priority of second data corresponding to the second downlink information.

Optionally, as an embodiment, the first downlink information may indicate the priority of the first data; and/or the second downlink information may indicate the priority of the second data.

Optionally, as an embodiment, the processing unit <NUM> may be further configured to perform at least one of: receive the first uplink information transmitted by the terminal device via the transceiving unit <NUM>, when the priority of the first data is higher than the priority of the second data; determine that the terminal device skips or stops processing the second data and determine not to receive the second uplink information at the time domain position of the second uplink information, when the priority of the first data is higher than the priority of the second data; receive the second uplink information transmitted by the terminal device via the transceiving unit <NUM>, when the priority of the first data is lower than the priority of the second data; determine that the terminal device skips or stops processing the first data and determine not to receive the first uplink information at the time domain position of the first uplink information, when the priority of the first data is lower than the priority of the second data; and determine whether to receive the first uplink information via the transceiving unit <NUM> based on time for the terminal device to process the first data, when the priority of the first data is lower than the priority of the second data.

Optionally, as an embodiment, when the priority of the first data is lower than the priority of the second data, the processing unit <NUM> may be configured to perform at least one of: receive the first uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a first time length between the time domain position of the first downlink information and the time domain position of the second downlink information is greater than or equal to a first predetermined time length, the first predetermined time length including the time for processing the first data; receive the first uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a second time length between the time domain position of the second uplink information and the time domain position of the first uplink information is greater than or equal to the first predetermined time length; determine that the terminal device skips or stops processing the first data and determine not to receive the first uplink information at the time domain position of the first uplink information, when the first time length is smaller than the first predetermined time length and/or the second time length is smaller than the first predetermined time length; and receive the first uplink information and the second uplink information transmitted by the terminal device via the transceiving unit <NUM>, when a fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information is greater than or equal to a sum of the first predetermined time length and the second predetermined time length, the second predetermined time length including processing time for the second data.

Optionally, as an embodiment, the fourth time length between the time domain position of the first downlink information and the time domain position of the first uplink information may be greater than or equal to the first predetermined time length, and the first predetermined time length may include the time for the terminal device to process the first data; and/or the third time length between the time domain position of the second downlink information and the time domain position of the second uplink information may be greater than or equal to the second predetermined time length, and the second predetermined time length may include the time for the terminal device to process the second data.

Optionally, as an embodiment, the first predetermined time length may further include conversion time for the terminal device to convert from processing the second data to processing the first data and/or conversion time for the terminal device to convert from processing the first data to processing the second data, and/or the second predetermined time length may further include conversion time for the terminal device to convert from processing the first data to processing the second data.

Optionally, as an embodiment, the first downlink information, the second downlink information, the first uplink information, and the second uplink information may satisfy at least one of the following conditions: the time domain position of the first downlink information being start time or end time of a time domain resource occupied by the first downlink information; the time domain position of the second downlink information being start time or end time of a time domain resource occupied by the second downlink information; the time domain position of the first uplink information being start time or end time of a time domain resource occupied by the first uplink information; the time domain position of the second uplink information being start time or end time of a time domain resource occupied by the second uplink information.

Optionally, as an embodiment, the first time length to the fourth time length may satisfy at least one of the following conditions: the first time length being from end time of a time domain resource occupied by the first downlink information to end time of a time domain resource occupied by the second downlink information; the second time length being from start time of a time domain resource occupied by the second uplink information to start time of a time domain resource occupied by the first uplink information; the third time length being from the end time of the time domain resource occupied by the second downlink information to the start time of the time domain resource occupied by the second uplink information; and the fourth time length being from the end time of the time domain resource occupied by the first downlink information to the start time of the time domain resource occupied by the first uplink information.

Optionally, as an embodiment, the first downlink information may be first uplink resource indication information, and the first uplink information may be a first physical uplink shared channel. The first uplink resource indication information may indicate a resource occupied by the first physical uplink shared channel, and the first physical uplink shared channel may carry first data. The second downlink information may be second uplink resource indication information, and the second uplink information may be a second physical uplink shared channel. The second uplink resource indication information may indicate a resource occupied by the second physical uplink shared channel, and the second physical uplink shared channel may carry second data.

It can be appreciated that the above and other operations and/or functions of the respective units in the network device <NUM> according to the embodiment of the present disclosure can implement the corresponding processes performed by the network device in the method <NUM> as shown in <FIG>, and details thereof will be omitted here.

Therefore, in the network device according to the embodiment of the present disclosure, considering the HARQ-ACK feedback efficiency of the terminal device and system scheduling efficiency, the processing time interval corresponding to some PDSCH/PUSCH is typically much larger than the processing time of the terminal device of a processing capability. For example, there may be typically redundant, idle time within the PDSCH/PUSCH processing interval corresponding to an eMBB service. Thus, the terminal device can process other data, such as a delay-sensitive URLLC service, within the time interval. In particular, the network device can configure the terminal device to guarantee the processing of high-priority data according to the priority of the data, or properly arrange the processing order according to the processing time length of the data, so as to satisfy the low-latency scheduling requirements without significantly increasing the complexity of the terminal.

<FIG> is a schematic diagram showing a structure of a communication device <NUM> according to an embodiment of the present disclosure. The communication device <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> can invoke and execute a computer program from a memory to perform the method according to any of the embodiments of the present disclosure.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a memory <NUM>. The processor <NUM> can invoke and execute a computer program from the memory <NUM> to perform the method according to any of the embodiments of the present disclosure.

Optionally, as shown in <FIG>, the communication device <NUM> may further include a transceiver <NUM>. The processor <NUM> can control the transceiver <NUM> to communicate with other devices, and in particular to transmit information or data to other devices or receive information or data transmitted by other devices.

Optionally, the communication device <NUM> may be the network device in the embodiment of the present disclosure, and the communication device <NUM> can perform corresponding procedures implemented by the network device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the communication device <NUM> may be the mobile terminal/terminal device in the embodiment of the present disclosure, and the communication device <NUM> can perform corresponding procedures implemented by the mobile terminal/terminal device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

<FIG> is a schematic diagram showing a structure of a chip according to an embodiment of the present disclosure. The chip <NUM> shown in <FIG> includes a processor <NUM>, and the processor <NUM> can invoke and execute a computer program from a memory to implement the method in the embodiment of the present disclosure.

Optionally, as shown in <FIG>, the chip <NUM> may further include a memory <NUM>. The processor <NUM> can invoke and execute a computer program from the memory <NUM> to implement the method in the embodiment of the present disclosure.

The memory <NUM> may be a separate device independent from the processor <NUM>, or may be integrated in the processor <NUM>.

Optionally, the chip <NUM> may further include an input interface <NUM>. The processor <NUM> can control the input interface <NUM> to communicate with other devices or chips, and in particular, obtain information or data transmitted by other devices or chips.

The processor <NUM> can control the output interface <NUM> to communicate with other devices or chips, and in particular, output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present disclosure, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of the present disclosure. For the sake of brevity, details thereof will be omitted here.

Optionally, the chip can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure, and the chip can implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present disclosure. For the sake of brevity, details thereof will be omitted here.

It can be appreciated that the chip in the embodiment of the present disclosure may also be referred to as a system-level chip, a system-chip, a chip system, a system-on-chip or the like.

Here, the terminal device <NUM> can be configured to implement the corresponding functions implemented by the terminal device in the above method, and the network device <NUM> can be configured to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, details thereof will be omitted here.

It is to be noted that the processor in the embodiment of the present disclosure may be an integrated circuit chip with signal processing capability. In an implementation, the steps of the above method embodiments can be implemented by hardware integrated logic circuits in a processor or instructions in the form of software. The processor can be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps, and logical block diagrams disclosed in the embodiments of the present disclosure can be implemented or performed. The general purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present disclosure may be directly embodied as being performed and completed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can be located in a known storage medium in the related art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or register. The storage medium can be located in the memory, and the processor can read information from the memory and perform the steps of the above methods in combination with its hardware.

It can be appreciated that the memory in the embodiments of the present disclosure may be a transitory memory or a non-transitory memory, or may include both transitory and non-transitory memories. Here, the non-transitory memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The transitory memory may be a Random Access Memory (RAM), which is used as an external cache. As illustrative, rather than limiting, examples, many forms of RAMs are available, including Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM) ), and Direct Rambus RAM (DR RAM). It is to be noted that the memory used for the system and method described in the present disclosure is intended to include, but not limited to, these and any other suitable types of memories.

An embodiment of the present disclosure also provides a computer-readable storage medium for storing a computer program.

Optionally, the computer-readable storage medium can be applied to the network device in the embodiment of the present disclosure, and the computer program can cause a computer to perform corresponding procedures implemented by the network device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure, and the computer program can cause a computer to perform corresponding procedures implemented by the mobile terminal/terminal device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the computer program product can be applied to the network device in the embodiment of the present disclosure, and the computer program instructions can cause a computer to perform corresponding procedures implemented by the network device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure, and the computer program instructions can cause a computer to perform corresponding procedures implemented by the mobile terminal/terminal device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the computer program can be applied to the network device in the embodiment of the present disclosure. The computer program, when executed on a computer, can cause the computer to perform corresponding procedures implemented by the network device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present disclosure. The computer program, when executed on a computer, can cause the computer to perform corresponding procedures implemented by the mobile terminal/terminal device in the method according to any of the embodiments of the present disclosure. Details thereof will be omitted here for simplicity.

It can be appreciated by those skilled in the art that units and algorithm steps in the examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or any combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on specific applications and design constraint conditions of the technical solutions. Those skilled in the art may use different methods for each specific application to implement the described functions, and such implementation is to be encompassed by the scope of this disclosure.

In the embodiments of the present disclosure, it can be appreciated that the disclosed systems, devices, and methods may be implemented in other ways. For example, the device embodiments described above are illustrative only. For example, the divisions of the units are only divisions based on logical functions, and there may be other divisions in actual implementations. For example, more than one unit or component may be combined or integrated into another system, or some features can be ignored or omitted. In addition, the mutual coupling or direct coupling or communicative connection as shown or discussed may be indirect coupling or communicative connection between devices or units via some interfaces which may be electrical, mechanical, or in any other forms.

Claim 1:
A data transmission method, comprising:
receiving, by a terminal device, first downlink information and second downlink information transmitted by a network device, the first downlink information having a time domain position earlier than a time domain position of the second downlink information; and
determining, by the terminal device, to process first data corresponding to the first downlink information and/or second data corresponding to the second downlink information, and transmitting first uplink information corresponding to the first downlink information and/or second uplink information corresponding to the second downlink information to the network device based on a result of the processing,
characterized in that, the first uplink information corresponding to the first downlink information has a time domain position later than a time domain position of the second uplink information corresponding to the second downlink information.