A method for resource scheduling and a communication device

Abstract

This application provides a resource scheduling method and a communication device. The method includes: receiving a first DCI and a second DCI; the first DCI scheduling a first PDSCH; and the second DCI scheduling a second PDSCH; determining that the first PDSCH and the second PDSCH satisfy the following conditions: the number of symbols between the first PDSCH and the second PDSCH is less than or equal to a threshold; the first PDSCH includes pre-DMRS and additional DMRS; and the second PDSCH does not include additional DMRS; skipping the decoding process of the second PDSCH; and / or sending a second HARQ-ACK message for the second PDSCH; and there is no third PDSCH between the first PDSCH and the second PDSCH. By having the UE determine that the first PDSCH and the second PDSCH satisfy a first predefined condition, this application can avoid the impact of the previous PDSCH on the processing time of the subsequent PDSCH.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for resource scheduling and a communication device. Background Technology

[0002] New Radio (NR) protocol release 15 (Rel-15) introduced the processing time T of the Physical Downlink Shared Channel (PDSCH). proc,1 Concept. Processing time T proc,1 The definition starts from the next symbol after the end time domain symbol of the PDSCH transmitted by the network device, and ends one time domain symbol before the start time domain symbol of the Physical Uplink Control Channel (PUCCH) transmitted by the terminal device. The terminal device needs to send the Hybrid Automatic Repeat-Request Acknowledgment (HARQ-ACK) information corresponding to the PDSCH on the PUCCH resource.

[0003] Processing time T proc,1 The length of a PDSCH is mainly related to the additional demodulation reference signal (DMRS). For example, if a PDSCH contains additional pilots, the terminal device needs to receive all the pilots before starting channel estimation, and then demodulation and decoding. If a PDSCH only contains the first column of pilots, the terminal device can start channel estimation after receiving the first column of pilots, thus shortening the processing time T. proc,1 .

[0004] Back-to-back scheduling refers to network devices scheduling two consecutive PDSCHs. If the preceding PDSCH has an additional pilot and the following PDSCH does not, the additional pilot in the preceding PDSCH will delay the processing time of the following PDSCH by the terminal device, which may prevent the terminal device from completing the processing within the time specified in the protocol.

[0005] Therefore, how to solve the problem of the existence of additional pilots in back-to-back scheduling is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] This application provides a resource scheduling method and communication device that can solve the problem in back-to-back scheduling scenarios where the previous PDSCH has an additional pilot and the next PDSCH does not, by avoiding the impact of at least one additional pilot included in the previous PDSCH on the processing time of the next PDSCH, thereby improving the resource scheduling efficiency of the network device and enhancing communication efficiency.

[0007] In a first aspect, a resource scheduling method is provided, comprising: receiving a first downlink control information (DCI) and a second DCI, wherein the first DCI is used to schedule a first physical downlink shared channel (PDSCH) and the second DCI is used to schedule a second PDSCH; determining that the first PDSCH and the second PDSCH satisfy a first predefined condition, wherein the first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold, the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS, and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS; skipping the decoding process of the second PDSCH, and / or sending a second hybrid automatic repeat request (HARQ) ACK information corresponding to the second PDSCH, wherein the end time-domain symbol of the first PDSCH precedes the start time-domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

[0008] Through the above technical solution, this application can avoid the impact of the additional pilots included in the previous PDSCH on the processing time of the subsequent PDSCH, thereby improving communication efficiency.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first DCI is DCI format 1_0 or DCI format 1_1 or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0010] In conjunction with the first aspect, in some implementations of the first aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0012] It should be understood that the three possible implementations of the first aspect mentioned above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0013] Secondly, a resource scheduling method is provided, comprising: receiving a first downlink control information (DCI) and a second DCI, wherein the first DCI is used to schedule a first physical downlink shared channel (PDSCH), and the second DCI is used to schedule a second PDSCH. The second DCI includes a time slot offset parameter, which is used to indicate that the number of time slots between the time slot in which the terminal device sends the second hybrid automatic repeat request acknowledgment (HARQ-ACK) information corresponding to the second PDSCH and the time slot in which the second PDSCH is located is N, where N is a positive integer; determining that N is less than or equal to a predefined second threshold; skipping the decoding process of the second PDSCH; and / or sending the second HARQ-ACK information, wherein the number of time slots between the time slot in which the second HARQ-ACK information is located and the time slot in which the second PDSCH is located is N, wherein the end time domain symbol of the first PDSCH is before the start time domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

[0014] Through the above technical solution, this application can avoid the impact of the additional pilots included in the previous PDSCH on the processing time of the subsequent PDSCH, thereby improving communication efficiency.

[0015] In conjunction with the second aspect, in some implementations of the second aspect, the first DCI is DCI format 1_0 or DCI format 1_1 or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0016] In conjunction with the second aspect, in some implementations of the second aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0017] In conjunction with the second aspect, in some implementations of the second aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0018] It should be understood that the three possible implementations of the second aspect described above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0019] Thirdly, a resource scheduling method is provided, comprising: determining that a first physical downlink shared channel (PDSCH) and a second PDSCH sent to a terminal device satisfy a second predefined condition, the second predefined condition comprising: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH being greater than or equal to a first threshold; the first PDSCH including a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; the second PDSCH including a second pre-demodulation reference signal (DMRS) and not including additional DMRS; and sending a first downlink control information (DCI), a second DCI, the first PDSCH, and the second PDSCH, wherein the first DCI is used to schedule the first PDSCH, the second DCI is used to schedule the second PDSCH, wherein the end time-domain symbol of the first PDSCH precedes the start time-domain symbol of the second PDSCH, and there is no third PDSCH sent to the terminal device between the first PDSCH and the second PDSCH.

[0020] By determining whether the first PDSCH and the second PDSCH meet the second predefined conditions through the network device, the network device can schedule the first PDSCH and the second PDSCH normally. Thus, this application can achieve the following in back-to-back scheduling scenarios: when the first PDSCH has an additional pilot and the second PDSCH does not have an additional pilot, the processing time of the first PDSCH is avoided, thereby improving communication efficiency.

[0021] In conjunction with the third aspect, in some implementations of the third aspect, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0022] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0023] In conjunction with the third aspect, in some implementations of the third aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0024] It should be understood that the three possible implementations of the third aspect mentioned above can be combined with each other. For example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0025] Fourthly, a resource scheduling method is provided, comprising: determining that a first physical downlink control channel (PDSCH) and a second PDSCH sent to a terminal device satisfy a first predefined condition, the first predefined condition including: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; the second PDSCH includes a second pre-demodulation reference signal (DMRS) but does not include additional DMRS; and transmitting a first downlink control information (DCI), a second DCI, the first PDSCH, and the second PDSCH, wherein... The second DCI includes a time slot offset parameter, which is used to indicate the number of time slots N between the time slot where the terminal device sends the second hybrid automatic repeat request response (HARQ-ACK) information corresponding to the second PDSCH and the time slot where the second PDSCH is located. N is greater than or equal to a predefined second threshold, and N is a positive integer. The first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH. The end time domain symbol of the first PDSCH is before the start time domain symbol of the second PDSCH, and there is no third PDSCH sent to the terminal device between the first PDSCH and the second PDSCH.

[0026] By determining or judging that the first PDSCH and the second PDSCH meet the first predefined condition through the network device, the network device can schedule the first PDSCH and the second PDSCH normally. Thus, this application can achieve the following in the back-to-back scheduling scenario: when the first PDSCH has an additional pilot and the second PDSCH does not have an additional pilot, the processing time of the first PDSCH is avoided, thereby improving communication efficiency.

[0027] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0028] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0029] Fifthly, a resource scheduling method is provided, comprising: determining that a first physical downlink control channel (PDSCH) and a second PDSCH sent to a terminal device satisfy a first predefined condition, the first predefined condition comprising: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; the second PDSCH includes a second pre-demodulation DMRS and does not include additional DMRS; transmitting a first downlink control information (DCI), a third DCI, the first PDSCH, and the third PDSCH, wherein the first DCI is used to schedule the first PDSCH, the third DCI is used to schedule the third PDSCH, wherein the end time-domain symbol of the first PDSCH is before the start time-domain symbol of the second PDSCH, and there is no fourth PDSCH sent to the terminal device between the first PDSCH and the second PDSCH, wherein the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the third PDSCH is K, and K is greater than or equal to the first threshold.

[0030] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method also includes: not sending a second PDSCH.

[0031] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0032] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0033] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0034] It should be understood that the last three possible implementations of the fifth aspect mentioned above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0035] A sixth aspect provides a resource communication device, comprising: a transceiver unit for receiving a first downlink control information (DCI) and a second DCI, wherein the first DCI is used to schedule a first physical downlink shared channel (PDSCH) and the second DCI is used to schedule a second PDSCH; a processing unit for determining that the first PDSCH and the second PDSCH satisfy a first predefined condition, wherein the first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold, the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS, and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS; a processing unit for skipping the decoding process of the second PDSCH; and / or, the transceiver unit for sending a second hybrid automatic repeat request (HARQ) ACK information corresponding to the second PDSCH, wherein the end time-domain symbol of the first PDSCH precedes the start time-domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

[0036] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0037] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0038] In conjunction with the sixth aspect, in some implementations of the sixth aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0039] It should be understood that the three possible implementations of the sixth aspect mentioned above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0040] A seventh aspect provides a communication device, comprising: a transceiver unit, configured to receive a first downlink control information (DCI) and a second DCI, wherein the first DCI is used to schedule a first physical downlink shared channel (PDSCH), and the second DCI is used to schedule a second PDSCH, the second DCI including a time slot offset parameter, the time slot offset parameter being used to indicate that the number of time slots between the time slot in which the terminal device sends a second hybrid automatic repeat request acknowledgment (HARQ-ACK) information corresponding to the second PDSCH and the time slot in which the second PDSCH is located is N, where N is a positive integer; and determining that N is less than or equal to a predefined second threshold; a processing unit, configured to skip decoding processing of the second PDSCH; and / or, the transceiver unit, configured to send the second HARQ-ACK information, wherein the number of time slots between the time slot in which the second HARQ-ACK information is located and the time slot in which the second PDSCH is located is N, wherein the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

[0041] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0042] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0043] In conjunction with the seventh aspect, in some implementations of the seventh aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0044] It should be understood that the three possible implementations of the seventh aspect mentioned above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0045] Eighthly, a communication device is provided, comprising: a processing unit configured to determine that a first physical downlink shared channel (PDSCH) and a second PDSCH transmitted to a terminal device satisfy a second predefined condition, the second predefined condition comprising: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH being greater than or equal to a first threshold; the first PDSCH including a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; and the second PDSCH including a second pre-demodulation DMRS and excluding the additional DMRS; and a transceiver unit configured to transmit a first downlink control information (DCI), a second DCI, the first PDSCH, and the second PDSCH, wherein the first DCI is used to schedule the first PDSCH, the second DCI is used to schedule the second PDSCH, and the end time-domain symbol of the first PDSCH precedes the start time-domain symbol of the second PDSCH, and there is no third PDSCH transmitted to the terminal device between the first PDSCH and the second PDSCH.

[0046] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the first DCI is DCI format 1_0 or DCI format 1_1 or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0047] In conjunction with aspect eight, in some implementations of aspect eight, the cyclic redundancy check (CRC) code of DCI format 1_0 is scrambled by the cell radio network temporary identifier (C-RNTI), the configured scheduling radio network temporary identifier (CS-RNTI), or the modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI).

[0048] In conjunction with the eighth aspect, in some implementations of the eighth aspect, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0049] It should be understood that the three possible implementations of the eighth aspect mentioned above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0050] A ninth aspect provides a communication device, comprising: a processing unit configured to determine that a first physical downlink control channel (PDSCH) and a second PDSCH transmitted to a terminal device satisfy a first predefined condition, the first predefined condition including: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; the second PDSCH includes a second pre-demodulation reference signal (DMRS) but does not include additional DMRS; and a transceiver unit configured to transmit first downlink control information (DCI), the second DCI, the first PDSCH, and the second PDSCH. CH, wherein the second DCI includes a time slot offset parameter, which is used to indicate the number of time slots N between the time slot in which the terminal device sends the second hybrid automatic repeat request response (HARQ-ACK) information corresponding to the second PDSCH and the time slot in which the second PDSCH is located, where N is greater than or equal to a predefined second threshold and N is a positive integer, wherein the first DCI is used to schedule the first PDSCH and the second DCI is used to schedule the second PDSCH, wherein the end time domain symbol of the first PDSCH is before the start time domain symbol of the second PDSCH, and there is no third PDSCH sent to the terminal device between the first PDSCH and the second PDSCH.

[0051] In conjunction with the ninth aspect, in some implementations of the ninth aspect, the first DCI is DCI format 1_0 or DCI format 1_1 or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0052] In conjunction with aspect nine, in some implementations of aspect nine, the Cyclic Redundancy Check (CRC) code of DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

[0053] It should be understood that the two possible implementations of the ninth aspect above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0054] A tenth aspect provides a communication device, comprising: a processing unit configured to determine that a first physical downlink control channel (PDSCH) and a second PDSCH transmitted to a terminal device satisfy a first predefined condition, the first predefined condition including: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold, the first PDSCH including a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS, and the second PDSCH including a second pre-demodulation DMRS and excluding the additional DMRS; and a transceiver unit configured to transmit a first downlink control information (DCI), a third DCI, the first PDSCH, and the third PDSCH, wherein the first DCI is used to schedule the first PDSCH, the third DCI is used to schedule the third PDSCH, wherein the end time-domain symbol of the first PDSCH precedes the start time-domain symbol of the second PDSCH, and there is no fourth PDSCH transmitted to the terminal device between the first PDSCH and the second PDSCH, wherein the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the third PDSCH is K, and K is greater than or equal to the first threshold.

[0055] In conjunction with aspect ten, in some implementations of aspect ten, the transceiver unit is also used to not send a second PDSCH.

[0056] In conjunction with aspect ten, in some implementations of aspect ten, the first DCI is DCI format 1_0 or DCI format 1_1 or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0057] In conjunction with aspect ten, in some implementations of aspect ten, the cyclic redundancy check (CRC) code of DCI format 1_0 is scrambled by the cell radio network temporary identifier (C-RNTI), the configured scheduling radio network temporary identifier (CS-RNTI), or the modulation and coding scheme cell radio network temporary identifier (MCS-C-RNTI).

[0058] In conjunction with aspect ten, in some implementations of aspect ten, the HARQ-ACK information includes NACK, and a 0 value in the HARQ-ACK information corresponds to NACK.

[0059] It should be understood that the last three possible implementations of the tenth aspect above can be combined with each other, for example, the first possible implementation can be combined with the second possible implementation, the first possible implementation can be combined with the third possible implementation, and so on.

[0060] Eleventhly, a computer storage medium is provided, storing instructions that, when executed on a computer, cause the computer to perform a resource scheduling method as described in the first aspect and any possible implementation thereof; or, the computer to perform a resource scheduling method as described in the second aspect and any possible implementation thereof.

[0061] In a twelfth aspect, a computer storage medium is provided, storing instructions that, when executed on a computer, cause the computer to perform a resource scheduling method as described in the third aspect and any possible implementation thereof; or, the computer to perform a resource scheduling method as described in the fourth aspect and any possible implementation thereof; or, the computer to perform a resource scheduling method as described in the fifth aspect and any possible implementation thereof.

[0062] In a thirteenth aspect, a computer program product is provided that, when the computer program product is run on a computer, causes the computer to perform a resource scheduling method as described in the first aspect and any possible implementation thereof; or, to perform a resource scheduling method as described in the second aspect and any possible implementation thereof.

[0063] In a fourteenth aspect, a computer program product is provided that, when the computer program product is run on a computer, causes the computer to perform a resource scheduling method as described in the third aspect and any possible implementation thereof; or, a resource scheduling method as described in the fourth aspect and any possible implementation thereof; or, a resource scheduling method as described in the fifth aspect and any possible implementation thereof. Attached Figure Description

[0064] Figure 1 This is a schematic diagram of an application scenario provided in this application.

[0065] Figure 2 This is a schematic diagram of a method for scheduling PDSCH resources provided in this application.

[0066] Figure 3 This is a schematic diagram of a back-to-back scheduling method provided in this application.

[0067] Figure 4 This is a schematic flowchart of a resource scheduling method provided in this application.

[0068] Figure 5 This is a schematic flowchart illustrating another resource scheduling method provided in this application.

[0069] Figure 6This is a schematic flowchart illustrating another resource scheduling method provided in this application.

[0070] Figure 7 This is a schematic flowchart illustrating another resource scheduling method provided in this application.

[0071] Figure 8 This is a schematic flowchart illustrating yet another resource scheduling method provided in this application.

[0072] Figure 9 This is a schematic block diagram of the structure of a communication device provided in this application.

[0073] Figure 10 This is a schematic block diagram of the structure of another communication device provided in this application. Detailed Implementation

[0074] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0075] The technical solutions of this application embodiment can be applied to various communication systems, such as Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), 5th Generation (5G) systems or New Radio (NR), and future communication systems such as 6th Generation (6G) systems.

[0076] The terminal device in this application embodiment can be referred to as a terminal, which can be a device with wireless transceiver capabilities. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can also be deployed in the air (such as on airplanes, balloons, and satellites). The terminal device can be a user equipment (UE), where the UE includes a handheld device, vehicle-mounted device, wearable device, or computing device with wireless communication capabilities. For example, the UE can be a mobile phone, tablet computer, or computer with wireless transceiver capabilities. The terminal device can also be a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city, a wireless terminal in a smart home, and so on. In this application embodiment, the device used to implement the terminal's functions can be the terminal itself; it can also be a device capable of supporting the terminal in implementing these functions, such as a chip system, which can be installed in the terminal. In this application embodiment, the chip system may be composed of chips, or it may include chips and other discrete devices. In the technical solution of this application embodiment, the device for implementing the functions of the terminal is a terminal, and the terminal is a UE as an example to describe the technical solution of this application embodiment.

[0077] The network devices in this application embodiment include access network devices, such as base stations (BS). A BS can be a device deployed in a wireless access network capable of wirelessly communicating with terminals. Base stations may take various forms, such as macro base stations, micro base stations, relay stations, and access points. For example, the base station involved in this application embodiment can be a 5G base station or an evolved Node B (eNB) in LTE. The 5G base station can also be called a transmission reception point (TRP) or a 5G base station (next-generation node B, gNB). In this application embodiment, the apparatus for implementing the functions of the network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing that function, such as a chip system, which can be installed in the network device. In the technical solutions of this application embodiment, the apparatus for implementing the functions of the network device is a network device, and the network device is a base station, as an example, to describe the technical solutions of this application embodiment.

[0078] In the embodiments of this application, the term "wireless communication" can also be abbreviated as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0079] Figure 1 A schematic diagram of a communication system #100 applicable to the technical solution of this application is shown. Specifically, as follows... Figure 1 As shown, the communication system #100 includes network device #101 and UE #102. Network device #101 can be any of the network devices listed above, and UE #102 can be any of the terminal devices listed above.

[0080] exist Figure 1 In the communication system #100 shown, the transmission between network device #101 and UE #102 can be achieved through radio waves, or through transmission media such as visible light, laser, infrared, or optical fiber. This application does not make any specific limitation in this regard.

[0081] Figure 2 This illustration shows a schematic diagram of a method for scheduling PDSCH resources provided in this application. Specifically, as shown... Figure 2 As shown.

[0082] Specifically, network devices schedule PDSCH resources via the physical downlink control channel (PDCCH) and include control information, such as downlink control information (DCI), in the PDCCH to inform the UE of the relevant information in the PUCCH carrying the HARQ-ACK information corresponding to the PDSCH. The UE cannot send the HARQ-ACK information corresponding to the PDSCH before the start time domain symbol of the PUCCH resource; otherwise, it will be unable to process the data within time T. proc,1 The PDSCH is not processed within the network device, thus preventing the transmission of the HARG-ACK information corresponding to the PDSCH on the PUCCH resource indicated by the network device.

[0083] It should be understood that the processing time T proc,1 The length and N1 and d 1,1 These two parameters are positively correlated. N1 is a predefined set of values ​​in the protocol, related to the UE's capability reporting information and subcarrier spacing. Table 1 shows the N1 of the PDSCH corresponding to the UE's processing capability 1 (Cap1). (Alternatively, N1 can be considered as the processing time T.) proc,1Table 2 shows the N2 of PDSCH corresponding to the UE's PDSCH processing capability 2 (Cap2) (as before). Specific details are shown in Tables 1 and 2.

[0084] Table 1

[0085]

[0086] Table 2

[0087]

[0088] It should be understood that the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols in the left column of Table 1 is significantly greater than the number of OFDM symbols in the right column. This indicates that the UE's processing time for PDSCH is shorter when no additional pilots are present. Therefore, network devices can schedule the corresponding PUCCH closer to the time-domain symbol position of the corresponding PDSCH. The number of OFDM symbols in Table 2 is less than that in Table 1. This indicates that the UE's processing time for PDSCH is shorter when processing capability 2 is achieved. However, this places higher demands on the UE's processing capabilities. Therefore, network devices can schedule the corresponding PUCCH closer to the time-domain symbol position of the corresponding PDSCH.

[0089] Generally speaking, after determining N1, the UE also needs to determine d. 1,1 Only then can the processing time T of PDSCH be finally determined. proc,1 . d 1,1 This is a variable related to the number of overlapping OFDM symbols between the scheduling PDCCH and the scheduled PDSCH. 1,1 The definition varies depending on different UE capability reporting and PDSCH mapping types. The technical solutions in this application embodiment do not involve d. 1,1 The changes are too numerous to detail here.

[0090] Generally, when a UE reports to the network device that it supports PDSCH processing capability 2 in a certain subcarrier interval, the network device can configure whether the cell to which the UE belongs is enabled for PDSCH processing capability 2 through radio resource control (RRC) parameters. If enabled, the UE also needs to combine another condition to determine whether it can process PDSCH according to PDSCH processing capability 2, that is, whether it can process the PDSCH according to N1 defined in Table 2.

[0091] The other condition refers to the UE needing to determine whether the dmrs-AdditionalPosition contained in the higher-layer parameters dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB is configured as 'pos0'. For example:

[0092] If dmrs-AdditionalPosition is configured as 'pos0' in both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, and the network device is configured to enable PDSCH processing capability 2 for the cell (e.g., through the higher-layer parameter processingType2Enabled), then the UE will perform PDSCH processing according to N1 defined in Table 2, and the network device needs to refer to N1 defined in Table 2 for PUCCH scheduling.

[0093] If dmrs-AdditionalPosition in 2-dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB is configured as 'pos0', and the network device is configured to not enable PDSCH processing capability 2 (i.e., according to PDSCH processing capability 1), then the UE will perform PDSCH processing according to N1 defined in the left column of Table 1, and the network device needs to refer to N1 defined in the left column of Table 2 for PUCCH scheduling.

[0094] If at least one of the dmrs-AdditionalPosition configurations in dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB is not 'pos0' or at least not configured, and the network device configures the cell to not enable PDSCH processing capability 2 (i.e., according to PDSCH processing capability 1), then the UE performs PDSCH processing according to N1 defined in the right column of Table 1, and the network device needs to refer to N1 defined in the right column of Table 2 for PUCCH scheduling.

[0095] The following section further explains the relationship between high-level parameter configuration and PDSCH processing time.

[0096] Network devices can schedule PDSCHs using DCI formats 1_0, 1_1, and 1_2. DCI formats 1_1 and 1_2 each have their corresponding higher-layer parameter dmrs-AdditionalPosition, meaning network devices can configure specific higher-layer parameters through DCI formats 1_1 and 1_2 to schedule PDSCHs. It should be understood that whether the PDSCHs scheduled by the network device have additional pilots depends on the values ​​of the higher-layer parameters. For example, if the network device configures dmrs-AdditionalPosition to pos1, pos2, or pos3, it means that the PDSCHs scheduled using DCI formats 1_1 or 1_2 may have additional pilots.

[0097] For PDSCH mapping type A, when the OFDM symbol length of the PDSCH scheduled by the network device is l d When there are more than 7 OFDM symbols, additional pilot signals will exist. For example, dmrs-AdditionalPosition = 'pos2', l d =13. From Table 3, we know that this PDSCH contains 13 consecutive OFDM symbols, including the first column of pilots (front-loaded DMRS) and two additional pilots. The positions of the first column of pilots and the two additional pilots are respectively at symbols 10, 7, and 11. For example, dmrs-AdditionalPosition = 'pos0', l d =13. As can be seen from Table 3, this PDSCH contains 13 consecutive OFDM symbols, and only the first column of pilots is included. Its position is L0, and it does not contain any additional pilots.

[0098] Table 3

[0099]

[0100]

[0101] Specifically, the l in the first column of Table 1 d The value represents the number of time-domain symbols occupied in one transmission (one PDSCH). In PUSCH resource mapping type Type B, the candidate values ​​for the DMRS Additional Position (dmrs-Additional Position) are {0, 1, 2, 3}, representing the number of additional DMRSs as 0, 1, 2, and 3, respectively. The value of dmrs-Additional Position is configured by the network device through higher-layer signaling, where l0 refers to the front-end DMRS.

[0102] It should be noted that in the embodiments of this application, the first pilot is equivalent to the pre-DMRS, the additional pilot is equivalent to the supplementary DMRS, and the time domain symbol is mainly in the form of OFDM symbol. This will be explained uniformly here and will not be repeated later.

[0103] It should be understood that the protocol has specific definitions for network devices scheduling PDSCH based on DCI format 1_0. For example, when a network device schedules mapping type A and mapping type B based on DCI format 1_0, the value of the higher-layer parameter dmrs-AdditionalPosition corresponding to this DCI format 1_0 is considered as 'pos2', that is, the OFDM symbol length l of the PDSCH scheduled by the network device for mapping type A based on DCI format 1_0 is... d When the value is greater than 7, the PDSCH includes at least one additional pilot column (number), and the OFDM symbol length of the PDSCH for scheduling mapping type B is l. d When the value is greater than 4, the PDSCH includes at least one additional pilot. Otherwise, PDSCHs scheduled by network devices based on DCI format 1_0 will not include additional pilots.

[0104] Since the higher-layer parameter dmrs-AdditionalPosition value corresponding to the PDSCH scheduled in DCI format 1_0 is regarded as 'pos2' in the protocol, and referring to Tables 1 and 2, it can be seen that the UE's processing time for this PDSCH will always use the time defined in the right column of Table 1, and will not use N1 defined in the left column of Table 1, nor will it use N1 defined in Table 2, because the number of OFDM symbols in the scheduled PDSCH is l d In longer cases, the PDSCH will always include additional pilot signals, which requires the UE to process the PDSCH for a longer period of time. In addition, this is also to avoid the PDSCH processing time varying with dynamic parameters.

[0105] For example, if the UE reports PDSCH processing capability 2 to the network device, and the network device enables PDSCH processing capability 2 for a cell to which the UE belongs through higher-layer parameters, and also configures the higher-layer parameter dmrs-AdditionalPosition corresponding to DCI format 1_1 to be 'pos0', then when the UE receives a PDSCH scheduled by the network device based on DCI format 1_1, since the network device has enabled cell-based PDSCH processing capability 2 and the higher-layer parameter dmrs-AdditionalPosition corresponding to DCI format 1_1 is 'pos0', the UE will use N1 as defined in Table 2 to process the PDSCH. However, if the network device has enabled cell-based PDSCH processing capability 2, and the UE receives a PDSCH scheduled by the network device based on DCI format 1_0, then the UE will still use N1 as defined in the right column of Table 1.

[0106] As mentioned above, whether the UE can process PDSCH according to the time defined in Table 2 depends more on the DCI format type of the network device configuration received by the UE. Therefore, the DCI format type will affect the processing time of the UE in processing PDSCH.

[0107] It should be understood that back-to-back scheduling refers to a network device scheduling two consecutive PDSCHs together. For example, if the network device needs to schedule a first PDSCH and a second PDSCH for the same terminal device, and there are no other PDSCHs scheduled for that terminal device between them, and the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, then if the first PDSCH includes a pre-DMRS and at least one additional DMRS, and the second PDSCH only includes a pre-DMRS and does not include additional DMRS, the UE must receive all the pilots of the first PDSCH before it can process the first PDSCH. This will delay the UE's processing time for the second PDSCH, potentially preventing the UE from completing the processing within the time specified in the protocol.

[0108] It should be understood that the time specified here refers to the minimum processing time of PDSCH as defined by the protocol. The network device may schedule the UE to provide HARQ-ACK information feedback for the second PDSCH after this minimum processing time. Figure 3 This application provides a schematic diagram of a back-to-back scheduling scenario, specifically as follows: Figure 3 As shown.

[0109] More specifically, in the back-to-back scheduling scenario described above, if the UE reports the capability information of the first PDSCH as processing capability 1, the network device's configured DCI format is 1_0 (the higher-layer parameter dmrs-AdditionalPosition is 'pos2'), and the UE reports the capability information of the second PDSCH as processing capability 2, the network device's configured DCI format is 1_1, for example, the higher-layer parameter dmrs-AdditionalPosition is 'pos0', then the additional pilots included in the first PDSCH will delay the UE's processing time for the second PDSCH.

[0110] Currently, existing protocols have proposed several solutions to this technical problem, such as:

[0111] 1) The UE does not expect the network device to schedule unicast PDSCH based on DCI format 1_0, which involves two specific scenarios: d >7 (mapping type A) or l d >4 (mapping type B). Unicast PDSCH is relative to broadcast PDSCH. Broadcast PDSCH means that the PDSCH carries broadcast information, while unicast means that the PDSCH carries UE-specific information.

[0112] 2) The UE does not expect the network device to schedule unicast PDSCH based on DCI format 1_0.

[0113] 3) Regardless of whether the first PDSCH contains additional DM-RS, the UE's processing capability for the second PDSCH must be processing capability 2.

[0114] 4) Regardless of whether the first PDSCH contains additional DM-RS, the UE's processing capability for the second PDSCH must be processing capability 2, but the UE does not expect to process any additional DM-RS in the first PDSCH, thus keeping the pilot mapping and rules unchanged.

[0115] 5) Regardless of whether the first PDSCH contains additional DM-RS, the UE's processing capability for the second PDSCH must be processing capability 2. However, the UE does not expect to process any additional DM-RS in the first PDSCH and updates the pilot mapping rules: When the network device enables the cell's processing capability 2 but does not configure additional DM-RS in the first PDSCH, the UE assumes that the higher-layer parameter dmrs-AdditionalPosition of the first PDSCH is 'pos0'.

[0116] 6) Network devices can schedule unicast PDSCHs of all lengths based on DCI format 1_0. For example, in back-to-back scheduling, the first PDSCH is scheduled by the network device based on DCI format 1_0 and requires processing using N1 defined in the table corresponding to PDSCH processing capability 1. The second PDSCH is scheduled by the network device based on DCI format 1_1 and, according to the RRC parameter configuration, requires processing using N1 defined in the table corresponding to PDSCH processing capability 2. When the number of OFDM symbols of the PDSCH scheduled by the network device is l... d >7 (mapping type A) or l d When the value is >4 (mapping type B), the processing time of the UE for PDSCH will revert from the processing time based on processing capability 2 to the processing time based on processing capability 1.

[0117] However, the above-mentioned technical solution 1 imposes limitations on network device scheduling, preventing network devices from using DCI format 1_0 to schedule PDSCHs with a large number of OFDM symbols. Technical solution 2 imposes too many restrictions on network device scheduling, completely preventing network devices from using DCI format 1_0 to schedule unicast PDSCHs. Technical solution 3 places too high demands on the UE's processing capabilities, potentially leading to implementation issues. Technical solution 4 does not process additional pilot signals, which significantly impacts PDSCH performance in scenarios with low signal-to-interference-plus-noise ratio (SINR), high Doppler, and high spread latency, such as when the UE is in a high-speed movement scenario. Furthermore, the above technical solutions are all based on unicast PDSCHs. However, in back-to-back scheduling scenarios, if the first PDSCH is a broadcast PDSCH, even if the UE does not need to send corresponding HARQ-ACK feedback for that PDSCH, the UE's processing time for that broadcast PDSCH will still affect the UE's processing time for subsequent PDSCHs.

[0118] Furthermore, in back-to-back scheduling scenarios, the first PDSCH uses PDSCH processing capability 1, and the second PDSCH uses PDSCH processing capability 2. Since the processing time of the second PDSCH requires the time defined in Table 2, which is very short, the processing time of the first PDSCH has a significant impact on the processing time of the second PDSCH. Even if both PDSCHs use PDSCH processing capability 1, the processing time of the preceding PDSCH will still affect the processing time of the following PDSCH.

[0119] In view of the above-mentioned technical problems, this application provides a new resource scheduling method and communication device, which can solve the technical problem of avoiding the processing time of the first PDSCH from affecting the processing time of the second PDSCH when there is an additional pilot for the first PDSCH in a back-to-back scheduling scenario.

[0120] Figure 4 A flowchart illustrating a resource scheduling method #400 provided in this application is shown. The main implementers of this method are network devices and UEs, as detailed below. Figure 4 As shown.

[0121] S410, the network device sends the first DCI and the second DCI, the first PDSCH and the second PDSCH.

[0122] Correspondingly, the UE receives the first DCI, the second DCI, and the first PDSCH from the network device.

[0123] It should be understood that the first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH.

[0124] S420, the UE determines that the first PDSCH and the second PDSCH satisfy the first predefined condition.

[0125] It should be understood that the first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS.

[0126] It should be understood that when the UE determines that the first PDSCH and the second PDSCH meet the first predefined condition, it determines that the first PDSCH and the second PDSCH belong to a back-to-back scheduling scenario. In other words, the UE can regard the scheduling of the network device in this instance as a scheduling that the UE does not expect, and can formulate corresponding actions based on the judgment result.

[0127] It should be understood that the first threshold can be predefined or configured by the network device. The first threshold can be 0, 1, 2, etc., and this application does not specifically limit it in this regard.

[0128] S430, skip the decoding process of the second PDSCH, and / or send the second HARQ-ACK information corresponding to the second PDSCH.

[0129] It should be understood that skipping the decoding process of the second PDSCH can be interpreted as the terminal device not performing decoding on the second PDSCH, or it can be interpreted as not performing any processing on the second PDSCH, including not performing channel estimation, demodulation, or other processing. It can also be interpreted as not performing any reception operation on the second PDSCH. This will be explained uniformly here and will not be elaborated further below.

[0130] It should be understood that, in the back-to-back scheduling scenario described above, the UE may skip the decoding process of the second PDSCH and / or send the second HARQ-ACK information corresponding to the second PDSCH.

[0131] As one possible implementation, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0132] As one possible implementation, the cyclic redundancy check (CRC) code of DCI format 1_0 is scrambled by the cell-radio network temporary identifier (C-RNTI), the configured scheduling RNTI (CS-RNTI), or the modulation and coding scheme-C-RNTI (MCS-C-RNTI).

[0133] As one possible implementation, HARQ-ACK information includes NACK, where a value of 0 in HARQ-ACK information corresponds to NACK.

[0134] It should be understood that the end domain symbol of the first PDSCH precedes the start domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

[0135] The UE determines that the scheduling of the first PDSCH and the second PDSCH belongs to a back-to-back scheduling scenario by determining that the first PDSCH and the second PDSCH meet the first predefined condition, and thus can take corresponding actions, such as skipping the decoding process of the second PDSCH and / or sending the second HARQ-ACK information.

[0136] This technical solution enables the application to avoid the impact of the additional pilots included in the previous PDSCH on the processing time of the subsequent PDSCH, thereby improving communication efficiency.

[0137] Figure 5 A flowchart illustrating a resource scheduling method #500 provided in this application is shown. The main implementers of this method are network devices and UEs, as detailed below. Figure 5 As shown.

[0138] S510, the network device sends the first DCI and the second DCI, the first PDSCH and the second PDSCH.

[0139] Correspondingly, the UE receives the first DCI, the second DCI, and the first PDSCH from the network device.

[0140] It should be understood that the first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH.

[0141] The second DCI includes a time slot offset parameter, which indicates that the time slot in which the terminal device sends the second HARQ-ACK information corresponding to the second PDSCH is separated from the time slot in which the second PDSCH is located by an interval of N, where N is a positive integer. This time slot offset parameter can be the PDSCH-to-HARQ_feedback timingindicator field in the second DCI.

[0142] S520, the UE determines that N is less than or equal to a predefined second threshold.

[0143] It should be understood that when the UE determines, based on the time slot offset parameter in the second DCI, that the number of time slots between the time slot where the second HARQ-ACK information is fed back and the time slot where the second PDSCH is located is less than a predefined second threshold, it determines that it cannot complete the processing of the second PDSCH within the specified processing time. At this time, the UE can take corresponding actions.

[0144] It should be understood that the second threshold can be predefined or configured by the network device, and the second threshold can be 0, 1, 2, etc. This application does not make any specific limitation in this regard.

[0145] S530 skips the decoding process of the second PDSCH and / or sends the second HARQ-ACK message.

[0146] It should be understood that the UE may skip the decoding process of the second PDSCH and / or send the second HARQ-ACK information, thereby avoiding the inability to process the second PDSCH within the specified processing time.

[0147] As one possible implementation, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0148] As one possible implementation, the CRC of DCI format 1_0 is scrambled with C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0149] As one possible implementation, HARQ-ACK information includes NACK, where a value of 0 in HARQ-ACK information corresponds to NACK.

[0150] The UE determines, based on the time slot offset parameter in the second DCI, that when the number of time slots between the time slot containing the second HARQ-ACK information and the time slot containing the second PDSCH is less than a predefined second threshold, it can take corresponding actions. For example, it can skip the decoding process of the second PDSCH and / or send the second HARQ-ACK information.

[0151] This technical solution enables the application to avoid the impact of the additional pilots included in the previous PDSCH on the processing time of the subsequent PDSCH, thereby improving communication efficiency.

[0152] Figure 6 A flowchart illustrating a resource scheduling method #600 provided in this application is shown. The main implementers of this method are network devices and UEs, as detailed below. Figure 6 As shown.

[0153] S610, determine that the first PDSCH and the second PDSCH satisfy the second predefined condition.

[0154] It should be understood that the second predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is greater than or equal to the second threshold; the first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS.

[0155] It should be understood that network devices determine or perform PDSCH scheduling based on the UE's processing time for PDSCH or its processing capability for PDSCH.

[0156] Specifically, if the network device determines that the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is greater than or equal to the first threshold, and the first PDSCH includes a first pre-DMRS and at least one first additional DMRS, and the second PDSCH only includes a second pre-DMRS and does not include additional DMRS, then the network device determines that the first PDSCH will not affect the processing time of the second PDSCH, and the network device can schedule the first PDSCH and the second PDSCH normally.

[0157] It should be understood that the first threshold can be predefined or configured by the network device, and the first threshold can be 0, 1, 2, etc. This application does not make any specific limitation in this regard.

[0158] S620 transmits the first DCI, the second DCI, the first PDSCH, and the second PDSCH.

[0159] Correspondingly, the UE receives the first DCI, the second DCI, the first PDSCH, and the second PDSCH.

[0160] It should be understood that once the network device determines that the first PDSCH will not affect the processing time of the second PDSCH, it can send the first PDSCH and the second PDSCH to the UE.

[0161] It should be understood that the first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH.

[0162] It should be noted that there is no PDSCH between the first PDSCH and the second PDSCH that network devices use to send to other UEs.

[0163] S630 sends the first HARQ-ACK message and the second HARQ-ACK message.

[0164] Correspondingly, the network device receives the first HARQ-ACK information and the second HARQ-ACK information.

[0165] It should be understood that the first HARQ-ACK message corresponds to the first PDSCH, and the second HARQ-ACK message corresponds to the second PDSCH.

[0166] It should be understood that the UE receives the first DCI and the second DCI, and sends the first HARQ-ACK information corresponding to the first PDSCH and the second HARQ-ACK information corresponding to the second PDSCH to the network device on the time domain resources or time domain locations specified by the first DCI and the second DCI, respectively.

[0167] It should be understood that by sending the first HARQ-ACK message and the second HARQ-ACK message to the network device, the UE can help the network device determine that the UE has correctly completed the processing of the first PDSCH and the second PDSCH, thereby preparing for the subsequent scheduling of PDSCH resources.

[0168] As one possible implementation, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0169] As one possible implementation, the CRC of DCI format 1_0 is scrambled with C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0170] As one possible implementation, the HARQ-ACK information includes NACK, where a 0 value in the HARQ-ACK information corresponds to NACK.

[0171] By determining or judging that the first PDSCH and the second PDSCH meet the second predefined conditions through the network device, the network device can schedule the first PDSCH and the second PDSCH normally. Thus, this application can achieve the following in the back-to-back scheduling scenario: when the first PDSCH has an additional pilot and the second PDSCH does not have an additional pilot, the processing time of the first PDSCH is avoided, thereby improving communication efficiency.

[0172] Figure 7 A flowchart illustrating a resource scheduling method #700 provided in this application is shown. The main implementers of this method are network devices and UEs, as detailed below. Figure 7 As shown.

[0173] S710, determine that the first PDSCH and the second PDSCH satisfy the first predefined condition.

[0174] It should be understood that the first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS.

[0175] It should be understood that when the network device determines that the first PDSCH and the second PDSCH meet the first predefined condition, the network device needs to adjust the content of the second DCI used to schedule the second PDSCH. For example, the second DCI includes a time slot offset parameter to avoid the impact of the additional pilot of the first PDSCH on the processing time of the second PDSCH. For example, the network device schedules the UE to send the HARQ-ACK information corresponding to the second PDSCH in a time slot N times apart from the time slot where the second PDSCH is located. Here, N can be greater than a predefined value of the protocol, for example, the predefined value is 2. In this way, the impact of the first PDSCH on the processing time of the second PDSCH can be avoided.

[0176] S720 transmits the first DCI, the second DCI, the first PDSCH, and the second PDSCH.

[0177] Correspondingly, the UE receives the first DCI, the second DCI, the first PDSCH, and the second PDSCH.

[0178] It should be understood that the second PDSCH includes a slot offset parameter, which indicates that the number of slots between the slot in which the UE sends the second HARQ-ACK information corresponding to the second PDSCH and the slot in which the second PDSCH is located is N, where N is greater than or equal to a predefined second threshold, and N is a positive integer. For example, the threshold is 2, meaning that N is greater than or equal to 2.

[0179] S730 sends the first HARQ-ACK message and the second HARQ-ACK message.

[0180] Correspondingly, the network device receives the first HARQ-ACK information and the second HARQ-ACK information.

[0181] It should be understood that the first HARQ-ACK message corresponds to the first PDSCH, and the second HARQ-ACK message corresponds to the second PDSCH.

[0182] It should be understood that the UE receives the first DCI and the second DCI, and sends the first HARQ-ACK information corresponding to the first PDSCH and the second HARQ-ACK information corresponding to the second PDSCH to the network device on the time domain resources or time domain locations specified by the first DCI and the second DCI on the PUCCH resources.

[0183] It should be understood that by sending the first HARQ-ACK message and the second HARQ-ACK message to the network device, the UE can help the network device determine that the UE has correctly completed the processing of the first PDSCH and the second PDSCH, thereby preparing for the subsequent scheduling of PDSCH resources.

[0184] As one possible implementation, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0185] As one possible implementation, the CRC of DCI format 1_0 is scrambled with C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0186] The network device determines that the first PDSCH and the second PDSCH meet the first predefined condition, and then adds a time slot offset parameter to the second DCI to indicate the time slot in which the UE sends the second HARQ-ACK information corresponding to the second PDSCH. This application can thus avoid the extra pilot of the first PDSCH from affecting the processing time of the second PDSCH and improve communication efficiency.

[0187] Figure 8 A flowchart illustrating a resource scheduling method #800 provided in this application is shown. The main implementers of this method are network devices and UEs, as detailed below. Figure 8 As shown.

[0188] S810, determine that the first PDSCH and the second PDSCH satisfy the first predefined condition.

[0189] It should be understood that the first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS.

[0190] It should be understood that network devices determine or perform PDSCH scheduling based on the UE's processing time for PDSCH or its processing capability for PDSCH.

[0191] Specifically, if the network device determines that the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold, and the first PDSCH includes a first pre-DMRS and at least one first additional DMRS, and the second PDSCH only includes a second pre-DMRS and does not include additional DMRS, then the network device determines that the first PDSCH will affect the processing time of the second PDSCH.

[0192] It should be understood that the first threshold can be predefined or configured by the network device, and the first threshold can be 0, 1, 2, etc. This application does not make any specific limitation in this regard.

[0193] It should be noted that the first PDSCH and the second PDSCH are for the same UE, and there are no other PDSCHs sent to the UE between the first PDSCH and the second PDSCH.

[0194] S820 transmits the first DCI, the third DCI, the first PDSCH, and the third PDSCH.

[0195] Correspondingly, the UE receives the first DCI, the third DCI, the first PDSCH, and the third PDSCH.

[0196] After determining that the first PDSCH will affect the processing time of the second PDSCH, the network device sends the first PDSCH and the third PDSCH to the UE. The time-domain symbol interval between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the third PDSCH is K, where K can be greater than or equal to a first threshold. This application does not specifically limit the specific value of K, and it can be determined according to the specific circumstances.

[0197] As one possible implementation, the network device does not send a second PDSCH to the UE, thereby avoiding the impact of the first PDSCH on the processing time of the second PDSCH.

[0198] It should be understood that the first DCI is used to schedule the first PDSCH, the second DCI is used to schedule the second PDSCH, and the third DCI is used to schedule the third PDSCH.

[0199] It should be noted that there are no other PDSCHs between the first PDSCH and the second PDSCH. Furthermore, it should be understood that in this embodiment, the first PDSCH, the second PDSCH, and any subsequent PDSCHs are all scheduled for the same UE, and will not include other PDSCHs scheduled for other UEs.

[0200] S830 sends the first HARQ-ACK message and the third HARQ-ACK message.

[0201] Correspondingly, the network device receives the first HARQ-ACK information and the third HARQ-ACK information.

[0202] It should be understood that the first HARQ-ACK message corresponds to the first PDSCH, and the third HARQ-ACK message corresponds to the third PDSCH.

[0203] It should be understood that the UE receives the first DCI and the third DCI, and sends the first HARQ-ACK information corresponding to the first PDSCH and the third HARQ-ACK information corresponding to the third PDSCH to the network device on the PUCCH resource on the time domain resources or time domain locations specified by the first DCI and the third DCI.

[0204] It should be understood that by sending the first HARQ-ACK message and the third HARQ-ACK message to the network device, the UE can help the network device determine that the UE has completed the processing of the first PDSCH and the third PDSCH, thereby preparing for the subsequent scheduling of PDSCH resources.

[0205] As one possible implementation, after determining that the first PDSCH and the second PDSCH meet the first predefined condition, the network device adjusts the time-frequency resource positions of the first PDSCH and / or the second PDSCH. For example, it moves the time-domain symbols occupied by the first PDSCH forward and / or moves the time-domain symbols occupied by the second PDSCH backward, thereby increasing the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH, thereby avoiding the first PDSCH from affecting the processing time of the second PDSCH.

[0206] As one possible implementation, the number of time-domain symbols K between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the third PDSCH is related to the DMRS positions of the first PDSCH and the third PDSCH. For example, it is the number of OFDM symbols between the last DMRS of the first PDSCH and the third PDSCH; or, the number of OFDM symbols between the last DMRS of the first PDSCH and the first DMRS of the third PDSCH; or, the number of OFDM symbols between the last DMRS of the first PDSCH and the first OFDM of the third PDSCH.

[0207] As one possible implementation, when the value of the number of time-domain symbols K between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the third PDSCH is associated with the positions of the DMRS of the first PDSCH and the third PDSCH, the last DMRS of the first PDSCH is configured by the network device or actually sent by the network device.

[0208] As one possible implementation, the aforementioned third PDSCH can be obtained by adjusting the time-frequency resource positions of the first PDSCH and / or the second PDSCH.

[0209] As one possible implementation, the first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

[0210] As one possible implementation, the CRC of DCI format 1_0 is scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0211] As one possible implementation, the HARQ-ACK information includes NACK, where a 0 value in the HARQ-ACK information corresponds to NACK.

[0212] By determining that the first PDSCH and the second PDSCH meet the first predefined condition, the network device can change or adjust the order or content of the PDSCH sent to the UE. Thus, this application can solve the problem of avoiding the impact of the first PDSCH on the processing time of the second PDSCH in back-to-back scheduling scenarios when the first PDSCH has an additional pilot and the second PDSCH does not have an additional pilot, thereby improving communication efficiency.

[0213] The communication device in this application will now be described with reference to the accompanying drawings.

[0214] Figure 9 This is a schematic block diagram of the communication device 900 provided in this application. As shown, the communication device 900 may include a transceiver unit 910 and a processing unit 920.

[0215] In one possible design, the communication device 900 can be the UE in the above method embodiment, or it can be a chip used to implement the functions of the UE in the above method embodiment.

[0216] It should be understood that the communication device 900 may correspond to the UE in the method embodiment of this application, and the communication device 900 may include a unit for performing the method executed by the UE in the aforementioned method embodiment.

[0217] It should be understood that each unit in the communication device 900 and the other operations and / or functions described above are respectively for the purpose of implementing Figures 4 to 8 The corresponding process in the process.

[0218] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0219] It should be understood that the above content is only for illustrative purposes. The communication device 900 can also implement other UE-related steps, actions or methods in the above method embodiments, which will not be repeated here.

[0220] In another possible design, the communication device 900 can be a network device in the above method embodiment, or it can be a chip used to implement the functions of the network device in the above method embodiment.

[0221] It should be understood that the communication device 900 may correspond to the network device in the method embodiments of this application, and the communication device 900 may include a unit for performing the method executed by the network device in the above method embodiments.

[0222] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0223] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0224] It should also be understood that the transceiver unit 910 in the communication device 900 may correspond to Figure 10 The transceiver 1020 in the communication device 1000 shown in the figure, and the processing unit 920 in the communication device 900 can correspond to Figure 10 The processor 1010 in the communication device 1000 shown in the figure.

[0225] It should also be understood that when the communication device 900 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip.

[0226] The transceiver unit 910 is used to implement the signal transmission and reception operation of the communication device 900, and the processing unit 920 is used to implement the signal processing operation of the communication device 900.

[0227] Optionally, the communication device 900 further includes a storage unit 930 for storing instructions.

[0228] Figure 10 This is a schematic block diagram of a communication device 1000 provided in an embodiment of this application. As shown, the communication device 1000 includes at least one processor 1010 and a transceiver 1020. The processor 1010 is coupled to a memory and is used to execute instructions stored in the memory to control the transceiver 1020 to transmit and / or receive signals.

[0229] Optionally, the communication device 1000 also includes a memory 1030 for storing instructions.

[0230] It should be understood that the processor 1010 and memory 1030 described above can be combined into a single processing device, with the processor 1010 executing the program code stored in the memory 1030 to achieve the aforementioned functions. In specific implementations, the memory 1030 can be integrated into the processor 1010 or independent of the processor 1010.

[0231] It should also be understood that transceiver 1020 may include a receiver (or receiver unit) and a transmitter (or transmitter unit).

[0232] The transceiver 1020 may further include an antenna, and the number of antennas may be one or more. The transceiver 1020 may also include a communication interface or interface circuitry.

[0233] When the communication device 1000 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip.

[0234] This application also provides a processing apparatus, including a processor and an interface. The processor can be used to execute the methods described in the above method embodiments.

[0235] It should be understood that the aforementioned processing device can be a chip. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0236] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0237] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a network device in the above-described method embodiments.

[0238] For example, when the computer program is executed by a computer, it enables the computer to implement the method executed by the network device in the above method embodiments.

[0239] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the UE in the above method embodiments.

[0240] For example, when the computer program is executed by the computer, it enables the computer to implement the method executed by the UE in the above method embodiments.

[0241] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method executed by the UE in the above method embodiments.

[0242] This application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to implement the method executed by the network device in the above method embodiments.

[0243] This application also provides a chip system and a processor for calling and running a computer program from a memory, causing a communication device equipped with the chip system to perform a method that a UE should perform, or a method that a network device should perform.

[0244] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the explanations and beneficial effects of the relevant content in any of the communication devices provided above can be referred to the corresponding method embodiments provided above, and will not be repeated here.

[0245] This application does not impose any particular limitation on the specific structure of the execution subject of the method provided in this application embodiment. As long as it is possible to communicate according to the method provided in this application embodiment by running a program that records the code of the method provided in this application embodiment. For example, the execution subject of the method provided in this application embodiment can be a UE or a network device, or a functional module in the UE or network device that can call and execute a program.

[0246] Various aspects or features of this application may be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein may encompass a computer program accessible from any computer-readable device, carrier, or medium.

[0247] The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. Available media (or computer-readable media) can include, but are not limited to: magnetic media or magnetic storage devices (e.g., floppy disks, hard disks (such as portable hard drives), magnetic tapes), optical media (e.g., optical discs, compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives, etc.), or semiconductor media (e.g., solid-state disks (SSDs), USB flash drives, read-only memory (ROM), random access memory (RAM), and various other media capable of storing program code).

[0248] The various storage media described herein may represent one or more devices and / or other machine-readable media used for storing information. The term "machine-readable media" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0249] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM can include a variety of forms, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0250] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0251] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0252] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of the units described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed between each other may be through some interfaces, and the indirect coupling or communication connection between the apparatus or units may be electrical, mechanical, or other forms.

[0253] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to implement the solution provided in this application, depending on actual needs.

[0254] In addition, the functional units in the various embodiments of this application can be integrated into one unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0255] In the above embodiments, it can be implemented entirely or partially by software, hardware, firmware, or any combination thereof.

[0256] When implemented using software, it can be implemented wholly or partially as a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. For information on computer-readable storage media, please refer to the description above.

[0257] It should be understood that in the embodiments of this application, the designations "first", "second", etc. are only for distinguishing different objects, such as different network devices, and do not constitute a limitation on the scope of the embodiments of this application. The embodiments of this application are not limited thereto.

[0258] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0259] It should also be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0260] It should also be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0261] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A resource scheduling method, characterized in that, include: Receive a first downlink control information (DCI) and a second DCI. The first DCI is used to schedule the first physical downlink shared channel (PDSCH), and the second DCI is used to schedule the second PDSCH. The first PDSCH and the second PDSCH are determined to satisfy a first predefined condition. The first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold. The first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS. The second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS. Skip the decoding process of the second PDSCH, and / or send the second hybrid automatic repeat request response (HARQ-ACK) information corresponding to the second PDSCH. Wherein, the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

2. The method according to claim 1, characterized in that, The first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

3. The method according to claim 1 or 2, characterized in that, The Cyclic Redundancy Check (CRC) code of the DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

4. The method according to any one of claims 1 to 3, characterized in that, The HARQ-ACK information includes NACK, and the 0 value of the HARQ-ACK information corresponds to the NACK.

5. A resource scheduling method, characterized in that, include: The first physical downlink shared channel (PDSCH) and the second PDSCH sent to the terminal device are determined to satisfy a second predefined condition. The second predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is greater than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS. Send the first downlink control information (DCI), the second DCI, the first PDSCH, and the second PDSCH. The first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH. Wherein, the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, and there is no third PDSCH sent to the terminal device between the first PDSCH and the second PDSCH.

6. The method according to claim 5, characterized in that, The first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

7. The method according to claim 5 or 6, characterized in that, The Cyclic Redundancy Check (CRC) code of the DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

8. A communication device, characterized in that, include: The transceiver unit is used to receive a first downlink control information (DCI) and a second DCI. The first DCI is used to schedule a first physical downlink shared channel (PDSCH), and the second DCI is used to schedule a second PDSCH. The processing unit is configured to determine that the first PDSCH and the second PDSCH satisfy a first predefined condition. The first predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is less than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal DMRS and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation DMRS but does not include additional DMRS. The processing unit is configured to skip the decoding process of the second PDSCH, and / or the transceiver unit is configured to send the second hybrid automatic repeat request response (HARQ-ACK) information corresponding to the second PDSCH. Wherein, the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, and there is no third PDSCH between the first PDSCH and the second PDSCH.

9. The device according to claim 8, characterized in that, The first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

10. The device according to claim 8 or 9, characterized in that, The Cyclic Redundancy Check (CRC) code of the DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

11. The device according to any one of claims 8 to 10, characterized in that, The HARQ-ACK information includes NACK, and the 0 value of the HARQ-ACK information corresponds to the NACK.

12. A communication device, characterized in that, include: The processing unit is configured to determine that the first physical downlink shared channel (PDSCH) and the second PDSCH sent to the terminal device satisfy a second predefined condition. The second predefined condition includes: the number of time-domain symbols between the end time-domain symbol of the first PDSCH and the start time-domain symbol of the second PDSCH is greater than or equal to a first threshold; the first PDSCH includes a first pre-demodulation reference signal (DMRS) and at least one first additional DMRS; and the second PDSCH includes a second pre-demodulation reference signal (DMRS) but does not include additional DMRS. The transceiver unit is used to transmit first downlink control information (DCI), second DCI, first PDSCH, and second PDSCH. The first DCI is used to schedule the first PDSCH, and the second DCI is used to schedule the second PDSCH. Wherein, the end time domain symbol of the first PDSCH precedes the start time domain symbol of the second PDSCH, and there is no third PDSCH sent to the terminal device between the first PDSCH and the second PDSCH.

13. The device according to claim 12, characterized in that, The first DCI is DCI format 1_0, DCI format 1_1, or DCI format 1_2, and the second DCI is DCI format 1_1 or DCI format 1_2.

14. The device according to claim 12 or 13, characterized in that, The Cyclic Redundancy Check (CRC) code of the DCI format 1_0 is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI).

15. A computer storage medium, characterized in that, The system stores instructions that, when executed on a computer, cause the computer to perform a resource scheduling method as described in any one of claims 1 to 4.

16. A computer storage medium, characterized in that, The system stores instructions that, when executed on a computer, cause the computer to perform a resource scheduling method as described in any one of claims 5 to 7.

17. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the resource scheduling method as described in any one of claims 1 to 4.

18. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the resource scheduling method as described in any one of claims 5 to 7.

Images