Terminal, base station device, and reception method

Abstract

The terminal has a reception section that receives, from the base station device, setting information indicating cross-carrier scheduling for a first cell that is scheduled from a second cell, the reception section monitoring a PDCCH of the first cell and a PDCCH of the second cell.

Description

TECHNICAL FIELD

[0001] The present application relates to a terminal and a base station apparatus in a wireless communication system. BACKGROUND

[0002] In the 3GPP (3rd Generation Partnership Project), in order to realize further large capacity of system capacity, further high speed of data transmission speed, further low delay in a wireless section, and the like, research on a wireless communication scheme called 5G or NR (New Radio) (hereinafter, the wireless communication scheme will be referred to as "NR") is being conducted. In 5G, in order to satisfy a requirement condition of realizing a throughput of 10 Gbps or more and making a delay in a wireless section 1 ms or less, research on various wireless technologies and network architectures is being conducted (for example, Non-Patent Literature 1).

[0003] Further, a dynamic spectrum sharing technology (Dynamic spectrum sharing: DSS) in which LTE and NR coexist in the same frequency band is being researched. By making different RATs (Radio access technology) coexist in a single carrier, it is possible to flexibly cope with service demands at the time of system generation switching.

[0004] PRIOR ART DOCUMENT

[0005] NON-PATENT LITERATURE

[0006] Non-Patent Literature 1: 3GPP TS 38.300 V15.9.0 (2020-03)

[0007] Non-Patent Literature 2: 3GPP TS 38.331 V15.9.0 (2020-03)

[0008] Non-Patent Literature 3: 3GPP TS 38.213 V15.9.0 (2020-03) SUMMARY

[0009] PROBLEMS TO BE SOLVED BY THE INVENTION

[0010] In the current specification of DSS, resources for transmitting and receiving control signals are separately set for LTE terminals and NR terminals. The resources in which control signals can be configured are predetermined, and systems coexist in a single carrier, so the resources for transmitting and receiving control signals are insufficient compared to the case where systems independently operate in different carriers.

[0011] In cross-carrier scheduling in carrier aggregation, in the conventional technology (for example, Non-Patent Literature 2), PDSCH reception or PUSCH transmission of a P(S)Cell (PCell or PSCell) cannot be scheduled from an SCell. Therefore, in order to schedule PDSCH reception or PUSCH transmission of the P(S)Cell, only PDCCH of the P(S)Cell is used, and the resource utilization efficiency can be reduced.

[0012] Thus, in particular in DSS where resources for transmitting and receiving control signals are insufficient, in order to efficiently use resources, scheduling PDSCH reception or PUSCH transmission of a P(S)Cell by PDCCH of an SCell is studied.

[0013] However, in the case where PDSCH reception or PUSCH transmission of a P(S)Cell is scheduled by PDCCH of an SCell, as long as RRC reconfiguration is not performed, PDSCH reception or PUSCH transmission of the P(S)Cell cannot be scheduled by PDCCH of the P(S)Cell, and the resource utilization efficiency can be reduced. In addition, this problem is not limited to the case where DSS is used, and is a problem that occurs when it is desired to schedule PDSCH reception or PUSCH transmission of a P(S)Cell by PDCCH of an SCell.

[0014] The present application has been achieved in view of the above-described circumstances, and aims to provide a technology capable of easily switching a cell that performs scheduling for a first cell between the first cell and a second cell.

[0015] Means for solving the problem

[0016] According to the disclosed technology, a terminal is provided, the terminal having: a reception section that receives, from a base station device, setting information indicating cross-carrier scheduling for a first cell that schedules the first cell from a second cell, the reception section monitoring a PDCCH of the first cell and a PDCCH of the second cell.

[0017] Effects of the Invention

[0018] According to the disclosed technology, it is possible to easily switch a cell that performs scheduling for a first cell between the first cell and a second cell. BRIEF DESCRIPTION OF DRAWINGS

[0019] Figure 1 is a diagram for explaining a wireless communication system in an embodiment of the present application.

[0020] Figure 2 is a diagram for explaining a wireless communication system in an embodiment of the present application.

[0021] Figure 3 is a diagram for explaining the basic operation of a wireless communication system in the embodiment of the present application.

[0022] Figure 4 is a diagram for explaining an example of scheduling.

[0023] Figure 5 is a diagram for explaining an example of scheduling.

[0024] Figure 6 is a diagram showing a modification example of the specification.

[0025] Figure 7 is a diagram showing a modification example of the specification.

[0026] Figure 8 is a diagram for explaining an example of the operation of the terminal.

[0027] Figure 9 is a diagram for explaining an example of the operation of the terminal.

[0028] Figure 10 is a diagram for explaining an example of the operation of the terminal.

[0029] Figure 11 is a diagram for explaining an example of the operation of the terminal.

[0030] Figure 12 is a diagram for explaining an example of the operation of the terminal.

[0031] Figure 13 is a diagram for explaining an example of the operation of the terminal.

[0032] Figure 14 is a diagram for explaining an example of the operation of the terminal.

[0033] Figure 15 is a diagram for explaining an example of the operation of the terminal.

[0034] Figure 16 is a diagram showing an example of the functional structure of the base station device 10 in the embodiment of the present application.

[0035] Figure 17 is a diagram showing an example of the functional structure of the user terminal 20 in the embodiment of the present application.

[0036] Figure 18 is a diagram showing an example of the hardware structure of the base station device 10 or the user terminal 20 in the embodiment of the present application. DETAILED DESCRIPTION

[0037] Hereinafter, the embodiment of the present application will be described with reference to the accompanying drawings. Furthermore, the embodiment described below is only an example, and the application of the embodiment of the present application is not limited to the following embodiment.

[0038] The wireless communication system of the embodiment of the present application is appropriately used in operation with the existing technology. However, the existing technology is, for example, the existing NR or LTE, but is not limited to the existing NR or LTE.

[0039] (System configuration)

[0040] Figure 1 is a diagram for explaining the wireless communication system in the embodiment of the present application. As shown in Figure 1 , the wireless communication system in the embodiment of the present application includes a base station device 10 and a terminal 20. Figure 1 One base station device 10 and one terminal 20 are shown in each of the drawings, but this is merely an example, and a plurality of each can be provided.

[0041] The base station device 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resource of the wireless signal is defined by the time domain and the frequency domain, the time domain can be defined by the number of OFDM symbols, and the frequency domain can be defined by the number of subcarriers or the number of resource blocks. Further, the TTI (Transmission Time Interval) in the time domain can be a slot, and the TTI can also be a subframe.

[0042] The base station device 10 is capable of carrier aggregation that bundles a plurality of cells (a plurality of CCs (Component Carriers)) to perform communication with the terminal 20. In the carrier aggregation, one PCell (Primary Cell) and one or more SCells (Secondary Cells) are used.

[0043] The base station device 10 transmits a synchronization signal and system information and the like to the terminal 20. The synchronization signal is, for example, an NR-PSS and an NR-SSS. The system information is transmitted, for example, by an NR-PBCH or a PDSCH, and is also called broadcast information. As shown in Figure 1 , the base station device 10 transmits a control signal or data to the terminal 20 through a DL (Downlink), and receives a control signal or data from the terminal 20 through a UL (Uplink). In addition, here, a signal transmitted through a control channel such as a PUCCH, a PDCCH, and the like is called a control signal, and a signal transmitted through a shared channel such as a PUSCH, a PDSCH, and the like is called data, but these are examples.

[0044] The terminal 20 is a communication device 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), and the like. As shown in Figure 1As shown, terminal 20 receives control signals or data from base station device 10 via DL, and sends control signals or data to base station device 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Alternatively, terminal 20 can be referred to as UE, and base station device 10 as gNB.

[0045] Terminal 20 is capable of carrier aggregation, which bundles multiple cells (multiple CCs (component carriers)) to communicate with base station device 10. In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used. Alternatively, a PUCCH-SCell with a PUCCH can also be used.

[0046] Figure 2 This illustrates an example of the structure of a wireless communication system where DC (Dual connectivity) is implemented. For example... Figure 2 As shown, the system includes a base station device 10A acting as the MN (Master Node) and a base station device 10B acting as the SN (Secondary Node). Base station devices 10A and 10B are connected to the core network 30. Terminal 20 communicates with both base station devices 10A and 10B.

[0047] The cell group provided by base station device 10A, which acts as the MN, is referred to as the MCG (Master Cell Group), and the cell group provided by base station device 10B, which acts as the SN, is referred to as the SCG (Secondary Cell Group). Furthermore, in the DC, the MCG consists of one PCell and one or more SCells, and the SCG consists of one PSCell (Primary SCell) and one or more SCells. Additionally, in this specification, CC and cell are used synonymously.

[0048] The processing actions in this embodiment can be performed by Figure 1 The system architecture shown can also be executed by... Figure 2 The system architecture shown can be executed by other system architectures as well. Furthermore, when DC is executed, cross-carrier scheduling can be performed between cells within a single cell group or across multiple cell groups.

[0049] (Basic action example)

[0050] Reference Figure 3 A basic example of the operation of the communication system in the embodiments of the present invention will be described. This operation is common to Embodiments 1 to 4 described below.

[0051] In S101, the base station device 10 transmits setting information to the terminal 20 through an RRC message, and the terminal 20 receives the setting information. The setting information contains, for example, crossCarrierSchedulingConfig as setting information for cross-carrier scheduling of a serving cell. The crossCarrierSchedulingConfig contains information indicating whether a serving cell that is a target of setting of the setting information is scheduled from another serving cell or schedules another serving cell. In addition, the "serving cell" can be referred to as a "cell".

[0052] The setting information received by the terminal 20 in S101 can contain information set by the base station device 10 to the terminal 20 in each of the following embodiments.

[0053] In S102, the base station device 10 transmits DCI (control information) through a PDCCH in a certain cell (set to cell A), and the terminal 20 receives the DCI in the cell A. When cross-carrier scheduling is set to the terminal 20 in the cell A, the DCI is, for example, DCI that schedules PDSCH reception / PUSCH transmission (PDSCH reception or PUSCH transmission) of a cell (cell B) other than the cell A. In addition, in S102, the terminal 20 sometimes schedules PDSCH reception / PUSCH transmission of the cell A through DCI received in the cell B.

[0054] In S103, the terminal 20 performs PDSCH reception / PUSCH transmission in accordance with the DCI received in S102.

[0055] Hereinafter, scheduling through DCI transmitted by a PDCCH will be sometimes expressed as scheduling through a PDCCH.

[0056] (Problem, Summary of Embodiments)

[0057] As described above, in the present embodiment, the base station device 10 can perform cross-carrier scheduling to the terminal 20 through a PDCCH.

[0058] Reference Figure 4 An example of cross-carrier scheduling will be described. In this example, in Figure 4 (a), Figure 4 (b), CrossCarrierSchedulingConfig described in Non-Patent Literature 2 is set to be set for each cell constituting carrier aggregation.

[0059] In Figure 4(a) In the middle, since own is set as schedulingCellInfo in the P(S)Cell and SCell1, in the P(S)Cell and SCell, PDSCH reception / PUSCH transmission of the cell is scheduled by PDCCH of the cell, respectively.

[0060] In Figure 4 (b) In the middle, own is set as schedulingCellInfo in the P(S)Cell, and PDSCH reception / PUSCH transmission of SCell1 corresponding to cif included in DCI received in the P(S)Cell is scheduled.

[0061] Further, with respect to SCell1, other (scheduling cell is P(S)Cell) is set, and PDSCH reception / PUSCH transmission is scheduled by PDCCH of the P(S)Cell.

[0062] Further, when own (with cif) is set in SCell1, PDSCH reception / PUSCH transmission of SCell2 corresponding to cif included in DCI received in SCell1 is scheduled. With respect to SCell2, other (scheduling cell is SCell1) is set, and PDSCH reception / PUSCH transmission is scheduled by PDCCH of SCell1.

[0063] In Figure 4 (c) In the middle, PDSCH reception / PUSCH transmission of the P(S)Cell is scheduled by PDCCH of SCell1.

[0064] As a method capable of scheduling PDSCH reception / PUSCH transmission of the P(S)Cell from the SCell, a method of setting schedulingCellInfo = other to the P(S)Cell can be considered. In the related art described in Non-Patent Literature 2, only schedulingCellInfo = other can be set to the SCell, but by removing this limitation, schedulingCellInfo = other can be set to the P(S)Cell.

[0065] However, since schedulingCellInfo = other is set to the terminal 20 by the setting information of the RRC, as long as RRC reconfiguration is not performed to the terminal 20, the cell that schedules PDSCH reception / PUSCH transmission of the corresponding P(S)Cell is limited only to the SCell.

[0066] When the amount of resource usage of each cell is considered to change from time to time, it is desirable that PDSCH reception / PUSCH transmission of the P(S)Cell be scheduled from either the SCell or the P(S)Cell.

[0067] Thus, in the present embodiment, as shown in Figure 5 , it is possible to easily switch the cell that schedules PDSCH reception / PUSCH transmission of the P(S)Cell between the P(S)Cell and the SCell according to the passage of time.

[0068] The technology related to the present embodiment will be described below using Examples 1 to 4. Any of Examples 1 to 4 can be arbitrarily combined to be implemented. In the description of Examples 1 to 4, the step numbers in the basic action example shown in Figure 3 are appropriately referred to. Further, the technology of switching the cell that schedules PDSCH reception / PUSCH transmission of the P(S)Cell between the P(S)Cell and the SCell is appropriately illustrated in Figure 5 .

[0069] In addition, in each of the following examples, the technology of switching the cell that schedules PDSCH reception / PUSCH transmission of the P(S)Cell between the SCell and the P(S)Cell is described, but the technology can be applied without being limited to between the P(S)Cell and the SCell. For example, the technology described in each of the following examples can be applied even between a plurality of SCells.

[0070] (Example 1)

[0071] In Example 1, the terminal 20 assumes that, in a case where cross-carrier scheduling is set in the P(S)Cell from the base station device 10, the setting is made by RRC so that PDSCH reception / PUSCH transmission of the P(S)Cell is scheduled by the PDCCH of the SCell and the PDCCH of the P(S)Cell.

[0072] From the viewpoint of the base station device 10, in a case where cross-carrier scheduling is set in the P(S)Cell of the terminal 20, the base station device 10 assumes that PDSCH reception / PUSCH transmission of the P(S)Cell in the terminal 20 can be scheduled by either the PDCCH of the SCell or the PDCCH of the P(S)Cell. More specifically, as described below.

[0073] In Figure 3In S101 shown, the base station device 10 transmits, to the terminal 20, the CrossCarrierSchedulingConfig as the setting information of the P(S)Cell by RRC signaling, and the terminal 20 receives the setting information.

[0074] Figure 6 An example of a description in a specification book (extract from Non-Patent Literature 2, showing a change site) according to which the terminal 20 in Embodiment 1 operates is shown. As shown in Figure 6 As shown, the limitation of the object cell set as other in schedulingCellInfo in CrossCarrierSchedulingConfig (only SCell in the past) is deleted, and schedulingCellInfo = other can also be set in the P(S)Cell.

[0075] In Figure 3 In S101 shown, the CrossCarrierSchedulingConfig as the setting information of the P(S)Cell is set from the base station device 10 to the terminal 20 with schedulingCellInfo = other (schedulingCellId = n1).

[0076] The setting information indicates that the PDSCH reception / PUSCH transmission in the P(S)Cell is scheduled by the PDCCH received in the cell other than the P(S)Cell (i.e., SCell), and the ID of the cell that performs the scheduling is n1.

[0077] In this embodiment, the terminal 20 that receives the setting information monitors the PDCCH of the P(S)Cell in addition to the PDCCH of the SCell specified by other's schedulingCellId = n1.

[0078] The base station device 10 can schedule the PDSCH reception / PUSCH transmission in the P(S)Cell by the PDCCH of the SCell specified by other's schedulingCellId = n1, and can also schedule the PDSCH reception / PUSCH transmission in the P(S)Cell by the PDCCH of the P(S)Cell.

[0079] The terminal 20 monitors the PDCCH of the SCell and the PDCCH of the P(S)Cell, and thus, for example, as shown in Figure 5As shown, as "PDSCH reception / PUSCH transmission in the P(S)Cell by scheduling of the PDCCH received in the P(S)Cell, then PDSCH reception / PUSCH transmission in the P(S)Cell by scheduling of the PDCCH received in the SCell, then PDSCH reception / PUSCH transmission in the P(S)Cell by scheduling of the PDCCH received in the P(S)Cell", it is possible to easily switch the reception cell of the PDCCH that performs scheduling for PDSCH reception / PUSCH transmission in the P(S)Cell. From the viewpoint of the base station device 10, it is possible to easily switch the transmission cell of the PDCCH that performs scheduling for PDSCH reception / PUSCH transmission in the P(S)Cell.

[0080] In addition, in order to realize the above-described operation, the schedulingCellInfo = other (schedulingCellId = nl) is set to the terminal 20 from the base station device 10 by the CrossCarrierSchedulingConfig that is the setting information of the P(S)Cell. This is only an example.

[0081] It is also possible to set the above-described schedulingCellInfo = other (schedulingCellId = nl) to the terminal 20 from the base station device 10. An example in this case is described as a variation of Embodiment 1.

[0082] <Variation of Embodiment 1>

[0083] In this variation, Figure 7 An example of a description in a specification book that the terminal 20 refers to (excerpts from Non-Patent Literature 2, showing the change site) is shown.

[0084] As Figure 7 As shown, conditions are added as the value of schedulingCellInfo. The information of the contents of the conditions is cif-Presence, schedulingCellId, and cif-InSchedulingCell.

[0085] The cif-Presence is information that exists in the own of the past, and indicates that the setting target cell is a cell that performs scheduling in cross-carrier scheduling. When cif is received in this cell by DCI, scheduling of another cell (or the present cell) indicated by cif is performed.

[0086] schedulingCellId, cif-InSchedulingCell are information existing in the other in the past. The schedulingCellId indicates the ID of the other cell that performs scheduling in the setting target cell, and the cif-InSchedulingCell indicates the cif corresponding to the setting target cell in the DCI in the other cell.

[0087] In Figure 3 In S101, the schedulingCellInfo = conditions (schedulingCellId = n1, cif = Presence = true) is set to the terminal 20 from the base station device 10 by the CrossCarrierSchedulingConfig which is the setting information of the P(S)Cell.

[0088] The setting information indicates that the PDSCH reception / PUSCH transmission in the P(S)Cell is scheduled by the PDCCH received in the cell other than the P(S)Cell (i.e., the SCell), and the ID of the cell that performs the scheduling is n1. In addition, it also indicates that the PDSCH reception / PUSCH transmission in the P(S)Cell is scheduled by the PDCCH received in the P(S)Cell. In addition, in the case where the PDSCH reception / PUSCH transmission in the P(S)Cell is scheduled by the PDCCH received in the P(S)Cell, the cif in the DCI received in the PDCCH is 0.

[0089] The terminal 20 that receives the setting information monitors the PDCCH of the P(S)Cell in addition to the PDCCH of the SCell designated by the schedulingCellId = n1.

[0090] In addition, "monitoring the PDCCH" can be replaced with "monitoring the DCI transmitted by the PDCCH". In addition, "receiving the PDCCH" can be replaced with "receiving the DCI by the PDCCH". In addition, "decoding the PDCCH" can be replaced with "decoding the DCI". In addition, "decoding the PDCCH" can be replaced with "decoding the DCI format".

[0091] In addition, the base station device 10 can also schedule the PDSCH reception / PUSCH transmission in the P(S)Cell by the PDCCH of the SCell designated by the schedulingCellId = n1, and can also schedule the PDSCH reception / PUSCH transmission in the P(S)Cell by the PDCCH of the P(S)Cell.

[0092] The terminal 20 monitors the PDCCH of the SCell and the PDCCH of the P(S)Cell, and thus, for example, as shown in Figure 5 As shown in "PDSCH reception / PUSCH transmission in the P(S)Cell using the scheduling of the PDCCH received in the P(S)Cell, then PDSCH reception / PUSCH transmission in the P(S)Cell using the scheduling of the PDCCH received in the SCell, and thereafter, PDSCH reception / PUSCH transmission in the P(S)Cell using the scheduling of the PDCCH received in the P(S)Cell", the reception cell of the PDCCH that performs scheduling for PDSCH reception / PUSCH transmission in the P(S)Cell can be easily switched. From the viewpoint of the base station apparatus 10, the transmission cell of the PDCCH that performs scheduling for PDSCH reception / PUSCH transmission in the P(S)Cell can be easily switched.

[0093] With Embodiment 1 (including modifications), it is possible to switch the cell that schedules PDSCH reception / PUSCH transmission in the P(S)Cell between the P(S)Cell and the SCell without performing RRC reconfiguration.

[0094] (Embodiment 2)

[0095] Next, Embodiment 2 will be described. Embodiment 2 is premised on Embodiment 1. That is, with Embodiment 1, the terminal 20 monitors both the PDCCH of the SCell specified by schedulingCellId = nl and the PDCCH of the P(S)Cell as the PDCCH that schedules PDSCH reception / PUSCH transmission in the P(S)Cell. In Embodiment 2, an embodiment of decoding the PDCCH of the SCell and the PDCCH of the P(S)Cell will be described.

[0096] In Embodiment 2, as described in Embodiment 1, the P(S)Cell is set with schedulingCellInfo = other (schedulingCellId = nl) in the terminal 20. In addition, the P(S)Cell can be set with schedulingCellInfo = conditions (cif-Presence = true, schedulingCellId = nl).

[0097] Therefore, the terminal 20 monitors both the PDCCH transmitted by the P(S)Cell and the PDCCH transmitted by the SCell (SCellIndex=n1). In this case, in Embodiment 2, the terminal 20 sets the PDCCH to be decoded in the following modes. These modes are described as Embodiments 2-1 to 2-3.

[0098] In the example described below, the "same time slot" of the P(S)Cell and the SCell is one time slot, but can not be one time slot, but a plurality of time slots. Further, when the SCS is different between the P(S)Cell and the SCell, the time slot length is also different, but in this case, the time slot serving as the basis for the determination of the "same time slot" (length of time) can be the time slot of the P(S)Cell, or the time slot of the SCell. Hereinafter, it is assumed that the time slot lengths of the P(S)Cell and the SCell are the same.

[0099] <Embodiment 2-1>

[0100] In Embodiment 2-1, the terminal 20 receives the PDCCH in the P(S)Cell (schedulingCellInfo=other (schedulingCellId=n1)) and does not receive the PDCCH in the SCell (SCellIndex=n1) in the same time slot.

[0101] This case is, for example, a case where the base station apparatus 10 transmits the PDCCH in the P(S)Cell (schedulingCellInfo=other (schedulingCellId=n1)) and does not transmit the PDCCH in the SCell (SCellIndex=n1) in the same time slot. Alternatively, it can be a case where the base station apparatus 10 has transmitted the PDCCH in the P(S)Cell (schedulingCellInfo=other (schedulingCellId=n1)) and the PDCCH in the SCell (SCellIndex=n1) in the same time slot, but the terminal 20 has received the PDCCH only in the P(S)Cell.

[0102] In this case, as shown in Figure 8 the terminal 20 decodes the PDCCH received in the P(S)Cell (schedulingCellInfo=other (schedulingCellId=n1)). The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the information of the DCI obtained by the decoding (allocation information of time and frequency resources, and the like).

[0103] Embodiment 2-2

[0104] In Embodiment 2-2, the terminal 20 does not receive the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and receives the PDCCH in the SCell (SCellIndex = nl) in the same slot.

[0105] This case is, for example, a case where the base station device 10 does not transmit the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and transmits the PDCCH in the SCell (SCellIndex = nl) in the same slot. Alternatively, it can also be a case where the base station device 10 has transmitted the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and transmitted the PDCCH in the SCell (SCellIndex = nl) in the same slot, but the terminal 20 can receive the PDCCH only in the SCell.

[0106] In this case, as shown in Fig. 2-2, the terminal 20 decodes the PDCCH received in the SCell (SCellIndex = nl). The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the information of the DCI obtained by the decoding (cif indicating the P(S)Cell, allocation information of the time · frequency resources, and the like). Figure 9

[0107] Embodiment 2-3

[0108] In Embodiment 2-3, the terminal 20 receives the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and receives the PDCCH in the SCell (SCellIndex = nl) in the same slot.

[0109] This case is a case where the base station device 10 transmits the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and transmits the PDCCH in the SCell (SCellIndex = nl) in the same slot. There are multiple modes in this case. These modes are described as Embodiments 2-3-1 to 2-3-6 described below. ​

[0110] Embodiment 2-3-1

[0111] In Embodiment 2-3-1, the terminal 20 decodes the PDCCH received in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) without decoding the PDCCH received in the SCell (SCellIndex = nl).

[0112] The terminal 20 performs PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the information of the decoded DCI (allocation information of time · frequency resources, etc.).

[0113] Embodiment 2-3-2

[0114] In Embodiment 2-3-2, the terminal 20 decodes the PDCCH received in the SCell (SCellIndex = nl) without decoding the PDCCH received in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)).

[0115] The terminal 20 performs PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the information of the decoded DCI (cif indicating the P(S)Cell, allocation information of time · frequency resources, etc.).

[0116] Embodiment 2-3-3

[0117] In Embodiment 2-3-3, the terminal 20 decodes the PDCCH received in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) and decodes the PDCCH received in the SCell (SCellIndex = nl).

[0118] In this case, the terminal 20 acquires the decoding result of the PDCCH received in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) (supposed to be DCI-A) and the decoding result of the PDCCH received in the SCell (SCellIndex = nl) (supposed to be DCI-B).

[0119] For example, the terminal 20 performs PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with both of the DCI-A and the DCI-B. In this case, for example, the base station apparatus 10 generates the DCI-A and the DCI-B so that the information of the DCI-A and the information of the DCI-B constitute the information of one DCI. Alternatively, the DCI-A and the DCI-B can be the same.

[0120] Further, the terminal 20 can perform PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with either of the DCI-A and the DCI-B. Further, the condition of decoding explained in Embodiment 2-3-4 can be used for determining which of the DCI-A and the DCI-B is used.

[0121] Further, the terminal 20 can select the DCI to be used from the DCI-A and the DCI-B in accordance with the setting about which of the DCI-A and the DCI-B is used, which is made to the terminal 20 by RRC signaling or MAC signaling.

[0122] <Embodiment 2-3-4>

[0123] In Embodiment 2-3-4, the terminal 20 decides the PDCCH to be decoded (the PDCCH of the P(S)Cell or the PDCCH of the SCell) in accordance with the amount of time resources of the PDCCH in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = n1)).

[0124] The amount of time resources of the PDCCH is, for example, the number of symbols of the PDCCH. The number of symbols of the PDCCH of the P(S)Cell is information set to the terminal 20 from the base station apparatus 10 by RRC signaling.

[0125] For example, if the number of symbols of the PDCCH of the P(S)Cell is X [symbol / slot] or more, the terminal 20 decodes the PDCCH of the P(S)Cell, and if the number of symbols of the PDCCH of the P(S)Cell is less than X [symbol / slot], the terminal 20 decodes the PDCCH of the SCell.

[0126] As for the threshold value X described above, X can be predetermined in accordance with the specification, and X can be held by the terminal 20 (and the base station apparatus 10), X can be set to the terminal 20 from the base station apparatus 10 by RRC signaling (or MAC signaling), and X can be updated by MAC signaling (or RRC signaling).

[0127] Reference Signs Figure 10 , Figure 11 A specific example will be described.Figure 10 、 Figure 11 An example in the case of X = 2 [symbols / slot] is shown.

[0128] In the case shown in FIG. 17, the terminal 20 receives the PDCCH in the P(S)Cell and the SCell respectively within 1 slot. The terminal 20 judges from the setting information that the number of symbols of the PDCCH of the P(S)Cell is less than 2, and decodes only the PDCCH of the SCell. The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the DCI decoded. Figure 10 In the case shown in FIG. 18, the terminal 20 receives the PDCCH in the P(S)Cell and the SCell respectively within 1 slot. The terminal 20 judges from the setting information that the number of symbols of the PDCCH of the P(S)Cell is 2 or more, and decodes only the PDCCH of the P(S)Cell. The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the DCI decoded.

[0129] Figure 11 In the case shown in FIG. 19, the terminal 20 receives the PDCCH in the P(S)Cell and the SCell respectively within 1 slot. The terminal 20 judges from the setting information that the number of symbols of the PDCCH of the P(S)Cell is less than 2, and decodes only the PDCCH of the SCell. The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the DCI decoded.

[0130] <Embodiment 2-3-5>

[0131] The terminal 20 receives the PDCCH in the P(S)Cell and the SCell respectively within 1 slot. In Embodiment 2-3-5, the terminal 20 decodes the PDCCH received first among the PDCCH of the P(S)Cell and the PDCCH of the SCell, and does not decode the PDCCH received later. The terminal 20 performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the DCI decoded.

[0132] The terminal 20 can also decode the PDCCH received later among the PDCCH of the P(S)Cell and the PDCCH of the SCell, and does not decode the PDCCH received first.

[0133] Whether the PDCCH received first among the PDCCH of the P(S)Cell and the PDCCH of the SCell is decoded or the PDCCH received later is decoded can be specified in advance by the specification, and the information can be held by the terminal 20 (and the base station device 10), can be set to the terminal 20 from the base station device 10 by the RRC signaling (or the MAC signaling), or can be updated by the MAC signaling (or the RRC signaling).

[0134] <Embodiment 2-3-6>

[0135] ​In Embodiment 2-3-6, in the terminal 20, "information indicating a cell whose PDCCH is to be decoded, in a case where PDCCHs are received in the P(S)Cell and the SCell respectively in the same 1 slot" is set.

[0136] The terminal 20 decodes the PDCCH of the P(S)Cell, decodes the PDCCH of the SCell, or decodes both the PDCCH of the P(S)Cell and the PDCCH of the SCell, in accordance with the above setting, in a case where PDCCHs are received in the P(S)Cell and the SCell respectively in 1 slot.

[0137] The above information indicating a cell to be decoded can be specified in advance by a specification, and held by the terminal 20 (and the base station apparatus 10), can be set to the terminal 20 from the base station apparatus 10 by RRC signaling (or MAC signaling), or can be updated by MAC signaling (or RRC signaling).

[0138] According to Embodiment 2, it is also possible to switch a cell that schedules PDSCH reception / PUSCH transmission of the P(S)Cell between the P(S)Cell and the SCell without RRC reconfiguration.

[0139] (Embodiment 3)

[0140] Next, Embodiment 3 is described. Embodiment 3 is also premised on Embodiment 1. That is, by Embodiment 1, the terminal 20 monitors both the PDCCH of the SCell specified by schedulingCellld=n1 and the PDCCH of the P(S)Cell as a PDCCH that schedules PDSCH reception / PUSCH transmission of the P(S)Cell. As for an action of decoding at this time, Embodiment 3-1, Embodiment 3-2 are described below.

[0141] <Embodiment 3-1>

[0142] In Embodiment 3-1, the terminal 20 decides a PDCCH to be decoded in accordance with a reception timing of the PDCCH of the SCell, in which the PDCCH of the SCell should be decoded.

[0143] The above information of the reception timing of the PDCCH of the SCell (a specific example is n2 described below) can be specified in advance by a specification, and held by the terminal 20 (and the base station apparatus 10), can be set to the terminal 20 from the base station apparatus 10 by RRC signaling (or MAC signaling), or can be updated by MAC signaling (or RRC signaling).

[0144] For example, the terminal 20 decodes the PDCCH received in the SCell (SCellIndex = nl) after receiving the PDCCH scheduling the PDSCH reception / PUSCH transmission in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = nl)) in the P(S)Cell for n2 [slots] and does not decode the PDCCH received in the P(S)Cell for n2 [slots] from the reception of the PDCCH in the P(S)Cell.

[0145] Referring to Figure 12 , Figure 13 A specific example is described. In Figure 12 , for example, the terminal 20 receives the PDCCH in the P(S)Cell in slot x. Slot x does not correspond to the time interval of "n2 slots from the reception of the PDCCH in the P(S)Cell", and therefore the terminal 20 decodes the PDCCH received in the P(S)Cell in slot x and performs the PDSCH reception / PUSCH transmission according to the decoded DCI.

[0146] The terminal 20 does not decode the PDCCH received in the P(S)Cell for the time interval from the start of slot x+1 to the end of slot x+n2, but decodes the PDCCH received in the SCell. In Figure 12 , the terminal 20 receives the PDCCH in the SCell for the time interval, and therefore decodes it and performs the PDSCH reception / PUSCH transmission in the P(S)Cell according to the decoded DCI.

[0147] After that, as shown in Figure 13 , the terminal 20 receives the PDCCH in the P(S)Cell in slot y. Slot y does not correspond to the time interval of "n2 slots from the reception of the PDCCH in the P(S)Cell", and therefore the terminal 20 decodes the PDCCH received in the P(S)Cell in slot y and performs the PDSCH reception / PUSCH transmission according to the decoded DCI.

[0148] The terminal 20 does not decode the PDCCH received in the P(S)Cell for the time interval from the start of slot y+1 to the end of slot y+n2, but decodes the PDCCH received in the SCell. In Figure 13 , the terminal 20 receives the PDCCH in the SCell for the time interval, and therefore decodes it and performs the PDSCH reception / PUSCH transmission in the P(S)Cell according to the decoded DCI.

[0149] Since the base station device 10 knows the case where the terminal 20 does not decode the PDCCH in the P(S)Cell even if the terminal 20 receives the PDCCH in the P(S)Cell in the time interval from the start of the slot x+1 / y+1 to the end of the slot x+n2 / y+n2, the base station device 10 can not transmit the PDCCH in the P(S)Cell in the time interval from the start of the slot x+1 / y+1 to the end of the slot x+n2 / y+n2.

[0150] In addition, as for the counting of the n2 slots, it is assumed here that it is performed in the slots of the P(S)Cell, but it can also be performed in the slots of the SCell. As for in which cell's slots the counting of the n2 slots is performed, it can be predetermined by a specification, and the information can be held by the terminal 20 (and the base station device 10), it can be set to the terminal 20 from the base station device 10 by RRC signaling (or MAC signaling), or it can be updated by MAC signaling (or RRC signaling).

[0151] As for the time interval that does not correspond to the time interval from the start of the slot x+1 / y+1 to the end of the slot x+n2 / y+n2, the embodiment 2 can also be applied.

[0152] Embodiment 3-2

[0153] In the embodiment 3-2, the terminal 20 decides the PDCCH to be decoded in accordance with the reception timing of the PDCCH of the P(S)Cell in which the terminal 20 should decode the PDCCH.

[0154] As for the information of the reception timing of the PDCCH of the P(S)Cell (a specific example is the n2 described below), it can be predetermined by a specification, and the information can be held by the terminal 20 (and the base station device 10), it can be set to the terminal 20 from the base station device 10 by RRC signaling (or MAC signaling), or it can be updated by MAC signaling (or RRC signaling).

[0155] For example, the terminal 20 does not decode the PDCCH of the SCell between the n2 slots after receiving the PDCCH that schedules the PDSCH reception / PUSCH transmission of the P(S)Cell (schedulingCellInfo = other (schedulingCellId = n1)), but decodes the PDCCH received in the P(S)Cell (schedulingCellInfo = other (schedulingCellId = n1)).

[0156] Reference Signs Figure 14 A specific example will be described. In Figure 14In this case, for example, the terminal 20 receives the PDCCH in the SCell in the time slot x. Since the time slot x does not correspond to the time interval of "n2 time slots from the reception of the PDCCH in the SCell", the terminal 20 decodes the PDCCH received in the SCell in the time slot x, and performs the PDSCH reception / PUSCH transmission in accordance with the decoded DCI.

[0157] The terminal 20 does not decode the PDCCH received in the SCell in the time interval from the start of the time slot x+1 to the end of the time slot x+n2, but decodes the PDCCH received in the P(S)Cell. In this case, the terminal 20 receives the PDCCH in the P(S)Cell in the time interval, and thus decodes it, and performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the decoded DCI. Figure 14

[0158] Thereafter, as shown in FIG. 12, the terminal 20 receives the PDCCH in the SCell in the time slot y. Since the time slot y does not correspond to the time interval of "n2 time slots from the reception of the PDCCH in the SCell", the terminal 20 decodes the PDCCH received in the SCell in the time slot y, and performs the PDSCH reception / PUSCH transmission in accordance with the decoded DCI. Figure 15 The terminal 20 does not decode the PDCCH received in the SCell in the time interval from the start of the time slot y+1 to the end of the time slot y+n2, but decodes the PDCCH received in the P(S)Cell. In this case, the terminal 20 receives the PDCCH in the P(S)Cell in the time interval, and thus decodes it, and performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the decoded DCI.

[0159] Figure 15 The base station apparatus 10 knows the case where the terminal 20 does not decode the PDCCH received in the SCell in the time interval from the start of the time slot x+1 / y+1 to the end of the time slot x+n2 / y+n2, and thus can not transmit the PDCCH in the SCell in the time interval from the start of the time slot x+1 / y+1 to the end of the time slot x+n2 / y+n2.

[0160] The terminal 20 does not decode the PDCCH received in the SCell in the time interval from the start of the time slot x+1 / y+1 to the end of the time slot x+n2 / y+n2, but decodes the PDCCH received in the P(S)Cell. In this case, the terminal 20 receives the PDCCH in the P(S)Cell in the time interval, and thus decodes it, and performs the PDSCH reception / PUSCH transmission in the P(S)Cell in accordance with the decoded DCI.

[0161] ​​In addition, as for the counting of the n2 time slots, it is assumed here to be performed in the time slots of the SCell, but it can also be performed in the time slots of the P(S)Cell. As for in which cell's time slots the counting of the n2 time slots is performed, it can be predetermined by the specification, and the information is held by the terminal 20 (and the base station device 10), it can be set to the terminal 20 from the base station device 10 by RRC signaling (or MAC signaling), or it can be updated by MAC signaling (or RRC signaling).

[0162] As for the time interval that does not correspond to the time interval from the start of the time slot x+1 / y+1 to the end of the time slot x+n2 / y+n2, the embodiment 2 can also be applied.

[0163] In addition, as for which of the actions in the embodiment 3-1 and the embodiment 3-2 should be performed, it can be predetermined by the specification, and the information is held by the terminal 20 (and the base station device 10), it can be set to the terminal 20 from the base station device 10 by RRC signaling (or MAC signaling), or it can be updated by MAC signaling (or RRC signaling).

[0164] With the embodiment 3, it is possible to switch the cell that schedules the PDSCH reception / PUSCH transmission of the P(S)Cell between the P(S)Cell and the SCell without performing RRC reconfiguration. In addition, with the embodiment 3, it is possible to reduce the number of times of decoding compared to the case where all the PDCCHs of the P(S)Cell and the SCell are monitored and decoded.

[0165] (Embodiment 4)

[0166] Next, the embodiment 4 is described. The embodiment 3 is also premised on the embodiment 1. That is, with the embodiment 1, the terminal 20 monitors both the PDCCH of the SCell specified by schedulingCellId=n1 and the PDCCH of the P(S)Cell as the PDCCH that schedules the PDSCH reception / PUSCH transmission of the P(S)Cell.

[0167] In the embodiment 4, the kinds of the PDCCHs that should be monitored in the P(S)Cell and the SCell, respectively, are predetermined or set. The terminal 20 assumes the predetermination or the setting, and performs the monitoring of the PDCCHs in the P(S)Cell and the SCell, respectively.

[0168] The kinds of the PDCCHs that should be monitored in the P(S)Cell and the SCell, respectively, can be predetermined by the specification, and the information is held by the terminal 20 (and the base station device 10), it can be set to the terminal 20 from the base station device 10 by RRC signaling (or MAC signaling), or it can be updated by MAC signaling (or RRC signaling).

[0169] The kind of PDCCH is, for example, a search space in which the PDCCH is monitored or a scheduling target of the PDCCH. The kind of PDCCH can be a beam in which the PDCCH is transmitted (specifically, an SSB index or a CSI-RS resource index in a QCI relationship with the PDCCH). Further, the kind of PDCCH can also be an RNTI used for decoding the DCI.

[0170] In a case where the kind of PDCCH is a search space in which the PDCCH is monitored, the terminal 20 is configured with information indicating that the PDCCH is monitored with a CSS (Common Search Space) in the P(S)Cell and the PDCCH is monitored with a USS (UE-specific Search Space) in the SCell.

[0171] In this case, the terminal 20 monitors the PDCCH with the CSS in the P(S)Cell and monitors the PDCCH with the USS in the SCell.

[0172] Further, in a case where the terminal 20 is configured with information indicating that the PDCCH is monitored with the USS in the P(S)Cell and the PDCCH is monitored with the CSS in the SCell, the terminal 20 monitors the PDCCH with the USS in the P(S)Cell and monitors the PDCCH with the CSS in the SCell.

[0173] In a case where the kind of PDCCH is a scheduling target of the PDCCH (i.e., DCI), the terminal 20 is configured with information indicating that the PDCCH scheduling a PDSCH in the P(S)Cell is monitored and the PDCCH scheduling a PUSCH in the SCell is monitored. In this case, the terminal 20 monitors the PDCCH scheduling the PDSCH in the P(S)Cell and monitors the PDCCH scheduling the PUSCH in the SCell.

[0174] The terminal 20 is configured with information indicating that the PDCCH scheduling a PUSCH in the P(S)Cell is monitored and the PDCCH scheduling a PDSCH in the SCell is monitored. In this case, the terminal 20 monitors the PDCCH scheduling the PUSCH in the P(S)Cell and monitors the PDCCH scheduling the PDSCH in the SCell.

[0175] In Embodiment 4, as a result of the monitoring, the terminal 20 can determine which PDCCH of which cell to decode with respect to the received PDCCH, for example, by applying Embodiment 2 or Embodiment 3.

[0176] (Apparatus Structure)

[0177] Next, functional configuration examples of the base station device 10 and the terminal 20 that execute the processes and actions described so far will be described. The base station device 10 and the terminal 20 include the functions of the above-described Embodiments 1 to 4. However, the base station device 10 and the terminal 20 can each have only the function of any of Embodiments 1 to 4.

[0178] <BASE STATION DEVICE 10>

[0179] Figure 16 is a diagram showing an example of the functional configuration of the base station device 10. As shown in Figure 16 , the base station device 10 has a transmission section 110, a reception section 120, a setting section 130, and a control section 140. Figure 16 The functional configuration shown in the diagram is merely an example. As long as the actions related to the embodiments of the present application can be executed, the functional divisions and the names of the functional sections can be arbitrary. The transmission section 110 and the reception section 120 can be referred to as a communication section.

[0180] The transmission section 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal in a wireless manner. The reception section 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, higher layer information from the received signals. Further, the transmission section 110 has a function of transmitting an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, DL data, and the like to the terminal 20. Further, the transmission section 110 transmits the setting information described in Embodiments 1 to 4.

[0181] The setting section 130 stores setting information set in advance and various setting information transmitted to the terminal 20 in a storage device and reads out from the storage device as necessary. The control section 140 performs, for example, resource allocation and control of the entire base station device 10. In addition, the functional sections in the control section 140 related to signal transmission can be included in the transmission section 110, and the functional sections in the control section 140 related to signal reception can be included in the reception section 120. Further, the transmission section 110 and the reception section 120 can each be referred to as a transmitter and a receiver.

[0182] <TERMINAL 20>

[0183] Figure 17 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Figure 17 , the terminal 20 has a transmission section 210, a reception section 220, a setting section 230, and a control section 240. Figure 17 The functional configuration shown in the diagram is merely an example. As long as the actions related to the embodiments of the present application can be executed, the functional divisions and the names of the functional sections can be arbitrary. The transmission section 210 and the reception section 220 can be referred to as a communication section.

[0184] The transmission section 210 generates a transmission signal from transmission data and transmits the transmission signal wirelessly. The reception section 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals.

[0185] The setting section 230 stores various setting information received by the reception section 220 from the base station device 10 in a storage device and reads out the setting information from the storage device as necessary. Further, the setting section 230 also stores setting information set in advance. The control section 240 performs control of the terminal 20 as a whole and the like. Further, the control section 240 can also perform monitoring of the PDCCH. In addition, the function section of the control section 240 related to signal transmission can be included in the transmission section 210 and the function section of the control section 240 related to signal reception can be included in the reception section 220. Further, the transmission section 210 and the reception section 220 can also be referred to as a transmitter and a receiver, respectively.

[0186] The terminal 20 and the base station device 10 are configured as a terminal and a base station device described in each of the following items, for example. Further, a reception method described in the following is provided.

[0187] (Item 1)

[0188] A terminal, wherein the terminal has:

[0189] a reception section that receives, from a base station device, setting information indicating cross-carrier scheduling for a first cell scheduled from a second cell,

[0190] the reception section monitors a PDCCH of the first cell and a PDCCH of the second cell.

[0191] (Item 2)

[0192] The terminal according to item 1, wherein:

[0193] in a case where the reception section receives a PDCCH in the first cell and receives a PDCCH in the second cell within a time interval of a certain time slot,

[0194] decodes the PDCCH received in the first cell, or

[0195] decodes the PDCCH received in the second cell, or

[0196] decodes both the PDCCH received in the first cell and the PDCCH received in the second cell, or

[0197] decides the PDCCH to be decoded according to an amount of time resources of the PDCCH, or

[0198] decodes the first received PDCCH or the last received PDCCH among the PDCCH received in the first cell and the PDCCH received in the second cell.

[0199] (3)

[0200] The terminal according to (1), wherein

[0201] The receiving section does not decode the PDCCH received in the first cell, but decodes the PDCCH received in the second cell, from the time when the PDCCH is received in the first cell until the time when a certain number of slots elapses, or

[0202] The receiving section does not decode the PDCCH received in the second cell, but decodes the PDCCH received in the first cell, from the time when the PDCCH is received in the second cell until the time when a certain number of slots elapses.

[0203] (4)

[0204] The terminal according to any one of (1) to (3), wherein

[0205] The receiving section monitors, in the first cell and the second cell, respectively, the PDCCH of a type specified or set as a type of PDCCH that should be monitored.

[0206] (5)

[0207] A base station device, wherein the base station device has:

[0208] a transmitting section that transmits, to a terminal, setting information indicating cross carrier scheduling for a first cell from a second cell,

[0209] The transmitting section transmits, in the first cell, a PDCCH that schedules the first cell, or transmits, in the second cell, a PDCCH that schedules the first cell, or transmits, in the first cell, a PDCCH that schedules the first cell and transmits, in the second cell, a PDCCH that schedules the first cell.

[0210] (6)

[0211] A receiving method, wherein the receiving method performs, by a terminal, the steps of:

[0212] receive, from a base station device, setting information indicating cross carrier scheduling for a first cell, which is scheduling by a second cell to the first cell; and

[0213] monitor a PDCCH of the first cell and a PDCCH of the second cell.

[0214] According to the structure of any one of the above, a cell capable of easily switching scheduling for a first cell between the first cell and a second cell is provided.

[0215] (Hardware structure)

[0216] The block diagrams used in the description of the above-described embodiments Figure 16 and Figure 17 illustrate blocks in units of functions. These functional blocks (structural units) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block can be realized using one device that is physically or logically integrated, or two or more devices that are physically or logically separated can be directly or indirectly (for example, using wired, wireless, or the like) connected and realized using these multiple devices. Each functional block can also be realized by combining software with the above-described one device or the above-described multiple devices.

[0217] have judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, and the like, but are not limited thereto. For example, a functional block (structural unit) that causes transmission to function is referred to as a transmitting unit or a transmitter. In any case, as described above, the method of realization is not particularly limited.

[0218] For example, the base station device 10, the terminal 20, and the like in one embodiment of the present disclosure can also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 18is a diagram showing an example of a hardware structure of the base station device 10 and the terminal 20 according to one embodiment of the present disclosure. The base station device 10 and the terminal 20 described above can also be configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like in a physical manner.

[0219] In addition, in the following description, the expression "device" can be replaced with "circuit", "equipment", "unit", or the like. The hardware structure of the base station device 10 and the terminal 20 can be configured to include one or more of each of the devices shown in the drawings, or can be configured not to include a part of the devices.

[0220] Each function in the base station device 10 and the terminal 20 is realized by reading predetermined software (program) into the hardware such as the processor 1001, the storage device 1002, and causing the processor 1001 to perform arithmetic operation and control at least one of communication of the communication device 1004 or reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0221] The processor 1001 controls the entire computer, for example, by causing an operating system to operate. The processor 1001 can also be configured by a central processing device (CPU: Central Processing Unit) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like. For example, the control section 140, the control section 240, and the like described above can also be realized by the processor 1001.

[0222] Further, the processor 1001 reads a program (program code), a software module, or data, and the like from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and performs various processing based on the same. As the program, a program that causes a computer to perform at least a part of the operation described in the above-described embodiment is used. For example, Figure 16 The control section 140 of the base station device 10 shown can also be realized by a control program stored in the storage device 1002 and operated by the processor 1001. Further, for example, Figure 17 The control section 240 of the terminal 20 shown can also be realized by a control program stored in the storage device 1002 and operated by the processor 1001. As for the above-described various processing, although it is described that the above-described various processing is executed by one processor 1001, the above-described various processing can also be executed by two or more processors 1001 simultaneously or sequentially. The processor 1001 can also be mounted by one or more chips. In addition, the program can also be transmitted from a network via a telecommunication line.

[0223] The storage 1002 is a computer-readable recording medium, and can be constituted by at least one of, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), or the like. The storage 1002 can also be referred to as a register, a cache, a main memory (main storage), or the like. The storage 1002 is capable of holding a program (program code), a software module, or the like that can be executed in order to implement a communication method according to an embodiment of the present disclosure.

[0224] The auxiliary storage 1003 is a computer-readable recording medium, and can be constituted by 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 (for example, a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a Key drive), a Floppy (registered trademark) disk, a magnetic stripe, or the like. The auxiliary storage 1003 can also be referred to as an auxiliary storage device. The storage medium described above can be, for example, a database, a server, or another appropriate medium that includes at least one of the storage 1002 and the auxiliary storage 1003.

[0225] The communication device 1004 is hardware (a transceiver device) for communication between computers via at least one of a wired network and a wireless network, and can also be referred to as a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 can also be constituted to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or the like, for example, in order to implement at least one of FDD (Frequency Division Duplex) and TDD (Time Division Duplex). For example, a transceiving antenna, an amplification section, a transceiving section, a transmission path interface, or the like can also be implemented by the communication device 1004. With respect to the transceiving section, installation can be physically or logically separated in a transmission section and a reception section.

[0226] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that implements output to the outside. In addition, the input device 1005 and the output device 1006 can also be integrally constituted (for example, a touch panel).

[0227] Further, the respective devices such as the processor 1001 and the storage device 1002 are connected through a bus 1007 for communication of information. The bus 1007 can be configured using a single bus, or can be configured using different buses between each device.

[0228] Further, the base station device 10 and the terminal 20 can be configured to include a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), a FPGA (Field Programmable Gate Array), or the like, and a part or all of the respective functional blocks can be implemented by the hardware. For example, the processor 1001 can be installed using at least one of these hardware.

[0229] (Supplement to Embodiments)

[0230] The embodiments of the present application have been described above, but the disclosed application is not limited to such embodiments, and various modifications, alternatives, substitutions, replacements, and the like will be understood by those skilled in the art. Specific numerical examples have been described for facilitating understanding of the application, but these numerical examples are only examples, and any appropriate value can be used unless specifically indicated. The division of items in the above description is not essential to the present application, and matters described in two or more items can be used in combination as needed, or matters described in one item can be applied to matters described in another item (as long as there is no contradiction). The boundary of a functional block or a processing block in a functional block diagram does not necessarily correspond to the boundary of a physical component. The actions of multiple functional blocks can be performed physically by one component, or the actions of one functional block can be performed physically by multiple components. The order of processes described in the embodiments can be changed without contradiction. The base station device 10 and the terminal 20 have been described using a functional block diagram for convenience of description of processes, but such devices can also be implemented by hardware, by software, or by a combination thereof. Software operated by the processor possessed by the base station device 10 according to the embodiments of the present application and software operated by the processor possessed by the terminal 20 according to the embodiments of the present application can each be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an EPROM, an EEPROM, a register, a hard disk (HDD), a removable disk, a CD-ROM, a database, a server, and another appropriate arbitrary storage medium.

[0231] Further, the notification of the information is not limited to the forms / embodiments explained in the present disclosure, and can be performed using other methods. For example, the notification of the information can be implemented by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, the RRC signaling can also be referred to as an RRC message, and for example, can be an RRC connection setup message, an RRC connection reconfiguration message, or the like.

[0232] The forms / embodiments explained in the present disclosure can also be applied to at least one of LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA 2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems using other appropriate systems, and next-generation systems extended therefrom. Further, a plurality of systems (e.g., at least one of LTE and LTE-A and 5G, etc.) can also be combined and applied.

[0233] For the processes, timings, flows, and the like of the forms / embodiments described in this specification, the order can be changed without contradiction. For example, for the methods described in this disclosure, the order of the elements of the various steps is prompted using the exemplified order, but is not limited to the specific order prompted.

[0234] In this specification, certain actions performed by the base station device 10 are sometimes performed by an upper node thereof according to the situation. In a network constituted by one or a plurality of network nodes having the base station device 10, it is obvious that various actions performed for communication with the terminal 20 can be performed by at least one of the base station device 10 and other network nodes (for example, consider MME or S-GW or the like, but not limited to these) other than the base station device 10. In the above, a case where the other network node other than the base station device 10 is one is exemplified, but the other network node can also be a combination of a plurality of other network nodes (for example, MME and S-GW).

[0235] Information or a signal and the like described in this disclosure can be output from a higher layer (or lower layer) to a lower layer (or higher layer). It can also be input or output via a plurality of network nodes.

[0236] The information and the like input or output can be saved in a specific location (for example, a memory), and can be managed using a management table. The information and the like input or output can be rewritten, updated, or appended. The information and the like output can also be deleted. The information and the like input can also be transmitted to other devices.

[0237] The determination in this disclosure can be performed by a value (0 or 1) represented by 1 bit, by a Boolean value (true or false), or by comparison of numerical values (for example, comparison with a predetermined value).

[0238] For software, regardless of being called software, firmware, middleware, microcode, hardware description language, or by another name, it should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and the like.

[0239] Moreover, software, commands, information, and so on can be transmitted via transmission media. For example, if the software is transmitted from a webpage, a server, or other remote source using at least one of wired technology (e.g., coaxial cables, fiber optic cables, twisted pair, digital subscriber line (DSL), or the like) and / or wireless technology (e.g., infrared, microwave, or the like), at least a portion of the transmission media is within the definition of transmission media.

[0240] Information, signals, and so on in the disclosure can be represented using any of a variety of different technologies and techniques. For example, data, commands, instructions, information, signals, bits, symbols, chips, and so on that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0241] Further, terms described in the disclosure and terms necessary for understanding the disclosure can be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol can also be a signal (signaling). Further, a signal can also be a message. In addition, a component carrier (CC) can be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

[0242] The terms "system" and "network" and the like used in the disclosure can be used interchangeably.

[0243] Further, information, parameters, and so on described in the disclosure can be represented using absolute values, can be represented using relative values from predetermined values, and can be represented using corresponding other information. For example, a radio resource can also be indicated by an index.

[0244] The names used for the above-described parameters are non-limiting in any respect. Further, the formulas and so on using these parameters are sometimes different from what is explicitly shown in the disclosure. A variety of channels (e.g., PUCCH, PDCCH, and so on) and information elements can be identified by appropriate names, and thus a variety of names allocated to the variety of channels and information elements are non-limiting in any respect.

[0245] In the present disclosure, the terms "base station (BS)", "wireless base station", "base station device", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", and the like can be used interchangeably. The base station is also sometimes referred to as a macro cell, a small cell, a femto cell, a pico cell, and the like.

[0246] A base station can accommodate one or a plurality of (for example, three) cells. In a case where a base station accommodates a plurality of cells, the coverage area of the base station as a whole can be divided into a plurality of smaller areas, and each of the smaller areas can also be provided with communication services by a base station subsystem (for example, a small base station for indoor use (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in the coverage range.

[0247] In the present disclosure, the terms "mobile station (MS)", "user terminal", "user equipment (UE)", "terminal", and the like can be used interchangeably.

[0248] For a mobile station, the person skilled in the art also sometimes refers to it using the following terms: 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 term.

[0249] At least one of the base station and the mobile station can also be referred to as a transmission device, a reception device, a communication device, or the like. In addition, at least one of the base station and the mobile station can be a device mounted on a mobile body, the mobile body itself, or the like. The mobile body can be a vehicle (for example, an automobile, an airplane, or the like), can be a mobile body that moves in an unmanned manner (for example, a drone, an autonomous vehicle, or the like), or can be a robot (manned or unmanned). In addition, at least one of the base station and the mobile station also includes a device that does not necessarily move when performing communication. For example, at least one of the base station and the mobile station can be an IoT (Internet of Things) device such as a sensor.

[0250] Furthermore, the base station device in the present disclosure can also be replaced with a terminal. For example, regarding replacing the communication between the base station device and the terminal with the communication between a plurality of terminals 20 (for example, a structure also referred to as D2D (Device-to-Device), V2X (Vehicle-to-Everything), or the like), each form / embodiment of the present disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station device 10 described above. In addition, the expressions "uplink" and "downlink" and the like can also be replaced with expressions corresponding to the inter-terminal communication (for example, "side"). For example, the uplink channel, the downlink channel, and the like can also be replaced with a side channel.

[0251] Likewise, the terminal in the present disclosure can also be replaced with a base station device. In this case, the base station device can also be configured to have the functions of the terminal described above.

[0252] The terms "determining" and "deciding" as used in the present disclosure also include various actions sometimes. For example, "determining" and "deciding" can include cases where matters that have been judged, calculated, computed, processed, derived, investigated, searched (for example, searched in a table, a database, or other data structures), ascertained, and the like are regarded as "determined" and "decided". In addition, "determining" and "deciding" can include cases where matters that have been received (for example, received information), transmitted (for example, transmitted information), input, output, accessed (for example, accessed data in a memory), and the like are regarded as "determined" and "decided". Furthermore, "determining" and "deciding" can include cases where matters that have been resolved, selected, chosen, established, compared, and the like are regarded as "determined" and "decided". That is, "determining" and "deciding" can include cases where any action has been "determined" and "decided". In addition, "determining" and "deciding" can be replaced with "assuming", "expecting", and "considering".

[0253] The terms "connected" and "coupled" or all modifications of these terms used in the present disclosure are intended to mean all direct or indirect connections or couplings between two or more elements, and can include cases where one or more intervening elements exist between the two elements that are "connected" or "coupled" with each other. The coupling or connection between elements can be a physical coupling or connection, a logical coupling or connection, or a combination of these. For example, "connected" can be replaced with "accessed". In the present disclosure, for two elements, it can be considered that the two elements are "connected" or "coupled" with each other by using at least one of a wire, a cable, and a printed electric connection, and as some non-limiting and non-inclusive examples, by using electromagnetic energy such as electromagnetic energy having a wavelength in a radio frequency domain, a microwave region, and an optical (including both visible and non-visible) region.

[0254] A reference signal can be simply referred to as RS (Reference Signal), and can also be referred to as a pilot depending on the applied standard.

[0255] The expression "according to" as used in the present disclosure does not mean "only according to" unless explicitly stated otherwise. In other words, the expression "according to" means both "only according to" and "at least according to".

[0256] Any reference to elements using the expressions "first", "second", and the like used in the present disclosure does not necessarily limit the number and the order of the elements. These expressions are used in the present disclosure as a convenient method for distinguishing between two or more elements. Therefore, a reference to first and second elements does not mean that there can be only two elements or that the first element must precede the second element in any manner.

[0257] The "unit" in each of the above-described device structures can be replaced with "section", "circuit", "device", or the like.

[0258] When the expressions "include", "including", and variations thereof are used in the present disclosure, these expressions mean the same as the expression "comprising". Also, the expression "or" used in the present disclosure means not only the exclusive or but also the inclusive or.

[0259] A radio frame can be composed of one or more frames in the time domain. One or more frames in the time domain can also be referred to as a subframe. A subframe can be composed of one or more slots in the time domain. A subframe can be a fixed length of time (e.g., 1 ms) regardless of numerology.

[0260] A numerology can also be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The numerology can indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, a specific windowing process performed by a transceiver in the time domain, and the like.

[0261] A slot can be configured with one or a plurality of symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, and the like) in the time domain. A slot can be a time unit based on a numerology.

[0262] A slot can also include a plurality of mini-slots. Each mini-slot can be configured with one or a plurality of symbols in the time domain. In addition, a mini-slot can also be referred to as a sub-slot. A mini-slot can also be configured with a smaller number of symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot can also be referred to as PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot can also be referred to as PDSCH (or PUSCH) mapping type B.

[0263] A radio frame, a subframe, a slot, a mini-slot, and a symbol each represent a time unit for transmitting a signal. A radio frame, a subframe, a slot, a mini-slot, and a symbol can also be referred to by other names respectively corresponding thereto.

[0264] For example, 1 subframe can also be referred to as a transmission time interval (TTI), a plurality of consecutive subframes can also be referred to as a TTI, 1 slot or 1 mini-slot can also be referred to as a TTI. That is, at least one of a subframe and a TTI can be a subframe (1 ms) in the existing LTE, can be a period shorter than 1 ms (for example, 1-13 symbols), or can be a period longer than 1 ms. Furthermore, a unit representing a TTI can not be a subframe, but can be referred to as a slot, a mini-slot, or the like.

[0265] Here, a TTI, for example, refers to a minimum time unit of scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling in which a radio resource (a frequency domain width, a transmission power, and the like, which can be used in each terminal 20) is allocated to each terminal 20 in units of a TTI. Furthermore, the definition of a TTI is not limited thereto.

[0266] A TTI can be a transmission time unit of a data packet (a transport block) after channel coding, a code block, a codeword, or the like, or can be a processing unit of scheduling, link adaptation, or the like. Furthermore, when a TTI is given, an actual time interval (for example, a number of symbols) in which a transport block, a code block, a codeword, or the like is mapped can be shorter than the TTI.

[0267] In addition, in a case where 1 slot or 1 mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) can also constitute the minimum time unit of scheduling. In addition, the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling can also be controlled.

[0268] A TTI having a time length of 1 ms can be referred to as a normal TTI (a TTI in LTE Rel. 8-12), a general TTI, a long TTI, a normal subframe, a general subframe, a long subframe, a slot, etc. A TTI shorter than the general TTI can be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.

[0269] In addition, the long TTI (e.g., normal TTI, subframe, etc.) can be replaced with a TTI having a time length of more than 1 ms, and the short TTI (e.g., shortened TTI, etc.) can be replaced with a TTI having a TTI length shorter than the long TTI and a TTI length of 1 ms or more.

[0270] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and in the frequency domain, can also include one or more contiguous subcarriers. The number of subcarriers included in the RB can be the same regardless of numerologies, for example, can be 12. The number of subcarriers included in the RB can be determined based on numerologies.

[0271] In addition, the time domain of the RB can include one or more symbols, and can also be the length of 1 slot, 1 mini-slot, 1 subframe, or 1 TTI. 1 TTI, 1 subframe, etc. can also be constituted by one or more resource blocks, respectively.

[0272] In addition, one or more RBs can also be referred to as a physical resource block (PRB), a subcarrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0273] In addition, a resource block can also be constituted by one or more resource elements (REs). For example, 1 RE can also be a wireless resource area of 1 subcarrier and 1 symbol.

[0274] A bandwidth part (BWP) (may also be referred to as a partial bandwidth, etc.) can represent a subset of contiguous common resource blocks (RBs) for a certain numerology in a certain carrier. Here, the common RBs can also be determined by indices of the RBs from a common reference point of the carrier. The PRB can also be defined by a certain BWP and numbered within the BWP.

[0275] A BWP for UL (UL BWP) and a BWP for DL (DL BWP) can also be included in the BWP. For a UE, one or more BWPs can also be configured within one carrier.

[0276] At least one of the configured BWPs can also be activated, and the UE can not be assumed to transmit / receive a predetermined signal / channel outside the activated BWP. In addition, "cell", "carrier", etc. in the present disclosure can also be replaced with "BWP".

[0277] The structures of the wireless frame, the subframe, the slot, the mini-slot, the symbol, etc. described above are merely examples. For example, the number of subframes included in the wireless frame, the number of slots per subframe or per wireless frame, the number of mini-slots included in the slot, the number of symbols and RBs included in the slot or the mini-slot, the number of subcarriers included in the RB, and the number of symbols, the symbol length, the cyclic prefix (CP) length, etc. in the TTI can be variously changed.

[0278] In the present disclosure, for example, in a case where an article is added by a translation of a, an, and the in English, the present disclosure also includes a case where the article following these articles is plural.

[0279] In the present disclosure, the expression "A and B are different" can also mean that "A and B are different from each other". In addition, the expression can also mean that "A and B are different from C, respectively". The expressions "separate", "combine", etc. can also be interpreted as "different" in the same manner.

[0280] Each form / embodiment described in the present disclosure can be used alone, can be used in combination, and can also be switched for use according to execution. In addition, the notification of the predetermined information is not limited to being performed explicitly (for example, notification of "X is X"), and can also be performed implicitly (for example, without performing the notification of the predetermined information).

[0281] In addition, in the present disclosure, the SS block or the CRI-RS is an example of a synchronization signal or a reference signal.

[0282] The present disclosure has been described in detail above, but it should be understood that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in various modified and changed forms without departing from the spirit and scope of the present disclosure defined by the claims. Therefore, the present disclosure is intended to be illustrative, not limiting.

[0283] REFERENCE NUMERALS

[0284] 10 base station device

[0285] 110 transmission section

[0286] 120 reception section

[0287] 130 setting section

[0288] 140 control section

[0289] 20 terminal

[0290] 210 transmission section

[0291] 220 reception section

[0292] 230 setting section

[0293] 240 control section

[0294] 1001 processor

[0295] 1002 storage device

[0296] 1003 auxiliary storage device

[0297] 1004 communication device

[0298] 1005 input device

[0299] 1006 output device

Claims

1. A terminal having: a reception section that receives first setting information indicating cross carrier scheduling for a primary cell or a primary secondary cell and a secondary cell; and a control section that controls at least one of reception in a downlink shared channel of the primary cell or the primary secondary cell and transmission in an uplink shared channel of the primary cell or the primary secondary cell based on the first setting information, the first setting information including schedulingCellInfo, the primary cell or the primary secondary cell being scheduled by the terminal by being set as schedulingCellInfo = own, the primary cell or the primary secondary cell being scheduled by the secondary cell by being set as schedulingCellInfo = other.

2. The terminal according to claim 1, wherein the control section monitors a downlink control channel of the primary cell or the primary secondary cell and a downlink control channel in the secondary cell.

3. The terminal according to claim 1, wherein the reception section receives second setting information related to decoding of a first downlink control channel of the primary cell or the primary secondary cell and a second downlink control channel of the secondary cell, the control section controls to decode the first downlink control channel and the second downlink control channel based on the second setting information.

4. The terminal according to claim 1, wherein the reception section receives second setting information related to decoding of a first downlink control channel of the primary cell or the primary secondary cell and a second downlink control channel of the secondary cell, the control section controls to decode either one of the first downlink control channel and the second downlink control channel based on the second setting information.

5. A communication method executed by a terminal, having: a step of receiving first setting information indicating cross carrier scheduling for a primary cell or a primary secondary cell and a secondary cell; and a step of controlling at least one of reception in a downlink shared channel of the primary cell or the primary secondary cell and transmission in an uplink shared channel of the primary cell or the primary secondary cell based on the first setting information, the first setting information including schedulingCellInfo, the primary cell or the primary secondary cell being scheduled by the terminal by being set as schedulingCellInfo = own, the primary cell or the primary secondary cell being scheduled by the secondary cell by being set as schedulingCellInfo = other.

6. A base station having: a transmission section that transmits first setting information indicating cross carrier scheduling for a primary cell or a primary secondary cell and a secondary cell; and ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ a control section that controls at least one of reception in a downlink shared channel of the primary cell or the primary secondary cell and transmission in an uplink shared channel of the primary cell or the primary secondary cell based on the first configuration information, the first configuration information includes schedulingCellInfo, the primary cell or the primary secondary cell is scheduled by the own cell by being set as schedulingCellInfo = own, and the primary cell or the primary secondary cell is scheduled by the secondary cell by being set as schedulingCellInfo = other.

7. A communication system including a terminal and a base station, the terminal has: a reception section that receives first configuration information indicating cross-carrier scheduling with respect to the primary cell or the primary secondary cell, which is scheduled by a primary cell or a primary secondary cell and a secondary cell; and a control section that controls at least one of reception in a downlink shared channel of the primary cell or the primary secondary cell and transmission in an uplink shared channel of the primary cell or the primary secondary cell based on the first configuration information, the base station has: a transmission section that transmits the first configuration information; and a control section that controls at least one of transmission for reception in a downlink shared channel and reception for transmission in an uplink shared channel based on the first configuration information, the first configuration information includes schedulingCellInfo, the primary cell or the primary secondary cell is scheduled by the own cell by being set as schedulingCellInfo = own, and the primary cell or the primary secondary cell is scheduled by the secondary cell by being set as schedulingCellInfo = other.

Images