Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives downlink control information which includes control information relating to time domain resource allocation; and a control unit that specifies, on the basis of the downlink control information, a time domain resource of a plurality of physical uplink shared channels and / or a plurality of physical downlink shared channels. The time domain resource allocation refers to a joint time domain resource allocation table for scheduling, for each of a plurality of cells, the plurality of physical uplink shared channels and / or the plurality of physical downlink shared channels. The bit count of a specific field included in the downlink control information is set in each of the entries in an index of the joint time domain resource allocation table, and is set to a maximum bit count in a combination of the number of the plurality of physical uplink shared channels and / or the plurality of physical downlink shared channels.

Description

Terminal and Communication Method

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

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), standardization of technologies for further increasing system capacity, further increasing data transmission speed, and further reducing latency in the radio section is being carried out (for example, Non-Patent Document 1 and Non-Patent Document 2).

[0003] Among these technologies, as multi-carrier enhancements (MCE: Multi-Carrier Enhancements), in 3GPP Release 18, multi-carrier scheduling (which may also be called multi-cell scheduling) was defined to reduce the signaling overhead. Multi-carrier scheduling enables scheduling of multiple cells (multi-cells) with one downlink control information (DCI: Downlink Control Information) (for example, Non-Patent Document 3 and Non-Patent Document 4).

[0004] In 3GPP Release 18, the physical uplink control channel (PUCCH: Physical Uplink Control Channel) / physical downlink shared channel (PDSCH: Physical Downlink Shared Channel) in each cell scheduled by multi-carrier scheduling was limited to one (which may also be called multi-cell single PUSCH / PDSCH scheduling or multi-PUSCH / PDSCH scheduling). However, in 3GPP Release 19, multi-carrier scheduling has become capable of scheduling multiple PUSCH / PDSCHs in each cell (which may also be called multi-cell multi-PUSCH / PDSCH scheduling).

[0005] 3GPP TS 38.300 V18.2.0 (2024-06) 3GPP TS 38.401 V18.2.0 (2024-06) 3GPP TS 38.212 V18.2.0 (2024-06) 3GPP TS 38.331 V18.2.0 (2024-06)

[0006] As shown in Non-Patent Document 4, DCI format 0_3 / 1_3 notifies which index to use among the indexes containing one or more entries in the Joint Time Domain Resource Allocation (Joint TDRA) table used in multi-carrier scheduling. Furthermore, the entries in the Joint TDRA table are the indexes in the TDRA table used when 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), the NDI (New Data Indicator) and RV (Redundancy Version) are notified using DCI format 0_1 / 1_1. In this case, the number of NDI bits and RV bits is required to be the maximum number of PUSCH / PDSCHs that can be scheduled among all entries, unless the scheduled number of PUSCHs / PDSCHs is 1.

[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 RV bits is required for each transport block (TB) (each cell) for the number of cells scheduled.

[0009] Here, NDI is a notification bit in the downlink control signal that indicates whether the data signal to which the resource has been allocated is the first transmission or a retransmission of a particular codeword (CW). RV is a notification bit in the downlink control signal that indicates the portion of the signal modulated and encoded by the transmitter that was actually transmitted.

[0010] When applying existing specifications to the number of NDI bits and RV bits required for DCI in multi-cell multi-PUCH / PDSCH scheduling, there is a risk that the number of NDI bits and RV bits will exceed the maximum number that can actually be set. This makes efficient resource allocation difficult.

[0011] This invention has been made in view of the above-mentioned problems, and aims to enable efficient operation in multi-carrier scheduling.

[0012] According to the disclosed technology, a terminal is provided having a receiving unit that receives downlink control information including control information relating to time-domain resource allocation, and a control unit that identifies a time-domain resource from at least one of a plurality of physical uplink sharing channels and a plurality of physical downlink sharing 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 sharing channels and a plurality of physical downlink sharing 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 for a number of combinations of at least one of the plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels set in each entry in the index of the joint time-domain resource allocation table.

[0013] According to the disclosed technology, efficient operation can be achieved in multi-carrier scheduling.

[0014] Figure 1 shows an example of the configuration of a wireless communication system (1). Figure 2 shows an example of the configuration of a wireless communication system (2). Figure 3 shows an example of the configuration of upper-layer parameters when a joint TDRA table is specified as defined in 3GPP Release 18. Figure 4 shows an example of the specification regarding a joint TDRA table as defined in 3GPP Release 18. Figure 5 shows an example of the specification regarding TDRA for multi-PDSCH as defined in 3GPP Release 16 and 17. Figure 6 shows an example of the specification regarding DCI format 0_1 ​​as defined in 3GPP Release 17. Figure 7 shows an example of the specification regarding DCI format 0_3 as defined in 3GPP Release 18. Figure 8 is a diagram (1) showing an example of a problem that the present invention aims to solve. Figure 9 is a diagram (2) showing an example of a problem that the present invention aims to solve. Figure 10 is a diagram showing an example of the number of PUSCHs / PDSCHs and the number of NDI bits for each entry corresponding to the index of the joint TDRA table. Figure 11 is a diagram showing an example of the number of NDI bits corresponding to the index of the joint TDRA table. Figure 12 is a diagram showing an example of the functional configuration of a base station. Figure 13 is a diagram showing an example of the functional configuration of a terminal. Figure 14 is a diagram showing an example of the hardware configuration of a base station and a terminal. Figure 15 is a diagram showing an example of the configuration of a vehicle.

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

[0016] In the following explanation, " / " means "and / or" unless otherwise specified, or unless the context makes it clear that it has a different meaning.

[0017] In the operation of the wireless communication system of this embodiment, existing technologies will be used as appropriate. However, such existing technologies include, for example, existing LTE (Long Term Evolution), but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (for example, NR (New Radio)), unless otherwise specified.

[0018] In the embodiments described below, terms such as Synchronization Signal (SS), Primary SS (PSS), Secondary SS (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), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. The above terms in NR may also be called SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE.

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

[0020] In this embodiment, "configuring" wireless parameters means either pre-configuring predetermined values, or configuring wireless parameters notified by a base station or terminal.

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

[0022] The wireless communication system in this embodiment includes a base station 10 and a terminal 20, as shown in Figure 1. Although Figure 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple base stations 10 and terminal 20.

[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 the 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 resource blocks.

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

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

[0026] Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, 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 secondary cells (SCell) and primary cells (PCell) using carrier aggregation (CA). Furthermore, the terminal 20 may communicate via the PCell of base station 10 and the primary secondary cell group cell (PSCell) of other base stations 10 using dual connectivity (DC).

[0028] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module.

[0029] Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of said reference signals.

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

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

[0032] Terminal 20 supports NR-NR dual connectivity, or NR-DC, with base station 10A as the master node (MN) and base station 10B as the secondary node (SN). Furthermore, terminal 20 can simultaneously transmit or receive data with base station 10A and base station 10B by simultaneously utilizing multiple component carriers (CCs) provided by base station 10A (master node) and base station 10B (secondary node).

[0033] Terminal 20 may communicate with base station 10A provided by the LTE system and base station 10B provided by the NR system. Terminal 20 may also support LTE-NR dual connectivity, i.e., EN-DC, where base station 10A is the MN and base station 10B is the SN. Furthermore, terminal 20 can simultaneously transmit or receive with base station 10A, the master node, and base station 10B, the secondary node, by simultaneously utilizing multiple CCs provided by base station 10A, the master node, and base station 10B, the secondary node.

[0034] Terminal 20 may communicate with base station 10A provided by the NR system and base station 10B provided by the LTE system. Terminal 20 may also support NR-LTE dual connectivity, i.e., NE (NR-E-UTRA (Evolved Universal Terrestrial Radio Access Network))-DC, where base station 10A is the MN and base station 10B is the SN. Furthermore, terminal 20 can simultaneously transmit or receive with base station 10A, the master node, and base station 10B, the secondary node, by simultaneously utilizing multiple CCs provided by base station 10A, the master node, and base station 10B, the secondary node.

[0035] Terminal 20 may communicate with base station 10A and base station 10B provided by the NR system. Terminal 20 may also support NR-NR dual connectivity, i.e., NR-DC, where base station 10A is the MN and base station 10B is the SN. Furthermore, terminal 20 can simultaneously transmit or receive with base station 10A, the master node, and base station 10B, the secondary node, by simultaneously utilizing multiple CCs provided by base station 10A, the master node, and base station 10B, the secondary node.

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

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

[0038] In the following explanations, only one of the operations related to UL or DL ​​may be described, but the explanations are not limited to those below. For example, if a TDRA for multi-PDSCH is described, a similar explanation may be given for a TDRA for multi-PUSCH. For example, if a DCI format 0_1 / 0_3 used for UL resource allocation is described, a similar explanation may be given for DCI format 1_1 / 1_3 used for DL ​​resource allocation.

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

[0040] Define the following support for multi-cell PDSCH / PUSCH scheduling using single DCI.

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

[0042] (Agreement 2) One or more PDSCH / PUSCH for each cell scheduled by 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 is not extended for multi-carrier scheduling in 3GPP Release 19.

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

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

[0047] (Agreement 3) Do not introduce a new DCI format. 3]

[0048] For multi-carrier scheduling supported by MCE in 3GPP Release 18, in 3GPP Release 19, it is planned to be extended in terms of Agreement 1 and Agreement 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 PUSCH / PDSCH per cell was limited to 1, but in 3GPP Release 19, it is possible to schedule multiple PUSCH / PDSCH per cell.

[0049] <Existing Specifications> Figure 3 shows an example of the configuration of upper-layer parameters when defining a joint TDRA table, as defined in 3GPP Release 18.

[0050] The upper layer parameters that define the joint TDRA table in 3GPP Release 18 may be configured as follows: an upper layer parameter set in DCI format 0_3 (e.g., tdra-FieldIndexListDCI-0-3) that includes an entry in the joint TDRA table (e.g., TDRA-FieldIndexDCI-0-3), and an upper layer parameter set in DCI format 1_3 (e.g., tdra-FieldIndexListDCI-1-3) that includes an entry in the joint TDRA table (e.g., TDRA-FieldIndexDCI-1-3).

[0051] Figure 4 shows an example of the provisions regarding joint TDRA tables as defined in 3GPP Release 18.

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

[0053] Each index in a joint TDRA table may contain between two and a maximum of maxNrofBWPsInSetOfCells (e.g., 4 cells × 4 bandwidth parts (BWP) = 16) entries. These entries may be notified to terminal 20 by a higher-layer parameter (e.g., TDRA-FieldIndexDCI-1-3). Each entry may correspond to a row index in the TDRA table set for each cell or each BWP in each CC.

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

[0055] Here, K0 is information indicating the offset from the slot where PDCCH is received to the slot where PDSCH is received. SLIV is information indicating the start symbol S of PDSCH and its length L. Mapping type is information indicating how PDSCH resources are allocated.

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

[0057] Figure 5 shows an example of the TDRA for multi-PDSCH as defined in 3GPP Release 16 and Release 17.

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

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

[0060] Figure 6 shows an example of the specification for DCI format 0_1 ​​as defined in 3GPP Release 17.

[0061] In TB1, the size of the NDI field in 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 in DCI format 0_1 ​​is 2 to 8 bits, determined based on the maximum number of schedulable PUSCHs among all entries in the higher-layer parameter (e.g., push-TimeDomainAllocationListForMultiPUSCH).

[0062] In TB1, the size of the RV field of DCI format 0_1 ​​is 2 bits, as defined in a given 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 in the higher-layer parameter (e.g., push-TimeDomainAllocationListForMultiPUSCH).

[0063] Furthermore, the provisions concerning DCI format 0_1 ​​also apply to the provisions concerning DCI format 1_1.

[0064] Figure 7 shows an example of the provisions regarding DCI format 0_3 as defined in 3GPP Release 18.

[0065] As shown in Figure 7(a), the size of the NDI field in 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 in DCI format 0_3 is also determined by block number 1, block number 2, ... block number N_cell^UL.

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

[0067] Furthermore, the provisions concerning DCI format 0_3 also apply to the provisions concerning DCI format 1_3.

[0068] <Challenges> Based on the existing specifications mentioned above, in order to support multi-cell multi-PDSCH / PUSCH scheduling in 3GPP Release 19, the DCI format 0_3 / 1_3 requires NDI bits and RV bits for each multi-cell multi-PUSCH / PDSCH.

[0069] However, when applying existing specifications to the number of bits in the NDI field and RV field required for DCI in multi-cell multi-PUSCH / PDSCH scheduling, the number of bits in the NDI field and RV field may exceed the maximum number that can actually be set. This makes efficient resource allocation difficult.

[0070] Figure 8 is a diagram (1) illustrating an example of a problem that the present invention aims to solve.

[0071] For example, consider a case where there are four PUSCH / PDSCH commands that can be scheduled simultaneously per cell / CC, and two cells / CCs are scheduled simultaneously. In this case, according to the existing specifications, the NDI bit count is set to 4 bits even if the maximum of four PUSCH / PDSCH commands are not set simultaneously in each cell / CC.

[0072] The case where "a maximum of four PUSCH / PDSCH are not set simultaneously in each cell / CC" will be explained using Figure 8. For example, consider the case where, in DCI format 0_3, index 0 of the joint TDRA table is notified to terminal 20, and entry #1 in index 0 of the joint TDRA table is 0 and entry #2 is 0. In this case, four PUSCHs are set (and scheduled) simultaneously in CC#0, but two PUSCHs are set (and scheduled) simultaneously in CC#1. For example, consider the case where, in DCI format 0_3, index 1 of the joint TDRA table is notified to terminal 20, and entry #1 in index 0 of the joint TDRA table is 1 and entry #2 is 1. In this case, three PUSCHs are set (and scheduled) simultaneously in CC#0, and three PUSCHs are also set (and scheduled) simultaneously in CC#1.

[0073] Note that while Figure 8 limits the scheduling target to PUSCH, the same applies to PDSCH.

[0074] Figure 9 is a diagram (2) illustrating an example of a problem that the present invention aims to solve.

[0075] Similar to Figure 8, consider the case where, for example, there are four PUSCH / PDSCH commands that can be scheduled simultaneously per cell / CC, and two cells / CCs are scheduled simultaneously. In this case, even if a maximum of four PUSCH / PDSCH commands are not set (and scheduled) simultaneously in each cell / CC, the number of bits in the NDI field is set to four.

[0076] As shown in Figure 9, the number of NDI bits corresponding to index 0 in the joint TDRA table is set to 4 bits per entry. Therefore, the number of bits in the NDI field corresponding to index 0 in 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 indexes other than index 0 in the joint TDRA table must also be set to 8 bits.

[0077] <Examples> Examples of this embodiment are described below.

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

[0079] <Specific Example 1> The total number of bits in the NDI field (NDI total bits) may be fixed. The number of bits in the row index with the highest total PUSCH count / PDSCH count 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 in Specific Example 1, consistency of the DCI format can be maintained. Furthermore, by setting the number of bits in the NDI field based on the maximum number of PUSCHs / PDSCHs, it can accommodate any scheduling scenario.

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

[0082] Figure 10 shows an example of the number of PUSCHs / PDSCHs and the number of NDI bits for each entry corresponding to the index in the joint TDRA table.

[0083] To illustrate with the example in Figure 8, consider the case where, for example, in DCI format 0_3, index 0 of the joint TDRA table is notified to terminal 20, and entry #1 and entry #2 included in index 0 of the joint TDRA table are both 0. In this case, four PUSCHs are set simultaneously in CC#0, so the PUSCH count / PDSCH count for entry #1 becomes 4. Also, two PUSCHs are set simultaneously in CC#1, so the PUSCH count / PDSCH count for entry #2 becomes 2. In other words, as shown in Figure 10, the total number of bits in the NDI field may be set based on the sum of the PUSCH count / PDSCH count for entry #1 and the PUSCH count / PDSCH count for entry #2.

[0084] Figure 11 shows an example of the number of NDI bits corresponding to an index in a joint TDRA table.

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

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

[0087] <Specific Example 3> The order of the bits in the NDI field may be in ascending or descending order relative to the index of each PUSCH / PDSCH within each entry.

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

[0089] For example, consider a case where two cells / CCs are scheduled simultaneously, with three PUSCHs (#0 to #2) scheduled in CC#0 and two PUSCHs (#0 to #1) scheduled in CC#1. In this case, the order of the bits in the descending NDI field 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 in specific example 3, defining the order within the NDI field simplifies the implementation and decoding process of the terminal.

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

[0092] According to the configuration of Specific Example 4, for example, the introduction of new parameters can be minimized by utilizing the existing TDRA table. According to the configuration of Specific Example 4, for example, the introduction of new parameters can enable more flexible bit position allocation. According to the configuration of Specific Example 4, for example, terminal misinterpretation can be prevented by explicitly indicating the boundaries of entries.

[0093] Examples 1 through 4 may be used in combination. For example, by combining Example 1 and Example 4, the total number of bits in the NDI field can be fixed while flexibly assigning bit positions corresponding to each entry within the NDI field. For example, by combining Example 2 and Example 3, efficient use of NDI field bits and simplification of terminal implementation / processing can be achieved simultaneously.

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

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

[0096] <Device Configuration> An example of the functional configuration of the base station 10 and terminal 20 that perform the processing and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0097] ≪Base Station≫ Figure 12 shows 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 Figure 12 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to this embodiment.

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

[0100] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to measurements in low-power signals.

[0101] As described in the embodiment, the control unit 140 performs control related to the setting, instruction, and notification of TDRA, TDRA table, and joint TDRA. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0102] <Terminal> Figure 13 shows an example of the functional configuration of a terminal.

[0103] The terminal 20 includes a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 13 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0104] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 transmits capability information related to TDRA, TDRA table, and joint TDRA to the base station 10. The transmitting unit 210 transmits PUSCH, etc., based on the wireless resources identified by the control unit 240. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc., transmitted from the base station 10. The receiving unit 220 receives setting information, instructions, and notifications related to TDRA, TDRA table, and joint TDRA from the base station 10. The receiving unit 220 receives PDSCH, etc., based on the wireless resources identified by the control unit 240. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores various pre-configured setting information.

[0105] As described in the embodiment, the control unit 240 performs control related to the setting, instruction, and notification of TDRA, TDRA table, and joint TDRA. Based on the setting information related to the TDRA table, the control unit 240 identifies the wireless resource. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0106] <Hardware Configuration> The block diagrams (Figures 12 and 13) used in the description of the above embodiment show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0107] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0108] Figure 14 shows an example of the hardware configuration of a base station and a terminal.

[0109] For example, the base station 10, terminal 20, etc. in this embodiment may function as a computer that processes the wireless communication method of this embodiment. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, storage device 1002, auxiliary storage device 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0110] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0111] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0112] The processor 1001 controls the entire computer, for example, by running an operating system (OS). The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0113] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 12 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 13 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0114] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0115] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[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 a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of FDD and TDD. For example, the transmitting / receiving antenna, amplifier section, transmitting / receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting / receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0117] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED (Light-Emitting Diode) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., 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 different buses may be configured for each device.

[0119] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0120] ≪Vehicle≫ Figure 15 shows an example of the vehicle's configuration.

[0121] 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 this disclosure may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0122] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0123] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (I / O (Input / Output) ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0124] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

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

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

[0127] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[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 external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

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

[0130] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0131] For example, embodiments of the present invention are as follows:

[0132] <1> A terminal comprising: a receiving unit that receives downlink control information including control information relating to time domain resource allocation; and a control unit that identifies at least one of a plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels as a time domain resource 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 sharing channels and a plurality of physical downlink sharing 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 for combinations of at least one of the plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels set in each entry in the index of the joint time domain resource allocation table. <2> The terminal according to <1>, wherein the total number of bits of the specific field corresponding to the index of the joint time domain resource allocation table is set based on the 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 sharing channels and a plurality of physical downlink sharing channels. <3> The terminal according to <1> or <2>, wherein the total number of bits in the specific field corresponding to the index of the joint time-domain resource allocation table is set based on the total number of at least one of the multiple physical uplink sharing channels and the multiple physical downlink sharing channels in each index of the joint time-domain resource allocation table. <4> The terminal according to any one of <1> to <3>, wherein the order of bits in the specific field corresponding to the index of the joint time-domain resource allocation table is set in ascending or descending order with respect to the index of each physical uplink sharing channel and each physical downlink sharing channel in each entry of the index of the joint time-domain resource allocation table.<5> A terminal according to any one of <1> to <4>, wherein in the specific field, the assignment of the bit positions corresponding to each entry in the index of the joint time-domain resource allocation table is set based on the time-domain resource allocation table referenced in the joint time-domain resource allocation table. <6> A communication method performed by a terminal, comprising the steps of: receiving downlink control information including control information relating to time-domain resource allocation; and identifying at least one time-domain resource from a plurality of physical uplink sharing channels and a plurality of physical downlink sharing 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 sharing channels and a plurality of physical downlink sharing channels for each of a plurality of cells, and the number of bits in the specific field included in the downlink control information is set to the maximum number of bits for a combination of at least one of the plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels set in each entry in the index of the joint time-domain resource allocation table.

[0133] In any of the above configurations, the terminal can operate efficiently in multi-carrier scheduling.

[0134] <Supplement to Embodiments> Although these embodiments have been described above, the disclosed invention is not limited to these embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0135] Furthermore, notification of information is not limited to the embodiments described herein and may be performed by other methods. For example, 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 combinations thereof. Information notified by higher layer signaling may be called configuration information. Information notified by physical layer signaling may be called control information. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0136] Each aspect / embodiment described herein may be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR, W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).

[0137] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0138] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME (Mobility Management Entity) or an S-GW (Serving Gateway), but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0139] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0140] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0141] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0142] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0143] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technologies (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0145] Furthermore, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, the signal may be a message. Also, CC may be called carrier frequency, cell, frequency carrier, etc.

[0146] The terms “system” and “network” as used in this disclosure are interchangeable.

[0147] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0148] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0149] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0150] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0151] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0152] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" 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 several other appropriate terms.

[0154] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0155] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0156] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

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

[0158] The terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0160] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0161] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0163] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0164] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0165] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

[0168] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

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

[0170] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0171] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0172] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0173] A TTI with a time length of 1 ms may be called a normal TTI (TTI in LTE Release 8-12), a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0174] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0176] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0177] One or more RBs may also be called a Physical RB (PRB), Subcarrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0178] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0179] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (Routing Bands) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of RBs relative to a common reference point of the carrier. PRBs may be defined and numbered within a given BWP.

[0180] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0181] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0182] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0183] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0184] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0185] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0186] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0187] This patent application claims priority based on Japanese Patent Application No. 2024-181402, filed on 17 October 2024, and the entire contents of Japanese Patent Application No. 2024-181402 are incorporated herein by reference.

[0188] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a receiving unit that receives downlink control information including control information relating to time domain resource allocation; and a control unit that identifies at least one of a plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels as a time domain resource 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 sharing channels and a plurality of physical downlink sharing 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 for a number of combinations of at least one of the plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels set in each entry in the index of the joint time domain resource allocation table.

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

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

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

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

6. A communication method performed by a terminal, comprising the steps of: receiving downlink control information including control information relating to time-domain resource allocation; and identifying a time-domain resource from a plurality of physical uplink sharing channels and a plurality of physical downlink sharing 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 sharing channels and a plurality of physical downlink sharing 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 for a combination of at least one of the plurality of physical uplink sharing channels and a plurality of physical downlink sharing channels set in each entry in the index of the joint time-domain resource allocation table.

Images