Terminal, communication method, and base station

Abstract

To provide an efficient method for specifying whether or not the settings are to be applied in the scheduled cells in the case where multiple cells are scheduled by a single DCI.SOLUTION: A terminal includes a receiving unit that receives, via a first component carrier, scheduling information for a second component carrier; and a control unit that configures the second component carrier, based on configuration information contained in the scheduling information.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a terminal and a communication method in a wireless communication system. [Background technology]

[0002] NR (New Radio) Dynamic spectrum sharing (DSS) is a method of using LTE (Long Term Evolution) and NR on the same carrier. In the LTE system, CRS (Cell Specific Reference Signal), PDCCH (Physical Downlink Control Channel), etc. are transmitted for LTE users. For this reason, in DSS, NR PDCCH and data are transmitted while avoiding the time resources for transmitting signals for LTE users.

[0003] In Release 17 of 3GPP, enhancement of DSS is being considered. As a specific content of the DSS enhancement, for example, cross-carrier scheduling of the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) of a PCell (or primary second cell (PSCell)) by the Physical Downlink Control Channel (PDCCH) of a secondary cell (SCell) of CA is being considered. Furthermore, for the PDCCH of a P(S)Cell / SCell, scheduling of the PDSCH of multiple cells using a single Downlink Control Information (DCI) is being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TSG RAN Meeting #86,RP-193260,Sitges,Spain,December 9-12,2019 [Non-Patent Document 2] 3GPP TS38.212 V15.7.0(2019-09) [Non-Patent Document 3] 3GPP TS38.214 V15.7.0(2019-09) Summary of the Invention [Problem to be solved by the invention]

[0005] It is being considered to minimize the size of a single DCI used for scheduling to multiple cells, while including an indicator field in the DCI to specify whether or not and what pattern the configuration should be applied in the scheduled cells.

[0006] When scheduling is performed on multiple cells using a single DCI, a method is needed to efficiently specify whether or not a configuration should be applied in the scheduled cells. [Means for solving the problem]

[0007] According to an aspect of the present invention, there is provided a terminal comprising: a receiving unit configured to receive scheduling information for a second component carrier via a first component carrier; and a control unit configured to perform configuration in the second component carrier based on configuration information included in the scheduling information. Effect of the Invention

[0008] According to an embodiment, when scheduling is performed to multiple cells using a single DCI, a method is provided for efficiently specifying whether or not to apply a setting in the scheduled cell. [Brief description of the drawings]

[0009] [Figure 1] 1 is a configuration diagram of a communication system according to an embodiment of the present invention. [Diagram 2] A diagram showing an example of scheduling to multiple cells using a single DCI. [Diagram 3] 11 is a diagram showing an example of correspondence between bit values ​​of a rate matching indicator field and on / off of each rate matching pattern. FIG. [Figure 4] A diagram showing an example of joint coding of a Rate matching indicator field and a BWP indication field. [Diagram 5] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal. [Figure 6] FIG. 2 is a diagram illustrating an example of a functional configuration of a base station. [Figure 7] FIG. 2 is a diagram illustrating an example of a hardware configuration of a terminal and a base station. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] The wireless communication system in the following embodiments is basically assumed to be compliant with NR, but this is only one example, and the wireless communication system in the present embodiments may be compliant in part or in whole with a wireless communication system other than NR (e.g., LTE).

[0012] (Overall system configuration) A configuration diagram of a wireless communication system according to the present embodiment is shown in Fig. 1. As shown in Fig. 1, the wireless communication system according to the present embodiment includes a terminal 10 and a base station 20. Although Fig. 1 shows one terminal 10 and one base station 20, this is an example, and there may be a plurality of each.

[0013] The terminal 10 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, a communication module for M2M (Machine-to-Machine), etc. The terminal 10 receives a control signal or data from the base station 20 in DL and transmits a control signal or data to the base station 20 in UL, thereby utilizing various communication services provided by the wireless communication system. For example, the channels transmitted from the terminal 10 include a PUCCH (Physical Uplink Control Channel) and a PUSCH (Physical Uplink Shared Channel). The terminal 10 may be referred to as a UE, and the base station 20 may be referred to as a gNB.

[0014] In this embodiment, the duplexing method may be a time division duplex (TDD) method or a frequency division duplex (FDD) method.

[0015] In addition, in the embodiments, when radio parameters, etc. are "configured," this may mean that a predetermined value is pre-configured, or that the parameters are configured based on radio parameters notified from the base station 20 or the terminal 10.

[0016] The base station 20 is a communication device that provides one or more cells and performs wireless communication with the terminal 10. The physical resources of a wireless signal are defined in a time domain and a frequency domain, and the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 20 transmits a synchronization signal and system information to the terminal 10. The synchronization signal is, for example, NR-PSS and NR-SSS. A part of the system information is, for example, transmitted in NR-PBCH and is also called broadcast information. The synchronization signal and the broadcast information may be periodically transmitted as an SS block (SS / PBCH block) consisting of a predetermined number of OFDM symbols. For example, the base station 20 transmits a control signal or data to the terminal 10 in DL (Downlink) and receives a control signal or data from the terminal 10 in UL (Uplink). Both the base station 20 and the terminal 10 can transmit and receive signals by performing beamforming. For example, as shown in FIG. 1, the reference signal transmitted from the base station 20 includes a Channel State Information Reference Signal (CSI-RS), and the channels transmitted from the base station 20 include a Physical Downlink Control Channel (PDCCH) and a Physical Downlink Shared Channel (PDSCH).

[0017] (NR Dynamic spectrum sharing(DSS)) NR (New Radio) Dynamic spectrum sharing (DSS) is a method of using LTE (Long Term Evolution) and NR on the same carrier. In the LTE system, CRS (Cell Specific Reference Signal), PDCCH (Physical Downlink Control Channel), etc. are transmitted for LTE users. For this reason, in DSS, NR PDCCH and data are transmitted while avoiding the time resources for transmitting signals for LTE users.

[0018] Regarding DSS, methods have been introduced to date, such as introducing signaling to rate-match LTE CRS resources and shifting the position of the NR Demodulation Reference Signal (DMRS) to avoid collision between the NR DMRS and the LTE CRS.

[0019] A carrier to which DSS is applied is a carrier used in an LTE system, and therefore is a carrier with a lower frequency, such as 800 MHz or 2 GHz, compared to a normal NR carrier. In this way, a carrier to which DSS is applied is a carrier used in an LTE system, and therefore the NR system side maps NR control signals to the carrier, avoiding LTE control signals, CRS, etc. Therefore, in the case of a carrier to which DSS is applied, it is expected that the capacity for transmitting NR control signals will be smaller than the capacity for transmitting NR control signals in a normal NR carrier.

[0020] Here, in the NR system, it is assumed that carrier aggregation (CA) including a carrier to which DSS is applied is performed. As described above, the carrier to which DSS is applied is a carrier with a lower frequency than a normal NR carrier. Therefore, it is assumed that carrier aggregation (CA) is performed with the carrier to which DSS is applied as a primary cell (PCell). However, as described above, it is assumed that the capacity for transmitting NR control signals of the carrier to which DSS is applied is smaller than the capacity for transmitting NR control signals in a normal NR carrier. Therefore, in this case, the capacity for transmitting NR control signals of the carrier to which DSS is applied may be insufficient for the PCell.

[0021] For this reason, enhancements to DSS are being considered in 3GPP Release 17. It may be assumed that the frequency band will be limited to, for example, Frequency Range (FR1) of FR1 and FR2.

[0022] As a specific example of the extension of DSS, cross-carrier scheduling of a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH) of a PCell (or a primary second cell (PSCell)) by a Physical Downlink Control Channel (PDCCH) of a secondary cell (SCell) of CA is being considered. Furthermore, scheduling of PDSCHs of multiple cells using a single Downlink Control Information (DCI) for the PDCCH of a P(S)Cell / SCell is being considered. The number of multiple cells when scheduling is performed using a single DCI may be, for example, two or more.

[0023] It is being considered to minimize the size of a single DCI used when scheduling the PDSCH of multiple cells. For example, an upper limit may be set for the size of a single DCI used when scheduling the PDSCH of multiple cells. In the above example, it is assumed that the PDSCH of multiple cells is scheduled by a single DCI, but the number of DCIs is not limited to this example and may be, for example, two or more. In addition, the scheduling of multiple cells may be, for example, when CA including component carriers (CC) #1, CC #2, and CC #3 is performed as shown in FIG. 2, scheduling of PUSCH transmission and / or PDSCH reception in the terminal 10 via CC #2 and / or scheduling of PUSCH transmission and / or PDSCH reception in the terminal 10 via CC #3 by DCI transmitted from the base station 20 to the terminal 10 via CC #1. In the example of FIG. 2, three component carriers are shown, but the number of component carriers is not limited to three. For example, the number of component carriers may be two, or the number of component carriers may be greater than three. Furthermore, the cell performing the scheduling (CC#1 in the example of FIG. 2) itself may be one of the multiple cells to be scheduled.

[0024] (DCI Format 1_1) DCI is transmitted via the PDCCH. DCI format 1_1 can be used to perform downlink scheduling assignment or uplink scheduling for the terminal 10. DCI format 1_1 can include, for example, a DCI format identifier, resource information, information related to a transport block, information related to a Hybrid Automatic Repeat Request (HARQ), information related to multiple antennas, information related to a Physical Uplink Control Channel (PUCCH), and the like.

[0025] DCI format 1_1 may include, as resource information, for example, Carrier indicator, Bandwidth-part indicator, Frequency-domain resource allocation, Time-domain resource allocation, VRB-to-PRB mapping, PRB bundling size indicator, Rate matching indicator, Zero-power CSI-RS trigger, etc.

[0026] The inclusion of a carrier indicator field (CIF) in DCI format 1_1 indicates that cross-carrier scheduling is configured. The number of bits of the carrier indicator included in the CIF is 0 or 3 bits, and is used to indicate the component carrier associated with the DCI.

[0027] (Rate matching indicator field) The following provides an overview of the Rate matching indicator field. The Rate matching indicator field may be, for example, information indicating whether a rate matching pattern set for multiple resource elements (REs) can be used for PDSCH, that is, whether rate matching is applied in a cell scheduled by DCI. As described above, DCI format 1_1 includes a Rate matching indicator field. The size of the Rate matching indicator field may be, for example, 0, 1, or 2 bits depending on whether rateMatchPatternGroup1 and / or rateMatchPatternGroup2 are set for multiple resource elements (REs) that can be used for downlink transmission.

[0028] For example, when rateMatchPatternGroup1 and rateMatchPatternGroup2 are configured for a plurality of REs usable for downlink transmission, the size of the Rate matching indicator field may be 2 bits. Also, for example, when only one of rateMatchPatternGroup1 and rateMatchPatternGroup2 is configured for a plurality of REs usable for downlink transmission, the size of the Rate matching indicator field may be 1 bit. Also, for example, when neither rateMatchPatternGroup1 nor rateMatchPatternGroup2 is configured for a plurality of REs usable for downlink transmission, the size of the Rate matching indicator field may be 0 bit.

[0029] For example, when rateMatchPatternGroup1 and rateMatchPatternGroup2 are set for multiple REs and the size of the Rate matching indicator field is 2 bits, one bit of the Rate matching indicator field may indicate whether multiple REs to which rateMatchPatternGroup1 is set can be used for the PDSCH, and the other bit of the Rate matching indicator field may indicate whether multiple REs to which rateMatchPatternGroup2 is set can be used for the PDSCH. For example, the above-mentioned one bit of the Rate matching indicator field being 1 may indicate that multiple REs to which rateMatchPatternGroup1 is set cannot be used for the PDSCH, i.e., rate matching based on rateMatchPatternGroup1 is applied. Similarly, the above-mentioned other bit of the Rate matching indicator field being 1 may indicate that multiple REs to which rateMatchPatternGroup2 is set cannot be used for the PDSCH, i.e., rate matching based on rateMatchPatternGroup2 is applied.

[0030] For example, in scheduling, the base station 20 can specify, while performing downlink scheduling, whether or not to perform rate matching in the scheduled cell specified by the CIF field, using a Rate matching indicator field.

[0031] A specific configuration of the rate matching indicator field in the case of scheduling for multiple cells will be considered below. For example, it may be determined whether or not rate matching can be specified by the rate matching indicator field for multiple cells scheduled by the base station 20, and how rate matching is specified by the rate matching indicator field. Additionally or alternatively, it may be determined whether or not rate matching can be specified by the rate matching indicator field for one cell of multiple cells scheduled by the base station 20, and how rate matching is specified. Note that, in the embodiment described below, the number of CCs scheduled by a single DCI is two, but the number of CCs scheduled by a single DCI is not limited to two. The number of CCs scheduled by a single DCI may be, for example, one, or may be greater than two.

[0032] (Proposal 1) When the base station 20 performs scheduling for a plurality of cells, it may be possible to instruct rate matching for each scheduled cell. When the base station 20 performs scheduling for a plurality of cells, a rate matching instruction may be given for each of the plurality of cells by a Rate matching indicator field. The terminal 10 may set whether or not to apply rate matching for each of the plurality of cells, based on a value set in the Rate matching indicator field.

[0033] (Proposal 1-1) When the base station 20 performs scheduling for multiple cells using a single DCI, the Rate matching indicator field may be extended to, for example, X bits. Here, X may be {0, 1, or 2}+{0, 1, or 2} based on whether rateMatchPatternGroup1 and / or rateMatchPatternGroup2 are set in each cell to be scheduled. That is, X may be, for example, the sum of the number of bits required to specify rateMatchPatternGroup1 and / or rateMatchPatternGroup2 set in each cell among the multiple cells. Note that X may be determined based on the number of cells to be scheduled. Note that the rateMatchPatternGroup may be a set of resource elements that cannot be used for PDSCH when rate matching is applied.

[0034] For example, in the example shown in Fig. 2, it is assumed that transmission of PDSCH of CC#2 and CC#3 is scheduled for terminal 10 by DCI transmitted from base station 20 via PDCCH of CC#1. It is also assumed that only rateMatchPatternGroup1 is set in CC#2, and rateMatchPatternGroup1 and rateMatchPatternGroup2 are set in CC#3. In this case, the Rate matching indicator field of DCI may include a total of three bits, including one bit indicating whether rateMatchPatternGroup1 can be used for PDSCH in CC#2, and two bits indicating whether rateMatchPatternGroup1 can be used for PDSCH in CC#3 and whether rateMatchPatternGroup2 can be used for PDSCH.

[0035] A terminal 10 that receives DCI via the PDCCH of CC#1 may set rate matching in CC#2 based on a one-bit value included in the Rate matching indicator field included in the DCI that indicates whether rateMatchPatternGroup1 can be used for PDSCH in CC#2, and may also set rate matching in CC#3 based on a two-bit value included in the Rate matching indicator field that indicates whether rateMatchPatternGroup1 can be used for PDSCH in CC#3 and whether rateMatchPatternGroup2 can be used for PDSCH.

[0036] (Proposal 1-2) When the base station 20 schedules multiple cells using a single DCI, the Rate matching indicator field may be extended to, for example, Y bits. The value of Y may be, for example, the number of rate matching pattern groups configured in advance, or the number of rate matching pattern groups configured by RRC signaling. For example, as shown in Fig. 3, assume that rateMatchPatternGroupCC1, rateMatchPatternGroupCC2, and rateMatchPatternGroupCC3 are configured in advance. Here, rateMatchPatternGroupCC1, rateMatchPatternGroupCC2, and rateMatchPatternGroupCC3 may be patterns (e.g., bitmaps) that specify a set of multiple REs of one or more cells to be scheduled, respectively. Alternatively, rateMatchPatternGroupCC1, rateMatchPatternGroupCC2, and rateMatchPatternGroupCC3 may each include one or more of rateMatchPattern or rateMatchPatternGroup set in each cell to be scheduled (for example, rateMatchPatternGroupCC1 includes only rateMatchPatternGroup1 set in CC#2, rateMatchPatternGroupCC2 includes rateMatchPatternGroup1 set in CC#2 and rateMatchPatternGroup1 and rateMatchPatternGroup2 set in CC#3, and rateMatchPatternGroupCC3 includes rateMatchPatternGroup1 and rateMatchPatternGroup2 set in CC#3). When three rate matching pattern groups are preset as in the example of FIG. 3, the value of Y may be, for example, 3.In the example of Fig. 3, for example, the first most significant bit (MSB) of the three bits of the Rate matching indicator field may indicate whether or not rateMatchPatternGroupCC1 can be used for PDSCH. Also, in the example of Fig. 3, for example, the second most significant bit of the three bits of the Rate matching indicator field may indicate whether or not rateMatchPatternGroupCC2 can be used for PDSCH. Also, in the example of Fig. 3, for example, the least significant bit of the three bits of the Rate matching indicator field may indicate whether or not rateMatchPatternGroupCC3 can be used for PDSCH. For example, as shown in Fig. 3, when base station 20 sets the value "011" in the Rate matching indicator field and notifies terminal 10, terminal 10 may assume that rateMatchPatternGroupCC1 can be used for the PDSCH, that rateMatchPatternGroupCC2 cannot be used for the PDSCH, and that rateMatchPatternGroupCC3 cannot be used for the PDSCH. In the example of Fig. 3, the value of Y is 3, but the value of Y is not limited to 3. The value of Y may be 2 or less, or may be greater than 3.

[0037] (Proposals 1-3) When the base station 20 performs scheduling for multiple cells using a single DCI, the size of the Rate matching indicator field may not be extended. For example, the size of the Rate matching indicator field may be 0 bit (when neither rateMatchPatternGroup1 nor rateMatchPatternGroup2 is set), 1 bit (when only one of rateMatchPatternGroup1 and rateMatchPatternGroup2 is set), or 2 bits (when rateMatchPatternGroup1 and rateMatchPatternGroup2 are set) depending on whether rateMatchPatternGroup1 and / or rateMatchPatternGroup2 are set. For example, when the first CC and the second CC are scheduled using a single DCI, a correspondence may be defined between the bit value set in the Rate matching indicator field and the combination of the rate matching setting in each CC, so that a combination of the rate matching setting in the first CC and the rate matching setting in the second CC is specified based on the bit value set in the Rate matching indicator field. The correspondence may be, for example, predefined by a specification or may be set by a higher layer. In this case, the size of the Rate matching indicator field may be predefined or may be set by a higher layer, or may be set to the maximum size or the minimum size of the size of the Rate matching indicator field for the first CC and the size of the Rate matching indicator field for the second CC.

[0038] (Proposal 2) When the base station 20 performs scheduling for multiple cells using a single DCI, rate matching may be configured for one cell (which may be one or multiple cells) of the multiple cells using the Rate matching indicator field. The terminal 10 may perform rate matching configured for the one cell of the multiple cells, which is specified by the bit value of the Rate matching indicator field.

[0039] For example, in the example shown in Fig. 2, it is assumed that transmission of PDSCHs of CC#2 and CC#3 is scheduled for terminal 10 by DCI transmitted from base station 20 via PDCCH of CC#1. In this case, for example, rate matching in CC#2 may be set by a bit value set in the Rate matching indicator field of DCI transmitted from base station 20 via PDCCH of CC#1. Terminal 10 may set rate matching for CC#2 based on the bit value set in the Rate matching indicator field.

[0040] (Proposal 2-1) When the base station 20 schedules for multiple cells, the Rate matching indicator field may be extended to, for example, X bits, where X may be {0, 1, 2, 3, or 4} based on the maximum number of rate matching pattern groups in each scheduled cell + (1 or 2).

[0041] For example, when X is the maximum number of rate matching pattern groups in each scheduled cell + 1, one bit (e.g., one MSB (Most Significant Bit) or one LSB (Least Significant Bit)) of the Rate matching indicator field may specify one cell to which a rate matching pattern is assigned for terminal 10, and in this case, terminal 10 may assume that no rate matching pattern is assigned to other cells among the multiple cells.

[0042] For example, if X is the maximum number of rate matching pattern groups in each scheduled cell + 2, then two bits (e.g., the 2 MSBs or the 2 LSBs) of the Rate matching indicator field may specify to the terminal 10 the cell to which the rate matching pattern is assigned.

[0043] (Proposal 2-2) When the base station 20 performs scheduling for multiple cells using a single DCI, the size of the Rate matching indicator field may not be extended. For example, the size of the Rate matching indicator field may be 0, 1, or 2 bits. For example, the size of the Rate matching indicator field may be 0, 1, or 2 bits based on the setting of rateMatchPatternGroup1 and / or rateMatchPatternGroup2 for a specific cell to be scheduled. Note that, in this example, it is assumed that rateMatchPatternGroup1 and / or rateMatchPatternGroup2 are set for a specific cell, but the present embodiment is not limited to this example. For example, the number of rateMatchPatternGroups set for a specific cell may be 3 or more.

[0044] (Proposal 2-2-1) In the above-mentioned Proposal 2-2, the specific cell to be scheduled may be set based on, for example, a cell index. For example, the specific cell to be scheduled may be a cell having the smallest serving cell index among the multiple cells to be scheduled.

[0045] (Proposal 2-2-2) In the above-mentioned Proposal 2-2, the specific cell to be scheduled may be the cell having the maximum number of rate match pattern groups among the multiple cells to be scheduled.

[0046] (Proposal 2-2-3) In the above-mentioned Proposal 2-2, the specific cell to be scheduled may be determined by the RRC configuration.

[0047] In addition, in the above-mentioned Proposal 2-2-1 to Proposal 2-2-3, the terminal 10 may assume that, among the multiple cells to be scheduled, a rate matching pattern is not specified for cells other than the specific cell. Also, the specific cell may be determined by any combination of Proposal 2-2-1 to Proposal 2-2-3.

[0048] (Proposal 2') When base station 20 schedules multiple cells using a single DCI, if one of the multiple scheduled cells is the scheduling cell (i.e., the scheduling cell schedules itself and other cells using a single DCI), it may be possible to set rate matching for the scheduling cell using the Rate matching indicator field, but it may not be possible to set rate matching for cells other than the scheduling cell among the multiple scheduled cells using the Rate matching indicator field.

[0049] (Proposal 3) When the base station 20 performs scheduling for multiple cells using a single DCI, rate matching does not need to be configured for the multiple cells.

[0050] (Proposal 3-1) For example, when the base station 20 performs scheduling for multiple cells, the terminal 10 may assume that the rate matching indicator field size is zero. In this case, the terminal 10 may assume that rate matching is not configured for each of the multiple scheduled cells.

[0051] (Proposal 3-2) In the case of Proposal 3 described above, the terminal 10 may assume that the size of the Rate matching indicator field is 0 bits, 1 bit, or 2 bits, in which case the terminal 10 may ignore the Rate matching indicator field, and may assume that rate matching is not configured for each cell among multiple cells to be scheduled. For example, when the base station 20 performs scheduling for multiple cells, the terminal 10 may assume that the values ​​of the bits of the Rate matching indicator field are all set to zero.

[0052] (Proposal 4) When the base station 20 performs scheduling for multiple cells using a single DCI, it may be possible to switch, by RRC signaling, whether or not to assume that the terminal 10 will configure rate matching based on the Rate matching indicator field. For example, it may be possible to configure the terminal 10 with any of the above-mentioned Proposal 1 to Proposal 3 methods by RRC signaling.

[0053] (Proposal 5) When the base station 20 performs scheduling for multiple cells using a single DCI, if any one or all of the following conditions 1 and 2 are satisfied, the base station 20 may be able to configure rate matching for the terminal 10 based on the Rate matching indicator field.

[0054] (Condition 1) The number of rate matching pattern groups is the same in multiple cells to be scheduled.

[0055] (Condition 2) Rate matching set by the same rate matching pattern group identifier can be performed simultaneously for multiple scheduled cells.

[0056] (Proposal 6) When the base station 20 performs scheduling for a plurality of cells using a single DCI, joint coding of the Rate matching indicator field and other fields may be performed. For example, as shown in FIG. 4, joint coding of the Rate matching indicator field and the BWP indicator field may be performed. For example, as shown in FIG. 4, an association between the (Rate matching+BWP indicator) bit field, the BWP in the specified component carrier, and the setting of rate matching in the specified component carrier may be defined. In this case, for example, the base station 20 notifies the terminal 10 of the (Rate matching+BWP indicator) bit by including the (Rate matching+BWP indicator) bit field in the DCI, and the terminal 10 that receives the (Rate matching++BWP indicator) bit may activate the specified BWP in the specified component carrier and set rate matching in the specified component carrier based on the correspondence shown in FIG. 4. Note that, in the example of FIG. 4, an example in which joint coding of the Rate matching indicator field and the BWP indicator field is performed is shown, but the embodiment is not limited to this example. For example, joint coding of the rate matching indicator field and a carrier indicator field (CIF) may be performed, or joint coding of the rate matching indicator field, the CIF, and the BWP indicator field may be performed.

[0057] Note that Proposal 1 to Proposal 6 described above may be applied to the ZP-CSI-RS trigger field of DCI format 1_1. For example, in the example shown in FIG. 2, it is assumed that the transmission of PDSCH of CC#2 and CC#3 is scheduled for terminal 10 by DCI transmitted from base station 20 via PDCCH of CC#1. It is also assumed that only one ZP-CSI-RS-ResourceSet is configured in CC#2, and two aperiodic ZP-CSI-RS-ResourceSets are configured in CC#3. In this case, the ZP-CSI-RS trigger field of DCI may include a total of three bits, including one bit indicating whether or not aperiodic ZP-CSI-RS is configured in CC#2, and two bits indicating whether or not aperiodic ZP-CSI-RS is configured in CC#3. Terminal 10 that has received DCI via the PDCCH of CC#1 may receive aperiodic ZP-CSI-RS in CC#2 based on a one-bit value indicating whether or not aperiodic ZP-CSI-RS is configured in CC#2 included in the ZP-CSI-RS trigger field included in the DCI, and may receive aperiodic ZP-CSI-RS in CC#3 based on a two-bit value indicating whether or not aperiodic ZP-CSI-RS is configured in CC#3 included in the ZP-CSI-RS trigger field. Also, for example, the Rate matching indicator fields in Proposals 1-2, 1-3, and 2-1 may be replaced with the ZP-CSI-RS trigger field.

[0058] (Device configuration) Next, a functional configuration example of the terminal 10 and the base station 20 that execute the processing operations described above will be described. The terminal 10 and the base station 20 have all the functions described in this embodiment. However, the terminal 10 and the base station 20 may have only a part of all the functions described in this embodiment. The terminal 10 and the base station 20 may be collectively referred to as a communication device.

[0059] <Device> Fig. 5 is a diagram showing an example of the functional configuration of the terminal 10. As shown in Fig. 5, the terminal 10 has a transmitting unit 110, a receiving unit 120, and a control unit 130. The functional configuration shown in Fig. 5 is merely an example. As long as the operation according to the present embodiment can be executed, the functional divisions and the names of the functional units may be any. Note that the transmitting unit 110 may be called a transmitter, and the receiving unit 120 may be called a receiver.

[0060] The transmitter 110 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The transmitter 110 can form one or more beams. The receiver 120 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 120 also includes a measurement unit that measures the received signals and acquires the received power, etc.

[0061] The control unit 130 controls the terminal 10. Note that the functions of the control unit 130 related to transmission may be included in the transmitting unit 110, and the functions of the control unit 130 related to reception may be included in the receiving unit 120.

[0062] For example, the receiver 120 receives DCI including scheduling information via the PDCCH from the base station 20. The controller 130 sets rate matching for each component carrier based on a value set in a Rate matching indicator field included in the DCI.

[0063] <Base station 20> Fig. 6 is a diagram showing an example of the functional configuration of the base station 20. As shown in Fig. 6, the base station 20 has a transmitting unit 210, a receiving unit 220, and a control unit 230. The functional configuration shown in Fig. 6 is merely an example. As long as the operation according to the present embodiment can be executed, the functional divisions and the names of the functional units may be any. Note that the transmitting unit 210 may be called a transmitter, and the receiving unit 220 may be called a receiver.

[0064] The transmitting unit 210 includes a function of generating a signal to be transmitted to the terminal 10 side and wirelessly transmitting the signal. The receiving unit 220 includes a function of receiving various signals transmitted from the terminal 10 and acquiring, for example, information of a higher layer from the received signals. The receiving unit 220 also includes a measuring unit that measures the received signal and acquires the received power, etc.

[0065] The control unit 230 controls the base station 20. Note that the functions of the control unit 230 related to transmission may be included in the transmitting unit 210, and the functions of the control unit 230 related to reception may be included in the receiving unit 220.

[0066] For example, when scheduling to a plurality of cells, the control unit 230 generates a rate matching indicator field including setting information of rate matching in each component carrier, and includes the rate matching indicator field in the DCI including the scheduling information. The transmission unit 210 transmits the DCI generated by the control unit 230 via the PDCCH.

[0067] <Hardware configuration> The block diagrams (FIGS. 5 and 6) used in the description of the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the means for realizing each functional block is not particularly limited. That is, each functional block may be realized by one device in which multiple elements are physically and / or logically combined, or may be realized by two or more devices that are physically and / or logically separated and directly and / or indirectly (for example, wired and / or wirelessly) connected to each other and these multiple devices.

[0068] Also, for example, the terminal 10 and the base station 20 in one embodiment of the present invention may both function as a computer that performs processing according to this embodiment. Fig. 7 is a diagram showing an example of a hardware configuration of the terminal 10 and the base station 20 according to this embodiment. Each of the terminal 10 and the base station 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0069] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the terminal 10 and the base station 20 may be configured to include one or more of the devices indicated by 1001 to 1006 shown in the figure, or may be configured to exclude some of the devices.

[0070] Each function in the terminal 10 and the base station 20 is realized by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and controls communication by a communication device 1004 and the reading and / or writing of data in the memory 1002 and the storage 1003.

[0071] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.

[0072] Moreover, the processor 1001 reads out a program (program code), a software module, or data from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processes according to the program. As the program, a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment is used. For example, the transmitting unit 110, the receiving unit 120, and the control unit 130 of the terminal 10 shown in FIG. 5 may be stored in the memory 1002 and realized by a control program that runs on the processor 1001. Also, for example, the transmitting unit 210, the receiving unit 220, and the control unit 230 of the base station 20 shown in FIG. 6 may be stored in the memory 1002 and realized by a control program that runs on the processor 1001. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented in one or more chips. The program may be transmitted from a network via a telecommunication line.

[0073] The memory 1002 is a computer-readable recording medium, and may be composed of at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for carrying out processing according to one embodiment of the present invention.

[0074] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray® disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including memory 1002 and / or storage 1003.

[0075] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. For example, the transmission unit 110 and the reception unit 120 of the terminal 10 may be realized by the communication device 1004. Also, the transmission unit 210 and the reception unit 220 of the base station 20 may be realized by the communication device 1004.

[0076] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0077] Furthermore, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured as a single bus, or may be configured as different buses between the devices.

[0078] Furthermore, each of the terminal 10 and the base station 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented by at least one of these pieces of hardware.

[0079] (Summary of the embodiment) This specification discloses at least the following terminal and communication method.

[0080] A terminal comprising: a receiving unit that receives scheduling information for one or more second component carriers among a plurality of component carriers constituting carrier aggregation via a first component carrier among the plurality of component carriers; and a control unit that performs rate matching setting in the one or more second component carriers based on rate matching setting information included in the scheduling information.

[0081] According to the above configuration, the terminal is able to configure rate matching in a scheduled component carrier based on rate matching configuration information included in the scheduling information.

[0082] The rate matching configuration information may include information indicating whether or not one or more rate matching patterns configured for each component carrier among the one or more second component carriers can be used for a physical downlink shared channel (PDSCH).

[0083] According to the above configuration, the terminal is able to configure rate matching for each component carrier based on rate matching configuration information included in the scheduling information.

[0084] The one or more second component carriers may consist of two component carriers, and the rate matching configuration information may include information indicating whether a plurality of resource elements indicated by one or more rate matching patterns set for one of the two component carriers can be used for a physical downlink shared channel (PDSCH) of the one component carrier, and may also include information indicating whether a plurality of resource elements indicated by one or more rate matching patterns set for the other of the two component carriers can be used for a PDSCH of the other component carrier.

[0085] According to the above configuration, the terminal is able to configure rate matching for each component carrier based on rate matching configuration information included in the scheduling information.

[0086] The one or more second component carriers may include the first component carrier, and the control unit may configure rate matching for only the first component carrier based on rate matching configuration information included in the scheduling information.

[0087] According to the above configuration, when carrier aggregation is performed, for example, it is possible to perform rate matching only for the secondary cell.

[0088] A communication method for a terminal, comprising: a step of receiving scheduling information for one or more second component carriers among a plurality of component carriers constituting carrier aggregation via a first component carrier among the plurality of component carriers; and a step of configuring rate matching in the one or more second component carriers based on rate matching configuration information included in the scheduling information.

[0089] According to the above configuration, the terminal is able to configure rate matching in a scheduled component carrier based on rate matching configuration information included in the scheduling information.

[0090] (Supplementary embodiment) Although the embodiment of the present invention has been described above, the disclosed invention is not limited to such an embodiment, and a person skilled in the art will understand various modifications, modifications, alternatives, replacements, and the like. Although the description has been given using specific numerical examples to facilitate understanding of the invention, unless otherwise specified, those numerical values ​​are merely examples and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operations of multiple functional units may be physically performed by one part, or the operations of one functional unit may be physically performed by multiple parts. The order of the processing procedures described in the embodiment may be changed as long as there is no contradiction. For convenience of the processing description, the terminal 10 and the base station 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the terminal 10 in accordance with an embodiment of the present invention and the software operated by the processor of the base station 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0091] The notification of information is not limited to the aspects / embodiments described in this specification, and may be performed in other ways. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. In addition, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0092] Each aspect / embodiment described herein may be applied to systems utilizing LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), or other suitable systems and / or next generation systems enhanced thereon.

[0093] The steps, sequences, flow charts, etc. of each aspect / embodiment described herein may be reordered unless inconsistent, For example, the methods described herein present elements of various steps in an example order, and are not limited to the particular order presented.

[0094] In this specification, a specific operation performed by the base station 20 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 20, it is clear that various operations performed for communication with the terminal 10 may be performed by the base station 20 and / or other network nodes other than the base station 20 (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station 20, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0095] Each aspect / embodiment described in this specification may be used alone, in combination, or switched depending on the implementation.

[0096] Terminal 10 may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0097] Base station 20 may also be referred to by those skilled in the art as a NodeB (NB), an enhanced NodeB (eNB), a Base Station, a gNB, or some other suitable terminology.

[0098] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0099] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0100] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0101] As used herein, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. In addition, "judgment" and "decision" can include resolving, selecting, choosing, establishing, comparing, etc., and regarding that as a "judgment" or "decision." In other words, "judgment" and "decision" can include regarding some action as a "judgment" or "decision."

[0102] As used herein, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0103] To the extent that the terms "include," "including," and variations thereof are used herein in the specification or claims, these terms are intended to be inclusive, similar to the term "comprising." Further, the term "or" as used herein is not intended to be an exclusive or.

[0104] Throughout this disclosure, where articles are added by translation, such as a, an, and the in English, these articles may include plurals unless the context clearly indicates otherwise.

[0105] Although the present invention has been described in detail above, it is clear to those skilled in the art that the present invention is not limited to the embodiments described in this specification. The present invention can be implemented in modified and altered forms without departing from the spirit and scope of the present invention as defined by the claims. Therefore, the description in this specification is intended to be illustrative and does not have any limiting meaning on the present invention. [Explanation of symbols]

[0106] 10 Terminal 110 Transmitter 120 Receiving unit 130 Control section 20 base station 210 Transmitter 220 Receiving unit 230 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device

Claims

1. A method for scheduling a plurality of cells, comprising: a receiving unit configured to receive, from a base station, a single piece of downlink control information used for scheduling a plurality of cells and including an instruction for rate matching; A terminal comprising: a control unit that performs rate matching based on a rate matching pattern to be applied to each of the plurality of cells determined based on the instruction.

2. The instruction is indicated as a rate matching instruction field included in the downlink control information, The terminal of claim 1 , wherein the rate matching indication field specifies a combination indicating one or more rate matching patterns to be applied to each of the plurality of cells.

3. The terminal described in claim 2, wherein the control unit applies a rate matching pattern based on the combination specified by the rate matching instruction field to a physical downlink shared channel.

4. The terminal described in Claim 2, wherein the control unit determines the size of the rate matching instruction field based on the number of combinations of whether or not one or more rate matching patterns can be applied to each of the multiple cells.

5. The receiving unit receives rate matching setting information including a plurality of combinations indicating whether or not one or more rate matching patterns can be applied to each of the plurality of cells from the base station; The terminal according to claim 2 , wherein the control unit performs the rate matching based on one combination from the plurality of combinations that is specified by the rate matching instruction field.

6. A communication method executed by a terminal, comprising: receiving, from a base station, a single downlink control information used for scheduling a plurality of cells, the single downlink control information including an indication of rate matching; A control unit that performs rate matching based on a rate matching pattern to be applied to each of the plurality of cells determined based on the instruction.

7. A control unit for generating a single downlink control information used for scheduling a plurality of cells, the single downlink control information including an instruction for rate matching; A transmitter that transmits the downlink control information to a terminal, The base station, wherein the terminal performs rate matching for a downlink shared channel based on a rate matching pattern for each of the plurality of cells determined based on the instruction.

Images