Downlink control information transmission method and device

Abstract

Provided are a downlink control information transmission method and device, the method comprising: scheduling traffic channels in a plurality of transmission time intervals (TTIs) through a downlink control information (DCI), the scheduling of traffic channels in a plurality of TTIs through a DCI comprising: indicating the number of TTIs and the number of repetitions of multi-TTI scheduling through the same bit field in the DCI, according to the invention, the problem of how to use multi-TTI scheduling for cross-carrier scheduling in which the subcarrier interval of the scheduling carrier is smaller than the subcarrier interval of the scheduled carrier in the related technology can be solved, and the effect of scheduling multiple TTIs through one DCI with low overhead is realized.

Description

[0001] This application is a divisional application of the invention patent application with the application number 201910253189.8 and the invention title "Downlink Control Information Transmission Method and Device", which was filed on March 29, 2019. Technical Field

[0002] This application relates to the field of communications, and more particularly, to a downlink control information transmission method and device. Background Art

[0003] Currently, the fourth-generation mobile communication technology (4G, the 4th Generation mobile communication technology) Long-Term Evolution (LTE) / Long-Term Evolution Advance (LTE-A) and the fifth-generation mobile communication technology (5G, the 5th Generation mobile communication technology) are facing more and more requirements. From the current development trend, both 4G and 5G systems are researching features to support enhanced mobile broadband, ultra-high reliability, ultra-low latency transmission, and massive connections. Currently, for the carrier aggregation technology, the 5G system is more complex than the 4G system and needs to solve the cross-carrier scheduling between carriers with different subcarrier spacings. Currently, NRR16 CA needs to support cross-carrier scheduling between different subcarrier spacings (subcarrier spacing, abbreviated as SCS). Figure 1 It is a schematic diagram of multiple DCI scheduling multiple slots in the related art, as Figure 1 shown. 4 DCI are used to schedule 4 slots. However, for the case where the subcarrier spacing of the scheduling carrier is smaller than the subcarrier spacing of the scheduled carrier, it is currently not allowed to use multiple DCI to schedule the traffic channels in multiple slots at the same time.

[0004] Therefore, in order to solve the problem of cross-carrier scheduling of multiple large subcarrier spacing slots with a small subcarrier spacing, there are currently two solutions. One is to introduce new UE capabilities for R16 terminals to support demodulating multiple downlink control information (Downlink Control Information, abbreviated as DCI) at the same time. The other is to support multi-slot scheduling in R16 and use one DCI to schedule multiple slots. Currently, there is no specific solution for how to use multi-slot scheduling for cross-carrier scheduling where the subcarrier spacing of the scheduling carrier is smaller than the subcarrier spacing of the scheduled carrier. Therefore, it is necessary to solve how to support multi-slot scheduling in R16.

[0005] In the related art, there is no solution proposed for the problem of how to use multi-TTI scheduling for cross-carrier scheduling where the subcarrier spacing of the scheduling carrier is less than that of the scheduled carrier. Summary of the Invention

[0006] Embodiments of the present application provide a method and apparatus for downlink control information transmission to at least solve the problem of how to use multi-TTI scheduling for cross-carrier scheduling where the subcarrier spacing of the scheduling carrier is less than that of the scheduled carrier in the related art.

[0007] According to an embodiment of the present application, a method for downlink control information transmission is provided, including:

[0008] Scheduling traffic channels in multiple Transmission Time Intervals (TTIs) through a Downlink Control Information (DCI), where the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI for scheduling the traffic channel is located;

[0009] Transmitting the DCI.

[0010] Optionally, scheduling traffic channels in multiple TTIs through a DCI includes:

[0011] The DCI indicates the number of scheduled TTIs in one of the following ways:

[0012] Determining the number of bits in the bit field for the number of scheduled TTIs according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier;

[0013] Indicating the scheduled TTIs among up to N or 2N TTIs after the first scheduled TTI through N bits, where the 2N TTIs are consecutive TTIs and N is a natural number;

[0014] Indicating single-TTI scheduling or multi-TTI scheduling through 1 bit;

[0015] Indicating the number of TTIs or the number of repetitions for multi-TTI scheduling through the same bit field;

[0016] Implicitly determining the number of TTIs for multi-TTI scheduling through Physical Downlink Control Channel (PDCCH) related parameters.

[0017] Optionally, in the case of indicating single-TTI scheduling or multi-TTI scheduling through 1 bit, the number of TTIs for the multi-TTI scheduling is determined by a predefined method or configured by Radio Resource Control (RRC).

[0018] Optionally, determine the number of bits of the bit field for the number of scheduled TTIs according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier in the following manner:

[0019] Or

[0020] where μ PDSCH is the subcarrier spacing index of the Physical Downlink Shared Channel (PDSCH) of the scheduled carrier, and μ PUSCH is the subcarrier spacing index of the Physical Uplink Shared Channel (PUSCH) of the scheduled carrier, and μ PDCCH is the subcarrier spacing index of the PDCCH of the scheduling carrier.

[0021] Optionally, indicate by N bits that among up to N or 2N TTIs after the first scheduled TTI, the scheduled TTIs include one of the following:

[0022] Indicate by N bits whether each of the N TTIs adjacent to the first TTI is scheduled;

[0023] Indicate by N bits whether each of the N TTIs belonging to the first set among the N TTIs after the first TTI is scheduled, where the N TTIs are N TTI positions selected backward in the first set starting from the value of element A indicated in the DCI; the first set is all the values of the fixed time intervals configured in the high-layer signaling for time-domain resource allocation;

[0024] Indicate by N bits that among 2N TTIs after the first TTI, x consecutive TTIs are scheduled, where x = 1, 2,.., 2N;

[0025] Indicate by N bits that among 2N TTIs belonging to the first set after the first TTI, x consecutive TTIs are scheduled, where x = 1, 2,.., 2N, where the 2N TTIs are 2N TTI positions selected backward in the first set starting from the value of element A indicated in the DCI, and the first set is all the values of the fixed time intervals configured in the high-layer signaling for time-domain resource allocation.

[0026] Optionally, indicate the number of TTIs or the repetition times of multi-TTI scheduling through the same bit field according to one of the following manners:

[0027] Use the same bit field to determine and indicate the number of TTIs or the repetition times of multi-TTI scheduling through high-layer signaling configuration;

[0028] Using the same bit field, determine the number of TTIs or the number of repetitions indicating multi-TTI scheduling through physical signaling indication.

[0029] Optionally, determining the number of TTIs for the multi-TTI scheduling implicitly through the PDCCH-related parameters includes one of the following:

[0030] Determine the number of TTIs for the multi-TTI scheduling by the starting control channel element (CCE) position;

[0031] Determine the number of TTIs for the multi-TTI scheduling by the starting CCE position and M-bit indication;

[0032] Determine the number of TTIs for the multi-TTI scheduling by the candidate position or the aggregation level;

[0033] Determine the number of TTIs for the multi-TTI scheduling by the candidate position and M-bit;

[0034] Determine the number of TTIs for the multi-TTI scheduling by the aggregation level and M-bit indication;

[0035] Wherein, M is less than N.

[0036] Optionally, the method further includes:

[0037] When using the DCI to indicate the number of TTIs and the number of repetitions for the multi-TTI scheduling, perform the repeated transmission first and then perform the transmission of different transport blocks; or perform the transmission of different transport blocks first and then perform the repeated transmission.

[0038] Optionally, scheduling the traffic channels of multiple TTIs through one DCI includes:

[0039] The DCI indicates the time-domain resource allocation in one of the following ways:

[0040] Configure the timing interval, the starting symbol of the first TTI, and the ending symbol in the last TTI through higher-layer signaling;

[0041] Configure the timing interval, the starting symbol of the first TTI, the number of scheduled TTIs, and the ending symbol in the last TTI through higher-layer signaling;

[0042] Configure the timing interval, the starting symbol of the first TTI, the number of symbols, and the number of scheduled TTIs through higher-layer signaling;

[0043] Configure the timing interval through higher-layer signaling, indicate the starting symbol and the number of symbols for each TTI or each group of TTIs, and the number of scheduled TTIs, wherein the starting symbol and the number of symbols are not all the same for each TTI;

[0044] Configure the timing interval, the starting symbol and the number of symbols of the first TTI, the number of scheduled TTIs, and the number of sub - time slots / micro - time slots within the scheduled TTIs through high - level signaling.

[0045] Optionally, when transmitting the Physical Downlink Shared Channel (PDSCH) in the multiple TTIs, the method for Hybrid Automatic Repeat reQuest - Acknowledgement (HARQ - ACK) feedback for the PDSCH includes one of the following:

[0046] For each TTI in the multiple TTIs, with its own TTI as the timing starting point, determine the uplink TTI where the HARQ - ACK information corresponding to each TTI is located respectively according to the feedback timing K1 indicated by the Downlink Control Information (DCI).

[0047] For each TTI in the multiple TTIs, use the last TTI as the timing starting point, and determine the uplink TTI where the HARQ - ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI.

[0048] Optionally, the method further includes:

[0049] When the HARQ - ACK is feedback through a semi - static codebook, if the PDSCH determined by using the K1 set configured by high - level signaling belongs to the PDSCH in the multi - TTI scheduling, then determine the DCI that schedules the PDSCH as the last DCI.

[0050] Optionally, for each TTI in the multiple TTIs, with its own TTI as the timing starting point, determining the uplink TTI where the HARQ - ACK information corresponding to each TTI is located respectively according to the feedback timing K1 indicated by the DCI includes one of the following:

[0051] When the HARQ - ACK is feedback through a dynamic codebook, if the HARQ - ACK for scheduling the first PDSCH indicates to the same uplink TTI, the Downlink Allocation Index (DAI) of at least one DCI in the DCI that schedules the first PDSCH needs to be incremented by one.

[0052] When the HARQ - ACK is feedback through a dynamic codebook, if the HARQ - ACK for scheduling the first PDSCH indicates to the same uplink TTI, the HARQ - ACK information corresponding to the PDSCH in the multi - TTI scheduling is located at the beginning of the dynamic codebook.

[0053] Optionally, the method further includes:

[0054] When the HARQ-ACK information corresponding to the PDSCH with multi-TTI scheduling is at the beginning of the dynamic codebook, the PDSCH with multi-TTI scheduling is sorted according to one of the following principles:

[0055] Sort in the order of carrier CC index first and then time domain at the beginning of the codebook;

[0056] Sort in the order of time domain first and then CC index at the beginning of the codebook.

[0057] Optionally, for each TTI among the multiple TTIs, the last TTI is used as the timing starting point, and the uplink TTIs where the HARQ-ACK information corresponding to all TTIs is located are determined according to the feedback timing K1 in the DCI, including:

[0058] HARQ-ACK is fed back using the dynamic codebook. When the count DAI increments the DCI by 1, the codebook size is determined according to the actual scheduling quantity of the multi-TTI scheduling.

[0059] Optionally, the method further includes:

[0060] The DCI determines the coding block group transmission information CBGTI in one of the following ways:

[0061] Independently indicate the CBGTI of each TTI among the multiple TTIs, where each TTI uses X / Y bits, X is the number of scheduled TTIs, and Y is the maximum number of coding block groups CBGs configured by the radio resource control RRC;

[0062] Multiple TTIs share the same CBGTI. Among them, the TTIs with the new data indication NDI not flipped share the same CBGTI indication, and the TTIs with the NDI flipped ignore the CBGTI indication.

[0063] Optionally, the method further includes:

[0064] The DCI determines the coding block group refresh information CBGFI in one of the following ways:

[0065] Independently indicate the CBGFI of each TTI among the multiple TTIs. Among them, for a maximum of N scheduled TTIs, each TTI uses 1 bit; or use N1 bits to indicate the CBGFI of the TTIs with the new data indication NDI not flipped, where N1 is not greater than N;

[0066] Multiple TTIs share the same CBGFI. Among them, the TTIs with the NDI not flipped share the same CBGFI indication, and the TTIs with the NDI flipped ignore the CBGFI indication.

[0067] Optionally, the demodulation reference signal pattern (DMRS pattern) in the multiple TTIs is determined by one of the following methods:

[0068] The multiple TTIs use the same DMRS pattern as that in the first TTI, where the DMRS pattern of the first TTI is determined by combining time-domain resource allocation with RRC configuration;

[0069] The DMRS pattern of the first TTI is determined by combining time-domain resource allocation with RRC configuration. For a TTI that continuously occupies 14 orthogonal frequency-division multiplexing symbols (OS), the first DMRS pattern is determined by RRC or predefined means;

[0070] The multiple TTIs use the same DMRS pattern as that in the first TTI, and the TTIs to which the DMRS pattern is applied are determined by configuring the TTI pattern. Among them, the DMRS pattern of the first TTI is determined by combining time-domain resource allocation with radio resource control (RRC) configuration.

[0071] According to another aspect of the embodiments of the present application, a downlink control information transmission device is further provided, including:

[0072] A scheduling module, configured to schedule a traffic channel in multiple transmission time intervals (TTIs) through a downlink control information (DCI), where the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI for scheduling the traffic channel is located;

[0073] A transmission module, configured to transmit the DCI.

[0074] Optionally, the scheduling module includes:

[0075] A first indication sub-module, configured to indicate the number of scheduled TTIs by the DCI in one of the following ways:

[0076] A first determination unit, configured to determine the number of bits in the bit field for indicating the number of scheduled TTIs according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier;

[0077] A first indication unit, configured to indicate the scheduled TTIs in at most N or 2N TTIs after the first scheduled TTI by N bits, where the 2N TTIs are consecutive TTIs and N is a natural number;

[0078] A second indication unit, configured to indicate single-TTI scheduling or multi-TTI scheduling by 1 bit;

[0079] A third indication unit, configured to indicate the number of TTIs or the number of repetitions of multi-TTI scheduling through the same bit field;

[0080] A second determination unit, configured to implicitly determine the number of TTIs of multi-TTI scheduling through physical downlink control channel PDCCH related parameters.

[0081] Optionally, the first determination unit is further configured to determine the number of bits of the bit field for scheduling the number of TTIs according to the following method based on the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier:

[0082] Or

[0083] Where μ PDSCH is the subcarrier spacing index of the physical downlink shared channel PDSCH of the scheduled carrier, μ PUSCH is the subcarrier spacing index of the physical uplink shared channel PUSCH of the scheduled carrier, μ PDCCH is the subcarrier spacing index of the PDCCH of the scheduling carrier.

[0084] Optionally, the first indication unit is further configured to indicate, through N bits, that among the maximum N or 2N TTIs after the first scheduled TTI, the scheduled TTIs include one of the following:

[0085] Indicating whether each of the N TTIs adjacent to the first TTI is scheduled through N bits;

[0086] Indicating whether each of the N TTIs belonging to the first set among the N TTIs after the first TTI is scheduled through N bits, where the N TTIs are N TTI positions selected backward in the first set starting from the value of element A indicated in the DCI; the first set is all the values of the fixed time interval in the high-layer signaling configured time domain resource allocation;

[0087] Indicating that x consecutive TTIs are scheduled among the 2N TTIs after the first TTI through N bits, where x = 1, 2,.., 2N;

[0088] Indicating that x consecutive TTIs are scheduled among the 2N TTIs belonging to the first set after the first TTI through N bits, where x = 1, 2,.., 2N, where the 2N TTIs are 2N TTI positions selected backward in the first set starting from the value of element A indicated in the DCI, and the first set is all the values of the fixed time interval in the high-layer signaling configured time domain resource allocation.

[0089] Optionally, the third indication unit is further configured to indicate the number of TTIs or the number of repetitions of multi-TTI scheduling through the same bit field according to one of the following methods:

[0090] Using the same bit field, determine the number of TTIs or the number of repetitions indicating multi-TTI scheduling through high-layer signaling configuration;

[0091] Using the same bit field, determine the number of TTIs or the number of repetitions indicating multi-TTI scheduling through physical signaling indication.

[0092] Optionally, the second determination unit is further configured to implicitly determine, through the PDCCH-related parameters, that the number of TTIs for the multi-TTI scheduling includes one of the following:

[0093] Determine the number of TTIs for the multi-TTI scheduling through the starting control channel element (CCE) position;

[0094] Determine the number of TTIs for the multi-TTI scheduling through the starting CCE position and M-bit indication;

[0095] Determine the number of TTIs for the multi-TTI scheduling through the candidate set position or the aggregation level;

[0096] Determine the number of TTIs for the multi-TTI scheduling through the candidate set position and M-bit;

[0097] Determine the number of TTIs for the multi-TTI scheduling through the aggregation level and M-bit indication;

[0098] Wherein, M is less than N.

[0099] Optionally, the device further includes:

[0100] An execution module, configured to, when using the DCI to indicate the number of TTIs and the number of repetitions for multi-TTI scheduling, first perform retransmission and then perform the transmission of different transport blocks; or first perform the transmission of different transport blocks and then perform repeated transmission.

[0101] Optionally, the scheduling module includes:

[0102] A second indication sub-module, configured to indicate time domain resource allocation by the DCI in one of the following manners:

[0103] Configure the timing interval, the starting symbol of the first TTI, and the ending symbol in the last TTI through high-layer signaling;

[0104] Configure the timing interval, the starting symbol of the first TTI, the number of scheduled TTIs, and the ending symbol in the last TTI through high-layer signaling;

[0105] Configure the timing interval, the starting symbol of the first TTI, the number of symbols, and the number of scheduled TTIs through high-layer signaling;

[0106] Configure the timing interval through high-layer signaling, indicate the starting symbol and the number of symbols for each TTI or each group of TTIs, and the number of scheduled TTIs, where the starting symbol and the number of symbols are not all the same for each TTI;

[0107] Configure the timing interval through high-layer signaling, the starting symbol and the number of symbols of the first TTI, the number of scheduled TTIs, and the number of sub-slots / micro-slots within the scheduled TTIs.

[0108] Optionally, when transmitting the Physical Downlink Shared Channel (PDSCH) in the multiple TTIs, the method for performing Hybrid Automatic Repeat request-ACKnowledge (HARQ-ACK) feedback on the PDSCH includes one of the following:

[0109] Each TTI in the multiple TTIs uses its own TTI as the timing starting point, and respectively determines the uplink TTI where the HARQ-ACK information corresponding to each TTI is located according to the feedback timing K1 indicated by the DCI;

[0110] Each TTI in the multiple TTIs uses the last TTI as the timing starting point, and determines the uplink TTI where the HARQ-ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI.

[0111] Optionally, the device further includes:

[0112] A first determination module, configured to determine the Coding Block Group Transmission Information (CBGTI) by one of the following methods for the DCI:

[0113] Independently indicate the CBGTI of each TTI in the multiple TTIs, where each TTI uses X / Y bits, where X is the number of scheduled TTIs, and Y is the maximum number of Coding Block Groups (CBGs) configured by Radio Resource Control (RRC);

[0114] Multiple TTIs share the same CBGTI, where TTIs with the New Data Indicator (NDI) not flipped share the same CBGTI indication, and TTIs with the NDI flipped ignore the CBGTI indication.

[0115] Optionally, the device further includes:

[0116] A second determination module, configured to determine the Coding Block Group Flush Information (CBGFI) by one of the following methods for the DCI:

[0117] Independently indicate the CBGFI of each TTI among the multiple TTIs, where, for scheduling up to N TTIs, each TTI uses 1 bit; or use N1 bits to indicate the CBGFI of the TTIs where the new data indication NDI does not flip, and N1 is not greater than N.

[0118] Multiple TTIs share the same CBGFI, where the TTIs with non-flipping NDI share the same CBGFI indication, and the TTIs with flipping NDI ignore the CBGFI indication.

[0119] Optionally, the demodulation reference signal pattern DMRS pattern in the multi-TTI is determined by one of the following methods:

[0120] The multi-TTI uses the same DMRS pattern as that in the first TTI, and the DMRS pattern of the first TTI is determined by time-domain resource allocation in combination with RRC configuration;

[0121] The DMRS pattern of the first TTI is determined by time-domain resource allocation in combination with RRC configuration. For the TTIs that continuously occupy 14 orthogonal frequency division multiplexing symbols OS, the first DMRS pattern is used, and the first DMRS pattern is determined by RRC or a predefined method;

[0122] The multi-TTI uses the same DMRS pattern as that in the first TTI, and the TTIs to which the DMRS pattern is applied are determined by configuring the TTI pattern, where the DMRS pattern of the first TTI is determined by time-domain resource allocation in combination with radio resource control RRC configuration.

[0123] According to another embodiment of the present application, a storage medium is further provided. A computer program is stored in the storage medium, where the computer program is set to execute the steps in any one of the above method embodiments when running.

[0124] According to another embodiment of the present application, an electronic device is further provided, including a memory and a processor. A computer program is stored in the memory, and the processor is set to run the computer program to execute the steps in any one of the above method embodiments.

[0125] With this application, a traffic channel in multiple transmission time intervals (TTIs) is scheduled by a downlink control information (DCI). Among them, the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI for scheduling the traffic channel is located; transmitting the DCI can solve the problem of how to use multi-TTI scheduling for cross-carrier scheduling where the subcarrier spacing of the scheduled carrier is less than the subcarrier spacing of the scheduling carrier in the related art, and achieves the effect of scheduling multiple TTIs through one DCI with relatively small overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0126] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0127] Figure 1 is a schematic diagram of multiple DCIs scheduling multiple slots in the related art;

[0128] Figure 2 is a hardware structure block diagram of a mobile terminal for a method of transmitting downlink control information according to an embodiment of the present application;

[0129] Figure 3 is a flowchart of a method of transmitting downlink control information according to an embodiment of the present application;

[0130] Figure 4 is a schematic diagram of one DCI scheduling multiple slots according to an embodiment of the present application Figure 1 ;

[0131] Figure 5 is a schematic diagram of one DCI scheduling multiple slots according to an embodiment of the present application Figure 2 ;

[0132] Figure 6 is a schematic diagram of one DCI scheduling multiple slots according to an embodiment of the present application Figure 3 ;

[0133] Figure 7 is a schematic diagram of one DCI scheduling multiple slots according to an embodiment of the present application Figure 4 ;

[0134] Figure 8 is a block diagram of a downlink control information transmission device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0135] The present application will be described in detail below with reference to the drawings and in conjunction with embodiments. It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

[0136] It should be noted that the terms "first", "second", etc. in the description, claims and the above-mentioned drawings of this application are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence.

[0137] Embodiment 1

[0138] The method embodiment provided in Embodiment 1 of this application can be executed on a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 2 is a hardware structure block diagram of a mobile terminal for a downlink control information transmission method according to an embodiment of this application. As Figure 2 shown, the mobile terminal 10 may include one or more ( Figure 2 only one is shown in the figure) processors 102 (the processors 102 may include, but are not limited to, processing devices such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Optionally, the above-mentioned mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those of ordinary skill in the art can understand that Figure 2 the structure shown is only schematic and does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal 10 may further include more or fewer components than those shown in Figure 2 the figure, or have a different configuration from that shown in Figure 2 the figure.

[0139] The memory 104 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the message receiving method in the embodiment of this application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implements the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 104 may further include a memory remotely disposed relative to the processor 102, and these remote memories can be connected to the mobile terminal 10 through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0140] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the mobile terminal 10. In one example, the transmission device 106 includes a network adapter (Network INterface CoNtroller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet wirelessly.

[0141] In this embodiment, a downlink control information transmission method is provided, which is applied to a base station and is sent to the above-mentioned mobile terminal after time slot aggregation. Figure 3 is a flowchart of a method for transmitting downlink control information according to an embodiment of the present application. Figure 3 As shown, the process includes the following steps:

[0142] Step S302, scheduling service channels in multiple transmission time intervals TTI through a downlink control information DCI, wherein the subcarrier spacing of the carrier where the scheduled service channel is located is not less than the subcarrier spacing of the carrier where the DCI scheduling the service channel is located;

[0143] Among them, the subcarrier spacing of the carrier where the service channel is located is preferably the subcarrier spacing of the carrier where the BWP (BandwidthPart) is activated, that is, one or more BWPs can be configured in the carrier, and each BWP can be independently configured with a subcarrier spacing; or preferably the subcarrier spacing of the carrier where the service channel is located (in this case, there is no BWP division, which means the entire carrier). Similarly, the subcarrier spacing of the carrier where the DCI is located is preferably the subcarrier spacing of the carrier where the BWP is activated or the subcarrier spacing of the carrier where the DCI is located. In addition, the DCI can also be replaced with the PDCCH description as the subcarrier spacing of the carrier where the PDCCH is located, because the DCI is carried in the PDCCH, that is, preferably, the channel for transmitting the DCI is the physical downlink control channel PDCCH.

[0144] The downlink control information DCI may be a DL assignment for scheduling a PDSCH or a UL grant for scheduling a PUSCH.

[0145] Step S304: transmitting the DCI.

[0146] Through the above steps S302 to S304, a downlink control information (DCI) is used to schedule traffic channels in multiple transmission time intervals (TTIs). Among them, the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI for scheduling the traffic channel is located. Transmitting the DCI can solve the problem of how to use multi-TTI scheduling for cross-carrier scheduling where the subcarrier spacing of the scheduled carrier is less than the subcarrier spacing of the scheduling carrier in the related art, achieving the effect of scheduling multiple TTIs through one DCI with relatively small overhead.

[0147] In an optional embodiment, step S302 above may specifically include:

[0148] The DCI indicates the number of scheduled TTIs in one of the following ways:

[0149] Determine the number of bits in the bit field for indicating the number of scheduled TTIs according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier;

[0150] Use N bits to indicate the scheduled TTIs among at most N or 2N TTIs after the first scheduled TTI, where the 2N TTIs are consecutive TTIs and N is a natural number;

[0151] Use 1 bit to indicate single-TTI scheduling or multi-TTI scheduling;

[0152] Use the same bit field to indicate the number of TTIs or the repetition times for multi-TTI scheduling;

[0153] Implicitly determine the number of TTIs for multi-TTI scheduling through the physical downlink control channel (PDCCH) related parameters.

[0154] Among them, in the case of using 1 bit to indicate single-TTI scheduling or multi-TTI scheduling, the number of TTIs for multi-TTI scheduling is determined by a predefined method or configured by radio resource control (RRC).

[0155] Furthermore, the number of bits in the bit field for indicating the number of scheduled TTIs is determined according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier in the following way:

[0156] Or

[0157] Where μ PDSCH is the subcarrier spacing index of the physical downlink shared channel (PDSCH) of the scheduled carrier, μ PUSCH is the subcarrier spacing index of the physical uplink shared channel (PUSCH) of the scheduled carrier, and μ PDCCH is the subcarrier spacing index of the PDCCH of the scheduling carrier.

[0158] In the embodiments of the present application, when SCS = 15 kHz, μ = 0; when SCS = 30 kHz, μ = 1; when SCS = 60 kHz, μ = 2; when SCS = 120 kHz, μ = 3; when SCS = 240 kHz, μ = 4.

[0159] Further, it is indicated by N bits that among the maximum N or 2N TTIs scheduled after the first TTI of the scheduling, the scheduled TTIs include one of the following:

[0160] It is indicated by N bits whether each TTI among the N adjacent TTIs after the first TTI is scheduled;

[0161] It is indicated by N bits whether each TTI among the N TTIs belonging to the first set after the first TTI is scheduled, where the N TTIs are N TTI positions selected backward in the first set starting from the value of element A in the first set indicated in the DCI; the first set is all the values of the fixed time intervals in the high-layer signaling configuration of the time-domain resource allocation;

[0162] It is indicated by N bits that among the 2N TTIs after the first TTI, x consecutive TTIs are scheduled, where x = 1, 2,.., 2N;

[0163] It is indicated by N bits that among the 2N TTIs belonging to the first set after the first TTI, x consecutive TTIs are scheduled, where x = 1, 2,.., 2N, where the 2N TTIs are 2N TTI positions selected backward in the first set starting from the value of element A in the first set indicated in the DCI, and the first set is all the values of the fixed time intervals in the high-layer signaling configuration of the time-domain resource allocation.

[0164] The above fixed time interval is K0 or K2, that is, the first set can be the K0 set (when scheduling PDSCH), or can be the K2 set (when scheduling PUSCH).

[0165] Further, the number of TTIs or the number of repetitions of the multi-TTI scheduling is indicated by the same bit field in one of the following ways:

[0166] Using the same bit field, the number of TTIs or the number of repetitions of the multi-TTI scheduling is determined by high-layer signaling configuration;

[0167] Using the same bit field, the number of TTIs or the number of repetitions of the multi-TTI scheduling is determined by physical signaling indication. Preferably, 1 bit in the DCI is used to indicate the number of TTIs and the number of repetitions of the multi-TTI scheduling.

[0168] Further, the number of TTIs of the multi-TTI scheduling is implicitly determined by the PDCCH-related parameters, which may specifically include one of the following:

[0169] Determine the number of TTIs for the multi-TTI scheduling through the starting control channel element (CCE) position;

[0170] Determine the number of TTIs for the multi-TTI scheduling through the starting CCE position and the M-bit indication;

[0171] Determine the number of TTIs for the multi-TTI scheduling through the candidate position or the aggregation level; wherein, the candidate can be the candidate of the physical downlink control channel (PDCCH);

[0172] Determine the number of TTIs for the multi-TTI scheduling through the candidate position and the M-bit;

[0173] Determine the number of TTIs for the multi-TTI scheduling through the aggregation level and the M-bit indication;

[0174] Wherein, M is less than N, and optionally, M = N - 1.

[0175] In the embodiment of the present application, when using the downlink control information (DCI) to indicate the number of TTIs and the repetition times for the multi-TTI scheduling, perform the repeated transmission first and then perform the transmission of different transport blocks; or perform the transmission of different transport blocks first and then perform the repeated transmission.

[0176] In an optional embodiment, the above dissatisfaction with S302 may specifically include:

[0177] The DCI indicates the time-domain resource allocation in one of the following ways:

[0178] Configure the periodicity, the starting symbol of the first TTI, and the ending symbol in the last TTI through the higher layer signaling;

[0179] Configure the periodicity, the starting symbol of the first TTI, the number of scheduled TTIs, and the ending symbol in the last TTI through the higher layer signaling;

[0180] Configure the periodicity, the starting symbol of the first TTI, the number of symbols, and the number of scheduled TTIs through the higher layer signaling;

[0181] Configure the periodicity through the higher layer signaling, and indicate the starting symbol and the number of symbols for each TTI or each group of TTIs, and the number of scheduled TTIs, wherein the starting symbol and the number of symbols are not all the same for each TTI;

[0182] Configure the periodicity through the higher layer signaling, the starting symbol of the first TTI, the number of symbols, the number of scheduled TTIs, and the number of sub-slots / micro-slots within the scheduled TTIs.

[0183] The above higher layer signaling may be the radio resource control (RRC).

[0184] In the embodiments of the present application, when transmitting the Physical Downlink Shared Channel (PDSCH) in multiple Transmission Time Intervals (TTIs), the method for Hybrid Automatic Repeat reQuest - ACKnowledgement (HARQ - ACK) feedback for the PDSCH includes one of the following:

[0185] For each TTI among the multiple TTIs, with its own TTI as the timing starting point, the uplink TTI where the HARQ - ACK information corresponding to each TTI is located is determined respectively according to the feedback timing K1 indicated by the Downlink Control Information (DCI).

[0186] For each TTI among the multiple TTIs, the last TTI is used as the timing starting point, and the uplink TTI where the HARQ - ACK information corresponding to all TTIs is located is determined according to the feedback timing K1 in the DCI.

[0187] In the embodiments of the present application, when the HARQ - ACK is feedback through a semi - static codebook, if the PDSCH determined by using the K1 set configured by higher - layer signaling belongs to the PDSCH in multi - TTI scheduling, the DCI scheduling the PDSCH is determined as the last DCI.

[0188] Optionally, for each TTI among the multiple TTIs, with its own TTI as the timing starting point, the method for determining the uplink TTI where the HARQ - ACK information corresponding to each TTI is located respectively according to the feedback timing K1 indicated by the DCI includes one of the following:

[0189] When the HARQ - ACK is feedback through a dynamic codebook, if the HARQ - ACKs for scheduling the first PDSCH are indicated to the same uplink TTI, the Downlink Allocation Index (DAI) of at least one DCI in the DCI scheduling the first PDSCH needs to be incremented by one.

[0190] When the HARQ - ACK is feedback through a dynamic codebook, if the HARQ - ACKs for scheduling the first PDSCH are indicated to the same one uplink TTI, the HARQ - ACK information corresponding to the PDSCH in multi - TTI scheduling is located at the beginning of the dynamic codebook.

[0191] In the embodiments of the present application, in the case where the HARQ - ACK information corresponding to the PDSCH in multi - TTI scheduling is located at the beginning of the dynamic codebook, the PDSCHs in multi - TTI scheduling are sorted according to one of the following principles:

[0192] Sorted at the beginning of the codebook in the order of carrier Component Carrier (CC) index first and then time domain; sorted at the beginning of the codebook in the order of time domain first and then CC index. That is, in the order of increasing carrier index; the time domain can refer to the order in time or the PDSCH occasion order.

[0193] Optionally, each of the multiple TTIs uses the last TTI as the timing starting point. Determining the uplink TTI where the HARQ-ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI includes:

[0194] HARQ-ACK is feedback using a dynamic codebook. When count DAI increments the DCI by 1, the codebook size is determined according to the actual scheduling quantity of the scheduled multiple TTIs.

[0195] In an optional embodiment, the DCI determines the coded block group transmission information CBGTI in one of the following ways:

[0196] Independently indicate the CBGTI of each TTI among the multiple TTIs, where each TTI uses X / Y bits, where X is the number of scheduled TTIs, and Y is the maximum number of coded block groups CBGs configured by radio resource control RRC;

[0197] Multiple TTIs share the same CBGTI, where TTIs with non-flipped new data indication NDI share the same CBGTI indication, and TTIs with flipped NDI ignore the CBGTI indication.

[0198] In another embodiment, the DCI determines the coded block group flush information CBGFI in one of the following ways:

[0199] Independently indicate the CBGFI of each TTI among the multiple TTIs, where for a maximum of N scheduled TTIs, each TTI uses 1 bit; or use N1 bits to indicate the CBGFI of TTIs with non-flipped new data indication NDI, and N1 is not greater than N;

[0200] Multiple TTIs share the same CBGFI, where TTIs with non-flipped NDI share the same CBGFI indication, and TTIs with flipped NDI ignore the CBGFI indication.

[0201] In the embodiments of the present application, the demodulation reference signal pattern DMRS pattern in the multiple TTIs is determined in one of the following ways:

[0202] The multiple TTIs use the same DMRS pattern and the same as that in the first TTI, where the DMRS pattern of the first TTI is determined by time-domain resource allocation in combination with RRC configuration;

[0203] The DMRS pattern of the first TTI is determined by time-domain resource allocation in combination with RRC configuration. For TTIs that continuously occupy 14 orthogonal frequency division multiplexing symbols OS, the first DMRS pattern is used, and the first DMRS pattern is determined by RRC or a predefined method;

[0204] The multiple TTIs use the same DMRS pattern, which is the same as that in the first TTI. The TTIs to which the DMRS pattern is applied are determined by configuring the TTI pattern. Among them, the DMRS pattern of the first TTI is determined by combining time-domain resource allocation with Radio Resource Control (RRC) configuration.

[0205] Multi-slot scheduling, which can also be referred to as multiple TTI scheduling, where the TTI unit can be time units such as slot, subframe, mini-slot, subslot, etc. In the embodiments of this application, only the slot is taken as an example for illustration, and other TTI units will not be elaborated. It is necessary to solve which same scheduling signaling and which different scheduling signaling are used for the multiple slots to be scheduled, and how HARQ feedback is performed on the data in the multiple scheduled slots. The embodiments of this application will be described in detail below with specific examples.

[0206] Example 1

[0207] This embodiment focuses on how to determine the number of scheduled slots in multi-slot scheduling and how to determine the size of the bit field indicating multi-slot scheduling. The bit field indicating multi-slot scheduling and its size are determined by one of the following methods.

[0208] Method 1: The size (number of bits) of the bit field indicating the number of consecutive scheduled slots is determined according to the subcarrier spacing ratio between the scheduled carrier and the scheduling carrier. As shown in Table 1, when cross-carrier scheduling is for a carrier with SCS = 15 kHz scheduling a carrier with SCS = 30 kHz, the size of this bit field is 1 bit, that is, it only supports indicating whether to schedule 1 slot or 2 consecutive slots; when cross-carrier scheduling is for a carrier with SCS = 15 kHz scheduling a carrier with SCS = 60 kHz, the size of this bit field is 2 bits, that is, it only supports indicating whether to schedule 1 slot or 2 consecutive slots or 3 consecutive slots or 4 consecutive slots; when cross-carrier scheduling is for a carrier with SCS = 15 kHz scheduling a carrier with SCS = 120 kHz, the size of this bit field is 3 bits, that is, it only supports indicating whether to schedule 1 slot or 2 consecutive slots or 3 consecutive slots or 4 consecutive slots or 5 consecutive slots or 6 consecutive slots or 7 consecutive slots or 8 consecutive slots.

[0209] Table 1

[0210]

[0211] Method 2: Use N bits to indicate whether the N or 2N slots after the first slot are scheduled. That is, by default, the first slot is definitely scheduled, and whether the N or 2N slots after the first slot are scheduled is indicated by the N bits.

[0212] Among them, the first slot is determined by or determined,

[0213] where n represents the slot where the PDCCH is located, K0 is the fixed time interval determined based on the carrier where the PDSCH is located, K2 is the fixed time interval determined based on the carrier where the PUSCH is located, μ PUSCH , μ PDSCH and μ PDCCH a respectively represent the subcarrier spacing of the PUSCH, PDSCH, and PDCCH. The position of the first scheduled slot is indicated by K0 or K2, and the scheduling situation of the subsequent slots is indicated by the other N bits. Specifically, it is one of the following methods. Method 1: Indicate whether the subsequent adjacent N slots are scheduled (that is, a total of N + 1 adjacent slots are indicated whether they are scheduled, supporting non - continuous scheduling); Method 2: Indicate whether the N slots belonging to the K0 set (the K0 set depends on which K0 values are configured in the time - domain resource allocation of the radio resource control RRC parameter) among the subsequent N slots are scheduled, and select N slot positions starting from the K0 value indicated in the DCI (that is, a total of N + 1 slots in the K0 set are indicated whether they are scheduled, supporting non - continuous scheduling); Method 3: Indicate that among the subsequent 2N slots, 1, 2,.., 2N consecutive slots are scheduled, that is, a total of 2,.., 2N + 1 consecutive slots are indicated, including the first slot; Method 4: Indicate that among the subsequent 2N slots in the K0 set, 1, 2,.., 2N consecutive slots are scheduled, that is, a total of 2,.., 2N + 1 consecutive slots are indicated, including the first slot;

[0214] Method 3: Use 1 bit to indicate whether it is single - slot scheduling or multi - slot scheduling, and the number of slots for multi - slot scheduling is determined by predefined or RRC configuration.

[0215] Among them, the predefined can be determined according to determined.

[0216] Method 4: Use the same bit field to indicate the number of multi - slot scheduling and / or the number of Repetition times.

[0217] Specifically, when multi-slot scheduling and Repetition cannot be supported simultaneously, determine how to indicate through one of the following methods. Method 1: Use the same bit field in DCI, and determine whether to indicate multi-slot scheduling or Repetition scheduling through RRC configuration. That is, only semi-statically support one of the two. Method 2: Use 1 bit in DCI to indicate whether it is multi-slot scheduling or Repetition scheduling, that is, dynamically support one of the two. Further, when the bit field sizes indicating multi-slot scheduling and Repetition times are not equal, when one of the sizes is fixed and the other is not fixed (RRC configuration or according to preset rules), then when using the same bit field, reuse the other function indication according to the bit field with a fixed size from the least significant bit (LSB) to the most significant bit (MSB) (or the reverse order). For example, the Repetition times indication is fixed at 2 bits, and when the multi-slot scheduling is 1 bit, only reuse the 1 bit of the least significant bit (LSB). If the fixed size is not enough, optionally increase the size, or only determine the upper limit according to the fixed size and no longer increase, that is, discard the most significant bit (MSB).

[0218] Specifically, Figure 4 is a schematic diagram of a DCI scheduling multiple slots according to an embodiment of the present application Figure 1 , Figure 5 is a schematic diagram of a DCI scheduling multiple slots according to an embodiment of the present application Figure 2 , such as Figure 4 and 5 shown, when multi-slot scheduling and Repetition can be supported simultaneously, whether the multi-slot scheduling quantity and Repetition times are jointly indicated or independently indicated, it is necessary to determine how to Repetition among the indicated N slots through RRC / dynamic indication / preset rules. The candidate methods are one of the following: execute Repetition first and then multi-slot scheduling; Method 2: Execute multi-slot scheduling first and then Repetition. For example: Assume N = 8 (multi-slot quantity), R = 2 (Repetition times), then the execution method of Method 1 is as shown in Figure 4 shown, starting from the starting slot determined by K0, first Repetition and then different TB; the execution method of Method 2 is as shown in Figure 5As shown, starting from the starting slot determined by K0, different TBs are sent first and then repetitions are sent; for another example: assuming that the number of TBs for multi-slot scheduling is indicated as N = 4 and R = 2 (number of repetitions), then the total number of slots required is 4 * 2 = 8. Similarly, the execution method of Method 1 is as follows Figure 4 As shown, starting from the starting slot determined by K0, repetitions are sent first and then different TBs are sent; the execution method of Method 2 is as follows Figure 5 As shown, starting from the starting slot determined by K0, different TBs are sent first and then repetitions are sent.

[0219] Method 5: Implicitly determine the number of slots through PDCCH.

[0220] Specifically, it includes one of the following methods. Method 1: Determine multi-slot scheduling through the position of the starting control channel element (CCE), or the starting CCE position + M bits indication. For example, implicitly determine 1 bit of the N bits required for multi-slot scheduling through the parity number of the starting CCE index, and the remaining N - 1 = M bits are determined through explicit indication; for another example, implicitly determine whether it is single-slot scheduling or multi-slot scheduling through the parity number of the starting CCE index. Method 2: Determine multi-slot scheduling through different candidates or aggregation levels, or different candidates or aggregation levels + M bits indication. For example, implicitly determine 1 or 2 bits of the N bits required for multi-slot scheduling through different candidates or aggregation levels, and the remaining N - 1 = M (or N - 2 = M) bits are determined through explicit indication; for another example, implicitly determine whether it is single-slot scheduling or multi-slot scheduling through different candidates or aggregation levels. This method can be used as a means to save the overhead of multi-slot indication.

[0221] Optionally, the continuous slot scheduling described in this embodiment refers to slots in the same transmission direction, preferably slots in the same transmission direction that are continuously available.

[0222] Through the method for indicating the number of multi-slot scheduling in the multi-slot scheduling method described in this embodiment, determine the size of the multi-slot scheduling number bit field through the subcarrier spacing between the modulated carrier and the scheduling carrier, or indicate whether 1 or more slots after the first slot are scheduled, or reuse other bit fields, or implicitly determine, so as to realize notifying the terminal of the number and position of multi-slot scheduling. At this time, while ensuring the multi-slot scheduling function, the physical layer signaling overhead is reduced and the performance of the downlink control channel is improved.

[0223] Example 2

[0224] This embodiment is directed to how to determine the time-domain resource allocation in multiple-slot scheduling. The bit field indicating the time-domain resource allocation for multiple-slot scheduling is determined by one of the following methods.

[0225] Method 1: The time-domain resource allocation is configured by RRC for scheduling timing (K0 or K2), the starting symbol of the first slot, and optionally also the ending symbol in the last symbol. Here, the starting symbol is the starting symbol in the first slot, the ending symbol is the ending symbol in the last slot, and the number of slots is assumed to be determinable by the multiple-slot scheduling number indication.

[0226] Method 2: The time-domain resource allocation is configured by RRC for scheduling timing (K0 or K2), the starting symbol of the first slot, the number of slots to be scheduled, and optionally also the ending symbol in the last symbol. Here, the starting symbol is the starting symbol in the first slot, the ending symbol is the ending symbol in the last slot, and the number of slots indication is added compared to Method 1.

[0227] Method 3: The time-domain resource allocation is configured by RRC for scheduling timing (K0 or K2), the starting symbol and the number of symbols, and the number of slots to be scheduled. That is, compared with the time-domain resource allocation in the prior art, only the number of slots to be scheduled is increased. Further, the number of slots to be scheduled may be all slots including the first slot determined according to the scheduling timing, or the remaining slots excluding the first slot determined according to the scheduling timing.

[0228] Method 4: The time-domain resource allocation configures the scheduling timing (K0 or K2) through RRC, indicates the starting symbol and the number of symbols for each slot or each group of slots, and the number of scheduled slots. That is, at this time, compared with the time-domain resource allocation of the prior art, only the number of scheduled slots is increased. Further, the number of scheduled slots may be all slots including the first slot determined according to the scheduling timing, or the remaining slots excluding the first slot determined according to the scheduling timing. Among them, the starting symbol and the number of symbols are not all the same for each slot. For example: for each scheduled slot, indicate the starting symbol and the number of symbols of each slot (for example, schedule 2 slots, indicate that the starting symbol of the first slot is OS#3, L = 7 OSs, indicate that the starting symbol of the second slot is OS#2, L = 7 OSs); or indicate different starting symbols and the number of symbols and the corresponding slots (for example, schedule 4 slots, indicate the starting symbol is OS#3, L = 11 and apply to the 1st and 3rd slots, indicate the starting symbol is OS#2, L = 12 and apply to the 2nd and 4th slots). Among them, OS is the Orthogonal Frequency Division Multiplexing (OFDM) symbol.

[0229] Method 5: The time-domain resource allocation configures the scheduling timing (K0 or K2), the starting symbol and the number of symbols, the number of scheduled slots (optional), and the number of subslots / mini-slots within the scheduled slot (optional) through RRC. That is, at this time, compared with the time-domain resource allocation of the prior art, only the number of scheduled slots (optional) and the number of subslots / mini-slots within the scheduled slot (optional) are increased. Further, the number of symbols in the time-domain resource allocation in the subslots / mini-slots within the slot is the same as the indicated number of symbols. Preferably, each subslot / mini-slot continuously occupies the time-domain symbol resources. For example: The time-domain resource allocation indicates that the starting symbol is OS#2, the number of symbols L = 2, the number of scheduled slots = 3, and the number of subslots / mini-slots within the scheduled slot is 4. Then, this multi-slot scheduling transmits a total of 8 TTIs, where each slot transmits 4 TTIs. The 4 TTIs within the slot start from OS#2, continuously occupy 8 OSs, and each TTI occupies 2 OSs. Further, the sum of the number of symbols in each subslot / mini-slot within the slot is the indicated number of symbols. Preferably, each subslot / mini-slot determines its own symbol length in an equal division manner, or according to a preset or configured symbol length pattern. Preferably, each subslot / mini-slot continuously occupies the time-domain symbol resources. For example: The time-domain resource allocation indicates that the starting symbol is OS#2, the number of symbols L = 8, the number of scheduled slots = 3, and the number of subslots / mini-slots within the scheduled slot is 4. Then, this multi-slot scheduling transmits a total of 8 TTIs, where each slot transmits 4 TTIs. The 4 TTIs within the slot start from OS#2, continuously occupy 8 OSs, and each TTI occupies 8 / 4 = 2 OSs. Further, the number of scheduled slots can be all slots including the first slot determined according to the scheduling timing, or the remaining slots excluding the first slot determined according to the scheduling timing.

[0230] Further, based on any of the above methods, the scheduled traffic channel only uses the available symbols in each slot. For example, for PDSCH, only D or X symbols are used, and if it is a U symbol, it is not transmitted (punctured or rate-matched); for PUSCH, only X or U symbols are used, and if it is a D symbol, it is not transmitted (punctured or rate-matched).

[0231] Further, based on any of the above methods, according to the possible candidate time-domain resource allocation tables configured by RRC, one of them can be dynamically indicated through DCI.

[0232] Through the multi-slot scheduling time-domain resource allocation indication method in the multi-slot scheduling method described in this embodiment, by indicating the starting symbol of multi-slot scheduling, or further including the number of multi-slot scheduling, or further including the ending symbol, or different slots applying different starting symbols and lengths, the time-domain resource allocation during multi-slot scheduling is notified to the terminal. At this time, while ensuring the multi-slot scheduling function, the physical layer signaling overhead is maintained unchanged, and a certain degree of flexibility in the time-domain resource allocation of multi-slot scheduling is ensured.

[0233] Example 3

[0234] This embodiment aims at how to determine the HARQ feedback timing and feedback resources corresponding to multiple scheduled slots in the downlink PDSCH multi-slot scheduling. The HARQ feedback for the PDSCH multi-slot scheduling is determined by one of the following methods.

[0235] Method 1: Each scheduled slot independently determines the uplink slot where the corresponding HARQ-ACK information is located according to the feedback timing K1 indication in the DCI (DL assignment). Figure 6 It is a schematic diagram of scheduling multiple slots by a DCI according to an embodiment of the present application Figure 3 , as Figure 6 shown, for the PDSCH transmission in 4 DL slots, each TB determines the feedback timing with its own slot as the timing starting point according to the K1 indicated in the DCI.

[0236] When the HARQ-ACK is fed back using a semi-static codebook, if the PDSCH determined using the configured K1 set has no DCI, it is assumed that the DCI for multi-slot scheduling is used as the last DCI. For example: if the configured K1 set is 2, 3 at this time, taking UL slot #4 as an example, when determining the PUCCH resource in UL slot #4 to find the last DCI, if it finds some PDSCHs of multi-slot scheduling according to the K1 set (i.e., Figure 6 the PDSCHs in DL slot #1, 2 in ), but there is no DCI, then it is assumed that the DCI for multi-slot scheduling is the last DCI, assuming that there is no other unicast PDSCH except the PDSCH for multi-slot scheduling at this time. Or the base station needs to ensure that the configured K1 set always includes the DCI for multi-slot scheduling. In addition: if the DCI for scheduling multi-slot transmission is before slot 0, and there is no other DCI when determining the codebook window at this time, the K1 set should include the slot where the DCI for multi-slot scheduling sent before slot 0 is located.

[0237] When HARQ-ACK is fed back using a dynamic codebook, when the UE feeds back the HARQ-ACK for the TB in the slot after the non-first slot, each slot is used as the timing starting point, and the (UL) slot is determined according to K1 (in Time Division Duplex (TDD), if an unavailable slot is encountered, it is postponed) and the ACK / NACK bit is determined in the HARQ-ACK codebook of that slot; further, if the HARQ-ACK for the TB scheduled by other DCI also needs to be fed back in that slot, the count Downlink Assignment Index (DAI) in the DCI scheduling other TBs needs to start counting from 1 (or more accurately described as at least one of the count DAI in the DCI scheduling other TBs needs to be incremented by 1, that is, the count DAI of the first DCI is incremented by 1, and the count DAI of the non-first DCI is incremented by 2. Note: The increment of 1 or 2 described in this paragraph is only the increment of the value in the DAI field, because DAI indicates that 00 means counting 1, 01 means counting 2, 10 means counting 3, and 11 means counting 4; the specific position of the TB in the slot after the non-first slot in the HARQ-ACK codebook of that slot in multi-slot scheduling is the counting position incremented by 1). Note: If there is no uplink resource in the slot found according to the indication of K1 for each slot (in TDD), K1 is extended to the nearest slot with uplink resources, and ACK / NACK multiplexing is performed in the subsequent slot. Or, the count DAI remains consistent with R15, only counting the number of currently scheduled PDSCHs (with PDCCH), similar to placing the SPS PDSCH at the end of the codebook, and here the un-fed-back PDSCH can be placed at the beginning of the codebook. Further, the order in the codebook can be determined according to the Component Carrier (CC) index from low to high, or according to the order of first CC and then time domain in the codebook.

[0238] Alternatively, when HARQ-ACK feedback is performed using a dynamic codebook, when incrementing the count DAI for the DCI of multi-slot scheduling by 1, the codebook size can be determined according to the actual number of scheduled slots in the multi-slot scheduling and before the UL slot for transmitting HARQ-ACK. For the TBs in subsequent slots, the feedback bits corresponding to the TBs need to be included in the ACK / NACK codebook in the UL slot of subsequent slot n+K1 (i.e., only the feedback information of that TB (no new scheduled DCI at this time); or if there are other schedulings at this time (regardless of single-slot or multi-slot scheduling, for example, in the case of a UE with support capability 3-5b with 7 occasions, other schedulings occur), the count DAI of at least one of the subsequent DCIs needs to be incremented by 1 for counting.

[0239] Method 2: For each slot in the scheduling, according to the feedback timing K1 indication in the DCI (DL assignment), the UL slot where the HARQ-ACK information corresponding to all slots is located is uniformly determined based on the last slot. Figure 7 It is a schematic diagram of a DCI scheduling multiple slots according to an embodiment of the present application Figure 4 , such as Figure 7 shown, for the transmission of each TB in the PDSCH in 4 DL slots, the feedback timing is determined with the last slot as the timing starting point according to the K1 indicated in the DCI.

[0240] When HARQ-ACK feedback is performed using a semi-static codebook, if there is no DCI for the PDSCH determined using the configured K1 set, it is assumed that the DCI for multi-slot scheduling is used as the last DCI. For example: if the configured K1 set is 2, 3, 4, 5 at this time, taking UL slot #5 as an example, when finding the last DCI for the PUCCH resource in UL slot #5, if it finds some PDSCHs of multi-slot scheduling according to the K1 set (i.e., Figure 7 the PDSCHs in DL slot #0, 1, 2, 3 in

[0241] When HARQ-ACK feedback is performed using a dynamic codebook, it is only necessary to determine the codebook size according to the actual scheduling quantity of the multi-slot scheduling when the count DAI increments the DCI by 1.

[0242] Through this embodiment, by allowing each TB to feedback independently and ensuring that the UE can find the corresponding DCI to determine the PUCCH resource, the latency during multi-slot scheduling can be reduced while ensuring the multi-slot scheduling function.

[0243] Example 4

[0244] This embodiment focuses on how to determine the CBGTI (CBG transmission information) and CBGFI (CBG flushing out information) indications corresponding to the scheduled multiple slots during downlink PDSCH multi-slot scheduling when supporting the Code Block group (CBG) mode of transmission. The CBGTI for multi-slot scheduling is determined by one of the following methods.

[0245] Method 1: The CBGTI in each slot is independently indicated, and each slot uses M / N bits, where N is the number of scheduled slots and M is the maximum number of CBGs configured by RRC.

[0246] Method 2: Unified indication. The slots with non-flipped NDI share the same CBGTI indication, and the slots with flipped NDI ignore the CBGTI indication. Difference from the prior art NR R15: The M bits configured for the two CWs are split. Assuming M = 8 bits, that is, each CW uses 4 bits. In the embodiment of this application, the configured M = 8 bits are applied to the TBs with errors, and each TB uses the same CBGTI indication. Preferably, the specific implementation is to perform an "OR" operation on the incorrect CBGs in each error TB to determine the CBGTI indication. For example, when scheduling 2 slots, CBG#0,1 needs to be retransmitted in the first slot, and CBG#0,3 needs to be retransmitted in the second slot. Then, when retransmitting in multi-slot scheduling, the CBGTI indication for the retransmitted CBGs is CBG#0,1,3.

[0247] The CBGFI for multi-slot scheduling is determined by one of the following methods.

[0248] Method 1: The CBGFI in each slot is independently indicated, using N bits for indication. For the N scheduled slots, each slot uses 1 bit; or use N1 bits, where N1 is not greater than N, that is, only the CBGFI is indicated for the slots with non-flipped NDI.

[0249] Method 2: Unified indication. Slots where the New Data Indicator (NDI) does not flip share the same CBGFI indication, and slots where the NDI flips ignore the CBGFI indication. Preferably, the specific implementation is that the CBGFIs determined independently by each retransmitted TB are subject to an "AND" operation to determine the 1-bit CBGFI in multi-slot scheduling. For example, when scheduling 2 slots, CBGFI = 0 in the first slot indicates that the data may be contaminated, and CBGFI = 1 in the second slot indicates that the data can be merged with the same CBG as before. Then, when retransmitting in multi-slot scheduling, it is indicated that CBGFI = 0, indicating that the data may be contaminated.

[0250] Through this embodiment, multiple TBs are allowed to share the same CBGTI or CBGFI, and the CBG retransmission function can be ensured. At this time, while ensuring the multi-slot scheduling function, the physical layer indication overhead during multi-slot scheduling is reduced, and the downlink control channel performance is improved.

[0251] Example 5

[0252] This embodiment is directed to how to determine the DMRS pattern in multiple slots scheduled in the downlink PDSCH multi-slot scheduling. The DMRS pattern for multi-slot scheduling is determined by one of the following methods.

[0253] Method 1: All slots use the same DMRS pattern and are the same as that in the first slot. The DMRS pattern of the first slot is determined by combining the time-domain resource allocation TRA indicated by the DCI with the RRC configuration.

[0254] Method 2: When the time-domain resource allocation TRA indicates the start symbol of the first slot + the number of slots (optional) + the end symbol of the last slot (optional), the DMRS pattern indicates the slot for the first or last or non-zero start symbol. For slots that continuously occupy 14 OS, it can be pre-configured / indicated by the DMRS pattern + offset / implicitly determined.

[0255] For example: The first slot (where the PDSCH has 12 OS) uses symbol 9 as the additional DMRS (assuming that the RRC configures 2 additional DMRSs at this time), and the RRC configures 4 additional DMRSs in the slots that continuously occupy 14 OS. That is, the RRC configuration of the additional DMRS differentiates between the first non-14-OS slot and the subsequent slots that are full of 14 OS.

[0256] Method 3: Based on Method 1, configure the TTI pattern to apply DMRS. For example, when 4 TTIs are configured as 1010, only the 1st and 3rd slots support DMRS, while the 2nd and 4th slots do not have DMRS or additional DMRS.

[0257] Through this embodiment, multiple TBs are allowed to share the same DMRS pattern or a DMRS pattern with reduced density, so as to provide a certain degree of scheduling flexibility for different pilot density requirements such as high speed or low speed.

[0258] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc), and includes several instructions for causing a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present application.

[0259] Embodiment 2

[0260] In this embodiment, a downlink control information transmission device is further provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used hereinafter, the term "module" can be a combination of software and / or hardware that can implement a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0261] Figure 8 is a block diagram of a downlink control information transmission device according to an embodiment of the present application, as Figure 8 shown, including:

[0262] A scheduling module 82, configured to schedule traffic channels in multiple TTIs through a DCI, where the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI for scheduling the traffic channel is located;

[0263] A transmission module 84, configured to transmit the DCI.

[0264] Optionally, the scheduling module 82 includes:

[0265] A first indication sub-module, configured to indicate the number of scheduled TTIs by the DCI in one of the following manners:

[0266] A first determination unit, configured to determine the number of bits in the bit field of the scheduling TTI quantity according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier;

[0267] A first indication unit, configured to indicate the scheduled TTIs among at most N or 2N TTIs after the first scheduled TTI by N bits, where the 2N TTIs are consecutive TTIs and N is a natural number;

[0268] A second indication unit, configured to indicate single-TTI scheduling or multi-TTI scheduling by 1 bit;

[0269] A third indication unit, configured to indicate the number of TTIs or the repetition times of multi-TTI scheduling by the same bit field;

[0270] A second determination unit, configured to implicitly determine the number of TTIs of multi-TTI scheduling through physical downlink control channel PDCCH related parameters.

[0271] Optionally, the first determination unit is further configured to determine the number of bits in the bit field of the scheduling TTI quantity according to the subcarrier spacing of the scheduled carrier and the subcarrier spacing of the scheduling carrier in the following manner:

[0272] Or

[0273] Where μ PDSCH is the subcarrier spacing index of the physical downlink shared channel PDSCH of the scheduled carrier, μ PUSCH is the subcarrier spacing index of the physical uplink shared channel PUSCH of the scheduled carrier, and μ PDCCH is the subcarrier spacing index of the PDCCH of the scheduling carrier.

[0274] Optionally, the first indication unit is further configured to indicate the scheduled TTIs among at most N or 2N TTIs after the first scheduled TTI by N bits, including one of the following:

[0275] Indicating whether each of the N TTIs adjacent to the first TTI is scheduled by N bits;

[0276] Indicating whether each of the N TTIs belonging to the first set among the N TTIs after the first TTI is scheduled by N bits, where the N TTIs are N TTI positions selected backward in the first set starting from the value of element A indicated in the DCI; the first set is all the values of the fixed time interval in the high-layer signaling configured time domain resource allocation;

[0277] Indicating that x consecutive TTIs are scheduled among the 2N TTIs after the first TTI, where x = 1, 2,.., 2N;

[0278] The first TTI is followed by 2N TTIs belonging to the first set, and x consecutive TTIs are scheduled, where x = 1, 2,.., 2N. The 2N TTIs are the 2N TTI positions selected backward in the first set starting from the value of element A in the first set indicated in the DCI. The first set is all the values of the fixed time interval in the high-layer signaling configuration of time-domain resource allocation.

[0279] Optionally, the third indication unit is further configured to indicate the number of TTIs or the number of repetitions of multi-TTI scheduling through the same bit field in one of the following manners:

[0280] Using the same bit field, determine the number of TTIs or the number of repetitions of multi-TTI scheduling through high-layer signaling configuration;

[0281] Using the same bit field, determine the number of TTIs or the number of repetitions of multi-TTI scheduling through physical signaling indication.

[0282] Optionally, the second determination unit is further configured to implicitly determine the number of TTIs of the multi-TTI scheduling through one of the following PDCCH-related parameters:

[0283] Determine the number of TTIs of the multi-TTI scheduling through the starting control channel element (CCE) position;

[0284] Determine the number of TTIs of the multi-TTI scheduling through the starting CCE position and M-bit indication;

[0285] Determine the number of TTIs of the multi-TTI scheduling through the candidate position or the aggregation level;

[0286] Determine the number of TTIs of the multi-TTI scheduling through the candidate position and M-bit;

[0287] Determine the number of TTIs of the multi-TTI scheduling through the aggregation level and M-bit indication;

[0288] Wherein, M is less than N.

[0289] Optionally, the device further includes:

[0290] An execution module, configured to, when using the DCI to indicate the number of TTIs and the number of repetitions of multi-TTI scheduling, first perform retransmission and then perform the transmission of different transport blocks; or first perform the transmission of different transport blocks and then perform repeated transmission.

[0291] Optionally, the scheduling module 82 includes:

[0292] A second indicator sub-module, configured to indicate time-domain resource allocation by the DCI in one of the following ways:

[0293] Configure a fixed time interval, the starting symbol of the first TTI, and the ending symbol in the last TTI through high-layer signaling;

[0294] Configure a fixed time interval, the starting symbol of the first TTI, the number of scheduled TTIs, and the ending symbol in the last TTI through high-layer signaling;

[0295] Configure a fixed time interval, the starting symbol of the first TTI, the number of symbols, and the number of scheduled TTIs through high-layer signaling;

[0296] Configure a fixed time interval through high-layer signaling, and indicate the starting symbol and the number of symbols for each TTI or each group of TTIs, and the number of scheduled TTIs, where the starting symbol and the number of symbols are not all the same for each TTI;

[0297] Configure a fixed time interval through high-layer signaling, the starting symbol, the number of symbols of the first TTI, the number of scheduled TTIs, and the number of sub-slots / micro-slots within the scheduled TTIs.

[0298] Optionally, when transmitting a physical downlink shared channel (PDSCH) in the multiple TTIs, the method for performing hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback on the PDSCH includes one of the following:

[0299] For each TTI in the multiple TTIs, using each TTI as the timing starting point, respectively determine the uplink TTI where the HARQ-ACK information corresponding to each TTI is located according to the feedback timing K1 indicated by the DCI;

[0300] For each TTI in the multiple TTIs, using the last TTI as the timing starting point, determine the uplink TTI where the HARQ-ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI.

[0301] Optionally, the apparatus further includes:

[0302] A first determination module, configured to determine the coding block group transmission information (CBGTI) by the DCI in one of the following ways:

[0303] Independently indicate the CBGTI of each TTI in the multiple TTIs, where each TTI uses X / Y bits, where X is the number of scheduled TTIs, and Y is the maximum number of coding block groups (CBGs) configured by radio resource control (RRC);

[0304] Multiple TTIs share the same CBGTI. Among them, the TTIs with the new data indication NDI not flipped share the same CBGTI indication, and the TTIs with the NDI flipped ignore the CBGTI indication.

[0305] Optionally, the device further includes:

[0306] A second determination module, configured to determine the coding block group flush information CBGFI by one of the following methods for the DCI:

[0307] Independently indicate the CBGFI of each TTI among the multiple TTIs. Among them, for a maximum of N scheduled TTIs, each TTI uses 1 bit; or use N1 bits to indicate the CBGFI of the TTIs with the new data indication NDI not flipped, where N1 is not greater than N;

[0308] Multiple TTIs share the same CBGFI. Among them, the TTIs with the NDI not flipped share the same CBGFI indication, and the TTIs with the NDI flipped ignore the CBGFI indication.

[0309] Optionally, the demodulation reference signal pattern DMRS pattern in the multiple TTIs is determined by one of the following methods:

[0310] The multiple TTIs use the same DMRS pattern and the same as that in the first TTI, where the DMRS pattern of the first TTI is determined by time-domain resource allocation combined with RRC configuration;

[0311] The DMRS pattern of the first TTI is determined by time-domain resource allocation combined with RRC configuration. For the TTIs continuously occupying 14 orthogonal frequency division multiplexing symbols OS, the first DMRS pattern is used, and the first DMRS pattern is determined by RRC or a predefined method;

[0312] The multiple TTIs use the same DMRS pattern and the same as that in the first TTI. The TTIs applying the DMRS pattern are determined by configuring the TTI pattern, where the DMRS pattern of the first TTI is determined by time-domain resource allocation combined with the radio resource control RRC configuration.

[0313] It should be noted that the above-mentioned various modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to this: all the above-mentioned modules are located in the same processor; or, the above-mentioned various modules are separately located in different processors in any combination form.

[0314] Embodiment 3

[0315] An embodiment of the present application further provides a storage medium storing a computer program, where the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0316] Optionally, in this embodiment, the above storage medium may be configured to store a computer program for executing the following steps:

[0317] S11, scheduling traffic channels in multiple TTIs through a downlink control information DCI, where the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI scheduling the traffic channel is located;

[0318] S12, transmitting the DCI.

[0319] Optionally, in this embodiment, the above storage medium may include but is not limited to: various media such as USB flash drives, read-only memories (ROM), random access memories (RAM), external hard drives, magnetic disks, or optical discs that can store computer programs.

[0320] Embodiment 4

[0321] An embodiment of the present application further provides an electronic device including a memory and a processor, where the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0322] Optionally, the above electronic device may further include a transmission device and an input / output device, where the transmission device is connected to the above processor, and the input / output device is connected to the above processor.

[0323] Optionally, in this embodiment, the above processor may be configured to execute the following steps through a computer program:

[0324] S11, scheduling traffic channels in multiple TTIs through a downlink control information DCI, where the subcarrier spacing of the carrier where the scheduled traffic channel is located is not less than the subcarrier spacing of the carrier where the DCI scheduling the traffic channel is located;

[0325] S12, transmitting the DCI.

[0326] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and will not be elaborated herein.

[0327] Obviously, those skilled in the art should understand that the various modules or steps of the present application described above can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. Optionally, they can be implemented by program codes executable by the computing device. Thus, they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described can be executed in a different order from here, or they can be separately fabricated into individual integrated circuit modules, or multiple modules or steps among them can be fabricated into a single integrated circuit module for implementation. In this way, the present application is not limited to any specific combination of hardware and software.

[0328] The above are only the preferred embodiments of the present application and are not used to limit the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the principle of the present application shall be included within the protection scope of the present application.

Claims

1. A method for downlink control information transmission, characterized in that, Comprising: Scheduling a traffic channel in multiple transmission time intervals (TTIs) through a downlink control information (DCI); Scheduling a traffic channel in multiple TTIs through a DCI includes: indicating the number of TTIs and the number of repetitions of multi-TTI scheduling through the same bit field in the DCI.

2. The method according to claim 1, characterized in that, Indicating the number of TTIs and the number of repetitions of multi-TTI scheduling through the same bit field according to one of the following methods: Using the same bit field, determining and indicating the number of TTIs and the number of repetitions of multi-TTI scheduling through high-layer signaling configuration; Using the same bit field, determining and indicating the number of TTIs and the number of repetitions of multi-TTI scheduling through physical signaling indication.

3. The method according to claim 1, characterized in that, The method further includes: When using the DCI to indicate the number of TTIs and the number of repetitions of multi-TTI scheduling, perform repeated transmission first and then transmit different transport blocks; or transmit different transport blocks first and then perform repeated transmission.

4. The method according to claim 1, characterized in that, Scheduling a traffic channel in multiple TTIs through a DCI includes: The DCI indicates time domain resource allocation according to one of the following methods: Configuring the time interval, the starting symbol of the first TTI, and the ending symbol in the last TTI through high-layer signaling; Configuring the time interval, the starting symbol of the first TTI, the number of scheduled TTIs, and the ending symbol in the last TTI through high-layer signaling; Configuring the time interval, the starting symbol of the first TTI, the number of symbols, and the number of scheduled TTIs through high-layer signaling; Configuring the time interval through high-layer signaling, indicating the starting symbol and the number of symbols for each TTI or each group of TTIs, and the number of scheduled TTIs, where the starting symbol and the number of symbols are not all the same for each TTI; Configuring the time interval through high-layer signaling, the starting symbol of the first TTI, the number of symbols, the number of scheduled TTIs, and the number of sub-slots / micro-slots within the scheduled TTIs.

5. The method according to claim 1, characterized in that, When transmitting a physical downlink shared channel (PDSCH) in the multi-TTIs, the method for hybrid automatic repeat request - acknowledgement (HARQ-ACK) feedback for the PDSCH includes one of the following: Each TTI in the multiple TTIs uses its own TTI as the timing starting point, and respectively determines the uplink TTI where the HARQ-ACK information corresponding to each TTI is located according to the feedback timing K1 indicated by the DCI; Each TTI in the multiple TTIs uses the last TTI as the timing starting point, and determines the uplink TTI where the HARQ-ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI.

6. The method according to claim 5, characterized in that, The method further includes: When the HARQ-ACK is feedback through a semi-static codebook, if the PDSCH determined using the K1 set configured by high-layer signaling belongs to the PDSCH in multi-TTI scheduling, then determine the DCI scheduling the PDSCH as the last DCI.

7. The method according to claim 5, characterized in that, Each TTI in the multiple TTIs uses its own TTI as the timing starting point, and respectively determines the uplink TTI where the HARQ-ACK information corresponding to each TTI is located according to the feedback timing K1 indicated by the DCI includes one of the following: When the HARQ-ACK is fed back through a dynamic codebook, if the HARQ-ACK indicating the scheduling of the first PDSCH is directed to the same uplink TTI, the downlink allocation index DAI of at least one DCI in the DCI scheduling the first PDSCH needs to be incremented by one; When the HARQ-ACK is fed back through a dynamic codebook, if the HARQ-ACK indicating the scheduling of the first PDSCH is directed to the same one of the uplink TTIs, the HARQ-ACK information corresponding to the PDSCH scheduled by multiple TTIs is located at the beginning of the dynamic codebook.

8. The method according to claim 7, characterized in that, The method further includes: In the case where the HARQ-ACK information corresponding to the PDSCH scheduled by multiple TTIs is located at the beginning of the dynamic codebook, the PDSCHs scheduled by multiple TTIs are sorted according to one of the following principles: Sorted in the order of carrier CC index first and then time domain at the beginning of the codebook; Sorted in the order of time domain first and then CC index at the beginning of the codebook.

9. The method according to claim 5, characterized in that, For each TTI among the multiple TTIs, with the last TTI as the timing starting point, determining the uplink TTI where the HARQ-ACK information corresponding to all TTIs is located according to the feedback timing K1 in the DCI includes: The HARQ-ACK is fed back using a dynamic codebook. When counting DAI increments the DCI by 1, the codebook size is determined according to the actual scheduling quantity of the multiple TTIs scheduled.

10. The method according to claim 1, characterized in that, The method further includes: The DCI determines the coded block group transmission information CBGTI in one of the following ways: Independently indicates the CBGTI of each TTI among the multiple TTIs, where each TTI uses X / Y bits, where X is the number of scheduled TTIs and Y is the maximum number of coded block groups CBGs configured by radio resource control RRC; Multiple TTIs share the same CBGTI, where the TTIs with the new data indication NDI not flipped share the same CBGTI indication, and the TTIs with the NDI flipped ignore the CBGTI indication.

11. The method according to claim 1, wherein, The method further includes: The DCI determines the coded block group refresh information CBGFI in one of the following ways: Independently indicates the CBGFI of each TTI among the multiple TTIs, where for a maximum of N scheduled TTIs, each TTI uses 1 bit; or uses N1 bits to indicate the CBGFI of the TTIs with the new data indication NDI not flipped, where N1 is not greater than N; Multiple TTIs share the same CBGFI, where the TTIs with the NDI not flipped share the same CBGFI indication, and the TTIs with the NDI flipped ignore the CBGFI indication.

12. The method according to claim 1, wherein, The demodulation reference signal pattern DMRSpattern in the multiple TTIs is determined in one of the following ways: The multiple TTIs use the same DMRS pattern and the same as that in the first TTI, where the DMRSpattern of the first TTI is determined by time domain resource allocation combined with RRC configuration; The DMRS pattern of the first TTI is determined by combining time-domain resource allocation with RRC configuration. For a TTI that continuously occupies 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols, the first DMRS pattern is used, and the first DMRS pattern is determined by RRC or in a predefined manner. The multiple TTIs use the same DMRS pattern as that in the first TTI. The TTIs to which the DMRS pattern is applied are determined by configuring the TTI pattern. Among them, the DMRS pattern of the first TTI is determined by combining time-domain resource allocation with Radio Resource Control (RRC) configuration.

13. The method according to claim 4, wherein, The TTI is a sub-slot, and a sub-slot is a time-domain resource of length L allocated to a Transport Block (TB).

14. A downlink control information transmission device, wherein, It includes: A scheduling module for scheduling traffic channels in multiple Transmission Time Intervals (TTIs) through a Downlink Control Information (DCI). The scheduling module includes: A first indication sub-module for the DCI to indicate the number of scheduled TTIs in the following manner: A third indication unit for indicating the number of TTIs and the repetition times of multi-TTI scheduling through the same bit field in the DCI.

15. A storage medium, wherein, A computer program is stored in the storage medium. Among them, the computer program is set to execute the method described in any one of claims 1 to 13 when running.

16. An electronic device, comprising a memory and a processor, wherein, A computer program is stored in the memory, and the processor is set to run the computer program to execute the method described in any one of claims 1 to 13.

Images