Terminal, communication system, and communication method

Abstract

A terminal of the present invention comprises: a receiving unit that receives, from a base station, single control information and a plurality of downlink channels scheduled by using the single control information; a control unit that determines, on the basis of time domain resource allocation information, a codebook related to feedback information for the plurality of downlink channels, and determines the feedback information for the plurality of channels on the basis of the codebook; and a transmitting unit that transmits the feedback information for the plurality of channels to the base station. The control unit determines the time domain resource allocation information on the basis of whether the plurality of downlink channels overlap with an uplink symbol.

Description

[Technical Field]

[0001] The present invention relates to a wireless communication system. Terminal, communication system, and communication method Regarding. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high data transmission speed, low latency, simultaneous connection of many terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1). In addition, for NR, the use of high frequency bands such as 52.6 to 114.25 GHz is being considered.

[0003] In addition, in order to expand the frequency band, the NR system supports the use of frequency bands different from the frequency bands licensed to telecommunications carriers (operators) (also called unlicensed bands, unlicensed carriers, or unlicensed CCs). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 38.300 V16.4.0 (2020-12) [Non-patent document 2] 3GPP TS 38.331 V16.3.0 (2020-12) [Non-patent document 3] 3GPP TS 38.213 V16.4.0 (2020-12) [Non-patent document 4] 3GPP TS 38.321 V16.3.0 (2020-12) [Non-patent document 5] 3GPP TS 38.214 V16.4.0 (2020-12) Summary of the Invention [Problem to be solved by the invention]

[0005] As slot lengths become shorter with the use of higher frequency bands, it is expected that a base station will schedule multiple PDSCHs for a terminal using one piece of control information (DCI).

[0006] However, the conventional technologies described in Non-Patent Documents 1 to 5, etc., do not specify how to generate and transmit feedback information (specifically, HARQ-ACK information) when scheduling multiple PDSCHs with one DCI, and there is a possibility that the conventional technologies will not be able to transmit feedback information appropriately.

[0007] The present invention has been made in view of the above points, and aims to provide a technique that enables appropriate transmission of feedback information when scheduling multiple PDSCHs using one control information. [Means for solving the problem]

[0008] According to the disclosed technology, a receiving unit configured to receive, from a base station, single control information for scheduling a plurality of downlink channels and at least one of the plurality of downlink channels; a control unit configured to determine HARQ-ACK information for the plurality of downlink channels; and a transmitting unit configured to transmit the HARQ-ACK information to the base station, wherein the receiving unit does not receive a downlink channel that overlaps with an uplink symbol among the plurality of downlink channels; the control unit assumes that at least one of the plurality of downlink channels does not overlap with an uplink symbol; and when determining a codebook for the HARQ-ACK information, excludes a TDRA (Time Domain Resource Allocation) that overlaps with an uplink symbol from among TDRAs corresponding to the plurality of downlink channels; and assumes a maximum number of schedulable transport blocks for each of the plurality of downlink channels. is provided. [Effects of the Invention]

[0009] According to the disclosed technology, a technology is provided that enables appropriate transmission of feedback information when scheduling multiple PDSCHs using one piece of control information. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 2] 1 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. [Figure 3] FIG. 10 is a diagram illustrating an example of a band. [Figure 4] FIG. 10 is a diagram illustrating the relationship between SCS and symbol length. [Figure 5] FIG. 1 is a diagram illustrating an example of a basic procedure according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram illustrating a method for determining a PDSCH slot window. [Figure 7] FIG. 10 is a diagram illustrating a method for determining a PDSCH slot window. [Figure 8] FIG. 10 is a diagram for explaining a method for determining candidate reception opportunities in each slot. [Figure 9] FIG. 10 is a diagram illustrating an example of a HARQ-ACK codebook. [Figure 10] FIG. 10 is a diagram illustrating scheduling of multiple PDSCHs using one DCI. [Figure 11] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 12] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 13] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] Existing technology is used as appropriate when operating the wireless communication system according to the embodiment of the present invention. The existing technology is, for example, the existing NR. The wireless communication system (base station 10 and terminal 20) according to the present embodiment basically operates in accordance with existing regulations (e.g., Non-Patent Documents 1 to 5). However, to solve problems when high frequency bands are used, the base station 10 and terminal 20 also perform operations that are not specified in the existing regulations. In the explanation of the embodiments described below, operations that are not specified in the existing regulations will be mainly explained. Note that all numerical values described below are examples.

[0013] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

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

[0015] (System Configuration)

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

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

[0018] OFDM is used as the radio access method. In the frequency domain, subcarrier spacing (SCS) of at least 15 kHz, 30 kHz, 120 kHz, and 240 kHz is supported. Regardless of the SCS, a resource block is composed of a predetermined number of consecutive subcarriers (e.g., 12).

[0019] When performing initial access, terminal 20 detects an SSB (SS / PBCH block) and identifies the SCS in the PDCCH and PDSCH based on the PBCH included in the SSB.

[0020] In the time domain, a slot is made up of multiple OFDM symbols (for example, 14 symbols regardless of the subcarrier spacing). Hereinafter, an OFDM symbol is called a "symbol." A slot is the scheduling unit. Subframes with a duration of 1 ms are defined, and a frame consisting of 10 subframes is defined. Note that the number of symbols per slot is not limited to 14.

[0021] As shown in Fig. 1, a base station 10 transmits control information or data to a terminal 20 in a DL (Downlink) and receives control information or data from the terminal 20 in an UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a SCell (Secondary Cell) and a PCell (Primary Cell) using CA (Carrier Aggregation).

[0022] 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, an M2M (Machine-to-Machine) communication module, etc. As shown in Fig. 1, the terminal 20 receives control information or data from the base station 10 via DL and transmits control information or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0023] Terminal 20 can perform carrier aggregation, which aggregates multiple cells (multiple CCs (component carriers)) to communicate with base station 10. In carrier aggregation, one PCell (primary cell) and one or more SCells (secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0024] Fig. 2 shows an example of the configuration of a wireless communication system when NR-DC (NR-Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 communicates with both the base station 10A and the base station 10B.

[0025] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCell) and one or more SCells. Note that in this specification, a CC (Component Carrier) and a cell may be used synonymously. Also, a PCell and a PSCell may be referred to as an SPCell.

[0026] In the wireless communication system according to this embodiment, when an unlicensed band is used, LBT (Listen Before Talk) is executed. The base station 10 or the terminal 20 senses a signal, and transmits if the sensing result is idle, and does not transmit if the sensing result is busy. Note that LBT is not necessarily performed in an unlicensed band, and there may be cases where LBT is not performed in an unlicensed band.

[0027] (Regarding frequency bands) Fig. 3 shows examples of frequency bands used in the existing NR and frequency bands used in the wireless communication system according to this embodiment. The existing NR has two frequency bands (which may also be referred to as frequency ranges): FR1 (0.41 GHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). As shown in Fig. 3, FR1 supports SCSs of 15 kHz, 30 kHz, and 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 supports SCSs of 60 kHz, 120 kHz, and 240 kHz (SSB only), and a bandwidth (BW) of 50 to 400 MHz.

[0028] The wireless communication system according to this embodiment is assumed to use a frequency band higher than 52.6 GHz (for example, 52.6 GHz to 114.25 GHz) that is not used in the existing NR. This frequency band may be referred to as FR4, for example.

[0029] Furthermore, in this embodiment, it is assumed that, with the expansion of the frequency band as described above, an SCS wider than the existing SCS will be used. For example, an SCS of 480 kHz or an SCS wider than 480 kHz will be used as the SCS for SSB and PDCCH / PDSCH.

[0030] In the high frequency band, it is expected that multiple narrow beams will be used to compensate for the large propagation loss, and the SCS will be wider than the existing FR2 SCS (for example, 480 kHz, 960 kHz).

[0031] Figure 4 shows the relationship between SCS and symbol length (symbol time length). As shown in Figure 4, as the SCS becomes wider, the symbol length (symbol time length) becomes shorter. Also, assuming that the number of symbols per slot is constant (i.e., 14 symbols), as the SCS becomes wider, the slot length becomes shorter.

[0032] In a wireless communication system, a terminal 20 transmits HARQ-ACK information, in which a HARQ-ACK information bit value is set in a HARQ-ACK CodeBook (HARQ-ACK CB), as feedback to the base station 10 in response to data reception via a PDSCH from the base station 10. Note that transmitting / receiving data via a PDSCH may also be referred to as transmitting / receiving a PDSCH.

[0033] However, as described above, when the slot length is shortened due to the use of a high frequency band, it is assumed that multiple PDSCHs will be scheduled with one DCI scheduling. Based on such an assumption, it is not clear in the prior art how to generate the HARQ-ACK CB.

[0034] Hereinafter, an embodiment relating to generation of HARQ-ACK CB and transmission of HARQ-ACK information in a mode in which multiple PDSCHs are scheduled by scheduling using one DCI will be described.

[0035] (Basic operation) First, an example of a basic operation in the wireless communication system of this embodiment will be described with reference to FIG.

[0036] In S100, the terminal 20 transmits capability information (UE capability) to the base station 10. Using this capability information, the base station 10 can determine, for example, the content of the information to be transmitted to the terminal 20 in S101 and S102 below.

[0037] In S101, the base station 10 transmits configuration information to the terminal 20 by an RRC message, and the terminal 20 receives the configuration information. The configuration information is, for example, configuration information related to a K1 set and a TDRA table, as described below. Note that the K1 set and the TDRA table may both be notified from the base station 10 to the terminal 20, or may be predetermined in specifications or the like, and the base station 10 and the terminal 20 may use the predetermined ones. The TDRA table may also be called time domain resource allocation configuration information.

[0038] In S102, the base station 10 transmits scheduling (allocation information) for multiple PDSCHs by DCI to the terminal 20, and the terminal 20 receives the DCI. The DCI also includes information about uplink resources for transmitting HARQ-ACK information.

[0039] In S103, the terminal 20 receives the PDSCH based on the scheduling information in the DCI, and in S104 transmits HARQ-ACK information to the base station 10. The base station 10 receives the HARQ-ACK information.

[0040] (Type 1 HARQ-ACK CB generation) This embodiment is directed to Type 1 HARQ-ACK CB. First, a method for generating Type 1 HARQ-ACK CB in R16 (Release 16) will be described (see Non-Patent Document 3, etc.). In the following description, a case will be described in which PUCCH is used as a channel for transmitting HARQ-ACK information, but the channel for transmitting HARQ-ACK information may also be PUSCH.

[0041] First, the general flow is divided into the following steps A and B. The flow itself is the same in the first and second embodiments.

[0042] In step A, terminal 20 determines HARQ-ACK occasions indicating the PDSCHs that may be received. The bit indexes in the HARQ-ACK occasions represent the reception opportunities for each PDSCH. The HARQ-ACK occasions may also be referred to as a HARQ-ACK codebook.

[0043] In step B, the terminal 20 performs the O in the HARQ-ACK occasions determined in step A. ACK For example, if data is received correctly at a certain reception opportunity, the corresponding bit becomes a bit indicating ACK.

[0044] Then, the terminal 20 transmits to the base station 10 HARQ-ACK information in which the value of the HARQ-ACK information bit is set to the bit position of each reception opportunity.

[0045] More specifically, Step A consists of the following Steps A-1 and A-2.

[0046] <Step A-1> The terminal 20 determines the PDSCH slot window based on the set K1 set.

[0047] The K1 set C(K1) = {1, 2, 3, 4}, and the uplink and downlink numerologies are equal (μ DL =μ UL An example of a PDSCH slot window in this case is shown in FIG.

[0048] 6, the upper part shows the serving cell c that receives the PDSCH, and the lower part shows the PUCCH cell. This also applies to the subsequent figures.

[0049] K1 indicates the distance (number of slots) between the slot in which the PDSCH is received and the slot in which the PUCCH is transmitted, as viewed from the PUCCH cell. In other words, K1 is a parameter value indicating the timing of transmitting feedback. In the case of FIG. 6, since the PUCCH is transmitted in slot n+4 of the PUCCH cell, slots n to n+3 of the serving cell c are determined as the PDSCH slot window (the time window of slots in which the PDSCH may be received).

[0050] K1 set C(K1) = {1,2,3,4,5}, and μ DL >μ UL An example of a PDSCH slot window in this case is shown in Figure 7. In the case of Figure 7, since the PUCCH is transmitted in slot n+5 of the PUCCH cell, slots 2n to 2n+9 of serving cell c are determined as the PDSCH slot window (a time window of slots in which the PDSCH may be received). For example, slot 2n of the serving cell corresponds to the time position of slot n of the PUCCH cell, so slot n+5, which is five slots later (K1=5) based on the slot length in the PUCCH cell, becomes the slot for transmitting the PUCCH.

[0051] <Step A-2> In step A-2, terminal 20 determines candidate PDSCH reception occasions for each slot in the window determined in step A-2. Specifically, it executes the steps S1 to S3 as follows.

[0052] In S1, the candidate PDSCH reception occasions are associated with a set R (a set of rows) of a Time Domain Resource Allocation (TDRA) table.

[0053] In S2, the overlapping part with the part where the UL is set by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated is excluded from the allocation information (SLIV) in the TDRA table.

[0054] In S3, for candidate PDSCH reception occasions that overlap in the time domain, candidate PDSCH reception occasions are determined according to a predetermined rule.

[0055] An example of determining candidate PDSCH reception occasions in a certain slot n will be described with reference to Figure 8. In the TDRA table shown in Figure 8(a), one row corresponds to one SLIV (allocation information: indicating the start symbol and symbol length in the slot), and there are nine types, each identified by a row index (RI). Note that the RI is specified by DCI, and terminal 20 recognizes the specified SLIV as the actual PDSCH reception occasion. Furthermore, K1 is also specified by DCI.

[0056] (b) shows the SLIVs of all RIs defined in the TDRA table on a slot-by-slot basis. For convenience of notation, three slots are shown, but this shows that there are nine types of SLIV candidates in one slot.

[0057] Here, as shown in (c), RI2, RI3, and RI8 overlap with semi-static UL symbols and are therefore excluded from the candidate PDSCH reception occasions.

[0058] After excluding RI2, RI3, and RI8, the SLIVs are RI0, RI1, and RI4 to RI7. As shown in (d) and (e), RI0 and RI4 overlap, and RI1 overlaps with RI5 and RI6, but according to a predetermined rule, RI0 and RI4 become one occasion as candidate PDSCH reception occasions and are assigned index 0, and RI1 and RI5 also become one occasion as candidate PDSCH reception occasions and are assigned index 1. As a result, the candidate PDSCH reception occasions (M A,c ) becomes {0,1,2,3}.

[0059] By performing the above processing for each slot, as shown in FIG. 9, M PDSCH reception occasions consisting of candidate PDSCH reception occasions for each slot in the PDSCH slot window are obtained. A,c is generated.

[0060] (Multi-PDSCH / PUSCH scheduling) In this embodiment, multi-PDSCH / PUSCH scheduling is supported, in which multiple PDSCHs (or multiple PUSCHs) are scheduled by one scheduling using DCI. Multi-PDSCH scheduling will be described below.

[0061] The TDRA table used in multi-PDSCH scheduling is, for example, a table having one or more SLIVs in each row. Furthermore, multiple PDSCHs scheduled by one DCI may or may not be contiguous in time.

[0062] More specifically, the TDRA table is extended so that each row indicates up to eight PDSCHs, each with a different SLIV and mapping type. The number of PDSCHs scheduled by one DCI is implicitly indicated by the number of valid SLIVs in the row of the TDRA table indicated by the DCI.

[0063] (HARQ-ACK in multi-PDSCH scheduling) In this embodiment, terminal 20 can transmit HARQ-ACK feedback for multiple PDSCHs scheduled by multi-PDSCH scheduling, using the same PUCCH.

[0064] That is, HARQ-ACK information corresponding to multiple PDSCHs scheduled by one DCI that schedules multiple PDSCHs is multiplexed into one PUCCH in a slot determined based on K1.

[0065] Here, as shown in FIG. 10, K1 is the slot offset between the slot in the last PDSCH scheduled by the DCI and the slot carrying HARQ-ACK information corresponding to the scheduled multiple PDSCHs.

[0066] Note that K1 is a value indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI. If the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI, K1 is a value given by dl-DataToUL-ACK.

[0067] In addition, in this embodiment, the following options 1, 1a, and 2 are available for generating a type 1 HARQ-ACK codebook corresponding to DCI that schedules multiple PDSCHs.

[0068] Option 1: The terminal 20 determines candidate PDSCH reception occasions based on each SLIV in each row in the TDRA table and an extension of the K1 set.

[0069] Option 1a: The terminal 20 determines candidate PDSCH reception occasions based on each SLIV in each row in the TDRA table.

[0070] Option 2: The terminal 20 determines candidate PDSCH reception occasions based on the last SLIV in each row in the TDRA table.

[0071] (Restrictions on PDSCH / PUSCH dynamic scheduling) In the dynamic grant for PDSCH and PUSCH in the prior art, when repeated transmission is not applied to the PDSCH / PUSCH, the PDSCH may not assume overlap with semi-static or dynamic UL symbols, and the PUSCH may not assume overlap with semi-static or dynamic DL symbols. Note that "PDSCH / PUSCH" represents "PDSCH and / or PUSCH."

[0072] Furthermore, when slot-based repeated transmission is supported for PDSCU / PUSCH, in repeated transmission of PDSCH / PUSCH by dynamic grant in multiple slots, if the slot in which the PDSCH is placed overlaps with a quasi-static UL symbol, the PDSCH does not need to be transmitted, and if the slot in which the PUSCH is placed overlaps with a quasi-static DL symbol, the PUSCH does not need to be transmitted.

[0073] Also, if minislot-based repeat transmission is supported for PUSCH, the division is performed by quasi-static DL symbols and invalid symbols. Repeat transmissions that overlap with quasi-static DL symbols and invalid symbols are not transmitted.

[0074] Here, we need to consider the TDRA limitation due to TDD-DL / UL collision. For example, if TDRA is excluded due to TDD-DL / UL collision, it will affect the generation of the Type 1 HARQ-ACK codebook.

[0075] In addition, it is necessary to determine the number of transport blocks supported when scheduling multiple PDSCHs, which is related to the number of HARQ-ACK bits for one candidate PDSCH reception occasion and the number of HARQ-ACK bits for the type 1 HARQ-ACK codebook.

[0076] Therefore, we investigate the limitations of multiple PDSCH / PUSCH scheduling due to TDD-DL / UL collisions. For example, we consider how to limit TDRA by taking TDD-DL / UL collisions into account. We also investigate the impact of TDRA limitations on PDSCH reception opportunity candidates for generating the Type 1 HARQ-ACK codebook.

[0077] Furthermore, we consider the maximum number of transport blocks supported in multiple PDSCH scheduling, for example, how to determine the maximum number of transport blocks supported in multiple PDSCH scheduling, and how this affects the number of bits in the type 1 HARQ-ACK codebook.

[0078] It should be noted that any of the steps or operations described above may be used to generate the HARQ-ACK codebook in the following description.

[0079] (Example) (Proposal 1) The following describes restrictions on scheduling by TDRA in multiple-PDSCH / multiple-PUSCH scheduling.

[0080] (Option 1) Terminal 20 may not assume that the PDSCH overlaps with semi-static and / or dynamic UL symbols in multiple PDSCH scheduling, and may not assume that the PUSCH overlaps with semi-static and / or dynamic DL symbols in multiple PUSCH scheduling. In other words, the same restrictions as those in conventional dynamic PDSCH / PUSCH scheduling without repeated transmission may be applied.

[0081] (Option 2) In multiple-PDSCH scheduling, a PDSCH may overlap with a semi-static and / or dynamic UL symbol, and in multiple-PUSCH scheduling, a PUSCH may overlap with a semi-static and / or dynamic DL symbol. Terminal 20 may not receive a PDSCH that overlaps with a semi-static and / or dynamic UL symbol, and may not receive a PUSCH that overlaps with a semi-static and / or dynamic DL symbol. By allowing this overlap, more rows can be used in TDRA when scheduling multiple PDSCHs / PUSCHs using one DCI.

[0082] (Option2-1) In multiple PDSCH scheduling, any PDSCH may overlap with semi-static and / or dynamic UL symbols, and in multiple PUSCH scheduling, any PUSCH may overlap with semi-static and / or dynamic DL symbols.

[0083] (Option2-2) In multiple PDSCH scheduling, it may not be assumed that all PDSCHs overlap with semi-static and / or dynamic UL symbols, and in multiple PUSCH scheduling, it may not be assumed that all PUSCHs overlap with semi-static and / or dynamic DL symbols, i.e., at least one PDSCH / PUSCH may be received or transmitted.

[0084] (Option 2-3) In multiple PDSCH scheduling, it may not be assumed that the first, last and penultimate PDSCHs overlap with semi-static and / or dynamic UL symbols, and in multiple PUSCH scheduling, it may not be assumed that the first, last and penultimate PUSCHs overlap with semi-static and / or dynamic DL symbols.

[0085] (Option 2-4) In multiple-PDSCH scheduling, it is not necessary to assume that a predetermined PDSCH overlaps with a quasi-static and / or dynamic UL symbol, and in multiple-PUSCH scheduling, it is not necessary to assume that a predetermined PUSCH overlaps with a quasi-static and / or dynamic DL symbol. The predetermined PDSCH / the predetermined PUSCH may be designated by a set index or a predefined index. For example, it is not necessary to assume that the first, second from the top, and third from the top PDSCH / PUSCH overlap with a quasi-static and / or dynamic UL / DL symbol.

[0086] (Proposal 2) The following describes the effect of deleting TDRA rows for the Type 1 HARQ-ACK codebook due to restrictions on scheduling by TDRA in multiple-PDSCH / multiple-PUSCH scheduling.

[0087] When generating a type 1 HARQ-ACK codebook, whether and how to remove TDRA rows largely depends on the constraints imposed by TDRA scheduling. Terminal 20 may operate as shown in 1)-5) below. Note that the operations shown in 1)-5) may be applied to any type 1 HARQ-ACK codebook generation.

[0088] 1) Restrictions on TDRA scheduling: In multiple PDSCH scheduling, the terminal 20 may not assume that the PDSCH overlaps with quasi-static and / or dynamic UL symbols, and in multiple PUSCH scheduling, the terminal 20 may not assume that the PUSCH overlaps with quasi-static and / or dynamic DL symbols. Operation for TDRA row elimination based on TDD-DL / UL collision: SLIVs included in TDRA rows that collide with quasi-static and / or dynamic UL / DL symbols may be eliminated.

[0089] 2) TDRA Scheduling Restrictions: In multiple PDSCH scheduling, any PDSCH may overlap with semi-static and / or dynamic UL symbols, and in multiple PUSCH scheduling, any PUSCH may overlap with semi-static and / or dynamic DL symbols. Operation for TDRA row elimination based on TDD-DL / UL collision: SLIVs included in TDRA rows that collide with quasi-static and / or dynamic UL / DL symbols may not be eliminated.

[0090] 3) Restrictions on TDRA scheduling: In multiple-PDSCH scheduling, the terminal 20 may not assume that all PDSCHs overlap with quasi-static and / or dynamic UL symbols, and in multiple-PUSCH scheduling, the terminal 20 may not assume that all PUSCHs overlap with quasi-static and / or dynamic DL symbols. Operation for TDRA row elimination based on TDD-DL / UL collision: All SLIVs included in a TDRA row that collide with a quasi-static and / or dynamic UL / DL symbol may be eliminated.

[0091] 4) Restrictions on TDRA scheduling: In multiple PDSCH scheduling, the terminal 20 may not assume that the first, last, or second to last PDSCH overlaps with a quasi-static and / or dynamic UL symbol, and in multiple PUSCH scheduling, the terminal 20 may not assume that the first, last, or second to last PUSCH overlaps with a quasi-static and / or dynamic DL symbol. Operation related to TDRA row deletion based on TDD-DL / UL collision: The SLIV corresponding to the first, last or penultimate PDSCH / PUSCH included in a TDRA row that collides with a quasi-static and / or dynamic UL / DL symbol may be deleted.

[0092] 5) Restrictions on TDRA scheduling: In multiple PDSCH scheduling, the terminal 20 may not assume that a given PDSCH overlaps with a quasi-static and / or dynamic UL symbol, and in multiple PUSCH scheduling, may not assume that a given PUSCH overlaps with a quasi-static and / or dynamic DL symbol. Operation related to TDRA row elimination based on TDD-DL / UL collision: SLIVs corresponding to a given PDSCH / PUSCH included in a TDRA row that collides with a quasi-static and / or dynamic UL / DL symbol may be eliminated.

[0093] In the above 2), the PDSCH / PUSCH slot window may be determined after row deletion of TDRA.

[0094] (Proposal 3) Restrictions on transport block scheduling will be described below. Note that hereinafter, PDSCH may be replaced with PUSCH.

[0095] (Case A) In multiple PDSCH scheduling using one DCI, the maximum number of transport blocks that can be scheduled in one PDSCH may be 2. The number of transport blocks that can be scheduled in one PDSCH may be determined by Alt1 or Alt2 below.

[0096] Alt 1) The same maximum number of transport blocks that can be scheduled for one PDSCH may be configured for both single-PDSCH scheduling and multiple-PDSCH scheduling. For example, the maximum number of transport blocks that can be scheduled for one PDSCH may reuse the RRC parameter "maxNrofCodeWordsScheduledByDCI" referenced for single-PDSCH scheduling.

[0097] Alt2) The maximum number of transport blocks that can be scheduled for one PDSCH may be configured independently for single-PDSCH scheduling and multiple-PDSCH scheduling. For example, the maximum number of transport blocks that can be scheduled for one PDSCH for multiple-PDSCH scheduling may be configured using a new RRC parameter "maxNrofCodeWordsMultiplePdschsScheduledByDCI-R17". The maximum number of transport blocks that can be scheduled for one PDSCH for multiple-PDSCH scheduling may be the same as, smaller than, or larger than the maximum number of transport blocks that can be scheduled for one PDSCH for single-PDSCH scheduling.

[0098] (Case B) In multiple PDSCH scheduling using one DCI, only one transport block may be supported as the number of transport blocks that can be scheduled in one PDSCH.

[0099] (Proposal 4) The following describes the effect of the restriction on the number of transport blocks on the number of HARQ-ACK bits corresponding to one PDSCH candidate reception opportunity. Note that hereinafter, PDSCH may be replaced with PUSCH.

[0100] (Case 1) When the HARQ-ACK information of each PDSCH is mapped to a PDSCH candidate reception opportunity corresponding to the SLIV of the PDSCH, the terminal 20 may perform the operation shown in Option 1 or Option 2 below.

[0101] (Option 1) The number of HARQ-ACK bits may be the same for all PDSCH candidate reception opportunities. For example, the number of HARQ-ACK bits may be determined based on the maximum number of transport blocks supported by single-PDSCH scheduling or the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0102] (Option 2) The number of HARQ-ACK bits may be different for different PDSCH candidate reception opportunities. Hereinafter, terminal 20 may perform the operations shown in 1)-3).

[0103] 1) When each SLIV corresponding to one PDSCH candidate reception opportunity is included only in a single SLIV row of the TDRA, or when it is included in multiple SLIV rows of the TDRA and the multiple SLIV rows are deleted due to TDD-DL / UL collision, the number of HARQ-ACK bits corresponding to the PDSCH candidate reception opportunity may be determined by Alt1 or Alt2 below. Alt1) Maximum number of transport blocks supported for single PDSCH scheduling. Alt2) The maximum number of transport blocks supported by single-PDSCH scheduling and the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0104] 2) When each SLIV corresponding to one PDSCH candidate reception opportunity is included only in a row of multiple SLIVs in the TDRA, the number of HARQ-ACK bits corresponding to the PDSCH candidate reception opportunity may be determined by Alt1 or Alt2 below. Alt1) Maximum number of transport blocks supported for single PDSCH scheduling. Alt2) The maximum number of transport blocks supported by single-PDSCH scheduling and the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0105] 3) In cases other than 1) and 2) above, the number of HARQ-ACK bits corresponding to a PDSCH candidate reception opportunity may be determined by the maximum number of transport blocks supported by single-PDSCH scheduling or the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0106] (Case 2) When the HARQ-ACK information of each PDSCH is mapped to one PDSCH candidate reception opportunity corresponding to the last SLIV of the PDSCH, the terminal 20 may perform the operation shown in Option 1 or Option 2 below.

[0107] (Option 1) The number of HARQ-ACK bits may be the same for each reserved PDSCH reception corresponding to all PDSCH candidate reception opportunities. For example, the number of HARQ-ACK bits may be determined based on the maximum number of transport blocks supported by single-PDSCH scheduling or the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0108] (Option 2) The number of HARQ-ACK bits may be different for reserved PDSCH receptions corresponding to different PDSCH candidate reception opportunities. Hereinafter, terminal 20 may perform the operations shown in 1)-3).

[0109] 1) When the number of reserved PDSCH receptions corresponding to the PDSCH candidate reception opportunities is 1, the number of HARQ-ACK bits for the reserved PDSCH receptions corresponding to the PDSCH candidate reception opportunities may be determined by Alt1 or Alt2 below. Alt1) Maximum number of transport blocks supported for single PDSCH scheduling. Alt2) The maximum number of transport blocks supported by single-PDSCH scheduling and the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0110] 2) If the number of reserved PDSCH receptions corresponding to the PDSCH candidate reception opportunities exceeds 1, and each SLIV corresponding to the PDSCH candidate reception opportunities is included only in the multiple SLIV row of the TDRA and not in the single SLIV row, the number of HARQ-ACK bits for the reserved PDSCH reception corresponding to the PDSCH candidate reception opportunities may be determined by Alt1 or Alt2 below. Alt1) Maximum number of transport blocks supported for single PDSCH scheduling. Alt2) The maximum number of transport blocks supported by single-PDSCH scheduling and the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0111] 3) In cases other than 1) and 2) above, the number of HARQ-ACK bits corresponding to a PDSCH candidate reception opportunity may be determined by the maximum number of transport blocks supported by single-PDSCH scheduling or the maximum number of transport blocks supported by multiple-PDSCH scheduling, whichever is larger.

[0112] The number of reserved PDSCHs for one PDSCH candidate reception opportunity may be determined based on the settings in the TDRA table, or may be determined based on the maximum number of PDSCHs scheduled by one DCI.

[0113] (Other examples) An example applicable to any of the embodiments will be described below.

[0114] Which of the above-mentioned multiple Proposals / Options / Alts is used may be set by upper layer parameters transmitted from the base station 10 to the terminal 20, or may be notified from the terminal 20 to the base station 10 as terminal capability (UE Capability), may be defined by specifications, or may be set by upper layer parameters and notified by the terminal 20 as terminal capability (UE Capability).

[0115] Information indicating whether terminal 20 supports scheduling of multiple PDSCHs based on a single DCI may be defined as UE capability.

[0116] Furthermore, as the terminal capability (UE Capability), information indicating whether or not the terminal 20 supports joint HARQ-ACK feedback for multiple PDSCHs scheduled in a single DCI (a function of collectively notifying multiple HARQ-ACKs for multiple PDSCHs) may be defined.

[0117] Furthermore, as the UE capability, information indicating whether or not the UE supports determining candidate PDSCHoccasions based on each SLIV in each TDRA row may be defined.

[0118] Furthermore, as the UE capability, information indicating whether or not the UE supports determining an SLIV set (for determining candidate PDSCH occurrences) based on the span of a TDRA row in a certain PDSCH slot may be defined.

[0119] Furthermore, information indicating whether or not the extension of the PDSCH slot window is supported may be defined as the UE capability. Furthermore, information indicating whether or not the extension of the K1 set is supported may be defined as the UE capability.

[0120] Furthermore, information indicating whether or not mapping of multiple PDSCH slots associated with a corresponding DL slot to a K1 value may be defined as UE capability.

[0121] Furthermore, as UE capability, information indicating whether or not multiple PDSCH / PUSCH scheduling, which schedules PDSCHs / PUSCHs that overlap with UL / DL symbols, is supported may be defined.

[0122] Furthermore, as UE capability, information indicating whether multiple PDSCH / PUSCH scheduling, in which at least one PDSCH / PUSCH that does not overlap with UL / DL symbols, is scheduled, may be defined.

[0123] Furthermore, as the UE capability, information indicating whether or not multiple PDSCH / PUSCH scheduling is supported, which schedules PDSCHs / PUSCHs that overlap with UL / DL symbols and are other than the first, last, and penultimate PDSCHs / PUSCHs, may be defined.

[0124] Furthermore, as the UE capability, information indicating whether or not multiple PDSCH / PUSCH scheduling is supported, which schedules PDSCH / PUSCHs that overlap with UL / DL symbols and are other than a predetermined PDSCH / PUSCH, may be defined.

[0125] Furthermore, as UE capability, information indicating whether multiple PDSCH / PUSCH scheduling for scheduling up to two transport blocks per PDSCH is supported may be defined.

[0126] The terminal 20 may transmit one or more of the above-mentioned capability information to the base station 10. Furthermore, based on the capability information received from the terminal 20, the base station 10 may instruct the terminal 20 to operate in accordance with the capability.

[0127] According to the technology of the present embodiment described above, when multiple PDSCHs / PUSCHs are scheduled by one DCI, terminal 20 can determine the TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit feedback information to base station 10.

[0128] That is, a technique is provided that enables appropriate transmission of feedback information when scheduling multiple PDSCHs using one piece of control information.

[0129] (Device configuration) Next, 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.

[0130] <Base station 10> Fig. 11 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 11, 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. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention. Furthermore, the transmitting unit 110 and the receiving unit 120 may be collectively referred to as a communication unit.

[0131] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signals. The transmitter 110 also has a function of transmitting, to the terminal 20, an NR-PSS, an NR-SSS, an NR-PBCH, a DL / UL control signal, DCI via a PDCCH, data via a PDSCH, and the like.

[0132] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device provided in the setting unit 130, and reads out the information from the storage device as needed.

[0133] The control unit 140 schedules DL reception or UL transmission of the terminal 20 via the transmission unit 110. The control unit 140 also includes a function for performing LBT. The functional unit related to signal transmission in the control unit 140 may be included in the transmission unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the reception unit 120. The transmission unit 110 may also be called a transmitter, and the reception unit 120 may also be called a receiver.

[0134] <Terminal 20> Fig. 12 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 12, 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. 12 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0135] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires a higher layer signal from the received physical layer signal. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, DCI via PDCCH, data via PDSCH, and the like transmitted from the base station 10. For example, the transmitter 210 may transmit a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 may receive the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0136] The setting unit 230 stores various setting information received by the receiving unit 220 from the base station 10 or other terminals in a storage device provided in the setting unit 230, and reads the information from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The control unit 240 controls the terminal 20. The control unit 240 also includes a function for performing LBT.

[0137] (Summary of the embodiment) As described above, according to an embodiment of the present invention, there is provided a terminal including: a receiver that receives, from a base station, single control information and multiple downlink channels scheduled by the single control information; a controller that determines a codebook for feedback information for the multiple downlink channels based on time domain resource allocation information and determines feedback information for the multiple channels based on the codebook; and a transmitter that transmits the feedback information for the multiple channels to the base station, wherein the controller determines the time domain resource allocation information based on whether the multiple downlink channels overlap with an uplink symbol.

[0138] With the above configuration, when multiple PDSCHs / PUSCHs are scheduled by one DCI, terminal 20 can determine the TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit feedback information to base station 10. In other words, a technique is provided that enables appropriate transmission of feedback information when multiple PDSCHs are scheduled by one control information.

[0139] The control unit may delete elements of the time domain resource allocation information corresponding to downlink channels that overlap with uplink symbols from among the plurality of downlink channels. With this configuration, when multiple PDSCHs / PUSCHs are scheduled by one DCI, the terminal 20 can determine a TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit feedback information to the base station 10.

[0140] The control unit may delete elements of the time domain resource allocation information corresponding to the first downlink channel, the last downlink channel, and the penultimate downlink channel that overlap with an uplink symbol among the plurality of downlink channels. With this configuration, when a plurality of PDSCHs / PUSCHs are scheduled by one DCI, the terminal 20 can determine a TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit feedback information to the base station 10.

[0141] When mapping the feedback information to the channel candidates corresponding to values included in elements of the time domain resource allocation information, the control unit may assume the same number of bits of the feedback information among the channel candidates. With this configuration, when multiple PDSCHs / PUSCHs are scheduled by one DCI, the terminal 20 can determine a TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit the feedback information to the base station 10.

[0142] When mapping the feedback information to one or more channels that are candidates for the channel corresponding to the last value included in the element of the time domain resource allocation information, the control unit may assume the same number of bits of the feedback information among the candidate channels. With this configuration, when multiple PDSCHs / PUSCHs are scheduled by one DCI, the terminal 20 can determine a TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit the feedback information to the base station 10.

[0143] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures: a receiving procedure of receiving, from a base station, single control information and multiple downlink channels scheduled by the single control information; a control procedure of determining a codebook for feedback information for the multiple downlink channels based on time domain resource allocation information and determining feedback information for the multiple channels based on the codebook; a transmitting procedure of transmitting the feedback information for the multiple channels to the base station; and a procedure of determining the time domain resource allocation information based on whether the multiple downlink channels overlap with an uplink symbol.

[0144] With the above configuration, when multiple PDSCHs / PUSCHs are scheduled by one DCI, terminal 20 can determine the TDRA table and the number of HARQ-ACK bits in consideration of overlap with TDD-UL / DL, and transmit feedback information to base station 10. In other words, a technique is provided that enables appropriate transmission of feedback information when multiple PDSCHs are scheduled by one control information.

[0145] (Hardware configuration) The block diagrams (FIGS. 11 and 12) 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.

[0146] 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, allocation, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0147] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0148] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

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

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

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

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

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

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

[0155] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

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

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

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

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

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

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

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

[0163] The information, signals, etc. 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.

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

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

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

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

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

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

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

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

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

[0173] In this disclosure, terms such as "base station (BS)," "radio base station," "base station," "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.

[0174] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of a base station and / or base station subsystem that provides communication service within this coverage.

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

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

[0177] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the mobile body itself. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0178] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between a plurality of terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0179] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.

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

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

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

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

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

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

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

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

[0188] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

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

[0192] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe. Furthermore, one slot may be called a unit time. The unit time may differ for each cell depending on the numerology.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0209] In the present disclosure, TDRA is an example of time domain resource allocation information, a row of TDRA is an example of an element of time domain resource allocation information, and SLIV is an example of a value included in an element of time domain resource allocation information.

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

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

Claims

1. A receiver that receives single control information for scheduling a plurality of downlink channels and at least one of the plurality of downlink channels from a base station; a control unit that determines HARQ-ACK information for the plurality of downlink channels; a transmitter that transmits the HARQ-ACK information to the base station; The receiving unit not receiving a downlink channel that overlaps with an uplink symbol among the plurality of downlink channels; The control unit Assuming that at least one of the plurality of downlink channels does not overlap with an uplink symbol, In determining the codebook for the HARQ-ACK information, excluding TDRAs (Time Domain Resource Allocations) corresponding to the plurality of downlink channels that overlap with uplink symbols; A terminal that assumes a maximum number of transport blocks that can be scheduled for each of the plurality of downlink channels.

2. A communication system having a terminal and a base station, The terminal a receiving unit that receives, from the base station, single control information for scheduling a plurality of downlink channels and at least one of the plurality of downlink channels; a control unit that determines HARQ-ACK information for the plurality of downlink channels; a transmitter that transmits the HARQ-ACK information to the base station; The receiving unit not receiving a downlink channel that overlaps with an uplink symbol among the plurality of downlink channels; The control unit Assuming that at least one of the plurality of downlink channels does not overlap with an uplink symbol, In determining the codebook for the HARQ-ACK information, excluding TDRAs (Time Domain Resource Allocations) corresponding to the plurality of downlink channels that overlap with uplink symbols; A maximum number of transport blocks that can be scheduled is assumed for each of the plurality of downlink channels; The base station a transmitter that transmits the single control information and at least one of the plurality of downlink channels to the terminal; a receiving unit that receives HARQ-ACK information for the plurality of downlink channels from the terminal.

3. A method of receiving, from a base station, single control information for scheduling a plurality of downlink channels and at least one of the plurality of downlink channels; determining HARQ-ACK information for the plurality of downlink channels; transmitting the HARQ-ACK information to the base station; a step of not receiving a downlink channel that overlaps with an uplink symbol among the plurality of downlink channels; assuming that at least one of the plurality of downlink channels does not overlap with an uplink symbol; In determining the codebook for the HARQ-ACK information, excluding TDRAs (Time Domain Resource Allocations) corresponding to the plurality of downlink channels that overlap with uplink symbols; and a procedure for estimating the maximum number of transport blocks that can be scheduled for each of the plurality of downlink channels.

Images