CN115379571A

CN115379571A - Resource indication method and related equipment

Info

Publication number: CN115379571A
Application number: CN202110555623.5A
Authority: CN
Inventors: 罗之虎; 金哲; 侯海龙; 曲韦霖
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-05-21
Filing date: 2021-05-21
Publication date: 2022-11-22
Also published as: WO2022242474A1

Abstract

The embodiment of the application discloses a resource indication method and related equipment, wherein the method comprises the following steps: the method comprises the steps that a network device sends configuration information to a terminal device, wherein the configuration information is used for configuring a plurality of partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP in the plurality of BWPs; sending Downlink Control Information (DCI) to the terminal equipment, wherein the DCI comprises scheduling information and indication information, the scheduling information is used for scheduling the transmission of a Physical Downlink Shared Channel (PDSCH) or/and a Physical Uplink Shared Channel (PUSCH), and the indication information is used for determining whether rate matching resources on the plurality of BWPs can be used during the transmission of the PDSCH or/and the PUSCH. By adopting the embodiment of the application, the transmission performance of the PDSCH or PUSCH is ensured, and the transmission efficiency of the service on the rate matching resource is improved.

Description

Resource indication method and related equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a resource indication method and related device.

Background

A bandwidth part (BWP) is a new concept proposed in the New Radio (NR) standard, and is a continuous bandwidth resource configured by a network device to a User Equipment (UE), so that flexible transmission bandwidth configuration can be implemented at the network device and the UE side. In addition, currently, only a Physical Downlink Shared Channel (PDSCH) supports rate matching, where rate matching refers to that a resource that cannot be used is avoided during PDSCH resource mapping, and mapping is performed only on an available resource. For low-capability (redcp) UEs, a PDSCH and/or Physical Uplink Shared Channel (PUSCH) transmission may span multiple BWPs or frequency locations at a time, but some of the resources require transmission of data, control signals, or reference signals for non-low-capability (non-redcp) UEs, so PDSCH or PUSCH performance cannot be guaranteed and traffic on rate-matched resources is affected.

Disclosure of Invention

The embodiment of the application provides a resource indication method and related equipment, which can guarantee the transmission performance of a PDSCH (physical Downlink shared channel) or a PUSCH (physical uplink shared channel) and improve the transmission efficiency of services on rate matching resources.

In a first aspect, an embodiment of the present application provides a resource indication method, including: the method comprises the steps that a network device sends configuration information to a terminal device, wherein the configuration information is used for configuring a plurality of partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP in the plurality of BWPs; sending Downlink Control Information (DCI) to the terminal equipment, wherein the DCI comprises scheduling information and indication information, the scheduling information is used for scheduling the transmission of a Physical Downlink Shared Channel (PDSCH) or/and a Physical Uplink Shared Channel (PUSCH), and the indication information is used for determining whether rate matching resources on the plurality of BWPs can be used during the transmission of the PDSCH or/and the PUSCH. Under the coexistence condition of the REDCAP terminal device and the non-REDCAP terminal device, whether the REDCAP terminal device can use the rate matching resources on a plurality of BWPs during the transmission of the PDSCH or/and the PUSCH is informed, so that the transmission performance of the PDSCH or the PUSCH is guaranteed, the service on the rate matching resources is prevented from being influenced, and the transmission efficiency of the service on the rate matching resources is improved.

In one possible design, the at least one rate-matching resource on each BWP is independently grouped into at least one group of rate-matching resources, the group of rate-matching resources on the BWPs is divided into at least one association, and the indication information is used to determine whether each of the at least one association can be used during the PDSCH or/and PUSCH transmission. By indicating whether each association group can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is guaranteed, and the transmission efficiency of services on rate matching resources is improved.

In another possible design, the indication information includes a plurality of bits, one bit corresponds to one association group, the number of the plurality of bits is smaller than the number of groups of the rate matching resource groups on the plurality of BWPs, and one bit corresponds to one association group, so as to reduce the overhead of DCI.

In another possible design, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the indication information is used to determine whether each rate matching resource group on the plurality of BWPs can be used during the PDSCH or/and PUSCH transmission. By indicating whether each rate matching resource group can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is guaranteed, and the transmission efficiency of services on the rate matching resources is improved.

In another possible design, the indication information includes a plurality of bits, one bit corresponds to one of the rate-matching resource groups, and the number of the plurality of bits is equal to the number of groups of the rate-matching resource groups on the BWPs.

In another possible design, all rate matching resources on the plurality of BWPs are jointly grouped into at least one rate matching resource group, and the indication information is used to determine whether each of the at least one rate matching resource group can be used during the PDSCH or/and PUSCH transmission. By indicating whether each rate matching resource group can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is guaranteed, and the transmission efficiency of services on the rate matching resources is improved.

In another possible design, the indication information includes a plurality of bits, one bit corresponding to one of the rate matching resource groups, and a number of the plurality of bits is equal to a number of the at least one rate matching resource group. By joint grouping, the overhead of DCI can be reduced.

In another possible design, the BWPs correspond to different identifiers, the starting positions of the resource blocks RB of the BWPs are different, or the BWPs correspond to the same identifier and the starting positions of the resource blocks RB of the BWPs are different.

In another possible design, the first BWP and the second BWP are two BWPs of the plurality of BWPs, and the parameters of the first BWP and the second BWP are the same and include at least one of: bandwidth, subcarrier interval, port number corresponding to sounding reference signal SRS, and maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

In another possible design, the subcarrier spacing of the rate-matched resources on the multiple BWPs is the same.

In another possible design, the rate matching resource is a resource block RB or symbol level rate matching resource, or the rate matching resource is a resource element RE level rate matching resource.

In another possible design, the terminal device is a low-power terminal device.

In a second aspect, an embodiment of the present application provides a resource indication method, including: the method comprises the steps that a terminal device receives configuration information from a network device, wherein the configuration information is used for configuring a plurality of partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP in the plurality of BWPs; receiving Downlink Control Information (DCI) from the network device, the DCI comprising scheduling information and indication information, the scheduling information being used for scheduling transmission of a Physical Downlink Shared Channel (PDSCH) or/and a Physical Uplink Shared Channel (PUSCH), the indication information being used for determining whether the rate matching resources on the plurality of BWPs can be used during transmission of the PDSCH or/and the PUSCH. By informing the REDCAP terminal device whether the rate matching resources on a plurality of BWPs can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is ensured, the influence on the service performed on the rate matching resources is avoided, and the transmission efficiency of the service performed on the rate matching resources is improved.

In one possible design, the at least one rate-matching resource on each BWP is independently grouped into at least one group of rate-matching resources, the group of rate-matching resources on the BWPs is divided into at least one association, and the indication information is used to determine whether each of the at least one association can be used during the PDSCH or/and PUSCH transmission. By indicating whether each association group can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is ensured, and the transmission efficiency of services on rate matching resources is improved.

In another possible design, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the indication information is used to determine whether each rate matching resource group on the plurality of BWPs can be used during the PDSCH or/and the PUSCH transmission. By indicating whether each rate matching resource group can be used during the transmission of the PDSCH or/and the PUSCH, the transmission performance of the PDSCH or the PUSCH is guaranteed, and the transmission efficiency of services on the rate matching resources is improved.

In another possible design, all rate matching resources on the plurality of BWPs are jointly grouped into at least one rate matching resource group, and the indication information is used to determine whether each of the at least one rate matching resource group can be used during the PDSCH or/and PUSCH transmission. The transmission performance of the PDSCH or the PUSCH is ensured by indicating whether each rate matching resource group can be used during the transmission of the PDSCH or/and the PUSCH, and the transmission efficiency of services on the rate matching resources is improved.

In another possible design, the indication information includes a plurality of bits, one bit corresponds to one of the rate matching resource sets, and the number of the plurality of bits is equal to the number of sets of the at least one rate matching resource set. By joint grouping, the overhead of DCI can be reduced.

In another possible design, the first BWP and the second BWP are two BWPs of the plurality of BWPs, and the parameters of the first BWP and the second BWP are the same and include at least one of: bandwidth, subcarrier spacing, the number of ports corresponding to sounding reference signals SRS, and the maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

In another possible design, the terminal device is a low-power terminal device.

In a third aspect, an embodiment of the present application provides a resource indication method, including: configuring, by a network device, a first active partial bandwidth BWP set identifier and a first active BWP identifier, where the first active BWP set identifier is associated with a BWP set, and the BWP set includes multiple BWPs, and the first active BWP identifier is associated with one BWP in the BWP set; the network device sends configuration information to a terminal device, wherein the configuration information comprises the first active BWP set identifier and the first active BWP identifier, the first active BWP set identifier is used for indicating the active BWP set after performing RRC configuration or RRC reconfiguration, and the first active BWP identifier is used for indicating the active BWP in the BWP set after performing RRC configuration or RRC reconfiguration. The first activation BWP set identifier indicates that one BWP set of the multiple BWP sets is activated after RRC configuration or RRC reconfiguration is performed, and the first activation BWP set identifier indicates that one BWP set of the BWP sets is activated after RRC configuration or RRC reconfiguration is performed, so that the terminal device can determine a frequency domain location of downlink or uplink communication with the network device, thereby improving communication efficiency.

In a fourth aspect, an embodiment of the present application provides a resource indication method, including: the method comprises the steps that a terminal device receives configuration information sent by a network device, wherein the configuration information comprises a first active BWP set identification and a first active BWP identification, the first active BWP set identification is associated with one BWP set, the BWP set comprises a plurality of BWPs, and the first active BWP identification is associated with one BWP in the BWP set. And the terminal equipment activates the BWP set according to the first activation BWP set identification, and activates the BWP in the BWP set according to the first activation BWP identification. The first activation BWP set identifier indicates that one BWP set of the multiple BWP sets is activated after RRC configuration or RRC reconfiguration is performed, and the first activation BWP set identifier indicates that one BWP set of the BWP sets is activated after RRC configuration or RRC reconfiguration is performed, so that the terminal device can determine a frequency domain location of downlink or uplink communication with the network device, thereby improving communication efficiency.

In a fifth aspect, an embodiment of the present application provides a resource indication method, including: the network device configures a first active BWP ID and a starting RB position ID of the first BWP, wherein the first active BWP ID is associated with one BWP, and the starting RB position ID of the first BWP is associated with a starting RB position of one BWP. And the network equipment sends configuration information to the terminal equipment, wherein the configuration information comprises a first activation BWP identifier and a start RB position identifier of the first BWP, the first activation BWP identifier is used for indicating that the BWP is activated after RRC configuration or RRC reconfiguration is performed, and the start RB position identifier of the first BWP is used for indicating that the start RB position of the BWP is activated after the RRC configuration or the RRC reconfiguration is performed.

The first active BWP identification indicates to activate the BWP after RRC configuration or RRC reconfiguration is performed, and the starting RB position of the BWP after the RRC configuration or RRC reconfiguration is indicated through the starting RB position identification of the first BWP, so that the terminal device can determine the frequency domain position of downlink or uplink communication with the network device, and the communication efficiency is improved.

In a sixth aspect, an embodiment of the present application provides a resource indication method, including: the terminal device receives configuration information sent by the network device, wherein the configuration information comprises a first active BWP identifier and a start RB position identifier of a first BWP, the first active BWP identifier is associated with one BWP, and the start RB position identifier of the first BWP is associated with a start RB position of one BWP. And the terminal equipment activates the BWP after performing RRC configuration or RRC reconfiguration according to the first activation BWP identifier, and activates the starting RB position of the BWP after performing RRC configuration or RRC reconfiguration according to the starting RB position identifier of the first BWP.

The first activation BWP identification indicates that the BWP is activated after RRC configuration or RRC reconfiguration is performed, and the starting RB position of the BWP after the RRC configuration or the RRC reconfiguration is indicated through the starting RB position identification of the first BWP, so that the terminal device can determine the frequency domain position of downlink or uplink communication with the network device, and the communication efficiency is improved.

In a seventh aspect, an embodiment of the present application provides a resource indication method, including: the network device configures a default BWP set identifier associated with a BWP set, where the BWP set includes a plurality of BWPs, and configures a default BWP identifier associated with a BWP in the BWP set. The network device sends configuration information to a terminal device, wherein the configuration information comprises the BWP set identification and the default BWP identification, the default BWP set identification is used for indicating that the BWP set is used after a BWP inactivity timer is overtime, and the default BWP identification is used for indicating that the BWP in the BWP set is used after the BWP inactivity timer is overtime.

And indicating to use the BWP set after the BWP inactivity timer expires through the default BWP set identifier, and indicating to use the BWP in the BWP set after the BWP inactivity timer expires through the default BWP set identifier, so that the terminal device can determine a frequency domain position for downlink or uplink communication with the network device, thereby improving the efficiency of communication.

In an eighth aspect, an embodiment of the present application provides a resource indication method, including: the method comprises the steps that a terminal device receives configuration information sent by a network device, wherein the configuration information comprises a default BWP set identification and a default BWP identification, the default BWP set identification is associated with a BWP set, the BWP set comprises a plurality of BWPs, and the default BWP identification is associated with one BWP in the BWP set. The terminal device uses the BWP set after the BWP inactivity timer is overtime according to the default BWP set identification, and uses the BWP in the BWP set after the BWP inactivity timer is overtime according to the default BWP identification.

Indicating, by the default BWP set identification, to use the BWP set after the BWP inactivity timer expires and indicating, by the default BWP identification, to use the BWP in the BWP set after the BWP inactivity timer expires, so that the terminal device can determine the frequency domain location of the downlink or uplink communication with the network device, thereby improving the efficiency of the communication.

In a ninth aspect, an embodiment of the present application provides a resource indication method, including: the network device configures a default BWP identification and a default BWP start RB position identification, wherein the default BWP identification is associated with a BWP, and the default BWP start RB position identification is associated with the default start RB position of the BWP. The network device sends configuration information to a terminal device, wherein the configuration information comprises the default BWP identification and a starting RB position identification of the default BWP, the default BWP identification is used for indicating that the BWP is used after a BWP inactivity timer is overtime, and the starting RB position identification of the default BWP is used for indicating that the default starting RB position of the BWP is used after the BWP inactivity timer is overtime.

Indicating, by the default BWP flag, that BWP is used after the BWP inactivity timer expires, and indicating, by the default start RB location flag of BWP, that the default start RB location of BWP is used after the BWP inactivity timer expires, so that the terminal device can determine the frequency domain location of downlink or uplink communication with the network device, thereby improving the efficiency of communication.

In a tenth aspect, an embodiment of the present application provides a resource indication method, including: the terminal device receives configuration information sent by the network device, where the configuration information includes a default BWP id and a default BWP start RB location id, the default BWP id is associated with a BWP, and the default BWP start RB location id is associated with the default start RB location of the BWP. And the terminal equipment uses the BWP after the BWP inactivity timer is overtime according to the default BWP identification, and uses the default starting RB position of the BWP after the BWP inactivity timer is overtime according to the default starting RB position identification of the BWP.

The default BWP flag indicates to use BWP after the BWP inactivity timer expires and the default start RB location flag of the BWP indicates to use the default start RB location of the BWP after the BWP inactivity timer expires, so that the terminal device can determine the frequency domain location of downlink or uplink communication with the network device, thereby improving the communication efficiency.

In an eleventh aspect, the present application provides a resource indication apparatus, where the resource indication apparatus is configured to implement the methods and functions performed by the network device in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and the ninth aspect, and is implemented by hardware/software, where the hardware/software includes modules corresponding to the functions.

In a twelfth aspect, an embodiment of the present application provides a resource indication apparatus, configured to implement the methods and functions performed by the terminal device in the second, fourth, sixth, eighth and tenth aspects, where the resource indication apparatus is implemented by hardware/software, and the hardware/software includes modules corresponding to the functions.

In a thirteenth aspect, the present application provides a resource indication apparatus, which may be a network device, an apparatus in a network device, or an apparatus capable of being used in cooperation with a network device. The resource indicating device can also be a chip system. The resource indication means may perform the methods of the first, third, fifth, seventh and ninth aspects. The functions of the resource indicating device can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. The module may be software and/or hardware. For the operations and advantageous effects performed by the resource indication apparatus, reference may be made to the methods and advantageous effects described in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and the ninth aspect, and repeated details are not repeated.

In a fourteenth aspect, the present application provides a resource indication apparatus, which may be a terminal device, or an apparatus in a terminal device, or an apparatus capable of being used in cooperation with a terminal device. The resource indicating device can also be a chip system. The resource indication means may perform the methods of the second, fourth, sixth, eighth and tenth aspects. The functions of the resource indicating device can be realized by hardware, and can also be realized by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. The module may be software and/or hardware. The operations and beneficial effects executed by the resource indication apparatus may refer to the methods and beneficial effects described in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and the tenth aspect, and repeated descriptions are omitted.

In a fifteenth aspect, the present application provides a resource indicating apparatus comprising a processor, wherein the method according to any one of the first to tenth aspects is performed when the processor calls a computer program in a memory.

In a sixteenth aspect, the present application provides a resource indicating apparatus comprising a processor and a memory, the memory for storing a computer program; the processor is configured to execute a computer program stored in the memory to cause the resource indicating apparatus to perform the method of any of the first to tenth aspects.

In a seventeenth aspect, the present application provides a resource indicating apparatus, including a processor, a memory, and a transceiver, configured to receive a channel or a signal, or transmit a channel or a signal; the memory for storing a computer program; the processor is configured to invoke the computer program from the memory to perform the method according to any one of the first aspect to the tenth aspect.

In an eighteenth aspect, the present application provides a resource indication apparatus, comprising a processor and an interface circuit, the interface circuit being configured to receive a computer program and transmit the computer program to the processor; the processor runs the computer program to perform the method of any one of the first to tenth aspects.

Nineteenth aspect, the present application provides a computer readable storage medium for storing a computer program which, when executed, causes the method of any one of the first to tenth aspects to be carried out.

In a twentieth aspect, the present application provides a computer program product comprising a computer program which, when executed, causes the method of any one of the first to tenth aspects to be carried out.

In a twenty-first aspect, an embodiment of the present application provides a communication system, where the communication system includes at least one terminal device and at least one network device, the network device is configured to perform the steps in the first aspect, the third aspect, the fifth aspect, the seventh aspect, and the ninth aspect, and the terminal device is configured to perform the steps in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect, and the tenth aspect.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

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

FIG. 2 is a schematic diagram of a BWP configuration;

FIG. 3 is a schematic diagram of a rate matching pattern configuration;

FIG. 4 is a schematic diagram of another rate matching pattern configuration;

FIG. 5 is a schematic diagram of a ZP CSI-RS;

fig. 6 is a schematic diagram of legacy NR PDSCH and PUSCH transmissions;

fig. 7 is a schematic diagram of a REDCAP PDSCH and PUSCH transmission at different frequency locations;

fig. 8 is a flowchart illustrating a resource indication method according to an embodiment of the present application;

fig. 9 is a schematic diagram of a rate matching resource indication provided in an embodiment of the present application;

fig. 10 is a diagram illustrating another indication of rate matching resources according to an embodiment of the present application;

fig. 11 is a diagram illustrating another rate matching resource indication provided in an embodiment of the present application;

fig. 12 is a diagram illustrating another rate matching resource indication provided in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a resource indication apparatus according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another resource indication apparatus provided in an embodiment of the present application;

fig. 15 is a schematic structural diagram of a network device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

As shown in fig. 1, fig. 1 is a schematic architecture diagram of a communication system 100 according to an embodiment of the present disclosure. The communication system 100 may include a network device 110 and terminal devices 101 to 106. It should be understood that more or fewer network devices or terminal devices may be included in the communication system 100 to which the methods of the embodiments of the present application may be applied. The network device or the terminal device may be hardware, or may be functionally divided software, or a combination of the two. The network device and the terminal device can communicate through other devices or network elements. In this communication system 100, the network device 110 can transmit downlink data to the terminal devices 101 to 106. Of course, terminal apparatuses 101 to 106 may transmit uplink data to network apparatus 110. Terminal devices 101-106 may be cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, personal Digital Assistants (PDAs), and/or any other suitable device for communicating over wireless communication system 100, among others. The network device 110 may be a Long Term Evolution (LTE) and/or NR network device, and specifically may be a base station (NodeB), an evolved Node B (eNodeB), a base station in a 5G mobile communication system, a Next generation mobile communication base station (Next generation Node B, gNB), a base station in a future mobile communication system, or an access Node in a Wi-Fi system.

The communication system 100 may employ a Public Land Mobile Network (PLMN), a vehicle networking (V2X), a device-to-device (D2D) network, a machine-to-machine (M2M) network, an internet of things (IoT), or other networks. Further, the terminal apparatuses 104 to 106 may also constitute one communication system. In the communication system, the terminal device 105 may transmit downlink data to the terminal device 104 or the terminal device 106. The method in the embodiment of the present application can be applied to the communication system 100 shown in fig. 1.

Terminal devices can be classified into a plurality of types of terminals according to the types of services supported by the terminal devices. For example, a terminal device supporting a service with a higher data transmission rate requirement may be referred to as a first type terminal device, and a terminal device supporting a service with a lower data transmission rate requirement may be referred to as a second type terminal device. The terminal devices of the second class may be considered to be terminal devices with lower complexity or lower capability than the terminal devices of the first class, for example, the terminal devices of the second class may have lower complexity than the terminal devices of the first class in terms of supported bandwidth, power consumption, number of antennas, and the like, for example, the supported bandwidth is narrower, the power consumption is lower, the number of antennas is less, and the like.

In the embodiment of the present application, the first type of terminal device may also be referred to as a normal terminal device, or a legacy capability or/normal capability/high capability terminal device, and may also be referred to as a legacy terminal device or a legacy (legacy) terminal device. The second category of terminal devices may be referred to as low-complexity or low-power (redcapability ) terminal devices, mtc UEs, or (NR light, NRL) terminal devices, that is, lightweight terminal devices. The terminal device in the embodiment of the present application may be a first type terminal device, and may also be a second type terminal device.

It should be noted that the difference between the first type of terminal device and the second type of terminal device includes at least one of the following:

1. the bandwidth capabilities are different. The maximum bandwidth supported by the first type of terminal device may be greater than the maximum bandwidth supported by the second type of terminal device. For example, a first class of terminal devices may support communication with network devices using 100MHz frequency domain resources on one carrier at maximum, while a second class of terminal devices may support communication with network devices using 20MHz or less than 20MHz frequency domain resources on one carrier at maximum. For example, the second type of terminal device may support communication with the network device using 10MHz or 5MHz frequency domain resources on one carrier at the same time.

2. The number of the transmitting and receiving antennas is different. The antenna configuration of the first type of terminal device may be larger than the antenna configuration of the second type of terminal device. For example, the minimum antenna configuration supported by the first type of terminal device may be greater than the maximum antenna configuration supported by the second type of terminal device. For example, a first class of terminal devices may support 4 receive and 2 transmit (4 receive antennas and 2 transmit antennas). The second type of terminal device may support 2 receive and 1 transmit (2 receive antennas and 1 transmit antenna), or 1 receive and 1 transmit (1 receive antenna and 1 transmit antenna). It can be understood that, under the condition of achieving the same data transmission rate, since the number of the transceiving antennas of the second type terminal device is less than that of the transceiving antennas of the first type terminal device, the maximum coverage range that can be achieved by data transmission between the second type terminal device and the base station is less than that can be achieved by data transmission between the first type terminal device and the base station.

3. The maximum uplink transmit power is different. The uplink maximum transmitting power of the first type terminal equipment is larger than that of the second type terminal equipment.

4. The protocol versions are different. The first class of terminal devices may be terminal devices in NR version 15 (release-15, rel-15) or NR version 16 (release-16, rel-16). The second class of terminal devices may be considered terminal devices in NR version 17 (release-17, rel-17) or in later versions of NR Rel-17.

5. Carrier Aggregation (CA) capabilities differ. For example, a first class of terminal devices may support carrier aggregation, while a second class of terminal devices does not support carrier aggregation; for another example, the terminal devices of the second type and the terminal devices of the first type both support carrier aggregation, but the maximum number of cells for carrier aggregation simultaneously supported by the terminal devices of the first type is greater than the maximum number of cells for carrier aggregation simultaneously supported by the terminal devices of the second type.

6. Frequency Division Duplex (FDD) capabilities differ. For example, a first class of terminal devices supports full duplex FDD, while a second class of terminal devices supports only half duplex FDD.

7. The processing time capabilities for the data are different, for example, the minimum time delay between the first type of terminal device receiving the downlink data and sending the feedback for the downlink data is smaller than the minimum time delay between the second type of terminal device receiving the downlink data and sending the feedback for the downlink data. And/or the minimum time delay between the sending of the uplink data and the receiving of the feedback of the uplink data by the first type terminal equipment is less than the minimum time delay between the sending of the uplink data by the second type terminal equipment and the receiving of the feedback of the uplink data.

8. The processing capabilities (ability/capability) are different. For example, the baseband processing capability of the first type of terminal device is higher than the baseband processing capability of the second type of terminal device. Wherein the baseband processing capability may include at least one of: the maximum number of MIMO layers supported by the terminal device during data transmission, the number of HARQ processes supported by the terminal device, and the maximum Transport Block Size (TBS) supported by the terminal device.

9. The peak rates of uplink and/or downlink transmissions are different. The transmission peak rate refers to a maximum data transmission rate that the terminal device can achieve per unit time (e.g., per second). The uplink peak rate supported by the first class of terminal device may be higher than the uplink peak rate supported by the second class of terminal device, and/or the downlink peak rate supported by the first class of terminal device may be lower than the downlink peak rate supported by the second class of terminal device. For example, the uplink peak rate of the first type of terminal device is greater than or equal to 50Mbps, the downlink peak rate is greater than or equal to 150Mbps, the uplink peak rate of the second type of terminal device is less than or equal to 50Mbps, and the downlink peak rate is less than or equal to 150Mbps. For another example, the uplink peak rate or the downlink peak rate of the first type of terminal device is in the order of hundreds Mbps, and the uplink peak rate or the downlink peak rate of the second type of terminal device is in the order of Gbps.

10. The buffers (buffers) are of different sizes. Buffer is understood as the total size of Layer 2 (L2) buffer, which is defined as the sum of the number of bytes buffered in a Radio Link Control (RLC) transmission window and reception and reordering window and the number of bytes buffered in a Packet Convergence Protocol (PDCP) reordering window for all radio bearers. Alternatively, the buffer may also be understood as the total number of soft channel bits that can be used by a Hybrid Automatic Repeat reQuest (HARQ) process.

Of course, the above is only an example, and there may be other differences between the first type of terminal device and the second type of terminal device. In addition to the previous differences, there may be other differences, for example, the first type of terminal device does not support coverage enhancement, and the second type of terminal device supports coverage enhancement; for another example, the first type of terminal device does not support packet transmission, and the second type of terminal device supports packet transmission, which are not illustrated in sequence here.

(1)REDCAP。

The Fifth Generation (5G) mobile communication technology NR is a global 5G standard designed based on a new air interface of Orthogonal Frequency Division Multiplexing (OFDM), and is also a very important cellular mobile technology base of the next Generation, and the 5G technology has very diverse services and can be oriented to enhanced mobile broadband (eMBB) services, ultra-reliable low-latency communication (URLLC) services, and mass machine communication (mtc) services, where the mtc services may be Industrial Wireless Sensor Network (IWSN) services, video surveillance (video) services, or wearable services.

Machine type terminal devices often have higher requirements on cost and power consumption. For example, machine type terminal devices are generally implemented at low cost because the data transmission rate requirements of services in the application scenario corresponding to the machine type terminal devices are not high. For example, the data transmission rate carried by the sensor under the IWSN is not more than 2Mbps, which is enough to satisfy the IWSN service, the data transmission rate carried by the economical video monitoring camera is generally 2 to 4Mbps, the downlink peak rate of the terminal device under the wearable service, such as a smart watch, is not more than 150Mbps, the uplink peak rate thereof is not more than 50Mbps, and is much lower than the peak rate of the legacy terminal device (such as an NR eMBB terminal device). Based on this, machine type terminal equipment can reduce the realization specification for legacy terminal equipment, and then reduces implementation cost. On the other hand, reducing the implementation cost of the machine type terminal device also contributes to expanding the market of the machine type terminal device. Currently, 3GPP has initiated research on REDCAP terminal devices under NR system, and aims to design a terminal device meeting performance requirements of the internet of things market and having low cost/low implementation complexity for increasing the application of NR system in the internet of things market in the growing internet of things market, such as the above-mentioned IWSN, video monitoring and wearable services. For convenience of description, in the following sections of this document, the REDCAP terminal device is taken as an example for illustration.

One way to reduce the cost of the terminal device is to reduce the channel bandwidth of the terminal device, which can also be understood as reducing the bandwidth capability of the terminal device, that is, the bandwidth capability of the REDCAP terminal device may be much smaller than that of the legacy terminal device. Currently, legacy terminal devices, such as the terminal device of release Rel-15/release Rel-16, must have a bandwidth capability of 100MHz, while REDCAP terminal devices may have a bandwidth capability of only 20MHz from the viewpoint of being able to receive an initial access signal sent by an NR base station and then access an NR system, and in some configurations of the NR system, the bandwidth capability of the REDCAP terminal devices may be further reduced, for example, 5MHz or 10MHz, and at this time, the REDCAP terminal devices may also access the NR system. The bandwidth capability of not more than 20MHz can greatly reduce the cost of the REDCAP terminal device relative to the bandwidth capability of 100MHz.

In addition to bandwidth reduction, the REDCAP terminal device may also reduce the number of receive antennas compared to legacy terminal devices within the same frequency band. For example, in a frequency band in which legacy terminal equipment supports 2 receiving antennas, 1 receiving antenna may be supported by REDCAP terminal equipment, and in a frequency band in which legacy terminal equipment supports 4 receiving antennas, 1 receiving antenna may be supported by REDCAP terminal equipment, or 2 receiving antennas may be supported by REDCAP terminal equipment. The reduced number of receive antennas may also significantly reduce the cost of the REDCAP terminal device.

(2)BWP。

BWP is a new concept proposed in NR standard, and is a continuous bandwidth resource configured by a network device to a UE, which can implement flexible transmission bandwidth configuration for the network device and the UE. BWP is a UE-level concept, and different UEs may configure different BWPs. The network device may configure one or more downlink BWPs for the terminal device, where the BWPs are composed of Physical Resource Blocks (PRBs) that are consecutive in the frequency domain, and the BWPs are a subset in the UE bandwidth. The minimum granularity of the BWP in the frequency domain is 1 PRB. Each BWP is configured or associated with a BWP Identification (ID). The system may configure one or more BWPs for the end device, and the multiple BWPs may overlap in the frequency domain (overlap). As shown in fig. 2, the system may configure 4 BWPs for the terminal device, including BWP1, BWP2, BWP3, and BWP4.BWP1 and BWP2 overlap in the frequency domain.

(3) NR rate matching mechanism.

NR currently only supports rate matching by PDSCH, where rate matching refers to avoiding unusable resources when PDSCH resources are mapped, and mapping is performed only on available resources, where the resources refer to time domain and frequency domain resources, and may be Resource Blocks (RBs) and symbols (symbols), or Resource Elements (REs).

NR introduces a rate matching mechanism for the following scenarios:

scene 1: forward compatibility, NR requires that partial time and frequency domain resources are configured as resources that PDSCH cannot use for supporting future new functions.

Scene 2: NR and LTE coexist, and NR needs to configure a part of time domain and frequency domain resources as resources where PDSCH cannot be used, where the resources may be resources occupied by a reference signal of Long Term Evolution (LTE) and an MBSFN (multimedia broadcast multicast single frequency network) subframe.

Scene 3: NR reference signal measurement, where a reference signal for interference and Radio Resource Management (RRM) measurement is introduced into an NR system, in order to ensure measurement performance, NR needs to configure partial time domain and frequency domain resources as resources that PDSCH cannot use, and the resources can be used to transmit the reference signal for measurement.

Scene 4: NR PDCCH and PDSCH are multiplexed, NR requires that partial time and frequency domain resources be configured as resources that PDSCH cannot use for PDCCH transmission.

The above scenario still exists for the REDCAP terminal device, and therefore the REDCAP terminal device also needs to support the rate matching mechanism. In addition to the above scenario, the REDCAP terminal device needs to consider the following scenario:

scene 5: coexistence of a red ap terminal device and a non-red ap terminal device, the red ap terminal device needs to configure partial time and frequency domain resources as resources that the red ap PDSCH cannot use for transmission of data, control signals or reference signals of the non-red ap UE. The Non-REDCAP terminal device may be NR eMBB or URLLC UE.

NR supports two types of rate matching configuration schemes according to the granularity of configured resources.

The first is RB/symbol level rate matching. That is, the minimum granularity of the configured resources for rate matching is 1 RB in the frequency domain and one OFDM symbol in the time domain. The network device may configure a BWP-level or cell-level rate matching pattern (rate match pattern) through Radio Resource Control (RRC) signaling. Each BWP may be configured with a maximum of 4 rate pattern patterns, each associated with a rate pattern ID. These rate match patterns can be divided into at most two groups, which can be called ratemacchpattern group1 and ratemacchpattern group2. At least one rate match pattern is contained in the rate MatchPattern group1 or the rate MatchPattern group2. In addition, the network device may dynamically indicate, through the DCI, whether the PDSCH may use a resource set corresponding to ratemacchpatternrroup 1 or ratemacchpatternrroup 2.

Each rate match pattern contains a frequency domain resource bitmap (bitmap) and a time domain resource bitmap (TDB). Each bit in the frequency domain resource bitmap represents an RB, and the number of bits occupied by the frequency domain resource bitmap is 275; each bit in the time domain resource bitmap represents a symbol, the time domain range corresponding to the time domain resource bitmap is one time slot or two time slots, and the bit number occupied by the time domain resource bitmap is 14 or 28. In addition to the two bitmaps, the rate pattern bitmap also includes a period pattern bitmap, where each bit in the bitmap is used to indicate whether the time domain resource bitmap is valid, and a time domain range corresponding to the period pattern bitmap is the same as that of the time domain resource bitmap. In addition to the bitmap indication, the rate match pattern may further include a control-resource set (core set) ID indication that PDSCH may not use a resource set composed of the frequency domain resources of core set of the core set ID and the time domain resources determined by the search space associated with the core set.

As shown in fig. 3, fig. 3 is a schematic diagram of a rate matching pattern configuration. From the time domain dimension, the time domain range corresponding to the time domain resource bitmap is one time slot, and the bitmap is indicated as 10000000000001, which indicates that the PDSCH in one time slot may not use the 1 st and last symbols. The period pattern bitmap is indicated as 10, each bit represents a time slot, the bit length of the bitmap is 2, and therefore the period is 2 time slots, that is, every two time slots in the time domain cycle down according to the bitmap indication. The first bit in the periodic pattern bitmap indication is 1, which indicates that the 1 st slot in every two slots is indicated according to the time domain resource bitmap, that is, the PDSCH in the first slot in every two slots cannot use the 1 st and the last symbols, the first bit in the periodic pattern bitmap indication is 0, which indicates that the PDSCH can use the symbols in the 2 nd slot in every two slots, that is, the 2 nd slot in every two slots is not indicated according to the time domain resource bitmap.

Fig. 4 is a schematic diagram of another rate matching pattern configuration, as shown in fig. 4. From time domain and frequency domain dimensions, 4 rate pattern patterns are configured in BWP with BWP ID =1, the ID of the corresponding rate pattern is 1,2,3,4, the patterns are divided into two groups, rate map pattern group1 includes rate map patterns with rate map pattern IDs of 1 and 2, rate map pattern group2 includes rate map patterns with rate map pattern IDs of 3 and 4, DCI includes 2 bits, the 1 st bit indicates whether the PDSCH can use the resource set corresponding to rate map pattern group1, and the 2 nd bit indicates whether the PDSCH can use the resource set corresponding to rate map pattern group2.

The second is RE-level rate matching. I.e., the minimum granularity of the configured resources for rate matching in time and frequency domains is one RE. The network device may configure an aperiodic Zero Power (ZP) channel state information reference signal (CSI-RS) resource set, a semi-persistent (semi-persistent) ZP CSI-RS resource set, and a periodic (periodic) ZP CSI-RS resource set on each BWP, with a maximum of 16 ZP CSI-RS resources configured within each resource set. The configuration of the periodic ZP CSI-RS resource set takes effect when completed, and the aperiodic ZP CSI-RS resource set and the semi-continuous ZP CSI-RS resource set need to be matched with a trigger signaling or an activation signaling for use and take effect after receiving the trigger signaling or the activation instruction. For the REs indicated by the periodic ZP CSI-RS resource set, PDSCH may not be used. For the REs indicated by the aperiodic ZP CSI-RS resource set and the semi-persistent ZP CSI-RS resource set, the PDSCH can not be used after a trigger or an activation instruction is received.

At most 3 aperiodic ZP CSI-RS resource sets can be configured in each BWP, a DCI carries an aperiodic CSI-RS trigger field, and the number of bits of the field, which is the number of the configured aperiodic ZP CSI-RS resource sets, occupies at most 2 bits. The value of the field is '00' to indicate that the aperiodic ZP CSI-RS is not triggered; the value of the field is '01', which indicates that a CSI-RS resource set corresponding to ZP-CSI-RS-ResourceSetIds =1 is triggered; the value of the field is '10' to indicate that a CSI-RS resource set corresponding to ZP-CSI-RS-ResourceSetIds =2 is triggered; a value of "11" in this field indicates that the set of CSI-RS resources corresponding to ZP-CSI-RS-ResourceSetIds =3 is triggered. As shown in fig. 5, fig. 5 is a ZP CSI-RS diagram for one slot and one RB with 3 REs that cannot be used by PDSCH.

The configuration parameters of the ZP CSI-RS comprise: ZP-CSI-RS-resource id used for determining ZP CSI-RS resource configuration identification; nrofPorts, for defining the port number of the CSI-RS; CDM-Type, CDM value and pattern are defined; and resource mapping, which defines the OFDM symbol and the subcarrier position occupied by the ZP CSI-RS in a time slot. period and offset indicating the period and the period of the semi-persistent ZP CSI-RS and the slot offset.

As shown in fig. 6, fig. 6 is a schematic diagram of legacy NR PDSCH and PUSCH transmissions. PDSCH and PUSCH transmission are completed in one BWP, the PDSCH supports interleaving transmission in a frequency range corresponding to the BWP, and the PUSCH supports frequency hopping transmission in the frequency range corresponding to the BWP. The bandwidth of BWP does not exceed the UE bandwidth capability, and for legacy UEs, the bandwidth of BWP may be 100MHz at maximum.

For the REDCAP terminal device, the BWP bandwidth capability is 20MHz maximum. The REDCAP terminal device can only transmit PDSCH and PUSCH in its BWP range if it is according to the existing framework. Compared to the NR legacy terminal device, the frequency diversity gain obtained by the redcp terminal device is reduced due to the reduced BWP bandwidth range. In order to obtain a frequency diversity gain comparable to that of the NR legacy terminal device, the REDCAP UE needs to support frequency hopping over a wider range. As shown in fig. 7, fig. 7 is a schematic diagram of the transmission of the red ap PDSCH and PUSCH at different frequency locations. The PDSCH/PUSCH are transmitted in 2 BWPs or frequency positions of 20MHz, respectively.

In summary, REDCAP and legacy NR include the following differences: first, legacy NR PDSCH/PUSCH transmissions are transmitted within only one BWP, whereas REDCAP PDSCH/PUSCH transmissions may span multiple BWPs or frequency locations at a time. Second, legacy NR supports rate matching only PDSCH. Compared with legacy NR, the scenario that REDCAP needs to perform rate matching is one more scenario 5, that is, coexistence of REDCAP terminal device and non-REDCAP terminal device, where the non-REDCAP terminal device may be understood as legacy terminal device, and in order to avoid mutual influence between REDCAP and legacy NR, it is necessary for REDCAP PUSCH to support rate matching.

For the REDCAP terminal device, the resource situation that one time of PDSCH/PUSCH transmission needs to be avoided in different BWP or frequency positions is different. How to inform the REDCAP terminal device of rate matching patterns (rate pattern) of multiple BWPs or frequency locations is an urgent problem to be solved.

In addition, the network device configures N BWP sets, where each BWP set configures M BWPs, and the identities of the M BWPs are different. Or the network device configures N BWPs, where each BWP corresponds to one BWP id and M start RB locations. Wherein M and N are positive integers. For a BWP set, or M starting RB locations corresponding to a BWP, how the terminal device determines the frequency domain location for downlink or uplink communication with the network device is a problem to be solved.

As shown in fig. 8, fig. 8 is a schematic flowchart of a resource indication method according to an embodiment of the present application. The steps in the embodiments of the present application include at least:

s801, the network device sends configuration information to the terminal device, where the configuration information is used to configure multiple partial bandwidth BWPs, and each BWP in the multiple BWPs configures at least one rate matching resource.

Optionally, the network device may send the configuration information to the terminal device through RRC signaling.

Wherein, the marks corresponding to the plurality of BWPs are different, the starting positions of the resource blocks RB of the plurality of BWPs are different, or the marks corresponding to the plurality of BWPs are the same, and the starting positions of the resource blocks RB of the plurality of BWPs are different.

Wherein the first BWP and the second BWP are two BWPs in the plurality of BWPs, and the parameters of the first BWP and the second BWP are the same, and the parameters include at least one of: bandwidth, subcarrier spacing, the number of ports corresponding to Sounding Reference Signals (SRS), and the number of maximum-input-multiple-output (MIMO) layers, where the maximum MIMO layers are the maximum MIMO layers used by the PDSCH.

Wherein the subcarrier spacing of the rate matching resources on the plurality of BWPs is the same.

The terminal device is a REDCAP terminal device, and the PDSCH/PUSCH one-time transmission of the REDCAP terminal device may span multiple BWPs or frequency positions.

Wherein, a plurality of BWPs form a BWP set. Optionally, the first BWP and the second BWP are two BWPs in the BWP set, and the time delay for adjusting the frequency domain position from the first BWP to the second BWP is the first time delay. The operation of adjusting the frequency-domain position from the first BWP to the second BWP may be referred to as switching or tuning or frequency hopping. The first time delay is smaller than a second time delay, wherein the second time delay is a BWP switching time delay supported by NR terminal equipment, namely T _{BWPswitchDelay} One time slot of the time slot is used,as shown in table 1. T is _{BWPswitchDelay} The value of (a) is determined according to the capability of the terminal equipment and the subcarrier spacing. The capability of the terminal equipment can be Type1 and Type 2, and the terminal equipment reports the capability to the network equipment. The value of μ corresponds to the subcarrier spacing, and is configured by the network device. The subcarrier spacing Δ f and μ satisfy: Δ f =2 ^μ ·15[kHz]. For example, assuming that μ is 0, the terminal device capability is Type1, and the subcarrier spacing before BWP handover and after BWP handover are the same, t is determined according to table 1 _{BWPswitchDelay} Is 1, the BWP handoff delay is T _{BWPswitchDelay} The slot length =1 × 1ms =1ms corresponding to multiplication of μ by 0.

TABLE 1

One or more rate matching resources are configured on each BWP, one rate matching resource corresponds to one rate matching pattern, and each rate matching pattern is associated with one rate matching pattern ID.

S802, the network device sends downlink control information DCI to the terminal device, where the DCI includes scheduling information and indication information, the scheduling information is used to schedule transmission of a physical downlink shared channel PDSCH or/and a physical uplink shared channel PUSCH, and the terminal device determines, according to the indication information, whether rate matching resources on multiple BWPs can be used during transmission of the PDSCH or/and the PUSCH. The method comprises the following steps:

in a first alternative, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, the rate matching resource groups on the BWPs are divided into at least one association group, and the indication information is used to determine whether each of the at least one association group can be used during the PDSCH or/and PUSCH transmission. The association relationship exists among the rate matching resource groups on the plurality of BWPs, and one or more rate matching resource groups with the association relationship are divided into one association group, and the association relationship may be predetermined or preconfigured by the network device.

Wherein the indication information comprises a plurality of bits, one bit corresponds to one of the associated groups, and the number of the plurality of bits is smaller than the group number of the rate matching resource groups on the plurality of BWPs.

For example, as shown in fig. 9, the network device configures two BWPs, the BWP with corresponding BWP ID =0 and BWP ID =1, BWP ID =0 is abbreviated as BWP #0, and the BWP with BWP ID =1 is abbreviated as BWP #1.BWP #0 and BWP #1 are each configured with 4 rate matching resources corresponding to four rate matching patterns (rate pattern IDs) 1,2,3, and 4, respectively. The rate matching resources on each BWP are grouped in an independent grouping manner, BWP #0 and BWP #1 are both divided into two rate matching resource groups, which include rate matching resource 1 (rate matching pattern ID = 1) and rate matching resource 2 (rate matching pattern ID = 2) belonging to rate matching resource group1 (group 1), rate matching resource 3 (rate matching pattern ID = 3) and rate matching resource 4 (rate matching pattern ID = 4) belonging to rate matching resource group2 (group 2). The network device and the terminal device may agree in advance that group1 on BWP #0 and group1 on BWP #1 have an association relationship, and divide group1 on BWP #0 and group1 on BWP #1 into an association group 1. It is agreed in advance that there is an association relationship between group2 on BWP #0 and group2 on BWP #1, and group2 on BWP #0 and group2 on BWP #1 are divided into another association group2. The bit number included in the rate matching indication information in DCI is 2, which is smaller than the total number of groups 4 included in BWP #0 and BWP #1. The first bit in the indication information in the DCI is 1, which indicates that the PDSCH or PUSCH scheduled by the DCI may not use the rate matching resources corresponding to group1 on BWP #0 and group1 on BWP #1. The second bit in the indication information in the DCI is 0, which indicates that the PDSCH or PUSCH scheduled by the DCI may use the rate matching resources corresponding to group2 on BWP #0 and group2 on BWP #1.

The indication information may also indicate that 0 and 1 are in reverse, that is, the first bit in the indication information is 1, and it indicates that the PDSCH or PUSCH scheduled by the DCI may use the rate matching resource corresponding to the group1 on BWP #0 and the group1 on BWP #1. The second bit in the indication information is 0, which indicates that the PDSCH or PUSCH scheduled by the DCI may not use the rate matching resources corresponding to group2 on BWP #0 and group2 on BWP #1.

As another example, as shown in fig. 10, the network device may also pre-configure the association between the rate matching resource groups on multiple BWPs. Group1 and group2 on BWP #0 and group1 on BWP #1 are configured as one association group1, and group2 on BWP #1 is configured as another association group2. The indication information in the DCI contains 2 bits, each bit corresponding to an association. The first bit in the indication information is 1, which indicates that the PDSCH or PUSCH scheduled by the DCI may not use the rate matching resources corresponding to group1 on BWP #0, group2 on BWP #0, and group1 on BWP #1. The second bit in the indication information in the DCI is 0, which indicates that the PDSCH or PUSCH scheduled by the DCI may use the rate matching resource corresponding to group2 on BWP #1.

Optionally, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the indication information is used to determine whether each rate matching resource group on the multiple BWPs can be used during the PDSCH or/and PUSCH transmission.

Wherein the indication information comprises a plurality of bits, one bit corresponds to one rate-matching resource group, and the number of the plurality of bits is equal to the group number of the rate-matching resource groups on the plurality of BWPs. The correspondence between the bits of the indication information and the rate matching resource groups may be preset. For example, the BWP IDs are sequentially from small to large, and then the group numbers are sequentially from small to large, and the bits in the indication information correspond to each other, that is, the first bit of the indication information corresponds to BWP #0group1, the second bit corresponds to BWP #0group2, the third bit corresponds to BWP #1group1, and the fourth bit corresponds to BWP #1group2. Alternatively, the BWP IDs may be associated with the bits in the indication information in descending order of BWP IDs and then in ascending order of group numbers. That is, the first bit of the indication information corresponds to BWP #0group2, and the first bit corresponds to BWP #0group1, \ 8230 \ 8230, and other corresponding relations are similar, and are not illustrated here.

As shown in fig. 11, the network device configures two BWPs, the BWP with BWP ID =0 and BWP ID =1, BWP ID =0 is abbreviated as BWP #0, and the BWP with BWP ID =1 is abbreviated as BWP #1.BWP #0 and BWP #1 are each configured with 4 rate matching resources, corresponding to four rate matching patterns (rate pattern IDs) of 1,2,3 and 4. The rate matching resources on each BWP are grouped in an independent grouping manner, BWP #0 and BWP #1 are both divided into two rate matching resource groups, including rate matching resource 1 (rate pattern ID = 1) and rate matching resource 2 (rate pattern ID = 2) belonging to rate matching resource group1 (group 1), rate matching resource 3 (rate pattern ID = 3) and rate matching resource 4 (rate pattern ID = 4) belonging to rate matching resource group2 (group 2). The number of bits included in the indication information in the DCI is 4, which is equal to 4, which is the total number of groups included in BWP #0 and BWP #1. The 4 bits in the DCI correspond to the rate matching resource groups one by one, and the corresponding relation is determined according to the sequence of the BWP ID from small to large and then according to the sequence of the group numbers from small to large, namely the first bit corresponds to BWP #0group1, the second bit corresponds to BWP #0group2, the third bit corresponds to BWP #1group1, and the fourth bit corresponds to BWP #2group2. The bit value of 1 indicates that the rate matching resource group corresponding to the bit cannot be used during the transmission of the PDSCH/PUSCH; a bit value of 0 indicates that the rate matching resource group corresponding to the bit can be used during PDSCH/PUSCH transmission. The

values

0 and 1 may also be indicated in reverse, that is, a bit value of 1 indicates that the rate matching resource group corresponding to the bit may be used during the PDSCH/PUSCH transmission, and a bit value of 0 indicates that the rate matching resource group corresponding to the bit may not be used during the PDSCH/PUSCH transmission.

Optionally, the network device may pre-configure grouping information, where the grouping information includes at least one rate matching resource group. All rate matching resources on the plurality of BWPs are jointly grouped into at least one rate matching resource group, and the indication information contained in the DCI is used for determining whether each of the at least one rate matching resource group can be used during the PDSCH or/and PUSCH transmission.

Wherein the indication information comprises a plurality of bits, one bit corresponds to one rate matching resource group, and the number of the plurality of bits is equal to the group number of the at least one rate matching resource group.

For example, as shown in fig. 12, the network device configures two BWPs, the BWPs with BWP IDs of BWP ID =0 and BWP ID =1, BWP ID =0 are abbreviated as BWP #0, and the BWPs with BWP ID =1 are abbreviated as BWP #1.BWP #0 and BWP #1 are each configured with 4 rate matching resources, corresponding to four rate matching patterns (rate pattern IDs) of 1,2,3 and 4. And grouping the rate matching resources on two BWPs by adopting a joint grouping, wherein the rate matching resource with the rate pattern ID of 1,2,3 and 4 on BWP #0 and the rate matching resource with the rate pattern ID of 1,2 on BWP #1 is a rate matching resource group1 (group 1), and the rate matching resource with the rate pattern ID of 3 and 4 on BWP #1 is a rate matching resource group2 (group 2). The number of bits included in the indication information in the DCI is 2, which is equal to the number of groups 2 in the rate matching resource group. The bit value of 1 indicates that the rate matching resource corresponding to the bit may not be used during the PDSCH/PUSCH transmission, and the bit value of 0 indicates that the rate matching resource corresponding to the bit may be used during the PDSCH/PUSCH transmission. A bit value of 0 and 1 may also indicate the other way around, that is, a bit value of 1 indicates that the rate matching resource corresponding to the bit may be used during the PDSCH/PUSCH transmission, and a bit value of 0 indicates that the rate matching resource corresponding to the bit may not be used during the PDSCH/PUSCH transmission.

The rate matching resource is a resource block RB or symbol level rate matching resource, or the rate matching resource is a resource element RE level rate matching resource. One rate matching resource corresponds to one rate matching pattern, and the method for configuring the rate matching resource in the embodiment of the present application may refer to the method for configuring the rate matching resource. And will not be described in detail herein.

In the embodiment of the present application, in a coexistence situation of the red ap terminal device and the non-red ap terminal device, by notifying the red ap terminal device whether the rate matching resources on multiple BWPs can be used during PDSCH or/and PUSCH transmission, the transmission performance of the PDSCH or PUSCH is guaranteed, and the traffic on the rate matching resources is prevented from being affected, thereby improving the transmission efficiency of the traffic on the rate matching resources.

If the network device configures N BWP sets, each BWP set in the N BWP sets configures M BWPs, and the identifications of the M BWPs are different. Or the network device configures N BWPs, where each BWP corresponds to one BWP id and M start RB locations. The following describes how the terminal device determines the frequency domain location for downlink or uplink communication with the network device in the above case.

The network device configures a first active BWP set identification, which is associated with a BWP set. The BWP set identified by the first active BWP set is activated after performing RRC configuration or RRC reconfiguration (e-) configuration). The network device is further configured with a first active BWP id, and the first active BWP id is associated with a BWP. The BWP may be one BWP in a first active BWP set identification association. The BWP identified by the first active BWP is activated (e-) configuration) after performing RRC configuration or RRC reconfiguration. Accordingly, the terminal device receives the first active BWP set identification and the first active BWP identification configured by the network device. An active BWP set is determined based on the first active BWP set identification and an active BWP is determined based on the first BWP set identification. The terminal device performs downlink or uplink communication with the network device on the activated BWP set and the activated BWP. It should be noted that the BWP set here is an uplink BWP set or a downlink BWP set, and the BWP set here is an uplink BWP or a downlink BWP. The above mentioned identities also need to be configured separately for the downlink and uplink. For the one BWP set, the first BWP and the second BWP are two BWPs in the BWP set, and the parameters of the first BWP and the second BWP are the same, and the parameters include at least one of: bandwidth, subcarrier spacing, a port number corresponding to a Sounding Reference Signal (SRS), and a maximum-input-multiple-output (MIMO) layer number, where the maximum MIMO layer number is a maximum MIMO layer number used by the PDSCH. Optionally, the first BWP and the second BWP are two BWPs in the BWP set, and the time delay for adjusting the frequency domain position from the first BWP to the second BWP is the first time delay. Frequency domain position from first BThe operation of WP tuning to the second BWP may be referred to as switching or tuning or frequency hopping. The first time delay is smaller than a second time delay, wherein the second time delay is the BWP switching time delay supported by the NR terminal equipment, namely T _{BWPswitchDelay} As shown in table 1, refer to the related description in S801, and are not described herein again.

Alternatively, the network device configures a first active BWP identity, and the first active BWP identity is associated with a BWP. The BWP identified by the first active BWP is activated after performing RRC configuration or RRC reconfiguration (to activated uplink configuration). In addition, the network device configures a starting RB position id of the first BWP, where the starting RB position id of the first BWP is associated with a starting RB position of the first BWP. The starting RB position of the BWP may be one starting RB position of the first active BWP identification associated BWP. The starting RB location of the first BWP identifies the associated starting RB location to be activated after RRC configuration or RRC reconfiguration is performed (e-) configuration). Accordingly, the terminal device receives a first active BWP identifier configured by the network device and a start RB location identifier of the first BWP. And determining the activated BWP according to the first activated BWP identification, and determining the activated starting RB position according to the starting RB position identification of the first BWP. The terminal device takes the activated starting RB position as a starting RB position, and performs downlink or uplink communication with the network device on the activated BWP. It should be noted that BWP here is uplink BWP or downlink BWP. The above mentioned identities also need to be configured separately for the downlink and uplink.

Optionally, the network device configures a default BWP set identifier, and the default BWP set identifier is associated with a BWP set. The BWP set identified by the default BWP set is used (to be used up expiry of the BWP inactivity timer) after the BWP inactivity timer expires. In addition, the network device is configured with a default BWP identification, and the default identification is associated with a BWP. The BWP may be one of a default BWP set identification associated BWP set. The BWP of the default BWP identification is used (to be used up expiration of the BWP inactivity timer) after the BWP inactivity timer expirestimer). Accordingly, the terminal device receives the default BWP set identification and the default BWP identification configured by the network device. A default BWP set is determined according to the default BWP set identification, and a default BWP is determined according to the first BWP set identification. The terminal device communicates with the network device in the default BWP set and the default BWP in a downlink or uplink manner. It should be noted that the BWP set here is an uplink BWP set or a downlink BWP set, and the BWP set here is an uplink BWP or a downlink BWP. The above mentioned identities also need to be configured separately for the downlink and uplink. For the one BWP set, the first BWP and the second BWP are two BWPs in the BWP set, and the parameters of the first BWP and the second BWP are the same, where the parameters include at least one of: bandwidth, subcarrier spacing, a port number corresponding to a Sounding Reference Signal (SRS), and a maximum-input-multiple-output (MIMO) layer number, where the maximum MIMO layer number is a maximum MIMO layer number used by the PDSCH. Optionally, the first BWP and the second BWP are two BWPs in the BWP set, and the time delay for adjusting the frequency domain position from the first BWP to the second BWP is the first time delay. The operation of adjusting the frequency-domain position from the first BWP to the second BWP may be referred to as switching or tuning or frequency hopping. The first time delay is smaller than a second time delay, wherein the second time delay is a BWP switching time delay supported by NR terminal equipment, namely T _{BWPswitchDelay} As shown in table 1, refer to the related description in S801, and are not described herein again.

Alternatively, the network device configures a default BWP identity, which is associated with a BWP. The BWP of the default BWP identification is used (to be used on expiration of the BWP inactivity timer) upon expiration of the BWP inactivity timer. In addition, the network device configures a default starting RB position id of the BWP, where the default starting RB position id of the BWP is associated with a default starting RB position of the BWP. The default starting RB position for the BWP may be one starting RB position for which the default BWP identifies the associated BWP. The default starting RB position ID of BWP is used (to used up expiry of the BWP inactivity timer) upon timeout of the BWP inactivity timer. Accordingly, the terminal device receives the default BWP identification configured by the network device and the start RB location identification of the default BWP. A default BWP is determined based on the default BWP identification and a default starting RB position is determined based on the starting RB position identification for the default BWP. And the terminal equipment takes the default starting RB position as the starting RB position and carries out downlink or uplink communication with the network equipment on the default BWP. Here, BWP is an upstream BWP or a downstream BWP. The above mentioned identities also need to be configured separately for the downlink and uplink.

It is to be understood that, in the above-described method embodiments, the method and the operation implemented by the terminal device may also be implemented by a component (e.g., a chip or a circuit) available for the terminal device, and the method and the operation implemented by the network device may also be implemented by a component (e.g., a chip or a circuit) available for the network device.

The above description mainly introduces the scheme provided by the embodiments of the present application from various interaction perspectives. It is understood that each network element, for example, the transmitting end device or the receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to implement the above functions. Those of skill in the art would appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiment of the present application, the functional modules may be divided according to the above method example for the transmitting end device or the receiving end device, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be implemented in the form of hardware, and can also be implemented in the form of a software functional module. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and another division manner may be available in actual implementation. The following description will be given by taking an example in which each function module is divided for each function.

The method provided by the embodiment of the present application is described in detail above with reference to fig. 8. Hereinafter, a resource indicating apparatus according to an embodiment of the present application will be described in detail with reference to fig. 13 to 14. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment, and therefore, for the sake of brevity, details which are not described in detail above may be referred to the method embodiment.

Referring to fig. 13, fig. 13 is a schematic structural diagram of a resource indicating apparatus according to an embodiment of the present disclosure. The resource indication apparatus may include a sending module 1301, the sending module 1301 may communicate with the outside, and the sending module 1301 may also be referred to as a communication interface, a transceiving unit, or a transceiving module. The sending module 1301 may be configured to perform the actions performed by the network device in the foregoing method embodiments.

For example: the sending module 1301 may also be referred to as a transceiver module or a transceiver unit (including a receiving unit and a receiving unit), and is configured to perform the steps of sending and receiving by the network device in the foregoing method embodiments, respectively.

In one possible design, the resource indication apparatus may implement the steps or processes performed by the network device corresponding to the above method embodiments, for example, the resource indication apparatus may be a network device, or a chip or a circuit configured in the network device. The sending module 1301 is configured to perform the transceiving related operations on the network device side in the foregoing method embodiment.

A sending module 1301, configured to send configuration information to a terminal device, where the configuration information is used to configure a plurality of partial bandwidth BWPs, and each BWP in the plurality of BWPs configures at least one rate matching resource;

the sending module 1301 is further configured to send downlink control information DCI to the terminal device, where the DCI includes scheduling information and indication information, the scheduling information is used to schedule transmission of a physical downlink shared channel PDSCH or/and a physical uplink shared channel PUSCH, and the indication information is used to determine whether rate matching resources on the multiple BWPs can be used during transmission of the PDSCH or/and the PUSCH.

Optionally, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, the rate matching resource groups on the BWPs are divided into at least one association group, and the indication information is used to determine whether each of the at least one association group can be used during the PDSCH or/and PUSCH transmission.

Optionally, the indication information includes a plurality of bits, one bit corresponds to one association group, and the number of the plurality of bits is smaller than the number of groups of the rate matching resource groups on the plurality of BWPs.

Optionally, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the indication information is used to determine whether each rate matching resource group on the multiple BWPs can be used during the PDSCH or/and the PUSCH transmission.

Optionally, the indication information includes a plurality of bits, one bit corresponds to one rate-matching resource group, and the number of the plurality of bits is equal to the number of groups of the rate-matching resource groups on the plurality of BWPs.

Optionally, all rate matching resources on the multiple BWPs are jointly grouped into at least one rate matching resource group, and the indication information is used to determine whether each of the at least one rate matching resource group can be used during the PDSCH or/and the PUSCH transmission.

Optionally, the indication information includes a plurality of bits, one bit corresponds to one rate matching resource group, and the number of the plurality of bits is equal to the group number of the at least one rate matching resource group.

Optionally, the identifiers corresponding to the BWPs are different, the starting positions of the resource blocks RB of the BWPs are different, or the identifiers corresponding to the BWPs are the same, and the starting positions of the resource blocks RB of the BWPs are different.

Optionally, the first BWP and the second BWP are two BWPs in the plurality of BWPs, and the parameters of the first BWP and the second BWP are the same, where the parameters include at least one of: bandwidth, subcarrier interval, port number corresponding to sounding reference signal SRS, and maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

Optionally, the subcarrier spacing of the rate matching resources on the plurality of BWPs is the same.

Optionally, the rate matching resource is a resource block RB or symbol level rate matching resource, or the rate matching resource is a resource element RE level rate matching resource.

It should be noted that, the implementation of each module may also correspond to the corresponding description of the method embodiment shown in fig. 8, and execute the method and the function executed by the network device in the foregoing embodiment.

Referring to fig. 14, fig. 14 is a schematic structural diagram of a resource indicating apparatus according to an embodiment of the present disclosure. The resource indication apparatus may include a receiving module 1401, and the receiving module 1401 may communicate with the outside. The receiving module 1401 may also be referred to as a communication interface, a transceiving unit, or a transceiving module. The receiving module 1401 may be configured to perform the actions performed by the terminal device in the foregoing method embodiments.

For example: the receiving module 1401 may also be referred to as a transceiver module or a transceiver unit (including a receiving unit and a receiving unit), and is used for performing the steps of the terminal device transmitting and receiving in the above method embodiments, respectively.

In a possible design, the resource indication apparatus may implement the steps or processes executed by the terminal device corresponding to the above method embodiment, for example, the resource indication apparatus may be the terminal device, or a chip or a circuit configured in the terminal device. The receiving module 1401 is configured to perform transceiving related operations on the terminal device side in the foregoing method embodiments.

A receiving module 1401, configured to receive configuration information from a network device, where the configuration information is used to configure a plurality of partial bandwidth BWPs, and each BWP in the plurality of BWPs configures at least one rate matching resource thereon;

a receiving module 1401, further configured to receive downlink control information DCI from the network device, where the DCI includes scheduling information and indication information, the scheduling information is used to schedule transmission of a physical downlink shared channel PDSCH or/and a physical uplink shared channel PUSCH, and the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during transmission of the PDSCH or/and the PUSCH.

Optionally, the indication information includes a plurality of bits, one bit corresponds to one rate-matching resource group, and the number of the plurality of bits is equal to the group number of the rate-matching resource groups on the plurality of BWPs.

Optionally, all rate matching resources on the BWPs are jointly grouped into at least one rate matching resource group, and the indication information is used to determine whether each of the at least one rate matching resource group can be used during the PDSCH or/and PUSCH transmission.

Optionally, the first BWP and the second BWP are two BWPs in the multiple BWPs, and the parameters of the first BWP and the second BWP are the same, where the parameters include at least one of: bandwidth, subcarrier spacing, the number of ports corresponding to sounding reference signals SRS, and the maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

Optionally, the subcarrier spacing of the rate matching resources on the multiple BWPs is the same.

It should be noted that, the implementation of each module may also correspond to the corresponding description of the method embodiment shown in fig. 8, and execute the method and the function executed by the terminal device in the foregoing embodiment.

Fig. 15 is a schematic structural diagram of a network device according to an embodiment of the present application. The network device may be applied in a system as shown in fig. 1, and perform the functions of the network device in the above method embodiment, or implement the steps or processes performed by the network device in the above method embodiment.

As shown in fig. 15, the network device includes a processor 1501 and a transceiver 1502. Optionally, the network device further comprises a memory 1503. The processor 1501, the transceiver 1502 and the memory 1503 can communicate with each other via the interconnection path to transmit control and/or data signals, the memory 1503 is used for storing computer programs, and the processor 1501 is used for calling and running the computer programs from the memory 1503 to control the transceiver 1502 to transmit and receive signals. Optionally, the network device may further include an antenna, configured to send uplink data or uplink control signaling output by the transceiver 1502 through a wireless signal.

The processor 1501 may be combined with the memory 1503 to form a processing device, and the processor 1501 is configured to execute the program codes stored in the memory 1503 to implement the functions described above. In particular, the memory 1503 may be integrated into the processor 1501 or may be separate from the processor 1501.

The transceiver 1502 may correspond to the transmitting module in fig. 13, and may also be referred to as a transceiver unit or a transceiver module. The transceiver 1502 may include a receiver (or receiver, receive circuitry) and a transmitter (or transmitter, transmit circuitry). Wherein the receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the network device shown in fig. 15 can implement various processes involving the network device in the method embodiment shown in fig. 8. The operations and/or functions of the modules in the network device are respectively for implementing the corresponding flows in the above method embodiments. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

The processor 1501 described above may be used to perform the actions described in the previous method embodiments that are implemented internally by the network device, while the transceiver 1502 may be used to perform the actions described in the previous method embodiments that the network device transmits to or receives from the terminal device. Please refer to the description of the previous embodiment of the method, which is not repeated herein.

The processor 1501 may be, among other things, a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. Processor 1501 may also be a combination of computing functions, e.g., comprising one or more microprocessors, a combination of digital signal processors and microprocessors, and so forth. The communication bus 1504 may be a peripheral component interconnect standard PCI bus or an extended industry standard architecture EISA bus or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 15, but this is not intended to represent only one bus or type of bus. A communication bus 1504 is used to enable connective communication between these components. In the embodiment of the present application, the transceiver 1502 is used for performing signaling or data communication with other node devices. The memory 1503 may include a volatile memory, such as a nonvolatile dynamic random access memory (NVRAM), a phase change random access memory (PRAM), a Magnetoresistive Random Access Memory (MRAM), and the like, and may further include a nonvolatile memory, such as at least one magnetic disk memory device, an electrically erasable programmable read-only memory (EEPROM), a flash memory device, such as a NOR flash memory (NOR flash memory) or a NAND flash memory (EEPROM), a semiconductor device, such as a Solid State Disk (SSD), and the like. Memory 1503 may alternatively be at least one memory device located remotely from the aforementioned processor 1501. Optionally, a set of computer program code or configuration information may also be stored in memory 1503. Alternatively, the processor 1501 may also execute programs stored in the memory 1503. The processor may cooperate with the memory and the transceiver to perform any of the methods and functions of the network device of the embodiments of the above-mentioned application.

Fig. 16 is a schematic structural diagram of a terminal device according to an embodiment of the present application. The terminal device may be applied to a system as shown in fig. 1, and execute the functions of the terminal device in the foregoing method embodiment, or implement the steps or processes executed by the terminal device in the foregoing method embodiment.

As shown in fig. 16, the terminal device includes a processor 1601 and a transceiver 1602. Optionally, the terminal device further includes a memory 1603. The processor 1601, the transceiver 1602 and the memory 1603 may communicate with each other via an internal connection path to transmit control and/or data signals, the memory 1603 is used for storing a computer program, and the processor 1601 is used for calling and running the computer program from the memory 1603 to control the transceiver 1602 to transmit and receive signals. Optionally, the terminal device may further include an antenna, configured to send out the uplink data or the uplink control signaling output by the transceiver 1602 through a wireless signal.

The processor 1601 may be combined with the memory 1603 to form a processing device, and the processor 1601 is configured to execute the program code stored in the memory 1603 to implement the functions. In particular, the memory 1603 may be integrated into the processor 1601 or may be independent of the processor 1601.

The transceiver 1602 may correspond to the receiving module in fig. 14, and may also be referred to as a transceiver unit or a transceiver module. The transceiver 1602 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). The receiver is used for receiving signals, and the transmitter is used for transmitting signals.

It should be understood that the terminal device shown in fig. 16 can implement the various processes involving the terminal device in the method embodiment shown in fig. 8. The operation and/or function of each module in the terminal device are respectively for implementing the corresponding flow in the above method embodiment. Specifically, reference may be made to the description of the above method embodiments, and the detailed description is appropriately omitted herein to avoid redundancy.

The processor 1601 may be used to perform the actions described in the previous method embodiments that are implemented inside the terminal device, and the transceiver 1602 may be used to perform the actions described in the previous method embodiments that the terminal device transmits to or receives from the network device. Please refer to the description in the previous embodiment of the method, which is not repeated herein.

The processor 1601 may be any of the various types of processors mentioned above. The communication bus 1604 may be a peripheral component interconnect standard PCI bus or an extended industry standard architecture EISA bus or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 16, but this is not intended to represent only one bus or type of bus. A communication bus 1604 is used to enable connective communication between these components. The transceiver 1602 of the device in the embodiment of the present application is used for communicating signaling or data with other devices. Memory 1603 may be of the various types mentioned previously. The memory 1603 may optionally be at least one storage device remotely located from the processor 1601. A set of computer program codes or configuration information is stored in memory 1603 and processor 1601 executes programs in memory 1603. The processor may cooperate with the memory and the transceiver to perform any of the methods and functions of the terminal device of the embodiments of the above-mentioned application.

The embodiment of the present application further provides a chip system, where the chip system includes a processor, configured to support a terminal device or a network device to implement the functions involved in any of the foregoing embodiments, for example, to generate or process the DCI involved in the foregoing methods. In one possible design, the system-on-chip may further include a memory for necessary program instructions and data for the terminal device or the network device. The chip system may be constituted by a chip, or may include a chip and other discrete devices. The input and output of the chip system respectively correspond to the receiving and sending operations of the terminal device or the network device in the method embodiment.

The embodiment of the application further provides a processing device which comprises a processor and an interface. The processor may be adapted to perform the method of the above-described method embodiments.

It should be understood that the processing means may be a chip. For example, the processing device may be a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a digital signal processing circuit (DSP), a Microcontroller (MCU), a Programmable Logic Device (PLD), or other integrated chips.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software modules may be located in ram, flash, rom, prom, or eprom, registers, etc. as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete the steps of the method. To avoid repetition, it is not described in detail here.

It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capability. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

According to the method provided by the embodiment of the present application, the present application further provides a computer program product, which includes: computer program, which, when run on a computer, causes the computer to perform the method of any one of the embodiments shown in fig. 8.

According to the method provided by the embodiment of the present application, the present application further provides a computer-readable medium, which stores a computer program, and when the computer program runs on a computer, the computer is caused to execute the method of any one of the embodiments shown in fig. 8.

According to the method provided by the embodiment of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disc (DVD)), or a semiconductor medium (e.g., a Solid State Disc (SSD)), among others.

The network device in the foregoing various apparatus embodiments corresponds to the terminal device or the network device in the terminal device and method embodiments, and the corresponding module or unit executes the corresponding steps, for example, the receiving module and the sending module (transceiver) execute the steps of receiving or sending in the method embodiments, and other steps besides sending and receiving may be executed by the processing module (processor). The functionality of the specific modules may be referred to in the respective method embodiments. The number of the processors may be one or more.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps (step) described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

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

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

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a portable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for resource indication, comprising:

the method comprises the steps that a network device sends configuration information to a terminal device, wherein the configuration information is used for configuring a plurality of partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP in the plurality of BWPs;

the network equipment sends Downlink Control Information (DCI) to the terminal equipment, wherein the DCI comprises scheduling information and indication information, the scheduling information is used for scheduling the transmission of a Physical Downlink Shared Channel (PDSCH) or/and a Physical Uplink Shared Channel (PUSCH), and the indication information is used for determining whether rate matching resources on the plurality of BWPs can be used during the transmission of the PDSCH or/and the PUSCH.

2. A method for resource indication, comprising:

the method comprises the steps that a terminal device receives configuration information from a network device, wherein the configuration information is used for configuring a plurality of partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP in the plurality of BWPs;

the terminal equipment receives Downlink Control Information (DCI) from the network equipment, wherein the DCI comprises scheduling information and indication information, the scheduling information is used for scheduling transmission of a Physical Downlink Shared Channel (PDSCH) or/and a Physical Uplink Shared Channel (PUSCH), and the indication information is used for determining whether the rate matching resources on the plurality of BWPs can be used during transmission of the PDSCH or/and the PUSCH.

3. The method of claim 1 or 2, wherein the at least one rate-matching resource on each BWP is independently grouped into at least one group of rate-matching resources, the group of rate-matching resources on the plurality of BWPs is divided into at least one association, and the indication information is used to determine whether each of the at least one association can be used during the PDSCH or/and PUSCH transmission.

4. The method of claim 3, wherein the indication information includes a plurality of bits, one bit for each of the associated sets, the number of the plurality of bits being less than the number of sets of rate matching resource sets on the plurality of BWPs.

5. The method of claim 1 or 2, wherein the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, the indication information being used to determine whether each rate matching resource group on the plurality of BWPs can be used during the PDSCH or/and the PUSCH transmission.

6. The method of claim 5, wherein the indication information includes a number of bits, one bit for each of the set of rate-matching resources, the number of bits being equal to the number of sets of rate-matching resources on the plurality of BWPs.

7. The method of claim 1 or 2, wherein all rate matching resources over the multiple BWPs are jointly grouped into at least one set of rate matching resources, the indication information being used to determine whether each of the at least one set of rate matching resources can be used during the PDSCH or/and the PUSCH transmission.

8. The method of any of claim 7, wherein the indication information includes a plurality of bits, one bit for each of the set of rate matching resources, the number of the plurality of bits being equal to the number of sets of the at least one set of rate matching resources.

9. The method of any of claims 1-8, wherein the identities for the plurality of BWPs are different, the starting positions of the resource blocks RB for the plurality of BWPs are different, or the identities for the plurality of BWPs are the same, the starting positions of the resource blocks RB for the plurality of BWPs are different.

10. The method of any one of claims 1-9, wherein a first BWP and a second BWP are two BWPs of the plurality of BWPs, the first BWP and the second BWP having the same parameters, the parameters comprising at least one of: bandwidth, subcarrier spacing, the number of ports corresponding to sounding reference signals SRS, and the maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

11. The method of any of claims 1-10, wherein the subcarrier spacing of the rate-matched resources on the plurality of BWPs is the same.

12. The method according to any of claims 1-11, wherein the rate matching resources are resource block, RB, or symbol, symbol level rate matching resources, or wherein the rate matching resources are resource element, RE, level rate matching resources.

13. The method of any one of claims 1-12, wherein the terminal device is a low-capability terminal device.

14. A resource indication apparatus, comprising:

a sending module, configured to send configuration information to a terminal device, where the configuration information is used to configure a plurality of partial bandwidth BWPs, and each BWP in the plurality of BWPs is configured with at least one rate matching resource;

the sending module is further configured to send downlink control information DCI to the terminal device, where the DCI includes scheduling information and indication information, the scheduling information is used to schedule transmission of a physical downlink shared channel PDSCH or/and a physical uplink shared channel PUSCH, and the indication information is used to determine whether rate matching resources on the multiple BWPs can be used during transmission of the PDSCH or/and the PUSCH.

15. A resource indication apparatus, comprising:

a receiving module, configured to receive configuration information from a network device, where the configuration information is used to configure a plurality of partial bandwidth BWPs, and each BWP in the plurality of BWPs has at least one rate matching resource configured thereon;

the receiving module is further configured to receive downlink control information DCI from the network device, where the DCI includes scheduling information and indication information, the scheduling information is used to schedule transmission of a physical downlink shared channel PDSCH or/and a physical uplink shared channel PUSCH, and the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during transmission of the PDSCH or/and the PUSCH.

16. The apparatus of claim 14 or 15, wherein the at least one rate-matching resource on each BWP is independently grouped into at least one group of rate-matching resources, the group of rate-matching resources on the plurality of BWPs being divided into at least one association, the indication information being used to determine whether each of the at least one association can be used during the PDSCH or/and the PUSCH transmission.

17. The apparatus of claim 16, wherein the indication information comprises a plurality of bits, one bit for each of the associated sets, the plurality of bits being less than the number of sets of rate-matching resource sets on the plurality of BWPs.

18. The apparatus of claim 14 or 15, wherein the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, the indication information being used to determine whether each rate matching resource group on the plurality of BWPs can be used during the PDSCH or/and the PUSCH transmission.

19. The apparatus of claim 18, wherein the indication information comprises a plurality of bits, one bit for each of the set of rate-matching resources, the number of the plurality of bits being equal to the number of sets of rate-matching resources on the plurality of BWPs.

20. The apparatus of claim 14 or 15, wherein all rate matching resources on the plurality of BWPs are jointly grouped into at least one set of rate matching resources, the indication information being used to determine whether each of the at least one set of rate matching resources can be used during the PDSCH or/and PUSCH transmission.

21. The apparatus of claim 20, wherein the indication information comprises a plurality of bits, one bit for each of the set of rate matching resources, the number of the plurality of bits being equal to the number of sets of the at least one set of rate matching resources.

22. The apparatus of any one of claims 14-21, wherein the identifications for the plurality of BWPs are different, the starting positions of the resource blocks RB of the plurality of BWPs are different, or the identifications for the plurality of BWPs are the same, the starting positions of the resource blocks RB of the plurality of BWPs are different.

23. The apparatus of any one of claims 14-21, wherein a first BWP and a second BWP are two BWPs of the plurality of BWPs, the first BWP and the second BWP having the same parameters, the parameters comprising at least one of: bandwidth, subcarrier spacing, the number of ports corresponding to sounding reference signals SRS, and the maximum number of MIMO layers, where the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

24. The apparatus of any one of claims 14-23, wherein the subcarrier spacing of the rate-matched resources on the plurality of BWPs is the same.

25. The apparatus according to any of claims 14-24 wherein the rate matching resource is a resource block, RB, or symbol, symbol level rate matching resource or the rate matching resource is a resource element, RE, level rate matching resource.

26. An apparatus comprising a processor and a memory, the memory for storing a computer program, the processor running the computer program to cause the apparatus to perform the method of any of claims 1 to 13.

27. A chip, characterized in that it is a chip within a network device or a terminal device, said chip comprising a processor and an input interface and an output interface connected to said processor, said chip further comprising a memory in which the method of any of claims 1 to 13 is performed when a computer program is executed.

28. A computer-readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 13.

29. A computer program product, characterized in that it comprises a computer program which, when run on a computer, causes the computer to carry out the method of any one of claims 1 to 13.

30. A communication system, characterized in that the system comprises a network device and a network device, the network device performing the method of any one of claims 1, 3-13, and the terminal device performing the method of any one of claims 2-13.