Terminal and communication method

Abstract

To appropriately perform multi-carrier scheduling in a wireless communication system.SOLUTION: A terminal includes 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 bit positions that constitute specific fields included in the DCI on the basis of the parameters, and the communication unit receives or transmits channels scheduled by the DCI.SELECTED DRAWING: Figure 5

Description

[Technical Field]

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, this wireless communication system will be referred to as "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while keeping the latency in wireless sections to 1 ms or less (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0003] Among these technologies, multi-carrier scheduling (which may also be called multi-cell scheduling) is defined as multi-carrier enhancements (MCE) in 3GPP Release 18 to reduce signaling overhead. Multi-carrier scheduling makes it possible to schedule multiple cells with one downlink control information (DCI) (e.g., Non-Patent Document 3 and Non-Patent Document 4).

[0004] In addition, in 3GPP Release 18, the number of Physical Downlink Shared Channels (PDSCHs) / Physical Uplink Control Channels (PUCCHs) scheduled in each cell by multicarrier scheduling was limited to one. However, in 3GPP Release 19, multicarrier scheduling allows multiple PDSCHs / PUSCHs to be scheduled in each cell (this may also be referred to as multi-cell PDSCH / PUSCH scheduling or multi-cell-multi PDSCH / PUSCH scheduling).

[0005] Additionally, multiple DCI format field types have been agreed upon, including, for example, Type 2, which has separate fields for reporting information for each of the co-scheduled cells by the DCI. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 38.300 V18.2.0(2024-06) [Non-patent document 2] 3GPP TS 38.401 V18.2.0(2024-06) [Non-patent document 3] 3GPP TS 38.212 V18.2.0(2024-06) [Non-patent document 4] 3GPP TS 38.331 V18.2.0(2024-06) Summary of the Invention [Problem to be solved by the invention]

[0007] According to Non-Patent Document 3, DCI formats 0_1 / 1_1 are DCIs that perform single or multi-PUSCH / PDSCH scheduling in a single cell (which may also be referred to as single-PUSCH / PDSCH scheduling or multi-PUSCH / PDSCH scheduling). DCI formats 0_3 / 1_3 are DCIs that perform PUSCH / PDSCH scheduling in a single cell / multi-cell (which may also be referred to as 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, information indicating initial transmission or retransmission of uplink data / downlink data (NDI: New Data Indicator) and a redundancy version (RV: Redundancy Version) related to redundancy are signaled by DCI for each PUSCH / PDSCH. 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 blocks, which are the notification units for each scheduled cell, and the entire field including each block.

[0009] The present invention has been made in view of the above points, and has as its object to appropriately perform multi-carrier scheduling in a wireless communication system. [Means for solving the problem]

[0010] According to the disclosed technology, a terminal is provided which includes 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 bit positions that constitute specific fields included in the DCI based on the parameters, and the communication unit receives or transmits channels scheduled by the DCI. [Effects of the Invention]

[0011] According to the disclosed technology, multi-carrier scheduling can be appropriately performed in a wireless communication system. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 3] 1 is a flowchart illustrating multi-cell scheduling according to an embodiment of the present invention. [Figure 4] FIG. 1 is a diagram for explaining an example (1) of multi-cell scheduling. [Figure 5] FIG. 10 is a diagram for explaining an example (2) of multi-cell scheduling. [Figure 6] FIG. 1 is a diagram illustrating an example (1) of a DCI field configuration according to an embodiment of the present invention. [Figure 7] FIG. 10 is a diagram illustrating an example (2) of a DCI field configuration according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram illustrating an example (3) of a DCI field configuration according to an embodiment of the present invention. [Figure 9] FIG. 10 is a diagram illustrating an example (4) of a DCI field configuration according to an embodiment of the present invention. [Figure 10]FIG. 10 is a diagram illustrating an example (5) of a DCI field configuration according to an embodiment of the present invention. [Figure 11] FIG. 10 is a diagram illustrating an example (6) of a DCI field configuration according to an embodiment of the present invention. [Figure 12] FIG. 10 is a diagram illustrating an example (7) of a DCI field configuration according to an embodiment of the present invention. [Figure 13] FIG. 10 is a diagram illustrating an example (8) of a DCI field configuration according to an embodiment of the present invention. [Figure 14] FIG. 9 is a diagram illustrating an example (9) of a DCI field configuration according to an embodiment of the present invention. [Figure 15] FIG. 10 is a diagram illustrating an example (10) of a DCI field configuration according to an embodiment of the present invention. [Figure 16] FIG. 11 is a diagram illustrating an example (11) of a DCI field configuration according to an embodiment of the present invention. [Figure 17] FIG. 12 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 18] FIG. 13 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 19] FIG. 14 is a diagram illustrating an example (14) of a DCI field configuration according to an embodiment of the present invention. [Figure 20] FIG. 15 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 21] FIG. 16 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 22] FIG. 17 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 23] FIG. 18 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 24] FIG. 19 is a diagram illustrating an example of a DCI field configuration according to an embodiment of the present invention. [Figure 25] FIG. 2 is a diagram illustrating an example (20) of a DCI field configuration according to an embodiment of the present invention. [Figure 26] FIG. 2 is a diagram illustrating an example (21) of a DCI field configuration according to an embodiment of the present invention. [Figure 27] FIG. 2 is a diagram illustrating an example (22) of a DCI field configuration according to an embodiment of the present invention. [Figure 28] FIG. 2 is a diagram illustrating an example (23) of a DCI field configuration according to an embodiment of the present invention. [Figure 29] FIG. 2 is a diagram illustrating an example (24) of a DCI field configuration according to an embodiment of the present invention. [Figure 30] FIG. 2 is a diagram illustrating an example (25) of a DCI field configuration according to an embodiment of the present invention. [Figure 31] FIG. 2 is a diagram illustrating an example (26) of a DCI field configuration according to an embodiment of the present invention. [Figure 32] FIG. 2 is a diagram illustrating an example (27) of a DCI field configuration according to an embodiment of the present invention. [Figure 33] FIG. 2 is a diagram illustrating an example (28) of a DCI field configuration according to an embodiment of the present invention. [Figure 34] FIG. 2 is a diagram illustrating an example (29) of a DCI field configuration according to an embodiment of the present invention. [Figure 35] FIG. 3 is a diagram illustrating an example (30) of a DCI field configuration according to an embodiment of the present invention. [Figure 36] FIG. 3 is a diagram illustrating an example (31) of a DCI field configuration according to an embodiment of the present invention. [Figure 37] FIG. 10 is a diagram illustrating an example (32) of a DCI field configuration according to an embodiment of the present invention. [Figure 38] FIG. 3 is a diagram illustrating an example of a DCI field configuration (33) according to an embodiment of the present invention. [Figure 39]FIG. 10 is a diagram illustrating an example of a DCI field configuration (34) according to an embodiment of the present invention. [Figure 40] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 41] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 42] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 43] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

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

[0014] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0015] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, 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), are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned terms in NR are 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 method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0017] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

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

[0019] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, a PSS and an SSS. The system information is, for example, transmitted via a PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in a downlink (DL) and receives control signals or data from the terminal 20 in an uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0020] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the 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. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0021] Fig. 2 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. Fig. 2 shows an example of the configuration of a wireless communication system in which DC (Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 can communicate with both the base station 10A and the base station 10B.

[0022] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.

[0023] The processing operations in this embodiment may be executed in the system configuration shown in Fig. 1, in the system configuration shown in Fig. 2, or in other system configurations. 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] In order to reduce signaling overhead, 3GPP Release 18 defines multi-carrier scheduling (which may also be called multi-cell scheduling) as Multi-Carrier Enhancements (MCE). Multi-carrier scheduling enables scheduling of multiple cells with one Downlink Control Information (DCI) (see, for example, Non-Patent Document 3 and Non-Patent Document 4).

[0025] In addition, in 3GPP Release 18, the number of Physical Downlink Shared Channels (PDSCHs) / Physical Uplink Control Channels (PUCCHs) scheduled in each cell by multicarrier scheduling was limited to one. However, in 3GPP Release 19, multicarrier scheduling allows multiple PDSCHs / PUSCHs to be scheduled in each cell (this may be referred to as multi-cell multi-PDSCH / PUSCH scheduling).

[0026] Additionally, multiple DCI format field types have been agreed upon, including, for example, Type 2, which has separate fields for reporting information for each of the co-scheduled cells by the DCI.

[0027] In MCE (Multi-carrier enhancements), a single DCI may support co-scheduling cells with different SCSs and / or carrier types. A single DCI may support scheduling of one or multiple PUSCHs / PDSCHs per scheduled cell. A maximum of four or eight PUSCHs per scheduled cell may be supported. Note that in multi-cell scheduling, the type-1 HARQ-ACK codebook need not be extended. Note that the maximum number of type-2 HARQ-ACK codebooks need not be increased. Note that a UE does not need to assume that both single-cell multi-PUSCH / PDSCH scheduling and multi-cell multi-PUSCH / PDSCH scheduling are configured in the same or different cells in the same PUCCH group.

[0028] Furthermore, the multi-cell scheduling supported by 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 one DCI (DCI format 0_3 / 1_3) were restricted to all having the same SCS and carrier type. In Rel-19, this restriction has been lifted, allowing co-scheduling of cells with different SCS or carrier types. In Rel-18, when scheduling multiple cells with one DCI (DCI format 0_3 / 1_3), the number of PDSCH / PUSCH per cell was limited to one. In Rel-19, multiple PDSCH / PUSCH can be scheduled per cell.

[0030] DCI field types may be applied. When there are multiple scheduled cells, the following DCI fields are defined: DCI field type 1A, in which one notification is commonly applied to all co-scheduled cells; DCI field type 1B, in which one notification is a joint notification index and is applied to each co-scheduled cell; DCI field type 1C, in which one notification is applied only to a specific scheduled cell; DCI field type 2, in which a separate notification field is provided for each co-scheduled cell; and DCI field type 3, which can be set to either DCI field type 1A or DCI field type 2.

[0031] For example, the NDI in DCI format 0_3 or 1_3 is DCI field type 2, and the RV is DCI field type 2. Hereinafter, DCI format 0_3 or 1_3 will also be described as DCI format 0_3(1_3). The description scheduledCellComboListDCI-0-3(1-3) may be replaced with scheduledCellComboListDCI-0-3 and / or scheduledCellComboListDCI-1-3.

[0032] According to non-patent document 3, when a scheduled cell combination list scheduledCellComboListDCI-0-3(1-3) is set for a co-scheduled cell, a co-scheduled cell combination pattern is set in each entry of scheduledCellComboListDCI-0-3(1-3), and the cell included in the entry selected in the scheduled cell indicator field of the DCI becomes the co-scheduled cell.

[0033] If scheduledCellComboListDCI-0-3(1-3) is not set, the scheduled cells indicator field in DCI is 0 bit, and the cells set in scheduledCellListDCI-0-3(1-3) are the cells to be jointly scheduled.

[0034] Whether or not PDSCH / PUSCH is actually scheduled for each cell may be determined by whether a valid allocation or an invalid allocation is notified in a block corresponding to each cell in an FDRA (Frequency Domain Resource Allocation) field.

[0035] According to Non-Patent Document 3, when scheduledCellComboListDCI-0-3(1-3) is set for the DCI format size for scheduling jointly scheduled cells, the DCI format size is determined by the setting of each cell that has the largest size among the entries. When scheduledCellComboListDCI-0-3(1-3) is not set, the DCI format size may be determined by the setting of each cell set in the scheduled cell list scheduledCellListDCI-0-3(1-3).

[0036] Note that since a UE can only decode a predetermined number of DCI formats of different sizes, the DCI size is determined based on the RRC configuration and does not need to be dynamically changed for each DCI.

[0037] According to Non-Patent Document 3, an example of the FDRA field is as follows: The same applies to other Type 2 fields such as MCS, NDI, RV, and HPN.

[0038] If scheduledCellComboListDCI-0-3 (1-3) is set and the number of entries is 2 or more, the number of blocks (boxes containing notifications for each cell) will be the number of co-scheduled cells notified in the scheduled cells indicator field. The number of blocks or the size of each block changes dynamically depending on which cell is scheduled, but 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 entries is 1, the number of blocks is the number of cells included in the entries set in scheduledCellComboListDCI-0-3(1-3).

[0040] If scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks will be the number of cells set in scheduledCellListDCI-0-3(1-3).

[0041] As a specific example, it is assumed that four cells (cell #1 / 2 / 3 / 4) are set in scheduledCellListDCI-0-3(1-3) as shown in Table 1.

[0042] [Table 1]

[0043] As shown in Table 2, when the scheduledCellComboListDCI-0-3 (1-3) entry is set, the overall size of the DCI format is determined according to the case where the largest size is required among the cases where the scheduled cells indicator indicates 0, 1, or 2 (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 three cells are scheduled).

[0044] [Table 2]

[0045] In the example of Table 2, the number of blocks in the type 2 fields such as FDRA, MCS, NDI, RV, and HPN is two when the scheduled cells indicator value is 0 or 2, and three when the scheduled cells indicator value is 1. When the scheduled cells indicator value notified by the DCI is 0 or 2, the number of blocks in the type 2 field is two, and the number of required bits is smaller than the size of the DCI format, but padding is performed to make the size the same as when three cells are scheduled.

[0046] If 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 for Type 2 fields such as FDRA, MCS, NDI, RV, and HPN is 4.

[0047] In single-cell multi-PDSCH / PUSCH scheduling using DCI format 0_1 / 1_1, the NDI and RV are notified for each PDSCH / PUSCH by DCI. The size of the NDI / RV is determined as follows depending on how many PDSCHs / PUSCHs 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 the NDI is 1 bit and the size of the RV is 2 bits. When two or more PDSCHs / PUSCHs are scheduled, the size of the NDI or RV is the number of bits for the maximum number of PDSCHs / PUSCHs that can be notified by TDRA (determined by the entry set in TDRA table n). · When only one PDSCH / PUSCH is scheduled, RV is notified using two bits from RV=0, 1, 2, 3, and when two or more PDSCH / PUSCH are scheduled, RV is notified for each PDSCH / PUSCH using one bit from RV=0, 2.

[0048] Also, for multi-cell-multi-PDSCH / PUSCH scheduling, the following operations may be applied.

[0049] Action 1a) In each corresponding cell according to DCI format 0_3 (1_3), the number of bits is set to be equal to the maximum number of PDSCH / PUSCHs that can be scheduled. Action 1b) In all cells with DCI format 0_3 (1_3), the number of bits is set to be equal to the maximum number of PDSCH / PUSCHs that can be scheduled. Operation 2) In each corresponding cell according to DCI format 0_3 (1_3), the number of bits is set equal to the number of PDSCH / PUSCH actually scheduled. Operation 3) If the number of scheduled PDSCH / PUSCHs is 1, set NDI to 1 bit; otherwise, apply operation 1.

[0050] A method for determining the sizes of the NDI and RV fields when multi-cell-multi-PDSCH / PUSCH scheduling using DCI format 0_3 / 1_3 is configured may be specified as follows.

[0051] 3 is a flowchart illustrating an example of multi-cell scheduling according to an embodiment of the present invention. In step S101, multi-cell scheduling is configured in the UE. This configuration may be, for example, a configuration by an RRC parameter from the BS to the UE. For example, scheduledCellComboListDCI-0-3(1-3) and scheduledCellListDCI-0-3(1-3) may be the RRC parameters.

[0052] In step S102, the UE determines a specific field size of the DCI format. When the UE receives the DCI format, the UE may determine the specific field size of the DCI format and interpret the DCI format based on the field size.

[0053] Alt. 1: The size of each block of 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.

[0054] Alt.1-1 (action 2 or action 1a) Example: When scheduledCellComboListDCI-0-3(1-3) is set, the size of each block is set to the number of bits corresponding to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 2). Example: When scheduledCellComboListDCI-0-3(1-3) is not set, the size of each block is set to the number of bits equal to the maximum number of PDSCHs / PUSCHs that can be scheduled for the cell (operation 1a).

[0055] Alt.1-2 (action 2 or action 1b) Example: When scheduledCellComboListDCI-0-3(1-3) is set, the size of each block is set to the number of bits corresponding to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 2). Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the total size of all blocks shall be the number of bits equal to the maximum total number of PDSCHs / PUSCHs for multiple cells that can be scheduled, and the size of each block shall be the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 1b).

[0056] Alt.1-3 (action 1b or action 1a) Example: When scheduledCellComboListDCI-0-3(1-3) is set, the total size of all blocks is the number of bits equal to the maximum total number of PDSCHs / PUSCHs for multiple cells that can be scheduled, and the size of each block is the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 1b). Example: When scheduledCellComboListDCI-0-3(1-3) is not set, the size of each block is set to the number of bits equal to the maximum number of PDSCHs / PUSCHs that can be scheduled for the cell (operation 1a).

[0057] Alt. 1': The size of each block of NDI and RV and / or the total size of all blocks may be determined differently depending on whether the UE supports notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3).

[0058] Alt.1'-1 (action 2 or action 1a) Example: When supporting notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3), the size of each block is set to the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 2). Example: When notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3) is not supported, the size of each block shall be the number of bits equal to the maximum number of PDSCHs / PUSCHs that can be scheduled for the cell (operation 1a).

[0059] Alt.1'-2 (action 2 or action 1b) Example: When supporting notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3), the size of each block is set to the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 2). Example: When notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3) is not supported, the total size of all blocks shall be the number of bits equal to the maximum total number of PDSCHs / PUSCHs for multiple cells that can be scheduled, and the size of each block shall be the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 1b).

[0060] Alt.1'-3 (action 1b or action 1a) Example: When supporting notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3), the total size of all blocks shall be the number of bits equal to the maximum total number of PDSCHs / PUSCHs for multiple cells that can be scheduled, and the size of each block shall be the number of bits equal to the number of PDSCHs / PUSCHs actually scheduled for the cell (operation 1b). Example: When notification of commonly scheduled cells using scheduledCellComboListDCI-0-3(1-3) is not supported, the size of each block is set to the number of bits equal to the maximum number of PDSCH / PUSCHs that can be scheduled for the cell (operation 1a).

[0061] For example, as a specific 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 max_PUSCH It may be N bits. max_PUSCH is the maximum number of PUSCHs that can be scheduled among all entries of the higher layer parameter pusch-TimeDomainAllocationListForMultiPUSCH-r19 if scheduledCellComboListDCI-0-3 is not configured, and is the number of PUSCHs scheduled for the cell if scheduledCellComboListDCI-0-3 is configured.

[0062] Alt. 2: The method for determining the number of NDI and RV blocks may differ depending on whether multi-cell multi-PDSCH / PUSCH scheduling is configured.

[0063] Alt.2-1: When multi-cell-multi-PDSCH / PUSCH scheduling is configured, the number of NDI and RV blocks may be 1, and the block size may be the number of bits equal to the maximum total number of PDSCH / PUSCHs for multiple cells that can be scheduled (equivalent to operation 1b).

[0064] Alt. 2-2: When multi-cell multi-PDSCH / PUSCH scheduling is configured, the method for determining the number of blocks and block size of NDI and RV may differ depending on whether scheduledCellComboListDCI-0-3 (1-3) is configured or not.

[0065] Example: When scheduledCellComboListDCI-0-3 (1-3) is set, the number of blocks for each of NDI and RV is 1, and the block size is the number of bits equal to the maximum number of total PDSCH / PUSCHs for multiple cells that can be scheduled. Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the number of NDI and RV blocks shall be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block shall be the number of bits equal to the maximum number of PDSCH / PUSCHs that can be scheduled for the cell.

[0066] Alt.2-2-1: Example: When scheduledCellComboListDCI-0-3 (1-3) is set, the number of blocks for each of NDI and RV is 1, and the block size is the number of bits equal to the maximum number of total PDSCH / PUSCHs for multiple cells that can be scheduled. Example: If scheduledCellComboListDCI-0-3(1-3) is not set, the number of NDI and RV blocks shall be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block shall be the number of bits for the number of PDSCH / PUSCHs actually scheduled for the cell.

[0067] Alt.2-2-2: Example: When scheduledCellComboListDCI-0-3 (1-3) is set, the number of NDI and RV blocks shall be the maximum total number of PDSCHs / PUSCHs for multiple cells that can be scheduled, and the size of each block shall be the number of bits required for NDI / RV notification for each PDSCH / PUSCH. Example: When scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks for NDI and RV shall be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block shall be the number of bits for the maximum number of PDSCH / PUSCH that can be scheduled for the cell. Alternatively, when scheduledCellComboListDCI-0-3(1-3) is not set, the number of blocks for NDI and RV shall be the number of cells set in scheduledCellListDCI-0-3(1-3), and the size of each block shall be the number of bits for the number of PDSCH / PUSCH that are actually scheduled for the 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 in each block: The number of bits may be specified to be the number of PDSCHs / PUSCHs that can be scheduled for the cell, or the number of PDSCHs / PUSCHs that can be scheduled for all commonly scheduled cells. For NDI or RV signaling in DCI format 0_3 / 1_3, the following options may be applied:

[0069] Option 1) The number of bits in each block of the field is equal to the maximum number of PUSCHs / PDSCHs on the corresponding cell that can be scheduled by DCI format 0_3 / 1_3, which is determined by the TDRA table for that cell.

[0070] Option 2a) The number of bits in the block of the field corresponding to the scheduled cell is equal to the maximum number of PUSCHs / PDSCHs that can be scheduled by DCI format 0_3 / 1_3 among all co-scheduled cells. The number of bits in the block of the field corresponding to a scheduled cell is equal to the actual number of PUSCHs / PDSCHs that are scheduled by DCI format 0_3 / 1_3 in that cell. If the actual number of PUSCHs / PDSCHs that are scheduled by DCI format 0_3 / 1_3 is smaller than the maximum number of PUSCHs / PDSCHs that can be scheduled by DCI format 0_3 / 1_3 among all co-scheduled cells, some reserved bits may be set.

[0071] 4 is a diagram for explaining an example (1) of multi-cell scheduling. As shown in FIG. 4, when the number of PUSCHs / PDSCHs actually scheduled (for example, 3 in FIG. 4) is less than the maximum number of PUSCHs / PDSCHs that can be scheduled (for example, 4 in FIG. 4), the surplus bits may be filled with zeros to fix the field and / or block size. Note that the PXSCH may be replaced with a PUSCH or a PDSCH.

[0072] According to Non-Patent Document 3, for a Type 1A field that is not divided into blocks (e.g., a PDSCH-to-HARQ_feedback timing indicator), the size may be adjusted by inserting zeros into the MSB at the field level. However, the zero insertion method is not specified for a Type 2 NDI or RV field at the block level.

[0073] Fig. 5 is a diagram for explaining an example (2) of multi-cell scheduling. According to Non-Patent Document 3, as shown in Fig. 5, the order of blocks in each field may be in ascending order of serving cell index. Note that the order of PXSCHs in a block is not specified.

[0074] As described above, if the number of PUSCHs / PDSCHs actually scheduled is less than the maximum number of PUSCHs / PDSCHs that can be scheduled, it is necessary to fill the surplus bits with zeros to fix the field and / or block size. It is necessary to specify the order of PXSCHs within a block.

[0075] The following 1) to 4) may be determined taking into consideration the correspondence with the cell index.

[0076] 1) Whether to insert 0s MSB first or LSB first at the field and / or block level.

[0077] 2) Whether the PUSCH / PDSCH in a field and / or block should be arranged 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 order may be determined so that the bit position within the field is fixed. Note that FDRA-based scheduling may also be scheduling when scheduledCellComboListDCI-0-3(1-3) is not set.

[0079] 4) The size determination method for the field may differ depending on whether scheduledCellComboListDCI-0-3 (1-3) is set, and different provisions may apply to the zero padding method, block order, and / or PXSCH order within the block depending on the size determination method.

[0080] If the number of PUSCHs / PDSCHs that are actually scheduled is less than the maximum number of PUSCHs / 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). 0 may be inserted as a size adjustment bit. The adjustment bits may be inserted so that the bit positions are fixed for each field, or so that the bit positions are fixed for each block within the field. The adjustment bits may be inserted from the most significant bit (MSB) or least significant bit (LSB) of the field and / or block. Different operations related to the adjustment bit insertion may be specified depending on whether the notification method of 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 a block of a DCI field corresponding to a scheduled PUSCH / PDSCH may be specified. For example, the order of bits within a field of a block corresponding to each cell may be specified.

[0083] The order may be applied to Type 2 fields (e.g., NDI / RV fields). The order may be the ascending or descending order of PUSCH / PDSCH scheduled in a certain cell. Different operations related to the order may be defined depending on whether the notification method of co-scheduled cells is FDRA-based or scheduled cell indicator-based (i.e., whether scheduledCellComboListDCI-0-3(1-3) is configured or not).

[0084] Hereinafter, scheduling is assumed when four cells are included in the cell set as shown in Fig. 5. The notification mechanism for the scheduled cell assumes the following case 1) or case 2).

[0085] Case 1) FDRA based (scheduledCellComboListDCI-0-3(1-3) is not set).

[0086] Case 2) Based on scheduled cell indicator (when scheduledCellComboListDCI-0-3 (1-3) is set). Also includes cases where the scheduled cells are cell A + cell B + cell C + cell D, when the scheduled cells are cell A + cell B, when the scheduled cell is cell A, etc.

[0087] The entries in the joint TDRA table may be envisioned as follows: for example, 4 P X SCHs may be scheduled in each cell, or up to 16 P X SCHs across all scheduled cells with up to 4 P X SCHs in each cell, or 3 P X SCHs may be scheduled in each cell, or 2 P X SCHs may be scheduled in each cell, or 1 P X SCH may be scheduled in each cell.

[0088] Although the NDI field will be described below as an example, 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 one bit of the NDI field below may be replaced with two bits of the RV field.

[0089] Below, we will explain Case 1) FDRA-based and the case where Option 1) above is applied.

[0090] Operation 1-1) Figure 6 is a diagram illustrating an example (1) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+4+4 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Figure 6. The PXSCHs in the blocks may be arranged in ascending order or in descending order.

[0091] Note that 4+4+4+4PXSCH may mean scheduling 4PXSCH to cell A, 4PXSCH to cell B, 4PXSCH to cell C, and 4PXSCH to cell D, and so on. Also, below, the adjustment bits may be replaceable with zero padding.

[0092] Operation 1-2) Figure 7 is a diagram illustrating an example (2) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 7. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 7, adjustment bits may be inserted within the block from the LSB, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed.

[0093] Fig. 8 is a diagram illustrating an example (3) of a DCI field configuration according to an embodiment of the present invention. When FDRA-based notification for 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Fig. 8. The PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Fig. 8, adjustment bits may be inserted from the MSB in the block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed.

[0094] Note that 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, floating of the bit position does not occur.

[0095] Operation 1-3) Figure 9 is a diagram illustrating an example (4) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+0+0 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Figure 9. The PXSCHs in the blocks may be arranged in ascending order or in descending order.

[0096] Operation 1-4) Figure 10 is a diagram illustrating an example (5) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 10. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 10, a rectification bit may be inserted within a block from the LSB, or the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. A rectification bit may be inserted into a block that is not scheduled.

[0097] Fig. 11 is a diagram illustrating an example (6) of a DCI field configuration according to an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Fig. 11. The PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Fig. 11, the alignment bits may be inserted from the MSB within the block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. The alignment bits may also be inserted into blocks that are not scheduled.

[0098] Operation 1-5) Figure 12 is a diagram illustrating an example (7) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 12. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 12, a rectification bit may be inserted within a block from the LSB, or the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. A rectification bit may be inserted into a block that is not scheduled.

[0099] Fig. 13 is a diagram illustrating an example (8) of a DCI field configuration according to an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Fig. 13. The PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Fig. 13, the alignment bits may be inserted from the MSB within the block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. Alignment bits may also be inserted into blocks that are not scheduled.

[0100] Below, we will explain Case 1) FDRA-based and the case where Option 2a) above is applied.

[0101] Operation 2-1) Figure 14 is a diagram illustrating an example (9) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+4+4 PXSCH is performed on scheduled cells A / B / C / D, the blocks in the field may be arranged in ascending order as shown in Figure 14. The PXSCHs in the blocks may be arranged in ascending order or in descending order.

[0102] Operation 2-2) Figure 15 is a diagram illustrating an example (10) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 15. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 15, a justification bit may be inserted in the field starting from the LSB.

[0103] Figure 16 is a diagram illustrating an example (11) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 16. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 16, a calibration bit may be inserted in the field starting from the MSB.

[0104] Note that although bit position floating occurs within the NDI or RV field, floating of the NDI or RV field position does not occur.

[0105] Operation 2-3) Figure 17 is a diagram illustrating an example (12) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 17. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 17, a justification bit may be inserted in the field starting from the LSB.

[0106] Figure 18 is a diagram illustrating an example (13) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 4+4+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 18. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 18, a justification bit may be inserted in the field starting from the MSB.

[0107] Operation 2-4) Figure 19 is a diagram for explaining an example (14) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 19. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 19, a justification bit may be inserted in the field starting from the LSB.

[0108] Figure 20 is a diagram for explaining an example (15) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 20. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 20, a justification bit may be inserted in the field starting from the MSB.

[0109] Operation 2-5) Figure 21 is a diagram illustrating an example (16) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 21. PXSCH within a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 21, a justification bit may be inserted in the field starting from the LSB.

[0110] Figure 22 is a diagram illustrating an example (17) of a DCI field configuration in an embodiment of the present invention. When FDRA-based notification for 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 22. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 20, a justification bit may be inserted in the field starting from the MSB.

[0111] Case 2) scheduled cell indicator based and the case where the above option 1) is applied will be described below.

[0112] Operation 3-1) Figure 23 is a diagram for explaining an example (18) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 4+4+4+4 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 23. PXSCH in a block may be arranged in ascending order or in 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 on 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 24. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 24, adjustment bits may be inserted in the block from the LSB, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed.

[0114] Figure 25 is a diagram for explaining an example (20) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 25. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 25, adjustment bits may be inserted from the MSB in a block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed.

[0115] Note that bit position floating occurs within the NDI or RV field and across NDI or RV field positions.

[0116] Operation 3-3) Figure 26 is a diagram illustrating an example (21) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 4+4+0+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 26. PXSCH in a block may be arranged in ascending order or in descending order. Also, as shown in Figure 26, bits of other fields may be arranged following the NDI field, and further, adjustment bits may be arranged following the other fields.

[0117] Operation 3-4) Figure 27 is a diagram illustrating an example (22) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+0+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 27. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 27, a rectification bit may be inserted in a block from the LSB, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. Furthermore, as shown in Figure 27, bits of other fields may be arranged following the NDI field, and rectification bits may be arranged following the other fields.

[0118] Figure 28 is a diagram for explaining an example (23) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notification for 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 28. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 28, a rectification bit may be inserted from the MSB within the block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. Furthermore, as shown in Figure 28, bits of other fields may be arranged following the NDI field, and rectification bits may be arranged following the other fields.

[0119] Operation 3-5) Figure 29 is a diagram illustrating an example (24) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+0+3+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 29. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 29, a rectification bit may be inserted in a block from the LSB, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. Furthermore, as shown in Figure 29, bits of other fields may be arranged following the NDI field, and rectification bits may be arranged following the other fields.

[0120] Figure 30 is a diagram for explaining an example (25) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification-based notification for 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 30. PXSCHs in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 30, a rectification bit may be inserted from the MSB in the block, and the same operation may be performed at the block level and the field level, and the association between each bit of NDI or RV and the position of the first PXSCH may be fixed. Furthermore, as shown in Figure 30, bits of other fields may be arranged following the NDI field, and rectification bits may be arranged following the other fields.

[0121] Case 2) scheduled cell indicator based and the case where option 2a) above is applied will be described below.

[0122] Operation 4-1) Figure 31 is a diagram for explaining an example (26) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 4+4+4+4 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 31. PXSCH in a block may be arranged in ascending order or in descending order.

[0123] Operation 4-2) Figure 32 is a diagram for explaining an example (27) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 24. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 32, a justification bit may be inserted in the field from the LSB.

[0124] Figure 33 is a diagram for explaining an example (28) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+3+3 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 33. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 33, adjustment bits may be inserted in the field starting from the MSB.

[0125] Note that bit position floating occurs within the NDI or RV field and across NDI or RV field positions.

[0126] Operation 4-3) Figure 34 is a diagram illustrating an example of a DCI field configuration (29) in an embodiment of the present invention. When scheduled cell notification based on 4+4+0+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 34. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 34, a justification bit may be inserted in the field starting from the LSB.

[0127] Figure 35 is a diagram for explaining an example (30) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 4+4+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 35. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 35, a justification bit may be inserted in the field starting from the MSB.

[0128] Operation 4-4) Figure 36 is a diagram for explaining an example (31) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+0+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 36. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 36, a justification bit may be inserted in the field from the LSB.

[0129] Figure 37 is a diagram for explaining an example (32) of a DCI field configuration in an embodiment of the present invention. When scheduled cell notification based on 3+3+0+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 37. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 37, a justification bit may be inserted in the field starting from the MSB.

[0130] Operation 4-5) Figure 38 is a diagram for explaining an example of a DCI field configuration (33) in an embodiment of the present invention. When scheduled cell notification based on 3+0+3+0 PXSCH is performed on scheduled cell A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 38. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 38, a justification bit may be inserted in the field from the LSB.

[0131] Figure 39 is a diagram for explaining an example of a DCI field configuration (34) in an embodiment of the present invention. When scheduled cell notification based on 3+0+3+0 PXSCH is performed on scheduled cells A / B / C / D, each block in the field may be arranged in ascending order as shown in Figure 39. PXSCH in a block may be arranged in ascending order or in descending order. Furthermore, as shown in Figure 39, a justification bit may be inserted in the field starting from the MSB.

[0132] According to the above-described embodiment, when multi-cell-multi-PDSCH / PUSCH scheduling is performed, the bit positions of specific fields and blocks of the DCI format can be determined and the DCI format can be correctly interpreted.

[0133] That is, multi-carrier scheduling can be appropriately performed in a wireless communication system.

[0134] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0135] <Base station 10> Figure 40 is a diagram showing an example of the functional configuration of base station 10 in the embodiment of the present invention. As shown in Figure 40, 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. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

[0136] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitter 110 also transmits setting information, instructions, notifications, etc. related to a low-power wake-up signal to the terminal 20. The transmitter 110 also transmits notifications related to switching of monitoring operations to the terminal. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0137] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to multi-cell scheduling.

[0138] As described in the embodiments, the control unit 140 controls settings, instructions, and notifications related to multi-cell scheduling, etc. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0139] <Terminal 20> Fig. 41 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 41, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 41 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Transmitting unit 210 and receiving unit 220 may be collectively referred to as a communication unit.

[0140] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The transmitter 210 also transmits capability information related to a low-power wake-up signal to the base station 10. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. The receiver 220 also receives configuration information, instructions, notifications, and the like related to multi-cell scheduling from the base station 10. For example, the receiver 220 receives DCI for scheduling multi-cells from the base station 10. The setting unit 230 stores various types of configuration information received by the receiver 220 from the base station 10. The setting unit 230 also stores pre-configured configuration information. The configuration information includes, for example, information related to multi-cell scheduling.

[0141] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to multi-cell scheduling. The signal transmission-related functional unit in the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functional unit in the control unit 240 may be included in the receiving unit 220.

[0142] (Hardware configuration) The block diagrams (FIGS. 40 and 41) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining the single device or the multiple devices with software.

[0143] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0144] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 42 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above 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 description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0146] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0147] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0148] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 40 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 41 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0149] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

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

[0151] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0152] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, 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 may be configured using different buses between each device.

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

[0155] Fig. 43 shows a configuration example of a vehicle 2001. As shown in Fig. 43, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0156] The drive unit 2002 is configured, for example, by 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 operated by the user.

[0157] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0158] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0159] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0160] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0161] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

[0163] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0164] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, etc. provided in the vehicle 2001.

[0165] <Configuration of this embodiment> (Section 1) a communication unit that receives parameters related to multi-cell multi-channel scheduling and DCI (Downlink Control Information) from a base station; a control unit that determines a bit position constituting a specific field included in the DCI based on the parameter; The communication unit is a terminal that receives or transmits a channel scheduled by the DCI. (Section 2) The terminal according to claim 1, wherein the control unit determines the bit positions that constitute the specific field based on whether a combination list of cells to be scheduled is set by the parameters. (Section 3) The terminal described in paragraph 1, wherein the control unit sets the number of bits of a block in the specific field to a number of bits corresponding to the maximum number of channels in a cell that can be scheduled, or a number of bits corresponding to the maximum number of channels in a cell that is the largest among all cells that can be scheduled. (Section 4) 2. The terminal according to claim 1, wherein the control unit arranges bits corresponding to channels in a block in the particular field in ascending or descending order. (Section 5) The terminal described in 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 a block within the specific field to align the bit width. (Section 6) receiving parameters related to multi-cell multi-channel scheduling and DCI (Downlink Control Information) from a base station; determining, based on the parameters, bit positions constituting a specific field included in the DCI; and a procedure for receiving or transmitting a channel scheduled by the DCI.

[0166] Any of the above configurations makes it possible to appropriately perform multi-carrier scheduling in a wireless communication system. Furthermore, according to claims 2 to 5, when performing multi-cell-multi-PDSCH / PUSCH scheduling, it is possible to determine the bit positions of specific fields and blocks in a DCI format and correctly interpret the DCI format.

[0167] (Supplementary explanation of the embodiment) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0168] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0169] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0170] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0171] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0172] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0173] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0174] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0175] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0176] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0177] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0178] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0179] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0180] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0181] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0182] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," 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. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0184] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0185] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. 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 some other suitable terminology.

[0187] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0189] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0190] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0191] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0192] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

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

[0194] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0195] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0196] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0197] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0199] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0200] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0201] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0204] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0205] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0206] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0207] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0209] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0210] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0211] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

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

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

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

[0215] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0216] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0217] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0218] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0219] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0220] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM 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 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. a communication unit that receives parameters related to multi-cell multi-channel scheduling and DCI (Downlink Control Information) from a base station; a control unit that determines a bit position constituting a specific field included in the DCI based on the parameter; The communication unit is a terminal that receives or transmits a channel scheduled by the DCI.

2. The terminal according to claim 1 , wherein the control unit determines a bit position that configures the specific field based on whether a combination list of cells to be scheduled is set by the parameter.

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

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

5. 2. The terminal according to claim 1, wherein the control unit inserts an adjustment bit from the most significant bit (MSB) or the least significant bit (LSB) into the specific field or a block within the specific field to align the bit width.

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

Images