WO2022082371A1 - Communication method, apparatus, system, and chip - Google Patents

Abstract

The present application relates to the field of communication technology and discloses a communication method, an apparatus, a system, and a chip, which are used to solve the problem in current technology of large power consumption of a scheduled device during data transmission. The method comprises: a first device receives a first message from a second device, the first message comprising scheduling information, and being used for scheduling shared channels, wherein the size of a frequency domain resource of the shared channels is equal to the size of a bandwidth part BWP where the shared channels are located; and the first device communicates with the second device on the basis of the shared channels.

Description

A communication method, device, system and chip technical field

The present application relates to the field of wireless communication technologies, and in particular, to a communication method, device, system and chip.

Background technique

In an existing communication system, when two devices communicate with each other, one device usually schedules time-frequency resources, and sends the scheduling information to another device, and the two devices communicate according to the scheduled time-frequency resources. For example, the terminal device communicates with the network device according to the time-frequency resources scheduled by the network device.

However, when communicating between existing devices, only the shared channel mapped in one time slot is scheduled at a time, and the frequency domain resources of the shared channel are only a part of the activated bandwidth part (BWP). There are fewer frequency resources, resulting in less data that can be carried by the scheduled time-frequency resources. This requires the device receiving the scheduling information to continuously monitor the physical downlink control channel (PDCCH) to obtain the scheduling information, and to continuously open a larger part of the active bandwidth for data transmission, which increases the power consumption of the device.

SUMMARY OF THE INVENTION

The present application provides a communication method, device, system and chip, which are used to solve the problem of high power consumption of scheduled equipment during data transmission in the prior art.

In a first aspect, the present application provides a communication method, the method comprising: a first device receiving a first message from a second device, the first message including scheduling information for scheduling K shared channels, wherein the K shared channels are mapped to K time slots for carrying S different transport blocks TB, where K is a positive integer greater than or equal to 2, and S is a positive integer greater than or equal to the K; the first A device communicates with the second device based on the K shared channels. Optionally, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

By using the above method, the second device can perform time-domain full scheduling on the first device, that is, one first message can schedule multiple shared channels, which reduces the monitoring time and monitoring times of the PDCCH by the first device, and saves the first device's power consumption.

In a possible design, the scheduling information includes time-domain resource indication information; wherein the time-domain resource indication information is used to indicate K consecutive time slots in the time domain that can be used for mapping the shared channel; or, The time domain resource indication information is used to indicate consecutive M time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and M is greater than or equal to the positive integer of K. Wherein, if the shared channel is a physical downlink shared channel PDSCH, the time slot that can be used to map the shared channel is a downlink time slot; if the shared channel is a physical uplink shared channel PUSCH, the time slot that can be used to map the shared channel The time slot of the shared channel is an uplink time slot; if the shared channel is a physical sideway channel PSSCH, the time slot that can be used for mapping the shared channel is a sideway time slot.

The above design enriches the implementation manner of the second device performing time-domain full scheduling on the first device, which facilitates selecting a corresponding time-domain full scheduling implementation manner according to different communication requirements, which is beneficial to ensure the reliability of communication.

In a possible design, the method further includes: the first device determines, by the first device, a time slot that includes a number of downlink symbols greater than or equal to a first number threshold as a downlink time slot; and/or, the first device includes an uplink time slot The time slot with the number of symbols greater than or equal to the second number threshold is determined as the uplink time slot; and/or, the first device determines the time slot including the number of sideline symbols greater than or equal to the third number threshold as the sideline time slot.

In the above design, for a dedicated time slot (or special time slot) containing more than one symbol type, when the number of corresponding symbols in the time slot is greater than the corresponding number threshold, the time slot can be determined as an uplink time slot or a downlink time slot. Slot or sideline time slot for mapping PDSCH or PUSCH or PSSCH, and a time slot can be both an uplink time slot for mapping PUSCH and a downlink time slot for mapping PDSCH, or it can be both an uplink time slot and a downlink time slot. It is used for mapping PUSCH and PDSCH, which avoids the waste of time domain resources caused by a single time slot type, and is beneficial to improve the utilization rate of time domain resources, thereby improving the data transmission efficiency and reducing the power consumption of the first device.

In a possible design, the first message further includes hybrid automatic repeat request HARQ process indication information, where the HARQ process indication information is used to indicate one HARQ process corresponding to the K shared channels, or used to indicate K HARQ processes corresponding to the K shared channels one-to-one. Optionally, the HARQ process indication information includes a HARQ process number; the HARQ process number is used to indicate a HARQ process corresponding to the K shared channels; or the HARQ process number is used to indicate that the HARQ process The K consecutive HARQ processes starting with the HARQ process corresponding to the process number are in one-to-one correspondence with the K shared channels; or, the HARQ process number is used to indicate the HARQ process starting with the HARQ process corresponding to the HARQ process number. The K idle HARQ processes are in one-to-one correspondence with the K shared channels.

In the above design, the HARQ process indication information can be used to indicate a HARQ process corresponding to the K shared channels to save HARQ signaling transmission redundancy; the HARQ process indication information can also be used to indicate K corresponding to the K shared channels one-to-one. For the HARQ process, a corresponding HARQ process can be designed for each shared channel, so as to avoid the TB retransmission of K shared channels caused by TB errors in one shared channel, which will reduce the transmission efficiency, thereby improving the transmission efficiency.

In a possible design, the first device releases the K HARQ processes after all the S TBs carried by the K shared channels are successfully transmitted; or, when the first device determines that the K HARQ processes are After the transmission of the TB carried by any one of the shared channels is successful, the first device releases the HARQ process corresponding to the shared channel that is successfully transmitted.

In the above design, different implementation manners for releasing the K HARQ processes corresponding to the K shared channels in the case of full scheduling in the time domain are provided, which is beneficial to meet different communication requirements.

In a possible design, the demodulation reference signal DMRSs in the K shared channels use the same mapping rule; or, the DMRSs in the K shared channels use different mapping rules according to the mapping rule determination method.

In the above design, the demodulation reference signal DMRS of the K shared channels adopts the same mapping rule, which is beneficial to simplify the channel estimation algorithm; Conducive to saving DMRS transmission redundancy.

In a possible design, the K shared channels are indicated by the same set of demodulation reference signal DMRS configuration parameters.

In the above design, the K shared channels are indicated by the same set of demodulation reference signal DMRS configuration parameters, which can avoid signaling redundancy caused by multiple sets of demodulation reference signal DMRS configuration parameters.

In a possible design, the K shared channels are indicated by the same set of demodulation reference signal DMRS configuration parameters, and the DMRSs in the K shared channels use different mapping rules according to the mapping rules. The set of demodulation reference signal configuration parameters is used to indicate the DMRS configuration of one shared channel among the K shared channels, and the DMRS configurations of the remaining K-1 shared channels are obtained according to the DMRS configuration of the one shared channel according to certain rules .

In the above design, signaling redundancy caused by multiple sets of demodulation reference signal DMRS configuration parameters is avoided, and DMRS transmission redundancy is also saved.

In a possible design, the K shared channels use the same or different modulation and coding modes MCS.

In the above design, the K shared channels use the same MCS, which is beneficial to simplify the demodulation receiving algorithm; the K shared channels use different MCSs, which is beneficial to improve the transmission efficiency.

In a possible design, the K shared channels use the same MCS parameter to indicate their modulation and coding modes.

In the above design, the K shared channels use the same set of MCS parameters to indicate their modulation and coding modes, which can avoid signaling transmission redundancy caused by multiple sets of MCS parameters.

In a possible design, the K shared channels use the same MCS parameter to indicate their modulation and coding modes, the K shared channels use different modulation and coding modes MCS, and the one MCS parameter is used to indicate the K The MCS of one shared channel among the shared channels, and the MCS of the remaining (K-1) shared channels can be obtained according to a certain rule according to the MCS of the one shared channel.

In the above design, not only the redundancy of signaling transmission caused by multiple sets of MCS parameters is avoided, but also different MCSs can be used for the K shared channels, which improves the transmission efficiency.

In a possible design, the scheduling information includes frequency domain resource indication information, where the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels, wherein the frequency domain resources of the K shared channels The size of is less than or equal to the size of the bandwidth part BWP where the K shared channels are located.

In the above design, when time-domain full scheduling is used, the second device may further use frequency-domain full scheduling, and the frequency-domain full scheduling is that the size of the frequency domain resources of the shared channel scheduled by the scheduling information is equal to the size of the frequency domain resource where the shared channel is located. The size of the BWP further improves the data transmission efficiency and reduces the power consumption of the first device.

In a possible design, the method further includes: the first device sending capability information to the second device, where the capability information includes information that the first device supports full time-domain scheduling, or the The capability information includes information that the first device supports full scheduling in the time domain and information that the first device supports full scheduling in the frequency domain, wherein the full scheduling in the time domain is scheduling information to schedule multiple shared channels, and the frequency domain The size of the frequency domain resource of the shared channel scheduled for full scheduling is equal to the size of the BWP where the shared channel is located.

In the above design, it is beneficial for the second device to know the capability of the first device, and to fully schedule the first device according to the capability of the first device.

In a possible design, the method further includes: the first device sending a full scheduling request message to the second device, where the full scheduling request message includes a time domain full scheduling request, or the full scheduling request The message includes a request for full scheduling in the time domain and a request for full scheduling in the frequency domain. Optionally, before the first device sends the full scheduling request message to the second device, the method further includes: the first device determines that power saving is required; and/or the first device determines that the amount of data to be transmitted is greater than is equal to a data volume threshold; and/or the first device determines that the current bandwidth is less than a bandwidth threshold; and/or the first device determines that the second device is in a low load state.

In the above design, the first device may initiate a full scheduling request to the second device according to the state of itself or the second device, so as to improve data transmission efficiency and reduce its own power consumption.

In a possible design, the method further includes: before the first device sends a full scheduling request message to the second device, further comprising: receiving, by the first device, full scheduling indication information from the second device , the full scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

In the above design, the second device can also indicate the first device according to its own communication situation and/or the situation of the first device, such as its own load situation, the power situation of the first device, whether the first device is in an overheated state, etc. Whether to initiate a full scheduling request, so as to prevent the first device from sending a full scheduling request without permission, which is beneficial to ensure the validity and reliability of the communication between the second device and the first device.

In a second aspect, the present application provides a communication method, the method comprising: a first device receiving a first message from a second device, the first message including scheduling information for scheduling a shared channel, wherein the shared channel The size of the frequency domain resource is equal to the size of the bandwidth part BWP where the shared channel is located; the first device communicates with the second device based on the shared channel. Optionally, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

Using the above method, the second device can perform full frequency domain scheduling on the first device, that is, the size of the frequency domain resources of the scheduled shared channel is equal to the size of the BWP of the bandwidth part where the shared channel is located, and more data can be transmitted in one scheduling , thereby reducing the monitoring time and the number of times of monitoring the PDCCH by the first device, reducing the time for the first device to open the transceiver channel, and saving the power consumption of the first device.

In a possible design, the first message uses a BWP number to indicate the size of the frequency domain resource of the shared channel. At this time, the first message may not include the frequency domain resource assignment field (Frequency domain resource assignment field), or the frequency domain resource indication field originally used to carry the bits of the frequency domain resource indication information may be reinterpreted to have other meanings information.

In the above design, the size of the frequency domain resources of the shared channel can be directly indicated by the BWP number, which further reduces the signaling used to transmit the frequency domain resource indication information, saves the transmission redundancy of the control signaling, and can improve the control signaling. Transmission reliability.

In a possible design, the method further includes: the first device sends capability information to the second device, where the capability information includes information that the first device supports full frequency-domain scheduling, wherein the The frequency domain full scheduling is that the size of the frequency domain resource of the shared channel scheduled by the scheduling information is equal to the size of the BWP where the shared channel is located.

In the above design, it is beneficial for the second device to know the capability of the first device, and to fully schedule the first device according to the capability of the first device.

In a possible design, the method further includes: the first device sends a full scheduling request message to the second device, where the full scheduling request message includes a request for full scheduling in the frequency domain. Optionally, before the first device sends the full scheduling request message to the second device, the method further includes: the first device determines that power saving is required; and/or the first device determines that the amount of data to be transmitted is greater than is equal to a data volume threshold; and/or the first device determines that the current bandwidth is less than a bandwidth threshold; and/or the first device determines that the second device is in a low load state.

In the above design, the first device may initiate a full scheduling request to the second device according to the state of itself or the second device, so as to improve data transmission efficiency and reduce its own power consumption.

In a possible design, the method further includes: before the first device sends a full scheduling request message to the second device, further comprising: receiving, by the first device, full scheduling indication information from the second device , the full scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

In the above design, the second device can also indicate the first device according to its own communication situation and/or the situation of the first device, such as its own load situation, the power situation of the first device, whether the first device is in an overheated state, etc. Whether to initiate a full scheduling request, so as to prevent the first device from sending a full scheduling request without permission, which is beneficial to ensure the validity and reliability of the communication between the second device and the first device.

In a third aspect, the present application provides a communication method, the method comprising: a second device sending a first message to a first device, where the first message includes scheduling information for scheduling K shared channels, wherein the K The shared channel is mapped to K time slots for carrying S different transport blocks TB, the K is a positive integer greater than or equal to 2, and the S is a positive integer greater than or equal to the K; the second device is based on The K shared channels communicate with the first device. Optionally, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

In a possible design, the scheduling information includes time-domain resource indication information; wherein the time-domain resource indication information is used to indicate K consecutive time slots in the time domain that can be used for mapping the shared channel; or, The time domain resource indication information is used to indicate consecutive M time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and M is greater than or equal to the positive integer of K. Wherein, if the shared channel is a physical downlink shared channel PDSCH, the time slot that can be used to map the shared channel is a downlink time slot; if the shared channel is a physical uplink shared channel PUSCH, the time slot that can be used to map the shared channel The time slot of the shared channel is an uplink time slot; if the shared channel is a physical sideway channel PSSCH, the time slot that can be used for mapping the shared channel is a sideway time slot.

In a possible design, the method further includes: the second device determines, by the second device, a time slot including a number of downlink symbols greater than or equal to a first number threshold as a downlink time slot; and/or, the second device includes an uplink time slot and/or, the second device determines a time slot including a number of sideline symbols greater than or equal to a third number threshold as a sideline time slot.

In a possible design, the first message further includes hybrid automatic repeat request HARQ process indication information, where the HARQ process indication information is used to indicate one HARQ process corresponding to the K shared channels, or used to indicate K HARQ processes corresponding to the K shared channels one-to-one. Optionally, the HARQ process indication information includes a HARQ process number; the HARQ process number is used to indicate a HARQ process corresponding to the K shared channels; or the HARQ process number is used to indicate that the HARQ process The K consecutive HARQ processes starting with the HARQ process corresponding to the process number are in one-to-one correspondence with the K shared channels; or, the HARQ process number is used to indicate the HARQ process starting with the HARQ process corresponding to the HARQ process number. The K idle HARQ processes are in one-to-one correspondence with the K shared channels.

In a possible design, the method further includes: the second device releases the K HARQ processes after all the S TBs carried by the K shared channels are successfully transmitted; or, when the second After the device determines that the transmission of the TB carried by any one of the K shared channels is successful, the second device releases the HARQ process corresponding to the shared channel that is successfully transmitted.

In a possible design, the demodulation reference signal DMRSs in the K shared channels use the same mapping rule; or, the DMRSs in the K shared channels use different mapping rules according to the mapping rule determination method.

In a possible design, the K shared channels are indicated by the same set of demodulation reference signal DMRS configuration parameters.

In a possible design, the K shared channels are indicated by the same set of demodulation reference signal DMRS configuration parameters, and the DMRSs in the K shared channels use different mapping rules according to the mapping rules. The set of demodulation reference signal configuration parameters is used to indicate the DMRS configuration of one shared channel among the K shared channels, and the DMRS configurations of the remaining K-1 shared channels are obtained according to the DMRS configuration of the one shared channel according to certain rules .

In a possible design, the K shared channels use the same or different modulation and coding modes MCS.

In a possible design, the K shared channels use the same MCS parameter to indicate their modulation and coding modes.

In a possible design, the K shared channels use the same MCS parameter to indicate their modulation and coding modes, the K shared channels use different modulation and coding modes MCS, and the one MCS parameter is used to indicate the K The MCS of one shared channel among the shared channels, and the MCS of the remaining (K-1) shared channels may be obtained according to a certain rule according to the MCS of the one shared channel.

In a possible design, the scheduling information includes frequency domain resource indication information, where the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels, wherein the frequency domain resources of the K shared channels The size of is less than or equal to the size of the bandwidth part BWP where the K shared channels are located.

In a possible design, the method further includes: receiving, by the second device, capability information from the first device, where the capability information includes information that the first device supports full time-domain scheduling, or The capability information includes information that the first device supports full scheduling in the time domain and information that the first device supports full scheduling in the frequency domain, wherein the full scheduling in the time domain is scheduling information to schedule multiple shared channels, and the frequency In domain full scheduling, the size of the frequency domain resource of the shared channel scheduled by the scheduling information is equal to the size of the BWP where the shared channel is located.

In a possible design, the method further includes: receiving, by the second device, a full scheduling request message sent by the first device, where the full scheduling request message includes a time domain full scheduling request, or the full scheduling request The request message includes a request for full scheduling in the time domain and a request for full scheduling in the frequency domain.

In a possible design, before the second device receives the full scheduling request message sent by the first device, the method further includes: the second device sends full scheduling indication information to the first device, and the full scheduling request message is sent by the second device to the first device. The scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

In a fourth aspect, the present application provides a communication method, the method comprising: a second device sending a first message to a first device, the first message including scheduling information for scheduling a shared channel, wherein the shared channel is The size of the frequency domain resource is equal to the size of the bandwidth part BWP where the shared channel is located; the second device communicates with the first device based on the shared channel. Optionally, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

In a possible design, the first message uses a BWP number to indicate the size of the frequency domain resource of the shared channel. At this time, the first message may not include the frequency domain resource indication field, or the content carried in the frequency domain resource indication field may be reinterpreted as a message with other meanings.

In a possible design, the method further includes: receiving, by the second device, capability information from the first device, where the capability information includes information that the first device supports full frequency-domain scheduling, wherein, The frequency domain full scheduling is that the size of the frequency domain resource of the shared channel scheduled by the scheduling information is equal to the size of the BWP where the shared channel is located.

In a possible design, the method further includes: receiving, by the second device, a full scheduling request message sent by the first device, where the full scheduling request message includes a request for full scheduling in the frequency domain.

In a possible design, before the second device receives the full scheduling request message sent by the first device, the method further includes: the second device sends full scheduling indication information to the first device, and the full scheduling request message is sent by the second device to the first device. The scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

In a fifth aspect, an embodiment of the present application provides a communication device, the device having the function of implementing the first aspect or any possible method in the design of the first aspect, or implementing the second aspect or any of the second aspect. A function of the method in a possible design, the function can be realized by hardware, or can be realized by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a transceiver unit and a processing unit.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the apparatus includes a processor and a transceiver, the processor is coupled to the transceiver for implementing the method described in the first aspect or any possible design of the first aspect function, or implement the function of the second aspect or any possible design method of the second aspect. The apparatus may further include a memory, where the memory stores functions executable by the processor for implementing the method described in the above first aspect or any possible design of the first aspect, or implementing the above second aspect Or a program of the functionality of the method in any possible design of the second aspect.

In one possible design, the apparatus may be the first device.

In a sixth aspect, an embodiment of the present application provides a communication device, the device having the function of implementing the third aspect or any possible method in the design of the third aspect, or implementing the fourth aspect or any of the fourth aspect. A function of the method in a possible design, the function can be realized by hardware, or can be realized by hardware executing corresponding software. The hardware or software includes one or more units (modules) corresponding to the above functions, such as a transceiver unit and a processing unit.

In one possible design, the device may be a chip or an integrated circuit.

In a possible design, the apparatus includes a processor and a transceiver, the processor is coupled to the transceiver for implementing the method described in the third aspect or any possible design of the third aspect function, or realize the function of the fourth aspect or any possible design method of the fourth aspect. The apparatus may further include a memory storing functions executable by the processor for implementing the method described in the above third aspect or any possible design of the third aspect, or implementing the above fourth aspect Or a program of the functionality of the method in any possible design of the fourth aspect.

In one possible design, the apparatus may be the second device.

In a seventh aspect, an embodiment of the present application provides a communication system, where the communication system may include a first device and a second device, wherein the first device may execute the first aspect or any of the possible designs of the first aspect. The method described above, the second device may execute the method described in the third aspect or any possible design of the third aspect; or, the first device may execute the second aspect or any possible design of the second aspect. The method described in the design of the second device may perform the method described in the fourth aspect or any possible design of the fourth aspect.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium has a method for executing the first aspect or any possible design of the first aspect, or Perform the method described in the second aspect or any possible design of the second aspect above, or perform the method described in the third aspect or any possible design of the third aspect above, or perform the fourth aspect above. A computer program or instructions for the method described in the aspect or any possible design of the fourth aspect.

In a ninth aspect, an embodiment of the present application further provides a computer program product, including a computer program or an instruction, when the computer program or instruction is executed, the above-mentioned first aspect or any possible design of the first aspect can be implemented The method described in, or the method described in implementing the above second aspect or any possible design of the second aspect, or the method described in implementing the above third aspect or any possible design of the third aspect method, or implementing the method described in the fourth aspect or any possible design of the fourth aspect.

In a tenth aspect, the present application further provides a chip for implementing the method described in the first aspect or any possible design of the first aspect, or implementing the second aspect or the second aspect. The method described in any of the possible designs, or the method described in the implementation of the third aspect or any of the possible designs of the third aspect, or the implementation of the fourth aspect or the fourth aspect. method described in the design.

For the technical effects that can be achieved in the third aspect to the tenth aspect, please refer to the technical effects that can be achieved in the first aspect to the second aspect, which will not be repeated here.

Description of drawings

FIG. 1 is one of the schematic diagrams of the communication system architecture provided by the embodiment of the present application;

FIG. 2 is the second schematic diagram of the communication system architecture provided by the embodiment of the present application;

FIG. 3 is one of schematic diagrams of frame formats provided by an embodiment of the present application;

FIG. 4 is one of the schematic diagrams of frequency division multiplexing a segment of spectrum for multi-terminal equipment provided by an embodiment of the present application;

FIG. 5 is one of schematic diagrams of a communication process provided by an embodiment of the present application;

6 is a schematic diagram of K consecutive PDSCHs in the time domain provided by an embodiment of the present application;

FIG. 7 is one of schematic diagrams of different PDSCH time domain lengths provided by an embodiment of the present application;

FIG. 8 is the second schematic diagram of different PDSCH time domain lengths provided by the embodiment of the present application;

FIG. 9 is the second schematic diagram of a frame format provided by an embodiment of the present application;

FIG. 10 is the second schematic diagram of the frequency division multiplexing of a segment of spectrum for multi-terminal equipment provided by an embodiment of the application;

FIG. 11 is a schematic diagram of a HARQ codebook feedback manner provided by an embodiment of the present application;

FIG. 12 is a second schematic diagram of a HARQ codebook feedback manner provided by an embodiment of the present application;

13 is a schematic diagram of a frequency domain resource originally carrying a bit of frequency domain resource information carrying HARQ information according to an embodiment of the present application;

FIG. 14 is a schematic diagram of HARQ codebook feedback provided by an embodiment of the present application;

FIG. 15 is one of the schematic diagrams of DMRS mapping provided by an embodiment of the present application;

FIG. 16 is the second schematic diagram of DMRS mapping provided by the embodiment of the present application;

FIG. 17 is the third schematic diagram of DMRS mapping provided by the embodiment of the present application;

FIG. 18 is the fourth schematic diagram of DMRS mapping provided by the embodiment of the present application;

19 is a schematic diagram of different DMRS densities provided by an embodiment of the present application;

FIG. 20 is the second schematic diagram of the communication process provided by the embodiment of the present application;

FIG. 21 is one of schematic diagrams of a communication device provided by an embodiment of the present application;

FIG. 22 is the second schematic diagram of a communication apparatus provided by an embodiment of the present application.

Detailed ways

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a long term evolution (LTE) system, a fifth generation (5G) mobile communication system, or a new radio (NR) system It can also be extended to related cellular systems such as wireless fidelity (WiFi), worldwide interoperability for microwave access (wimax), and 3GPP, as well as future communication systems. Such as 6G system and so on. Specifically, the architecture of the communication system to which the embodiments of the present application are applied may be as shown in FIG. 1 , including a first device (ie a terminal device) and a second device (ie a network device), where the first device serves as the scheduled device, the first device The second device acts as a scheduling device, the second device can schedule the shared channel of the first device (such as the physical downlink shared channel or the physical uplink shared channel), and the first device and the second device communicate based on the shared channel scheduled by the second device.

It can be understood that the architecture of the communication system to which the embodiments of the present application are applied may also be as shown in FIG. 2 , including a first device (ie, terminal device 1 ) and a second device (ie, terminal device 2 ), where the first device serves as the The scheduled device and the second device are used as scheduling devices, the second device can schedule the shared channel (eg, physical side channel) of the first device, and the first device and the second device communicate based on the shared channel scheduled by the second device.

For ease of description, in the subsequent description of this application, the communication system architecture shown in FIG. 1 is mainly used as an example for description, that is, the shared channel is a physical downlink shared channel or a physical uplink shared channel as an example for description.

Before introducing the embodiments of the present application, some terms in the present application will be explained first, so as to facilitate the understanding of those skilled in the art.

1) Terminal equipment, including equipment that provides voice and/or data connectivity to a user, for example, may include a handheld device with a wireless connection function, or a processing device connected to a wireless modem. The terminal equipment may communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN. The terminal equipment may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, device-to-device (D2D) terminal equipment, V2X terminal equipment, machine-to-machine/machine-type communication ( machine-to-machine/machine-type communications, M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station) , remote station (remote station), access point (access point, AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), or user equipment (user device), etc. For example, these may include mobile telephones (or "cellular" telephones), computers with mobile terminal equipment, portable, pocket-sized, hand-held, computer-embedded mobile devices, and the like. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistants), PDA), etc. Also includes constrained devices, such as devices with lower power consumption, or devices with limited storage capacity, or devices with limited computing power, etc. For example, it includes information sensing devices such as barcodes, radio frequency identification (RFID), sensors, global positioning system (GPS), and laser scanners.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. Wait. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.

The various terminal devices described above, if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be considered as on-board terminal equipment. For example, the on-board terminal equipment is also called on-board unit (OBU). ).

In this embodiment of the present application, the terminal device may further include a relay (relay). Alternatively, it can be understood that any device capable of data communication with the base station can be regarded as a terminal device.

2) A network device may refer to a device in an access network that communicates with a wireless terminal device through one or more cells over an air interface. The network device may be a node in a radio access network, and may also be referred to as a base station, and may also be referred to as a radio access network (radio access network, RAN) node (or device). At present, some examples of network equipment are: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B) B, NB), base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), base band unit (base band unit) , BBU), or wireless fidelity (wireless fidelity, Wifi) access point (access point, AP), etc. In addition, in a network structure, the network device may include a centralized unit (centralized unit, CU) node and a distributed unit (distributed unit, DU) node. The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer.

3), uplink and downlink transmission and time slots, in the communication system architecture shown in Figure 1, the data transmission from the second device to the first device is called downlink transmission, and the data transmission from the first device to the second device is called Uplink transmission, downlink transmission and uplink transmission are performed according to a certain frame format. Data transmission includes either or both of sending data by a sending device and receiving data by a receiving device. The frame format defines which times are used for downstream transmissions, which times are used for upstream transmissions, and how long upstream and downstream transmissions are. Taking the 3rd generation partnership project (3GPP) as an example, 10ms is defined as a frame, each frame includes multiple time slots, and one time slot has 14 orthogonal frequency division multiple access (orthogonal frequency division multiple access). -division multiplexing, OFDM) symbol, for the convenience of description, the OFDM symbol may also be referred to as a symbol for short in the subsequent description of this application, and no further explanation is required. Among them, the one carrying downlink data is called downlink symbol, and the one carrying uplink data is called uplink symbol. If a time slot is all downlink symbols, the time slot is called a downlink time slot, and if a time slot is all uplink symbols, the time slot is called an uplink time slot. Uplink (UL) time slot (slot) is represented by U time slot, downlink (downlink, DL) time slot is represented by D time slot, if a time slot has both uplink symbols and downlink symbols, it is called dedicated time. Slot (special slot) or special time slot, denoted by S. The frame format can be defined in advance according to certain rules, or determined by the configuration of the second device and notified to the first device through high-layer signaling, or dynamically determined by the second device and notified to the first device through high-layer signaling. Some symbols may be determined by the first device as D symbols (ie downlink symbols) or U symbols (ie uplink symbols), these symbols are called flexible symbols or symbols with undefined uplink and downlink, which are represented by F. One of the frame formats is configured in a pattern. For example, the configuration pattern is DDDSU, which means that data transmission is performed according to the pattern of 3 downlink time slots, one S time slot, and one uplink time slot, as shown in Figure 3. Among them, the S time slot includes several D symbols, several U symbols, several F symbols, and can also include several GP symbols, that is, protection symbols. The GP symbols correspond to a certain conversion time, and the conversion time is also called the protection time ( gourd period, GP). The F symbol may be indicated as a D symbol, a U symbol, or a GP symbol according to an indication of dynamic scheduling.

In addition, because the frame includes special time slots, in order to improve the utilization rate of time domain resources, in this embodiment of the present application, the special time slots may also be classified for mapping (or transmitting) corresponding shared channels.

If the downlink symbols in the special time slot (S time slot) are greater than or equal to the first number threshold (N), the special time slot can be used to map (or transmit) the physical downlink shared channel (PDSCH), which can be The special time slot is called a special downlink time slot (special DL slot), or SD time slot for short. If the downlink symbols in a special time slot are less than N, the special time slot may be called a non-special downlink time slot (Non-SD time slot). In the embodiment of the present application, the Non-SD slot is not used to map (or transmit) the PDSCH. Non-SD timeslots are not used to map PDSCH mainly because a shorter PDSCH will bring greater transmission redundancy. Among them, N is greater than or equal to 1 and less than the total number of symbols in the special time slot, which can be determined by the second device and then allocated to the first device, or pre-agreed by the second device and the first device, for example, the second device and the first device The device may agree on N=3. If the downlink symbols in a special time slot are less than N, the special time slot cannot be used for PDSCH mapping. In addition, the first device and the second device have different scheduling parameters, such as bandwidth part (band width part, BWP), sub-carrier spacing (sub-carrier spacing, SCS), demodulation reference signal (demodulation reference signal, DMRS) position etc., different values of N can be configured or agreed upon. For example, when the BWP is less than 20MHz, N=7; when the BWP is greater than or equal to 20MHz, N=2, and so on. For another example, when the DMRS symbol position is 2, N=3, and when the DMRS position is symbol 3, N=4.

If the uplink symbols in the special time slot (S time slot) are greater than or equal to the second number threshold (M), the special time slot can be used to map (or transmit) the physical uplink shared channel (PUSCH), which can be The special time slot is called a special uplink time slot (special UL slot), or SU time slot for short. If the uplink symbol in a special time slot is less than M, the time slot is called a non-special uplink time slot (Non-SU time slot). In the embodiment of the present application, the Non-SU slot is not used to map (or transmit) the PUSCH. Non-SD time slots are not used to map PUSCH mainly because a shorter PUSCH will bring greater transmission redundancy. Among them, M is greater than or equal to 1 and less than the total number of symbols in the special time slot, which can be determined by the second device and then allocated to the first device, or pre-agreed by the second device and the first device, for example, the second device and the first device The device may agree that M=1. If the uplink symbol in a special time slot is less than M, the special time slot cannot be used for mapping PUSCH. In addition, the first device and the second device may also configure or agree on different values of M for different scheduling parameters, such as BWP, SCS, and so on. For example, when the BWP is less than 20MHz, M=7, and when the BWP is greater than or equal to 20MHz, M=2, etc. For another example, when the BWP is less than or equal to 51 resource blocks (resource blocks, RBs), M=7. When the BWP is greater than 51RB, M=4.

In addition, it should be understood that, in this application, a special time slot can be either an SD time slot or an SU time slot. That is, a special time slot, for PDSCH, is a special downlink time slot, and for PUSCH, it is also a special uplink time slot.

In addition, it can be understood that, in the communication system architecture shown in FIG. 2 , the first device and the second device communicate through a side link. Taking 3GPP as an example, 10ms is defined as a frame, each frame includes multiple time slots, and a time slot has 14 symbols, among which, the sidelink data is called sideline symbol; If all the slots are side row symbols, the time slot is called a side row slot. In 4G and 5G protocols, side-line symbols generally use the resources of uplink symbols. Because the frame contains special time slots, in order to improve the utilization rate of time domain resources, the first device and the second device can also determine the special time slot including the number of sideline symbols greater than or equal to the third number threshold (0) as the special sideline time slot A slot is used to map a physical sidelink shared channel (PSSCH), wherein the third number threshold can be determined by the second device and then configured to the first device, or pre-agreed by the second device and the first device.

4) Downlink control information (DCI), also known as downlink control signaling, in the communication architecture shown in Figure 1, the scheduling information of the second device to the first device is usually carried by DCI, which is carried by The scheduled PDSCH or PUSCH air interface transmission resources include time domain resource indication information and frequency domain resource indication information. In the communication architecture shown in FIG. 2 , the first device and the second device communicate through the sidelink, and the scheduling information of the second device to the first device is usually carried by the sidelink control information (SCI), The SCI carries the scheduled PSSCH air interface transmission resources, including time domain resource indication information and frequency domain resource indication information. Without loss of generality, we take the downlink control signaling as an example to illustrate. The time domain resource indication information is represented by bits 0-4, which are used to indicate the time slot where the scheduled PDSCH or PUSCH is located, the length of the PDSCH or PUSCH, and the mapping type of the PDSCH or PUSCH. Specifically, the second device can configure the time domain resource table through high-level signaling. The time domain resource table has a maximum of 16 lines. In the 3GPP R-15 protocol, each line includes the following parameters: a SLIV, K2 parameter (with for PUSCH) or K0 parameter (for PDSCH), PDSCH mapping type (mapping type) or PUSCH mapping type (mapping type). Among them, the SLIV value is the result obtained by jointly encoding S and L. Among them, S represents the time domain starting symbol position of PDSCH or PUSCH, L represents the time domain length of PDSCH or PUSCH, and SLIV and S and L satisfy the following mapping relationship:

If (L-1)≤7,

Then SLIV=14*(L-1)+S;

Otherwise SLIV=14*(14-L+1)+(14-1-S),

where 0<L≤(14-S).

In this application, the above-mentioned mapping relationship is referred to as mapping relationship (1). Among them, the value ranges of S and L are shown in Table 1 and Table 2. Through the above mapping relationship (1), a SLIV value can uniquely determine a combination of the value of S and the value of L, and a combination of the value of S and the value of L can also uniquely determine a SLIV value. Wherein, Table 1 is a table of valid combinations of S and L in the time domain resources of downlink transmission, and Table 2 is a table of combinations of valid S and L in the time domain resources of uplink transmission.

Table 1

Table 2

In the 3GPP R-16 protocol, in order to increase the reliability of data transmission, further, each TB can be repeatedly transmitted many times, and the number of repetitions is further introduced. Among them, each row of the PDSCH time domain table includes PDSCH mapping type (mapping type), K0 parameter, SLIV parameter and repetition number (repetitionNumber), and each row of the PUSCH time domain table includes PUSCH mapping type (mapping type), K2 parameter, S parameter, L parameter and repetitionNumber. Among them, the meaning of S parameter and L parameter is the same as that of R-15, see Table 1 and Table 2. Taking PUSCH as an example, Table 3 gives an example of an R-16 PUSCH time domain table.

Row index PUSCH mapping type K ₂ S L RepetitionNumber 1 Type B 1 2 2 4 2 Type B 1 4 2 8 3 Type B 2 2 4 4 4 Type B 2 2 4 16 5 Type B 3 7 7 3 6 Type B 3 7 7 2 7 Type B 1 4 4 1 8 Type B 1 5 7 2 9 Type B 2 5 2 3 10 Type B 2 9 2 7 11 Type B 3 12 2 8 12 Type B 3 1 13 12 13 Type B 0 12 2 16 14 Type B 0 12 4 1 15 Type B 0 7 7 2 16 Type B 0 7 4 6

table 3

计算得到的比特长度来表示，再例如，对于PUSCH，频域资源指示信息的大小根据资源分配类型和BWP大小确定，如仅配置了资源分配类型0，则频域资源指示信息为N _RBG比特，如仅配置了资源分配类型1，则频域资源指示域的比特位为根据

计算得到的比特长度，如即配置了资源分配类型0，也分配了资源类型1，则用根据

计算得到的比特位来表示。其中，

为被调度的PDSCH的BWP大小，

为被调度的PUSCH的BWP的大小，N _RBG为被调度的PUSCH的RBG的大小，公式给出了对于所确定的资源分配类型和所确定的BWP大小，需要用多少比特来指示其资源。其中，资源分配类型0用比特图来表示哪些RBG被分配给第一设备，或用资源的起始位置和长度来表示哪些RBG被分配给第一设备。 The frequency domain resource indication information indicates the frequency domain resources that bear the shared channel, and is indicated by three information fields, including a carrier indicator field of 0-3 bits, which is used to indicate the component carrier where the scheduled shared channel is located. carrier, CC), the 0-2 bit part bandwidth part indicator field, used to indicate the BWP where the scheduled shared channel is located, and the frequency domain resource indication field, used to indicate that the scheduled shared channel is located in the The frequency domain resources occupied by the BWP, and the bit size of the frequency domain resource indication field is related to the size of the BWP where the scheduled PDSCH or PUSCH is located. For example, for PDSCH, the bits in the frequency domain resource indication field are based on

It is represented by the calculated bit length. For another example, for PUSCH, the size of the frequency domain resource indication information is determined according to the resource allocation type and BWP size. If only resource allocation type 0 is configured, the frequency domain resource indication information is N _RBG bits, If only resource allocation type 1 is configured, the bits in the frequency domain resource indication field are based on

The calculated bit length, if both resource allocation type 0 and resource type 1 are configured, use the

Calculated bits to represent. in,

is the BWP size of the scheduled PDSCH,

is the size of the BWP of the scheduled PUSCH, N _RBG is the size of the RBG of the scheduled PUSCH, and the formula gives how many bits are needed to indicate its resources for the determined resource allocation type and the determined BWP size. The resource allocation type 0 uses a bitmap to represent which RBGs are allocated to the first device, or uses the start position and length of the resources to represent which RBGs are allocated to the first device.

In addition, it should be understood that the time slot described in this application refers to a scheduled time unit, which may include at least one time symbol, may be a time slot (slot) composed of multiple symbols, or a sub-frame (sub-frame) ), or frame, or mini-slot, or sub-slot, or transmission time interval (TTI), or short transmission period (short TTI, sTTI), etc., For simplicity, we take the time slot as an example for description.

In the prior art, in a cellular communication system, the terminal device (ie the first device) according to the frequency domain bandwidth resources scheduled by the network device (ie the second device), such as the scheduled frequency band (band), carrier (carrier), A component carrier (component carrier) or a part of the frequency domain resource block (RB) in the BWP is used for communication, and the network device can configure or activate a part of the frequency domain bandwidth resource for the terminal device in advance. In a 4G LTE system, scheduling occurs within an activated carrier, and in a 5G NR system, scheduling usually occurs within an activated BWP. Since a network device may serve multiple terminal devices at the same time, the network device will schedule multiple terminal devices at the same time, and these terminal devices reuse this section of frequency domain bandwidth resources by means of frequency division multiplexing. As shown in FIG. 4 , within this period of frequency domain resources, the frequency domain resources of different terminal devices may be localized (localized) allocating a section of resources or distributed (distributing) allocating a certain amount of frequency domain resources.

However, the network device will be in the BWP activated by the terminal device (for simplicity, we take the frequency domain bandwidth resource as BWP as an example for description) any frequency domain resource may schedule the terminal device. Therefore, the transceiver of the terminal device (such as sending and receiving (phone etc.) always configure and prepare resources according to the activated BWP as a whole. In the existing network, it is found that the terminal equipment is generally configured with a relatively large BWP, such as 100MHz, which is 273 RBs, while the actual terminal is scheduled with less resources, such as 10 RBs. According to the 3GPP NR protocol, when the SCS is 30khz, the total The frequency domain resource scheduled to the terminal equipment is 3.6MHz, that is to say, about 94% of the spectrum resources have not been used by the terminal equipment. The long-term scheduling of the terminal equipment will bring greater power consumption to the terminal equipment.

In addition, the existing network equipment only schedules the shared channel mapped in one time slot at a time, and the frequency domain resources of the shared channel are only a part of the activated BWP, and the scheduled time-frequency resources are few, so that the scheduled time-frequency resources can be The data carried is also less, and the actual service needs to carry a large amount of data. The device that needs to receive the scheduling information continuously monitors the PDCCH to obtain the scheduling information, which increases the power consumption of the device. For example: the actual speed of the existing terminal equipment is usually only about 1Mbps. For some common applications, such as uploading 1-2M photos, the terminal device needs to continuously monitor the PDCCH for more than 1s and keep it active for more than 1s. If you want to download a 500Mb movie, it even needs to continuously monitor the PDCCH for a few minutes and keep it for a few minutes. active state, which increases the power consumption of the terminal device.

The purpose of this application is through time-domain full scheduling (that is, scheduling information to schedule multiple shared channels at a time) and/or frequency-domain full scheduling (that is, the size of the frequency domain resources of the scheduled shared channel is equal to the size of the bandwidth part BWP where the shared channel is located) ) scheduling method to reduce the power consumption of the scheduled device during data transmission.

In addition, it should be understood that, in the embodiments of the present application, at least one may also be described as one or more, and the multiple may be two, three, four or more, which is not limited in this application. In this embodiment of the present application, "/" may indicate that the objects associated before and after are an "or" relationship, for example, A/B may indicate A or B; "and/or" may be used to describe that there are three types of associated objects A relationship, for example, A and/or B, can mean that A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In order to facilitate the description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" may be used to distinguish technical features with the same or similar functions. The words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not limit the difference. In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or illustrations, and any embodiment or design solution described as "exemplary" or "for example" should not be construed are preferred or advantageous over other embodiments or designs. The use of words such as "exemplary" or "such as" is intended to present the relevant concepts in a specific manner to facilitate understanding.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 5 is a schematic diagram of a communication process provided by an embodiment of the present application, and the process includes:

S501: A second device sends a first message to a first device, and the first device receives the first message, where the first message includes scheduling information for scheduling K shared channels.

The K shared channels are mapped to K time slots for carrying S different TBs, the K is a positive integer greater than or equal to 2, and the S is a positive integer greater than or equal to the K.

In a possible implementation, the second device may carry scheduling information through the first message, and send the scheduling information to the first device through the first message, where the scheduling information carries the air interface transmission resources of the shared channel of the first device, For example, the air interface transmission resources of PDSCH, PUSCH or PSSCH are recorded, including time domain resource indication information and frequency domain resource indication information. As an example, the first message may be DCI.

In this embodiment of the present application, K shared channels are mapped to K time slots, and each shared channel is mapped to a different time slot. In a possible implementation, the time domain resource indication information may be used to indicate continuous time-domain K timeslots that can be used to map the shared channel to realize the indication (or scheduling) of the K shared channel time-domain resources; in another possible implementation, the time-domain resource indication information is used to indicate consecutive M in the time-domain time slots, wherein the M time slots include K time slots that can be used to map the shared channel, and the M is a positive integer greater than or equal to the K, to realize the indication of the K shared channel time domain resources (or scheduling). Among them, if the shared channel is PDSCH, the time slots that can be used to map the shared channel are downlink time slots (including special downlink time slots); if the shared channel is PUSCH, the time slots that can be used to map the shared channel are uplink time slots (including special uplink time slots). time slot); if the shared channel is PSSCH, the time slot that can be used to map the shared channel is the sideline time slot (including the special sideline time slot). It should be understood that the downlink time slot may be a special downlink time slot, the uplink time slot may be a special uplink time slot, and the side-going time slot may be a special side-going time slot.

Taking the shared channel as PDSCH and K equal to 6 as an example, the time domain resource indication information can indicate K consecutive downlink time slots in the time domain that can be used to map the shared channel (which may include a special downlink time slot S), as shown in Figure 6, Then, starting from time slot n, schedule 6 consecutive downlink time slots, that is, from time slot n to time slot n+6, where time slot n+4 is an uplink time slot, then in the 6 consecutive downlink time slots, Slot n+4 is not included. From the time dimension, there are a total of 7 time slots. Also referring to FIG. 6 , still taking the shared channel as PDSCH and K equal to 6 as an example, if the time domain resource indication information indicates M consecutive time slots in the time domain, then M is equal to 7, that is, it indicates the time from time slot n to time gap n+6.

Each of the K shared channels can carry R TBs, and each TB is carried in a time slot that can be used to map the shared channels. Each TB is carried by only one time slot, which can reduce the processing complexity. R is a positive integer greater than or equal to 1. As an example, the value of R may be related to the number of layers of the shared channel. Taking the shared channel as PDSCH as an example, if the number of layers of PDSCH is small, for example, the number of layers of PDSCH is less than or equal to 8, then R=1; if the number of layers of PDSCH is large, such as the number of layers of PDSCH is greater than 8, then R= 2.

In addition, the symbol lengths of the shared channels in each time slot may be the same or different. Still taking the shared channel as PDSCH as an example, for a normal cyclic prefix (CP) OFDM system, among the K PDSCHs, the time domain symbol lengths of the first PDSCH and the last PDSCH can be less than or equal to 14 symbols, and the other The length of the time-domain symbol of the PDSCH is equal to the length of the downlink symbol of the time slot in which it is located. For an OFDM system with extended CP, among the K PDSCHs, the time-domain symbol lengths of the first PDSCH and the last PDSCH may be less than or equal to 12 symbols, and the time-domain symbol lengths of other PDSCHs may be equal to 12 symbols. That is to say, the K PDSCHs are continuous in time from the start symbol to the end symbol, or are continuous in time except for some uplink symbols and special symbols, but the start symbol may not be symbol 0, and the end symbol may not be Symbol 13. The advantage of this is that the appropriate time-domain symbol length can be selected according to the size of the actual data packet to be transmitted, so as to avoid the waste of resources caused by the fact that all time slots are 14 symbols. For example, assuming that a data packet needs 32 symbols for transmission, as shown in FIG. 7 , according to the embodiment described in this application, K=3, 3 PDSCHs are scheduled, and the length of the first PDSCH time domain symbol is 11 symbols, The length of the second PDSCH time domain symbol is 14 symbols, and the length of the third PDSCH time domain symbol is 7 symbols. Correspondingly, the size of the TB carried by each PDSCH is also different.

Alternatively, as shown in FIG. 8 , assuming that a data packet requires 32 symbols for transmission, according to the embodiment described in this application, K=3, 3 PDSCHs are scheduled, and the length of the first PDSCH time domain symbol is 11 symbols , the length of the second PDSCH time domain symbol is 9 symbols, and the length of the third PDSCH time domain symbol is 12 symbols. Correspondingly, the size of the TB carried by each PDSCH is also different.

In a possible implementation, the time domain resource indication of the K shared channels (taking PDSCH as an example) may be indicated by three parameters (K0, S, L). Among them, K0 represents the time slot difference between the time slot where the PDCCH is located and the time slot where the first PDSCH is located, S represents the symbol number of the starting symbol of the first PDSCH in the time slot where the first PDSCH is located, and L represents the total number of PDSCHs. time-domain symbol length or total time-domain downlink symbol length. The total time-domain symbol length described here includes uplink symbols and symbols used for guard time, and the total time-domain downlink symbol length does not include uplink symbols and symbols used for guard time. Taking FIG. 7 and FIG. 8 as examples, K0, S and L are used as the method for determining the time slots where multiple PDSCHs are located. If L represents the total time-domain symbol length of multiple PDSCHs, then L=32 in FIG. 7 and FIG. 8 Medium L=37. If L represents the total time-domain downlink symbol length of multiple PDSCHs, in both FIG. 7 and FIG. 8 , L is equal to 32. For simplicity, we take L representing the total time-domain downlink symbol length as an example for description. For the specific embodiments of FIG. 7 and FIG. 8 , K0=0, S=3, L=32, and the instant domain indication information may include K0=0, S=3, L=32.

In another possible implementation, the time domain resource indication of the K shared channels (taking PDSCH as an example) can be indicated by four parameters (K0, S, W, E), where K0 represents the time slot where the PDCCH is located The time slot difference with the time slot where the first PDSCH is located, S represents the symbol number of the start symbol of the first PDSCH in the time slot where the first PDSCH is located, W represents the number of consecutive time slots or the number of consecutive downlink time slots, E represents the length of the last PDSCH. K0, S, W and E are used as the method for determining the time slots where multiple PDSCHs are located. Taking FIG. 7 as an example, K0=0, S=3, W=3, and E=7; taking FIG. 8 as an example, K0= 0, S=3, W=3, E=12. Let W represent the number of consecutive time slots, then the W time slots include uplink time slots or non-special downlink time slots; let W represent the number of consecutive downlink time slots, then the W time slots do not include uplink time slots, do not include Non-special downlink time slots, including only downlink time slots or special downlink time slots. Taking FIG. 6 as an example, if W represents the number of consecutive time slots, W=7; if W represents the number of consecutive downlink time slots, W=6.

In another possible implementation, the time domain resource indication of the K shared channels (taking PDSCH as an example) can be indicated by four parameters (K0, S, W', E'), where K0 indicates where the PDCCH is located The time slot difference between the time slot and the time slot where the first PDSCH is located, S represents the symbol number of the start symbol of the first PDSCH in the time slot where the first PDSCH is located, W' represents the time slot number where the last PDSCH is located, E' Indicates the symbol number where the last PDSCH is located.

Further, the scheduled K PDSCHs and the sizes of the TBs carried in the K PDSCHs may be different. The size of the TB in a PDSCH can be adaptively adjusted according to the symbol length of the PDSCH. For example, the first device and the second device can determine the symbol length of each PDSCH through DCI signaling, so the size of each TB can be calculated according to the symbol length of each PDSCH.

In addition, the first message (eg, DCI) schedules K PDSCHs, and may have the same length as scheduling information for scheduling one PDSCH. This means that, except for the time domain resources, the K PDSCHs may adopt the same scheduling parameters, that is, the scheduling parameters included in the first message are applicable to the multiple PDSCHs. Exemplarily, in addition to the time domain resource indication information and the frequency domain resource indication information, the first message may also include other signaling, such as indicating a virtual resource block (virtual resource block, VRB) to a physical resource block (physical resource block, Signaling in PRB) mapping mode, signaling in PRB bundling mode, signaling indicating transmission configuration indication (TCI) state, signaling indicating antenna port configuration, signaling indicating resource information of PUCCH And so on, and so on, in the embodiments described in this application, these signalings of K PDSCHs are all the same. The first message may also include information indicating the MCS, information about the redundancy version (redundancy version, RV), and a new data indicator (new data indicator, NDI) indicating a new transmission and retransmission, etc. The K PDSCHs use the same MCS and redundant versions. If the DCI indicates that one PDSCH includes two TBs, and each TB has its own MCS, RV and NDI, then correspondingly, each of the K PDSCHs also includes two TBs, and they all use the same corresponding PDSCH. MCS, RV and NDR. For example, the values of MCS, RV and NDI of the first TB in PDSCH 1 are (4, 2, 0) respectively, and the values of MCS, RV and NDI of the second TB in PDSCH 1 are (9, 1, 0), then the values of MCS, RV and NDI of the first TB in PDSCH 2 are also (4, 2, 0), respectively, and the values of MCS, RV and NDI of the second TB in PDSCH 2 are also (4, 2, 0). The values are also (9, 1, 0) respectively.

Similarly, when the shared channel is PUSCH, three parameters (K1, S, L) can be used to indicate the time domain resources of K PUSCHs, or four parameters (K1, S, W, E) can be used to indicate Time domain resources of K PUSCHs, where K1 is the time slot difference between the start time slot of the first PUSCH in the K PUSCHs and the time slot where the first message is located, S is the start symbol number of the first PUSCH, L In order to represent the total time-domain symbol length or the total time-domain uplink symbol length of multiple PUSCHs, W represents the number of consecutive time slots or the number of consecutive uplink time slots, and E represents the length of the last PUSCH. It is also possible to use K1, S, and the time slot number of the last PUSCH, the symbol number of the last PUSCH and other information to realize the scheduling of the K PUSCHs. In addition, similar to PDSCH, the sizes of TBs carried in the K scheduled PUSCHs may be different. The size of the TB in a PUSCH can also be adaptively adjusted according to the symbol length of the PUSCH. For the realization of the time domain resource indication information for K PUSCH scheduling, refer to the above time domain resource indication information for K PDSCHs. The realization of scheduling is not repeated here.

In addition, for the TDD system, in a possible implementation, when the shared channel is PDSCH, the scheduling of K PDSCHs from the start time slot to the end time slot will not be greater than one downlink to uplink transition point; when the shared channel is PUSCH When , from the start time slot of PUSCH to the end time slot of PUSCH, the scheduling will not be greater than one uplink to downlink transition point. The advantage that the scheduled shared channel does not cross transition points (uplink to downlink transition point or downlink to uplink transition point) is that it can avoid the need to identify unmappable shared channel symbols in time domain resources, thereby simplifying the design.

As an example, taking the K scheduled shared channels as K PUSCHs as an example, as shown in FIG. 9 , if the time slot of the starting PUSCH is in time slot n, the value of K is less than or equal to 3; In time slot n+1, the value of K is less than or equal to 2.

In this embodiment of the present application, the size of the frequency domain resources of the K shared channels may be smaller than the size of the BWP where the K shared channels are located (that is, the frequency domain is not fully scheduled), or may be equal to the BWP where the K shared channels are located size (that is, full scheduling in the frequency domain). That is, when the second device schedules the first device, it can only use time-domain full scheduling (that is, schedule multiple shared channels at a time), or it can use both time-domain full scheduling and frequency-domain full scheduling (that is, the scheduling of the shared channels to be scheduled). The size of the frequency domain resource is equal to the size of the BWP where the shared channel is located or the size of the carrier where the shared channel is located). Among them, for full scheduling in the frequency domain, that is, the size of the frequency domain resources of the K shared channels is equal to the size of the BWP where the K shared channels are located, the frequency domain resources of the shared channels can be indicated by bandwidth part indicator, which is used to indicate the current The BWP where the scheduled shared channel is located. When the second device determines that the frequency domain full scheduling is applicable to BWP, and when the scheduled CC includes multiple configured or activated BWPs, the frequency domain resource indication information may also indicate the scheduled shared channel (eg, a BWP index) through a BWP index. PDSCH or PUSCH) is located in the BWP. When the second device determines that the full scheduling in the frequency domain is applicable to a component carrier (component carrier, CC), and when the second device has multiple activated carriers, the frequency domain resources of the shared channel can also be indicated by a carrier identifier.

For full scheduling in the frequency domain, the scheduled shared channel, such as PDSCH or PUSCH or PSSCH, has a frequency domain resource size equal to the size of the BWP where the scheduled PDSCH or PUSCH or PSSCH is located, and the frequency domain of the scheduled PDSCH or PUSCH or PSSCH is mapped to this frequency domain. All of the BWPs where the PDSCH, PUCSH or PSSCH are located may be used to carry resources of the PDSCH, PUSCH or PSSCH. This can be used to carry PDSCH or PUSH or PSSCH resources. For downlink, it refers to removing PDCCH, synchronization signal and physical broadcast channel (PBCH) block (synchronization signal and PBCH block, referred to as SSB), and through rate matching The style indicates the occupied BWP resources. For the uplink, it means removing the SRS and indicating the occupied BWP resources by the rate matching pattern. Exemplary: compared to the prior art scheduling method shown in FIG. 4 , the frequency domain scheduling described in this application is shown in FIG. 10 . It can be seen that in the prior art, the first device only uses part of the frequency domain resources in the BWP , and the frequency domain full scheduling described in this application means that the first device uses all frequency domain resources in the BWP, which can improve data transmission efficiency and save power consumption of the first device.

For full scheduling in the frequency domain, the scheduled shared channel, such as PDSCH or PUSCH or PSSCH, the size of its frequency domain resources is the size of the component carrier bandwidth where the scheduled PDSCH or PUSCH or PSSCH is located, and the frequency domain mapping of the scheduled PDSCH or PUSCH or PSSCH The entire bandwidth up to the component carrier where the PDSCH or PUSCH or PSSCH is located can be used to carry the resources of the PDSCH or PUSCH or PSSCH. This can be used to carry PDSCH or PUSH or PSSCH resources. For downlink, it refers to removing PDCCH, synchronization signal and physical broadcast channel (PBCH) block (synchronization signal and PBCH block, referred to as SSB), and through rate matching The pattern indicates the occupied resources within the component carrier bandwidth. For the uplink, it means removing the SRS and indicating the occupied resources within the component carrier bandwidth by the rate matching pattern.

For frequency-domain full scheduling, if the first message is DCI, the bit in the frequency-domain resource indication field in the DCI that was originally used to indicate the frequency-domain resources occupied by the scheduled shared channel in the BWP where it is located may be set to 0, or One or more bits in the frequency domain resource indication field are multiplexed, for example, used to carry other information, and of course they can also be reserved.

S502: The first device and the second device communicate based on the K shared channels.

In the implementation of this application, the first device and the second device can communicate according to the scheduled K shared channels, for example, the downlink data transmission is performed according to the scheduled PDSCH, the uplink data transmission is performed according to the scheduled PUSCH, and the scheduled PSSCH is performed. Transmission of sideline data, etc., and feedback of the transmitted downlink data or uplink data or sideline data.

Specifically, in this embodiment of the present application, one shared channel may correspond to a certain hybrid automatic repeat request (HARQ) process. Specifically, the scheduled K shared channels may correspond to one HARQ process, and the scheduled K Each of the shared channels may also correspond to one HARQ process. The HARQ processes corresponding to the K shared channels may be indicated by the HARQ process indication information carried in the first message.

Method 1: The HARQ process indication information includes a HARQ process number, which is used to indicate one HARQ process corresponding to the K shared channels.

The K shared channels jointly correspond to one HARQ process, and this design can save signaling. When the first message is DCI, the existing DCI design can also be reused, and the compatibility is good. However, since one HARQ process corresponds to K shared channels, the amount of data that needs to be buffered corresponding to the HARQ process increases, which increases the cost of the first device. This problem can be overcome for the design that adopts the shared buffer between HARQ processes.

Method 2: The HARQ process indication information includes a HARQ process number, and the HARQ processes corresponding to the K shared channels can be obtained according to a predefined rule or through pre-signaling interaction.

As an example, the predefined rule may be: a part of the HARQ process is reserved for a first message (or scheduling information included in the first message) to schedule a shared channel, and a part of the HARQ process number is used for one of the HARQ processes described in this application. The first message schedules K shared channels. For example, the total number of HARQ processes is 16, numbered from 0. HARQ processes 0-7 are used for scheduling one shared channel for one first message, and HARQ processes 8-16 are used for scheduling K shared channels for one first message. Of course, all HARQ process numbers may be used for one first message to schedule one shared channel, or may be used for one first message to schedule multiple shared information. The following describes in conjunction with specific methods.

Manner 1: The HARQ process indication information includes a HARQ process ID, which is used to indicate that K consecutive HARQ processes starting with the HARQ process corresponding to the HARQ process ID are in one-to-one correspondence with the K shared channels.

As an example: the HARQ process indication information includes the process ID of process H, then HARQ process H corresponds to the first shared channel among the K shared channels, and is associated with the TB carried by the first shared channel; HARQ process H+1 Corresponding to the second shared channel, it is associated with the TB carried by the second shared channel; and so on, until the HARQ process H+K-1 corresponds to the Kth shared channel and is associated with the TB carried by the Kth shared channel.

When the shared channel is PDSCH, the following two specific implementation manners are also available for the HARQ codebook, taking each PDSCH carrying one TB as an example, and the specific reference is shown in FIG. 11 .

Feedback mode 1: Referring to HARQ codebook feedback mode 1 in Figure 11, K bits can be used for feedback. If all TBs carried by a PDSCH have transmitted correct feedback ACK, it is represented by 1; otherwise, NACK is fed back, which is represented by 0.

Feedback mode 2: Referring to HARQ codebook feedback mode 2 in FIG. 11 , except for the first transmission, only the retransmitted PDSCH is fed back. This feedback mode HARQ payload size is variable, but it saves signaling resources. Feedback can preferably be done in this way.

Manner 2: The HARQ process indication information includes a HARQ process number, which is used to indicate that the K idle HARQ processes starting with the HARQ process corresponding to the HARQ process number are in one-to-one correspondence with the K shared channels.

As an example: the HARQ process indication information includes the process ID of process H, then HARQ process H corresponds to the first shared channel among the K shared channels, and is associated with the TB carried by the first shared channel; the next idle HARQ process Corresponding to the second shared channel, it is associated with the TB carried by the second shared channel; and so on, until the Kth shared channel corresponds to the corresponding idle HARQ process. In a possible implementation, if there is no corresponding HARQ process on the shared channel after the HARQ process with the largest HARQ process number is reached, the search for an idle HARQ process is continued from HARQ process zero. And so on, until the Kth shared channel corresponds to the corresponding idle HARQ process. The advantage of this design is that during scheduling, there is no need to wait for K consecutive idle HARQ processes, but as long as there are K idle HARQ processes, it is more flexible and efficient. Further, after the K idle process numbers are used for the first time, the successfully transmitted HARQ processes can be released at any time when the transmission is successful, and it is not necessary to keep these HARQ processes all the time. The HARQ process that has been successfully transmitted can be released at any time to obtain more HARQ processes for subsequent scheduling, but the HARQ process mapping process is relatively more complicated.

Method 2 This design saves signaling, can reuse the existing DCI design, and has good compatibility. In addition, each TB of the shared channel is associated with its own HARQ process, and the HARQ data buffer is the same as the existing design, and it is simpler to increase the HARQ data buffer. The disadvantage of this design is that the association relationship between multiple HARQ processes and the shared channel needs to be preset, which limits the flexibility of HARQ process selection. If the association relationship between the HARQ process and the shared channel is determined according to the predefined rules, the problem of flexibility is overcome, but if there is a mismatch between the second device and the first device due to errors, it will lead to a mapping relationship error.

As shown in Figure 12, when the shared channel is PDSCH, for the HARQ codebook, each PDSCH carries one TB as an example. Specifically, as shown in Figure 12, the first PDSCH corresponds to HARQ process 5, and the second PDSCH corresponds to HARQ process 5. The PDSCH corresponds to HARQ process 6, the third PDSCH corresponds to HARQ process 1, and the fourth PDSCH corresponds to HARQ process 2. Similarly, for the HARQ codebook feedback corresponding to this method, HARQ codebook feedback method 1 can be used, that is, K bits are fixed for feedback, or HARQ codebook feedback method 2 can be used, that is, except for the first transmission, Only the retransmitted PDSCH is fed back.

Method 3: The HARQ process indication information includes K HARQ process numbers, which are used to indicate K HARQ processes corresponding to the K shared channels one-to-one.

比特来指示被调度的频域资源。可以用原HARQ信息承载比特(含RV和NDI标识)承载一个HARQ进程号，剩余的HARQ进程号通过

比特来承载。为了不引入由于DCI比特数变化导致的DCI检测复杂度增加，本申请提出一种实施，根据频域资源指示域的比特数和HARQ比特数确定K的取值，其中一种方法为：

其中，R为频域资源指示域比特位宽，Q为HARQ信息比特数，K为被调度的最大PDSCH的个数，

表示对R/(Q+2)的结果进行向下取整。按照这种方式，下表4给出了几个具体的取值。当然也可以通过增加DCI的比特来实施本方法，这种方式K的取值不受限，但会导致DCI检测复杂度增加。第一设备和第二设备可以根据实际情况来选择本申请所述的这两种设计中的任意一种或者全部。 When the first message is DCI, for full scheduling in the frequency domain, the size of the frequency domain resources of the K shared channels is equal to the size of the BWP where the K shared channels are located, and there is no need to indicate the size of the BWP where the K shared channels are located. frequency domain resources. Therefore, for the HARQ process indication information including the K HARQ process numbers corresponding to the K shared channels one-to-one, the bits originally used to indicate the frequency domain resource information occupied by the shared channel in the BWP can also be used to indicate the HARQ process number. Taking the PDSCH as the shared channel as an example, according to the prior art, there are several bits in the DCI related to the BWP size of the scheduled PDSCH to indicate the scheduled frequency domain resources, such as using

bits to indicate the scheduled frequency domain resources. The original HARQ information bearing bits (including RV and NDI identifiers) can be used to carry a HARQ process number, and the remaining HARQ process numbers are passed through

bits to carry. In order not to introduce an increase in the complexity of DCI detection due to changes in the number of DCI bits, the present application proposes an implementation where the value of K is determined according to the number of bits in the frequency domain resource indication field and the number of HARQ bits, and one of the methods is:

Among them, R is the bit width of the frequency domain resource indication domain, Q is the number of HARQ information bits, K is the maximum number of scheduled PDSCHs,

Indicates that the result of R/(Q+2) is rounded down. In this way, Table 4 gives several specific values. Of course, this method can also be implemented by increasing the bits of the DCI. The value of K in this manner is not limited, but it will lead to an increase in the complexity of DCI detection. The first device and the second device may select any one or all of the two designs described in this application according to actual conditions.

Table 4

Taking the DL BWP bandwidth of 48RB and the number of HARQ process bits as 3 bits as an example, at this time, after calculating K=3, we can use the original HARQ process information bits, RV bits and NDI bits to carry the information of one of the PDSCHs, as shown in Figure 13 As shown, some or all of the 11 bits in the frequency domain resource indication domain carry the HARQ information of the other two PDSCHs.

In the above-mentioned method 1 and method 2, only one HARQ process number is carried in the first message. During initial transmission, the corresponding relationship between each shared channel and the HARQ process number can be designed in various ways. How to notify which TB is, there are several specific implementation methods as follows:

Method 1: S TBs of K shared channels have only one HARQ ACK/NACK feedback bit. Once retransmitted, all K shared channels are retransmitted. This method is the simplest to design, but the system transmission efficiency is low.

Method 2: Each of the K shared channels has independent HARQ ACK/NACK feedback bits. At this time, according to the feedback ACK/NACK, it is determined which TB of the shared channel or the specific TB needs to be retransmitted. In addition, when the first message is DCI, in order not to increase the complexity by adding a new DCI format, two methods can be adopted:

Manner 1: Use frequency domain resources to indicate bits in the domain. If the time-domain full scheduling and the frequency-domain full scheduling are used in combination, in the frequency-domain full scheduling, the bits in the frequency domain resource indication field originally used to indicate the frequency domain resources occupied by the shared channel in the BWP no longer need to carry the frequency domain. Domain resource information, these bits can be used to indicate which shared channel was retransmitted. For example, if 1 is used to indicate retransmission, then 4 bits are 0101, indicating that the TBs carried by the second shared channel and the fourth shared channel are retransmitted, and the TBs carried by the first shared channel and the third shared channel have been successfully transmitted and will not be transmitted. . It should be noted that at this time, from the initial transmission of 4 shared channels (such as PDSCH) to the retransmission of 2 shared channels (such as PDSCH), K in the time domain resource indication can be changed from 4 to 2, or maintain K= 4 remains unchanged. Both designs are acceptable, and the first device and the second device may agree in advance whether to change the value of K during retransmission.

Mode 2: Use code block group transmission indication (CBGTI) bits (applicable to the shared channel being PDSCH). Taking the first message as DCI as an example, in the prior art, in DCI, CBGTI is used to indicate which CBG is to be retransmitted in a TB configured with a code block group (code block group, CBG). This application may reuse this bit to indicate which TB was retransmitted. Assuming that N_CBG CBGs are configured, N_CBG indicates the number of CBGs included in each TB, and K*N_CBG bits are used to indicate which CBG of which TB is to be retransmitted. Currently, CBGTI can be configured as 0, 2, 4, 6, and 8 bits. For the single DCI designed in this application to schedule K PDSCHs, one way is to increase the number of configurable bits of CBGTI, for example, to 16, 24, and so on. Another way is to limit the value of K according to CBGTI. For example, CBGTI is K_CBG bits, then K=floor(K_CBG/N_CBG), for example, K_CBG=8 bits, N_CBG=2, then the value of K is 4, and floor means round down.

The HARQ process scheduling (indication method) corresponding to the above three K shared channels, the first device and the second device can select one of the methods according to the agreement, or can support one or more of them respectively. The method of reporting notifies the second device of the scheduling method it supports, and the second device may also notify the first device which scheduling method to select through RRC signaling configuration or physical layer signaling or MAC layer signaling.

Further, for the first message scheduling K shared channels, and the HARQ feedback information of the K shared channels, there may also be the following specific implementation methods: The following is an example of the shared channel being PDSCH for description.

One: The TB of K PDSCH uses 1 bit for feedback. ACK is fed back only when all TBs are correct, and NACK is fed back only when one TB is incorrect. This way saves feedback overhead, but the transmission efficiency is lower.

Two: Each of the K PDSCH TBs has independent HARQ ACK/NACK feedback. If a PDSCH carries one TB, and the transmission is not configured with CBG retransmission, 1 bit is used to feedback whether the TB is received correctly; if a PDSCH carries one TB, and N_CBG CBGs are configured, the N_CBG bit is used to feedback the Whether the TB is received correctly; if a PDSCH carries 2 TBs, you can configure whether the 2 TBs are bundled with ACK/NACK feedback or independent feedback. If they are bundled feedback, use 1 bit to feedback whether the 2 TBs are Correctly received, if it is independent feedback, use 2 bits to feedback whether the 2 TBs are correctly received; if a PDSCH carries 2 TBs and N_CBG CBGs are configured, according to whether the binding feedback is configured, use 2* N_CBG bits for feedback or N_CBG bits for feedback. The HARQ ACK/NACK of multiple PDSCHs is concatenated to form a total HARQ ACK/NACK feedback codebook. Figure 14 shows a schematic diagram of the HARQ ACK/NACK feedback codebook for three PDSCHs. From high-order bits to low-order bits, the order is the ACK/NACK of the first PDSCH, the ACK/NACK of the second PDSCH, and the ACK of the third PDSCH. /NACK.

When the shared channel is the PUSCH, it may be implemented with reference to the HARQ scheduling in which the shared channel is the PDSCH, and details are not repeated here. However, PUSCH does not require HARQ feedback, and the first device determines which PUSCH needs to be retransmitted according to the retransmission indication sent by the second device.

In addition, the first device and the second device can release the K HARQ processes after the S TBs carried by the K shared channels are all successfully transmitted; or the TBs carried by any one of the K shared channels can be successfully transmitted. Afterwards, the HARQ process corresponding to the shared channel successfully transmitted is released.

When the shared channel is PUSCH or PDSCH or PSSCH, for the DMRS of PUSCH or PDSCH or PSSCH, the same mapping rules can be used for the DMRS in K PDSCH or PUSCH or PSSCH, or the DMRS in different PDSCH or PUSCH or PSSCH can be Certain rules use different mapping rules. The mapping rule of PDSCH or PUSCH or PSSCH may be related to the PDSCH or PUSCH or PSSCH mapping type, the configuration position of additional DMRS, the length of PDSCH or PUSCH or PSSCH, and the length of DMRS.

As an example, Table 5 shows an example of the mapping rule when the PDSCH DMRS length is 1 symbol length. In Table 5, 1 ₀ represents the position of the first DMRS, 1 _d represents the PDSCH length, PDSCH mapping type A and mapping The meaning of type B is shown in Table 1 and Table 2 above, pos0, pos1, pos2, pos3 are used to indicate the number of extra DMRS, pos0 means no extra DMRS, pos1 means there is at most 1 extra DMRS, pos2 means there are at most 2 extra DMRS DMRS, pos3 means there are up to 3 additional DMRS. The length of one DMRS may be one symbol or two symbols. The following table shows an example of the length of the DMRS being one symbol. The DMRS length symbol of PDSCH or PUSCH is 2 symbols long, and the DMRS mapping rules of PDSCH or PUSCH at this time can be found in Section 38.211 Vg.2.06.4.1.1.3 and Section 7.4.1.1.2 of the protocol, which will not be repeated in this application. .

table 5

Taking PDSCH as an example, multiple PDSCHs use the same mapping rule, for example, the configuration of additional DMRS is 'pos2', and PDSCH mapping type A is taken as an example. At this time, l ₀ =2, the length of the first PDSCH is 12, according to In Table 5 above, the DMRS is located at symbols 2, 6, and 9, and the length of the second PDSCH is 14. According to the above table 5, the DMRS is located at symbols 2, 7, and 14, and the length of the third PDSCH is 7. According to the above table 5, DMRS is at symbol 2. As shown in Figure 15. Multiple PDSCHs adopt the same mapping rule, and the mapping rule is simple and easy to implement.

In a possible implementation, DMRSs in different PDSCHs or PUSCHs may also adopt different mapping rules according to certain rules, one of which is that the number of additional DMRSs in different PDSCHs is configured differently. For example, in the above configuration, PDSCH 1 follows pos2, and PDSCH 2 and PDSCH 3 follow pos0, as shown in Figure 16. In the case of full scheduling in the time domain, the demodulation of the following PDSCH can use the previous PDSCH DMRS for channel estimation, and the PDSCH transmitted later can use less (sparse) DMRS to save system overhead.

Another rule may be that the lengths of the DMRSs of different PDSCHs are different. As shown in Figure 17, the additional pilot configurations of the DMRS are all pos1, but the DMRS length of the first PDSCH is 2, the DMRS length of the second and third PDSCH is 1, and different PDSCHs use different DMRS configurations , the following PDSCH can use less (sparse) DMRS to save system overhead.

In another possible implementation, the DMRS in different PDSCH or PUSCH adopt different mapping rules according to certain rules, as shown in FIG. 18 , taking the shared channel as PDSCH as an example, one of the rules is different PDSCH The densities of DMRS vary. The DMRS density of the former PDSCH is higher, the DMRS density of the latter PDSCH is sparser, and the latter PDSCH can use fewer (sparse) DMRSs to save system overhead.

The density of DMRS refers to the amount of resources occupied by a DMRS in the frequency domain. Figure 19 shows a schematic diagram of different DMRS densities. As shown in FIG. 19 , the further to the right, the fewer resources (RBs) occupied by the DMRS, and the less the system overhead is.

The first message may include the DMRS configuration of one of the K shared channels, and the DMRS configurations of the other (K-1) shared channels may use the same mapping rule as the one shared channel, or the other K- The DMRS configuration of one shared channel is obtained according to a certain rule according to the DMRS configuration of the one shared channel. By adopting this method, signaling redundancy caused by multiple sets of demodulation reference signal DMRS configuration parameters is avoided.

For the MCS of the shared channel, the K shared channels may adopt the same or different MCS.

1. The K shared channels use the same MCS. Take the shared channel as PDSCH as an example. K PDSCHs use the same MCS. If 2 CWs are scheduled, then all PDSCH TBs are 2 CWs, and the first TB of each PDSCH is the same MCS, and the second TB is the same MCS. That is, the MCS/RV/NDI of the first TB of PDSCH 1 and PDSCH2 are the same, the MCS/RV/NDI of the second TB of PDSCH 1 and PDSCH 2 are the same, but the first TB and the second TB of PDSCH1 The MCS/RV/NDI can be different.

2. The K shared channels use different MCSs. Take the shared channel as PDSCH as an example. Different PDSCHs use different MCSs, for example, the MCSs of the first X PDSCHs are relatively low, and the MCSs of the last Y PDSCHs are relatively high.

The first message may include the MCS of one of the K shared channels, and the other (K-1) shared channels may use the same MCS as the one shared channel, or may be based on the MCS of the one shared channel , obtained according to certain rules. In this way, the redundancy of signaling transmission caused by multiple sets of MCS parameters is avoided.

Full scheduling (full scheduling in the time domain and/or full scheduling in the frequency domain) can improve data transmission efficiency, reduce the monitoring time and monitoring times of the PDCCH by the first device, and reduce the power consumption of the first device. In a possible implementation Among them, the first device can confirm whether to use full scheduling according to one or more of its own power, whether it is in an overheated state, service conditions, wireless resource configuration, device type, and network load conditions.

As an example, the first device may determine that it needs to save power (for example, when the current power is lower than the power threshold or the first device is in an overheated state), the amount of data to be transmitted is greater than or equal to the data amount threshold, the current bandwidth is less than the bandwidth threshold, and the When one or more of determining the device type (such as an IoT low-power terminal), determining that the second device is in a low load state, etc. are satisfied, send a full scheduling request to the second device, where the full scheduling request includes the time The domain full scheduling request, or the full scheduling request includes a time domain full scheduling request and a frequency domain full scheduling request, and is used to request the second device to perform time domain full scheduling on the first device, or to perform frequency domain full scheduling on the first device. Scheduling and time-domain full scheduling.

In another possible implementation, the second device may also be based on the power of the first device, the service situation of the first device, the wireless resource configuration of the first device, the type of the first device, and the load situation of the second device, etc. One or more items to confirm whether full scheduling is adopted for the first device, and when it is determined that full scheduling is adopted for the first device, send full scheduling indication information to the first device, where the full scheduling indication information is used to indicate that the first device is allowed to A device sends a full scheduling request message, that is, full scheduling can also be initiated by the second device.

As an example, the second device may notify the first device whether to allow the first device to send the full scheduling request through signaling. Specifically, there are the following ways:

Manner 1: The second device notifies the first device through RRC signaling, allowing the first device to send a full scheduling request. The second device may determine, on each carrier or each BWP configured for the second device, whether to allow the first device to send a full scheduling request on the carrier or the BWP. Specifically, the second device may include a message allowing the first device to send the full scheduling request in the RRC configuration signaling or the RRC reconfiguration signaling. After the first device receives the RRC configuration signaling or reconfiguration signaling, when the RRC configuration takes effect, the sending full scheduling request signaling included in the RRC configuration takes effect, and then the first device can send the full scheduling request. This configuration method has a low bit error rate, but takes a long time for signaling to take effect.

Manner 2: The second device sends the signaling of whether to allow the first device to send the full scheduling request through MAC layer signaling. Method 2 can be used in combination with method 1. For example, the second device may first configure through RRC signaling whether to allow the first device, or one or more CCs of the first device, or one or more BWPs of the first device to send a full scheduling request. However, the first device cannot send the full scheduling request after receiving the configuration signaling. Full scheduling requests can be sent. The second device may also stop allowing the first device to send the full scheduling request through MAC layer signaling. This method can overcome the problem of long delay caused by the RRC signaling taking effect.

Manner 3: The second device may further indicate whether the first device adopts full scheduling through physical layer signaling. Specifically, there are two ways:

Manner 1: In physical layer signaling such as DCI, a new bit is added to indicate whether full scheduling is adopted for scheduling the first device, and the full scheduling mode. This method of notification through physical layer signaling can quickly switch between full scheduling and non-full scheduling, but because the first device cannot confirm whether full scheduling is used when receiving control signaling, the power consumption is less saved.

Manner 2: The second device activates or deactivates full scheduling through the physical layer indication. If full scheduling is activated through physical layer signaling, the first device is instructed, and the corresponding CC or BWP adopts full scheduling in the subsequent scheduling manner. If full scheduling is deactivated through physical layer signaling, the CC or BWP corresponding to the first device is instructed not to use full scheduling in the subsequent scheduling manner. In this way, full scheduling can be quickly activated and deactivated, and the first device can know the scheduling way in advance, so that it can make preparations in advance to save power consumption.

As an example, the first device may send the full scheduling request to the network device by using physical layer signaling. For example, a new physical layer sequence or new uplink control signaling is used to send the full scheduling request. The first device may also use media access control (media access control, MAC) signaling to send the full scheduling request to the network device. For example, the first device may send the full scheduling request together with the buffer status report (buffer status report, BSR) MAC signaling to the second device, and use the reserved bits in the BSR to transmit the full scheduling request. This method only needs to change the software, and the compatibility is better. However, the delay is higher than that of signaling through the physical layer. In addition, the first device may also send the full scheduling request to the second device by using RRC layer signaling. For example, the first device may send the full scheduling request to the second device through the terminal assistance information.

In addition, different first devices have different capabilities. In order to facilitate the second device to know the full scheduling capability of the first device, the first device is fully scheduled according to the full scheduling capability information of the first device to ensure the efficiency and reliability of communication. The first device can also send capability information to the second device before sending the full scheduling request to the second device. In this embodiment of the present application, the time domain full scheduling of the first device requires the capability information sent by the first device. includes information that the first device supports full scheduling in the time domain, or includes information that the first device supports full scheduling in the time domain and information that the first device supports full scheduling in the frequency domain.

The above mainly introduces the communication method from the perspective of time-domain full scheduling, time-domain full scheduling and frequency-domain full scheduling. It can be understood that when the first device supports frequency-domain full scheduling, and sends full When the scheduling request message only includes the full frequency domain scheduling request, the second device may also perform full frequency domain scheduling on the first device.

FIG. 20 is a schematic diagram of another communication process provided by an embodiment of the application, and the process includes:

S2001: The second device sends a first message to the first device, and the first device receives the first message, where the first message includes scheduling information for scheduling a shared channel, where the frequency domain resources of the shared channel is equal to the size of the BWP where the shared channel is located.

Further, for a shared carrier without BWP configured or activated BWP, the size of the frequency domain resource of the shared channel is equal to the size of the bandwidth of the component carrier where the shared channel is located.

S2002: The first device and the second device communicate based on the shared channel.

In a possible implementation, the second device may carry scheduling information through the first message, and send the scheduling information to the first device through the first message, where the scheduling information carries the air interface transmission resources of the shared channel of the first device, For example, the air interface transmission resources of PDSCH or PUSCH are recorded, including time domain resource indication information and frequency domain indication information. As an example, the first message may be DCI. The frequency domain resource indication information is used to indicate the frequency domain resources of the shared channel, wherein the size of the frequency domain resources of the shared channel is equal to the size of the BWP where the shared channel is located; the time domain resource indication information is used to indicate the frequency domain resources of the shared channel. . For the implementation of the frequency domain resource indication information and the time domain resource indication information when the frequency domain is fully scheduled, reference may be made to the implementation in the embodiment shown in FIG. 5 above. The difference is that the frequency domain resource indication information in this embodiment is used to indicate The frequency domain resource of the shared channel is equal to the size of the BWP where the shared channel is located, and/or the frequency domain resource of the shared channel indicated by the frequency domain resource indication information is equal to the size of the component carrier where the shared channel is located, and the time domain resource indication information only indicates a shared channel.

In this embodiment, the frequency domain resource indication information may include a BWP identifier indicating the BWP where the shared channel is located, and/or a carrier identifier indicating the component carrier where the shared channel is located, but does not include the prior art used to indicate that the shared channel is located in the BWP and/or The frequency domain resource indication field of the frequency domain resource in the component carrier. The frequency domain resource indication field in the prior art can be cancelled and not transmitted, or reused to transmit other messages. For example, when both frequency domain full scheduling and time domain full scheduling are used at the same time, the frequency domain resource indication in the prior art can be reused. domain to transmit HARQ information of multiple shared channels, as shown in Figure 13.

In addition, similar to the time-domain full scheduling shown in FIG. 5 , the first device may also be based on one or more of its own power, its own state, service status, wireless resource configuration, device type, network load, etc. item to confirm whether to trigger full scheduling in the frequency domain.

As an example, the first device may determine that it needs to save power (for example, when the current power is lower than the power threshold or when the first device is in an overheating state), the amount of data to be transmitted is greater than or equal to the data amount threshold, the current bandwidth is less than the bandwidth threshold, and the When one or more of setting the device type (such as an IoT low-power terminal), determining that the second device is in a low load state, etc. are satisfied, send a full scheduling request to the second device, where the full scheduling request includes The request for full frequency domain scheduling, which is used to request the second device to perform full frequency domain scheduling on the first device.

Further, the full scheduling request further includes a scheduling bandwidth (Preferred BW) suggested by the first device, and/or a suggested scheduling BWP (preferred BWP), and/or a suggested scheduling component carrier (preferred CC). In this way, the first device can suggest an appropriate bandwidth to the second device to better meet the low power consumption requirement of the second device. The suggested scheduling bandwidth, and/or the suggested scheduling BWP, and/or the suggested scheduling component carrier here refers to the scheduling assistance information provided by the first device for the second device. The first device expects the second device to follow the information provided by the terminal. Scheduling auxiliary information for scheduling.

In another possible implementation, the second device may also be based on the power of the first device, the service situation of the first device, the wireless resource configuration of the first device, the type of the first device, and the load situation of the second device, etc. One or more items to confirm whether full scheduling is adopted for the first device, and when it is determined that full scheduling is adopted for the first device, send full scheduling indication information to the first device, where the full scheduling indication information is used to indicate that the first device is allowed to A device sends a full scheduling request message, that is, full scheduling can also be initiated by the second device.

Similarly, in order to facilitate the second device to know whether the first device supports full scheduling in the frequency domain, the first device is fully scheduled according to the full scheduling capability information of the first device to ensure the reliability of communication. Before the second device sends the full scheduling request, it may also send capability information to the second device. In this embodiment of the present application, to perform full scheduling in the frequency domain for the first device, the capability information that needs to be sent by the first device includes that the first device supports the frequency domain Full scheduling information.

In addition, it should be understood that when the second device performs full scheduling (full scheduling in the time domain and/or full scheduling in the frequency domain) for the first device, it may only perform full scheduling in the time domain and full scheduling in the frequency domain on the downlink (PDSCH) of the first device. One or more of the full scheduling, or only one or more of the time-domain full scheduling and the frequency-domain full scheduling can be performed on the uplink (PUSCH) of the first device, and the uplink (PUSCH) of the first device can also be performed at the same time. PUSCH) and downlink (PDSCH) to perform one or more of time-domain full scheduling and frequency-domain full scheduling. Specifically, when a certain full scheduling is performed, it is only required that the first device has a corresponding full scheduling capability. For example, to perform full time-domain scheduling on downlink (PDSCH), it is only required that the first device has the capability of full downlink (PDSCH) time-domain scheduling.

The above is mainly from the architecture shown in FIG. 1, mainly for full scheduling of PDSCH or PUSCH. It can be understood that for the architecture shown in FIG. ) carrying out full scheduling in time domain and/or frequency domain, and carrying out full scheduling in time domain or frequency domain to the side row (PSSCH) can refer to the above-mentioned realization of carrying out full scheduling in time domain and/or frequency domain to PDSCH or PUSCH. No longer.

The solution provided by the present application has been introduced above mainly from the perspective of interaction between the second device and the first device. It can be understood that, in order to realize the above functions, each network element includes a corresponding hardware structure and/or software module (or unit) for performing each function. Those skilled in the art should easily realize that the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

FIG. 21 and FIG. 22 are schematic structural diagrams of possible communication apparatuses provided by embodiments of the present application. These communication apparatuses can be used to implement the functions of the first device or the second device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments. In the embodiment of the present application, the communication apparatus may be the first device in FIG. 5 or FIG. 20 , or may be the second device in FIG. 5 or FIG. 20 , or may be applied to the first device or the second device modules (such as chips).

As shown in Figure 21. The communication apparatus 2100 may include: a processing unit 2102 and a transceiver unit 2103, and may further include a storage unit 2101. The communication apparatus 2100 is configured to implement the function of the first device or the second device in the method embodiment shown in FIG. 5 or FIG. 20 above.

In a possible design, the processing unit 2102 is used to implement corresponding processing functions. The transceiver unit 2103 is used to support the communication between the communication device 2100 and other network entities. The storage unit 2101 is used to store program codes and/or data of the communication device 2100 . Optionally, the transceiving unit 2103 may include a receiving unit and/or a sending unit, which are respectively configured to perform receiving and sending operations.

When the communication apparatus 2100 is used to implement the function of the first device in the method embodiment shown in FIG. 5 or FIG. 20 : the transceiver unit 2103 is configured to receive a first message from the second device, where the first message includes scheduling information , for scheduling a shared channel, wherein the size of the frequency domain resource of the shared channel is equal to the size of the bandwidth part BWP where the shared channel is located;

The processing unit 2102 is configured to use the transceiver unit 2103 to communicate with the second device based on the shared channel.

In a possible design, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

In a possible design, the transceiver unit 2103 is further configured to send capability information to the second device, where the capability information includes information supporting full scheduling in the frequency domain, where the full scheduling in the frequency domain is scheduling The size of the frequency domain resource of the shared channel scheduled by the information is equal to the size of the BWP where the shared channel is located.

In a possible design, the transceiver unit 2103 is further configured to send a full scheduling request message to the second device, where the full scheduling request message includes a request for full scheduling in the frequency domain. Wherein, the full scheduling request message may further include one or more of the scheduling bandwidth suggested by the first device, the suggested scheduling BWP, and the suggested scheduling component carrier.

In a possible design, the transceiver unit 2103 is further configured to receive full scheduling indication information from the second device before sending the full scheduling request message to the second device, where the full scheduling indication information is used to indicate Allow full scheduling request messages to be sent.

In another possible implementation, the transceiver unit 2103 is configured to receive a first message from the second device, where the first message includes scheduling information and is used to schedule K shared channels, where the K shared channels are mapped to K time slots for carrying S different transport blocks TB, where K is a positive integer greater than or equal to 2, and S is a positive integer greater than or equal to the K;

The processing unit 2102 is configured to use the transceiver unit 2103 to communicate with the second device based on the K shared channels.

In a possible design, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

In a possible design, the scheduling information includes time-domain resource indication information; wherein the time-domain resource indication information is used to indicate K consecutive time slots in the time domain that can be used for mapping the shared channel; or , the time domain resource indication information is used to indicate M consecutive time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and the M is greater than or equal to all A positive integer of K.

In a possible design, if the shared channel is a physical downlink shared channel PDSCH, the time slot available for mapping the shared channel is a downlink time slot; if the shared channel is a physical uplink shared channel PUSCH, all The time slot that can be used to map the shared channel is an uplink time slot; if the shared channel is a physical side channel PSSCH, the time slot that can be used to map the shared channel is a side channel time slot.

In a possible design, the processing unit 2102 is further configured to determine a time slot including a number of downlink symbols greater than or equal to a first number threshold as a downlink time slot; and/or, to include a number of uplink symbols greater than or equal to a second number of time slots The timeslots with the threshold quantity are determined as uplink timeslots; and/or, the timeslots including the number of side row symbols greater than or equal to the third quantity threshold are determined as side row timeslots.

In a possible design, the first message further includes hybrid automatic repeat request HARQ process indication information, where the HARQ process indication information is used to indicate one HARQ process corresponding to the K shared channels, or used for Indicates K HARQ processes one-to-one corresponding to the K shared channels.

In a possible design, the HARQ process indication information includes a HARQ process ID; the HARQ process ID is used to indicate a HARQ process corresponding to the K shared channels; or, the HARQ process ID is used to indicate K consecutive HARQ processes starting with the HARQ process corresponding to the HARQ process number are in one-to-one correspondence with the K shared channels; or, the HARQ process number is used to indicate the HARQ process corresponding to the HARQ process number. The initial K idle HARQ processes are in one-to-one correspondence with the K shared channels.

In a possible design, the processing unit 2102 is further configured to release the K HARQ processes after the S TBs carried by the K shared channels are all successfully transmitted; or, when it is determined that the K HARQ processes are After the TB carried by any shared channel in the shared channel is successfully transmitted, the HARQ process corresponding to the shared channel that is successfully transmitted is released.

In a possible design, the demodulation reference signal DMRSs in the K shared channels use the same mapping rule; or, the DMRSs in the K shared channels use different mapping rules according to the mapping rule determination method.

In a possible design, the K shared channels use the same or different modulation and coding modes MCS.

In a possible design, the scheduling information includes frequency domain resource indication information, where the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels, wherein the frequency domain of the K shared channels The size of the resource is less than or equal to the size of the bandwidth part BWP where the K shared channels are located.

In a possible design, the transceiver unit 2103 is further configured to send capability information to the second device, where the capability information includes information about supporting time-domain full scheduling, or the capability information includes supporting time-domain full scheduling Scheduling information and information supporting frequency-domain full scheduling, wherein the time-domain full scheduling is the scheduling information to schedule multiple shared channels, and the frequency-domain full scheduling is that the size of the frequency domain resources of the shared channel scheduled by the scheduling information is equal to all The size of the BWP where the shared channel is located.

In a possible design, the transceiver unit 2103 is further configured to send a full scheduling request message to the second device, where the full scheduling request message includes a time domain full scheduling request, or the full scheduling request message includes Time domain full scheduling request and frequency domain full scheduling request.

In a possible design, the transceiver unit 2103 is further configured to receive full scheduling indication information from the second device before sending the full scheduling request message to the second device, where the full scheduling indication information is used to indicate Allow full scheduling request messages to be sent.

When the communication apparatus 2100 is used to implement the function of the second device in the method embodiment shown in FIG. 5 or FIG. 20:

Transceiver unit 2103, configured to send a first message to the first device, where the first message includes scheduling information for scheduling a shared channel, where the size of the frequency domain resource of the shared channel is equal to the bandwidth part where the shared channel is located The size of the BWP.

The processing unit 2102 is configured to communicate with the first device based on the shared channel through the transceiver unit 2103.

In a possible design, the transceiver unit 2103 is further configured to receive capability information from the first device, where the capability information includes information that the first device supports full frequency-domain scheduling, wherein the The frequency domain full scheduling is that the size of the frequency domain resource of the shared channel scheduled by the scheduling information is equal to the size of the BWP where the shared channel is located.

In a possible design, the transceiver unit 2103 is further configured to receive a full scheduling request message sent by the first device, where the full scheduling request message includes a request for full scheduling in the frequency domain.

In a possible design, before receiving the full scheduling request message sent by the first device, the transceiver unit 2103 is further configured to send the full scheduling indication information to the first device by the second device, the The full scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

In another possible implementation, the transceiver unit 2103 is configured to send a first message to the first device, where the first message includes scheduling information for scheduling K shared channels, where the K shared channels are mapped to K time slots for carrying S different transport blocks TB, the K is a positive integer greater than or equal to 2, and the S is a positive integer greater than or equal to the K;

The processing unit 2102 is configured to use the transceiver unit 2103 to communicate with the first device based on the K shared channels.

In a possible design, the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH.

In a possible design, the scheduling information includes time-domain resource indication information; wherein the time-domain resource indication information is used to indicate K consecutive time slots in the time domain that can be used for mapping the shared channel; or , the time domain resource indication information is used to indicate M consecutive time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and the M is greater than or equal to all A positive integer of K.

In a possible design, if the shared channel is a physical downlink shared channel PDSCH, the time slot available for mapping the shared channel is a downlink time slot; if the shared channel is a physical uplink shared channel PUSCH, all The time slot that can be used to map the shared channel is an uplink time slot; if the shared channel is a physical side channel PSSCH, the time slot that can be used to map the shared channel is a side channel time slot.

In a possible design, the processing unit 2102 is further configured to release the K HARQ processes after the S TBs carried by the K shared channels are all successfully transmitted; or, when it is determined that the K HARQ processes are After the TB carried by any shared channel in the shared channel is successfully transmitted, the HARQ process corresponding to the shared channel that is successfully transmitted is released.

In a possible design, the demodulation reference signal DMRSs in the K shared channels use the same mapping rule; or, the DMRSs in the K shared channels use different mapping rules according to the mapping rule determination method.

In a possible design, the K shared channels use the same or different modulation and coding modes MCS.

In a possible design, the scheduling information includes frequency domain resource indication information, where the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels, wherein the frequency domain of the K shared channels The size of the resource is less than or equal to the size of the bandwidth part BWP where the K shared channels are located.

In a possible design, the transceiver unit 2103 is further configured to receive capability information from the first device, where the capability information includes information that the first device supports full time-domain scheduling, or the capability The information includes information that the first device supports full scheduling in the time domain and information that the first device supports full scheduling in the frequency domain, wherein the full scheduling in the time domain is scheduling information to schedule multiple shared channels, and the full scheduling in the frequency domain The size of the frequency domain resource of the shared channel scheduled for scheduling information is equal to the size of the BWP where the shared channel is located.

In a possible design, the transceiver unit 2103 is further configured to receive a full scheduling request message sent by the first device, where the full scheduling request message includes a time domain full scheduling request, or the full scheduling request message Including full scheduling requests in the time domain and requests for full scheduling in the frequency domain.

In a possible design, before receiving the full scheduling request message sent by the first device, the transceiver unit 2103 is further configured to send the full scheduling indication information to the first device by the second device, the The full scheduling indication information is used to indicate that the first device is allowed to send a full scheduling request message.

More detailed descriptions about the above-mentioned processing unit 2102 and the transceiver unit 2103 can be obtained directly by referring to the relevant descriptions in the method embodiments shown in FIG. 5 or FIG. 20 , and details are not repeated here.

As shown in FIG. 22 , the communication apparatus 2200 includes a processor 2210 and an interface circuit 2220 . The processor 2210 and the interface circuit 2220 are coupled to each other. It can be understood that the interface circuit 2220 can be a transceiver or an input-output interface. Optionally, the communication apparatus 2200 may further include a memory 2230 for storing instructions executed by the processor 2210 or input data required by the processor 2210 to execute the instructions or data generated after the processor 2210 executes the instructions.

When the communication apparatus 2200 is used to implement the method shown in FIG. 5 or FIG. 20 , the processor 2210 is used to implement the function of the above-mentioned processing unit 2102 , and the interface circuit 2220 is used to implement the function of the above-mentioned transceiver unit 2103 .

As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed, the communication methods applicable to the first device or the second device in the above method embodiments can be executed.

As another form of this embodiment, a computer program product containing an instruction is provided, and when the instruction is executed, the communication method applicable to the first device or the second device in the above method embodiment can be executed.

As another form of this embodiment, a chip is provided, and when the chip is running, the communication method applicable to the first device or the second device in the above method embodiments can be executed.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

While the preferred embodiments of the present application have been described, additional changes and modifications to these embodiments may occur to those skilled in the art once the basic inventive concepts are known. Therefore, the appended claims are intended to be construed to include the preferred embodiment and all changes and modifications that fall within the scope of this application.

Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (30)

A communication method, comprising: The first device receives a first message from the second device, where the first message includes scheduling information for scheduling a shared channel, wherein the size of the frequency domain resources of the shared channel is equal to the size of the bandwidth part BWP where the shared channel is located. size; The first device communicates with the second device based on the shared channel. The method of claim 1, wherein the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH. A communication method, comprising: The first device receives a first message from the second device, the first message includes scheduling information for scheduling K shared channels, where the K shared channels are mapped to K time slots for carrying S different The transport block TB, the K is a positive integer greater than or equal to 2, and the S is a positive integer greater than or equal to the K; The first device communicates with the second device based on the K shared channels. The method of claim 3, wherein the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH. The method according to claim 3 or 4, wherein the scheduling information includes time-domain resource indication information; wherein the time-domain resource indication information is used to indicate that consecutive K in time domain can be used for mapping the a time slot of a shared channel; or, The time domain resource indication information is used to indicate consecutive M time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and M is greater than or equal to the A positive integer of K. The method according to claim 5, wherein if the shared channel is a physical downlink shared channel (PDSCH), the time slot available for mapping the shared channel is a downlink time slot; If the shared channel is a physical uplink shared channel PUSCH, the time slot that can be used to map the shared channel is an uplink time slot; If the shared channel is a physical side channel PSSCH, the time slot available for mapping the shared channel is a side channel time slot. The method of claim 5 or 6, wherein the method further comprises: The first device determines a time slot including a number of downlink symbols greater than or equal to a first number threshold as a downlink time slot; and/or, The first device determines a time slot including a number of uplink symbols greater than or equal to a second number threshold as an uplink time slot; and/or, The first device determines a time slot including a number of side row symbols greater than or equal to a third number threshold as a side row time slot. The method according to any one of claims 3-7, wherein the first message further includes HARQ process indication information of hybrid automatic repeat request, and the HARQ process indication information is used to indicate the K One HARQ process corresponding to the shared channel, or used to indicate K HARQ processes corresponding to the K shared channels one-to-one. The method of claim 8, wherein the HARQ process indication information includes a HARQ process number; The HARQ process number is used to indicate a HARQ process corresponding to the K shared channels; or, The HARQ process number is used to indicate that the K continuous HARQ processes starting with the HARQ process corresponding to the HARQ process number are in one-to-one correspondence with the K shared channels; or, The HARQ process ID is used to indicate that the K idle HARQ processes starting with the HARQ process corresponding to the HARQ process ID are in one-to-one correspondence with the K shared channels. The method of claim 8 or 9, wherein the method further comprises: After the S TBs carried by the K shared channels are all successfully transmitted, the first device releases the K HARQ processes; or, After the first device determines that the transmission of the TB carried by any one of the K shared channels is successful, the first device releases the HARQ process corresponding to the shared channel that is successfully transmitted. The method according to any one of claims 3-10, wherein the demodulation reference signal DMRS in the K shared channels adopts the same mapping rule; or, The DMRSs in the K shared channels adopt different mapping rules according to the way of determining the mapping rules. The method according to any one of claims 3-11, wherein the K shared channels use the same or different modulation and coding modes MCS. The method according to any one of claims 3-12, wherein the scheduling information includes frequency domain resource indication information, and the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels , wherein the size of the frequency domain resources of the K shared channels is less than or equal to the size of the bandwidth part BWP where the K shared channels are located. A communication method, comprising: The second device sends a first message to the first device, where the first message includes scheduling information for scheduling a shared channel, where the size of the frequency domain resource of the shared channel is equal to the size of the bandwidth part BWP where the shared channel is located ; The second device communicates with the first device based on the shared channel. The method of claim 14, wherein the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH. A communication method, comprising: The second device sends a first message to the first device, where the first message includes scheduling information for scheduling K shared channels, where the K shared channels are mapped to K time slots for carrying S different transport block TB, the K is a positive integer greater than or equal to 2, and the S is a positive integer greater than or equal to the K; The second device communicates with the first device based on the K shared channels. The method of claim 16, wherein the shared channel is a physical downlink shared channel PDSCH or a physical uplink shared channel PUSCH or a physical side channel PSSCH. The method according to claim 16 or 17, wherein the scheduling information comprises time-domain resource indication information; wherein the time-domain resource indication information is used to indicate that consecutive K in time domain can be used for mapping the a time slot of a shared channel; or, The time domain resource indication information is used to indicate consecutive M time slots in the time domain, wherein the M time slots include K time slots that can be used to map the shared channel, and M is greater than or equal to the A positive integer of K. The method of claim 18, wherein if the shared channel is a physical downlink shared channel (PDSCH), the time slot available for mapping the shared channel is a downlink time slot; If the shared channel is a physical uplink shared channel PUSCH, the time slot that can be used to map the shared channel is an uplink time slot; If the shared channel is a physical side channel PSSCH, the time slot available for mapping the shared channel is a side channel time slot. The method of claim 18 or 19, wherein the method further comprises: The second device determines a time slot including a number of downlink symbols greater than or equal to the first number threshold as a downlink time slot; and/or, The second device determines a time slot including a number of uplink symbols greater than or equal to a second number threshold as an uplink time slot; and/or, The second device determines a time slot including a number of side row symbols greater than or equal to a third number threshold as a side row time slot. The method according to any one of claims 16-20, wherein the first message further includes HARQ process indication information of hybrid automatic repeat request, where the HARQ process indication information is used to indicate the K One HARQ process corresponding to the shared channel, or used to indicate K HARQ processes corresponding to the K shared channels one-to-one. The method of claim 21, wherein the HARQ process indication information includes a HARQ process number; The HARQ process number is used to indicate a HARQ process corresponding to the K shared channels; or, The HARQ process number is used to indicate that K consecutive HARQ processes starting with the HARQ process corresponding to the HARQ process number are in one-to-one correspondence with the K shared channels; or, The HARQ process ID is used to indicate that the K idle HARQ processes starting with the HARQ process corresponding to the HARQ process ID are in one-to-one correspondence with the K shared channels. The method of claim 21 or 22, wherein the method further comprises: After the S TBs carried by the K shared channels are all successfully transmitted, the second device releases the K HARQ processes; or, After the second device determines that the transmission of the TB carried by any one of the K shared channels is successful, the second device releases the HARQ process corresponding to the shared channel that is successfully transmitted. The method according to any one of claims 16-23, wherein the demodulation reference signal DMRS in the K shared channels adopts the same mapping rule; or, The DMRSs in the K shared channels adopt different mapping rules according to the way of determining the mapping rules. The method according to any one of claims 16-24, wherein the K shared channels use the same or different modulation and coding modes MCS. The method according to any one of claims 16-25, wherein the scheduling information includes frequency domain resource indication information, and the frequency domain resource indication information is used to indicate frequency domain resources of the K shared channels , wherein the size of the frequency domain resources of the K shared channels is less than or equal to the size of the bandwidth part BWP where the K shared channels are located. A communication device, characterized in that the device comprises a unit for performing the method according to claim 1 or 2, or a unit for performing the method according to any one of claims 3-13, or Comprising means for performing a method as claimed in claim 14 or 15, or comprising means for performing a method as claimed in any of claims 16-26. A computer-readable storage medium, characterized in that, a computer program or instruction is stored in the storage medium, and when the computer program or instruction is executed by a communication device, the method according to claim 1 or 2 is implemented, or A method as claimed in any of claims 3-13 is implemented, or a method as claimed in claim 14 or 15 is implemented, or a method as claimed in any of claims 16-26 is implemented. A chip, characterized in that, when the chip is running, the method according to claim 1 or 2, the method according to any one of claims 3-13, or the method according to claim 14 or claim 14 is realized or realized. 15, or implementing the method of any of claims 16-26. A communication system, characterized in that the system comprises a first device for performing the method as claimed in claim 1 or 2 and a second device for performing the method as claimed in claim 14 or 15; A first device for performing the method according to any one of claims 3-13 and a second device for performing the method according to any one of claims 16-26.

Images