Terminal and communication method

Abstract

To perform an efficient operation in multi-carrier scheduling.SOLUTION: A terminal has: a receiving section that receives downlink control information including control information related to time domain resource allocation; and a control section that specifies time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels on the basis of the downlink control information. The time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, for each of a plurality of cells. The number of bits of a specific field included in the downlink control information is set to the maximum number of bits of the combination of numbers of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, the maximum number of bits being set in each entry in an index of the joint time domain resource allocation table.SELECTED DRAWING: Figure 10

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 standardizing technologies to achieve even larger system capacity, even faster data transmission speeds, and even lower latency in wireless sections (e.g., Non-Patent Documents 1 and 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 enables scheduling of multiple cells (multi-cells) using one downlink control information (DCI) (e.g., Non-Patent Document 3 and Non-Patent Document 4).

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

[0005] [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]

[0006] As shown in Non-Patent Document 4, which index to use among the indices containing one or more entries of the Joint Time Domain Resource Allocation (TDRA) table used in multi-carrier scheduling is indicated by DCI format 0_3 / 1_3. Also, the entries of the Joint TDRA table are indices of the TDRA table used in scheduling by DCI format 0_1 / 1_1.

[0007] As shown in Non-Patent Document 3, in scheduling using DCI format 0_1 / 1_1 (for example, single-cell multi-PUSCH / PDSCH scheduling), a New Data Indicator (NDI) and a Redundancy Version (RV) are notified using DCI format 0_1 / 1_1. In this case, if the number of scheduled PUSCHs / PDSCHs is not 1, the number of NDI bits and the number of RV bits must be equal to the maximum number of PUSCHs / PDSCHs that can be scheduled among all entries.

[0008] As shown in Non-Patent Document 3, in scheduling using DCI format 0_3 / 1_3 (for example, multi-cell single PUSCH / PDSCH scheduling), NDI and RV are notified using DCI format 0_3 / 1_3. In this case, the number of NDI bits and the number of RV bits required are equal to the number of cells scheduled per transport block (TB) (per cell).

[0009] Here, NDI is a notification bit in the downlink control signal that indicates whether the data signal to which resources have been allocated is the first transmission or a retransmission of a certain codeword (CW). RV is a notification bit in the downlink control signal that indicates the portion of the signal modulated and coded on the transmitting side that has actually been transmitted.

[0010] When the existing specifications are applied to the numbers of NDI bits and RV bits required for DCI in multi-cell multi-PUSCH / PDSCH scheduling, the numbers of NDI bits and RV bits may become larger than the maximum numbers that can actually be set, which makes it difficult to allocate resources efficiently.

[0011] The present invention has been made in view of the above problems, and has as its object to perform efficient operations in multi-carrier scheduling. [Means for solving the problem]

[0012] According to the disclosed technology, there is provided a terminal including: a receiving unit that receives downlink control information including control information regarding time domain resource allocation; and a control unit that identifies time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels based on the downlink control information, wherein the time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each of a plurality of cells, and the number of bits of a specific field included in the downlink control information is set to the maximum number of bits of a combination of the numbers of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, which is set in each entry in an index of the joint time domain resource allocation table. [Effects of the Invention]

[0013] The disclosed technology enables efficient operation in multi-carrier scheduling. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing an example (1) of the configuration of a wireless communication system. [Figure 2] FIG. 2 is a diagram showing an example (2) of the configuration of a wireless communication system. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of higher layer parameters when specifying a joint TDRA table, as specified in 3GPP Release 18. [Figure 4] FIG. 4 is a diagram showing an example of the specifications for a joint TDRA table specified in 3GPP Release 18. [Figure 5] FIG. 5 is a diagram showing an example of the provisions regarding TDRA for multi-PDSCH, which are specified in 3GPP Releases 16 and 17. [Figure 6]FIG. 6 is a diagram illustrating an example of the specifications for DCI format 0_1 ​​specified in 3GPP Release 17. [Figure 7] FIG. 7 is a diagram illustrating an example of the specifications for DCI format 0_3 specified in 3GPP Release 18. [Figure 8] FIG. 8 is a diagram (1) showing an example of the problem to be solved by the present invention. [Figure 9] FIG. 9 is a diagram (2) showing an example of the problem to be solved by the present invention. [Figure 10] FIG. 10 is a diagram showing an example of the number of PUSCHs / PDSCHs and the number of NDI bits of each entry corresponding to the index of the joint TDRA table. [Figure 11] FIG. 11 is a diagram showing an example of the number of NDI bits corresponding to the index of the joint TDRA table. [Figure 12] FIG. 12 is a diagram illustrating an example of a functional configuration of a base station. [Figure 13] FIG. 13 is a diagram illustrating an example of a functional configuration of a terminal. [Figure 14] FIG. 14 is a diagram illustrating an example of the hardware configuration of a base station and a terminal. [Figure 15] FIG. 15 is a diagram illustrating an example of the configuration of a vehicle. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which the present invention is applicable are not limited to the following embodiments.

[0016] In the following description, unless otherwise specified or unless a different meaning is clear from the context, " / " means "and / or."

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

[0018] In the present embodiment described below, terms used in existing LTE, such as synchronization signal (SS), primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH), physical random access channel (PRACH), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), physical uplink control channel (PUCCH), and physical uplink shared channel (PUSCH), are used. This is for convenience of description, and similar signals, functions, and the like may be called by other names. The above-mentioned terms in NR may be referred to as SS, PSS, SSS, PBCH, PRACH, and the like without any particular distinction from those in LTE.

[0019] In this embodiment, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0020] In this embodiment, when radio parameters etc. are "configured," it may mean that a predetermined value is pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0021] FIG. 1 is a diagram (1) showing an example of the configuration of a wireless communication system.

[0022] As shown in Fig. 1, the wireless communication system in this embodiment 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.

[0023] 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, and 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.

[0024] The base station 10 transmits a synchronization signal (SS) and system information (SI) to the terminal 20. The synchronization signal (SS) is, for example, a PSS and an SSS. The system information is transmitted, for example, on a PBCH or a PDSCH, and is also called broadcast information. The synchronization signal (SS) and system information (SI) may be called a synchronization signal block (SSB: SS / PBCH Block).

[0025] The base station 10 transmits a control signal or data to the terminal 20 on a downlink (DL) and receives a control signal or data from the terminal 20 on an uplink (UL).

[0026] Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming, and both the base station 10 and the terminal 20 are capable of applying Multiple Input Multiple Output (MIMO) communication to DL or UL.

[0027] Both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell) and a primary cell (PCell) using carrier aggregation (CA). Furthermore, the terminal 20 may communicate via a PCell of the base station 10 and a primary secondary cell group cell (PSCell) of another base station 10 using dual connectivity (DC).

[0028] 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.

[0029] 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.

[0030] FIG. 2 is a diagram (2) showing an example of the configuration of a wireless communication system.

[0031] The terminal 20 communicates with a base station 10A provided by the NR system and a base station 10B provided by the NR system (hereinafter, when the base station 10A and the base station 10B are not distinguished from each other, they may be referred to as "base station 10").

[0032] The terminal 20 supports NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is a master node (MN) and the base station 10B is a secondary node (SN). The terminal 20 can simultaneously use multiple component carriers (CCs) provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.

[0033] The terminal 20 may communicate with the base station 10A provided by the LTE system and the base station 10B provided by the NR system. The terminal 20 may also support LTE-NR dual connectivity, i.e., EN-DC, in which the base station 10A is the MN and the base station 10B is the SN. Furthermore, the terminal 20 can simultaneously use multiple CCs provided by the base station 10A serving as the master node and the base station 10B serving as the secondary node to perform simultaneous transmission or reception with the base station 10A serving as the master node and the base station 10B serving as the secondary node.

[0034] The terminal 20 may communicate with the base station 10A provided by the NR system and the base station 10B provided by the LTE system. The terminal 20 may also support NR-LTE dual connectivity, i.e., NE (NR-E-UTRA (Evolved Universal Terrestrial Radio Access Network))-DC, in which the base station 10A is the MN and the base station 10B is the SN. Furthermore, the terminal 20 can simultaneously use multiple CCs provided by the base station 10A serving as the master node and the base station 10B serving as the secondary node to perform simultaneous transmission or reception with the base station 10A serving as the master node and the base station 10B serving as the secondary node.

[0035] The terminal 20 may communicate with the base station 10A provided by the NR system and the base station 10B provided by the NR system. The terminal 20 may also support NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is the MN and the base station 10B is the SN. Furthermore, the terminal 20 can simultaneously use multiple CCs provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or simultaneous reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.

[0036] Terminal 20 may perform communication using one serving cell, or may perform communication using multiple serving cells (e.g., CA or DC). The processing operations in this embodiment may be performed in the system configuration shown in Fig. 1, the system configuration shown in Fig. 2, or other system configurations.

[0037] In the following description, "multiple" and "multi" may be used interchangeably. For example, multiple PDSCH / PUSCH and multi-PDSCH / PUSCH may be synonymous. Also, "one", "single", and "single" may be used interchangeably. For example, one PDSCH / PUSCH, a single PDSCH / PUSCH, and a single PDSCH / PUSCH may be synonymous.

[0038] In the following description, only one of the UL operation and the DL operation may be described, but this is not limited to the following description. For example, when a description is given of TDRA for multi-PDSCH, a similar description may also be given of TDRA for multi-PUSCH. For example, when a description is given of DCI format 0_1 / 0_3 used for UL resource allocation, a similar description may also be given of DCI format 1_1 / 1_3 used for DL ​​resource allocation.

[0039] <Agreement details> The agreement on MCE in 3GPP Release 19 is as follows:

[0040] For multi-cell PDSCH / PUSCH scheduling using single DCI, the following support is specified:

[0041] (Agreement 1) Different subcarrier spacing (SCS) / carrier types between simultaneously scheduled cells using a single DCI.

[0042] (Agreement 2) One or more PDSCH / PUSCH per cell scheduled by a single DCI.

[0043] (Agreement 2-1) The maximum number of PDSCH / PUSCH per scheduled cell is 4 or 8.

[0044] (Agreement 2-2) Type 1 HARQ-ACK CB will not be extended for multi-carrier scheduling in 3GPP Release 19.

[0045] (Agreement 2-3) The maximum number of sub-CBs for Type 2 HARQ-ACK CBs will not be increased for multi-carrier scheduling in 3GPP Release 19.

[0046] (Agreement 2-4) It is not assumed that the terminal 20 configures both the multi-PDSCH / PUSCH scheduling for single cell and the multi-PDSCH / PUSCH for multi-cell in the same cell or different cells in the same PUCCH group.

[0047] (Agreement 3) No new DCI formats will be introduced.

[0048] Multi-carrier scheduling, which is supported by MCE in 3GPP Release 18, is scheduled to be extended in 3GPP Release 19 in terms of Agreements 1 and 2. For example, as shown in Agreement 2, in 3GPP Release 18, when scheduling multiple cells with a single DCI (e.g., DCI format 0_3 / 1_3), the number of PUSCHs / PDSCHs per cell was limited to one, but in 3GPP Release 19, it will be possible to schedule multiple PUSCHs / PDSCHs per cell.

[0049] <Existing specifications> FIG. 3 is a diagram showing an example of the configuration of higher layer parameters when specifying a joint TDRA table, as specified in 3GPP Release 18.

[0050] Upper layer parameters configured in DCI format 0_3 (e.g., tdra-FieldIndexListDCI-0-3) including entries of the joint TDRA table (e.g., TDRA-FieldIndexDCI-0-3) and upper layer parameters configured in DCI format 1_3 (e.g., tdra-FieldIndexListDCI-1-3) including entries of the joint TDRA table (e.g., TDRA-FieldIndexDCI-1-3) may be configured as upper layer parameters defining the joint TDRA table in 3GPP Release 18.

[0051] FIG. 4 is a diagram showing an example of the specifications for a joint TDRA table specified in 3GPP Release 18.

[0052] The upper layer parameters (e.g., tdra-FieldIndexListDCI-1-3) including the entries of the joint TDRA table may be a list of 1 to a maximum of 32 joint TDRA table indices. The terminal 20 may be notified of which of these joint TDRA table indices to use by the Type-1B field for TDRA in DCI format 1_3.

[0053] Each index of one joint TDRA table may include from 2 to a maximum of maxNrofBWPsInSetOfCells (e.g., 4 cells x 4 Bandwidth Parts (BWPs) = 16) entries. These entries may be notified to the terminal 20 by higher layer parameters (e.g., TDRA-FieldIndexDCI-1-3). Each entry may correspond to a row index of the TDRA table set in each BWP of each cell or each CC.

[0054] The TDRA table set in each BWP of each cell may be the same as the TDRA table introduced in a release (e.g., Release 15) prior to 3GPP Release 18. The TDRA table may be notified to the terminal 20 by a higher layer parameter (e.g., PDSCH-Time Domain Resource Allocation List). The TDRA table may include K0, a Start and Length Indicator Value (SLIV), and a mapping type.

[0055] Here, K0 is information indicating the offset from the slot in which the PDCCH is received to the slot in which the PDSCH is received, SLIV is information indicating the start symbol S of the PDSCH and its length L, and the mapping type is information indicating the resource allocation method for the PDSCH.

[0056] For example, consider a case where row index 0 of the joint TDRA table includes four entries. Also consider that each of these four entries is 0, and that one BWP (BWP#0) exists in each cell or each CC (CC#0 to CC#3). In this case, since entry #1 included in row index 0 of the joint TDRA table of FIG. 4 is 0, the entry with row index 0 in the TDRA table of BWP#0 of CC#0 may be scheduled. Since entry #2 included in row index 0 of the joint TDRA table of FIG. 4 is also 0, the entry with row index 0 in the TDRA table of BWP#0 of CC#1 may be scheduled. Since entry #3 included in row index 0 of the joint TDRA table of FIG. 4 is also 0, the entry with row index 0 in the TDRA table of BWP#0 of CC#2 may be scheduled. Since entry #4 included in row index 0 of the joint TDRA table of FIG. 4 is also 0, the entry with row index 0 in the TDRA table of BWP#0 of CC#3 may be scheduled. In other words, these four schedulings may be performed simultaneously.

[0057] FIG. 5 is a diagram showing an example of the specifications for TDRA for multi-PDSCH, which are specified in 3GPP Release 16 and Release 17.

[0058] As shown in Fig. 5, higher layer parameters (e.g., MultiPDSCH-TDRA-List) including entries of the TDRA table for multi-PDSCH may be a list of 1 to a maximum of maxNrofDL-AllocationsExt (e.g., 64) entries. These entries may be notified to the terminal 20 by the higher layer parameters (e.g., MultiPDSCH-TDRA). Each entry may include TDRA parameters (e.g., PDSCH-TimeDomainResourceAllocation) for 1 to a maximum of MultiplePDSCHs (e.g., 8) PDSCHs.

[0059] In other words, up to eight PDSCHs can be scheduled from one DCI, and the DCI may indicate which of the up to 64 entries of TDRA parameter combinations (K0, SLIV, mapping type, etc.) for each PDSCH to use.

[0060] FIG. 6 is a diagram illustrating an example of the specifications for DCI format 0_1 ​​specified in 3GPP Release 17.

[0061] In TB1, the size of the NDI field of DCI format 0_1 ​​is 1 bit if the number of schedulable PUSCHs indicated by the TDRA field is 1. Otherwise, the size of the NDI field of DCI format 0_1 ​​is 2 to 8 bits determined based on the maximum number of schedulable PUSCHs among all entries of a higher layer parameter (e.g., pusch-TimeDomainAllocationListForMultiPUSCH).

[0062] In TB1, the size of the RV field of DCI format 0_1 ​​is 2 bits as defined in a predetermined table when the number of schedulable PUSCHs indicated by the TDRA field is 1. Otherwise, the size of the RV field of DCI format 0_1 ​​is 2 to 8 bits determined by the maximum number of schedulable PUSCHs among all entries of a higher layer parameter (e.g., pusch-TimeDomainAllocationListForMultiPUSCH).

[0063] The provisions regarding DCI format 0_1 ​​are the same as those regarding DCI format 1_1.

[0064] FIG. 7 is a diagram illustrating an example of the specifications for DCI format 0_3 specified in 3GPP Release 18.

[0065] As shown in Figure 7(a), the size of the NDI field of DCI format 0_3 is determined by block number 1, block number 2, ..., block number N_cell^UL. Similarly, the size of the RV field of DCI format 0_3 is determined by block number 1, block number 2, ..., block number N_cell^UL.

[0066] Here, as shown in FIG. 7(b), N_cell^UL is the number of scheduled cells indicated by the Scheduled cells indicator field of DCI format 0_3.

[0067] The provisions regarding DCI format 0_3 are the same as those regarding DCI format 1_3.

[0068] <Challenges> Considering the above-described existing specifications, in order to support multi-cell multi-PDSCH / PUSCH scheduling in 3GPP Release 19, NDI bits and RV bits for the number of multi-PUSCHs / PDSCHs for each of the multiple cells are required in DCI format 0_3 / 1_3.

[0069] However, when the existing specifications are applied to the number of bits of the NDI field and the number of bits of the RV field required for DCI in multi-cell multi-PUSCH / PDSCH scheduling, the number of NDI bits and the number of RV bits may become larger than the maximum number that can actually be set, which makes it difficult to allocate resources efficiently.

[0070] FIG. 8 is a diagram (1) showing an example of the problem to be solved by the present invention.

[0071] For example, consider a case where four PUSCHs / PDSCHs can be scheduled simultaneously per cell / CC and two cells / CCs are scheduled simultaneously. In this case, in the existing specifications, the number of NDI bits is set to 4 even if a maximum of four PUSCHs / PDSCHs are not configured simultaneously in each cell / CC.

[0072] A case where "up to four PUSCHs / PDSCHs are not configured simultaneously in each cell / CC" will be described with reference to FIG. 8. For example, consider a case where index 0 of the joint TDRA table is notified to terminal 20 using DCI format 0_3, and entry #1 and entry #2 included in index 0 of the joint TDRA table are 0. In this case, four PUSCHs are configured (and scheduled) simultaneously in CC#0, but two PUSCHs are configured (and scheduled) simultaneously in CC#1. For example, consider a case where index 1 of the joint TDRA table is notified to terminal 20 using DCI format 0_3, and entry #1 and entry #2 included in index 0 of the joint TDRA table are 1. In this case, three PUSCHs are configured (and scheduled) simultaneously in CC#0, and three PUSCHs are also configured (and scheduled) simultaneously in CC#1.

[0073] In FIG. 8, the scheduling target is limited to the PUSCH, but the same applies to the PDSCH.

[0074] FIG. 9 is a diagram (2) showing an example of the problem to be solved by the present invention.

[0075] As in Fig. 8, for example, consider a case where four PUSCHs / PDSCHs can be scheduled simultaneously per cell / CC and two cells / CCs are scheduled simultaneously. In this case, even if a maximum of four PUSCHs / PDSCHs are not configured (and scheduled) simultaneously in each cell / CC, the number of bits in the NDI field is set to 4 bits.

[0076] As shown in Fig. 9, the number of NDI bits corresponding to index 0 of the joint TDRA table is set to 4 bits for each entry. Therefore, the number of bits in the NDI field corresponding to index 0 of the joint TDRA table must be set to 8 bits. Although not shown in the figure, the number of bits in the NDI field corresponding to an index other than 0 in the joint TDRA table also must be set to 8 bits.

[0077] <Example> Examples of this embodiment will be described below.

[0078] In the case of scheduling multiple PUSCHs / PDSCHs to multiple cells (multi-cell multi-PUSCH / PDSCH scheduling), the number of NDI bits / RV bits may be the maximum number of bits for the combination of the number of PUSCHs / PDSCHs that can actually be set (or set) in each entry.

[0079] <Example 1> The total number of bits in the NDI field (NDI total bit number) may be fixed. The number of bits in the row index with the largest total number of PUSCHs / PDSCHs among the row indexes of the joint TDRA table may be set as the total number of bits in the NDI field.

[0080] According to the configuration of Example 1, it is possible to maintain the consistency of the DCI format. Furthermore, by setting the number of bits in the NDI field based on the maximum number of PUSCHs / PDSCHs, it is possible to support all scheduling scenarios.

[0081] <Example 2> The total number of bits in the NDI field (NDI total bit number) may be variable, and may be set based on the total number of PUSCHs / PDSCHs in each row index of the joint TDRA table.

[0082] FIG. 10 is a diagram showing an example of the number of PUSCHs / PDSCHs and the number of NDI bits of each entry corresponding to the index of the joint TDRA table.

[0083] Explaining this using the example of FIG. 8 above, consider a case where, for example, index 0 of the joint TDRA table is notified to terminal 20 in DCI format 0_3, and entry #1 and entry #2 included in index 0 of the joint TDRA table are 0. In this case, four PUSCHs are configured simultaneously in CC #0, so the number of PUSCHs / number of PDSCHs in entry #1 is 4. Also, two PUSCHs are configured simultaneously in CC #1, so the number of PUSCHs / number of PDSCHs in entry #2 is 2. In other words, as shown in FIG. 10, the total number of bits in the NDI field may be set based on the sum of the number of PUSCHs / number of PDSCHs in entry #1 and the number of PUSCHs / number of PDSCHs in entry #2.

[0084] FIG. 11 is a diagram showing an example of the number of NDI bits corresponding to the index of the joint TDRA table.

[0085] By setting the total number of bits in the NDI field based on the total number of PUSCHs / PDSCHs for each row index of the joint TDRA table, the total number of bits in the NDI field is always 8 bits in the example of Figure 9, but in the example of Figure 11, the total number of bits in the NDI field is only 6 bits.

[0086] According to the configuration of the second specific example, the number of bits in the NDI field can be minimized, enabling efficient use of wireless resources.

[0087] <Example 3> The order (sequence) of bits in the NDI field may be either ascending order or descending order with respect to the index of each PUSCH / each PDSCH in each entry.

[0088] For example, consider a case where two cells / CCs are scheduled simultaneously, and three PUSCHs (#0 to #2) are scheduled in CC#0, and two PUSCHs (#0 to #1) are scheduled in CC#1. In this case, the bit order of the NDI field in ascending order may be "[CC#0 PUSCH#0], [CC#0 PUSCH#1], [CC#0 PUSCH#2], [CC#1 PUSCH#0], and [CC#1 PUSCH#1]."

[0089] For example, consider a case where two cells / CCs are scheduled simultaneously, and three PUSCHs (#0 to #2) are scheduled in CC#0 and two PUSCHs (#0 to #1) are scheduled in CC#1. In this case, the bit order of the NDI field in descending order may be "[CC#1 PUSCH#1][CC#1 PUSCH#0][CC#0 PUSCH#2][CC#0 PUSCH#1][CC#0 PUSCH#0]".

[0090] According to the configuration of the specific example 3, the order in the NDI field is defined, which simplifies the implementation and decoding process of the terminal.

[0091] <Example 4> The allocation of bit positions corresponding to each entry in the NDI field may be variable. Entries and bit positions may be associated based on a TDRA table referenced in the joint TDRA table. Indicators and new parameters that associate entries and bit positions may also be defined. Alternatively, bits for indicating entry boundaries may be included in the NDI field.

[0092] According to the configuration of Specific Example 4, for example, by utilizing an existing TDRA table, the introduction of new parameters can be suppressed. According to the configuration of Specific Example 4, for example, by introducing new parameters, more flexible bit position allocation becomes possible. According to the configuration of Specific Example 4, for example, by explicitly indicating entry boundaries, it is possible to prevent misinterpretation by the terminal.

[0093] Specific examples 1 to 4 may be used in combination. For example, by combining specific example 1 and specific example 4, the total number of bits in the NDI field is fixed, while the bit positions corresponding to each entry in the NDI field are flexibly assigned. For example, by combining specific example 2 and specific example 3, both efficient use of the NDI field bits and simplification of the implementation / processing of the terminal can be achieved.

[0094] In specific examples 1 to 4, the number of bits in the NDI field is taken as an example, but the number of bits in the RV field can be considered in the same way.

[0095] As described above, the configuration of the embodiment enables efficient resource allocation, and enables efficient operation in multi-carrier scheduling.

[0096] <Device configuration> An example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. 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.

[0097] ≪Base station≫ FIG. 12 is a diagram illustrating an example of the functional configuration of a base station in this embodiment.

[0098] The base station 10 includes a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 12 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 according to this embodiment.

[0099] The transmitter 110 includes 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 includes 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.

[0100] 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 measurements of low-power signals.

[0101] As described in the embodiments, the control unit 140 controls settings, instructions, and notifications related to the TDRA, the TDRA table, and the joint TDRA. The signal transmission-related functional unit in the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functional unit in the control unit 140 may be included in the receiving unit 120.

[0102] Terminal FIG. 13 is a diagram illustrating an example of a functional configuration of a terminal.

[0103] The terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 13 is merely an example. As long as the operation according to this embodiment can be performed, the names of the functional divisions and functional units may be any. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0104] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 transmits the TDRA, TDRA table, and capability information related to the joint TDRA to the base station 10. The transmitter 210 transmits the PUSCH and the like based on the radio resources specified by the control unit 240. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 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 receives configuration information, instructions, and notifications related to the TDRA, TDRA table, and joint TDRA from the base station 10. The receiver 220 receives the PDSCH and the like based on the radio resources specified by the control unit 240. The setting unit 230 stores various configuration information received from the base station 10 by the receiver 220. The setting unit 230 also stores various configuration information that is set in advance.

[0105] As described in the embodiments, the control unit 240 controls the settings, instructions, and notifications related to the TDRA, the TDRA table, and the joint TDRA. The control unit 240 identifies radio resources based on setting information related to the TDRA table. The signal transmission-related functional unit of the control unit 240 may be included in the transmitting unit 210, and the signal reception-related functional unit of the control unit 240 may be included in the receiving unit 220.

[0106] <Hardware configuration> The block diagrams (FIGS. 12 and 13) used in the description of 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 of 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.

[0107] 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, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs a transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0108] FIG. 14 is a diagram illustrating an example of the hardware configuration of a base station and a terminal.

[0109] For example, the base station 10, the terminal 20, etc. in this embodiment may function as a computer that performs processing of the wireless communication method of this embodiment. 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.

[0110] 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.

[0111] 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.

[0112] The processor 1001 controls the entire computer by running, for example, an operating system (OS). 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.

[0113] 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. 12 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 13 may be implemented by a control program stored in the storage device 1002 and running on 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.

[0114] 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.

[0115] 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.

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

[0117] 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 (Light-Emitting Diode) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0118] 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.

[0119] 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.

[0120] Vehicles FIG. 15 is a diagram illustrating an example of the configuration of a vehicle.

[0121] 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 vehicle 2001, and may be applied to communication module 2013, for example.

[0122] 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.

[0123] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O (Input / Output) 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).

[0124] 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.

[0125] 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.

[0126] The driving assistance system unit 2030 is configured with various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS (Global Navigation Satellite System)), map information (e.g., HD (High Definition) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0127] 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.

[0128] 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.

[0129] 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.

[0130] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle 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.

[0131] For example, aspects of the present invention are as follows.

[0132] <1> a receiving unit for receiving downlink control information including control information regarding time domain resource allocation; a control unit that specifies time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels based on the downlink control information, the time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each of a plurality of cells; a terminal, wherein the number of bits of a specific field included in the downlink control information is set to the maximum number of bits of a combination of the number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, which is set in each entry in an index of the joint time domain resource allocation table. <2> a total number of bits of the specific field corresponding to an index of the joint time domain resource allocation table is set based on an index of the joint time domain resource allocation table that has the largest total number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels; <1> A terminal described in. <3> a total number of bits of the specific field corresponding to an index of the joint time domain resource allocation table is set based on a total number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each index of the joint time domain resource allocation table. <1> or <2> A terminal described in. <4> an order of bits in the specific field corresponding to an index of the joint time domain resource allocation table is set to an ascending order or a descending order with respect to an index of each physical uplink shared channel and each physical downlink shared channel in each entry in the index of the joint time domain resource allocation table; <1> from <3> A terminal described in any one of the above. <5> In the specific field, bit position assignment corresponding to each entry in the index of the joint time domain resource allocation table is set based on a time domain resource allocation table referenced in the joint time domain resource allocation table. <1> from <4> A terminal described in any one of the above. <6> receiving downlink control information including control information regarding time domain resource allocation; determining time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels based on the downlink control information; the time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each of a plurality of cells; a number of bits of a specific field included in the downlink control information is set to a maximum number of bits of a combination of the number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, which is set in each entry in an index of the joint time domain resource allocation table.

[0133] Any of the above configurations allows the terminal to perform efficient operations in multi-carrier scheduling.

[0134] <Supplementary information on the embodiment> Although the present embodiment has been described above, the disclosed invention is not limited to such an embodiment, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters 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 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment 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.

[0135] 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., DCI, UCI (Uplink Control Information)), higher layer signaling (e.g., RRC signaling, MAC signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Information notified by higher layer signaling may be referred to as configuration information. Information notified by physical layer signaling may be referred to as control information. Furthermore, 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.

[0136] 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, W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable 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) may also be applied.

[0137] 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.

[0138] 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 (Mobility Management Entity) or an S-GW (Serving Gateway)). 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 (for example, an MME and an S-GW).

[0139] 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.

[0140] 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.

[0141] 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).

[0142] 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.

[0143] 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.

[0144] 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.

[0145] 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). A signal may also be a message. A CC may also be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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 that coverage.

[0151] 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.

[0152] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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 at least one of one or more wires, cables, and 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.

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

[0160] 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."

[0161] 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.

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

[0163] 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.

[0164] 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.

[0165] Numerology may be communication parameters applied 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.

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

[0167] 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.

[0168] 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.

[0169] 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 millisecond (ms)) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0170] 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.

[0171] 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.

[0172] 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.

[0173] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Releases 8 to 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 TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot, etc.

[0174] 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.

[0175] 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.

[0176] 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.

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

[0178] 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.

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

[0180] 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.

[0181] 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."

[0182] 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.

[0183] 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.

[0184] 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."

[0185] 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).

[0186] 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]

[0187] 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 (I / O port)

Claims

1. a receiving unit for receiving downlink control information including control information regarding time domain resource allocation; a control unit that specifies time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels based on the downlink control information, the time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each of a plurality of cells; a terminal, wherein the number of bits of a specific field included in the downlink control information is set to the maximum number of bits of a combination of the number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, which is set in each entry in an index of the joint time domain resource allocation table.

2. 2. The terminal according to claim 1, wherein a total number of bits of the specific field corresponding to an index of the joint time domain resource allocation table is set based on an index of the joint time domain resource allocation table that has a largest total number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels.

3. 2. The terminal according to claim 1, wherein a total number of bits of the specific field corresponding to an index of the joint time domain resource allocation table is set based on a total number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each index of the joint time domain resource allocation table.

4. 2. The terminal of claim 1, wherein an order of bits in the specific field corresponding to an index of the joint time domain resource allocation table is set to ascending order or descending order with respect to an index of each physical uplink shared channel and each physical downlink shared channel in each entry in the index of the joint time domain resource allocation table.

5. 2. The terminal according to claim 1, wherein in the particular field, assignment of bit positions corresponding to each entry in an index of the joint time domain resource allocation table is set based on a time domain resource allocation table referenced in the joint time domain resource allocation table.

6. receiving downlink control information including control information regarding time domain resource allocation; determining time domain resources of at least one of a plurality of physical uplink shared channels and a plurality of physical downlink shared channels based on the downlink control information; the time domain resource allocation is a joint time domain resource allocation table for scheduling at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels for each of a plurality of cells; a number of bits of a specific field included in the downlink control information is set to a maximum number of bits of a combination of the number of at least one of the plurality of physical uplink shared channels and the plurality of physical downlink shared channels, which is set in each entry in an index of the joint time domain resource allocation table.

Images