WO2022242474A1

WO2022242474A1 - Resource indication method and related device

Info

Publication number: WO2022242474A1
Application number: PCT/CN2022/091469
Authority: WO
Inventors: 罗之虎; 金哲; 侯海龙; 曲韦霖
Original assignee: 华为技术有限公司
Priority date: 2021-05-21
Filing date: 2022-05-07
Publication date: 2022-11-24
Also published as: CN115379571A

Abstract

Disclosed in the embodiments of the present application are a resource indication method and a related device. The method comprises: a network device sending configuration information to a terminal device, wherein the configuration information is used for configuring a plurality of bandwidth parts (BWPs), and at least one rate matching resource is configured on each of the plurality of BWPs; and sending downlink control information (DCI) to the terminal device, 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) and/or 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 the transmission of the PDSCH and/or the PUSCH. By means of the embodiments of the present application, the transmission performance of a PDSCH or a PUSCH is ensured, and the efficiency of service transmission, which is performed on a rate matching resource, is improved.

Description

A resource indication method and related equipment

This application claims the priority of the Chinese patent application with the application number 202110555623.5 and the application title "A resource indication method and related equipment" submitted to the China Patent Office on May 21, 2021, the entire contents of which are incorporated in this application by reference middle.

technical field

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

Background technique

Partial bandwidth (bandwidth part, BWP) is a new concept proposed in the new radio (new radio, NR) standard. It is a continuous bandwidth resource allocated by network equipment to user equipment (UE), which can realize network equipment and Flexible transmission bandwidth configuration on the UE side. In addition, NR currently only supports rate matching on the physical downlink shared channel (PDSCH). Rate matching refers to the need to avoid unusable resources during PDSCH resource mapping, and only map on available resources. For low capability (reduced capability, REDCAP) UE, PDSCH and/or physical uplink shared channel (physical uplink shared channel, PUSCH) transmission may span multiple BWP or frequency positions, but because some resources need to be used for non-low capability (non-REDCAP) The transmission of data, control signals or reference signals of the UE, so the performance of PDSCH or PUSCH cannot be guaranteed, and services performed on rate matching resources are affected.

Contents of the invention

Embodiments of the present application provide a resource indication method and related equipment, which guarantee the transmission performance of PDSCH or PUSCH, and improve the transmission efficiency of services performed on rate matching resources.

In the first aspect, the embodiment of the present application provides a resource indication method, including: the network device sends configuration information to the terminal device, the configuration information is used to configure a plurality of partial bandwidth BWPs, and each BWP in the plurality of BWPs Configure at least one rate matching resource; send downlink control information DCI to the terminal device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule physical downlink shared channel PDSCH or/and physical uplink shared channel PUSCH and transmitting, the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH. In the case of coexistence of REDCAP terminal devices and non-REDCAP terminal devices, by notifying REDCAP terminal devices whether they can use rate matching resources on multiple BWPs during PDSCH or/and PUSCH transmission, so as to ensure the transmission performance of PDSCH or PUSCH, and Avoid affecting the services performed on the rate matching resources, and improve the transmission efficiency of the services performed on the rate matching resources.

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

In another possible design, the indication information includes multiple bits, one bit corresponds to one association group, and the number of the multiple bits is less than the number of rate matching resource groups on the multiple BWPs , by using one bit corresponding to one association group to reduce DCI overhead.

In another possible design, 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 the Whether each rate matching resource group on the multiple BWPs can be used. By indicating whether each rate matching resource group can be used during PDSCH or/and PUSCH transmission, the transmission performance of PDSCH or PUSCH is guaranteed, and the transmission efficiency of services performed on rate matching resources is improved.

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

In another possible design, all the 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 during the transmission of the PDSCH or/and the PUSCH Each rate matching resource group of the at least one rate matching resource group can be used. By indicating whether each rate matching resource group can be used during PDSCH or/and PUSCH transmission, the transmission performance of PDSCH or PUSCH is guaranteed, and the transmission efficiency of services performed on rate matching resources is improved.

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

In another possible design, the identifiers corresponding to the multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the identifiers corresponding to the multiple BWPs are the same, and the multiple BWPs The starting positions of the resource blocks RB are different.

In another possible design, the first BWP and the second BWP are two BWPs among the multiple BWPs, the parameters of the first BWP and the second BWP are the same, and the parameters include at least one of the following Items: bandwidth, subcarrier spacing, the number of ports corresponding to the sounding reference signal SRS, and the maximum number of multiple-input multiple-output 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 intervals of the rate matching resources on the multiple BWPs are the same.

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

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

In a second aspect, the embodiment of the present application provides a resource indication method, including: a terminal device receives configuration information from a network device, the configuration information is used to configure a plurality of partial bandwidth BWPs, and each of the plurality of BWPs Configure at least one rate matching resource on the BWP; receive downlink control information DCI from the network device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule the physical downlink shared channel PDSCH or/and the physical uplink shared channel For PUSCH transmission, the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH. By notifying REDCAP terminal devices whether they can use rate matching resources on multiple BWPs during PDSCH or/and PUSCH transmission, the transmission performance of PDSCH or PUSCH is guaranteed, and the business performed on rate matching resources is avoided, and the rate matching is improved. The transmission efficiency of the business performed on the resource.

In a third aspect, an embodiment of the present application provides a resource indication method, including: configuring a first active partial bandwidth BWP set ID and a first activated BWP ID on a network device, where the first activated BWP set ID is associated with a BWP set, and the The BWP set includes multiple BWPs, and the first activated BWP identifier is associated with one BWP in the BWP set; the network device sends configuration information to the terminal device, and the configuration information includes the first activated BWP set identifier and the The first activated BWP identifier, the first activated BWP set identifier is used to indicate the BWP set activated after RRC configuration or RRC reconfiguration is performed, and the first activated BWP identifier is used to indicate that the RRC configuration or RRC The BWP in the BWP set is activated after reconfiguration. Use the first activated BWP set identifier to indicate that one of the multiple BWP sets is activated after performing RRC configuration or RRC reconfiguration, and use the first activated BWP identifier to indicate that the BWP set is activated after performing RRC configuration or RRC reconfiguration A BWP of a terminal device enables the terminal device to determine the frequency domain position for 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: a terminal device receives configuration information sent by a network device, the configuration information includes a first activated BWP set identifier and a first activated BWP identifier, and the first activated The BWP set identifier is associated with a BWP set, and the BWP set includes multiple BWPs, and the first activated BWP identifier is associated with a BWP in the BWP set. The terminal device activates the BWP set according to the first activated BWP set identifier, and activates the BWP in the BWP set according to the first activated BWP identifier. Use the first activated BWP set identifier to indicate that one of the multiple BWP sets is activated after performing RRC configuration or RRC reconfiguration, and use the first activated BWP identifier to indicate that the BWP set is activated after performing RRC configuration or RRC reconfiguration A BWP of a terminal device enables the terminal device to determine the frequency domain position for downlink or uplink communication with the network device, thereby improving communication efficiency.

In the fifth aspect, the embodiment of the present application provides a resource indication method, including: a network device configuring a first activated BWP identifier and a starting RB location identifier of the first BWP, the first activated BWP identifier is associated with a BWP, and the first activated BWP identifier is associated with a BWP, and the first activated BWP identifier is associated with a BWP. The start RB position identifier of a BWP is associated with the start RB position of a BWP. The network device sends configuration information to the terminal device, where the configuration information includes the first activated BWP identifier and the starting RB position identifier of the first BWP, and the first activated BWP identifier is used to indicate that RRC configuration or RRC The BWP is activated after reconfiguration, and the start RB position identifier of the first BWP is used to indicate the start RB position for activating the BWP after performing RRC configuration or RRC reconfiguration.

The first activated BWP identifier indicates that the BWP is activated after performing RRC configuration or RRC reconfiguration, and the start RB position identifier of the first BWP indicates the start of the BWP after performing RRC configuration or RRC reconfiguration The RB position enables the terminal device to determine the frequency domain position for downlink or uplink communication with the network device, thereby improving communication efficiency.

In a sixth aspect, an embodiment of the present application provides a resource indication method, including: a terminal device receiving configuration information sent by a network device, where the configuration information includes a first activated BWP identifier and a starting RB location identifier of the first BWP, and the The first activated BWP identifier is associated with a BWP, and the start RB position identifier of the first BWP is associated with a start RB position of a BWP. The terminal device activates the BWP after performing RRC configuration or RRC reconfiguration according to the first activated BWP identifier, and activates the BWP after performing RRC configuration or RRC reconfiguration according to the initial RB position identifier of the first BWP The starting RB position of .

Use the first activated BWP identifier to indicate that the BWP is activated after performing RRC configuration or RRC reconfiguration, and use the first BWP start RB position identifier to indicate the start RB position of the BWP after performing RRC configuration or RRC reconfiguration , so that the terminal device can determine the frequency domain position for downlink or uplink communication with the network device, thereby improving communication efficiency.

In the seventh aspect, the embodiment of the present application provides a resource indication method, including: configuring a default BWP set identifier and a default BWP identifier on the network device, the default BWP set identifier is associated with a BWP set, and the BWP set includes multiple BWP , the default BWP identifier is associated with a BWP in the BWP set. The network device sends configuration information to the terminal device, where the configuration information includes the BWP set identifier and the default BWP identifier, and the default BWP set identifier is used to indicate that the BWP set is used after the BWP inactivation timer expires. The default BWP identifier is used to indicate to use the BWP in the BWP set after the BWP inactivation timer expires.

The default BWP set identifier indicates that the BWP set is used after the BWP inactivation timer expires, and the default BWP identifier indicates that the BWP in the BWP set is used after the BWP inactivation timer expires, so that the terminal device can determine The frequency domain position for downlink or uplink communication with network equipment, thereby improving communication efficiency.

In an eighth aspect, the embodiment of the present application provides a resource indication method, including: a terminal device receives configuration information sent by a network device, the configuration information includes a default BWP set identifier and a default BWP identifier, and the default BWP set identifier is associated with A BWP set, where the BWP set includes multiple BWPs, and the default BWP identifier is associated with a BWP in the BWP set. The terminal device uses the BWP set after the BWP inactivation timer expires according to the default BWP set identifier, and uses the BWP in the BWP set after the BWP inactivation timer expires according to the default BWP identifier.

In the ninth aspect, the embodiment of the present application provides a resource indication method, including: the network device configures a default BWP identifier and a default BWP start RB position identifier, the default BWP identifier is associated with a BWP, and the default BWP The start RB position identifies the default start RB position associated with the BWP. The network device sends configuration information to the terminal device, where the configuration information includes the default BWP identifier and the default BWP start RB position identifier, and the default BWP identifier is used to indicate that the default BWP identifier is used after the BWP inactivation timer expires. For the BWP, the default BWP start RB position identifier is used to indicate that the BWP default start RB position is used after the BWP inactivation timer expires.

The default BWP identifier indicates that the BWP is used after the BWP inactivation timer expires, and the default BWP start RB position identifier indicates that the default start RB position of the BWP is used after the BWP inactivation timer expires, so that The terminal device can determine the frequency domain position for downlink or uplink communication with the network device, thereby improving communication efficiency.

In the tenth aspect, the embodiment of the present application provides a resource indication method, including: the terminal device receives the configuration information sent by the network device, the configuration information includes a default BWP identifier and a default BWP start RB position identifier, the The default BWP identifier is associated with a BWP, and the default BWP start RB position identifier is associated with the default BWP start RB position. The terminal device uses the BWP after the BWP inactivation timer expires according to the default BWP identifier, and uses the BWP after the BWP inactivation timer expires according to the default BWP start RB position identifier. The default starting RB position.

In the eleventh aspect, the embodiment of the present application provides a resource indication device, the resource indication device is configured to implement the above-mentioned first aspect, the third aspect, the fifth aspect, the seventh aspect and the ninth aspect performed by the network device The methods and functions are realized by hardware/software, and the hardware/software includes modules corresponding to the above-mentioned functions.

In the twelfth aspect, the embodiment of the present application provides a resource indication device, the resource indication device is configured to implement the above-mentioned second aspect, the fourth aspect, the sixth aspect, the eighth aspect and the tenth aspect performed by the terminal device The methods and functions are realized by hardware/software, and the hardware/software includes modules corresponding to the above-mentioned functions.

In a thirteenth aspect, the present application provides a resource indication device, which may be a network device, or a device in the network device, or a device that can be used in conjunction with the network device. Wherein, the resource indication device may also be a system-on-a-chip. The resource indicating device can execute the methods described in the first aspect, the third aspect, the fifth aspect, the seventh aspect and the ninth aspect. The function of the resource indicating device may be implemented by hardware, or may be implemented by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. This module can be software and/or hardware. For the operations and beneficial effects performed by the resource indication device, reference may be made to the methods and beneficial effects described in the first, third, fifth, seventh, and ninth aspects above, and repeated descriptions will not be repeated.

In a fourteenth aspect, the present application provides a device for indicating resources. The device may be a terminal device, or a device in the terminal device, or a device that can be matched with the terminal device. Wherein, the resource indication device may also be a system-on-a-chip. The resource indicating device can execute the methods described in the second aspect, the fourth aspect, the sixth aspect, the eighth aspect and the tenth aspect. The function of the resource indicating device may be implemented by hardware, or may be implemented by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. This module can be software and/or hardware. For the operations and beneficial effects performed by the resource indicating device, reference may be made to the methods and beneficial effects described in the second, fourth, sixth, eighth, and tenth aspects above, and repeated descriptions will not be repeated.

In a fifteenth aspect, the present application provides a resource indication device, the resource indication device includes a processor, and when the processor invokes a computer program in the memory, as described in any one of the first to tenth aspects The method described above is executed.

In a sixteenth aspect, the present application provides a resource indicating device, the resource indicating device includes a processor and a memory, the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory, The resource indicating device is configured to execute the method according to any one of the first aspect to the tenth aspect.

In a seventeenth aspect, the present application provides a resource indication device, the resource indication device includes a processor, a memory, and a transceiver, the transceiver is used to receive a channel or a signal, or send a channel or a signal; the memory , for storing a computer program; the processor, for invoking the computer program from the memory to execute 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 device, the resource indication device includes a processor and an interface circuit, the interface circuit is used to receive a computer program and transmit it to the processor; the processor operates The computer program is used to execute the method described in any one of the first aspect to the tenth aspect.

In a nineteenth aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium is used to store a computer program, and when the computer program is executed, any A described method is implemented.

In a twentieth aspect, the present application provides a computer program product including a computer program. When the computer program is executed, the method described in any one of the first aspect to the tenth aspect is implemented.

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

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiment of the present application or the background art, the following will describe the drawings that need to be used in the embodiment of the present application or the background art.

FIG. 1 is a schematic structural diagram of a communication system provided by 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 transmission;

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

FIG. 8 is a schematic flowchart of a resource indication method provided by an embodiment of the present application;

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

FIG. 10 is a schematic diagram of another rate matching resource indication provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another rate matching resource indication provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of another rate matching resource indication provided by the embodiment of the present application;

Fig. 13 is a schematic structural diagram of a resource indication device provided by an embodiment of the present application;

Fig. 14 is a schematic structural diagram of another resource indication device provided by an embodiment of the present application;

FIG. 15 is a schematic structural diagram of a network device provided by an embodiment of the present application;

FIG. 16 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

As shown in FIG. 1 , FIG. 1 is a schematic structural diagram of a communication system 100 provided in an embodiment of the present application. The communication system 100 may include a network device 110 and terminal devices 101 - 106 . It should be understood that more or less network devices or terminal devices may be included in the communication system 100 to which the method of the embodiment of the present application can be applied. A network device or a terminal device may be hardware, or functionally divided software, or a combination of the above two. Network devices and terminal devices can communicate through other devices or network elements. In the communication system 100, the network device 110 can send downlink data to the terminal device 101-106. Of course, the terminal devices 101 - 106 may also send uplink data to the network device 110 . Terminal equipment 101～terminal equipment 106 can be cellular phone, smart phone, portable computer, handheld communication device, handheld computing device, satellite radio device, global positioning system, palm computer (personal digital assistant, PDA) and/or be used in wireless Any other suitable device for communicating over the communication system 100, and the like. The network device 110 may be a long term evolution (long term evolution, LTE) and/or NR network device, specifically a base station (NodeB), an evolved base station (eNodeB), a base station in a 5G mobile communication system, a next-generation mobile Communication base station (Next generation Node B, gNB), the base station in the future mobile communication system or the access node in the Wi-Fi system.

The communication system 100 may adopt public land mobile network (public land mobile network, PLMN), vehicle networking (vehicle to everything, V2X), device-to-device (device-to-device, D2D) network, machine to machine (machine to machine, M2M) network, Internet of things (IoT) or other networks. In addition, terminal devices 104 to 106 may also form a communication system. In the communication system, the terminal device 105 can send downlink data to the terminal device 104 or the terminal device 106 . The method in the embodiment of the present application may be applied to the communication system 100 shown in FIG. 1 .

According to the types of services supported by the terminal equipment, the terminal equipment can be divided into multiple types of terminals. For example, a terminal device that supports a service requiring a higher data transmission rate may be called a first-type terminal device, and relatively speaking, a terminal device that supports a service that requires a lower data transmission rate may be called a second-type terminal device. Compared with the first type of terminal equipment, the second type of terminal equipment can be regarded as a terminal equipment with lower complexity or lower capability. The complexity is lower, such as narrower supported bandwidth, lower power consumption, fewer antennas, etc.

In this embodiment of the present application, the terminal device of the first type may also be called a normal terminal device, or a terminal device with legacy capability or/normal capability/high capability, and may also be called a legacy terminal device or a legacy (legacy) terminal device. The second type of terminal equipment can be called low-complexity or low-capability (Reduced CAPability, REDCAP) terminal equipment, reduced capability terminal equipment, mMTC UE, or (NR light, NRL) terminal equipment, that is, a lightweight version Terminal Equipment. The terminal device in this embodiment of the present application may be a first-type terminal device, or may be a second-type terminal device.

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

1. Different bandwidth capabilities. 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, the first type of terminal equipment can support the simultaneous use of 100MHz frequency domain resources and network equipment on one carrier at the same time, while the second type of terminal equipment can support the simultaneous use of 20MHz or less than 20MHz frequency domain resources on one carrier at the same time communicate with network devices. For example, the second type of terminal equipment can support communication with network equipment by simultaneously using 10 MHz or 5 MHz frequency domain resources on one carrier.

2. The number of 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, the first type of terminal equipment may support 4 receiving and 2 transmitting (4 receiving antennas and 2 transmitting antennas). The second type of terminal equipment can support 2 reception and 1 transmission (2 reception antennas and 1 transmission antenna), or 1 reception and 1 transmission (1 reception antenna and 1 transmission antenna). It can be understood that, under the condition of achieving the same data transmission rate, since the number of receiving and transmitting antennas of the second type of terminal equipment is less than the number of transmitting and receiving antennas of the first type of terminal equipment, the connection between the second type of terminal equipment and the base station The maximum coverage that can be achieved by data transmission is smaller than the maximum coverage that can be achieved by data transmission between the first type of terminal equipment and the base station.

3. The maximum uplink transmit power is different. The maximum uplink transmit power of the first type of terminal device is greater than the maximum uplink transmit power of the second type of terminal device.

4. The protocol version is different. The first type of terminal device may be a terminal device in NR release 15 (release-15, Rel-15) or NR release 16 (release-16, Rel-16). The second type of terminal equipment can be considered as terminal equipment in NR version 17 (release-17, Rel-17) or later versions of NR Rel-17.

5. Carrier aggregation (CA) capabilities are different. For example, the first type of terminal device may support carrier aggregation, but the second type of terminal device does not support carrier aggregation; for another example, both the second type of terminal device and the first type of terminal device support carrier aggregation, but the first type of terminal device supports carrier aggregation at the same time The maximum number of cells of the carrier aggregation is greater than the maximum number of cells of the carrier aggregation supported by the terminal device of the second type at the same time.

6. Different frequency division duplex (FDD) capabilities. For example, the first type of terminal equipment supports full-duplex FDD, while the second type of terminal equipment only supports half-duplex FDD.

7. The ability to process data is different. For example, the minimum delay between receiving downlink data and sending feedback on the downlink data for the first type of terminal equipment is less than the time delay between receiving downlink data and sending the downlink data for the second type terminal equipment. Minimum delay between feedbacks. And/or, the minimum time delay between the first type of terminal device sending the uplink data and receiving the feedback on the uplink data is smaller than the minimum time delay between the second type of terminal device sending the uplink data and receiving the feedback on the uplink data.

8. Different processing capabilities (ability/capability). 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 following: the maximum number of MIMO layers supported by the terminal device for data transmission, the number of HARQ processes supported by the terminal device, and the maximum transmission block size (transmission block size, TBS) supported by the terminal device.

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

10. The buffer size is different. The cache buffer can be understood as the total size of the Layer 2 (Layer 2, L2) cache, which is defined as the word buffered by the terminal device in the radio link control (radio link control, RLC) transmission window and reception and reordering window for all radio bearers. The sum of the number of sections and the number of bytes buffered in the Packet Data Convergence Protocol (PDCP) reordering window. Alternatively, the cache buffer can also be understood as the total number of soft channel bits that can be used for Hybrid Automatic Repeat reQuest (HARQ) processing.

Of course, the above are only examples, and there may be other differences between the first type of terminal equipment and the second type of terminal equipment. In addition to the previous differences above, there may be other differences. For example, the first type of terminal equipment does not support coverage enhancement, while the second type of terminal equipment supports coverage enhancement; The device supports small packet transmission, so we will not give examples one by one here.

(1) REDCAP.

The fifth-generation (the Fifth-Generation, 5G) mobile communication technology NR is a global 5G standard based on a new air interface design based on orthogonal frequency division multiplexing (OFDM), and it is also a very important next-generation cellular mobile Technical basis, the business of 5G technology is very diverse, which can be oriented to enhanced mobile broadband (eMBB) business, ultra-reliable low-latency communication (ultra-reliability low-latency communication, URLLC) business and large-scale machine communication (massive machine-type communication (mMTC) service, where the mMTC service may be an industrial wireless sensor network (industrial wireless sensor network, IWSN) service, a video surveillance (video surveillance) service, or a wearables (wearables) service, etc.

Machine-type terminal equipment often has higher requirements on cost and power consumption. For example, machine-type terminal devices are generally implemented at low cost, because services in application scenarios corresponding to machine-type terminal devices do not require high data transmission rates. For example, the data transmission rate carried by sensors under IWSN is not greater than 2Mbps, which is sufficient for IWSN services. The data transmission rate carried by economical video surveillance cameras is generally 2-4Mbps. The rate does not exceed 150Mbps, and its uplink peak rate does not exceed 50Mbps, which is much lower than the peak rate of legacy terminal equipment (such as NR eMBB terminal equipment). Based on this, the machine-type terminal equipment can reduce the implementation specifications compared with the legacy terminal equipment, thereby reducing the implementation cost. On the other hand, reducing the implementation cost of machine-type terminal equipment will also help expand the market for machine-type terminal equipment. At present, 3GPP has launched research on REDCAP terminal equipment under the NR system, aiming at the growing IoT market, such as the above-mentioned IWSN, video surveillance and wearable services, to design an Low/implementation of low-complexity terminal devices to expand the application of NR systems in the IoT market. For ease of description, in the following part of this document, REDCAP terminal equipment is used as an example for illustration.

One way to reduce the cost of terminal equipment is to reduce the channel bandwidth of the terminal equipment, which can also be understood as reducing the bandwidth capability of the terminal equipment, that is, the bandwidth capability of the REDCAP terminal equipment can be much smaller than the bandwidth capability of the legacy terminal equipment. At present, legacy terminal equipment such as version Rel-15/version Rel-16 terminal equipment must have a bandwidth capability of 100MHz, while REDCAP terminal equipment can receive the initial access signal sent by the NR base station and then access the NR system. , its bandwidth requirement can be only 20MHz. Under certain NR system configurations, the bandwidth capability of REDCAP terminal equipment can be further reduced, such as 5MHz or 10MHz. At this time, REDCAP terminal equipment can also access the NR system. Compared with the bandwidth capability of 100MHz, the bandwidth capability not greater than 20MHz can greatly reduce the cost of REDCAP terminal equipment.

In addition to bandwidth reduction, REDCAP terminal equipment can also reduce the number of receiving antennas compared with legacy terminal equipment within the same frequency band. For example, in a frequency band where a legacy terminal device supports two receiving antennas, a REDCAP terminal device can support one receiving antenna; in a frequency band where a legacy terminal device supports four receiving antennas, a REDCAP terminal device can support one receiving antenna, or Supports 2 receiving antennas. Reducing the number of receiving antennas can also greatly reduce the cost of REDCAP terminal equipment.

(2) BWP.

BWP is a new concept proposed in the NR standard. It is a continuous bandwidth resource configured by the network device to the UE, which can realize the flexible transmission bandwidth configuration of the network device and the UE. BWP is a UE-level concept, and different UEs can be configured with different BWPs. The network device may configure one or more downlink BWPs for the terminal device, the BWPs are composed of continuous physical resource blocks (physical resource blocks, PRBs) in the frequency domain, and the BWPs are a subset within 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 (identification, ID). The system may configure one or more BWPs for the terminal device, and the multiple BWPs may overlap in the frequency domain. As shown in Figure 2, the system can configure four BWPs for terminal equipment, 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 for PDSCH. Rate matching refers to the need to avoid unusable resources during PDSCH resource mapping, and only map on available resources. Among them, resources refer to time domain and frequency domain resources, which can be resource blocks. (resource block, RB) and symbols (symbol), can also be resource elements (resource element, RE).

NR introduces a rate matching mechanism for the following scenarios:

Scenario 1: Forward compatibility, NR needs to configure some time domain and frequency domain resources as resources that cannot be used by PDSCH, and these resources are used to support new functions in the future.

Scenario 2: NR and LTE coexist. NR needs to configure some time domain and frequency domain resources as resources that cannot be used by PDSCH. This resource can be long term evolution (long term evolution, LTE) reference signal and multimedia broadcast multicast single frequency network (multimedia broadcast multicast service single frequency network, MBSFN) resources occupied by subframes, in this way, mutual interference between LTE and NR PDSCH can be avoided.

Scenario 3: NR reference signal measurement. The NR system introduces reference signals for interference and radio resource management (Radio Resource Management, RRM) measurement. In order to ensure measurement performance, NR needs to configure part of the time domain and frequency domain resources as PDSCH cannot Resources used that can be used to transmit reference signals for measurements.

Scenario 4: NR PDCCH and PDSCH are multiplexed, and NR needs to configure some time domain and frequency domain resources as resources that cannot be used by PDSCH, and these resources are used for PDCCH transmission.

For REDCAP terminal devices, the above scenarios still exist, so it is necessary for REDCAP terminal devices to support the rate matching mechanism. In addition to the above scenarios, REDCAP terminal devices also need to consider the following scenarios:

Scenario 5: Coexistence of REDCAP terminal devices and non-REDCAP terminal devices. REDCAP terminal devices need to configure some time domain and frequency domain resources as resources that cannot be used by REDCAP PDSCH. These resources are used for non-REDCAP UE data, control signals or Transmission of reference signals. Among them, the Non-REDCAP terminal equipment can be NR eMBB or URLLC UE.

According to the granularity of configuration resources, NR supports two types of rate matching configuration schemes.

The first is RB/symbol level rate matching. That is, the minimum granularity of the resources configured for rate matching in the frequency domain is 1 RB, and the minimum granularity in the time domain is one OFDM symbol. A network device may configure a BWP-level or cell-level rate match pattern (rate match pattern) through radio resource control (radio resource control, RRC) signaling. Each BWP can configure up to 4 rate match patterns, and each rate match pattern is associated with a rate match pattern ID. These rate match patterns can be divided into two groups at most, and these two groups can be called rateMatchPatternGroup1 and rateMatchPatternGroup2. rateMatchPatternGroup1 or rateMatchPatternGroup2 contains at least one rate match pattern. In addition, the network device can dynamically indicate whether the PDSCH can use the resource set corresponding to rateMatchPatternGroup1 or rateMatchPatternGroup2 through the DCI.

Each rate match pattern contains a frequency domain resource bitmap (bitmap) and a time domain resource bitmap. 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, and the time domain range corresponding to the time domain resource bitmap is one One time slot or two time slots, that is, the number of bits occupied by the domain resource bitmap is 14 or 28. In addition to these two bitmaps, the rate match pattern also contains a periodic pattern bitmap, each bit in the bitmap is used to indicate whether the above time domain resource bitmap is valid, the corresponding time domain range of the periodic pattern bitmap and The above time domain resource bitmap is the same. In addition to the above bitmap indication, the rate match pattern can also include a control resource set (control-resource set, CORESET) ID indication, PDSCH cannot use the frequency domain resources of the CORESET with the CORESET ID, and the search space associated with the CORESET A resource set composed of certain time-domain resources.

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 a time slot, and the bitmap indication is 10000000000001, which means that the PDSCH in a time slot cannot use the first and last symbols. The period pattern bitmap indicates 10, each bit represents a time slot, and the bit length of the bitmap is 2, so the period is 2 time slots, that is to say, every two time slots in the time domain are indicated by this bitmap cycle down. The first bit in the periodic pattern bitmap indication is 1, indicating that the first time slot in every two time slots is indicated by the time domain resource bitmap, that is, the PDSCH in the first time slot in every two time slots is not available Using the first and last symbols, the first bit in the periodic pattern bitmap indication is 0, indicating that PDSCH can use symbols in the second slot of every two slots, that is to say, every two slots The second time slot is not indicated according to the time domain resource bitmap.

As shown in FIG. 4, FIG. 4 is a schematic diagram of another rate matching pattern configuration. From the time domain and frequency domain dimensions, 4 rate match patterns are configured in the BWP with BWP ID=1, and the corresponding rate match pattern IDs are 1, 2, 3, 4. These patterns are divided into two groups, and rateMatchPatternGroup1 includes rate match rate match pattern with

pattern ID

1 and 2, rateMatchPatternGroup2 contains rate match pattern with rate

match pattern ID

3 and 4, DCI contains 2 bits, the first bit indicates whether PDSCH can use the resource set corresponding to rateMatchPatternGroup1, the second The bit indicates whether the PDSCH can use the resource set corresponding to rateMatchPatternGroup2.

The second is RE-level rate matching. That is, the minimum granularity of the resources configured for rate matching in the time domain and the frequency domain is one RE. Network devices can configure aperiodic (aperiodic) zero power (zero power, ZP) channel state information reference signal (channel state information reference signal, CSI-RS) resource set, semi-persistent (semi-persistent) ZP CSI on each BWP -RS resource set and periodic (periodic) ZP CSI-RS resource set, and a maximum of 16 ZP CSI-RS resources are configured in each resource set. The periodic ZP CSI-RS resource set takes effect after the configuration is completed. The aperiodic ZP CSI-RS resource set and the semi-persistent ZP CSI-RS resource set need to be used in conjunction with trigger signaling or activation signaling. After receiving the trigger signaling or activation command to take effect. For the REs indicated by the periodic ZP CSI-RS resource set, the PDSCH cannot 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 cannot be used after receiving a trigger or activation instruction.

A maximum of 3 aperiodic ZP CSI-RS resource sets can be configured in each BWP. The DCI carries the aperiodic CSI-RS trigger field. The number of bits in this field is the number of aperiodic ZP CSI-RS resource sets configured. bits. The value of this field is "00", which means that aperiodic ZP CSI-RS is not triggered; the value of this field is "01", which means that the CSI-RS resource set corresponding to ZP-CSI-RS-ResourceSetIds=1 is triggered; A value of "10" means triggering the CSI-RS resource set corresponding to ZP-CSI-RS-ResourceSetIds=2; a value of "11" means triggering a CSI-RS resource set corresponding to ZP-CSI-RS-ResourceSetIds=3 Collection of resources. As shown in Figure 5, Figure 5 is a schematic diagram of a ZP CSI-RS in a time slot and an RB, and there are 3 REs in the RB and time slot that cannot be used by the PDSCH.

Among them, the configuration parameters of ZP CSI-RS include: zp-CSI-RS-ResourceId, which is used to determine the ZP CSI-RS resource configuration identifier; nrofPorts, which is used to define the number of ports of CSI-RS; cdm-Type, which defines the CDM value and Pattern; resourceMapping, which defines the OFDM symbol and subcarrier position occupied by ZP CSI-RS in a slot. periodicityAndOffset, indicating the periodicity and the period of the semi-persistent ZP CSI-RS and the slot offset.

As shown in Figure 6, Figure 6 is a schematic diagram of legacy NR PDSCH and PUSCH transmission. The PDSCH and PUSCH transmissions are completed within one BWP, the PDSCH supports interleaved transmission within the frequency range corresponding to the BWP, and the PUSCH supports frequency hopping transmission within the frequency range corresponding to the BWP. Among them, the BWP bandwidth does not exceed the UE bandwidth capability. For legacy UEs, the BWP bandwidth can be up to 100MHz.

For REDCAP terminal equipment, the maximum BWP bandwidth capability is 20MHz. According to the existing framework, REDCAP terminal equipment can only transmit PDSCH and PUSCH within its own BWP range. Compared with NR legacy terminal equipment, due to the reduced BWP bandwidth range, the frequency diversity gain obtained by REDCAP terminal equipment is reduced. In order to obtain the same frequency diversity gain as NR legacy terminal equipment, REDCAP UE needs to support frequency hopping in a wider range. As shown in Figure 7, Figure 7 is a schematic diagram of transmission of REDCAP PDSCH and PUSCH at different frequency positions. PDSCH/PUSCH are transmitted in two 20MHz BWPs or frequency positions respectively.

To sum up, REDCAP differs from legacy NR in the following points: First, legacy NR PDSCH/PUSCH is only transmitted within one BWP, while a transmission of REDCAP PDSCH/PUSCH may span multiple BWPs or frequency locations. Second, only PDSCH supports rate matching in legacy NR. Compared with legacy NR, REDCAP requires one more scenario for rate matching, namely scenario 5, that is, the coexistence of REDCAP terminal devices and non-REDCAP terminal devices. Among them, non-REDCAP terminal devices can be understood as legacy terminal devices. In order to avoid REDCAP and legacy The interaction between NR, REDCAP PUSCH also needs to support rate matching.

For a REDCAP terminal device, resources to be avoided for one transmission of the PDSCH/PUSCH on different BWPs or frequency positions are different. How to notify the REDCAP terminal equipment of the rate match pattern (rate match pattern) of multiple BWPs or frequency positions is an urgent problem to be solved.

In addition, the network device is configured with N BWP sets, and each BWP set in the N BWP sets is configured with M BWPs, and the identifiers of the M BWPs are different. Alternatively, the network device configures N BWPs, and each BWP corresponds to a BWP identifier and M starting RB positions. Wherein, M and N are both positive integers. For a BWP set, or M starting RB positions corresponding to a BWP, how the terminal device determines the frequency domain position for downlink or uplink communication with the network device is a problem that needs to be solved.

As shown in FIG. 8 , FIG. 8 is a schematic flowchart of a resource indication method provided by an embodiment of the present application. The steps in the embodiment 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 at least one rate matching resource is configured on each of the multiple BWPs.

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

Wherein, the identifiers corresponding to the multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the identifiers corresponding to the multiple BWPs are the same, and the start positions of the resource blocks RB of the multiple BWPs are The location is 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 the following: bandwidth, subcarrier spacing, sounding reference signal ( The number of ports corresponding to the sounding reference signal (SRS), the maximum number of multiple-input multiple-output (multiple-input multiple-output, MIMO) layers, wherein the maximum number of MIMO layers is the maximum number of MIMO layers used by the PDSCH.

Wherein, the subcarrier intervals of the rate matching resources on the multiple BWPs are the same.

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

Wherein, multiple 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 (switching) or tuning (retuning) or frequency hopping (hopping). The first delay is less than the second delay, where the second delay is the BWP switching delay supported by the NR terminal device, that is, T _{BWPswitchDelay} time slots, as shown in Table 1. The value of T _{BWPswitchDelay} is determined according to the capability of the terminal equipment and the subcarrier spacing. The capability of the terminal device may be Type 1 or Type 2, and the terminal device reports to the network device. The value of μ corresponds to the subcarrier spacing, which is configured by the network device. The subcarrier intervals Δf and ^μ satisfy: Δf=2μ·15[kHz]. For example, assuming that μ is 0, the capability of the terminal equipment is Type1, and the subcarrier spacing before and after BWP switching is the same, according to Table 1, T _{BWPswitchDelay} is 1, then the BWP switching delay is T _{BWPswitchDelay} multiplied by μ is 0 corresponding to Slot length = 1 x 1 ms = 1 ms.

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 a rate matching pattern ID.

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

In the first optional manner, the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the rate matching resource groups on the multiple BWPs are divided into at least one association group, and the indication Information for determining whether each of said at least one association group can be used during said PDSCH and/or said PUSCH transmission. Among them, there is an association relationship between the rate matching resource groups on multiple BWPs, and one or more rate matching resource groups with the association relationship are divided into an association group, and the association relationship can be pre-agreed or pre-configured by the network device .

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

For example, as shown in Figure 9, the network device is configured with two BWPs, and the corresponding BWP IDs are BWP ID=0 and BWP ID=1. The BWP with BWP ID=0 is called BWP#0 for short, and the BWP with BWP ID=1 Abbreviated as BWP#1. Both BWP#0 and BWP#1 are configured with 4 rate matching resources, corresponding to four rate match patterns, and the rate match pattern IDs are 1, 2, 3 and 4 respectively. The rate matching resources on each BWP are grouped in an independent grouping manner. Both BWP#0 and BWP#1 are divided into two rate matching resource groups, including rate matching resource 1 (rate match pattern ID=1) and rate matching resource 2 (rate match pattern ID=2) belongs to rate matching resource group 1 (group1), rate matching resource 3 (rate match pattern ID=3) and rate matching resource 4 (rate match pattern ID=4) belong to rate matching resource group 2 (group2). 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 group1 on BWP#0 and group1 on BWP#1 are divided into an association group1. It is agreed in advance that group2 on BWP#0 and group2 on BWP#1 have an association relationship, and group2 on BWP#0 and group2 on BWP#1 are divided into another association group2. The number of bits included in the rate matching indication information in the DCI is 2, which is less 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, indicating that the PDSCH or PUSCH scheduled by the DCI cannot 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, indicating that the PDSCH or PUSCH scheduled by the DCI can use the rate matching resources corresponding to group2 on BWP#0 and group2 on BWP#1.

The 0 and 1 in the indication information can also be reversely indicated, that is, the first bit in the indication information is 1, indicating that the PDSCH or PUSCH scheduled by the DCI can use group1 on BWP#0 and group1 on BWP#1 to correspond rate matching resource. The second bit in the indication information is 0, indicating that the PDSCH or PUSCH scheduled by the DCI cannot 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 association relationships between rate matching resource groups on multiple BWPs. Configure group1 and group2 on BWP#0 and group1 on BWP#1 as an association group 1, and configure group2 on BWP#1 as another association group 2. The indication information in the DCI includes 2 bits, and each bit corresponds to an association group. The first bit in the indication information is 1, indicating that the PDSCH or PUSCH scheduled by the DCI cannot 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, indicating that the PDSCH or PUSCH scheduled by the DCI can 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 the PDSCH or/and the PUSCH can be used during transmission. Each rate-matching resource group on multiple BWPs.

Wherein, the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the number of rate matching resource groups on the multiple BWPs. The correspondence between the bits of the indication information and the rate matching resource groups may be preset. For example, first follow the order of BWP ID from small to large, and then follow the order of group numbers from small to large, corresponding to the bits in the indication information, that is, the first bit of the indication information corresponds to BWP#0group1, the second bit It corresponds to BWP#0group2, the third bit corresponds to BWP#1group1, and the fourth bit corresponds to BWP#1group2. Alternatively, it may first correspond to the bits in the indication information in the ascending order of the BWP ID, and then in the ascending order of the group numbers. That is to say, the first bit of the indication information corresponds to BWP#0group2, the first bit corresponds to BWP#0group1, ... and other corresponding relationships are similar to this, and examples will not be given here.

As shown in Figure 11, the network device is configured with two BWPs. The BWP IDs are BWP ID=0 and BWP ID=1. The BWP with BWP ID=0 is called BWP#0 for short, and the BWP with BWP ID=1 is called BWP# for short. 1. Both BWP#0 and BWP#1 are configured with 4 rate matching resources, corresponding to four rate match patterns, and the rate match pattern IDs are 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 divided into two rate matching resource groups, including rate matching resource 1 (rate match pattern ID=1) and rate matching resource 2 (rate match pattern ID=2) belongs to rate matching resource group 1 (group1), rate matching resource 3 (rate match pattern ID=3) and rate matching resource 4 (rate match pattern ID=4) belong to rate matching resource group 2 (group2). The number of bits included in the indication information in the DCI is 4, which is equal to the total group number 4 included in BWP#0 and BWP#1. The 4 bits in the DCI are in one-to-one correspondence with the rate matching resource groups. The corresponding relationship is first determined in the order of BWP ID from small to large, and then according to the order of group numbers from small to large, that is, 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. Wherein, a bit value of 1 indicates that the rate matching resource group corresponding to the bit cannot be used during PDSCH/PUSCH transmission; a bit value of 0 indicates that the rate matching resource group corresponding to the bit can be used during PDSCH/PUSCH transmission. 0 and 1 can also be reversed, that is, a bit value of 1 indicates that the rate matching resource group corresponding to this bit can be used during PDSCH/PUSCH transmission, and a bit value of 0 indicates that the rate corresponding to this bit cannot be used during PDSCH/PUSCH transmission Match resource group.

Optionally, the network device may preconfigure group information, where the group information includes at least one rate matching resource group. All rate matching resources on the multiple BWPs are jointly grouped into at least one rate matching resource group, and the indication information included in the DCI is used to determine whether the PDSCH or/and the PUSCH can be used during transmission Each rate matching resource group in the at least one rate matching resource group.

Wherein, 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.

For example, as shown in Figure 12, the network device is configured with two BWPs. The BWP IDs are BWP ID=0 and BWP ID=1. The BWP with BWP ID=0 is called BWP#0 for short, and the BWP with BWP ID=1 is called BWP #1. Both BWP#0 and BWP#1 are configured with 4 rate matching resources, corresponding to four rate match patterns, and the rate match pattern IDs are 1, 2, 3 and 4 respectively. Use joint grouping to group the rate matching resources on the two BWPs, the rate match pattern IDs on BWP#0 are 1, 2, 3, 4 and the rate match pattern IDs on BWP#1 are 1, 2 rate matching resources It is rate matching resource group 1 (group1), the rate match pattern ID on BWP#1 is 3, and the rate matching resource of 4 is rate matching resource group 2 (group2). The number of bits included in the indication information in the DCI is 2, which is equal to the number 2 of the rate matching resource groups. Wherein, a bit value of 1 indicates that the rate matching resource corresponding to the bit cannot be used during PDSCH/PUSCH transmission, and a bit value of 0 indicates that the rate matching resource corresponding to the bit can be used during PDSCH/PUSCH transmission. 0 and 1 can also be reversed, that is, a bit value of 1 indicates that the rate matching resource corresponding to the bit can be used during PDSCH/PUSCH transmission, and a bit value of 0 indicates that the rate matching resource corresponding to the bit cannot be used during PDSCH/PUSCH transmission resource.

Wherein, the rate matching resource is a resource block RB or a 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. For the configuration method of the rate matching resource in the embodiment of this application, refer to the above configuration method of the rate matching resource. I won't repeat them here.

In the embodiment of this application, in the case of coexistence of REDCAP terminal equipment and non-REDCAP terminal equipment, the PDSCH is guaranteed by notifying the REDCAP terminal equipment whether it can use rate matching resources on multiple BWPs during PDSCH or/and PUSCH transmission. or the transmission performance of the PUSCH, and avoid affecting the services performed on the rate matching resources, and improve the transmission efficiency of the services performed on the rate matching resources.

If the network device is configured with N BWP sets, each BWP set in the N BWP sets is configured with M BWPs, and the identifiers of the M BWPs are different. Alternatively, the network device configures N BWPs, and each BWP corresponds to a BWP identifier and M starting RB positions. The following describes how the terminal device determines the frequency domain position for downlink or uplink communication with the network device under the above circumstances.

The network device is configured with a first activated BWP set identifier, and the first activated BWP set identifier is associated with a BWP set. The BWP set identified by the first activated BWP set is activated after performing RRC configuration or RRC reconfiguration (to be activated upon performing the RRC(re-)configuration). In addition, the network device is also configured with a first activated BWP identifier, and the first activated BWP identifier is associated with a BWP. The BWP may be a BWP in the BWP set associated with the first activated BWP set identifier. The BWP identified by the first activated BWP is activated after performing RRC configuration or RRC reconfiguration (to be activated upon performing the RRC(re-)configuration). Correspondingly, the terminal device receives the first activated BWP set identifier and the first activated BWP identifier configured by the network device. The activated BWP set is determined according to the first activated BWP set identifier, and the activated BWP is determined according to the first BWP set identifier. 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 here is an uplink BWP or a downlink BWP. The flags mentioned above also need to be configured separately for downlink and uplink. For the above-mentioned 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 the following: bandwidth, subcarrier spacing, sounding reference The number of ports corresponding to a signal (sounding reference signal, SRS), and the maximum number of multiple-input multiple-output (multiple-input multiple-output, MIMO) layers, where the maximum number of MIMO layers is the maximum number of MIMO layers 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 (switching) or tuning (retuning) or frequency hopping (hopping). The first time delay is less than the second time delay, wherein the second time delay is the BWP switching delay supported by the NR terminal equipment, that is, T _{BWPswitchDelay} time slots, as shown in Table 1. For details, refer to the relevant description in S801, which is not described here Let me repeat.

Alternatively, the network device configures a first activated BWP identifier, and the first activated BWP identifier is associated with a BWP. The BWP with the first activated BWP flag is activated after performing RRC configuration or RRC reconfiguration (to be activated upon performing the RRC(re-)configuration). In addition, the network device configures a first BWP start RB position identifier, and the first BWP start RB position identifier is associated with a BWP start RB position. The starting RB position of the BWP may be a starting RB position of the BWP associated with the first activated BWP identifier. The start RB position associated with the start RB position identifier of the first BWP is activated after performing RRC configuration or RRC reconfiguration (to be activated upon performing the RRC(re-)configuration). Correspondingly, the terminal device receives the first activated BWP identifier and the first BWP start RB location identifier configured by the network device. The activated BWP is determined according to the first activated BWP identifier, and the activated start RB position is determined according to the start RB position identifier of the first BWP. The terminal device uses the activated starting RB position as the starting RB position, and performs downlink or uplink communication with the network device on the activated BWP. It should be noted that the BWP here is an uplink BWP or a downlink BWP. The flags mentioned above also need to be configured separately for downlink and uplink.

Optionally, the network device is configured with a default (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 after the BWP inactivity timer (inactivity timer) expires (to be used upon expiration of the BWP inactivity timer). In addition, the network device is also configured with a default BWP identifier, and the default identifier is associated with a BWP. The BWP may be a BWP in the BWP set associated with the default BWP set identifier. The BWP identified by the default BWP is used after the BWP inactivity timer (inactivity timer) expires (to be used upon expiration of the BWP inactivity timer). Correspondingly, the terminal device receives the default BWP set identifier and the default BWP identifier configured by the network device. The default BWP set is determined according to the default BWP set identifier, and the default BWP is determined according to the first BWP set identifier. The terminal device performs downlink or uplink communication with the network device on the default BWP set and the default BWP. It should be noted that the BWP set here is an uplink BWP set or a downlink BWP set, and the BWP here is an uplink BWP or a downlink BWP. The flags mentioned above also need to be configured separately for downlink and uplink. For the above-mentioned 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 the following: bandwidth, subcarrier spacing, sounding reference The number of ports corresponding to a signal (sounding reference signal, SRS), and the maximum number of multiple-input multiple-output (multiple-input multiple-output, MIMO) layers, where the maximum number of MIMO layers is the maximum number of MIMO layers 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 (switching) or tuning (retuning) or frequency hopping (hopping). The first time delay is less than the second time delay, wherein the second time delay is the BWP switching delay supported by the NR terminal equipment, that is, T _{BWPswitchDelay} time slots, as shown in Table 1. For details, refer to the relevant description in S801, which is not described here Let me repeat.

Alternatively, the network device is configured with a default BWP identifier, and the default BWP identifier is associated with a BWP. The BWP identified by the default BWP is used after the BWP inactivity timer (inactivity timer) expires (to be used upon expiration of the BWP inactivity timer). In addition, the network device is also configured with a default BWP start RB position identifier, and the default BWP start RB position identifier is associated with a BWP default start RB position. The default starting RB position of the BWP may be a starting RB position of the BWP associated with the default BWP identifier. The initial RB position associated with the default BWP start RB position identifier is used after the BWP inactivity timer (inactivity timer) expires (to be used upon expiry of the BWP inactivity timer). Correspondingly, the terminal device receives the default BWP identifier configured by the network device and the default BWP start RB position identifier. The default BWP is determined according to the default BWP identifier, and the default start RB position is determined according to the default BWP start RB position identifier. The terminal device uses the default starting RB position as the starting RB position, and performs downlink or uplink communication with the network device on the default BWP. It should be noted that the BWP here is an uplink BWP or a downlink BWP. The flags mentioned above also need to be configured separately for downlink and uplink.

It can be understood that, in the above method embodiments, the methods and operations implemented by the terminal equipment may also be implemented by components (such as chips or circuits) that can be used for the terminal equipment, and the methods and operations implemented by the network equipment may also be implemented by A component (such as a chip or a circuit) implementation that can be used in a network device.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspectives of various interactions. It can be understood that each network element, such as a transmitting end device or a receiving end device, includes a corresponding hardware structure and/or software module for performing each function in order to realize the above functions. Those skilled in the art should be aware that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, the description will be made by taking the division of each functional module corresponding to each function as an example.

Above, the method provided by the embodiment of the present application is described in detail with reference to FIG. 8 . Hereinafter, the resource indication device provided by the embodiment of the present application will be described in detail with reference to FIG. 13 to FIG. 14 . It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments. Therefore, for details that are not described in detail, reference may be made to the method embodiments above. For brevity, details are not repeated here.

Please refer to FIG. 13 . FIG. 13 is a schematic structural diagram of a resource indication device provided by an embodiment of the present application. The resource indication device may include a sending module 1301, which can communicate with the outside, and the sending module 1301 can also be called a communication interface, a transceiver unit or a transceiver module. The sending module 1301 may be configured to perform the actions performed by the network device in the above method embodiments.

For example: the sending module 1301 may also be called a transceiver module or a transceiver unit (including a receiving unit and a receiving unit), which are respectively used to perform the steps of sending and receiving by the network device in the method embodiments above.

In a possible design, the resource indicating device may implement steps or processes corresponding to the execution of the network device in the above method embodiments, for example, may be a network device, or a chip or a circuit configured in the network device. The sending module 1301 is configured to perform operations related to sending and receiving on the network device side in the above method embodiments.

The sending module 1301 is configured to send configuration information to the terminal device, where the configuration information is used to configure multiple partial bandwidth BWPs, and at least one rate matching resource is configured on each of the multiple BWPs;

The sending module 1301 is further configured to send downlink control information DCI to the terminal device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule the transmission of the physical downlink shared channel PDSCH or/and the physical uplink shared channel PUSCH , the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the 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 multiple BWPs are divided into at least one association group, and the indication information is used to determining whether each of said at least one association group can be used during transmission of said PDSCH and/or said PUSCH.

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

Optionally, the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the number of rate matching resource groups on the multiple 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 the at least one rate matching resource group can be used during the transmission of the PDSCH or/and the PUSCH. Each rate matching resource group in a rate matching resource group.

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 multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the identifiers corresponding to the multiple BWPs are the same, and the resource blocks RB of the multiple BWPs have the same The starting position is 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, and the parameters include at least one of the following: bandwidth, subcarrier spacing, sounding reference The number of ports corresponding to the signal 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 intervals of the rate matching resources on the multiple BWPs are the same.

Optionally, the rate matching resources are resource block RB or symbol level rate matching resources, or the rate matching resources are resource element RE level rate matching resources.

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

Please refer to FIG. 14 . FIG. 14 is a schematic structural diagram of a resource indication device provided by an embodiment of the present application. The resource indication device may include a receiving module 1401, and the receiving module 1401 may communicate with the outside. The receiving module 1401 may also be called a communication interface, a transceiver unit or a transceiver module. The receiving module 1401 may be configured to perform the actions performed by the terminal device in the above method embodiments.

For example: the receiving module 1401 may also be called a transceiver module or a transceiver unit (including a receiving unit and a receiving unit), which are respectively used to perform the steps of sending and receiving by the terminal device in the method embodiments above.

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

The receiving module 1401 is configured to receive configuration information from a network device, the configuration information is used to configure multiple partial bandwidth BWPs, and at least one rate matching resource is configured on each of the multiple BWPs;

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

It should be noted that the implementation of each module may also refer to the corresponding description of the method embodiment shown in FIG. 8 to execute the methods and functions performed by the terminal device in the foregoing embodiments.

FIG. 15 is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device can be applied to the system shown in FIG. 1 to execute the functions of the network device in the above method embodiments, or implement the steps or processes performed by the network device in the above method embodiments.

As shown in FIG. 15 , the network device includes a processor 1501 and a transceiver 1502 . Optionally, the network device further includes a memory 1503 . Among them, the processor 1501, the transceiver 1502, and the memory 1503 can communicate with each other through an internal connection path, and transmit control and/or data signals. Call and run the computer program to control the transceiver 1502 to send and receive signals. Optionally, the network device may further include an antenna, configured to send the uplink data or uplink control signaling output by the transceiver 1502 through wireless signals.

The processor 1501 and the memory 1503 may be combined into a processing device, and the processor 1501 is configured to execute the program codes stored in the memory 1503 to realize the above functions. During specific implementation, the memory 1503 may also be integrated in the processor 1501 , or be independent of the processor 1501 .

The above-mentioned transceiver 1502 may correspond to the sending module in FIG. 13 , and may also be called a transceiver unit or a transceiver module. The transceiver 1502 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit 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 various modules in the network device are respectively for realizing the corresponding processes in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and detailed descriptions are appropriately omitted here to avoid repetition.

The above-mentioned processor 1501 can be used to execute the actions internally implemented by the network device described in the method embodiments above, and the transceiver 1502 can be used to execute the actions sent by the network device to the terminal device or received from the terminal device described in the method embodiments above. action. For details, please refer to the description in the foregoing method embodiments, and details are not repeated here.

Wherein, the processor 1501 may be a central processing unit, a general processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute the various illustrative logical blocks, modules and circuits described in connection with the present disclosure. The processor 1501 may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like. The communication bus 1504 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 15 , but it does not mean that there is only one bus or one type of bus. The communication bus 1504 is used to realize connection communication between these components. Wherein, in the embodiment of the present application, the transceiver 1502 is used for signaling or data communication with other node devices. Memory 1503 may include a volatile memory, such as nonvolatile random access memory (nonvolatile random access memory, NVRAM), phase change random access memory (phase change RAM, PRAM), magnetoresistive random access memory (magetoresistive) RAM, MRAM), etc., can also include non-volatile memory, such as at least one magnetic disk storage device, electronically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), flash memory devices, such as reverse or flash memory (NOR flash memory) or NAND flash memory (NAND flash memory), semiconductor devices, such as solid state disk (solid state disk, SSD) and so on. Optionally, the memory 1503 may also be at least one storage device located away from the aforementioned processor 1501 . Optionally, a set of computer program codes or configuration information may also be stored in the memory 1503 . Optionally, the processor 1501 may also execute programs stored in the memory 1503 . The processor may cooperate with the memory and the transceiver to execute any method and function of the network device in the foregoing application embodiments.

FIG. 16 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. The terminal device may be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the foregoing method embodiments, or implement the steps or processes executed by the terminal device in the foregoing method embodiments.

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. Wherein, the processor 1601, the transceiver 1602, and the memory 1603 can communicate with each other through an internal connection path, and transmit control and/or data signals. Call and run the computer program to control the transceiver 1602 to send and receive signals. Optionally, the terminal device may further include an antenna, configured to send the uplink data or uplink control signaling output by the transceiver 1602 through wireless signals.

The processor 1601 and the memory 1603 may be combined into a processing device, and the processor 1601 is configured to execute the program codes stored in the memory 1603 to realize the above functions. During specific implementation, the memory 1603 may also be integrated in the processor 1601 , or be independent of the processor 1601 .

The above-mentioned transceiver 1602 may correspond to the receiving module in FIG. 14 , and may also be called 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). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.

It should be understood that the terminal device shown in FIG. 16 can implement various processes involving the terminal device in the method embodiment shown in FIG. 8 . The operations and/or functions of the various modules in the terminal device are respectively for realizing the corresponding procedures in the foregoing method embodiments. For details, reference may be made to the descriptions in the foregoing method embodiments, and detailed descriptions are appropriately omitted here to avoid repetition.

The above-mentioned processor 1601 can be used to execute the actions implemented by the terminal device described in the previous method embodiments, and the transceiver 1602 can be used to execute the actions described in the previous method embodiments sent by the terminal device to the network device or received from the network device. action. For details, please refer to the description in the foregoing method embodiments, and details are not repeated here.

Wherein, the processor 1601 may be various types of processors mentioned above. The communication bus 1604 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in FIG. 16 , but it does not mean that there is only one bus or one type of bus. The communication bus 1604 is used to realize connection communication between these components. Wherein, the transceiver 1602 of the device in the embodiment of the present application is used for signaling or data communication with other devices. The memory 1603 may be various types of memory mentioned above. Optionally, the memory 1603 may also be at least one storage device located away from the aforementioned processor 1601 . A set of computer program codes or configuration information is stored in the memory 1603 , and the processor 1601 executes the programs in the memory 1603 . The processor may cooperate with the memory and the transceiver to execute any method and function of the terminal device in the foregoing application embodiments.

An embodiment of the present application also provides a chip system, which includes a processor, configured to support terminal devices or network devices to implement the functions involved in any of the above embodiments, such as generating or processing the DCI. In a possible design, the chip system may further include a memory, and the memory is used for necessary program instructions and data of a terminal device or a network device. The system-on-a-chip may consist of chips, or may include chips and other discrete devices. Wherein, 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 present application also provides a processing device, including a processor and an interface. The processor may be used to execute the methods in the foregoing method embodiments.

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

In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, no detailed description is given here.

It should be noted that the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability. In the implementation process, each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The above-mentioned processor 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 devices, discrete gate or transistor logic devices, discrete hardware components . Various methods, steps, and logic block diagrams disclosed in the embodiments of the present application may be implemented or executed. 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 can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.

According to the method provided in the embodiment of the present application, the present application also provides a computer program product, the computer program product includes: a computer program, when the computer program is run on the computer, the computer is made to execute any of the embodiments shown in FIG. The method of one embodiment.

According to the method provided in the embodiment of the present application, the present application also provides a computer-readable medium, the computer-readable medium stores a computer program, and when the computer program is run on a computer, the computer is made to execute the embodiment shown in FIG. 8 The method of any one of the embodiments.

According to the method provided in 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, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk (solid state disc, SSD)) etc.

The network equipment in each of the above device embodiments corresponds to the terminal equipment and the network equipment or terminal equipment in the method embodiments, and the corresponding modules or units perform corresponding steps, such as the receiving module and the sending module (transceiver) in the method embodiments. The step of receiving or sending, other steps besides sending and receiving may be performed by a processing module (processor). For the functions of the specific modules, reference may be made to the corresponding method embodiments. Wherein, there may be one or more processors.

Those of ordinary skill in the art can appreciate that various illustrative logical blocks (illustrative logical blocks) and steps (steps) described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. accomplish. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A resource indication method, characterized by comprising:

The network device sends configuration information to the terminal device, where the configuration information is used to configure multiple partial bandwidth BWPs, and at least one rate matching resource is configured on each BWP among the multiple BWPs;

The network device sends downlink control information DCI to the terminal device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule the transmission of the physical downlink shared channel PDSCH or/and the physical uplink shared channel PUSCH, the The indication information is used to determine whether rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH.
The method according to claim 1, wherein at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the rate matching resource groups on the multiple BWPs are divided into at least one an association group, the indication information is used to determine whether each association group in the at least one association group can be used during the transmission of the PDSCH or/and the PUSCH.
The method according to claim 2, wherein the indication information includes multiple bits, one bit corresponds to one association group, and the number of the multiple bits is less than the rate matching resources on the multiple BWPs The group number of groups.
The method according to claim 1, wherein 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 the Whether each rate matching resource group on the multiple BWPs can be used during the PUSCH transmission.
The method according to claim 4, wherein the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the rate on the multiple BWPs Number of groups to match resource groups.
The method according to claim 1, wherein all the 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 the PDSCH or/and the Whether each rate matching resource group in the at least one rate matching resource group can be used during PUSCH transmission.
The method according to claim 6, wherein 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 that of the at least one rate matching resource group Number of groups.
The method according to any one of claims 1-7, wherein the identifiers corresponding to the multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the multiple BWPs correspond to The IDs of the multiple BWPs are the same, and the starting positions of the resource blocks RB of the multiple BWPs are different.
The method according to any one of claims 1-8, 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 Similarly, the parameters include at least one of the following: bandwidth, subcarrier spacing, the number of ports corresponding to the sounding reference signal SRS, and the maximum number of multiple-input multiple-output MIMO layers, wherein the maximum number of MIMO layers is the maximum number of layers used by the PDSCH Number of MIMO layers.
The method according to any one of claims 1-9, wherein the subcarrier intervals of the rate matching resources on the multiple BWPs are the same.
The method according to any one of claims 1-10, wherein 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 .
The method according to any one of claims 1-11, wherein the terminal device is a low-capability terminal device.
A resource indication method, characterized by comprising:

The terminal device receives configuration information from the network device, where the configuration information is used to configure 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 device receives downlink control information DCI from the network device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule the transmission of the physical downlink shared channel PDSCH or/and the physical uplink shared channel PUSCH, the The indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH.
The method according to claim 13, wherein at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the rate matching resource groups on the multiple BWPs are divided into at least one an association group, the indication information is used to determine whether each association group in the at least one association group can be used during the transmission of the PDSCH or/and the PUSCH.
The method according to claim 14, wherein the indication information includes multiple bits, one bit corresponds to one association group, and the number of the multiple bits is less than the rate matching resources on the multiple BWPs The group number of groups.
The method according to claim 13, wherein 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 the Whether each rate matching resource group on the multiple BWPs can be used during the PUSCH transmission.
The method according to claim 16, wherein the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the rate on the multiple BWPs Number of groups to match resource groups.
The method according to claim 13, wherein all the 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 the PDSCH or/and the Whether each rate matching resource group in the at least one rate matching resource group can be used during PUSCH transmission.
The method according to claim 18, wherein 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 that of the at least one rate matching resource group Number of groups.
The method according to any one of claims 13-19, wherein the identifiers corresponding to the multiple BWPs are different, the starting positions of the resource blocks RB of the multiple BWPs are different, or the multiple BWPs correspond to The IDs of the multiple BWPs are the same, and the starting positions of the resource blocks RB of the multiple BWPs are different.
The method according to any one of claims 13-20, 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 Similarly, the parameters include at least one of the following: bandwidth, subcarrier spacing, the number of ports corresponding to the sounding reference signal SRS, and the maximum number of multiple-input multiple-output MIMO layers, wherein the maximum number of MIMO layers is the maximum number of layers used by the PDSCH Number of MIMO layers.
The method according to any one of claims 13-21, wherein the subcarrier spacing of the rate matching resources on the multiple BWPs is the same.
The method according to any one of claims 13-22, wherein 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 .
The method according to any one of claims 13-23, wherein the terminal device is a low-capability terminal device.
A resource indication device, characterized by comprising:

A sending module, configured to send configuration information to the 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, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule physical downlink shared channel PDSCH or/and physical uplink shared channel PUSCH and transmitting, the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH.
The device according to claim 25, wherein at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the rate matching resource groups on the multiple BWPs are divided into at least one an association group, the indication information is used to determine whether each association group in the at least one association group can be used during the transmission of the PDSCH or/and the PUSCH.
The device according to claim 26, wherein the indication information includes multiple bits, one bit corresponds to one association group, and the number of the multiple bits is less than the rate matching resources on the multiple BWPs The group number of groups.
The device according to claim 25, wherein 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 the Whether each rate matching resource group on the multiple BWPs can be used during the PUSCH transmission.
The device according to claim 28, wherein the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the rate on the multiple BWPs Number of groups to match resource groups.
The device according to claim 25, wherein all the 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 the PDSCH or/and the Whether each rate matching resource group in the at least one rate matching resource group can be used during PUSCH transmission.
The device according to claim 30, wherein 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 that of the at least one rate matching resource group Number of groups.
The device according to any one of claims 25-31, wherein the identifiers corresponding to the multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the multiple BWPs correspond to IDs of the multiple BWPs are the same, and the starting positions of the resource blocks RB of the multiple BWPs are different.
The device according to any one of claims 25-32, wherein the first BWP and the second BWP are two BWPs among the plurality of BWPs, and the parameters of the first BWP and the second BWP Similarly, the parameters include at least one of the following: bandwidth, subcarrier spacing, the number of ports corresponding to the sounding reference signal SRS, and the maximum number of multiple-input multiple-output MIMO layers, wherein the maximum number of MIMO layers is the maximum number of layers used by the PDSCH The number of MIMO layers.
The device according to any one of claims 25-33, wherein the subcarrier intervals of the rate matching resources on the multiple BWPs are the same.
The device according to any one of claims 25-34, wherein 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 .
A resource indication device, characterized by 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 at least one rate matching resource is configured on each BWP in the plurality of BWPs;

The receiving module is further configured to receive downlink control information DCI from the network device, the DCI includes scheduling information and indication information, and the scheduling information is used to schedule the physical downlink shared channel PDSCH or/and the physical uplink shared channel PUSCH transmission, the indication information is used to determine whether the rate matching resources on the multiple BWPs can be used during the transmission of the PDSCH or/and the PUSCH.
The device according to claim 36, wherein the at least one rate matching resource on each BWP is independently grouped into at least one rate matching resource group, and the rate matching resource groups on the multiple BWPs are divided into at least one an association group, the indication information is used to determine whether each association group in the at least one association group can be used during the transmission of the PDSCH or/and the PUSCH.
The device according to claim 37, wherein the indication information includes multiple bits, one bit corresponds to one association group, and the number of the multiple bits is less than the rate matching resources on the multiple BWPs The group number of groups.
The device according to claim 36, wherein 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 the Whether each rate matching resource group on the multiple BWPs can be used during the PUSCH transmission.
The device according to claim 39, wherein the indication information includes multiple bits, one bit corresponds to one rate matching resource group, and the number of the multiple bits is equal to the rate on the multiple BWPs Number of groups to match resource groups.
The device according to claim 36, wherein all the 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 the PDSCH or/and the Whether each rate matching resource group in the at least one rate matching resource group can be used during PUSCH transmission.
The device according to claim 41, wherein 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 that of the at least one rate matching resource group Number of groups.
The device according to any one of claims 36-42, wherein the identifications corresponding to the multiple BWPs are different, the start positions of the resource blocks RB of the multiple BWPs are different, or the multiple BWPs correspond to The IDs of the multiple BWPs are the same, and the starting positions of the resource blocks RB of the multiple BWPs are different.
The device according to any one of claims 36-43, wherein the first BWP and the second BWP are two BWPs among the plurality of BWPs, and the parameters of the first BWP and the second BWP Similarly, the parameters include at least one of the following: bandwidth, subcarrier spacing, the number of ports corresponding to the sounding reference signal SRS, and the maximum number of multiple-input multiple-output MIMO layers, wherein the maximum number of MIMO layers is the maximum number of layers used by the PDSCH Number of MIMO layers.
The device according to any one of claims 36-44, wherein the subcarrier intervals of the rate matching resources on the multiple BWPs are the same.
The device according to any one of claims 36-45, wherein 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 .
A communication device, characterized in that it includes a processor and a memory, the memory is used to store a computer program, and the processor runs the computer program so that the device executes any one of claims 1 to 24. Methods.
A chip, characterized in that the chip is a chip in a network device or a terminal device, the chip includes a processor and an input interface and an output interface connected to the processor, and the chip also includes a memory, when the When the computer program in the memory is executed, the method described in any one of claims 1 to 24 is executed.
A computer-readable storage medium, which is characterized in that it is used to store a computer program, and when the computer program is run on a computer, it causes the computer to execute the method according to any one of claims 1 to 24.
A computer program product, characterized in that the computer program product includes a computer program, and when the computer program is run on a computer, it causes the computer to execute the method according to any one of claims 1 to 24.
A communication system, characterized in that the system includes a network device and a network device, the network device executes the method according to any one of claims 1-12, and the terminal device executes any method according to any one of claims 13-24 one of the methods described.