Terminal and communication method

Abstract

This terminal has: a communication unit that receives, from a base station, a parameter related to multi-cell multi-channel scheduling and downlink control information (DCI); and a control unit that determines, on the basis of the parameter, bit positions constituting a specific field included in the DCI. The communication unit receives or transmits a channel scheduled by the DCI.

Description

Terminal and communication method 【0001】 The present invention relates to a terminal and a communication method in a wireless communication system. 【0002】 In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to further increase system capacity, further increase data transmission speed, further reduce latency in the radio section, etc., a wireless communication method called 5G or NR (New Radio) (hereinafter, this wireless communication method is referred to as "NR") is being studied. In 5G, in order to meet the requirement of achieving a throughput of 10 Gbps or more and reducing the latency in the radio section to 1 ms or less, various wireless technologies and network architectures are being studied (for example, Non-Patent Document 1 and Non-Patent Document 2). 【0003】 Among this technology, as multi-carrier enhancement (MCE: Multi-Carrier Enhancements), in 3GPP Release 18, multi-carrier scheduling (which may also be called multi-cell scheduling) was defined to reduce the overhead of signaling. Multi-carrier scheduling enables scheduling of multiple cells with one downlink control information (DCI: Downlink Control Information) (for example, Non-Patent Document 3 and Non-Patent Document 4). 【0004】 Also, in 3GPP Release 18, the physical downlink shared channel (PDSCH: Physical Downlink Shared Channel) / physical uplink control channel (PUCCH: Physical Uplink Control Channel) in each cell scheduled by multi-carrier scheduling was limited to one. However, in 3GPP Release 19, multi-carrier scheduling has become capable of scheduling a plurality of PDSCH / PUCH in each cell (which may be called multi-cell PDSCH / PUCH scheduling, multi-cell - multi-PDSCH / PUCH scheduling). 【0005】 Furthermore, multiple DCI format field types were agreed upon. These multiple DCI field types include, for example, a type (Type 2) that has separate fields to notify each of the co-scheduled cells by DCI. 【0006】 3GPP TS 38.300 V18.2.0(2024-06)3GPP TS 38.401 V18.2.0(2024-06)3GPP TS 38.212 V18.2.0(2024-06)3GPP TS 38.331 V18.2.0(2024-06) 【0007】 According to Non-Patent Document 3, DCI format 0_1 / 1_1 is a DCI that performs single or multi-PUSCH / PDSCH scheduling in a single cell (which may also be called single-PUSCH / PDSCH scheduling or multi-PUSCH / PDSCH scheduling). DCI format 0_3 / 1_3 is a DCI that performs single-cell / multi-cell PUSCH / PDSCH scheduling (which may also be called single-cell PUSCH / PDSCH scheduling, multi-cell PUSCH / PDSCH scheduling, or multi-cell-multi-PUSCH / PDSCH scheduling). Note that PUSCH / PDSCH may be replaced with PUSCH and / or PDSCH. 【0008】 In multi-PUSCH / PDSCH scheduling, for each PUSCH / PDSCH, information indicating the initial transmission or retransmission of uplink / downlink data (NDI: New Data Indicator) and a redundant version (RV: Redundancy Version) related to redundancy are notified in DCI. Here, in multi-cell multi-PUSCH / PDSCH scheduling, for example, for the NDI or RV field in the DCI format, it is necessary to determine the bit positions of the block, which is the notification unit for each scheduled cell, and the entire field containing each block. 【0009】This invention has been made in view of the above points, and aims to appropriately perform multi-carrier scheduling in a wireless communication system. 【0010】 According to the disclosed technology, a terminal is provided which includes a communication unit that receives parameters and DCI (Downlink Control Information) related to multi-cell multi-channel scheduling from a base station, and a control unit that determines the bit positions constituting a specific field included in the DCI based on the parameters, wherein the communication unit receives or transmits channels scheduled by the DCI. 【0011】 According to the disclosed technology, multi-carrier scheduling can be properly performed in a wireless communication system. 【0012】This is a diagram illustrating a wireless communication system in an embodiment of the present invention. This is a diagram illustrating a wireless communication system in an embodiment of the present invention. This is a flowchart illustrating multi-cell scheduling in an embodiment of the present invention. This is a diagram illustrating an example of multi-cell scheduling (1). This is a diagram illustrating an example of multi-cell scheduling (2). This is a diagram illustrating an example of DCI field configuration (1) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (2) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (3) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (4) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (5) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (6) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (7) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (8) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (9) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (10) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (11) in an embodiment of the present invention. This is a diagram illustrating an example of DCI field configuration (12) in an embodiment of the present invention. This is a diagram illustrating an example (13) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (14) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (15) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (16) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (17) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (18) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (19) of the DCI field configuration in an embodiment of the present invention.This is a diagram illustrating an example (20) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (21) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (22) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (23) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (24) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (25) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (26) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (27) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (28) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (29) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (30) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (31) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (32) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (33) of the DCI field configuration in an embodiment of the present invention. This is a diagram illustrating an example (34) of the DCI field configuration in an embodiment of the present invention. This figure shows an example of the functional configuration of the base station 10 in an embodiment of the present invention. This figure shows an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This figure shows an example of the hardware configuration of the base station 10 or terminal 20 in an embodiment of the present invention. This figure shows an example of the configuration of the vehicle 2001 in an embodiment of the present invention. 【0013】 Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below. 【0014】In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified. 【0015】 Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE technologies, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. In NR, the above terms will be referred to as SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE. 【0016】 Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex). 【0017】 Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured. 【0018】Figure 1 shows an example of the configuration of a wireless communication system in an embodiment of the present invention. The wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20. 【0019】 Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, PSS and SSS. System information is transmitted, for example, via PBCH and is also called broadcast information. Synchronization signals and system information may be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both base station 10 and terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using Carrier Aggregation (CA). In addition, the terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10 using Dual Connectivity (DC). 【0020】Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals. 【0021】 Figure 2 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A, which will be an MN (Master Node), and a base station 10B, which will be an SN (Secondary Node), are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B. 【0022】 A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells. 【0023】 The processing operations in this embodiment may be performed using the system configuration shown in Figure 1, the system configuration shown in Figure 2, or any other system configuration. In the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning. 【0024】As part of Multi-Carrier Enhancements (MCE), 3GPP Release 18 specifies multi-carrier scheduling (also known as multi-cell scheduling) to reduce signaling overhead. Multi-carrier scheduling makes it possible to schedule multiple cells with a single Downlink Control Information (DCI) (for example, Non-Patent Documents 3 and 4). 【0025】 Furthermore, in 3GPP Release 18, the number of Physical Downlink Shared Channels (PDSCHs) and Physical Uplink Control Channels (PUCCHs) scheduled in each cell using multi-carrier scheduling was limited to one. However, in 3GPP Release 19, multi-carrier scheduling made it possible to schedule multiple PDSCHs / PUCCHs in each cell (this may also be called multi-cell multi-PDSCH / PUCCH scheduling). 【0026】 Furthermore, multiple DCI format field types were agreed upon. These multiple DCI field types include, for example, a type (Type 2) that has separate fields to notify each of the co-scheduled cells by DCI. 【0027】In MCE (Multi-carrier enhancements), a single DCI may support co-scheduling cells of different SCS and / or carrier types. A single DCI may support one or more PUSCH / PDSCH schedulings per scheduled cell. The maximum number of PUSCH / PDSCH per scheduled cell may be four or eight. In multi-cell scheduling, the Type 1 HARQ-ACK codebook does not need to be extended. The maximum number of Type 2 HARQ-ACK codebooks does not need to be increased. The UE does not need to assume that both single-cell multi-PUSCH / PDSCH scheduling and multi-cell multi-PUSCH / PDSCH scheduling are set up in the same or different cells within the same PUCCH group. 【0028】 Furthermore, the multi-cell scheduling supported in Rel-18 MCE may be extended in the following respects. Note that " / " may be replaced with "and / or". 【0029】 - In Rel-18, multiple cells that could be scheduled with a single DCI (DCI format 0_3 / 1_3) were all limited to the same SCS and carrier type. In Rel-19, this restriction is removed, making co-scheduling of cells with different SCS or carrier types possible. - In Rel-18, when scheduling multiple cells with a single DCI (DCI format 0_3 / 1_3), the number of PDSCH / PUSCH per cell was limited to one. In Rel-19, it becomes possible to schedule multiple PDSCH / PUSCH per cell. 【0030】DCI field types may be applied. DCI field type 1A is defined when there are multiple scheduled cells and a single notification is applied to all jointly scheduled cells by the DCI field; DCI field type 1B is defined when a single notification is the index of the joint notification and is applied to each jointly scheduled cell; DCI field type 1C is defined when a single notification is applied to only a specific scheduled cell; DCI field type 2 is defined when each jointly scheduled cell has a separate notification field; and DCI field type 3 is defined when either DCI field type 1A or DCI field type 2 can be set. 【0031】 For example, in DCI format 0_3 or 1_3, NDI is DCI field type 2, and RV is DCI field type 2. Hereinafter, DCI format 0_3 or 1_3 will also be referred to as DCI format 0_3(1_3). The notation scheduledCellComboListDCI-0-3(1-3) may be replaced with scheduledCellComboListDCI-0-3 and / or scheduledCellComboListDCI-1-3. 【0032】 According to Non-Patent Literature 3, when a scheduledCellComboListDCI-0-3(1-3) is set for cells that are scheduled together, a combination pattern of cells that are scheduled together is set for each entry in scheduledCellComboListDCI-0-3(1-3), and the cell included in the entry selected in the scheduled cells indicator field of the DCI becomes a co-scheduled cell. 【0033】If scheduledCellComboListDCI-0-3(1-3) is not set, the scheduled cells indicator field in DCI will be 0 bits, and the cells set in scheduledCellListDCI-0-3(1-3) will be the cells that are jointly scheduled. 【0034】 Whether or not PDSCH / PUSCH is actually scheduled for each cell may be determined by whether the block corresponding to each cell in the FDRA (Frequency Domain Resource Allocation) field notifies a valid allocation or an invalid allocation. 【0035】 According to Non-Patent Document 3, when scheduledCellComboListDCI-0-3(1-3) is set, the DCI format size for scheduling jointly scheduled cells is determined by the settings of each cell that result in the largest size among the entries. If scheduledCellComboListDCI-0-3(1-3) is not set, the DCI format size may be determined by the settings of each cell set in the scheduled cell list scheduledCellListDCI-0-3(1-3). 【0036】 Furthermore, since UE can only decode a predetermined number of DCI formats of different sizes, the DCI size is determined based on the RRC settings and does not need to change dynamically for each DCI. 【0037】 According to Non-Patent Document 3, an example of an FDRA field is as follows. Other Type 2 fields such as MCS, NDI, RV, and HPN are similar. 【0038】When scheduledCellComboListDCI-0-3(1-3) is set and the number of its entries is 2 or more, the number of blocks (boxes for notifications for each cell) is the number of co-scheduled cells notified in the scheduled cells indicator field. Although the number of blocks or the size of each block changes dynamically depending on which cells are scheduled, since the size of the DCI format is determined based on the RRC configuration, padding is performed to match the size. 【0039】 When scheduledCellComboListDCI-0-3(1-3) is set and the number of its entries is 1, the number of blocks is the number of cells included in the entry set in scheduledCellComboListDCI-0-3(1-3). 【0040】 When scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks is the number of cells set in scheduledCellListDCI-0-3(1-3). 【0041】 As a specific example, as shown in Table 1, assume that 4 cells (cell #1 / 2 / 3 / 4) are set in scheduledCellListDCI-0-3(1-3). 【0042】 【0043】 As shown in Table 2, when an entry of scheduledCellComboListDCI-0-3(1-3) is set, the overall size of the DCI format is determined according to the case that requires the largest size among the cases where 0, 1, or 2 is indicated by the scheduled cells indicator (in the example, the case where Cell#1, Cell#2, and Cell#3 are scheduled at Index 1 has a larger size than the other two cases, so it is the size required for the case where 3 cells are scheduled). 【0044】 【0045】 For the number of blocks in the type 2 field of FDR A, MCS, NDI, RV, HPN, etc., in the example of Table 2, when the value of the scheduled cells indicator is 0 or 2, the number of blocks is 2, and when the value of the scheduled cells indicator is 1, the number of blocks is 3. When the value of the scheduled cells indicator notified by DCI is 0 or 2, the number of blocks in the type 2 field is 2 each, and the required number of bits is smaller than the size of the DCI format. However, it is padded to match the size when 3 cells are scheduled. 【0046】 When scheduledCellComboListDCI-0-3(1-3) is not set, the size of the entire DCI format is determined according to the case where Cell#1 / 2 / 3 / 4 is scheduled. In this example, the number of blocks in the type 2 field of FDR A, MCS, NDI, RV, HPN, etc. is 4. 【0047】 In single cell - multi - PDSCH / PUSCH scheduling by DCI format 0_1 / 1_1, NDI and RV are notified by DCI for each PDSCH / PUSCH. The size of NDI / RV is determined as follows according to the number of PDSCH / PUSCH that can be scheduled or have been scheduled in the TDRA (Time Domain Resource Allocation) field. ・When only 1 PDSCH / PUSCH is scheduled, the size of NDI is 1 bit and the size of RV is 2 bits. ・When two or more PDSCH / PUSCH are scheduled, the size of NDI or RV is the number of bits corresponding to the maximum number of PDSCH / PUSCH that can be notified in TDRA (determined by the entry set in the TDRA table n). ・RV is notified in 2 bits from RV = 0, 1, 2, 3 when only 1 PDSCH / PUSCH is scheduled, and is notified in 1 bit each for each PDSCH / PUSCH from RV = 0, 2 when two or more PDSCH / PUSCH are scheduled. 【0048】Furthermore, the following operations may be applied for multi-cell multi-PDSCH / PUSCH scheduling. 【0049】 Operation 1a) In each corresponding cell according to DCI format 0_3 (1_3), set the number of bits to be equal to the maximum number of schedulable PDSCH / PUSCH. Operation 1b) In all cells according to DCI format 0_3 (1_3), set the number of bits to be equal to the maximum number of schedulable PDSCH / PUSCH. Operation 2) In each corresponding cell according to DCI format 0_3 (1_3), set the number of bits to be equal to the number of PDSCH / PUSCH actually scheduled. Operation 3) If the number of scheduled PDSCH / PUSCH is 1, set NDI to 1 bit; otherwise, apply Operation 1. 【0050】 The method for determining the size of the NDI and RV fields when multi-cell multi-PDSCH / PUSCH scheduling is set according to DCI format 0_3 / 1_3 may be defined as follows. 【0051】 Figure 3 is a flowchart illustrating an example of multi-cell scheduling in an embodiment of the present invention. In step S101, multi-cell scheduling is set for UE. This setting may be done, for example, by RRC parameters from BS to UE. For example, scheduledCellComboListDCI-0-3(1-3) and scheduledCellListDCI-0-3(1-3) may be such RRC parameters. 【0052】 In step S102, the UE determines a specific field size of the DCI format. When the UE receives a DCI format, it may determine a specific field size of the DCI format and interpret the DCI format based on that field size. 【0053】Alt. 1: The size of each block in NDI and RV, and / or the total size of all blocks, may be determined differently depending on whether scheduledCellComboListDCI-0-3(1-3) is set or not. 【0054】 Alt. 1-1 (Operation 2 or Operation 1a) Example: If scheduledCellComboListDCI-0-3(1-3) is set, the size of each block will be the number of bits equal to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 2). Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the size of each block will be the number of bits equal to the maximum number of PDSCH / PUSCH that can be scheduled for that cell (Operation 1a). 【0055】 Alt. 1-2 (Operation 2 or Operation 1b) Example: If scheduledCellComboListDCI-0-3(1-3) is set, the size of each block will be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 2). Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the total size of all blocks will be the number of bits corresponding to the maximum total number of PDSCH / PUSCH for multiple schedulable cells, and the size of each block will be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 1b). 【0056】 Alt. 1-3 (Operation 1b or Operation 1a) Example: If scheduledCellComboListDCI-0-3(1-3) is set, the total size of all blocks will be the number of bits equal to the maximum total number of PDSCH / PUSCH for multiple cells that can be scheduled, and the size of each block will be the number of bits equal to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 1b). Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the size of each block will be the number of bits equal to the maximum number of PDSCH / PUSCH that can be scheduled for that cell (Operation 1a). 【0057】 Alt. 1': The size of each block in the NDI and RV, and / or the total size of all blocks, may be determined by different methods depending on whether the UE supports notifications regarding commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3). 【0058】 Alt. 1'-1 (Operation 2 or Operation 1a) Example: If notifications for commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3) are supported, the size of each block shall be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 2). Example: If notifications for commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3) are not supported, the size of each block shall be the number of bits corresponding to the maximum number of PDSCH / PUSCH that can be scheduled for that cell (Operation 1a). 【0059】 Alt. 1'-2 (Operation 2 or Operation 1b) Example: When supporting notifications for commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3), the size of each block shall be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 2). Example: When not supporting notifications for commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3), the total size of all blocks shall be the number of bits corresponding to the maximum total number of PDSCH / PUSCH for multiple schedulable cells, and the size of each block shall be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 1b). 【0060】Alt. 1'-3 (Operation 1b or Operation 1a) Example: When supporting notifications related to commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3), the total size of all blocks shall be the number of bits equal to the maximum total number of PDSCH / PUSCH for multiple schedulable cells, and the size of each block shall be the number of bits equal to the number of PDSCH / PUSCH actually scheduled for that cell (Operation 1b). Example: When not supporting notifications related to commonly scheduled cells by scheduledCellComboListDCI-0-3(1-3), the size of each block shall be the number of bits equal to the maximum number of PDSCH / PUSCH that can be scheduled for that cell (Operation 1a). 【0061】 For example, as a concrete example of Alt. 1-1, if tdra-FieldIndexListDCI-0-3-r19 is not set for each block of NDI, the cell may be 1 bit. If tdra-FieldIndexListDCI-0-3-r19 is set, the cell is N ｍａｘ＿ＰＵＳＣＨ It may also be a bit. N ｍａｘ＿ＰＵＳＣＨ This is the maximum number of PUSCHs that can be scheduled among all entries in the upper layer parameter push-TimeDomainAllocationListForMultiPUSCH-r19 if scheduledCellComboListDCI-0-3 is not set, and the number of PUSCHs that are scheduled to the cell if scheduledCellComboListDCI-0-3 is set. 【0062】 Alt. 2: The method for determining the number of blocks for NDI and RV may differ depending on whether or not multi-cell multi-PDSCH / PUSCH scheduling is set. 【0063】Alt. 2-1: When multi-cell multi-PDSCH / PUSCH scheduling is set, the number of blocks for NDI and RV may be set to 1, and the size of the block may be set to the maximum number of bits equal to the total number of PDSCH / PUSCH for the multiple cells that can be scheduled (equivalent to operation 1b). 【0064】 Alt. 2-2: When multi-cell multi-PDSCH / PUSCH scheduling is set, the method for determining the number of blocks and block size of NDI and RV may differ depending on whether scheduledComboListDCI-0-3(1-3) is set or not. 【0065】 Example: If scheduledCellComboListDCI-0-3(1-3) is set, the number of blocks for NDI and RV will be 1, and the size of each block will be the number of bits equal to the maximum total number of PDSCH / PUSCH for multiple cells that can be scheduled. Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks for NDI and RV will be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block will be the number of bits equal to the maximum number of PDSCH / PUSCH that can be scheduled for that cell. 【0066】 Alt. 2-2-1: Example: If scheduledCellComboListDCI-0-3(1-3) is set, the number of blocks in NDI and RV will be 1, and the size of each block will be the number of bits equal to the maximum total number of PDSCH / PUSCH for multiple cells that can be scheduled. Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks in NDI and RV will be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block will be the number of bits equal to the number of PDSCH / PUSCH actually scheduled for that cell. 【0067】Alt. 2-2-2: Example: If scheduledCellComboListDCI-0-3(1-3) is set, the number of blocks for NDI and RV will be the maximum number of total PDSCH / PUSCH for multiple cells that can be scheduled, and the size of each block will be the number of bits required for NDI / RV notification for each PDSCH / PUSCH. Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks for NDI and RV will be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block will be the number of bits equal to the maximum number of PDSCH / PUSCH that can be scheduled for that cell. Alternatively, if scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks in NDI and RV will be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block will be the number of bits corresponding to the number of PDSCH / PUSCH actually scheduled for that cell. 【0068】 For multi-cell multi-PDSCH / PUSCH scheduling, the following options may be specified for the NDI and RV fields to extend the number of bits within each block. The number of bits may be specified to be the number of PDSCH / PUSCHs that can be scheduled for that cell, or the number of PDSCH / PUSCHs that can be scheduled for all commonly scheduled cells. The following options may apply to the notification of NDI or RV in DCI format 0_3 / 1_3. 【0069】 Option 1) The number of bits in each block of the field is equal to the maximum number of PUSCH / PDSCH on the corresponding cell that can be scheduled by DCI format 0_3 / 1_3. This maximum number is determined by the TDRA table for that cell. 【0070】Option 2a) The number of bits in the field block corresponding to the scheduled cell is equal to the maximum number of PUSCH / PDSCH that can be scheduled by DCI format 0_3 / 1_3 among all co-scheduled cells. The number of bits in the field block corresponding to a given scheduled cell is equal to the actual number of PUSCH / PDSCH that can be scheduled by DCI format 0_3 / 1_3 in that cell. If the actual number of PUSCH / PDSCH that can be scheduled by DCI format 0_3 / 1_3 is less than the maximum number of PUSCH / PDSCH that can be scheduled by DCI format 0_3 / 1_3 among all co-scheduled cells, some reserved bits may be set. 【0071】 Figure 4 illustrates an example of multi-cell scheduling (1). As shown in Figure 4, if the number of PUSCH / PDSCH actually scheduled (e.g., 3 in Figure 4) is less than the maximum number of PUSCH / PDSCH that can be scheduled (e.g., 4 in Figure 4), the remaining bits may be filled with zeros to fix the field and / or block size. Note that PXSCH may be replaced with PUSCH or PDSCH. 【0072】 According to Non-Patent Document 3, for Type 1A fields that are not divided into blocks (e.g., PDSCH-to-HARQ_feedback timing indicator), the size may be adjusted at the field level by inserting zeros into the MSB. However, no method for inserting zeros is specified for Type 2NDI or RV fields at the block level. 【0073】 Figure 5 is a diagram illustrating an example of multi-cell scheduling (2). According to Non-Patent Literature 3, as shown in Figure 5, the order of blocks in each field may be in ascending order of the serving cell index. However, the order of PXSCH within a block is not specified. 【0074】As mentioned above, if the actual number of PXSCH / PDSCHs scheduled is less than the maximum number of PXSCH / PDSCHs that can be scheduled, it is necessary to fill the remaining bits with zeros to fix the field and / or block size. The order of PXSCHs within the block must be specified. 【0075】 The following 1)-4) may be determined while considering their correspondence with the cell index. 【0076】 1) Whether to insert zeros at the field and / or block level starting from the MSB or starting from the LSB. 【0077】 2) Should PUSCH / PDSCH entries within a field and / or block be sorted in ascending or descending order of the serving cell index? 【0078】 3) In the case of FDRA-based scheduling, since the position of each NDI and / or RV field in the DCI field is fixed, the padding and sorting order may be determined so that the bit positions within the field are fixed. Note that FDRA-based scheduling may also refer to scheduling when scheduledCellComboListDCI-0-3(1-3) is not set. 【0079】 4) The method for determining the size of a field may differ depending on whether scheduledCellComboListDCI-0-3(1-3) is set, and different rules may apply to the zero-padding method, block order, and / or PXSCH order within a block depending on the method for determining the size. 【0080】 If the actual number of PUSCH / PDSCHs scheduled is less than the maximum number of PUSCH / PDSCHs that can be scheduled, adjustment bits may be inserted to fix the size. 【0081】The adjustment bit insertion may be applied to type 2 fields (e.g., NDI / RV fields). A 0 may be inserted as the size adjustment bit. The adjustment bit may be inserted so that the bit position is fixed on a field-by-field basis, or so that the bit position is fixed on a block-by-block basis within a field. The adjustment bit may be inserted from the most significant bit (MSB) or the least significant bit (LSB) of the field and / or block. The operation related to adjustment bit insertion may be defined differently depending on whether the notification method for co-scheduled cells is FDRA-based or scheduled cell indicator-based (i.e., whether scheduledCellComboListDCI-0-3(1-3) is set or not). 【0082】 The order of bits within the DCI field block corresponding to the scheduled PUSCH / PDSCH may be defined. For example, the order of bits within the field block corresponding to each cell may be defined. 【0083】 The sorting order may also be applied to type 2 fields (e.g., NDI / RV fields). The sorting order may be ascending or descending order of PUSCH / PDSCH scheduled for a cell. The behavior related to the sorting order may be defined differently depending on whether the notification method for co-scheduled cells is FDRA-based or scheduled cell indicator-based (i.e., whether scheduledCellComboListDCI-0-3(1-3) is set or not). 【0084】 The following assumes scheduling when a cell set, as shown in Figure 5, contains four cells. The notification mechanism for the scheduled cells is assumed to be either Case 1) or Case 2) below. 【0085】Case 1) FDRA-based (when scheduledCellComboListDCI-0-3(1-3) is not set). 【0086】 Case 2) Based on scheduled cell indicator (when scheduledCellComboListDCI-0-3(1-3) is set). This also includes cases where the scheduled cell is cell A + cell B + cell C + cell D, where the scheduled cell is cell A + cell B, where the scheduled cell is cell A, etc. 【0087】 The entries in the joint TDRA table may be assumed to be as follows: For example, 4 PXSCH may be scheduled for each cell, or up to 16 PXSCH may be scheduled across all scheduled cells, with a maximum of 4 PXSCH per cell. 3 PXSCH may be scheduled for each cell, 2 PXSCH may be scheduled for each cell, or 1 PXSCH may be scheduled for each cell. 【0088】 The following description uses the NDI field as an example, but the scheduling method described below may also be applied to the RV field or other Type 2 fields. The bit width of the RV field may be 2 bits, and each bit of the NDI field below may be replaced by the 2 bits of the RV field. 【0089】 The following describes Case 1) where FDRA-based and option 1) described above are applied. 【0090】 Operation 1-1) Figure 6 is a diagram illustrating an example (1) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 4+4+4+4 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 6. The PXSCH within the blocks may be arranged in ascending order or descending order. 【0091】Note that 4+4+4+4PXSCH may also mean scheduling 4PXSCH for cell A, 4PXSCH for cell B, 4PXSCH for cell C, and 4PXSCH for cell D, and so on. Furthermore, the adjustment bits below may be replaced with zero padding. 【0092】 Operation 1-2) Figure 7 is a diagram illustrating an example (2) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+3+3 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 7. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 7, adjustment bits may be inserted from the LSB within a block, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. 【0093】 Figure 8 is a diagram illustrating an example (3) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 3+3+3+3 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 8. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 8, adjustment bits may be inserted from the MSB within a block, resulting in similar operation at the block level and field level, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. 【0094】 Furthermore, when the adjustment bits are inserted from the LSB in ascending order, and when the adjustment bits are inserted from the MSB in descending order, no bit position floating occurs. 【0095】Operation 1-3) Figure 9 is a diagram illustrating an example (4) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 4+4+0+0 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 9. The PXSCH within the blocks may be arranged in ascending order or descending order. 【0096】 Operation 1-4) Figure 10 is a diagram illustrating an example (5) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 10. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 10, adjustment bits may be inserted from the LSB within a block, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. Adjustment bits may be inserted in blocks that are not scheduled. 【0097】 Figure 11 is a diagram illustrating an example (6) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 11. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 11, adjustment bits may be inserted from the MSB within a block, resulting in similar operation at the block level and field level, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. Adjustment bits may be inserted in blocks that are not scheduled. 【0098】Operation 1-5) Figure 12 is a diagram illustrating an example (7) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 12. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 12, adjustment bits may be inserted from the LSB within a block, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. Adjustment bits may be inserted in blocks that are not scheduled. 【0099】 Figure 13 is a diagram illustrating an example (8) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 13. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 13, adjustment bits may be inserted from the MSB within a block, resulting in similar operation at the block level and field level, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. Adjustment bits may be inserted into blocks that are not scheduled. 【0100】 The following describes Case 1) where the FDRA base and option 2a) described above are applied. 【0101】 Operation 2-1) Figure 14 is a diagram illustrating an example (9) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 4+4+4+4PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 14. The PXSCH within the blocks may be arranged in ascending order or descending order. 【0102】Operation 2-2) Figure 15 is a diagram illustrating an example (10) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 3+3+3+3PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 15. The PXSCHs within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 15, adjustment bits may be inserted from the LSB in the field. 【0103】 Figure 16 is a diagram illustrating an example (11) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 3+3+3+3PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 16. The PXSCH within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 16, adjustment bits may be inserted in the field from the MSB. 【0104】 Note that bit position floating occurs within the NDI or RV field, but floating does not occur in the NDI or RV field position itself. 【0105】 Operation 2-3) Figure 17 is a diagram illustrating an example (12) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+0+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 17. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 17, adjustment bits may be inserted from the LSB in the field. 【0106】Figure 18 is a diagram illustrating an example (13) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 4+4+0+0 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 18. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 18, adjustment bits may be inserted in the field from the MSB. 【0107】 Operation 2-4) Figure 19 is a diagram illustrating an example (14) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 19. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 19, adjustment bits may be inserted from the LSB in the field. 【0108】 Figure 20 is a diagram illustrating an example (15) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 20. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 20, adjustment bits may be inserted in the field from the MSB. 【0109】 Operation 2-5) Figure 21 is a diagram illustrating an example (16) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 21. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 21, adjustment bits may be inserted from the LSB in the field. 【0110】Figure 22 is a diagram illustrating an example (17) of the DCI field configuration in an embodiment of the present invention. When FDRA-based notifications for 3+0+3+0 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 22. The PXSCHs within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted in the field from the MSB, as shown in Figure 20. 【0111】 The following describes Case 2) based on scheduled cell indicators and the application of Option 1) described above. 【0112】 Operation 3-1) Figure 23 is a diagram illustrating an example (18) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications for 4+4+4+4 PXSCH are made on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order, as shown in Figure 23. The PXSCH within the block may be arranged in ascending order or descending order. 【0113】 Operation 3-2) Figure 24 is a diagram illustrating an example (19) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+3+3 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 24. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 24, adjustment bits may be inserted from the LSB within a block, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. 【0114】Figure 25 is a diagram illustrating an example (20) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+3+3 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 25. The PXSCHs within a block may be arranged in ascending or descending order. Furthermore, as shown in Figure 25, adjustment bits may be inserted from the MSB within a block, resulting in similar operation at the block level and field level, and the association between each bit of NDI or RV and the position of the leading PXSCH may be fixed. 【0115】 Furthermore, bit position floating occurs both within the NDI or RV field and across the entire NDI or RV field location. 【0116】 Operation 3-3) Figure 26 is a diagram illustrating an example (21) of the DCI field configuration in an embodiment of the present invention. When scheduling cell notification-based notifications for 4+4+0+0 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 26. The PXSCH within the blocks may be arranged in ascending or descending order. Also, as shown in Figure 26, bits from other fields may be placed after the NDI field, and adjustment bits may be placed after other fields. 【0117】Operation 3-4) Figure 27 is a diagram illustrating an example (22) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+0+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 27. The PXSCHs in the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 27, adjustment bits may be inserted from the LSB within the blocks, and the association between each bit of the NDI or RV and the position of the leading PXSCH may be fixed. Also, as shown in Figure 27, bits of other fields may be arranged following the NDI field, and further adjustment bits may be arranged following other fields. 【0118】 Figure 28 is a diagram illustrating an example (23) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+0+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 28. The PXSCHs within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 28, adjustment bits may be inserted from the MSB within the blocks, resulting in similar operation at the block and field levels, and the association between each bit of the NDI or RV and the position of the leading PXSCH may be fixed. Also, as shown in Figure 28, bits from other fields may be placed following the NDI field, and adjustment bits may be placed following other fields. 【0119】Operation 3-5) Figure 29 is a diagram illustrating an example (24) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+0+3+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 29. The PXSCHs in the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 29, adjustment bits may be inserted from the LSB within the blocks, and the association between each bit of the NDI or RV and the position of the leading PXSCH may be fixed. Also, as shown in Figure 29, bits of other fields may be arranged following the NDI field, and further adjustment bits may be arranged following other fields. 【0120】 Figure 30 is a diagram illustrating an example (25) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+0+3+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 30. The PXSCHs within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 30, adjustment bits may be inserted from the MSB within the blocks, resulting in similar operation at the block and field levels, and the association between each bit of the NDI or RV and the position of the leading PXSCH may be fixed. Also, as shown in Figure 30, bits from other fields may be placed following the NDI field, and adjustment bits may be placed following other fields. 【0121】 The following describes Case 2) based on scheduled cell indicators and the application of option 2a) described above. 【0122】Operation 4-1) Figure 31 is a diagram illustrating an example (26) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications for 4+4+4+4 PXSCH are made on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order, as shown in Figure 31. The PXSCH within the blocks may be arranged in ascending or descending order. 【0123】 Operation 4-2) Figure 32 is a diagram illustrating an example (27) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+3+3PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 24. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted from the LSB in the field, as shown in Figure 32. 【0124】 Figure 33 is a diagram illustrating an example (28) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+3+3PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 33. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted in the field from the MSB, as shown in Figure 33. 【0125】 Furthermore, bit position floating occurs both within the NDI or RV field and across the entire NDI or RV field location. 【0126】Operation 4-3) Figure 34 is a diagram illustrating an example (29) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 4+4+0+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 34. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted from the LSB in the field, as shown in Figure 34. 【0127】 Figure 35 is a diagram illustrating an example (30) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 4+4+0+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 35. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, as shown in Figure 35, adjustment bits may be inserted in the field from the MSB. 【0128】 Operation 4-4) Figure 36 is a diagram illustrating an example (31) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+0+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 36. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted from the LSB in the field, as shown in Figure 36. 【0129】Figure 37 is a diagram illustrating an example (32) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+3+0+0PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 37. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted in the field from the MSB, as shown in Figure 37. 【0130】 Operation 4-5) Figure 38 is a diagram illustrating an example (33) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications are made for 3+0+3+0 PXSCH on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 38. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted from the LSB in the field, as shown in Figure 38. 【0131】 Figure 39 is a diagram illustrating an example (34) of the DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notifications for 3+0+3+0 PXSCH are made on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order, as shown in Figure 39. The PXSCH within the blocks may be arranged in ascending or descending order. Furthermore, adjustment bits may be inserted in the field from the MSB, as shown in Figure 39. 【0132】 The above-described embodiment makes it possible to determine the bit positions of specific fields and blocks in the DCI format and to correctly interpret the DCI format when performing multi-cell multi-PDSCH / PUSCH scheduling. 【0133】 In other words, multi-carrier scheduling can be properly executed in wireless communication systems. 【0134】(Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment. 【0135】 <Base Station 10> Figure 40 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 40, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 40 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. 【0136】 The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes. 【0137】 The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to multi-cell scheduling. 【0138】 As described in the embodiment, the control unit 140 performs control related to settings, instructions, and notifications concerning multi-cell scheduling, etc. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. 【0139】<Terminal 20> Figure 41 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 41, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 41 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit. 【0140】 The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiving unit 220 also receives setting information, instructions, and notifications related to multi-cell scheduling from the base station 10. For example, the receiving unit 220 receives DCI for multi-cell scheduling from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to multi-cell scheduling. 【0141】 As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying about multi-cell scheduling. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220. 【0142】(Hardware Configuration) The block diagrams (Figures 40 and 41) used in the description of the above embodiments show functional units. These functional blocks (components) 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 may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software. 【0143】 Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited. 【0144】 For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 42 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically 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, etc. 【0145】In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices. 【0146】 Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003. 【0147】 The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001. 【0148】Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 40 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 41 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line. 【0149】 The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure. 【0150】The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003. 【0151】 The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section. 【0152】 The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel). 【0153】Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device. 【0154】 Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components. 【0155】 Figure 43 shows an example of the configuration of vehicle 2001. As shown in Figure 43, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013. 【0156】 The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user. 【0157】The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit). 【0158】 Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc. 【0159】 The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.). 【0160】The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions. 【0161】 The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001. 【0162】 The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station. 【0163】The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input. 【0164】 The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001. 【0165】<Configuration relating to this embodiment> (1) A terminal comprising: a communication unit that receives parameters and DCI (Downlink Control Information) related to multi-cell multi-channel scheduling from a base station; and a control unit that determines the bit positions constituting a specific field included in the DCI based on the parameters, wherein the communication unit is a terminal that receives or transmits channels scheduled by the DCI. (2) The terminal according to paragraph 1, wherein the control unit determines the bit positions constituting the specific field based on whether or not a list of cell combinations scheduled by the parameters is set. (3) The terminal according to paragraph 1, wherein the control unit sets the number of bits in a block within the specific field to the number of bits corresponding to the maximum number of channels in a certain schedulable cell, or to the number of bits corresponding to the maximum number of channels in the largest cell among all schedulable cells. (4) The terminal according to paragraph 1, wherein the control unit arranges the bits corresponding to channels in a block within the specific field in ascending or descending order. (Clause 5) The terminal according to Clause 1, wherein the control unit inserts adjustment bits from the MSB (Most significant bit) or LSB (Least significant bit) into the specific field or a block within the specific field in order to match the bit width. (Clause 6) A communication method in which a terminal performs the following steps: receiving parameters and DCI (Downlink Control Information) related to multi-cell multi-channel scheduling from a base station; determining the bit positions constituting a specific field included in the DCI based on the parameters; and receiving or transmitting a channel scheduled by the DCI. 【0166】Any of the above configurations, i.e., multi-carrier scheduling can be properly performed in a wireless communication system. Furthermore, according to claims 2-5, when performing multi-cell multi-PDSCH / PUSCH scheduling, the bit positions of specific fields and blocks in the DCI format can be determined, and the DCI format can be correctly interpreted. 【0167】 (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, etc. 【0168】Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper 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 combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. 【0169】 Each aspect / embodiment described in this disclosure may be applied to at least one of the following systems: 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®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G). 【0170】 The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order. 【0171】 In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW). 【0172】 The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes. 【0173】 Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices. 【0174】 The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value). 【0175】Software should be broadly interpreted to mean instructions, instruction 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 so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name. 【0176】 Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium. 【0177】 The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. 【0178】 In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc. 【0179】 The terms “system” and “network” as used in this disclosure are interchangeable. 【0180】Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index. 【0181】 The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way. 【0182】 In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell. 【0183】 A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage. 【0184】In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information. 【0185】 In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably. 【0186】 A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms. 【0187】At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor. 【0188】 Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel. 【0189】 Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above. 【0190】 As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering." 【0191】The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain. 【0192】 The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard. 【0193】 In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on." 【0194】 Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way. 【0195】 In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc. 【0196】Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR. 【0197】 A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology. 【0198】 Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain. 【0199】 A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurologic. 【0200】A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B. 【0201】 Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms. 【0202】 For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe. 【0203】 Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this. 【0204】TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI. 【0205】 Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled. 【0206】 A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called 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. 【0207】 Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more. 【0208】 A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology. 【0209】Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks. 【0210】 One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc. 【0211】 Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol. 【0212】 A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP. 【0213】 A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE. 【0214】 At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP". 【0215】The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways. 【0216】 In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural. 【0217】 In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different." 【0218】 Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification). 【0219】 Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. 【0220】This international patent application claims priority based on Japanese Patent Application No. 2024-219479, filed on 13 December 2024, and the entire contents of Japanese Patent Application No. 2024-219479 are incorporated herein by reference. 【0221】 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a communication unit that receives parameters related to multi-cell multi-channel scheduling and DCI (Downlink Control Information) from a base station; and a control unit that determines the bit positions constituting a specific field included in the DCI based on the parameters, wherein the communication unit receives or transmits channels scheduled by the DCI.

2. The terminal according to claim 1, wherein the control unit determines the bit positions constituting the particular field based on whether or not a list of cell combinations scheduled by the parameter is set.

3. The terminal according to claim 1, wherein the control unit sets the number of bits in the block within the specific field to a number of bits corresponding to the maximum number of channels in a schedulable cell, or to a number of bits corresponding to the maximum number of channels in the largest cell among all schedulable cells.

4. The terminal according to claim 1, wherein the control unit arranges the bits corresponding to channels in blocks within a specific field in ascending or descending order.

5. The terminal according to claim 1, wherein the control unit inserts adjustment bits from the MSB (Most significant bit) or LSB (Least significant bit) into the specific field or block within the specific field in order to align the bit width.

6. A communication method in which a terminal performs the following steps: a procedure for receiving parameters and DCI (Downlink Control Information) related to multi-cell multi-channel scheduling from a base station; a procedure for determining the bit positions constituting a specific field included in the DCI based on the parameters; and a procedure for receiving or transmitting a channel scheduled by the DCI.

Images