Terminal and communication method

Abstract

To transmit feedback information appropriately in scheduling a plurality of PDSCHs / PUSCHs in a plurality of cells.SOLUTION: A terminal includes a receiving unit that receives downlink control information, a control unit that generates feedback information and bundles a plurality of pieces of the feedback information, and a transmission unit that transmits the bundled feedback information, and the downlink control information schedules a plurality of physical downlink shared channels in each of a plurality of cells, and the feedback information is a positive or negative response to a single physical downlink shared channel.SELECTED DRAWING: Figure 8

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 with 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 Downlink Shared Channels (PDSCHs) / Physical Uplink Control Channels (PUCCHs) scheduled by multi-carrier scheduling in each cell was limited to one. However, in 3GPP Release 19, multi-carrier scheduling allows scheduling of multiple PDSCHs / PUSCHs (which may also be referred to as multi-PDSCHs / PUSCHs) in each cell. [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] Multi-cell scheduling poses the problem of an increase in the amount of Hybrid Automatic Repeat reQuest-Acknowledgement (HARQ-ACK) information that terminals use to notify the success or failure of data reception. HARQ-ACK bundling is a possible solution to this problem. HARQ-ACK bundling is a technology that reduces the amount of HARQ-ACK information by bundling multiple HARQ-ACK information together and transmitting them.

[0007] However, in the current standardization work, it is not clear whether HARQ-ACK bundling will be supported when multi-cell multi-PDSCH scheduling is supported.

[0008] If HARQ-ACK bundling is not supported, the complexity of the specifications can be reduced, but the amount of HARQ-ACK information may increase.

[0009] If HARQ-ACK bundling is supported, the amount of HARQ-ACK information can be reduced. However, for some reasons, it is necessary to clarify how a terminal configures HARQ-ACK bundling, how a terminal reports that it supports HARQ-ACK bundling, etc. The reason is that, as agreed upon in the current standardization work, multi-PDSCH / PUSCH scheduling in a single cell (which may also be referred to as single-cell multi-PDSCH / PUSCH scheduling) and multi-PDSCH / PUSCH scheduling in a multi-cell (which may also be referred to as multi-cell multi-PDSCH / PUSCH scheduling) cannot be configured simultaneously for a terminal within the same PUCCH group due to restrictions caused by the HARQ-ACK codebook (CB).

[0010] When supporting multi-cell multi-PDSCH scheduling, if it is not clear whether or not HARQ-ACK bundling is supported and how HARQ-ACK bundling is supported, there is a possibility that inconsistencies may occur in communications between the terminal and the base station, such as the base station being unable to properly process HARQ-ACK bundling.

[0011] The present invention has been made in view of the above problems, and has as its object to appropriately transmit feedback information in scheduling a plurality of PDSCHs / PUSCHs in a plurality of cells. [Means for solving the problem]

[0012] According to the disclosed technology, a terminal is provided which includes a receiving unit that receives downlink control information, a control unit that generates feedback information and bundles multiple pieces of the feedback information, and a transmitting unit that transmits the bundled feedback information, wherein the downlink control information schedules multiple physical downlink shared channels in each of multiple cells, and the feedback information is a positive response or a negative response to a single physical downlink shared channel. [Effects of the Invention]

[0013] According to the disclosed technology, feedback information can be appropriately transmitted in scheduling of a plurality of PDSCHs / PUSCHs in a plurality of cells. [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 according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example (2) of the configuration of a wireless communication system according to this embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of Type 1 HARQ-ACK feedback for multi-PDSCH scheduling, as defined in 3GPP Release 17. [Figure 4] FIG. 4 is a diagram illustrating an example of Type 2 HARQ-ACK feedback for multi-PDSCH scheduling, as defined in 3GPP Release 17. [Figure 5] FIG. 5 is a diagram illustrating an example of RRC parameters for configuring HARQ-ACK bundling for multi-PDSCH scheduling, as specified in 3GPP Release 17. [Figure 6] FIG. 6 is a diagram illustrating an example of the operation related to HARQ-ACK bundling for multi-PDSCH scheduling defined in 3GPP Release 17. [Figure 7] FIG. 7 is a diagram illustrating an overview of HARQ-ACK bundling in multi-cell multi-PDSCH scheduling. [Figure 8] FIG. 8 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling is supported in multi-cell multi-PDSCH scheduling. [Figure 9]FIG. 9 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling for type 1 HARQ CB is supported when time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported. [Figure 10] FIG. 10 shows an example of a parameter configuration when new parameters different from existing parameters are introduced for type 1 HARQ-ACK CB configuration. [Figure 11] FIG. 11 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling for type 2 HARQ CB is supported when time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported. [Figure 12] FIG. 12 is a diagram illustrating an example of a parameter configuration when a parameter different from the existing parameters is newly introduced for the type 2 HARQ-ACK CB configuration. [Figure 13] FIG. 13 is a diagram illustrating an example of inter-cell / inter-carrier HARQ bundling in multi-cell multi-PDSCH scheduling. [Figure 14] FIG. 14 is a diagram illustrating an example of a combination of inter-cell / inter-carrier HARQ bundling and time-domain HARQ bundling in multi-cell multi-PDSCH scheduling. [Figure 15] FIG. 15 is a diagram illustrating an example of the functional configuration of a base station in this embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of the functional configuration of a terminal according to this embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to this embodiment. [Figure 18] FIG. 18 is a diagram showing an example of the configuration of a vehicle according to this embodiment. 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 in this embodiment. 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.

[0022] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal (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, via a PBCH or a PDSCH, and is also referred to as broadcast information. The synchronization signal (SS) and system information (SI) may also be referred to as a synchronization signal block (SS / PBCH Block). As shown in FIG. 1 , 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). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 can apply Multiple Input Multiple Output (MIMO) communication to DL or UL. Furthermore, 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).

[0023] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path (channel) quality based on the reception results of the reference signals.

[0024] FIG. 2 is a diagram (2) showing an example of the configuration of a wireless communication system according to this embodiment.

[0025] As shown in FIG. 2, 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 stations 10A and 10B are not distinguished from each other, they may be referred to as "base station 10"). Furthermore, the terminal 20 supports NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is the master node (MN) and the base station 10B is the 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.

[0026] 2, the terminal 20 may communicate with a base station 10A provided by an LTE system and a base station 10B provided by an NR system. Furthermore, the terminal 20 may support LTE-NR dual connectivity, i.e., EN-DC, in which the base station 10A is an MN and the base station 10B is an SN. 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 reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.

[0027] 2, the terminal 20 may communicate with a base station 10A provided by the NR system and a base station 10B provided by the LTE system. Furthermore, the terminal 20 may 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 an MN and the base station 10B is an SN. 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 reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.

[0028] 2, the terminal 20 may communicate with a base station 10A provided by the NR system and a base station 10B provided by the NR system. Furthermore, the terminal 20 may support NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is an MN and the base station 10B is an SN. 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 reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.

[0029] Terminal 20 in this embodiment 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 executed in the system configuration shown in Fig. 1, the system configuration shown in Fig. 2, or other system configurations.

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

[0031] In the following description, "HARQ-ACK feedback," "HARQ-ACK information," "HARQ-ACK feedback information," "HARQ-ACK bit," and "feedback information" may be used interchangeably. "Type 1 HARQ-ACK CB," "Type 1 HARQ CB," "Type 1 HARQ-ACK feedback," and "Type 1 CB" may be used interchangeably. "Type 2 HARQ-ACK CB," "Type 2 HARQ CB," "Type 2 HARQ-ACK feedback," and "Type 2 CB" may be used interchangeably.

[0032] In the following description, parameter setting may basically mean parameter setting by Radio Resource Control (RRC). The terms "higher layer parameter," "RRC parameter," and "information element (IE)" may be used interchangeably.

[0033] The agreement on MCE in 3GPP Release 19 is as follows:

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

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

[0036] (2) One or more PDSCH / PUSCHs per cell scheduled by a single DCI.

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

[0038] (2-2) Type 1 HARQ-ACK CB is not extended for multi-carrier scheduling in 3GPP Release 19.

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

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

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

[0042] The multi-carrier scheduling supported by MCE in 3GPP Release 18 is expected to be extended in 3GPP Release 19 in terms of the above-mentioned 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 1_3 / 0_3), the number of PDSCH / PUSCH per cell was limited to one. However, in 3GPP Release 19, it will be possible to schedule multiple PDSCH / PUSCH per cell.

[0043] Here, multi-carrier scheduling in 3GPP Release 18 does not assume code block group (CBG) processing and multi-cell PDSCH scheduling in the same PUCCH cell group having type 2 HARQ-ACK CB. Also, multi-carrier scheduling in 3GPP Release 18 does not assume single-cell multi-PDSCH scheduling and multi-cell PDSCH scheduling in the same PUCCH cell group having type 2 HARQ-ACK CB. These restrictions are due to the fact that only up to two sub-CBs can be used when using type 2 HARQ-ACK CB.

[0044] FIG. 3 is a diagram illustrating an example of Type 1 HARQ-ACK feedback for multi-PDSCH scheduling, as defined in 3GPP Release 17.

[0045] As shown in Fig. 3(a), in multi-PDSCH scheduling defined in 3GPP Release 17, multiple PDSCHs are scheduled from one DCI or one cell. These multiple PDSCHs are scheduled in the same cell.

[0046] Here, when HARQ-ACK feedback is transmitted for each of these multiple PDSCHs, there is a high possibility that the feedback information is highly correlated because these multiple PDSCHs are transmitted under the same channel state and interference conditions.

[0047] Therefore, time-domain bundling of HARQ-ACK feedback is specified in multi-PDSCH scheduling, as shown in Figure 3(b). In time-domain bundling of HARQ-ACK feedback, a logical AND operation of HARQ-ACK feedback is used to combine multiple HARQ-ACK feedbacks into one value.

[0048] Type 1 HARQ-ACK feedback generates HARQ-ACK bits for PDSCH candidates within a slot window regardless of whether PDSCH scheduling is performed, and therefore the CB size is determined semi-statically.

[0049] Therefore, type 1 HARQ-ACK feedback without time-domain bundling as shown in FIG. 3(a) requires many HARQ-ACK bits.

[0050] On the other hand, in Type 1 HARQ-ACK feedback with time-domain bundling as shown in Figure 3(b), a HARQ-ACK bit is generated for the PDSCH candidate opportunity with the last SLIV (Start and Length Indicator Value) among multiple PDSCHs scheduled from one DCI.

[0051] In this way, by performing time domain bundling on HARQ-ACK feedback, the number of HARQ-ACK bits can be reduced, thereby saving uplink resources, for example.

[0052] As described above, Type 1 HARQ-ACK feedback works in multi-PDSCH scheduling.

[0053] FIG. 4 is a diagram illustrating an example of Type 2 HARQ-ACK feedback for multi-PDSCH scheduling, as defined in 3GPP Release 17.

[0054] Type 2 HARQ-ACK feedback generates HARQ-ACK bits only for PDSCHs scheduled by DCI, so the CB size is determined dynamically.

[0055] This determination process uses a DAI field consisting of a Counter Downlink Assignment Index (C-DAI) DAI and a Total DAI (T-DAI) included in the DCI. The C-DAI is incremented for each time domain transmission opportunity across each carrier / cell / CC set and indicates the cumulative number of PDCCH monitoring opportunities. The T-DAI indicates the cumulative number of PDCCH monitoring opportunities after considering all serving cells. Based on these values, the terminal 20 generates HARQ-ACK bits for multiple scheduled PDSCHs and arranges them in the appropriate order.

[0056] Similar to the restrictions on multi-carrier scheduling in 3GPP Release 18, Type 2 HARQ-ACK feedback does not assume CBG processing and multi-PDSCH scheduling in the same PUCCH cell group with Type 2 HARQ-ACK CB.

[0057] The CB for Type 2 HARQ-ACK feedback consists of a 1st sub-CB and a 2nd sub-CB. The 1st sub-CB is used for single PDSCH scheduling or multi-PDSCH scheduling in which the number of time domain bundling groups is set to 1. The 2nd sub-CB is used for multi-PDSCH scheduling in which time domain bundling is not set or the number of time domain bundling groups is set to more than 1.

[0058] As shown in Figures 4(a) and 4(b), consider a case where DCI #0 schedules PDSCH #1-1 and PDSCH #1-2, DCI #1 schedules PDSCH #2, DCI #2 schedules PDSCH #3-1 and PDSCH #3-2, and DCI #3 schedules PDSCH #4. In this case, there is no time domain bundling.

[0059] In the above case, as shown in Figure 4(c), among the CBs for Type 2 HARQ-ACK feedback, the 1st sub-CB is used for single PDSCH#2 scheduling by DCI#1 and single PDSCH#4 scheduling by DCI#3.

[0060] In the above case, as shown in Figure 4(c), the 2nd sub-CB of the CB for Type 2 HARQ-ACK feedback is used for multi-PDSCH (#1-1 and #1-2) scheduling using DCI#0 and multi-PDSCH (#3-1 and #3-2) scheduling using DCI#2.

[0061] In the above case, as shown in Figures 4(a) and 4(b), the number of PDSCHs scheduled by DCI#0 and DCI#2 is two. Here, if the maximum number of PDSCHs scheduled by each DCI is three, the second sub-CB for DCI#0 and the second sub-CB for DCI#2 also require three bits each. Therefore, as shown in Figure 3(c), in the second sub-CB for DCI#0 and the second sub-CB for DCI#2, for example, a HARQ-NACK (Negative ACK) bit is used in places where there is no corresponding PDSCH.

[0062] As shown in Figures 4(a) and 4(b), C-DAI and T-DAI are applied separately to the first sub-CB and the second sub-CB.

[0063] As described above, Type 2 HARQ-ACK feedback works in multi-PDSCH scheduling.

[0064] FIG. 5 is a diagram illustrating an example of RRC parameters for configuring HARQ-ACK bundling for multi-PDSCH scheduling, as specified in 3GPP Release 17.

[0065] As shown in Figure 5, the time domain bundling of Type 1 HARQ-ACK feedback is configured by a predetermined RRC parameter (e.g., timeDomainHARQ-BundlingType1). With this configuration, the time domain bundling of Type 1 HARQ-ACK feedback bundles HARQ-ACK feedback for all PDSCHs scheduled by one DCI.

[0066] As shown in Fig. 5, the time-domain bundling of Type 2 HARQ-ACK feedback is configured by a predetermined RRC parameter (e.g., nrofHARQ-BundlingGroups). With this configuration, the time-domain bundling of Type 2 HARQ-ACK feedback bundles HARQ-ACK feedback for all PDSCHs scheduled by one DCI into groups equal to the configured value.

[0067] The RRC parameters shown in FIG. 5 may be included in a higher-level IE (for example, ServingCellConfig).

[0068] Capabilities of terminal 20 related to HARQ-ACK bundling for multi-PDSCH scheduling are also specified in 3GPP Release 17. A terminal 20 having a certain capability (e.g., multiPDSCH-SingleDCI-FR2-1-SCS-120kHz) supports time-domain bundling of Type 1 and Type 2 HARQ-ACK feedback when it supports multi-PDSCH scheduling.

[0069] FIG. 6 is a diagram illustrating an example of the operation related to HARQ-ACK bundling for multi-PDSCH scheduling defined in 3GPP Release 17.

[0070] As shown in Fig. 6, when time domain bundling of Type 2 HARQ-ACK feedback is configured, terminal 20 generates HARQ-ACK information for each of multiple Transport Block Groups (TBGs). The maximum number of TBGs is set by a predetermined RRC parameter (e.g., nrofHARQ-BundlingGroups). When the maximum number of TBGs is 1, the number of HARQ-ACK bits per DCI is 1. When the maximum number of TBGs is 4, the number of HARQ-ACK bits per DCI is 4.

[0071] As shown in Figure 6, when single-cell multi-PDSCH scheduling is configured but time-domain bundling of Type 2 HARQ-ACK feedback is not configured, terminal 20 generates HARQ-ACK information for each TB. That is, terminal 20 generates the number of HARQ-ACK bits equal to the maximum number of PDSCHs that can be scheduled for one DCI.

[0072] As described above, 3GPP Releases 17 to 19 define and agree on multi-PDSCH scheduling, HARQ-ACK bundling, and the like.

[0073] However, it is not clear whether HARQ-ACK bundling is supported in the multi-cell multi-PDSCH / PUSCH scheduling supported in 3GPP Release 19.

[0074] As a solution to this problem, if HARQ-ACK bundling is not supported, the complexity of the specifications can be reduced. However, if Type 2 HARQ-ACK CB is used, terminal 20 generates the number of HARQ-ACK bits equal to "the number of cells per DCI format 1_3 x the number of PDSCH TBs (in the cell with the largest number of PDSCHs)." This may unnecessarily increase the number of HARQ-ACK bits in cases where there is correlation between HARQ-ACK feedback information for multiple PDSCHs in a certain cell.

[0075] To address this issue, if HARQ-ACK bundling is supported, the number of HARQ-ACK bits can be reduced. However, as explained above, single-cell multi-PDSCH scheduling and multi-cell multi-PDSCH scheduling cannot be configured simultaneously. This requires clarifying how terminal 20 configures HARQ-ACK bundling and how terminal 20 reports that it supports HARQ-ACK bundling.

[0076] In other words, when supporting multi-cell multi-PDSCH scheduling, if it is not made clear whether or not HARQ-ACK bundling is supported and how HARQ-ACK bundling is supported, there is a risk of inconsistencies in communication between the terminal and the base station, such as the base station not being able to process HARQ-ACK bundling properly.

[0077] FIG. 7 is a diagram illustrating an overview of HARQ-ACK bundling in multi-cell multi-PDSCH scheduling.

[0078] As shown in FIG. 7, when multiple PDSCHs from one DCI are scheduled in multiple cells / multiple CCs, time domain bundling may be performed in each cell / each CC.

[0079] According to this embodiment, in scheduling a plurality of PDSCHs / PUSCHs in a plurality of cells, terminal 20 can appropriately transmit feedback information.

[0080] The following describes an example of this embodiment. Hereinafter, time domain bundling may be referred to as time domain HARQ bundling, time HARQ bundling, time bundling, etc. Spatial domain bundling may be referred to as spatial domain HARQ bundling, spatial HARQ bundling, spatial bundling, etc.

[0081] Example 1 It may be specified whether time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported in the specification.

[0082] FIG. 8 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling is supported in multi-cell multi-PDSCH scheduling.

[0083] As shown in FIG. 8, when time domain HARQ bundling in multi-cell multi-PDSCH scheduling is not supported (step S101: NO), as shown in the previous Example 1-1, terminal 20 may generate HARQ-ACK bits for the number of PDSCH TBs without spatial domain HARQ bundling or the number of PDSCHs with spatial domain HARQ bundling for received DCI format 1_3 (step S102).

[0084] As shown in FIG. 8, if time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported (step S101: YES), a detailed support method or support operation for time domain HARQ bundling may be determined (step S103), as shown in the previous example 1-2.

[0085] <Example 1-1> In multi-cell multi-PDSCH scheduling using DCI format 1_3, time-domain HARQ bundling may not be supported in the specifications. That is, as described above, terminal 20 may generate HARQ-ACK bits for the number of PDSCH TBs without spatial-domain HARQ bundling or the number of PDSCHs with spatial-domain HARQ bundling for received DCI format 1_3. Base station 10 may receive PUCCH or PUSCH including the HARQ-ACK bits.

[0086] <Example 1-2> In multi-cell multi-PDSCH scheduling according to DCI format 1_3, time-domain HARQ bundling may be supported in the specifications. The base station 10 may receive a PUCCH or PUSCH including time-domain HARQ-bundled HARQ-ACK bits.

[0087] In multi-cell multi-PDSCH scheduling using DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, one or more of the following operations may be supported.

[0088] (Operation 1) Terminal 20 that supports multi-cell multi-PDSCH scheduling using DCI format 1_3 may also necessarily support time-domain HARQ bundling.

[0089] (Operation 2) Terminal 20 that supports multi-cell multi-PDSCH scheduling according to DCI format 1_3 may also support time-domain HARQ bundling in cells of a specific SCS / carrier type (e.g., 120 kHz SCS, FR2-1 / FR2-2, etc.). Terminal 20 that supports multi-cell multi-PDSCH scheduling according to DCI format 1_3 may also be required to support single-cell multi-PDSCH scheduling and time-domain HARQ bundling in at least one band.

[0090] (Operation 3) Terminal 20 that supports multi-cell multi-PDSCH scheduling according to DCI format 1_3 may also support time-domain HARQ bundling in bands / SCSs / carrier types that support existing single-cell multi-PDSCH scheduling.

[0091] (Operation 4) Terminal 20 that supports multi-cell multi-PDSCH scheduling using DCI format 1_3 may report capability information regarding whether time-domain HARQ bundling is supported. The capability information may be reported in the following units:

[0092] (Unit 1) Reporting may be done in band combination (BC) units. In such cases, any band / cell within the BC may be reported.

[0093] (Unit 2) It may be reported in feature set (FS) units. In this case, support for time-domain HARQ bundling may be reported for each band in a BC.

[0094] (Unit 3) May be reported in SCS units / carrier type units.

[0095] In multi-cell multi-PDSCH scheduling using DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, for example, some SCS / carrier types do not support time-domain HARQ bundling, the support status of time-domain HARQ bundling may be reported using an operation or unit other than (Unit 3) of (Operation 4) among (Operation 1) to (Operation 4).

[0096] As described above, by clearly defining support for HARQ-ACK bundling as in Example 1, terminal 20 can flexibly respond according to the capabilities of terminal 20. Furthermore, by supporting HARQ-ACK bundling, terminal 20 can aggregate feedback information for multiple cells and multiple PDSCHs.

[0097] <Example 2> In multi-cell multi-PDSCH scheduling using DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, time-domain HARQ bundling for type 1 HARQ CB may or may not be supported in the specifications.

[0098] FIG. 9 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling for type 1 HARQ CB is supported when time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported.

[0099] As shown in FIG. 9, if time-domain HARQ bundling for type-1 HARQ CB is not supported (step S201: NO), time-domain HARQ bundling for type-1 HARQ CB may not be performed (step S202).

[0100] As shown in FIG. 9, if time-domain HARQ bundling for type-1 HARQ CB is supported (step S201: YES), detailed operation / settings for when time-domain HARQ bundling for type-1 HARQ CB is supported may be determined (step S203), as shown in previous examples 2-1 and 2-2.

[0101] <Example 2-1> In multi-cell multi-PDSCH scheduling according to DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, time-domain HARQ bundling for type-1 HARQ CB may be always supported. Alternatively, in multi-cell multi-PDSCH scheduling according to DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, terminal 20 may report to base station 10 or the like as capability information (e.g., multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r19) whether terminal 20 supports time-domain HARQ bundling for type-1 HARQ CB. Base station 10 may receive capability information regarding terminal 20's support of time-domain HARQ bundling for type-1 HARQ CB.

[0102] <Example 2-2> For the type 1 HARQ-ACK CB configuration, a parameter (e.g., timeDomainHARQ-BundlingType1-r19) different from the existing parameter (e.g., timeDomainHARQ-BundlingType1-r17) may or may not be newly introduced. Base station 10 may transmit to terminal 20, for the type 1 HARQ-ACK CB configuration, predetermined parameters including a parameter different from the existing parameter (e.g., timeDomainHARQ-BundlingType1-r17).

[0103] FIG. 10 shows an example of a parameter configuration when new parameters different from existing parameters are introduced for type 1 HARQ-ACK CB configuration.

[0104] As shown in Fig. 10, a parameter (e.g., timeDomainHARQ-BundlingType1-r19) different from an existing parameter (e.g., timeDomainHARQ-BundlingType1-r17) may be defined. The different parameter may have the same candidate value (e.g., enabled) as the existing parameter, or may have a different candidate value.

[0105] <Example 2-2-1> When a new parameter (e.g., timeDomainHARQ-BundlingType1-r19) other than the existing parameter (e.g., timeDomainHARQ-BundlingType1-r17) is introduced for Type 1 HARQ-ACK CB configuration, one or more of the following settings may be made.

[0106] (Configuration 1) Another parameter (e.g., timeDomainHARQ-BundlingType1-r19) may be configured within a predetermined parameter. The predetermined parameter may be, for example, within ServingCellConfig to configure it in units of a serving cell, or within PDSCH-Config to configure it in units of a BandWidth Part (BWP) within a serving cell.

[0107] (Configuration 2) Another parameter (for example, timeDomainHARQ-BundlingType1-r19) may be configurable only when multi-cell multi-PDSCH scheduling is configured in the serving cell. The case where multi-cell multi-PDSCH scheduling is configured in the serving cell may be, for example, the case where a Joint Time Domain Resource Allocation (TDRA) table for multi-cell multi-PDSCH scheduling is configured.

[0108] (Setting 3) Another parameter (e.g., timeDomainHARQ-BundlingType1-r19) may not be set simultaneously with an existing parameter (e.g., timeDomainHARQ-BundlingType1-r17) in the same serving cell, or may be set simultaneously.

[0109] (Configuration 4) Another parameter (e.g., timeDomainHARQ-BundlingType1-r19) may be applied only to multi-cell multi-PDSCH scheduling using DCI format 1_3, and may not be applied to scheduling using other DCI (e.g., DCI format 1_1).

[0110] <Example 2-2-2> When a parameter (e.g., timeDomainHARQ-BundlingType1-r19) different from the existing parameter (e.g., timeDomainHARQ-BundlingType1-r17) is not newly introduced for configuring Type 1 HARQ-ACK CB, whether or not the existing parameter is configured in the same serving may be used to determine whether or not time domain HARQ bundling is applied in multi-cell multi-PDSCH scheduling. Also, when multi-cell multi-PDSCH scheduling is configured, the existing parameter may be applied only to multi-cell multi-PDSCH scheduling using DCI format 1_3, and may not be applied to scheduling using other DCI (e.g., DCI format 1_1).

[0111] As described above, by supporting time-domain HARQ bundling for type 1 HARQ-ACK CB configuration as in Example 2, terminal 20 can transmit HARQ-ACK bits efficiently in multi-cell multi-PDSCH scheduling. Furthermore, by introducing new parameters, flexible implementation options are provided to network operators.

[0112] Example 3 In multi-cell multi-PDSCH scheduling using DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, time-domain HARQ bundling for type 2 HARQ CB may or may not be supported in the specifications.

[0113] FIG. 11 is a diagram showing an example of a flowchart of operations depending on whether time domain HARQ bundling for type 2 HARQ CB is supported when time domain HARQ bundling in multi-cell multi-PDSCH scheduling is supported.

[0114] As shown in FIG. 11, if time-domain HARQ bundling for type-2 HARQ CB is not supported (step S301: NO), time-domain HARQ bundling for type-2 HARQ CB may not be performed (step S302).

[0115] As shown in FIG. 11, if time-domain HARQ bundling for type-2 HARQ CB is supported (step S301: YES), detailed operation / settings for when time-domain HARQ bundling for type-2 HARQ CB is supported may be determined (step S303), as shown in previous examples 3-1 and 3-2.

[0116] <Example 3-1> In multi-cell multi-PDSCH scheduling according to DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, time-domain HARQ bundling for type-2 HARQ CB may be always supported. Alternatively, in multi-cell multi-PDSCH scheduling according to DCI format 1_3, if time-domain HARQ bundling is supported in the specifications, terminal 20 may report to base station 10 or the like as capability information (e.g., multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r19) whether terminal 20 supports time-domain HARQ bundling for type-2 HARQ CB. Base station 10 may receive capability information regarding terminal 20's support of time-domain HARQ bundling for type-2 HARQ CB.

[0117] <Example 3-2> For the Type 2 HARQ-ACK CB configuration, a parameter (e.g., nrofHARQ-BundlingGroups-r19) different from the existing parameter (e.g., nrofHARQ-BundlingGroups-r17) may or may not be newly introduced. Base station 10 may transmit to terminal 20, for the Type 2 HARQ-ACK CB configuration, predetermined parameters including a parameter (e.g., nrofHARQ-BundlingGroups-r19) different from the existing parameter (e.g., nrofHARQ-BundlingGroups-r17).

[0118] FIG. 12 is a diagram illustrating an example of a parameter configuration when a parameter different from the existing parameters is newly introduced for the type 2 HARQ-ACK CB configuration.

[0119] As shown in FIG. 12, a parameter (eg, nrofHARQ-BundlingGroups-r19) different from the existing parameter (eg, nrofHARQ-BundlingGroups-r17) may be defined.

[0120] <Example 3-2-1> When a new parameter (e.g., nrofHARQ-BundlingGroups-r19) other than the existing parameter (e.g., nrofHARQ-BundlingGroups-r17) is introduced for Type 2 HARQ-ACK CB configuration, one or more of the following settings may be made.

[0121] (Configuration 1) Another parameter (e.g., nrofHARQ-BundlingGroups-r19) may be configured within a predetermined parameter. The predetermined parameter may be, for example, within ServingCellConfig to configure it per serving cell, or within PDSCH-Config to configure it per BWP in the serving cell.

[0122] (Configuration 2) Another parameter (e.g., nrofHARQ-BundlingGroups-r19) may be configurable only when multi-cell multi-PDSCH scheduling is configured in the serving cell. The case where multi-cell multi-PDSCH scheduling is configured in the serving cell may be, for example, the case where a joint TDRA table for multi-cell multi-PDSCH scheduling is configured.

[0123] (Configuration 3) Another parameter (e.g., nrofHARQ-BundlingGroups-r19) may not be configured simultaneously with an existing parameter (e.g., nrofHARQ-BundlingGroups-r17) in the same serving cell, or may be configured simultaneously.

[0124] (Configuration 4) Another parameter (e.g., nrofHARQ-BundlingGroups-r19) may be applied only to multi-cell multi-PDSCH scheduling using DCI format 1_3, and may not be applied to scheduling using other DCI (e.g., DCI format 1_1).

[0125] (Configuration 5) The configurable candidate values ​​for another parameter (e.g., nr of HARQ-BundlingGroups-r19) may be the same as or different from the existing parameter (e.g., nr of HARQ-BundlingGroups-r17) (e.g., ENUMERATED {n1, n2, n4}). For example, if the maximum number of PDSCHs per cell is 4, the candidate values ​​may be {n1, n2}.

[0126] <Example 3-2-2> When a parameter (e.g., nrofHARQ-BundlingGroups-r19) different from the existing parameter (e.g., nrofHARQ-BundlingGroups-r17) is not newly introduced for configuring type 1 HARQ-ACK CB, whether or not the existing parameter is configured in the same serving may be used to determine whether or not to apply time-domain HARQ bundling in multi-cell multi-PDSCH scheduling. Also, when multi-cell multi-PDSCH scheduling is configured, the existing parameter may be applied only to multi-cell multi-PDSCH scheduling using DCI format 1_3, and may not be applied to scheduling using other DCI (e.g., DCI format 1_1).

[0127] As described above, by supporting time-domain HARQ bundling for type 2 HARQ-ACK CB configuration as in Example 3, terminal 20 can transmit HARQ-ACK bits efficiently in multi-cell multi-PDSCH scheduling. Furthermore, by introducing new parameters, flexible implementation options are provided to network operators.

[0128] Example 4 In multi-cell multi-PDSCH scheduling using DCI format 1-3, it may be specified whether HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling is supported in the specifications. HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling may be, for example, inter-cell / inter-carrier bundling.

[0129] <Example 4-1> In multi-cell multi-PDSCH scheduling using DCI format 1_3, HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling may not be supported in the specifications. Terminal 20 does not need to perform HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling. Base station 10 does not need to assume that terminal 20 will perform HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling.

[0130] <Example 4-2> In multi-cell multi-PDSCH scheduling using DCI format 1_3, HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling may be supported in the specifications. Terminal 20 may perform HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling. Base station 10 may assume that terminal 20 performs HARQ bundling other than time-domain HARQ bundling / spatial-domain HARQ bundling.

[0131] FIG. 13 is a diagram illustrating an example of inter-cell / inter-carrier HARQ bundling in multi-cell multi-PDSCH scheduling.

[0132] As shown in Figure 13, when multiple PDSCHs from one DCI are scheduled to multiple cells / multiple CCs / multiple carriers, terminal 20 may perform time-domain bundling of HARQ-ACK bits between these multiple cells / multiple CCs / multiple carriers.

[0133] In multi-cell multi-PDSCH scheduling according to DCI format 1_3, if HARQ bundling other than time domain HARQ bundling / spatial domain HARQ bundling is supported in the specifications, one or more of the following operations may be supported.

[0134] (Operation 1) If multi-cell multi-PDSCH scheduling using DCI format 1_3 is supported in the specifications, inter-cell / inter-carrier HARQ bundling may be necessarily supported. Alternatively, if multi-cell multi-PDSCH scheduling using DCI format 1_3 is supported in the specifications, terminal 20 may report, as capability information, to base station 10 or the like, whether or not terminal 20 supports inter-cell / inter-carrier HARQ bundling. Base station 10 may receive capability information regarding terminal 20's support of inter-cell / inter-carrier HARQ bundling.

[0135] (Operation 2) Inter-cell / inter-carrier HARQ bundling in multi-cell multi-PDSCH scheduling may be enabled or disabled by a notification from the base station 10, such as a higher layer (e.g., RRC) parameter / MAC CE (Medium Access Control Element) / DCI. Alternatively, whether inter-cell / inter-carrier HARQ bundling in multi-cell multi-PDSCH scheduling is enabled or disabled may be determined based on a specific condition.

[0136] (Operation 3) Inter-cell / inter-carrier HARQ bundling may be applicable only between cells / carriers that satisfy certain conditions.

[0137] (Operation 4) Inter-cell / inter-carrier HARQ bundling may be configurable in combination with time-domain HARQ bundling and spatial-domain HARQ bundling. Inter-cell / inter-carrier HARQ bundling may be configured in combination with time-domain HARQ bundling and spatial-domain HARQ bundling. Inter-cell / inter-carrier HARQ bundling may always be configured in combination with time-domain HARQ bundling and spatial-domain HARQ bundling, and it may be configured in combination with only one of them.

[0138] In the above (Operation 2) and (Operation 3), the specific condition may be one or more of the following.

[0139] (Condition 1) Whether or not the co-scheduled cells contain multiple cells with a specific SCS / carrier type.

[0140] (Condition 2) Whether or not co-scheduled cells include multiple cells / CCs in the same band.

[0141] (Condition 3) Whether the number of HARQ-ACK bits generated per DCI format 1_3 exceeds a predetermined number.

[0142] FIG. 14 is a diagram illustrating an example of a combination of inter-cell / inter-carrier HARQ bundling and time-domain HARQ bundling in multi-cell multi-PDSCH scheduling.

[0143] As shown in Figure 14, when multiple PDSCHs from one DCI are scheduled to multiple cells / multiple CCs / multiple carriers, terminal 20 may perform time-domain bundling of HARQ-ACK bits between these multiple cells / multiple CCs / multiple carriers and in multiple time domains.

[0144] A bundling order may be defined for the inter-cell / inter-carrier HARQ bundling and time-domain HARQ bundling shown in Fig. 14. For example, terminal 20 may first perform inter-cell / inter-carrier HARQ bundling and then perform time-domain HARQ bundling. For example, terminal 20 may first perform time-domain HARQ bundling and then perform inter-cell / inter-carrier HARQ bundling.

[0145] As described above, by specifying whether HARQ bundling other than time domain HARQ bundling / spatial domain HARQ bundling is supported in the specifications as in Example 4, terminal 20 can reduce the number of HARQ-ACK bits by inter-cell / inter-carrier HARQ bundling. Furthermore, by setting specific conditions for inter-cell / inter-carrier HARQ bundling, network operators can select the optimal HARQ bundling depending on various network configurations.

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

[0147] ≪Base station≫ Fig. 15 is a diagram showing an example of the functional configuration of a base station in this embodiment. As shown in Fig. 15, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 15 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.

[0148] 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 to the terminal 20 configuration information, instructions, notifications, etc. related to a low-power wake-up signal. The transmitter 110 also transmits to the terminal a notification related to switching of monitoring operation. 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 receiver 120 receives capability information related to time-domain HARQ bundling for type 1 / 2 HARQ CB from the terminal 20. 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.

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

[0150] As described in the embodiments, the control unit 140 controls the settings, instructions, and notifications related to HARQ-ACK feedback / HARQ-ACK bundling. 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.

[0151] Terminal Fig. 16 is a diagram showing an example of the functional configuration of a terminal in this embodiment. As shown in Fig. 16, 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. 16 is merely an example. As long as the operations 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.

[0152] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 transmits capability information related to time-domain HARQ bundling for Type 1 / 2 HARQ CB to the base station 10. The transmitter 210 transmits feedback information such as HARQ-ACK information generated and bundled by the control unit 240. The transmitter 210 transmits PUSCH and other signals 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 other signals transmitted from the base station 10. The receiver 220 receives configuration information, instructions, notifications, and other information related to HARQ-ACK feedback / HARQ-ACK bundling from the base station 10. The receiver 220 receives PDSCH and other signals based on the radio resources specified by the control unit 240. The setting unit 230 stores various pieces of setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores various pieces of setting information that are set in advance.

[0153] As described in the embodiments, the control unit 240 controls the settings, instructions, and notifications related to HARQ-ACK feedback / HARQ-ACK bundling. The control unit 240 generates feedback information such as HARQ-ACK information. The control unit 240 bundles feedback information such as HARQ-ACK information. 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.

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

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

[0156] 17 is a diagram showing an example of the hardware configuration of a base station and a terminal in this embodiment. 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 above-mentioned base station 10 and the terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0157] 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 FIG. 17, or may be configured to exclude some of the apparatuses.

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

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

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

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

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

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

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

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

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

[0167] Fig. 18 is a diagram showing an example of the configuration of a vehicle in this embodiment. As shown in Fig. 18, a vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, for example, the communication module 2013.

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

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

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

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

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

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

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

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

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

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

[0178] <1> a receiving unit for receiving downlink control information; a control unit that generates feedback information and bundles a plurality of pieces of the feedback information; a transmitter that transmits the bundled feedback information, the downlink control information schedules a plurality of physical downlink shared channels in each of a plurality of cells; The terminal, wherein the feedback information is a positive acknowledgment or a negative acknowledgment for a single physical downlink shared channel. <2> the control unit bundles the feedback information used in a codebook of predetermined types of feedback information; <1> A terminal described in. <3> The transmitter transmits capability information indicating whether to bundle the feedback information used in a codebook of a predetermined type of feedback information; the control unit bundles the feedback information used in a codebook of the predetermined type of feedback information based on the capability information. <1> or <2> A terminal described in. <4> the control unit bundles the plurality of pieces of feedback information in at least one of a time domain and a spatial domain; The control unit bundles the plurality of pieces of feedback information between cells and / or carriers. <1> from <3> A terminal described in any one of the above. <5> the control unit bundles the plurality of pieces of feedback information in at least one of a time domain and a spatial domain; The control unit bundles the plurality of pieces of feedback information between at least one of cells and carriers based on a predetermined condition. <1> from <4> A terminal described in any one of the above. <6> receiving downlink control information; generating feedback information and bundling a plurality of said feedback information; and transmitting the bundled feedback information; the downlink control information schedules a plurality of physical downlink shared channels in each of a plurality of cells; A communication method performed by a terminal, wherein the feedback information is a positive acknowledgement or a negative acknowledgement for a single physical downlink shared channel.

[0179] With any of the above configurations, terminal 20 can appropriately transmit feedback information in scheduling a plurality of PDSCHs / PUSCHs in a plurality of cells.

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

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

[0182] 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 appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0201] 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 such a 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.

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

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

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

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

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

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

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

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

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

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

[0212] A slot may be composed 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 be a time unit based on numerology.

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

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

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

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

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

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

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

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

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

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

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

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

[0225] A BandWidth Part (BWP) (which may also be referred to as a fractional 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 their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within the BWP.

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

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

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

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

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

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

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

[0233] 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; a control unit that generates feedback information and bundles a plurality of pieces of the feedback information; a transmitter that transmits the bundled feedback information, the downlink control information schedules a plurality of physical downlink shared channels in each of a plurality of cells; The terminal, wherein the feedback information is a positive acknowledgment or a negative acknowledgment for a single physical downlink shared channel.

2. The terminal of claim 1 , wherein the control unit bundles the feedback information used in a codebook of feedback information of a predetermined type.

3. The transmitter transmits capability information indicating whether to bundle the feedback information used in a codebook of a predetermined type of feedback information; The terminal according to claim 1 , wherein the control unit bundles the feedback information used in a codebook of the predetermined type of feedback information based on the capability information.

4. the control unit bundles the plurality of pieces of feedback information in at least one of a time domain and a spatial domain; The terminal according to claim 1 , wherein the control unit bundles the plurality of pieces of feedback information at least one of between cells and between carriers.

5. the control unit bundles the plurality of pieces of feedback information in at least one of a time domain and a spatial domain; The terminal according to claim 1 , wherein the control unit bundles the plurality of pieces of feedback information at least one of between cells and between carriers based on a predetermined condition.

6. receiving downlink control information; generating feedback information and bundling a plurality of said feedback information; and transmitting the bundled feedback information; the downlink control information schedules a plurality of physical downlink shared channels in each of a plurality of cells; A communication method performed by a terminal, wherein the feedback information is a positive acknowledgement or a negative acknowledgement for a single physical downlink shared channel.

Images