CN113708900A

CN113708900A - Data scheduling method and device

Info

Publication number: CN113708900A
Application number: CN202010437349.7A
Authority: CN
Inventors: 薛祎凡; 张健
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-05-21
Filing date: 2020-05-21
Publication date: 2021-11-26
Also published as: WO2021233146A1

Abstract

A data scheduling method and apparatus are disclosed. The method comprises the steps that a first communication device monitors first scheduling information sent by a second communication device, when the first scheduling information is monitored, first data which is originally transmitted between the first communication device and the second communication device is sent or received according to the first scheduling information, second scheduling information sent by the second communication device is monitored, when the second scheduling information is monitored, first data which is retransmitted between the first communication device and the second communication device is sent or received according to the second scheduling information, and a field domain included in the first scheduling information is different from a field domain included in the second scheduling information. The scheme can be widely applied to the fields of communication technology field, artificial intelligence, Internet of vehicles, intelligent home networking and the like.

Description

Data scheduling method and device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data scheduling method and device.

Background

In release 15(Rel-15) of the 3rd generation standardization part (3 GPP), when data is transmitted between two communication apparatuses, one piece of scheduling information is transmitted before the data is transmitted, and the data is transmitted according to the instruction of the scheduling information.

For example, taking two communication devices as a network device and a terminal respectively as an example, before the network device schedules a data channel of the terminal for data transmission, the network device sends a Downlink Control Information (DCI) to the terminal, where the DCI is carried in a Physical Downlink Control Channel (PDCCH), and the data channel of the terminal is scheduled through the DCI, for example, a Physical Downlink Shared Channel (PDSCH) of the terminal is scheduled through the DCI, or a Physical Uplink Shared Channel (PUSCH) of the terminal is scheduled through the DCI, and the DCI may indicate transmission parameters of the shared channel, such as: and the time domain resource position of the shared channel and the like, and the terminal transmits data at the time domain resource position of the PDSCH/PUSCH according to the indication of the DCI.

As can be seen from the above, the scheduling information provides a guarantee for data transmission between the terminal and the network device, and therefore, how to improve the transmission performance of the scheduling information becomes an urgent problem to be solved.

Disclosure of Invention

The embodiment of the application provides a data scheduling method and device, and the transmission performance of scheduling information is improved.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, a data scheduling method is provided, and the method is applied to a first communication device, and the method includes: monitoring first scheduling information sent by a second communication device, when the first scheduling information is monitored, sending or receiving first data which is initially transmitted between the first communication device and the second communication device according to the first scheduling information, monitoring second scheduling information sent by the second communication device, when the second scheduling information is monitored, sending or receiving first data which is retransmitted between the first communication device and the second communication device according to the second scheduling information, wherein a field domain included in the first scheduling information is different from a field domain of the second scheduling information.

Based on the method provided by the first aspect, the first scheduling information used for initially transmitting data between the first communication device and the second scheduling information used for scheduling retransmission data between the first communication device and the second communication device may be designed to include different field domains, and there is no need to set the first scheduling information and the second scheduling information to include the same field domain.

In one possible design, the length of the second scheduling information is set to be different from the length of the first scheduling information, e.g., the length of the second scheduling information is longer than the length of the first scheduling information, and compared with the first scheduling information, the second scheduling information includes the first field and the first scheduling information does not include the first field; or, the length of the first scheduling information is longer than that of the second scheduling information, and compared with the first scheduling information and the second scheduling information, the first scheduling information includes a first field and the second scheduling information does not include the first field.

Based on the possible design, the first field domain is removed/deleted from the first scheduling information, so that the first scheduling information carries fewer field domains, or the first field domain is removed/deleted from the second scheduling information, so that the second scheduling information carries fewer field domains, the bit number of the first scheduling information or the second scheduling information is reduced, and the reliability and the coverage range of the scheduling information transmission are improved.

In one possible design, the search space corresponding to the first scheduling information is different from the search space corresponding to the second scheduling information. The monitoring parameters corresponding to the first scheduling information are different from the monitoring parameters corresponding to the second scheduling information, and the monitoring parameters include: one or more information of the configuration of the search space, the configuration of the control resource set and the temporary identifier of the wireless network; the configuration of the search space comprises one or more of the monitoring period of the search space, the format of downlink control information to be monitored, the number of candidate sets to be monitored, and the aggregation level to be monitored.

Based on the possible design, the problem that when the length of the first scheduling information is different from the length of the second scheduling information, the first communication device needs to set the output length of the decoder to be different for decoding processing when monitoring the scheduling information, the number of Blind Decoding (BD) times is increased, the power consumption of the terminal is consumed can be avoided, and the number of blind decoding times of the second communication device is ensured not to be too large.

In one possible design, monitoring the second scheduling information transmitted by the second communication device includes: and monitoring the second scheduling information by using the monitoring parameters corresponding to the second scheduling information in the search space corresponding to the second scheduling information in a first time period after the first data is received or sent according to the first scheduling information. Based on the possible design, a time period for monitoring the second scheduling information is set, only the monitoring parameter corresponding to the second scheduling information is adopted for monitoring in the time period of the second scheduling information, blind monitoring is not attempted to be carried out by utilizing the monitoring parameter of the first scheduling information and the monitoring parameter of the second scheduling information, the blind monitoring times are reduced, and the power consumption of the first communication device for monitoring the second scheduling information is reduced.

In a possible design, the length of the first scheduling information is set to be the same as that of the second scheduling information, that is, the lengths of the scheduling information during initial transmission and retransmission are aligned, so that the problems that the first communication device needs to set the output length of a decoder to be different lengths to perform decoding processing when monitoring the scheduling information, the number of blind detection times is increased, and the power consumption of the first communication device is increased are solved.

In one possible design, a first field is added to the second scheduling information, and the second field is removed from the first scheduling information, so that the second scheduling information includes the first field and does not include the second field; in order to align the lengths of the first and second scheduling information, the first scheduling information includes a second field not including the first field, and the first field is different from the second field. Based on the possible design, when the field domain is added into the scheduling information, the length of the scheduling information during initial transmission can be ensured to be aligned with the length of the scheduling information during retransmission by deleting/removing/deleting other field domains in the scheduling information, and the method is simple and easy to implement.

In one possible design, the second field includes i fields, a total length of first (i-1) of the i fields is less than a length of the first field, and the total length of the i fields is greater than or equal to the length of the first field. Based on the possible design, when the first field domain is included in the second scheduling information, i field domains included in the second field domain are sequentially removed until the total length of the removed second field domain is less than or equal to the length of the first field domain after the last field domain is removed, and the two communication parties can include the first field domain in the second scheduling information and remove the second field domain in the second scheduling information based on the rule, so that the two pieces of scheduling information are aligned, and the implementation mode is simple and easy.

In one possible design, the first scheduling information and the second scheduling information include a hybrid automatic repeat request (HARQ) processing number (HPN) and a New Data Indicator (NDI), or the first scheduling information and the second scheduling information include a Carrier Indicator Field (CIF), a HPN, and an NDI; the position and the length of the HPN in the first scheduling information are the same as those of the HPN in the second scheduling information, the position and the length of the NDI in the first scheduling information are the same as those of the NDI in the second scheduling information, and the position and the length of the CIF in the first scheduling information are the same as those of the CIF in the second scheduling information.

Based on the possible design, the HPN and the NDI can be carried in the first scheduling information during initial transmission and the second scheduling information during retransmission in a carrier aggregation scene or a non-carrier aggregation scene, and specific values of the HPN and the NDI and bit positions occupied in the scheduling information must be the same, so as to ensure that the initial transmission and the retransmission of the same data on the same HARQ process and the same carrier are identified.

In one possible design, the first scheduling information or the second scheduling information includes a third field and a fourth field, and the third field indicates a type of the at least one fourth field. Based on the possible design, the field domain used for indicating the type of the field domain reserved in the scheduling information can be carried in the scheduling information, so that the second communication device can conveniently and flexibly delete/reserve some field domains, and the deleted/reserved field domains are indicated to the first communication device, and the method is simple and easy to implement.

In one possible design, the first data is uplink data, and the first field or the second field includes one or more of the following: the method comprises the steps of an uplink shared channel indication UL-SCH indicator, a frequency domain resource allocation FDRA, a bandwidth part indication BWP indicator, an antenna port, a sounding reference signal resource indication SRS resource indicator, a redundancy version RV, a time domain resource allocation TDRA, a transmission power control TPC command, an SRS triggering trigger indication, a channel state information reference signal trigger indication CSI-RS triggering, a precoding indication, a beta offset indication beta _ offset indicator, a frequency hopping response indication, a phase tracking reference signal-demodulation reference signal PTRS-DMRS association indication, a demodulation reference signal initial sequence DMRS sequence initial association and a code block group transmission indication CBGTI. In another possible design, the first data is downlink data, and the first field or the second field includes one or more of the following: frequency domain resource allocation FDRA, BWP indicator, antipna port, SRS resource indicator, transmission configuration indication TCI, mapping relation VRB-to-PRB mapping from virtual resource blocks to physical resource blocks, physical resource block bundling size indication PRB bundling size indicator, rate matching indication rate matching indicator, redundancy version RV, time domain resource allocation TDRA, TPC command, SRS triggering indication, CSI-RS triggering indication, DMRS sequence initiation, CBGTI and code block group clearing indication CBGFI.

Based on the possible design, a plurality of field domains which can be deleted are designed, and the flexibility of deleting the field domains of the scheduling information is increased.

In a second aspect, the present application provides a communication device, which may be the first communication device or a chip or a system on a chip in the first communication device, and may also be a functional module in the first communication device for implementing the method according to the first aspect or any possible design of the first aspect. The first communication means may implement the functions performed by the first communication means in the above aspects or possible designs, which functions may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions. Such as: the first communication device may include: a processing unit and a transmitting-receiving unit;

the processing unit is used for monitoring first scheduling information sent by the second communication device;

the receiving and sending unit is used for sending or receiving first data primarily transmitted between the first communication device and the second communication device according to the first scheduling information when the processing unit monitors the first scheduling information;

the processing unit is also used for monitoring second scheduling information sent by the second communication device;

and the transceiver unit is further configured to send or receive first data retransmitted between the first communication device and the second communication device according to the second scheduling information when the processing unit monitors the second scheduling information, where a field domain included in the first scheduling information is different from a field domain of the second scheduling information.

Specifically, the relevant execution actions of the processing unit and the transceiver unit, the relevant descriptions of the first scheduling information and the second scheduling information may refer to the first aspect or any possible design of the first aspect, which is not repeated herein.

In a third aspect, a communication device is provided, which may be a first communication device or a chip or a system on a chip in a first communication device. The first communication means may implement the functions performed by the first communication means in the aspects or possible designs described above, which may be implemented by hardware. In one possible design, the first communication device may include: a processor and a communications interface, the processor being operable to enable the first communications device to carry out the functions referred to in the first aspect above or in any one of the possible designs of the first aspect, for example: the processor is used for monitoring first scheduling information sent by the second communication device, triggering the communication interface to send or receive first data initially transmitted between the first communication device and the second communication device according to the first scheduling information when the first scheduling information is monitored, and monitoring second scheduling information sent by the second communication device, and triggering the communication interface to send or receive first data retransmitted between the first communication device and the second communication device according to the second scheduling information when the second scheduling information is monitored, wherein a field domain included in the first scheduling information is different from a field domain included in the second scheduling information. In yet another possible design, the first communication device may further include a memory for storing computer-executable instructions and data necessary for the first communication device. The processor executes the computer executable instructions stored by the memory when the first communication device is operating to cause the first communication device to perform the data scheduling method as described in the first aspect or any one of the possible designs of the first aspect.

In a fourth aspect, a computer-readable storage medium is provided, which may be a readable non-volatile storage medium, and has stored therein instructions, which when executed on a computer, cause the computer to perform the data scheduling method of the first aspect or any one of the above possible designs.

In a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the data scheduling method of the first aspect or any one of the possible designs of the above aspect.

In a sixth aspect, a communication device is provided, which may be a first communication device or a chip or system on a chip in a first communication device, the first communication device including one or more processors, one or more memories. The one or more memories are coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, cause the first communication device to perform the data scheduling method of the first aspect or any possible design of the first aspect.

For technical effects brought by any design manner in the third aspect to the sixth aspect, reference may be made to the technical effects brought by the first aspect or any possible design manner in the first aspect, and details are not repeated.

In a seventh aspect, an embodiment of the present application further provides a data scheduling method, where the method may include: the second communication device sends first scheduling information to the first communication device, and first data are transmitted to the first communication device according to the first scheduling information; after the first data transmission fails, the second communication device sends second scheduling information to the first communication device, wherein the field domain included in the second scheduling information is different from the field domain included in the first scheduling information; the second communication device retransmits the first data to the first communication device according to the second scheduling information.

The description of the first scheduling information and the second scheduling information may refer to the description in the first aspect or any possible design of the first aspect, and is not repeated herein.

In an eighth aspect, an embodiment of the present application provides a communication system, where the communication system may include: the first communication device, the second communication device of any of the second aspect or the third aspect.

Drawings

Fig. 1 is a simplified schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of a communication device according to an embodiment of the present application;

fig. 3 is a flowchart of a data scheduling method according to an embodiment of the present application;

fig. 4 is a schematic diagram of scheduling information for blind detection according to an embodiment of the present application;

fig. 5a is a schematic diagram of monitoring scheduling information according to an embodiment of the present application;

fig. 5b is a schematic diagram of monitoring scheduling information according to an embodiment of the present application;

fig. 6 is a schematic diagram illustrating a method for deleting field fields according to an embodiment of the present disclosure;

fig. 7 is a flowchart of another data scheduling method according to an embodiment of the present application;

fig. 8 is a schematic diagram illustrating a communication device 80 according to an embodiment of the present disclosure;

fig. 9 is a schematic composition diagram of a communication system according to an embodiment of the present application.

Detailed Description

In the communication system, according to the difference of transmission granularity when data transmission is performed between communication apparatuses, the data transmission between the communication apparatuses can be divided into: transmission Block (TB) based transmission, Code Block Group (CBG) based transmission. The TBs and CBGs have different transmission granularities, one TB may include N CBGs, and the value of N may be {2, 4, 6, 8, 16}, for example, one TB is 800 bits, one TB includes 8 CBGs, one CBG may be 100 bits, and the specific value of N may be configured to the communication apparatus by the network device. In addition to TB-based transmission and CBG-based transmission, the data transmission between the communication devices may also be transmission based on other transmission granularities, without limitation. In the embodiment of the present application, data transmission between wireless communications is based on TB (TB-based transmission) or CBG (CBG-based transmission), which is also referred to in the present application.

In TB or CBG based transmission, in order to improve data transmission quality between communication apparatuses, a hybrid automatic repeat request (HARQ) mechanism is introduced, and data transmission is performed using a stop-and-wait protocol (stop-and-wait protocol). The HARQ mechanism includes: after the initial transmission of data to the receiving end (receiving device), the transmitting end (transmitting device) stops waiting for the acknowledgement information fed back by the receiving end, wherein the acknowledgement information includes Acknowledgement (ACK) or Negative Acknowledgement (NACK). If the sending end receives the ACK fed back by the receiving end, the transmission is determined to be successful; if the transmitting end receives NACK fed back by the receiving end, the data transmission fails, and the transmitting end retransmits the data to the receiving end, so that the data transmission quality is improved.

In the transmission based on the TB, the receiving end may use 1-bit information to perform ACK or NACK confirmation on the TB, for example, perform NACK confirmation on the TB if transmission of part or all of data included in the TB fails, and perform ACK confirmation on the TB if transmission of all of the data included in the TB succeeds; and the receiving end feeds back the ACK or NACK corresponding to the TB to the transmitting end, and if the transmitting end receives the NACK corresponding to the TB, the TB is retransmitted. In the transmission based on CBG, after receiving a TB sent by a sending end, a receiving end confirms ACK or NACK for each CBG contained in the TB by using 1bit of information and feeds back the ACK or NACK corresponding to each CGB to the receiving end; if the receiving end receives NACK corresponding to a certain CBG, the CBG is retransmitted, and other CBGs which are not influenced do not need to be retransmitted, so that the retransmission overhead is reduced.

The sending end can refer to a device for sending data in the communication device for data transmission, and the receiving end can refer to a device for receiving data in the communication device for data transmission. The following description will be given taking as an example a case where a communication apparatus for performing data communication includes a first communication apparatus and a second communication apparatus, first data is transmitted between the first communication apparatus and the second communication apparatus, scheduling information for scheduling first data to be initially transmitted is first scheduling information, and scheduling information for scheduling first data to be retransmitted is second scheduling information. It should be noted that the transmission described herein may include an initial transmission (initial transmission) or a retransmission (retransmission), and the initial transmission may also be alternatively described as a new transmission (new transmission) or a first transmission, where the initial transmission may refer to first sending the first data, and the retransmission may refer to sending the first data again after the first data is sent for the first time or sending the first data again after the first data is retransmitted.

In one example, the first communication device may be a terminal, the second communication device may be a network device, the terminal may transmit first data to the network device, the network device may also transmit the first data to the terminal, the first data transmitted by the terminal to the network device may be referred to as uplink data, the first data transmitted by the network device to the terminal may be referred to as downlink data, and scheduling information for scheduling the first data may be Downlink Control Information (DCI). In yet another example, the first communication device may be a terminal, the second communication device may also be a terminal, the first data may be SL data, and the scheduling information for scheduling the first data may be Sidelink Control Information (SCI).

Taking the scheduling information as DCI, the first scheduling information for scheduling the first transmission data and the second scheduling information for scheduling the retransmission data may be DCI in any one of the following formats (formats): DCI format1-0, DCI format1-1, DCI format1-2, DCI format0-1, DCI format0-1 and DCI format 0-2. The first scheduling information for scheduling the initial transmission data and the second scheduling information for scheduling the retransmission data may include one or more of the following field fields (1) to (31). The position of each field in the scheduling information, the number of bits occupied by each field, and the meaning indicated by the value of each field may be predefined by a protocol or determined according to network device configuration. Some field fields are used as examples for the following description:

(1) modulation and Coding Scheme (MCS) of the transport block TB 1.

The MCS is used to specify a modulation and coding scheme used for data transmission, and may occupy 5 bits (bits).

(2) New Data Indication (NDI).

The NDI may be used to determine whether the data is initially transmitted or retransmitted, and the NDI occupies 1 bit. Judging whether the current data is initially transmitted or retransmitted through whether the NDI is inverted (toggled): if the NDI in the DCI corresponding to a certain uplink HARQ process is inverted compared with the last time, the terminal can perform uplink initial transmission at this time; if the NDI is the same as the last time, the terminal needs to perform uplink adaptive retransmission. NDI reversal means that the value of NDI changes from the last 0 to the current 1 or from 1 to 0.

(3) Redundancy Version (RV).

The RV is configured to implement Incremental Redundancy (IR) HARQ transmission, that is, coded bits generated by an encoder are divided into a plurality of groups, each RV defines a transmission start point, and different RVs may be used for first transmission and each HARQ retransmission, so as to implement gradual accumulation of redundant bits and complete incremental redundancy HARQ operations.

(4) Transmit Power Control (TPC) commands.

The TPC commands may be used to adjust the transmit power on the designated timing channel, and the TCP commands may be fixed to occupy 2 bits when the terminal is configured with closed loop power control.

(5) A Physical Uplink Control Channel (PUCCH) resource indication.

The PUCCH resource indication may be used to indicate a PUCCH resource used by the terminal to send information such as HARQ-ACK feedback and Channel State Information (CSI) feedback, and specifically may indicate a time-frequency resource position occupied by the PUCCH.

(6) A Sounding Reference Signal (SRS) resource indication (resource indicator).

The SRS resource indication may be used to indicate a reference signal of an antenna port used when a Physical Uplink Shared Channel (PUSCH) is transmitted, wherein the SRS is an uplink reference signal,

(7) SRS trigger indicator (triggering indicator)

The SRS trigger indication may be used to trigger transmission of the aperiodic SRS.

(8) Channel state information-reference signal (CSI-RS) trigger indicator (triggering indicator)

The CSI-RS trigger indication may be used to trigger aperiodic CSI measurements as well as feedback.

(9) Time Domain Resource Allocation (TDRA).

The TDRA may be used to indicate time domain resources for data transmission, including time slots used for data transmission, and symbols used in the time slots.

(10) Frequency Domain Resource Allocation (FDRA).

FDRA may be used to indicate frequency domain resources used for data transmission, including which Physical Resource Blocks (PRBs) are used for data transmission.

(11) Carrier Indication Field (CIF).

CIF is used for a carrier aggregation scenario and may be used to indicate an index value of a carrier occupied by data.

(12) Bandwidth part (BWP) indication (indicator).

The BWP indication may be used to indicate BWP for data transmission, i.e., active BWP when the terminal receives/sends data.

(13) Mapping relationship of Virtual Resource Block (VRB) to Physical Resource Block (PRB): VRB-to PRB mapping.

The VRB-to-PRB mapping indication information may be used to indicate a mapping manner adopted when the VRB is mapped to the PRB, and specifically may be interleaving mapping or non-interleaving mapping.

(14) PRB bundling size indication (bundling size indicator).

The PRB bundle size indication may be used to indicate the size of the PRB bundle size for channel precoding.

(16) A rate matching indicator (rate matching indicator).

The rate matching indication may be used to indicate whether rate matching resources exist for the current transmission.

(17) Zero power channel state information-reference signal (ZP CSI-RS) triggering.

The zero-power CSI-RS trigger may be used to indicate whether a zero-power channel state information reference signal is transmitted, and may be used to transmit a CSI-RS of a neighboring cell on an indicated resource, so that the terminal may measure the neighboring cell.

(20) A Downlink Assignment Index (DAI).

The DAI may be used to indicate a position of feedback information corresponding to a current Physical Downlink Shared Channel (PDSCH) in a dynamic HARQ codebook and a length of the dynamic HARQ codebook.

(21) PDSCH to HARQ feedback timing indication: PDSCH-to-HARQ feedback timing indication.

The PDSCH-to-HARQ feedback timing indication may be used to indicate the slot spacing between the PDSCH and the corresponding HARQ feedback.

(22) A Transmission Configuration Indicator (TCI) is transmitted.

The TCI may be used to indicate spatial filtering information of the PDSCH, or beam information, for the terminal to select appropriate reception parameters to receive the PDSCH.

(23) A Code Block Group Transmission Indication (CBGTI).

This field is included in the scheduling information when the terminal is configured to employ CBG-based transmission. The CBGTI may be used to indicate which CBGs of the CBGs are scheduled, and the number of bits occupied by the CBGTI is the same as the number of the scheduled CGBs, and if N CBGs are scheduled, the CBGTI occupies N bits.

(24) Code block group clear indication (CBG flush indication, CBGFI).

When the terminal is configured to use CBG-based transmission, the field is included in the scheduling information for scheduling uplink data. The CBGFI may be used to indicate whether to delete (flush)/clear data that has been received and stored in the cache before, the CBGFI fixedly occupies 1 bit.

(25) Number of hybrid automatic repeat request processes (HPN).

The HPN may be used to indicate the index value of the HARQ process occupied by the data.

(26) Antenna port (antenna port) indication.

The antenna port indication may be used to indicate an antenna port used for data transmission.

(27) Demodulation reference signal (DMRS) sequence initialization (sequence initialization).

DMRS sequence initialization may be used to indicate sequence initialization parameters for DMRSs.

(28) An uplink shared channel indicator (UL-SCH indicator).

The UL-SCH indication may be used to indicate whether the UL-SCH is carried in the current PUSCH.

(29) Frequency hopping (frequency hopping) indication.

The frequency hopping indication, which is fixed to occupy 1bit, may be used to indicate whether to frequency hop. When the bit value is 0, it indicates that the subsequent resource allocation field does not use frequency hopping, and when the bit value is 1, it indicates that frequency hopping is used.

(30) Precoding indication (indicator).

The precoding indication may be used to indicate the precoding matrix currently used by the PUSCH.

(31) Phase Tracking Reference Signal (PTRS) -DMRS association indication.

The PTRS-DMRS association indication may be used to indicate association information between the PTRS and the DMRS.

In the HARQ mechanism, the field fields contained in the first scheduling information for scheduling initial transmission of data and the second scheduling information for scheduling retransmission of data are the same, which may affect the transmission performance of the scheduling information. For example, taking the scheduling information as DCI as an example, when the network device and the terminal perform data transmission, and when the terminal is configured to adopt CBG-based transmission, both the DCI for scheduling the initially transmitted data and the DCI for scheduling the retransmitted data need to carry CBGTI, even if the initially transmitted data is initially transmitted, when all the CGBs are scheduled by default, CBGTI needs to be carried, extra bits are added in the scheduling information, and a load (payload) of the scheduling information is increased, so that the transmission distance of the scheduling information is limited, and only a communication device with a short distance can accurately receive and analyze the scheduling information, thereby reducing the coverage of the scheduling information.

In order to solve the technical problem, according to the method and the device, a field domain included in first scheduling information for scheduling first data to be transmitted is set to be different from a field domain included in second scheduling information for scheduling first data to be retransmitted, the load of the scheduling information is reduced by deleting some field domains originally included in the scheduling information, the transmission reliability and the coverage range of the scheduling information are improved, meanwhile, the field domains which are necessary to be included in the scheduling information and the field domains which cannot be deleted are reserved, and the function of scheduling data by the scheduling information is guaranteed.

In the present application, the field domain that can be deleted in the scheduling information is referred to as a deletable field domain, the deletable field domain does not affect the scheduling function of the scheduling information after being deleted, and the content/information indicated by the deleted field domain may be acquired from other scheduling information before the current scheduling or defaults the content/information indicated by the deleted field domain to a preset default value. In the following, a description will be given of which of the field fields (1) to (31) can be deleted as a deletable field and which are non-deletable fields and are required to be carried in a field of scheduling information.

(1) The MCS is a field that can be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information of the initially transmitted data may carry the MCS indication, or may not carry the MCS indication, but adopt a default MCS value (for example, the default MCS is 0). When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry an MCS indication, but the MCS when the retransmitted data is default is the same as the MCS when the retransmitted data is initially transmitted, that is, the modulation and coding formats when the initially transmitted data and the retransmitted data are default are the same.

(2) NDI is a field that is not pruneable.

Scheduling information for scheduling the initially transmitted data and scheduling information for scheduling the retransmitted data must include NDI, and the initially transmitted data or the retransmitted data are distinguished according to the values of the NDI included in the two types of scheduling information.

(3) The RV is a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry an RV field, or a default RV value (for example, the default RV is 0) may be adopted instead of carrying the RV field. When retransmitting data, the scheduling information for scheduling the retransmitted data can carry the RV field or not, if not, the RV when the data is retransmitted by default is the same as the RV when the data is initially transmitted.

(4) The TPC command is a field that may be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a TPC field, or may not carry a TPC name field, but adopt a default transmission power (for example, the default TPC command is 0 dB). When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the TPC name field, and if not, the transmission power when the data is retransmitted is the same as the transmission power when the data is initially transmitted by default (i.e. the TPC command is considered to be 0 dB).

(5) The PUCCH resource is indicated as a field that may be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a PUCCH resource indication field, or a default PUCCH resource (for example, PUCCH resource 0 is used) may not be carried by the scheduling information for scheduling the initially transmitted data. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the PUCCH resource indication field, and if not, the PUCCH resource indication in the default retransmitted data is the same as the PUCCH resource indication in the initial transmitted data, or a default PUCCH resource (e.g., PUCCH resource 0) may be used.

(6) The SRS resource is indicated as a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry an SRS resource indication field, or may adopt a default SRS resource (for example, SRS resource 0 is used, that is, PUSCH and SRS resource 0 use the same antenna port) instead of carrying the SRS resource indication field. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the SRS resource indication field, and if not, the SRS resource indication in the default retransmitted data is the same as the SRS resource indication in the initial transmitted data, that is, the retransmitted data and the initial transmitted data use the same antenna port, or a default SRS resource (for example, SRS resource 0, that is, PUSCH and SRS resource 0 use the same antenna port) may be used.

(7) The SRS trigger indicates a field that may be truncated.

When data is initially transmitted or data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry an SRS trigger indication field, or a default triggering manner, such as triggering SRS resource 0 or not triggering SRS transmission, may be adopted instead of carrying the SRS trigger indication field. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry an SRS trigger indication field, and if not, the SRS triggered during the retransmission of data is the same as the SRS triggered during the initial transmission of data by default, that is, the SRS triggered by the initial transmission scheduling DCI is triggered, or a default triggering manner, for example, SRS resource 0 is triggered, or SRS transmission is not triggered.

(8) The CSI-RS trigger indication is a field that may be punctured.

When data is initially transmitted or data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a CSI-RS trigger indication field, or a default triggering manner, such as triggering CSI-RS corresponding to CSI-RS triggering state 0, or not triggering CSI-RS transmission, may be adopted instead of carrying the CSI-RS trigger indication field. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry a CSI-RS trigger indication field, and if not, the triggered CSI-RS when retransmitting data is defaulted to be the same as the CSI-RS triggered when initially transmitting data, that is, the CSI-RS triggered to be the same as the initially transmitted scheduling DCI is triggered, or a default triggering manner may be used, for example, the CSI-RS corresponding to the CSI-RS triggerning state 0 is triggered, or the CSI-RS is not triggered to be transmitted.

(9) The TDRA is a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a TDRA field domain, or may not carry the TDRA field domain, but adopt predefined/preconfigured time domain resource allocation. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a TDRA field domain, or may not carry a TDRA field domain, but the TDRA when retransmitting data by default is the same as the TDRA when initially transmitting data, that is, the time domain resources for transmitting data are the same, or predefined/preconfigured time domain resource allocation is adopted.

(10) FDRA is a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry the FDRA field domain, or may not carry the FDRA field domain, but adopt predefined/preconfigured frequency domain resource allocation. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry an FDRA field domain, or may not carry the FDRA field domain, but the FDRA when retransmitting data is the same as the FDRA when initially transmitting data by default, that is, the frequency domain resources for transmitting data are the same, or predefined/preconfigured frequency domain resource allocation is adopted.

(11) CIF is an undeletable field.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry the CIF. When retransmitting data, the scheduling information of the scheduling retransmission data carries a CIF field, and the specific values of the CIF and the bit positions occupied in the scheduling information during initial transmission and retransmission must be the same so as to ensure that the initial transmission and the retransmission of the same data are identified.

(12) BWP indicates a field that is pruneable.

When the data is initially transmitted or the data is transmitted for the first time, the BWP indication may be carried in the scheduling information of the data to be initially transmitted, or the currently activated BWP may be used by default for transmission without carrying the BWP indication. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the BWP indication, but the BWP when retransmitting data by default is the same as the BWP when initially transmitting data, that is, the BWP for transmitting data is the same.

(13) The mapping relationship of VRBs to PRBs is a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a field domain of mapping relationship from the VRB to the PRB, or may not carry the field domain of mapping relationship from the VRB to the PRB, but adopt a default mapping manner, for example, interleaving mapping or non-interleaving mapping. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a mapping relation field from the VRB to the PRB, or may not carry a mapping relation field from the VRB to the PRB, but a mapping mode when retransmitting data is the default is the same as that when initially transmitting data, or a default mapping mode is adopted, for example, interleaving mapping or non-interleaving mapping.

(14) The PRB bundle size is indicated as a field that can be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a field indicating the bundling size of the PRB, or may not carry the field indicating the bundling size of the PRB, but adopt a predefined/preconfigured bundling size. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a field indicating the bundling size of a PRB, or may not carry a field indicating the bundling size of a PRB, but the bundling size when retransmitting data is the same as the bundling size when initially transmitting data by default, or a predefined/preconfigured bundling size is used.

(16) The rate matching indication is a field that may be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a field for rate matching indication, or may not carry a field for rate matching indication but defaults to no rate matching resource. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a rate matching indication field, or may not carry a rate matching indication field, but the rate matching resource when the data is retransmitted by default is the same as the rate matching resource when the data is initially transmitted, or no rate matching resource is defaulted.

(17) The ZP CSI-RS trigger is a field that can be pruned.

When data is initially transmitted or data is transmitted for the first time, a ZP CSI-RS trigger indication field may be carried in scheduling information for scheduling the initially transmitted data, or a default trigger mode, such as triggering a ZP CSI-RS corresponding to a CSI-RS triggering state 0, or not triggering the ZP CSI-RS, may not be carried in the ZP CSI-RS trigger indication field. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry a ZP CSI-RS trigger indication field, and if not, the ZP CSI-RS triggered during the data retransmission is the same as the ZP CSI-RS triggered during the data initial transmission, that is, the ZP CSI-RS triggered by the DCI initial transmission is triggered, or a default triggering mode may be used, for example, the ZP CSI-RS corresponding to the CSI-RS triggerning state 0 is triggered, or ZP CSI-RS transmission is not triggered.

(20) The DAI is an undeletable field.

When the terminal uses the dynamic HARQ codebook, DAI is used in both initial transmission and retransmission to determine the content of the HARQ codebook.

(21) The PDSCH-to-HARQ feedback timing indication is a field that may be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry the PDSCH to the HARQ feedback timing indication field, or may not carry the PDSCH to the HARQ feedback timing indication field, but adopt a default value, for example, equal to 4. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the PDSCH to the HARQ feedback timing indication field, and if not, the timing when the data is retransmitted by default is the same as the timing when the data is initially transmitted, that is, the values of K1 for initial transmission and retransmission are the same, or a default value may be used, for example, equal to 4.

(22) TCI is a field that can be truncated.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a TCI field, or may not carry the TCI field, but default to use the same TCI state as the PDCCH. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry a TCI field, and if not, the TCI state when the data is retransmitted by default is the same as the TCI state when the data is initially transmitted, or the TCI state same as the PDCCH is adopted by default.

(23) The CBGTI is a field domain which can be deleted in the initial transmission and is a field domain which can not be deleted in the retransmission.

When a terminal is configured to employ CBG-based transmission, this field must be included in the scheduling information for scheduling retransmission data. And the scheduling information for scheduling newly transmitted data does not need to carry the field, and all CBGs can be scheduled by default at the moment.

(24) CBGFI is a field that can be truncated.

When the terminal is configured with transmission based on the CBG, in downlink data scheduling, when data is initially transmitted or data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a CBGFI field domain, or may not carry the CBGFI field domain, but defaults to not empty or empty the buffer for storing the data. When retransmitting data, the scheduling information for scheduling the retransmitted data may or may not carry the CBGFI field, and if not, the default retransmitted data has the same indication as the initially transmitted data, and the buffer storing the data may not be emptied or emptied by default.

(25) The HPN is a non-pruneable field.

When data is transmitted for the first time or the first time, the scheduling information for scheduling the data to be transmitted for the first time and the scheduling information for scheduling the data to be retransmitted both need to carry HPN field fields, and the specific values of the HPN during the data to be transmitted for the first time and the data to be retransmitted and the bit positions occupied in the scheduling information need to be the same, so as to distinguish the data to be transmitted for the first time or the data to be retransmitted for the first time.

(26) an antenna port indicates a field domain that is pruneable.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information of the initially transmitted data can carry an antenna port indication field domain, or a predefined/preconfigured antenna port can be used instead of carrying the antenna port indication field domain. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry an antenna port indication field domain, or may not carry an antenna port indication field domain, but an antenna port when retransmitting data by default is the same as the antenna port when initially transmitting data, or a predefined/preconfigured antenna port is used.

(27) DMRS sequences are initialized to a field domain that can be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry the DMRS sequence initialization field, or may use a predefined/preconfigured value, for example, 0 or 1, instead of carrying the DMRS sequence initialization field. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry the DMRS sequence initialization field, or may not carry the DMRS sequence initialization field, but the DMRS sequence initialization indication when retransmitting data is the same as that when initially transmitting data by default, or a predefined/preconfigured value is used, for example, 0 or 1.

(28) The UL-SCH indicator is a field that can be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a field of an UL-SCH indicator, or may use a predefined/preconfigured value, for example, 0 or 1, instead of carrying the field of the UL-SCH indicator. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a field of a UL-SCH indicator, or may not carry the field of the UL-SCH indicator, but the UL-SCH indicator when retransmitting data is the same as that when initially transmitting data by default, or a predefined/preconfigured value is used, for example, 0 or 1.

(29) The frequency hopping indication is a field that can be pruned.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a frequency hopping indication field domain, or may use a predefined/preconfigured value instead of carrying the frequency hopping indication field domain, for example, frequency hopping or no frequency hopping. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a frequency hopping indication, or may not carry a frequency hopping indication, but the frequency hopping mode when retransmitting data by default is the same as the frequency hopping mode when initially transmitting data, or a predefined/preconfigured value is used, for example, frequency hopping or no frequency hopping.

(30) The precoding indication is a field that can be punctured.

When the data is initially transmitted or the data is transmitted for the first time, the scheduling information for scheduling the initially transmitted data may carry a precoding indication field, or a default precoding matrix, such as precoding matrix 0, may be used instead of carrying the precoding indication field. When retransmitting data, the scheduling information for scheduling the retransmitted data may carry a precoding indication field, or may not carry a precoding indication field, but a precoding matrix used when the data is retransmitted by default is the same as that used when the data is initially transmitted, or a default precoding matrix is used, for example, precoding matrix 0.

(31) The PTRS-DMRS association is indicated as a field domain that may be punctured.

When the initial transmission data or the data is transmitted for the first time, the PTRS-DMRS association indication field domain can be carried in the scheduling information of the scheduling initial transmission data, or a predefined/preconfigured association method can be used instead of carrying the PTRS-DMRS association indication field domain. When retransmitting data, the scheduling information for scheduling the retransmitted data can carry a PTRS-DMRS association indication field domain, or can not carry the PTRS-DMRS association indication field domain, but the association mode used when the data is retransmitted by default is the same as that used when the data is initially transmitted, or a predefined/preconfigured association method is used.

The following describes a data scheduling method provided in an embodiment of the present application with reference to the drawings of the specification.

The data scheduling method provided in the embodiment of the present application may be used in any system of a fourth generation (4G) system, a Long Term Evolution (LTE) system, a fifth generation (5G) system, a New Radio (NR) system, a vehicle-to-any communication (V2X) system for NR-vehicles, and an internet of things system, and may also be applied to other next generation communication systems, without limitation. The following describes a data scheduling method provided in an embodiment of the present application, by taking the communication system shown in fig. 1 as an example.

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application, and as shown in fig. 1, the communication system may include a network device and a plurality of terminals, such as: terminal 1, terminal 2, and terminal 3. In the system shown in fig. 1, data transmission may be performed between the terminal and the network device through the Uu port, for example, the network device may send downlink data to the terminal through the Uu port, and the terminal may send uplink data to the network device through the Uu port. As described above, the network device and the terminal in fig. 1 may be both referred to as a communication apparatus, and the transmission between the terminal and the network device and between the terminal and the terminal may be TB-based transmission or CBG-based transmission. It should be noted that fig. 1 is an exemplary framework diagram, the number of nodes included in fig. 1 is not limited, and other nodes may be included in addition to the functional nodes shown in fig. 1, such as: core network devices, gateway devices, application servers, etc., without limitation.

The network device is mainly used for realizing the functions of resource scheduling, wireless resource management, wireless access control and the like of the terminal. Specifically, the network device may be any one of a small cell, a wireless access point, a transmission point (TRP), a Transmission Point (TP), and some other access node. In the embodiment of the present application, the apparatus for implementing the function of the network device may be a network device, or may be an apparatus capable of supporting the network device to implement the function, such as a chip system (e.g., a processing system composed of one or more chips) or a modem (modem). The following describes a data scheduling method provided in an embodiment of the present application, by taking an example that a device for implementing a function of a network device is a network device.

The terminal may be a terminal equipment (terminal equipment) or a User Equipment (UE), or a Mobile Station (MS), or a Mobile Terminal (MT), etc. Specifically, the terminal may be a mobile phone (mobile phone), a tablet computer or a computer with a wireless transceiving function, and may also be a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city (smart city), a smart home, a vehicle-mounted terminal, and the like. In the embodiment of the present application, the apparatus for implementing the function of the terminal may be the terminal, or may be an apparatus capable of supporting the terminal to implement the function, such as a system-on-chip (e.g., a processing system composed of one chip or multiple chips) or a modem. The following describes a data scheduling method provided in an embodiment of the present application, by taking a device for implementing a function of a terminal as an example.

In a specific implementation, each network element shown in fig. 1 is as follows: the terminal and the network device may adopt the composition structure shown in fig. 2 or include the components shown in fig. 2. Fig. 2 is a schematic composition diagram of a communication device 200 according to an embodiment of the present application, where when the communication device 200 has a function of a terminal according to the embodiment of the present application, the communication device 200 may be a terminal or a chip or a system on a chip in the terminal. When the communication apparatus 200 has the functions of the network device according to the embodiment of the present application, the communication apparatus 200 may be a network device or a chip or a system on a chip in the network device.

As shown in fig. 2, the communication device 200 may include a processor 201, a communication line 202, and a communication interface 203. Further, the communication device 200 can also include a memory 204. The processor 201, the memory 204 and the communication interface 203 may be connected via a communication line 202.

The processor 201 may be a Central Processing Unit (CPU), a general purpose processor Network (NP), a Digital Signal Processor (DSP), a microprocessor, a microcontroller, a Programmable Logic Device (PLD), or any combination thereof. The processor 201 may also be other means with processing functionality such as a circuit, a device, or a software module.

A communication line 202 for transmitting information between the respective components included in the communication apparatus 200.

A communication interface 203 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), or the like. The communication interface 203 may be a radio frequency module, a transceiver, or any device capable of enabling communication. In the embodiment of the present application, the communication interface 203 is taken as an example of a radio frequency module, where the radio frequency module may include an antenna, a radio frequency circuit, and the like, and the radio frequency circuit may include a radio frequency integrated chip, a power amplifier, and the like.

A memory 204 for storing instructions. Wherein the instructions may be a computer program.

The memory 204 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and/or instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disc storage media or other magnetic storage devices, and the optical disc storage includes a compact disc, a laser disc, an optical disc, a digital versatile disc, a blu-ray disc, and the like.

It should be noted that the memory 204 may exist independently from the processor 201, or may be integrated with the processor 201. The memory 204 may be used for storing instructions or program code or some data etc. The memory 204 may be located inside the communication device 200 or outside the communication device 200, which is not limited. The processor 201 is configured to execute the instructions stored in the memory 204 to implement the data scheduling method provided in the following embodiments of the present application.

In one example, processor 201 may include one or more CPUs, such as CPU0 and CPU1 in fig. 2.

As an alternative implementation, the communication device 200 includes multiple processors, for example, the processor 207 may be included in addition to the processor 201 in fig. 2.

As an alternative implementation, the communication apparatus 200 further comprises an output device 205 and an input device 206. The input device 206 is a keyboard, mouse, microphone, joystick, or the like, and the output device 205 is a display screen, speaker (spaker), or the like.

It should be noted that the communication apparatus 200 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device with a similar structure as that in fig. 2. Further, the constituent structures shown in fig. 2 do not constitute limitations of the communication apparatus, and the communication apparatus may include more or less components than those shown in fig. 2, or combine some components, or a different arrangement of components, in addition to the components shown in fig. 2.

In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.

The following describes a data scheduling method provided in the embodiment of the present application, with reference to the communication system shown in fig. 1, by taking the example that the second communication device sends the first scheduling information and the second scheduling information to the first communication device. The second communication device may be the network device or a functional module or a chip system or a modem in the network device in fig. 1 or other functional modules, the first communication device may be the terminal or a functional module or a chip system or a modem in the terminal in fig. 1 or other functional modules, for example, the second communication device may be the network device in fig. 1, and the first communication device may be the terminal 1 in fig. 1. Alternatively, the second communication device may be the terminal in fig. 1 or a functional module or a chip system or a modem in the terminal or other functional modules, the first communication device may be the terminal in fig. 1 or a functional module or a chip system or a modem in the terminal or other functional modules, for example, the second communication device may be the terminal 1 in fig. 1, and the first communication device may be the terminal 3 in fig. 1. In the following embodiments, each device may have the components shown in fig. 2, and actions, terms, and the like related to each embodiment may be mutually referred to, a name of a message exchanged between devices or a name of a parameter in the message, and the like in each embodiment are only an example, and other names may also be used in specific implementations, without limitation. For example, "comprising" as used herein may be alternatively described as "including" or "carrying" and the like.

Fig. 3 is a data scheduling method provided in an embodiment of the present application, where the method supports scheduling information to schedule downlink data, and the scheduling information in the method shown in fig. 3 may be referred to as downlink scheduling information, for example, the first scheduling information may be referred to as first downlink scheduling information, and the second scheduling information may be referred to as second downlink scheduling information. The second communication device transmits the first data to the first communication device newly according to the first scheduling information, and the second communication device retransmits the data to the first communication device according to the second scheduling information, wherein the first data is downlink data. As shown in fig. 3, the method may include:

step 301: the second communication device transmits the first scheduling information to the first communication device.

The first scheduling information may be used to schedule first data initially transmitted between the first communication apparatus and the second communication apparatus. For example, the first scheduling information may be used to schedule first data initially transmitted by the second communication apparatus to the first communication apparatus, that is, schedule downlink data initially transmitted.

In one example, the first scheduling information may be the same as the protocol-specified scheduling information, and includes a protocol-specified field, such as one or more fields of (1) to (31) above. Or, in another example, to reduce the load of the first scheduling information during initial transmission and improve the coverage and transmission performance of the first scheduling information, a field, such as a first field, in the scheduling information of the existing scheduling initial transmission data, where a specific value of the field can be obtained without being indicated by the scheduling information may be deleted, and a field, which must be indicated by the scheduling information to the second communication device, is reserved to obtain the first scheduling information. The first field domain may include one or more deletable field domains, in this embodiment of the present application, a field domain whose specific value can be known without being indicated by the scheduling information may be referred to as a deletable field domain, the deletable field domain may refer to a field domain indicated to the first communication apparatus without being carried in the scheduling information, a value of the deletable field domain may be a default value at the time of initial transmission, and the default value may be preconfigured to the first communication apparatus.

The first data is downlink data, and the first field may include one or more of the following field fields that can be deleted: FDRA, BWP indicator, antiport, SRS resource indicator, TCI, VRB-to-PRB mapping, PRB bundling size indicator, rate matching indicator, RV, TDRA, TPC command, SRS trigger indication, CSI-RS trigger indication, DMRS sequence initiation, CBGTI, CBGFI. When the values of the field fields are the default values, the second communication device may exclude the field fields from the first scheduling information, and after receiving the first scheduling information, the first communication device does not translate the field fields from the first scheduling information, and determines that the values of the field fields are the default values. For example, when the first field is CBGTI, the default value is all 1, that is, the scheduling information for scheduling the initial transmission data does not include CBGTI, and all CBGs in the initial transmission data are sent by default. For another example, when the first field is CBGFI, the default value is 0, that is, the scheduling information for scheduling the initial transmission data does not include CBGFI, and it is default that the buffer does not need to be emptied in the initial transmission data. For example, when the first field is RV, the default value is 0, that is, the scheduling information for scheduling the initial transmission data does not include RV, and the initial transmission data is transmitted by using redundancy version 0 as a default.

Specifically, the first field includes which field fields can be specified by the protocol in advance; alternatively, the first communication device and the second communication device are configured in advance when they are shipped from a factory.

For example, assuming that the existing scheduling information for scheduling initial transmission includes field fields of MCS, antenna port, SRS resource indication, TDRA, BWP indication, FDRA, and RV, as described above, the RV may adopt a default value (for example, 0) and need not be carried in the first scheduling information and indicated to the first communication device, and therefore, in step 301, the RV field in the scheduling information of the original scheduling initial transmission data may be deleted to obtain the first scheduling information. The following table i shows field fields included in the first scheduling information, for example, the first scheduling information includes MCS, antenna port, SRS resource indication, TDRA, BWP indication, and FDRA.

Watch 1

For example, the second communication apparatus may utilize an encoder to encode the first scheduling information, and utilize a Radio Network Temporary Identifier (RNTI) corresponding to the first scheduling information to perform scrambling processing on the encoded first scheduling information, and carry/bear the scrambled first scheduling information on a control channel to send to the second communication apparatus.

The encoder may be an arithmetic unit having an encoding function in a modem included in the second communication apparatus. Illustratively, one or more encoders may be included in the modem, and when a plurality of encoders are included in the modem, a plurality of information encodings may be performed in parallel, and the output lengths of the different encoders may be the same or different. The second communication apparatus may perform encoding processing on the first scheduling information using an encoder having an output length equal to the length of the first scheduling information.

The length of the first scheduling information is equal to the total length of the number of bits occupied by all the field fields included in the first scheduling information. If the first scheduling information includes three field fields, i.e., a first field, a second field, and a third field, the first field occupies 4 bits, the second field occupies 5 bits, and the third field occupies 4 bits, the length of the first scheduling information is 13 bits.

If the first scheduling information is DCI, the control channel carrying the first scheduling information may be a Physical Downlink Control Channel (PDCCH); if the first scheduling information is SCI, the control channel carrying the first scheduling information may be a Physical Sidelink Control Channel (PSCCH).

Step 302: the second communication device initially transmits the first data to the first communication device according to the first scheduling information.

Wherein the first data may be data for TB-based transmission or data for CBG-based transmission.

For example, the second communications apparatus may initially transmit the first data to the first communications apparatus at a time-frequency resource location indicated by the first scheduling information. The second communication apparatus may transmit the first data to the first communication apparatus at the time domain position and carrier indicated by the first scheduling information using the HARQ process.

Step 303: the first communication device monitors first scheduling information.

For example, the first communication device may monitor the first scheduling information using the monitoring parameter corresponding to the first scheduling information in the search space corresponding to the first scheduling information.

The monitoring parameter corresponding to the first scheduling information may at least include one or more of configuration of a search space, configuration of a control resource set (CORESET), radio network temporary identifier (radio network temporary identifier), number of candidate sets (candidates) to be monitored, and aggregation level to be monitored. The search space corresponding to the first scheduling information and the monitoring parameter corresponding to the first scheduling information may be pre-configured to the first communication device, or may be indicated to the first communication device by the second communication device, without limitation. For example, as shown in fig. 5a, three search spaces are configured for the first scheduling information, and the second communication device may monitor the first scheduling information in the three search spaces. For another example, as shown in fig. 5b, if the search space 1 and the search space 2 among the three search spaces are arranged to correspond to the first scheduling information, the second communication device may monitor the first scheduling information in the search spaces 1 and 2.

Specifically, the process of monitoring the first scheduling information by the second communication device using the monitoring parameter corresponding to the first scheduling information in the search space corresponding to the first scheduling information may be as shown in fig. 4. As shown in FIG. 4, the process may include S1-S4:

and S1, the first communication device determines the candidate monitoring position of the control channel according to the CORESET and the search space configuration.

The first communication device may determine, according to the CORESET, information such as a frequency band occupied by the monitoring location of the control channel and the number of occupied Orthogonal Frequency Division Multiplexing (OFDM) symbols, and determine, according to the search space configuration, information such as a start OFDM symbol number of the monitoring location of the control channel and a monitoring period of the control channel.

S2, receiving a control channel at each candidate monitored location.

And S3, decoding the control channel received at each candidate monitoring position.

Specifically, the terminal may perform decoding at the candidate time-frequency position of the control channel by using a decoder, where an output length of the decoder is a length of the DCI. Decoding is considered successful if the Cyclic Redundancy Check (CRC) of the decoded information bits is the same as the CRC carried by the control channel, which can be scrambled by the RNTI.

The decoder may be an arithmetic unit having a decoding function in a modem included in the first communication device. Illustratively, the modem may include one or more decoders, the output length of different decoders being different. The first communication apparatus may decode the first scheduling information using a decoder having an output length identical to a length of the first scheduling information.

S4, parsing/translating the decoded first scheduling information, and determining information indicated by each field included in the first scheduling information.

It should be noted that, when parsing/translating the decoded first scheduling information, the following field fields carried in the scheduling information need to be translated first: and after determining which HARQ process data on which carrier is to be initially transmitted or retransmitted according to the CIF, the HPN and the NDI, translating other field domains included in the first scheduling information. In this application, the locations of the CIF, the HPN, and the NDI in the scheduling information may be well-defined protocols, and may be configured in advance to the second communication device.

Step 304: when the first scheduling information is monitored, the first communication device receives first data according to the first scheduling information.

For example, the first communication apparatus may receive the first data on the time-frequency resources indicated by the first scheduling information according to information indicated by each field included in the first scheduling information.

Further, if the first communication device successfully receives the first data, it indicates that the first data transmission is successful, and the first communication device feeds back ACK to the second communication device, otherwise, if the first communication device unsuccessfully receives the first data, it indicates that the first data transmission is failed, and the first communication device feeds back NACK to the second communication device. The method for determining whether the first communication device successfully receives the first data may refer to the prior art, and is not repeated herein.

Further, if the first data is successfully transmitted, the process is ended, the transmission of the first data is ended, and the transmission of other data is performed. If the first data transmission fails, the following steps 305 to 308 are performed.

Step 305: the first data transmission fails and the second communication device transmits second scheduling information to the first communication device.

And if the second communication device receives NACK corresponding to the first data fed back by the first communication device, the second communication device considers that the transmission of the first data fails and sends second scheduling information to the first communication device.

Wherein the second scheduling information may be used to schedule the first data for retransmission between the first communication apparatus and the second communication apparatus. The first scheduling information includes a field different from a field included in the second scheduling information. The field included in the first scheduling information may be different from the field included in the second scheduling information, and may include: the type of the field domain included by the first scheduling information is the same as the type of the field domain included by the second scheduling information, but the length of the field domain included by the first scheduling information is different from the length of the field domain included by the second scheduling information, and like the same field domain, the field domain occupies 3 bits in the first scheduling information and occupies 5 bits in the second scheduling information; alternatively, the first scheduling information includes a field of a different type from the field of the second scheduling information.

Example one, the length of the second scheduling information is different from the length of the first scheduling information, for example, the length of the first scheduling information is greater than the length of the second scheduling information, the first scheduling information includes a first field, and the second scheduling information does not include the first field; or the length of the first scheduling information is smaller than that of the second scheduling information, the first scheduling information does not include the first field domain, and the second scheduling information includes the first field domain. The description of the first field is as described above, and is not repeated.

It should be noted that, under the condition that the first scheduling information includes the first field domain and the second scheduling information does not include the first field domain, if the retransmitted first data needs to be scheduled according to the specific value of the first field domain when the first data is retransmitted, the second communication device may default the value of the first field domain to be the default value or the value of the first field domain is the same as the value of the first field domain when the first data is initially transmitted. For example, the following table two shows field fields included in the second scheduling information, and when the table one and the table two are compared, the second scheduling information does not include the FDRA field, and the frequency domain position when the first data is retransmitted may be the same as the frequency domain position when the first data is initially transmitted by default.

Watch two

In order to avoid the problem that the first communication device needs to set the output length of the decoder to a plurality of different lengths for performing decoding processing when monitoring the scheduling information due to the fact that the length of the first scheduling information is different from the length of the second scheduling information, for example, the output length of the decoder is set to the length of the first scheduling information and the length of the second scheduling information for performing decoding processing, the number of times of Blind Decoding (BD) is increased, and the power consumption of the terminal is consumed, in an example one, the search space corresponding to the first scheduling information is set to be different from the search space corresponding to the second scheduling information; and/or setting the monitoring parameters corresponding to the first scheduling information and the monitoring parameters corresponding to the second scheduling information to be different, monitoring the first scheduling data by using the search space and the monitoring parameters corresponding to the first scheduling information when the first data is initially transmitted, monitoring the second scheduling information by using the search space and the monitoring parameters corresponding to the second scheduling information when the first data is retransmitted, so that the first communication device sets the output length of the decoder to the length of the first scheduling information for decoding processing when monitoring the first scheduling information, and sets the output length of the decoder to the length of the second scheduling information for decoding processing when monitoring the second scheduling information, thereby ensuring that the number of blind tests of the first communication device is not too large, and reducing the power consumption brought by the blind test of the first communication device on the scheduling information.

Example two, the length of the second scheduling information is the same as the length of the first scheduling information. The second scheduling information comprises a first field domain and does not comprise a second field domain, namely the second field domain occupies 0bit in the second scheduling information, the first scheduling information comprises the second field domain and does not comprise the first field domain, namely the first field occupies 0bit in the first scheduling information. Comparing the first scheduling information with the second scheduling information, it is found that the second scheduling information lacks a second field included in the first scheduling information, but adds a first field not included in the first scheduling information, which can be understood as adding the first field to the first scheduling information, and truncating the first scheduling information to which the first field is added, for example, truncating the second field in the first scheduling information to which the first field is added, and carrying the field included in the truncated first scheduling information in the second scheduling information, so that the length of the second scheduling information is the same as that of the first scheduling information, that is, the length of the scheduling information at the initial transmission is aligned with that of the scheduling information at the retransmission.

The second field may include one or more field fields in the deletable field, and the description of the deletable field may refer to that in step 301, which is not repeated herein. The first field domain is different from the second field domain, and the length of the second field domain is smaller than or equal to the first field domain. Specifically, it may be determined which second field fields are deleted with reference to the manner shown in fig. 6, and as shown in fig. 6, the manner may include:

sorting the field fields which can be deleted, setting the length of the first scheduling information to be L1, and setting the length of the first scheduling information (which can be called as the initial length of the second scheduling information) after the first field is added to be L2 (0); setting i to 0, i to i +1, deleting the 1 st field in the field from the second scheduling information, if the length of the second scheduling information L2(1) after deleting the 1 st field is greater than L1, executing i +1, deleting the 2 nd field in the field from the second scheduling information, and so on, until the ith field is deleted, the length of the second scheduling information L2(i) is less than or equal to the first field, and ending the flow. Wherein, m (i) in fig. 6 is the length of the ith field that can be deleted.

It should be noted that, in the embodiment of the present application, the ordering manner of the deletable field domains is not limited, and the deletable field domains may be arranged in an order from a large bit number to a small bit number, or may be arranged in an order from a small bit number to a large bit number, or may be arranged randomly, or may be configured by a network device, and the like.

For example, downlink data is scheduled by using DCI format 1_ 1. The first field is CBGTI and CBGFI, i.e. CBGTI and CBGFI are not included in the first-transmitted DCI. If the number of the CBGs configured to the terminal by the network equipment is N, the bit length of the CBGTI is N bits. The bit length of CBGFI is 1 bit. The field domain which can be deleted and included in the second field domain is SRS request (2bit), BWP indicator (2bit), Antenna port (4bit), RV indication (2bit) and the like, namely, the field domain such as SRS request (2bit), BWP indicator (2bit), Antenna port (4bit), RV indication (2bit) and the like can not be included in the retransmission DCI. In order to align the length of the retransmitted DCI with that of the initially transmitted DCI, the length of N +1 bits needs to be selected from SRS request (2 bits), BWP indicator (2 bits), Antenna port (4 bits), and RV indicator (2 bits) for puncturing. The ordering of these pruneable field fields is assumed to be: SRS request (2bit) > BWP indicator (2bit) > Antenna port (4bit) > RV indicates (2 bit). If the network device configures the terminal with CBGs in a number of N-4, that is, the bit length of the CBGTI is 4 bits, the following 3 fields may be deleted in the manner shown in fig. 6: SRS request, BWP indicator, Antenna port. At this time, during data retransmission, it can be considered that the values of SRS request, BWP indicator and Antenna port indicated in the initially transmitted DCI are still used for retransmitted data. For example, if the SRS request value indicated in the initial transmission DCI is 1, the first group of SRS is triggered, the BWP indicator value is 0, the BWP0 is indicated, the Antenna port value is 0, and the 0 th Antenna port is indicated, that is, the PDSCH reception of the initial transmission data is accompanied by the transmission of the 1 st group of SRS, the initial transmission data is transmitted on the BWP0, and the PDSCH is received by using the 0 th Antenna port. In data retransmission, the PUSCH of the initial transmission data is also transmitted on BWP0 along with the transmission of the 1 st SRS group, and the PDSCH is received using the 0 th antenna port. If the number of CBGs configured by the network device to the terminal is N-2, that is, the bit length of the CBGTI is 2 bits, only the following 3 fields may be deleted in the manner shown in fig. 6: SRS request, BWP indicator. Similarly, the SRS request and BWP indicator indicated in the initial DCI may still be used for retransmitted data, and will not be explained here by way of example.

It should be noted that the method shown in fig. 6 may be pre-configured for the second communication apparatus and the first communication apparatus, and both apparatuses may determine which second field fields are deleted by using the method shown in fig. 6. In addition, when the length of the second field domain is greater than that of the first field domain, after the second field domain is deleted, zero padding processing can be performed on the second scheduling information, so that the length of the second scheduling information is aligned with that of the first scheduling information, and therefore the number of blind tests is avoided being too many. For example, if the length of the first scheduling information is 10 bits, and the length of the second scheduling information after the second field is deleted is 9 bits, a zero may be added to the end of the second scheduling information, so that the length of the second scheduling information is also 10 bits. For another example, the first field is CBGTI and CBGFI, and the number of CBGs configured by the network device to the terminal is N-4, that is, the bit length of the CBGTI is 4 bits. The bit length of CBGFI is 1 bit. The field fields which can be deleted and reduced and included in the second field are SRS request (2bit), BWP indicator (2bit) and Antenna port (4 bit). The second scheduling information has CBGTI and CBGFI more, SRS request, BWP indicator, Antenna port less, and 3 bits less as a whole, compared to the first scheduling information. At this time, three zeros may be added to the end/tail of the second scheduling information to align the length of the second scheduling information with the length of the first scheduling information.

In addition to the first communication device and the second communication device determining which second field fields are deleted in the manner shown in fig. 6, the second communication device may determine which field is deleted and which field is reserved, for example, determine which field is deleted in the manner shown in fig. 6, and indicating the deleted field and/or the reserved field to the first communication device, for example, the second scheduling information or the first scheduling information may further include a third field and a fourth field, the third field may be indication information, the third field may be used to indicate a type of at least one fourth field, and the fourth field may include an un-deleted field in the second field, i.e. the reserved field, the sum of the number of bits of the third field, the number of bits of the fourth field and the number of bits of the first field may be equal to or smaller than the number of bits of the second field. When the sum of the number of bits of the third field, the number of bits of the fourth field, and the number of bits of the first field is smaller than the number of bits of the second field, two zeros may be added at the end/tail of the second scheduling information, so that the length of the second scheduling information is aligned with the length of the first scheduling information.

In the present application, there is a corresponding relationship between the types of the third field domain and the at least one fourth field domain, and the corresponding relationship may be configured by the network device, or may be predefined by a protocol, which is not limited. The field fields included in the fourth field, that is, the field fields in the second field that need to be retained in the second scheduling information, may also be configured by the network device, or may be predefined by the protocol, which is not limited. Illustratively, if the field in the second field needs to be retained in the second scheduling information exists 2^MIn different combinations, i.e. there are 2^MA fourth field in a combined form, the third field can carry M bits, and the M bits can be used to indicate the 2^MAnd (4) combining the two.

For example, downlink data is scheduled by using DCI format 1_ 1. The first field is CBGTI, i.e. CBGTI and CBGFI are not included in the first-pass DCI. If the number of the CBGs configured to the terminal by the network equipment is N, the bit length of the CBGTI is N bits. The bit length of CBGFI is 1 bit. The field domain which can be deleted and included in the second field domain is SRS request (2bit), BWP indicator (2bit), Antenna port (4bit), RV indication (2bit) and the like, namely, the retransmission DCI can not include SRS request (2bit), BWP indicator (2bit), Antenna port (6bit), RV indication (2bit) and the like, namely, total 12 bits can be deleted. If the number of CBGs configured by the network device to the terminal is N-4, that is, the bit length of the CBGTI is 4 bits. Only 5 bits from the 12 bits need to be selected for puncturing and the remaining 7 bits are reserved. At this time, 2 bits of the remaining 7 bits may be used to indicate the contents of the remaining 5 bits. As shown in table three below. When the 2-bit indication information is 00, the remaining 5 bits contain information of SRS request (2bit) + BWP indicator (2bit) + padding (1bit), where padding is to fill in 1 '0' bit. At this time, the content of the Antenna port (6bit) and the RV indication (2bit) is the same as the content of the initial transmission indication by default. By the method, the network equipment can more flexibly determine which information is indicated in the second scheduling information, and the flexibility of the scheduling information is improved.

Watch III

It should be noted that, in each embodiment of the present application, the format of the first scheduling information is the same as the format of the second scheduling information; alternatively, the format of the first scheduling information is different from the format of the second scheduling information. For example, in this embodiment, the first scheduling information may adopt DCI format 0_2/format 1_2, and the second scheduling information may adopt DCI format 0_1/1_ 1.

Step 306: the second communication device retransmits the second data to the first communication device according to the second scheduling information.

For example, the second communication apparatus may retransmit the second data to the first communication apparatus on the time-frequency resources indicated by the second scheduling information. The second communication apparatus may retransmit the second data to the first communication apparatus at the time domain position and carrier indicated by the second scheduling information using the HARQ process, for example. The HARQ process and carrier used for retransmitting the second data are the same as the HARQ process and carrier used for the initial transmission.

Step 307: the first communication device monitors the second scheduling information.

Wherein the monitoring of the second scheduling information by the first communication device may include: and monitoring the second scheduling information by using the monitoring parameters corresponding to the second scheduling information in the search space corresponding to the second scheduling information in a first time period after the first data is received or sent according to the first scheduling information. The method for monitoring the second scheduling information by using the monitoring parameter corresponding to the second scheduling information in the search space corresponding to the second scheduling information of the first communication device is shown in fig. 4 and will not be described again.

The first data is data sent by the second communication device to the first communication device, and the starting time of the first time period is equal to or later than the time when the first communication device sends the NACK corresponding to the first data. The first time period may be controlled by a timer, which may be configured by the second communication device to the first communication device.

As described above, when the length of the second scheduling information is different from the length of the first scheduling information, the search space and the monitoring parameter corresponding to the second scheduling information are different from the search space and the monitoring parameter corresponding to the first scheduling information. As shown in fig. 5b, the first communication device is configured with a total of 3 different search spaces: the method includes the steps of searching a space 1, a space 2 and a space 3, wherein the space 1 and the space 2 are configured to correspond to first scheduling information, and the space 3 corresponds to second scheduling information. When the first data is initially transmitted, the first communication device monitors only the search space 1 and the search space 2. The first communication device monitors the second scheduling information in the search space 3 by "replacing" the search space 1 and the search space 2 with the search space 3 during a first period of time after receiving or transmitting the first data according to the first scheduling information.

When the length of the second scheduling information is the same as the length of the first scheduling information, the search space corresponding to the second scheduling information, the search space corresponding to the monitoring parameter corresponding to the first scheduling information, and the monitoring parameter may be the same, as shown in fig. 5a, the first communication device is configured with 3 different search spaces in total: the first communication device monitors the search spaces 1, 2, and 3 for a first time period after the first data is initially transmitted and the first data is subsequently transmitted.

Step 308: and when the second scheduling information is monitored, the first communication device receives the first data according to the second scheduling information.

For example, the first communications apparatus may receive the first data on the time-frequency resources indicated by the second scheduling information.

Further, if the retransmission of the first data fails, the second communication apparatus may transmit third scheduling information, schedule the retransmitted first data with the third scheduling information, and retransmit the first data again. The third scheduling information may not include a field carried by the scheduling information when the first data is initially transmitted or a field carried by the scheduling information when the first data is retransmitted last time, and at this time, the transmission parameter indicated in the initial transmission or the transmission parameter indicated in the retransmission may be used in the transmission of the first data retransmitted this time by default. For example, if the DCI does not include the BWP indicator at the time of the second retransmission, the BWP used for the second retransmission of the first data may be the same as the BWP used for the initial transmission of the first data, or may be the same as the BWP used for the first retransmission of the first data.

By applying the method shown in fig. 3, the field domain included in the scheduling information for scheduling the first-time transmission data is set to be different from the scheduling information for scheduling the retransmission data, and the first scheduling information and the second scheduling information do not need to be set to include the same field domain.

In the method shown in fig. 3, the second communication device newly transmits the first data to the first communication device according to the first scheduling information, and the second communication device retransmits the data to the first communication device according to the second scheduling information, that is, the data scheduling method provided in the embodiment of the present application is described by taking downlink data transmission as an example. Similarly, when uplink data is transmitted, a field included in the scheduling information for scheduling the uplink data for initial transmission may be set to be different from a field included in the scheduling information for scheduling the uplink data for retransmission, so as to reduce the number of bits included in the scheduling information when uplink data is transmitted and improve the transmission reliability and coverage of the scheduling information when uplink data is transmitted. Specifically, the following fig. 7 is referred to as a scheduling manner in uplink data transmission, where scheduling information for scheduling the initially transmitted uplink data in the method shown in fig. 7 may be referred to as first uplink scheduling information, and scheduling information for scheduling the retransmitted uplink data may be referred to as second uplink scheduling information.

Fig. 7 is a flowchart of another data scheduling method provided in an embodiment of the present application, and as shown in fig. 7, the method may include:

step 701: the second communication device sends the first uplink scheduling information to the first communication device.

The first uplink scheduling information may be used to schedule first data initially transmitted between the first communication device and the second communication device. In fig. 7, the first data may be referred to as uplink data, for example, the first uplink scheduling information may be used to schedule uplink data initially transmitted by the first communication device to the second communication device.

Similar to the first scheduling information described in step 301, the first uplink scheduling information described in step 701 may be the same as the protocol-specified uplink scheduling information, and include a field specified by the protocol, such as one or more field fields described in (1) to (31) above. Alternatively, the first uplink scheduling information may not include the first field. However, the first field when the first data is uplink data is slightly different from the first field when the first data is downlink data in step 301. For example, when the first data is uplink data, the first field may include one or more of the following field fields that can be deleted: UL-SCH indicator, FDRA, BWP indicator, antipna port, SRS resource indicator, RV, TDRA, TPC command, SRS triggering indication, CSI-RS triggering, precoding indication, beta _ offset indicator, frequency hopping indication, PTRS-DMRS association indication, DMRS sequence initiation, CBGTI.

Specifically, the description related to the first field may refer to the description in step 301, and is not repeated.

For example, the process of the second communication device sending the first uplink scheduling information to the first communication device may refer to the process of the second communication device sending the first scheduling information to the first communication device in step 301, which is not described in detail.

Step 702: the first communication device monitors first uplink scheduling information.

Specifically, step 702 can be referred to as step 303, and is not described in detail.

Step 703: when the first uplink scheduling information is monitored, the first communication device initially transmits first data to the second communication device according to the first uplink scheduling information.

For example, the first communications apparatus may initially transmit the first data to the second communications apparatus at a time-frequency resource location indicated by the first uplink scheduling information. The first communication apparatus may transmit the first data to the second communication apparatus at a time domain position and on a carrier indicated by the first uplink scheduling information using the HARQ process.

Step 704: the second communication device receives the first data.

For example, the second communications apparatus may receive the first data at a time-frequency resource location indicated by the first uplink scheduling information. If the second communication device receives and successfully analyzes the first data at the time-frequency resource position indicated by the first uplink scheduling information, the second communication device feeds back ACK corresponding to the first data to the first communication device, otherwise, if the second communication device does not successfully receive or does not receive the first data sent by the first communication device at the time-frequency resource position indicated by the first uplink scheduling information, the second communication device feeds back NACK corresponding to the first data to the first communication device. The method for determining whether the first data is successfully received by the second communication device may refer to the prior art and is not described in detail herein.

Further, if the first data is successfully transmitted, the process is ended, the transmission of the first data is ended, and the transmission of other data is performed. If the first data transmission fails, the following steps 705 to 708 are performed.

Step 705: and if the first data transmission fails, the second communication device sends second uplink scheduling information to the first communication device.

And after the second communication device sends the first uplink scheduling information, if the first data sent by the first communication device is not successfully received or not received in the time-frequency resource position indicated by the first uplink scheduling information, the first data is considered to be failed in transmission.

The second uplink scheduling information may be used to schedule the first data retransmitted between the first communication device and the second communication device. The field domain included in the first uplink scheduling information is different from the field domain included in the second uplink scheduling information. For example, in an example, the length of the second uplink scheduling information is different from the length of the first uplink scheduling information, for example, the length of the first uplink scheduling information is greater than the length of the second uplink scheduling information, the first uplink scheduling information includes a first field, and the second uplink scheduling information does not include the first field; or the length of the first uplink scheduling information is smaller than that of the second uplink scheduling information, the first uplink scheduling information does not include the first field domain, and the second uplink scheduling information includes the first field domain. The description of the first field is as described in fig. 3, and is not repeated.

In yet another example, the length of the second uplink scheduling information is the same as the length of the first uplink scheduling information. If the second uplink scheduling information includes the first field domain and does not include the second field domain, that is, the second field domain occupies 0bit in the second uplink scheduling information, and the first uplink scheduling information includes the second field domain and does not include the first field domain, that is, the first field occupies 0bit in the first uplink scheduling information. Specifically, a first field domain may be added to the first uplink scheduling information, and then the first uplink scheduling information to which the first field domain is added is truncated, for example, a second field domain in the first uplink scheduling information to which the first field domain is added is deleted, and the field domain included in the truncated first uplink scheduling information is carried in the second uplink scheduling information, so that the length of the second uplink scheduling information is the same as the length of the first uplink scheduling information, that is, the length of the uplink scheduling information at the time of initial transmission is aligned with the length of the uplink scheduling information at the time of retransmission. Specifically, the related description of the second field can refer to that shown in fig. 3, and the manner of deleting the second field can be described with reference to fig. 6.

For example, the uplink data is scheduled using DCI format 0_ 1. The first field is CBGTI, that is, CBGTI is not included in the first-transmitted DCI. If the number of the CBGs configured to the terminal by the network equipment is N, the bit length of the CBGTI is N bits. The field domain which can be deleted and included in the second field domain is UL-SCH indicator (1bit), BWP indicator (2bit), SRS resource indicator (3bit), RV indicator (2bit) and the like, namely the retransmission DCI can not include the field domains of UL-SCH indicator (1bit), BWP indicator (2bit), SRS resource indicator (3bit), RV indicator (2bit) and the like. In order to align the length of the retransmission DCI with the length of the initial transmission DCI, the length of the N-bit needs to be selected from UL-SCH indicator (1bit), BWP indicator (2bit), SRS resource indicator (3bit), and RV indicator (2bit) for puncturing. The ordering of these pruneable field fields is assumed to be: UL-SCH indicator (1bit) > BWP indicator (2bit) > SRS resource indicator (3bit) > RV indicator (2 bit). If the network device configures the terminal with CBGs in a number of N-4, that is, the bit length of the CBGTI is 4 bits, the following 3 fields may be deleted in the manner shown in fig. 6: UL-SCH indicator, BWP indicator, SRS resource indicator. At this time, during data retransmission, the values of the UL-SCH indicator, the BWP indicator, and the SRS resource indicator indicated in the initially transmitted DCI may still be used for retransmitted data. For example, if the initial transmission DCI indicates that the UL-SCH indicator is set to 1, the BWP indicator is set to 0, the BWP0 is indicated, and the SRS resource indicator is set to 0, the 0 th group of SRS is indicated, that is, the PUSCH of the initial transmission data includes the UL-SCH, the initial transmission data is transmitted on BWP0, and the PUSCH is transmitted using the antenna port corresponding to the 0 th group of SRS. In data retransmission, the PUSCH of the initial transmission data also includes the UL-SCH, and is also transmitted over BWP0, and the 0 th group SRS is also transmitted. If the number of CBGs configured by the network device to the terminal is N-2, that is, the bit length of the CBGTI is 2 bits, only the following 3 fields may be deleted in the manner shown in fig. 6: UL-SCH indicator, BWP indicator. Similarly, the values of the UL-SCH indicator and the BWP indicator indicated in the first-transmitted DCI are still used for retransmitted data, and are not explained here by way of example.

It should be noted that, when the length of the second field is greater than the length of the first field, after the second field is deleted, zero padding processing may be performed on the second uplink scheduling information, so that the lengths of the second uplink scheduling information and the first uplink scheduling information are aligned, thereby avoiding an excessive number of blind tests. For example, if the length of the first uplink scheduling information is 10 bits, and the length of the second uplink scheduling information after the second field domain is deleted is 9 bits, a zero may be added to the end of the second uplink scheduling information, so that the length of the second uplink scheduling information is also 10 bits. For another example, the first field is CBGTI, and the number of CBGs configured by the network device for the terminal is N-4, that is, the bit length of the CBGTI is 4 bits. The field fields included in the second field are a UL-SCH indicator (1bit), a BWP indicator (2bit), and a SRS resource indicator (3 bit). The second uplink scheduling information has more CBGTI, less UL-SCH indicator, BWP indicator, and SRS resource indicator, and less 2 bits as a whole, compared with the first uplink scheduling information. At this time, two zeros may be added to the end/tail of the second uplink scheduling information, so that the length of the second uplink scheduling information is aligned with the length of the first uplink scheduling information.

In addition to both the first communication device and the second communication device determining which second field fields to prune in the manner shown in figure 6 above, in the method shown in fig. 7, it can also be determined by the second communication device itself which field fields are to be deleted, which field fields are to be reserved, such as the way shown in fig. 6, and indicating the deleted field and/or the reserved field to the first communication device, for example, the second uplink scheduling information or the first uplink scheduling information may further include a third field and a fourth field, the third field may be indication information, the third field may be used to indicate a type of at least one fourth field, and the fourth field may include an unpunctured field in the second field, i.e. the reserved field, the sum of the number of bits of the third field, the number of bits of the fourth field and the number of bits of the first field may be equal to or smaller than the number of bits of the second field. When the sum of the number of bits of the third field, the number of bits of the fourth field, and the number of bits of the first field is smaller than the number of bits of the second field, two zeros may be added at the end/tail of the second uplink scheduling information, so that the length of the second uplink scheduling information is aligned with the length of the first uplink scheduling information.

For example, the uplink data is scheduled using DCI format 0_ 1. The first field is CBGTI, that is, CBGTI is not included in the first-transmitted DCI. If the number of the CBGs configured to the terminal by the network equipment is N, the bit length of the CBGTI is N bits. The field domain which can be deleted and reduced and included in the second field domain is UL-SCH indicator (1bit), BWP indicator (2bit), Antenna port (3bit), SRS resource indicator (3bit), RV indicator (2bit) and the like, namely UL-SCH indicator (1bit), BWP indicator (2bit), Antenna port (3bit), SRS resource indicator (3bit), RV indicator (2bit) and the like can not be included in the retransmission DCI, namely total 11 bits can be deleted and reduced. If the number of CBGs configured by the network device to the terminal is N-4, that is, the bit length of the CBGTI is 4 bits. Only 4 bits from the 11 bits need to be selected for puncturing and the remaining 7 bits are reserved. At this time, 2 bits of the remaining 7 bits may be used to indicate the contents of the remaining 5 bits. As shown in table four below. When the 2-bit indication information is 00, the remaining 5 bits include information of UL-SCH indicator (1bit) + BWP indicator (2bit) + RV indicator (2bit), and at this time, the contents of the antipna port (3bit) and SRS resource indicator (3bit) are the same as the contents of the initial transmission indication by default. By the method, the network equipment can more flexibly determine which information is indicated in the second uplink scheduling information, and the flexibility of the uplink scheduling information is improved.

Watch four

It should be noted that, in each embodiment of the present application, a format of the first uplink scheduling information is the same as a format of the second uplink scheduling information; or, the format of the first uplink scheduling information is different from the format of the second uplink scheduling information. For example, in this embodiment, the first uplink scheduling information may adopt DCI format 0_2/format 1_2, and the second uplink scheduling information may adopt DCI format 0_1/1_ 1.

Step 706: the first communication device monitors the second uplink scheduling information.

Step 706 can be described with reference to step 307, which is not described in detail. Unlike step 307, in fig. 7, the first data is data transmitted by the first communication apparatus to the second communication apparatus, and the start time of the first time period is equal to or later than the time when the first communication apparatus transmits the first data to the network device according to the first scheduling information.

Step 707: and when the second uplink scheduling information is monitored, the first communication device retransmits the second data to the second communication device according to the second uplink scheduling information.

For example, the first communication device may retransmit the second data to the second communication device on the time-frequency resource indicated by the second uplink scheduling information. The first communication apparatus may retransmit the first data to the second communication apparatus at a time domain position and on a carrier indicated by the first uplink scheduling information using the HARQ process. The HARQ process and carrier used for retransmitting the second data are the same as the HARQ process and carrier used for the initial transmission.

Step 708: the second communication device receives the retransmitted first data.

For example, the second communications apparatus may receive the retransmitted first data on the time-frequency resource indicated by the second uplink scheduling information.

Further, if the retransmission of the first data fails, the second communication device may transmit third uplink scheduling information, schedule the retransmitted first data with the third uplink scheduling information, and retransmit the first data again. The third uplink scheduling information may not include a field carried by the uplink scheduling information when the first data is initially transmitted or a field carried by the uplink scheduling information when the first data is retransmitted last time, and at this time, the transmission parameter indicated in the initial transmission or the transmission parameter indicated in the uplink retransmission may be used in the transmission of the first data retransmitted this time by default. For example, if the DCI does not include the BWP indicator at the time of the second retransmission, the BWP used for the second retransmission of the first data may be the same as the BWP used for the initial transmission of the first data, or may be the same as the BWP used for the first retransmission of the first data.

By applying the method shown in fig. 7, the field domain included in the uplink scheduling information for scheduling the first-pass data is set to be different from the uplink scheduling information for scheduling the retransmission data, and the first uplink scheduling information and the second uplink scheduling information do not need to be set to include the same field domain.

The data scheduling method described in the embodiment of the present application is described below with an example in which a first communication device is a terminal, the terminal is a mobile phone, a second communication device is a network device, the network device is a base station, and the base station sends a WeChat message to the mobile phone through an HARQ mechanism, where the WeChat message has 800 bits, and one CBG is 100 bits based on CBG transmission.

The base station determines to push the WeChat message to the mobile phone based on the CBG, and determines that time resources for sending the WeChat message are OFDM symbols 3 to 13 in the same time slot as the DCI, frequency resources are Physical Resource Blocks (PRBs), HARQ process 3 is used, the base station sends the DCI1 to the mobile phone, the DCI1 contains TDRA, FDRA and HPN field domains for indicating the above contents respectively, and sends PDSCH containing 8 CBGs to the mobile phone, and the PDSCH contains the content of the WeChat message.

The mobile phone monitors DCI1, and receives PDSCH containing WeChat message in time slot 0 and carrier 1 according to the indication of DCI1 by using HARQ process 3. If the mobile phone determines that the 7 th and 8 th CBGs are failed to be received, the ACK corresponding to the first 6 CBGs and the NACK corresponding to the 7 th and 8 th CBGs are fed back to the base station.

And the base station receives the NACK corresponding to the 7 th CBG and the NACK corresponding to the 8 th CBG fed back by the mobile phone, determines that the 7 th CBG and the 8 th CBG need to be retransmitted, sends DCI2 to the mobile phone, and sends a PDSCH carrying the 7 th CBG and the 8 th CBG to the mobile phone. At this time, the DCI2 must carry CBGTI, where the CBGTI is used to indicate that the PDSCH scheduled this time includes the 7 th CBG and the 8 th CBG, but does not include the remaining 6 CBGs, and in order to reduce the bit number of the DCI2, the DCI2 is set to include CBGTI, HPN, and TDRA, but does not include FDRA. In order to avoid too many times of blind detection of the mobile phone, the DCI1 and the DCI2 may be sent in different search spaces, and the mobile phone monitors different search spaces when monitoring the DCI1 and the DCI2, at this time, the lengths of the DCI1 and the DCI2 may be different; or the DCI1 and the DCI2 may be transmitted in the same search space, but the DCI1 and the DCI2 are guaranteed to be the same length in the manner previously described.

When the mobile phone monitors DCI2 and resolves that DCI2 carries CBGTI, HPN, and TDRA, the frequency resource used by the PDSCH including the 7 th CBG and the 8 th CBG is the same as that of the initial transmission by default, that is, all PRBs are used, and the PDSCH including the 7 th CBG and the 8 th CBG is received by using HARQ process 3.

The above-mentioned scheme provided by the embodiments of the present application is mainly introduced from the perspective of interaction between the nodes. It is to be understood that each node, for example, the first communication device, the second communication device, etc., contains a corresponding hardware structure and/or software module for performing each function in order to realize the above functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the first communication device, the second communication device, and the like may be divided into functional modules according to the above method examples, for example, each functional module may be divided according to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

Fig. 8 shows a block diagram of a communication device 80, where the communication device 80 may be a first communication device, or a chip in the first communication device, or a system on a chip, and the communication device 80 may be used to perform the functions of the first communication device involved in the above embodiments. As one implementation, the communication device 80 shown in fig. 8 includes: a processing unit 801, a transmitting/receiving unit 802;

in one example, the processing unit 801 monitors first scheduling information sent by the second communication device; for example, the processing unit 801 may enable the communication device 80 to perform step 303, step 702.

The transceiver 802 is configured to send or receive first data initially transmitted between the first communication device and the second communication device according to the first scheduling information when the processing unit 801 monitors the first scheduling information; for example, the transceiver unit 802 may support the communication device 80 to perform the steps 304, 703.

The processing unit 801 is further configured to monitor second scheduling information sent by the second communication device; for example, the processing unit 801 may enable the communication device 80 to perform step 307, step 706.

The transceiving unit 802 is further configured to, when the processing unit 801 monitors the first scheduling information, send or receive first data retransmitted between the first communication device and the second communication device according to the first scheduling information, where a field domain included in the first scheduling information is different from a field domain of the second scheduling information. For example, the transceiving unit 802 may support the communication device 80 to perform steps 308, 707.

Specifically, the relevant execution actions of the processing unit 801, the relevant descriptions of the first scheduling information and the second scheduling information may refer to the relevant descriptions in the method shown in fig. 3, and are not repeated.

Specifically, all relevant contents of each step related to the method embodiment shown in fig. 3 or fig. 7 may be referred to the functional description of the corresponding functional module, and are not described herein again. The communication device 80 is configured to perform the function of the first communication device in the data scheduling method shown in the method shown in fig. 3 or fig. 7, and thus the same effect as the data scheduling method described above can be achieved.

As still another implementation, the communication device 80 shown in fig. 8 includes: a processing module and a communication module. The processing module is used for controlling and managing the actions of the communication device 80, for example, the processing module may integrate the functions of the processing unit 801, and may be used for supporting the communication device 80 to perform the steps 303, 307, 702 and 706 and other processes of the technology described herein. The communication module may integrate the functions of the transceiver unit 802 and may be used to support the communication device 80 to perform the communication of steps 304, 308, 703, 707 with other network entities, for example, with the functional module or the network entity shown in fig. 1. The communication device 80 may also include a memory module for storing program codes and data for the communication device 80.

The processing module may be a processor or a controller. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module may be a transceiver circuit or a communication interface, etc. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 80 according to the embodiment of the present application may be the communication device shown in fig. 2.

Fig. 9 is a block diagram of a communication system according to an embodiment of the present application, and as shown in fig. 9, the communication system may include: a first communication device 90 and a second communication device 91. The function of the first communication device 90 is the same as that of the communication device 80 described above.

In one example, the second communication device 91 is configured to send first scheduling information to the first communication device 90, and initially transmit the first data to the first communication device 90 according to the first scheduling information;

a first communication device 90, configured to monitor the first scheduling information, and when the first scheduling information is monitored, receive first data according to the first scheduling information;

after the first data transmission fails, the second communication device 91 is further configured to send second scheduling information to the first communication device 90, and retransmit the first data to the first communication device 90 according to the second scheduling information.

The first communication device 90 is configured to monitor the second scheduling information, and receive the first data according to the second scheduling information when the second scheduling information is monitored.

The field domain included by the second scheduling information is different from the field domain included by the first scheduling information; the related descriptions of the first scheduling information and the second scheduling information may refer to the related descriptions and design manners in the method shown in fig. 3, and are not repeated.

In yet another example, the second communication device 91 is configured to send the first uplink scheduling information to the first communication device 90; the first communication device 90 is configured to monitor the first uplink scheduling information, and when the first uplink scheduling information is monitored, initially transmit first data to the second communication device according to the first uplink scheduling information;

after the first data transmission fails, the second communication device 91 is further configured to send second uplink scheduling information to the first communication device 90. The first communication device 90 is configured to monitor the second uplink scheduling information, and when the second uplink scheduling information is monitored, retransmit the first data to the second communication device according to the second uplink scheduling information.

The field domain included by the second uplink scheduling information is different from the field domain included by the first uplink scheduling information; the related descriptions of the first uplink scheduling information and the second uplink scheduling information may refer to the related descriptions and design manners in the method shown in fig. 7, which are not repeated.

The embodiment of the application also provides a computer readable storage medium. All or part of the processes in the above method embodiments may be performed by relevant hardware instructed by a computer program, which may be stored in the above computer-readable storage medium, and when executed, may include the processes in the above method embodiments. The computer readable storage medium may be a terminal of any of the foregoing embodiments, such as: including internal storage units of the data sending end and/or the data receiving end, such as a hard disk or a memory of the terminal. The computer readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, which are provided on the terminal. Further, the computer-readable storage medium may include both an internal storage unit and an external storage device of the terminal. The computer-readable storage medium stores the computer program and other programs and data required by the terminal. The above-described computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

In combination with the above, the present application also provides the following embodiments:

embodiment 1, a data scheduling method, wherein the method is applied to a first communication device, and the method includes:

monitoring first scheduling information sent by a second communication device;

when the first scheduling information is monitored, first data primarily transmitted between the first communication device and the second communication device is received or transmitted according to the first scheduling information;

monitoring second scheduling information sent by a second communication device;

and when monitoring second scheduling information, receiving or sending first data retransmitted between the first communication device and the second communication device according to the second scheduling information, wherein a field domain included in the second scheduling information is different from a field domain included in the first scheduling information.

Embodiment 2, a data scheduling method, wherein the data scheduling method includes:

the second communication device sends first scheduling information to the first communication device;

the second communication device initially transmits first data to the first communication device according to the first scheduling information;

after the first data transmission fails, the second communication device sends second scheduling information to the first communication device, wherein the field domain included in the second scheduling information is different from the field domain included in the first scheduling information;

the second communication device retransmits the first data to the first communication device according to the second scheduling information.

Embodiment 3 the method of embodiment 1 or embodiment 2, wherein,

the length of the second scheduling information is different from the length of the first scheduling information;

the second scheduling information includes a first field, and the first scheduling information does not include the first field; alternatively, the first and second electrodes may be,

the first scheduling information includes a first field and the second scheduling information does not include the first field.

Embodiment 4 the method of any one of embodiments 1 to 3, wherein the search space corresponding to the first scheduling information is different from the search space corresponding to the second scheduling information.

Embodiment 5 is the method according to any one of embodiment 1 to embodiment 4, wherein the monitoring parameter corresponding to the first scheduling information is different from the monitoring parameter corresponding to the second scheduling information, and the monitoring parameters include: one or more information of the configuration of a search space, the configuration of a control resource set (CORESET), and a Radio Network Temporary Identifier (RNTI);

the configuration of the search space includes one or more of a monitoring period of the search space, a DCI format of downlink control information to be monitored, a number of candidate sets candidate to be monitored, and an aggregation level to be monitored.

Embodiment 6, the method according to embodiment 4 or embodiment 5, wherein monitoring the second scheduling information transmitted by the second communication device includes: and monitoring the second scheduling information by using the monitoring parameters corresponding to the second scheduling information in the search space corresponding to the second scheduling information in a first time period after the first data is received or sent according to the first scheduling information.

Embodiment 7 the method of embodiment 6, wherein,

the first data is data sent by the second communication device to the first communication device, the starting time of the first time period is equal to or later than the time when the first communication device sends a negative acknowledgement, and the negative acknowledgement is used for indicating that the first data transmission fails;

the first data is data sent by the first communication device to the second communication device, and the starting time of the first time period is equal to or later than the time when the first communication device sends the first data to the second communication device according to the first scheduling information.

Embodiment 8 the method of embodiment 1 or embodiment 2, wherein,

the length of the first scheduling information is the same as the length of the second scheduling information.

Embodiment 9 the method of embodiment 8, wherein,

the second scheduling information includes a first field and does not include a second field;

the first scheduling information comprises a second field and does not comprise a first field;

wherein the first field domain is different from the second field domain.

Embodiment 10 the method of embodiment 9, wherein the second field comprises i field fields;

the total length of the first (i-1) field fields in the i field fields is less than the length of the first field, and the total length of the i field fields is greater than or equal to the length of the first field.

Embodiment 11, the method according to embodiment 9 or 10, wherein the first scheduling information and the second scheduling information include a hybrid automatic repeat request process number, HPN, and a new data indication, NDI, or the first scheduling information and the second scheduling information include carrier indicator fields, CIF, HPN, and NDI;

the position and the length of the HPN in the first scheduling information are the same as those of the HPN in the second scheduling information, the position and the length of the NDI in the first scheduling information are the same as those of the NDI in the second scheduling information, and the position and the length of the CIF in the first scheduling information are the same as those of the CIF in the second scheduling information.

Embodiment 12 the method of any one of embodiments 9-11, wherein,

the first scheduling information or the second scheduling information includes a third field and a fourth field, and the third field indicates a type of at least one fourth field.

Embodiment 13, the method according to any one of embodiments 9 to 12, wherein the first data is uplink data, and the first field or the second field includes one or more of the following:

UL-SCH indicator, FDRA, BWP indicator, antipna port, SRS resource indicator, RV, TDRA, TPC command, SRS triggering indication, CSI-RS triggering, precoding indication, beta _ offset indicator, frequency hopping indication, PTRS-DMRS association indication, DMRS sequence initiation, CBGTI.

Embodiment 14 or the method according to any one of embodiments 9 to 12, wherein the first data is downlink data, and the first field or the second field includes one or more of the following:

FDRA, BWP indicator, antiport, SRS resource indicator, TCI, VRB-to-PRB mapping, PRB bundling size indicator, rate matching indicator, RV, TDRA, TPC command, SRS trigger indication, CSI-RS trigger indication, DMRS sequence initiation, CBGTI, CBGFI.

Embodiment 15, a communication device, wherein the communication device comprises a processing unit, a transceiver unit;

the receiving and sending unit is used for receiving or sending first data primarily transmitted between the first communication device and the second communication device according to the first scheduling information when the processing unit monitors the first scheduling information;

and the transceiver unit is further configured to receive or transmit the first data retransmitted between the first communication device and the second communication device according to the second scheduling information when the processing unit monitors the second scheduling information, where a field domain included in the second scheduling information is different from a field domain included in the first scheduling information.

Embodiment 16, a communication device, wherein the communication device comprises: a processing unit and a transmitting-receiving unit;

the receiving and sending unit is used for sending first scheduling information to the first communication device and primarily transmitting first data to the first communication device according to the first scheduling information;

the receiving and sending unit is also used for sending second scheduling information to the first communication device after the first data transmission fails, and retransmitting the first data to the first communication device according to the second scheduling information; the second scheduling information includes a field different from a field included in the first scheduling information.

Embodiment 17 the communication device according to embodiment 15 or embodiment 16, wherein,

Embodiment 18, the communication apparatus according to any one of embodiments 15 to 17, wherein a search space corresponding to the first scheduling information is different from a search space corresponding to the second scheduling information.

Embodiment 19, the communication apparatus according to any one of embodiments 15 to 18, wherein the monitoring parameter corresponding to the first scheduling information is different from the monitoring parameter corresponding to the second scheduling information, and the monitoring parameters include: one or more information of the configuration of a search space, the configuration of a control resource set (CORESET), and a Radio Network Temporary Identifier (RNTI);

Embodiment 20, the communication apparatus according to embodiment 18 or embodiment 19, wherein the processing unit is specifically configured to monitor the second scheduling information by using a monitoring parameter corresponding to the second scheduling information in a search space corresponding to the second scheduling information in a first time period after the first data is received or transmitted according to the first scheduling information.

Embodiment 21 the communication device according to embodiment 20, wherein,

Embodiment 22, the communication device according to embodiment 15 or embodiment 16, wherein,

Embodiment 23 the communication device according to embodiment 20, wherein,

wherein the first field domain is different from the second field domain.

Embodiment 24 the communication device of embodiment 23, wherein the second field comprises i field fields;

Embodiment 25, the communication apparatus according to embodiment 23 or 24, wherein the first scheduling information and the second scheduling information include a hybrid automatic repeat request process number, HPN, and a new data indication, NDI, or the first scheduling information and the second scheduling information include carrier indication fields, CIF, HPN, and NDI;

Embodiment 26 the communication device of any one of embodiments 23-25, wherein,

Embodiment 27, the communication device according to any one of embodiments 23 to 26, wherein the first data is uplink data, and the first field or the second field includes one or more of the following:

Embodiment 28, the communication apparatus according to any one of embodiments 23 to 26, wherein the first data is downlink data, and the first field or the second field includes one or more of the following:

Embodiment 29, a communication system, wherein the communication system comprises:

a second communication device for transmitting the first scheduling information to the first communication device;

the first communication device is used for monitoring first scheduling information, and when the first scheduling information is monitored, first data which is initially transmitted between the first communication device and the second communication device is sent or received according to the first scheduling information;

the second communication device is also used for sending second scheduling information to the first communication device after the first data transmission fails; the field domain included by the second scheduling information is different from the field domain included by the first scheduling information;

and the first communication device is used for monitoring the second scheduling information, and when the second scheduling information is monitored, the first communication device sends or receives the first data retransmitted between the first communication device and the second communication device according to the second scheduling information.

Embodiment 30, a communication apparatus, comprising: a processor and a memory; the memory is to store program instructions; the processor is configured to call the program instructions in the memory to execute the data scheduling method according to any one of embodiments 1 to 14.

The communication apparatus according to embodiment 31 or 30 is a terminal or a chip applicable to a terminal, or the communication apparatus is a network device or a chip applicable to a network device.

Embodiment 32, a communication device, comprising one or more means to perform the data scheduling method according to any of embodiments 1 to 14.

Embodiment 33 is a computer readable storage medium, wherein the computer readable storage medium comprises computer instructions which, when executed on a computer, cause the computer to perform the data scheduling method of any of embodiments 1-14.

Embodiment 34, a computer program product, wherein the computer program product comprises computer instructions which, when run on a computer, cause the computer to perform the data scheduling method of any of embodiments 1-14.

It should be noted that the terms "first" and "second" and the like in the description, claims and drawings of the present application are used for distinguishing different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and three or more, "and/or" for describing an association relationship of associated objects, meaning that three relationships may exist, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.

It should be understood that in the embodiment of the present application, "B corresponding to a" means that B is associated with a. For example, B may be determined from A. It should also be understood that determining B from a does not mean determining B from a alone, but may also be determined from a and/or other information. In addition, the term "connect" in the embodiment of the present application refers to various connection manners, such as direct connection or indirect connection, to implement communication between devices, and this is not limited in this embodiment of the present application.

The "transmission" appearing in the embodiments of the present application refers to a bidirectional transmission, including actions of transmission and/or reception, unless otherwise specified. Specifically, "transmission" in the embodiment of the present application includes transmission of data, reception of data, or both transmission of data and reception of data. Alternatively, the data transmission herein includes uplink and/or downlink data transmission. The data may include channels and/or signals, uplink data transmission, i.e., uplink channel and/or uplink signal transmission, and downlink data transmission, i.e., downlink channel and/or downlink signal transmission. In the embodiments of the present application, "network" and "system" represent the same concept, and a communication system is a communication network.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be substantially or partially implemented in the form of software products, which are stored in a storage medium and include instructions for causing a device, such as: the method can be a single chip, a chip, or a processor (processor) for executing all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Claims

1. A data scheduling method applied to a first communication device, the method comprising:

monitoring first scheduling information sent by a second communication device;

when the first scheduling information is monitored, first data primarily transmitted between the first communication device and the second communication device is sent or received according to the first scheduling information;

monitoring second scheduling information sent by the second communication device;

when the second scheduling information is monitored, the first data retransmitted between the first communication device and the second communication device is sent or received according to the second scheduling information, and a field domain included in the second scheduling information is different from a field domain included in the first scheduling information.

2. A data scheduling method, characterized in that the data scheduling method comprises:

after the first data transmission fails, the second communication device sends second scheduling information to the first communication device, wherein a field domain included in the second scheduling information is different from a field domain included in the first scheduling information;

3. The method according to claim 1 or 2,

the first scheduling information includes the first field and the second scheduling information does not include the first field.

4. The method according to any of claims 1-3, wherein the search space corresponding to the first scheduling information is different from the search space corresponding to the second scheduling information.

5. The method according to any of claims 1-4, wherein the monitoring parameters corresponding to the first scheduling information are different from the monitoring parameters corresponding to the second scheduling information, and the monitoring parameters include: one or more information of the configuration of a search space, the configuration of a control resource set (CORESET), and a Radio Network Temporary Identifier (RNTI);

the configuration of the search space includes one or more information of a monitoring period of the search space, a DCI format of downlink control information to be monitored, a number of candidate sets candidate to be monitored, and an aggregation level to be monitored.

6. The method of claim 4 or 5, wherein the monitoring the second scheduling information transmitted by the second communication device comprises: and monitoring the second scheduling information by using monitoring parameters corresponding to the second scheduling information in a search space corresponding to the second scheduling information in a first time period after the first data is received or sent according to the first scheduling information.

7. The method of claim 6,

8. The method according to claim 1 or 2,

9. The method of claim 8,

the second scheduling information comprises a first field and does not comprise a second field;

the first scheduling information includes the second field and does not include the first field;

wherein the first field domain is different from the second field domain.

10. The method of claim 9, wherein the second field comprises i field fields;

a total length of first (i-1) field fields of the i field fields is less than a length of the first field, and the total length of the i field fields is greater than or equal to the length of the first field.

11. The method according to claim 9 or 10, wherein the first and second scheduling information comprise hybrid automatic repeat request process number, HPN, and new data indication, NDI, or wherein the first and second scheduling information comprise carrier indication fields, CIF, HPN, and NDI;

12. The method according to any one of claims 9 to 11,

13. The method of any of claims 9-12, wherein the first data is uplink data, and wherein the first field or the second field comprises one or more of:

the method comprises the steps of an uplink shared channel indication UL-SCH indicator, a frequency domain resource allocation FDRA, a bandwidth part indication BWP indicator, an antenna port, a sounding reference signal resource indication SRS resource indicator, a redundancy version RV, a time domain resource allocation TDRA, a transmission power control TPC command, an SRS triggering trigger indication, a channel state information reference signal trigger indication CSI-RS triggering, a precoding indication, a beta offset indication beta _ offset indicator, a frequency hopping response indication, a phase tracking reference signal-demodulation reference signal PTRS-DMRS association indication, a demodulation reference signal initial sequence DMRS sequence initial association and a code block group transmission indication CBGTI.

14. The method according to any of claims 9-12, wherein the first data is downlink data, and the first field or the second field comprises one or more of the following:

frequency domain resource allocation FDRA, BWP indicator, antipna port, SRS resource indicator, transmission configuration indication TCI, mapping relation VRB-to-PRB mapping from virtual resource blocks to physical resource blocks, physical resource block bundling size indication PRB bundling size indicator, rate matching indication rate matching indicator, redundancy version RV, time domain resource allocation TDRA, TPC command, SRS triggering indication, CSI-RS triggering indication, DMRS sequence initiation, CBGTI and code block group clearing indication CBGFI.

15. A communication system, characterized in that the communication system comprises a first communication device and a second communication device;

the second communication device is used for sending first scheduling information to the first communication device;

the first communication device is configured to monitor the first scheduling information, and when the first scheduling information is monitored, send or receive first data initially transmitted between the first communication device and the second communication device according to the first scheduling information;

the second communication device is further configured to send second scheduling information to the first communication device after the first data transmission fails; the field domain included in the second scheduling information is different from the field domain included in the first scheduling information;

the first communication device is configured to monitor the second scheduling information, and when the second scheduling information is monitored, send or receive the first data retransmitted between the first communication device and the second communication device according to the second scheduling information.

16. A communication apparatus, comprising one or more processors, a communication interface, the one or more processors and the communication interface to enable the communication apparatus to perform the data scheduling method of any one of claims 1-14.

17. A computer-readable storage medium, comprising computer instructions which, when executed on a computer, cause the computer to perform the data scheduling method of any one of claims 1-14.

18. A computer program product, characterized in that it comprises computer instructions which, when run on a computer, cause the computer to perform the data scheduling method according to any one of claims 1-14.