Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present disclosure includes: a control unit for determining, when a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information with respect to a multicast physical downlink shared channel (PDSCH) overlaps with an uplink channel in a time domain, at least one channel of the PUCCH and the uplink channel; and a transmission unit for transmitting this channel. According to the one embodiment of the present disclosure, HARQ-ACK for multicast downlink data can be appropriately processed.

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. law, basis earth Stations and systems Regarding. [Background technology]

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). In addition, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0005] In future wireless communication systems (e.g., NR), it is expected that multiple user terminals (User Equipment (UE)) will communicate in an ultra-high density and high traffic environment.

[0006] In NR, in such an environment, it is assumed that multiple UEs will receive downlink data using multicast.

[0007] However, in the NR specifications to date, the transmission of hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) for multicast downlink data from a UE has not been sufficiently considered. If HARQ-ACK is not processed appropriately, there is a risk of degradation in system performance, such as a decrease in throughput.

[0008] Therefore, the present disclosure relates to a terminal and a wireless communication method that appropriately process HARQ-ACK for multicast downlink data. law, basis earth Stations and systems One of the aims is to provide [Means for solving the problem]

[0009] A terminal according to one embodiment of the present disclosure includes: a receiving unit that receives a feedback setting based only on a negative acknowledgement (NACK) of a hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) corresponding to a multicast physical downlink shared channel (PDSCH); and a control unit that controls transmission of the HARQ-ACK multiplexed on a first physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) when the feedback based only on the NACK is set and the first physical uplink control channel (PUCCH) for transmitting the HARQ-ACK overlaps with the second PUCCH or the PUSCH in a time domain. When the first PUCCH overlaps with the second PUCCH or the PUSCH, the control unit multiplexes an ACK for the PDSCH that has been successfully decoded onto the second PUCCH or the PUSCH according to a feedback setting based on an ACK / NACK rather than a feedback setting based on only the NACK. do. Effect of the Invention

[0010] According to one aspect of the present disclosure, HARQ-ACK for multicast downlink data can be appropriately processed. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing an example of a PTM transmission method 1. [Diagram 2] FIG. 2 is a diagram showing an example of the PTM transmission method 2. [Diagram 3] FIG. 3 is a diagram showing an example of collision between a PUCCH and a PUSCH corresponding to a multicast PDSCH according to the first embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of collision between a PUCCH corresponding to a multicast PDSCH and a UL channel according to the second embodiment. [Diagram 5] 5A to 5C are diagrams illustrating an example of a collision between a PUCCH corresponding to a unicast PDSCH and a PUCCH corresponding to a multicast PDSCH according to the third embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 7]FIG. 7 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] (PUCCH format) In future wireless communication systems (e.g., Rel. 15 and later, 5G, NR, etc.), configurations (formats, also called PUCCH formats (PFs)) for uplink control channels (e.g., PUCCHs) used to transmit uplink control information (UCI) are under consideration. For example, in Rel. 15 NR, support for five types of PFs 0 to 4 is under consideration. Note that the names of the PFs shown below are merely examples, and different names may be used.

[0013] For example, PF0 and PF1 are PFs used for transmitting UCI of up to 2 bits. For example, UCI may be at least one of delivery acknowledgement information (also called hybrid automatic repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgement (ACK) or negative-acknowledgement (NACK), etc.) and scheduling request (SR). PF0 can be assigned to 1 or 2 symbols, and is therefore also called short PUCCH or sequence-based short PUCCH, etc. On the other hand, PF1 can be assigned to 4 to 14 symbols, and is therefore also called long PUCCH, etc. PF0 may transmit a sequence obtained by cyclic shifting a base sequence using a cyclic shift based on at least one of an initial cyclic shift (CS) index, a UCI value, a slot number, and a symbol number. In PF1, multiple user terminals may be code division multiplexed (CDM) within the same physical resource block (PRB) by time domain block spreading using at least one of CS and time domain (TD)-orthogonal cover code (OCC).

[0014] PF2-4 are PFs used for transmitting UCI of more than 2 bits (e.g., Channel State Information (CSI) or at least one of CSI, HARQ-ACK, and SR). PF2 can be allocated to 1 or 2 symbols, and is therefore also called a short PUCCH, etc. Meanwhile, PF3 and PF4 can be allocated to 4-14 symbols, and are therefore also called long PUCCH, etc. In PF4, multiple user terminals may be CDM-multiplexed using (frequency domain (FD)-OCC) block spreading before DFT.

[0015] For PF1, PF3, and PF4, intra-slot frequency hopping may be applied. symb Then, the length before frequency hopping (first hop) is floor(N symb / 2), and the length after frequency hopping (second hop) is ceil(N symb / 2).

[0016] The waveforms of PF0, PF1, and PF2 may be Cyclic Prefix (CP)-Orthogonal Frequency Division Multiplexing (OFDM). The waveforms of PF3 and PF4 may be Discrete Fourier Transform (DFT)-spread(s)-OFDM.

[0017] The allocation of resources (e.g., PUCCH resources) used for transmitting the uplink control channel is performed using higher layer signaling and / or downlink control information (DCI). Here, the higher layer signaling may be at least one of RRC (Radio Resource Control) signaling, system information (e.g., at least one of RMSI: Remaining Minimum System Information, OSI: Other System Information, MIB: Master Information Block, and SIB: System Information Block), and broadcast information (PBCH: Physical Broadcast Channel).

[0018] In addition, in NR, the number of symbols assigned to PUCCH (which may be called PUCCH assigned symbols, PUCCH symbols, etc.) can be determined as slot-specific, cell-specific, or user terminal-specific, or a combination of these. Since it is expected that the communication distance (coverage) will increase as the number of PUCCH symbols increases, it is assumed that the number of symbols will be increased for user terminals located farther away from a base station (e.g., eNB, gNB).

[0019] (HARQ-ACK feedback) In NR, a mechanism is being considered in which a user equipment (UE: User Equipment) feeds back (also referred to as report or transmission, etc.) delivery acknowledgement information (also referred to as Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK), ACKnowledge / Non-ACK (ACK / NACK), HARQ-ACK information, A / N, etc.) for a downlink shared channel (also referred to as Physical Downlink Shared Channel (PDSCH), etc.).

[0020] For example, in NR Rel.15, the value of a predetermined field in DCI (e.g., DCI format 1_0 or 1_1) used for scheduling a PDSCH indicates the feedback timing of HARQ-ACK for the PDSCH. When a UE transmits a HARQ-ACK for a PDSCH received in slot #n in slot #n+k, the value of the predetermined field may be mapped to the value of k. The predetermined field is called, for example, a PDSCH-to-HARQ_feedback timing indicator field.

[0021] Also, in NR Rel.15, a PUCCH resource used for feedback of HARQ-ACK for a PDSCH is determined based on a value of a predetermined field in DCI (e.g., DCI format 1_0 or 1_1) used for scheduling the PDSCH. The predetermined field may be called, for example, a PUCCH resource indicator (PRI) field, an ACK / NACK resource indicator (ARI) field, etc. The value of the predetermined field may be called, for example, a PRI, an ARI, etc.

[0022] The PUCCH resource mapped to each value of the predetermined field may be configured in advance in the UE by a higher layer parameter (e.g., ResourceList in PUCCH-ResourceSet). Also, the PUCCH resource may be configured in the UE for each set (PUCCH resource set) including one or more PUCCH resources.

[0023] Also, in NR Rel.15, it is considered that a UE will not expect to transmit more than one uplink control channel (Physical Uplink Control Channel (PUCCH)) with HARQ-ACK in a single slot.

[0024] Specifically, in NR Rel.15, one or more HARQ-ACKs in a single slot may be mapped to a single HARQ-ACK codebook, and the HARQ-ACK codebook may be transmitted on the PUCCH resource indicated by the last DCI.

[0025] Here, the HARQ-ACK codebook may be configured to include bits for HARQ-ACK in at least one unit of a time domain (e.g., slot), a frequency domain (e.g., component carrier (CC)), a spatial domain (e.g., layer), a transport block (TB), and a group of code blocks constituting a TB (code block group (CBG)). Note that a CC is also called a cell, a serving cell, a carrier, etc. Also, the bit is also called an HARQ-ACK bit, HARQ-ACK information, or an HARQ-ACK information bit, etc.

[0026] The HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), a codebook, a HARQ codebook, a HARQ-ACK size, etc.

[0027] The number of bits (size) included in the HARQ-ACK codebook, etc. may be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a type-1 HARQ-ACK codebook, a semi-static codebook, etc. A dynamic HARQ-ACK codebook is also called a type-2 HARQ-ACK codebook, a dynamic codebook, etc.

[0028] Whether to use the type-1 HARQ-ACK codebook or the type-2 HARQ-ACK codebook may be configured in the UE by a higher layer parameter (eg, pdsch-HARQ-ACK-Codebook).

[0029] In the case of a type 1 HARQ-ACK codebook, the UE may feed back HARQ-ACK bits corresponding to a predetermined range (e.g., a range set based on higher layer parameters) regardless of whether PDSCH is scheduled or not.

[0030] The predetermined range may be determined based on at least one of a predetermined time period (e.g., a set of a predetermined number of candidate occasions for receiving PDSCH, or a predetermined number of monitoring occasions for PDCCH), the number of CCs configured or activated in the UE, the number of TBs (number of layers or rank), the number of CBGs per TB, and whether spatial bundling is applied. The predetermined range is also called a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc.

[0031] In the case of the type 1 HARQ-ACK codebook, the UE feeds back a NACK bit within a predetermined range even if there is no PDSCH scheduled for the UE. Therefore, when the type 1 HARQ-ACK codebook is used, it is expected that the number of HARQ-ACK bits to be fed back increases.

[0032] Meanwhile, in the case of a type-2 HARQ-ACK codebook, the UE may feed back a HARQ-ACK bit for a scheduled PDSCH within the predetermined range.

[0033] Specifically, the UE may determine the number of bits of the type-2 HARQ-ACK codebook based on a predetermined field in the DCI (e.g., a Downlink Assignment Indicator (Index) (DAI) field). The DAI field may be split into a counter DAI (cDAI) and a total DAI (tDAI).

[0034] The counter DAI may indicate the counter value of downlink transmissions (PDSCH, data, TB) scheduled within a predetermined period. For example, the counter DAI in a DCI that schedules data within the predetermined period may indicate the number counted in the frequency domain (e.g., CC index order) first and then in the time domain (time index order) within the predetermined period.

[0035] The total DAI may indicate the sum (total number) of data scheduled within a given period. For example, the total DAI in a DCI that schedules data at a given time unit (e.g., PDCCH monitoring opportunity) within the given period may indicate the total number of data scheduled up to the given time unit (also called a point, timing, etc.) within the given period.

[0036] Also, if the UE is not configured with code block group (CBG)-based transmission (CBG-based HARQ-ACK codebook determination) by the higher layer parameter (PDSCH code block group transmission information element, PDSCH-CodeBlockGroupTransmission), the UE assumes transport block (TB)-based transmission (TB-based HARQ-ACK codebook determination). That is, the UE generates HARQ-ACK information bits for each TB.

[0037] When the UE is provided with higher layer parameters of the PDSCH code block group transmission information element for the serving cell (Component Carrier: CC), the UE receives a PDSCH including multiple CBGs for one TB. The PDSCH code block group transmission information element includes the maximum number of CBGs in one TB (maxCodeBlockGroupsPerTransportBlock). The UE generates HARQ-ACK information bits for each of the multiple CBGs for the TB reception of the serving cell, and generates a HARQ-ACK codebook including the maximum number of HARQ-ACK information bits for the CBG.

[0038] The UE may transmit one or more HARQ-ACK bits determined (generated) based on the above-mentioned Type 1 or Type 2 HARQ-ACK codebook using at least one of an uplink control channel (Physical Uplink Control Channel (PUCCH)) and an uplink shared channel (Physical Uplink Shared Channel (PUSCH)).

[0039] In Rel.15, DCI format 0_1 ​​(UL grant) used for scheduling PUSCH includes a 1 or 2-bit first downlink assignment index (first DAI) field and a 0 or 2-bit second downlink assignment index (second DAI) field.

[0040] The first DAI for a semi-static HARQ-ACK codebook (type 1 HARQ-ACK codebook) is 1 bit. The first DAI for a dynamic HARQ-ACK codebook (type 2 HARQ-ACK codebook) is 2 bits.

[0041] The second DAI for a dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks is 2 bits. Otherwise, the second DAI is 0 bits.

[0042] When a UE configured with a quasi-static HARQ-ACK codebook multiplexes HARQ-ACK information in a PUSCH transmission scheduled by DCI format 0_1, the value V T-DAI,m UL If DAI is 1, the UE may generate the HARQ-ACK codebook using the first DAI instead of the total DAI.

[0043] When a UE configured with a dynamic HARQ-ACK codebook multiplexes HARQ-ACK information in a PUSCH transmission scheduled by DCI format 0_1, the UE multiplexes the HARQ-ACK information in a PUSCH transmission scheduled by DCI format 0_1 ​​by setting the value V T-DAI,m UL Based on this, the HARQ-ACK codebook may be generated using the first DAI instead of the total DAI.

[0044] When the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook are used, DCI format 0_1 ​​includes a first DAI corresponding to the first HARQ-ACK sub-codebook and a second DAI corresponding to the second HARQ-ACK sub-codebook.

[0045] When the semi-static HARQ-ACK codebook is configured, the UE receives a 1-bit UL DAI (first DAI) in the UL grant for scheduling the PUSCH. If the value of the UL DAI is 1 and the PUCCH for reporting the HARQ-ACK and the PUSCH collide in at least one symbol, the UE piggybacks the HARQ-ACK on the PUSCH (UCI on PUSCH, HARQ-ACK on PUSCH). If the value of the UL DAI is 1, the base station may assume that the HARQ-ACK is piggybacked on the PUSCH regardless of whether the PUCCH and the PUSCH collide, and may perform rate matching of the UL-SCH carried on the PUSCH. Even if the UE fails to detect the PDCCH corresponding to the HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE may transmit a NACK on the PUSCH for rate matching.

[0046] When the dynamic HARQ-ACK codebook is configured, the UE receives a 2-bit UL DAI (first DAI) in the UL grant for scheduling the PUSCH. This UL DAI indicates the number of HARQ-ACKs piggybacked on the PUSCH (total DAI). If the PUCCH for reporting the HARQ-ACKs and the PUSCH collide in at least one symbol, the UE piggybacks the number of HARQ-ACKs indicated in the UL DAI on the PUSCH. Regardless of whether the PUCCH and the PUSCH collide, the base station may perform rate matching of the UL-SCH carried on the PUSCH, assuming that the number of HARQ-ACKs indicated in the UL DAI are piggybacked on the PUSCH. Even if the UE fails to detect the PDCCH corresponding to the HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE may transmit the number of NACKs indicated in the UL DAI on the PUSCH for rate matching.

[0047] When the CBG-based HARQ-ACK codebook is configured, the UE receives a 2-bit UL DAI (first DAI) and a 2-bit UL DAI (second DAI) in an UL grant for scheduling a PUSCH. The first DAI indicates the number of first HARQ-ACK sub-codebooks piggybacked on the PUSCH. The second DAI indicates the number of second HARQ-ACK sub-codebooks piggybacked on the PUSCH. When a PUCCH for HARQ-ACK reporting and a PUSCH collide in at least one symbol, the UE piggybacks the first HARQ-ACK sub-codebooks as many as indicated by the first DAI and the second HARQ-ACK sub-codebooks as many as indicated by the second DAI on the PUSCH. The base station may perform rate matching of the UL-SCH carried on the PUSCH, assuming that the HARQ-ACKs as many as indicated by the first DAI and the second DAI are piggybacked on the PUSCH, regardless of whether the PUCCH and the PUSCH collide. If the UE fails to detect a PDCCH corresponding to the HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE may still transmit the number of NACKs indicated in the first DAI and the second DAI on the PUSCH for rate matching.

[0048] In this way, the UE determines whether to piggyback a HARQ-ACK on a PUSCH based on the UL DAI in the UL grant for scheduling the PUSCH.

[0049] (NR Multicast / Broadcast) In NR up to Rel.16, the transmission of at least one of a signal and a channel (hereinafter referred to as a signal / channel) from a network to a UE is basically unicast transmission. In this case, it is assumed that each UE receives the same downlink (DL) data signal / channel (e.g., a downlink shared channel (PDSCH)) transmitted from the network to multiple UEs using multiple reception opportunities (reception occasions) corresponding to multiple beams (or panels) of the network.

[0050] In addition, in an ultra-high density and high traffic environment where many UEs are geographically concentrated (e.g., stadiums, etc.), it is assumed that multiple UEs will receive the same signal / channel simultaneously. In such a case, if multiple UEs are present in the same area and each UE receives the same signal / channel by unicast, it is considered that the reliability of communication can be ensured, but the efficiency of resource utilization will decrease.

[0051] A group scheduling mechanism is being studied to enable multicast / broadcast services (MBS) to be received by multiple UEs.

[0052] For example, it is being considered to schedule a multicast PDSCH using one or more DCIs, which may increase the size of the DCI (payload size, overhead).

[0053] In a Point-to-Point (PTP) transmission (distribution method), a RAN node (e.g., a base station) transmits separate copies of MBS data packets over the air to individual UEs. In a Point-to-Multipoint (PTM) transmission (distribution method), a RAN node (e.g., a base station) transmits a single copy of an MBS data packet over the air to a set of UEs. A PTP transmission may also be referred to as a unicast transmission.

[0054] It is considered that PTP transmission uses a UE-specific PDCCH to schedule UE-specific PDSCH for multiple RRC connected UEs (RRC_CONNECTED UEs), the UE-specific PDCCH has a cyclic redundancy check (CRC) scrambled with a UE-specific radio network temporary identifier (RNTI) (e.g., C-RNTI), and the UE-specific PDSCH is scrambled with the same UE-specific RNTI.

[0055] It is considered that PTM transmission method 1 uses a group-common PDCCH to schedule a group-common PDSCH for multiple RRC connected UEs in the same MBS group, the group-common PDCCH has a CRC scrambled with a group-common RNTI, and the group-common PDSCH is scrambled using the same group-common RNTI (Figure 1).

[0056] It is being considered that PTM transmission method 2 uses a UE-specific PDCCH to schedule a group-common PDSCH for multiple RRC connected UEs in the same MBS group, the UE-specific PDCCH has a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI), and the group-common PDSCH is scrambled using the group-common RNTI (Figure 2).

[0057] Here, the UE-specific PDCCH / PDSCH can be identified by the target UE but cannot be identified by other UEs in the same MBS group, whereas the group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group.

[0058] In addition, HARQ feedback is being considered to improve the reliability of MBS.

[0059] For an RRC connected UE receiving multicast, at least the PTM transmission scheme 1 may support at least one of the following feedback methods 1 and 2.

[0060] [Feedback method 1] HARQ-ACK feedback based on ACK / NACK for multicast (ACK / NACK based HARQ-ACK feedback, ACK / NACK based PUCCH, ACK / NACK transmission, ACK / NACK feedback, HARQ-ACK information includes ACK or NACK) A UE that successfully decodes the PDSCH transmits an ACK, whereas a UE that fails to decode the PDSCH transmits a NACK.

[0061] [Feedback method 2] HARQ-ACK feedback based only on NACK for multicast (NACK-only based HARQ-ACK feedback, NACK-only based PUCCH, NACK-only transmission, NACK-only feedback, HARQ-ACK information includes only NACK) A UE that successfully decodes the PDSCH does not send an ACK, and a UE that fails to decode the PDSCH sends a NACK.

[0062] However, it is unclear how the UE operates when the PUCCH including the HARQ-ACK corresponding to the multicast PDSCH collides with another UL channel in the time domain. For example, the following problems 1 to 3 may occur.

[0063] [Question 1] When a PUCCH including a HARQ-ACK corresponding to a multicast PDSCH is transmitted using a PUCCH resource shared (common) among multiple UEs, the UE behavior when a PUSCH exists in a UE that collides with the PUCCH in the time domain (Figure 3) is unclear.

[0064] In this case, it is not clear whether the UE will use shared (common) PUCCH resources or PUSCH. This UE behavior affects the base station operation.

[0065] [Question 2] When NACK-only feedback is configured / indicated for a PUCCH containing a HARQ-ACK corresponding to a multicast PDSCH, the UE behavior in the case where a UL channel exists that conflicts in the time domain with the PUCCH resource (Figure 4) is unclear.

[0066] In this case, it is not clear whether the UE transmits a HARQ-ACK. The base station does not know whether a NACK is transmitted. In this case, the value of the UL DAI is not clear.

[0067] [Problem 3] The UE operation regarding the collision between the HARQ-ACK corresponding to the unicast PDSCH and the HARQ-ACK corresponding to the multicast PDSCH is not clear. This collision may be at least one of the following Cases 1 to 3. [[Case 1]]PUCCH A including the HARQ-ACK corresponding to the unicast PDSCH and PUCCH B including the HARQ-ACK corresponding to the multicast PDSCH collide (Fig. 5A). [[Case 2]]PUCCH A including the HARQ-ACK corresponding to the unicast PDSCH and the PUSCH collide, and PUCCH B including the HARQ-ACK corresponding to the multicast PDSCH and the same PUSCH collide. PUCCH A and PUCCH B do not collide (Fig. 5B). [[Case 3]]PUCCH A including the HARQ-ACK corresponding to the unicast PDSCH and PUCCH C collide, and PUCCH B including the HARQ-ACK corresponding to the multicast PDSCH and PUCCH C collide. PUCCH A and PUCCH B do not collide (Fig. 5C).

[0068] If the UE operation when the PUCCH including the HARQ-ACK corresponding to the multicast PDSCH collides with another UL channel in the time domain is not clear, there is a risk of causing a throughput decrease or the like.

[0069] Therefore, the inventors conceived a method for resolving the overlap (collision) between the multicast PDSCH and other UL channels.

[0070] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to the respective embodiments may be applied individually or in combination.

[0071] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0072] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read as interchangeable.

[0073] In this disclosure, the words use, determine, apply, and select may be interpreted interchangeably.

[0074] In this disclosure, link, associate, correspond, and map may be read as interchangeable. In this disclosure, allocate, assign, monitor, and map may be read as interchangeable.

[0075] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be read as interchangeable.

[0076] The MAC signaling may be, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0077] In the present disclosure, MAC CE and activation / deactivation command may be read as interchangeable.

[0078] In the present disclosure, PUCCH, PUSCH, repetition, and transmission occasion may be read as interchangeable.

[0079] In the present disclosure, the terms "multicast," "groupcast," "broadcast," and "MBS" may be interchangeable. In the present disclosure, the terms "multicast PDSCH" and "PDSCH scrambled by a group-common RNTI" may be interchangeable.

[0080] In the present disclosure, HARQ-ACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, NACK, and UCI may be interpreted as interchangeable.

[0081] In the present disclosure, specific, dedicated, UE specific, and UE individual may be read as interchangeable.

[0082] In the present disclosure, common, shared, group-common, UE common, and UE shared may be read as interchangeable.

[0083] In the present disclosure, a UE-specific DCI and a DCI having a CEC scrambled by a UE-specific RNTI may be interpreted as interchangeable. The UE-specific RNTI may be, for example, a C-RNTI.

[0084] In the present disclosure, a UE common DCI and a DCI having a CEC scrambled by a UE common RNTI may be interpreted as interchangeable. The UE common RNTI may be, for example, a multicast-RNTI.

[0085] In this disclosure, the cast type of a PDSCH may indicate whether the PDSCH is unicast or multicast.

[0086] In the present disclosure, mapping HARQ-ACK information to PUSCH, multiplexing HARQ-ACK information and data (UL-SCH) on PUSCH, and transmitting HARQ-ACK information on PUSCH may be interchangeable. In the present disclosure, mapping HARQ-ACK information to PUCCH, multiplexing HARQ-ACK information and other UCI on PUCCH, and transmitting HARQ-ACK information on PUCCH may be interchangeable.

[0087] In the present disclosure, puncturing the PUSCH with HARQ-ACK information and overwriting the HARQ-ACK information onto the PUSCH after mapping data (uplink (UL)-shared channel (SCH)) onto the PUSCH may be interpreted as interchangeable.

[0088] (Wireless communication method) When the PUCCH for HARQ-ACK transmission corresponding to the multicast PDSCH and another UL channel overlap at least in the time domain, the UE performs overlap resolution based on a condition.

[0089] <First embodiment> For a PUCCH including a HARQ-ACK corresponding to a multicast PDSCH, when the PUCCH resource is shared (common) among multiple UEs, if a PUSCH exists in a UE that conflicts with the PUCCH in the time domain (Figure 3, problem 1), the UE may follow at least one of the following aspects 1-1 to 1-8.

[0090] [Aspect 1-1] The UE maps the HARQ-ACK to its PUSCH (multiplexes the HARQ-ACK and data (UL-SCH) in the PUSCH) and does not transmit its PUCCH.

[0091] [Aspect 1-2] The UE does not map the HARQ-ACK to the PUSCH and transmits the PUCCH. The UE may or may not transmit the PUSCH.

[0092] [Aspect 1-3] The UE maps the HARQ-ACK to the PUSCH and transmits the PUCCH at the same time.

[0093] [Aspect 1-4] The UE does not map the HARQ-ACK to the PUSCH, does not transmit the PUCCH, and may or may not transmit the PUSCH.

[0094] [Aspect 1-5] The UE uses (decides / applies / selects) one of the aspects 1-1 to 1-4 based on whether the HARQ-ACK transmission method is ACK / NACK feedback or NACK-only feedback.

[0095] [Aspect 1-6] The UE uses (decides / applies / selects) one of the aspects 1-1 to 1-4 based on the number of bits of its HARQ-ACK.

[0096] [Aspect 1-7] The UE uses (decides / applies / selects) one of the aspects 1-1 to 1-4 based on the PUCCH format of its PUCCH.

[0097] [Aspect 1-8] The UE uses (decides / applies / selects) one of aspects 1-1 to 1-4 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0098] For a PUCCH including a HARQ-ACK corresponding to a multicast PDSCH, when the PUCCH resource is UE-specific and a PUSCH exists that collides with the PUCCH in the time domain, the operation may be the same as the operation (Rel. 15 / 16) when a PUSCH exists that collides with a PUCCH including a HARQ-ACK corresponding to a unicast PDSCH in the time domain.

[0099] According to this embodiment, the UE operation is clear. When mapping HARQ-ACK to PUSCH, the operation is the same as that of unicast PDSCH, so the UE operation can be simplified. When transmitting HARQ-ACK using PUCCH, the base station operation in the common PUCCH resource is not required to be changed.

[0100] <Second embodiment> In the case where NACK-only feedback is configured / indicated for a PUCCH including a HARQ-ACK corresponding to a multicast PDSCH, in the case where a UL channel exists in a UE that conflicts in the time domain with the PUCCH resource (FIG. 4, problem 2), the UE may follow at least one of the following aspects 2a and 2b.

[0101] Aspect 2a If the UL channel that collides in the time domain with the PUCCH that includes the HARQ-ACK corresponding to the multicast PDSCH is a PUSCH, the UE may follow at least one of the following aspects 2a-1 to 2a-12.

[0102] [Aspect 2a-1] The UE maps the HARQ-ACK to its PUSCH (multiplexes the HARQ-ACK and data (UL-SCH) in the PUSCH) and does not transmit its PUCCH.

[0103] [Aspect 2a-2] The UE does not map the HARQ-ACK to the PUSCH and transmits the PUCCH. The UE may or may not transmit the PUSCH.

[0104] [Aspect 2a-3] The UE maps the HARQ-ACK to the PUSCH and transmits the PUCCH at the same time.

[0105] [Aspect 2a-4] The UE does not map the HARQ-ACK to the PUSCH, does not transmit the PUCCH, and may or may not transmit the PUSCH.

[0106] [Aspect 2a-5] The UE uses (decides / applies / selects) one of the aspects 2a-1 to 2a-4 depending on whether the PDSCH is successfully received / decoded (NACK is generated or not).

[0107] If the reception / decoding of the PDSCH is successful, the UE may use aspect 2a-4. If the reception / decoding of the PDSCH is unsuccessful, the UE may use aspect 2a-1. In this case, the UE may perform NACK-only feedback on the PUSCH and always send data.

[0108] If the reception / decoding of the PDSCH is successful, the UE may use the aspect 2a-4. If the reception / decoding of the PDSCH is unsuccessful, the UE may use the aspect 2a-2. In this case, the NACK-only feedback operation is not affected by collisions.

[0109] [Aspect 2a-6] The UE uses (decides / applies / selects) one of the aspects 2a-1 to 2a-3 based on the number of bits of its HARQ-ACK.

[0110] When the HARQ-ACK is up to 2 bits, the UE may use the aspect 2a-1. When the HARQ-ACK is more than 2 bits, the UE may use the aspect 2a-4 (the HARQ-ACK does not need to be mapped to the PUSCH). Here, when the HARQ-ACK is up to 2 bits, the base station can know the mapping of the UL-SCH by puncturing the PUSCH and mapping the HARQ-ACK to the PUSCH, even if it does not know whether the HARQ-ACK is mapped.

[0111] [Aspect 2a-7] The UE uses (decides / applies / selects) one of the aspects 2a-1 to 2a-4 based on the PUCCH format of its PUCCH.

[0112] [Aspect 2a-8] The UE uses (decides / applies / selects) one of aspects 2a-1 to 2a-4 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0113] [Aspect 2a-9] When the HARQ-ACK is mapped to the PUSCH, the mapping (multiplexing) method is different from the method of mapping the HARQ-ACK of the unicast PDSCH to the PUSCH.

[0114] For example, the UE may puncture the PUSCH regardless of the number of HARQ-ACK bits (after mapping the UL-SCH to the PUSCH, the HARQ-ACK may be overwritten onto the PUSCH). In this case, the mapping position of the UL-SCH does not depend on whether the HARQ-ACK is mapped or not.

[0115] [Aspect 2a-10] The UL DAI in the UL grant (DCI) that schedules the PUSCH may be a value that assumes that the HARQ-ACK is mapped to the PUSCH. The UL DAI in the UL grant (DCI) that schedules the PUSCH may be a value that assumes that the HARQ-ACK is not mapped to the PUSCH.

[0116] The UE may process the HARQ-ACK based on the UL DAI. The UE may map the HARQ-ACK to a PUSCH based on the UL DAI in the UL grant (DCI) that schedules the PUSCH. The UE may not map the HARQ-ACK to a PUSCH based on the UL DAI in the UL grant (DCI) that schedules the PUSCH.

[0117] It may be specified that the UE does not expect to receive DCI (DL assignment) that schedules a multicast PDSCH corresponding to a HARQ-ACK to be transmitted in a PUCCH that overlaps (in the time domain) with the PUSCH after the UL grant. It may be specified that the UE does not expect to receive DCI indicating a HARQ-ACK that overlaps (in the time domain) with the PUSCH after the UL grant.

[0118] [Aspect 2a-11] The UE may transmit an ACK if the PDSCH is successfully received / decoded and there is an opportunity to transmit a HARQ-ACK. For example, if the UE decides to transmit a PUSCH that collides with a PUCCH (e.g., aspect 2a-1), the UE may map an ACK for a multicast PDSCH to the PUSCH.

[0119] [Aspect 2a-12] If the UE successfully receives / decodes the PDSCH and transmits a HARQ-ACK (has an opportunity to transmit a HARQ-ACK), the UE may transmit the ACK regardless of the setting / indication of the NACK-only feedback. For example, if the UE decides to transmit a PUSCH that collides with a PUCCH (e.g., aspect 2a-1), the UE may map the ACK for the multicast PDSCH to the PUSCH regardless of the setting / indication of the NACK-only feedback for the multicast PDSCH.

[0120] In the example 2a, when HARQ-ACK is mapped to PUSCH, the operation is the same as that of unicast PDSCH, and the UE configuration can be simplified. In the example 2a, when HARQ-ACK is up to 2 bits, even when NACK-only feedback from multiple UEs is multiplexed, there is no need to change the base station operation. In the example 2a, when HARQ-ACK is mapped to PUCCH, there is no need to change the UE operation related to NACK-only feedback.

[0121] Aspect 2b If a UL channel that collides in the time domain with PUCCH X that includes a HARQ-ACK corresponding to a multicast PDSCH is PUCCH Y, the UE may follow at least one of the following aspects 2b-1 to 2b-9. PUCCH Y may include at least one of a scheduling request (SR) and channel state information (CSI).

[0122] [Aspect 2b-1] The UE multiplexes PUCCH X and PUCCH Y into at least one of PUCCH X, PUCCH Y, and another PUCCH Z. The UE may map UCI (e.g., HARQ-ACK) of PUCCH X and UCI (e.g., SR / CSI) of PUCCH Y into at least one of PUCCH X, PUCCH Y, and PUCCH Z. Of PUCCH X, PUCCH Y, and PUCCH Z, the PUCCH to which UCI (HARQ-ACK) is mapped may be specified in the specification or may be the PUCCH associated with a higher priority. The UE may not transmit one or both of PUCCH X and PUCCH Y.

[0123] [Aspect 2b-2] The UE transmits one of PUCCH X and PUCCH Y and drops the other. Which of PUCCH X and PUCCH Y is to be transmitted with priority may be specified in the specification. Each of PUCCH X and PUCCH Y may be associated with a priority (the DCI that schedules each of PUCCH X and PUCCH Y may include a priority indicator field). If the priority of PUCCH X is equal to the priority of PUCCH Y, the UE may prioritize one of PUCCH X and PUCCH Y as specified in the specification. If the priority of PUCCH X is different from the priority of PUCCH Y, the UE may prioritize the PUCCH with the higher priority of PUCCH X or PUCCH Y.

[0124] [Aspect 2b-3] The UE does not multiplex PUCCH X and PUCCH Y (maps the UCI for PUCCH X to PUCCH X, and maps the UCI for PUCCH Y to PUCCH Y), and transmits PUCCH X and PUCCH Y (simultaneously).

[0125] [Aspect 2b-4] The UE uses (decides / applies / selects) one of the aspects 2b-1 to 2b-3 depending on whether the PDSCH is successfully received / decoded (NACK is generated or not).

[0126] [Aspect 2b-5] The UE uses (decides / applies / selects) one of the aspects 2b-1 to 2b-3 based on the number of bits of its HARQ-ACK or the total number of bits of UCI for PUCCH X and UCI for PUCCH Y.

[0127] [Aspect 2b-6] The UE uses (decides / applies / selects) one of the aspects 2b-1 to 2b-3 based on the PUCCH format of at least one of PUCCH X and PUCCH Y.

[0128] [Aspect 2b-7] The UE uses (decides / applies / selects) one of aspects 2b-1 to 2b-3 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0129] [Aspect 2b-8] If the UE successfully receives / decodes the PDSCH and has an opportunity to send a HARQ-ACK, it may send an ACK on at least one of PUCCH X, PUCCH Y, and another PUCCH Z. For example, if the UE decides to send PUCCH Y, which collides with PUCCH X, it may map the ACK for the multicast PDSCH to PUCCH Y.

[0130] [Aspect 2b-9] If the UE successfully receives / decodes that PDSCH and has an opportunity to transmit a HARQ-ACK, the UE may transmit the ACK regardless of the configuration / indication of the NACK-only feedback. For example, if the UE decides to transmit a PUCCH Y that collides with PUCCH X, the UE may map the ACK for the multicast PDSCH to PUCCH Y regardless of the configuration / indication of the NACK-only feedback for the multicast PDSCH.

[0131] In embodiment 2b, if sent whenever PDSCH is successfully decoded, there is no impact on the UCI payload size and the PUCCH resources used.

[0132] In example 2b, when only NACK is sent or when one of the PUCCHs is dropped, the UE configuration can be simplified.

[0133] <Third embodiment> For collisions involving HARQ-ACKs corresponding to unicast PDSCHs and HARQ-ACKs corresponding to multicast PDSCHs, the UE may follow at least one of the following aspects 3a to 3c.

[0134] Aspect 3a If PUCCH A including HARQ-ACK A corresponding to a unicast PDSCH and PUCCH B including HARQ-ACK B corresponding to a multicast PDSCH collide in the time domain (FIG. 5A, case 1 of problem 3), the UE may follow at least one of the following aspects 3a-1 to 3a-7.

[0135] [Aspect 3a-1] The UE multiplexes HARQ-ACK A and HARQ-ACK B into at least one of PUCCHs, PUCCH A, PUCCH B, and another PUCCH C. The UE may map HARQ-ACK A and HARQ-ACK B into at least one of PUCCHs, PUCCH A, PUCCH B, and PUCCH C, and transmit at least one of PUCCHs, PUCCH A, PUCCH B, and PUCCH C. Of PUCCH A, PUCCH B, and PUCCH C, the PUCCH to which the HARQ-ACK is mapped may be specified in the specification or may be a PUCCH associated with a higher priority. The UE may not transmit one or both of PUCCH A and PUCCH B.

[0136] [Aspect 3a-2] The UE transmits one of PUCCH A and PUCCH B (HARQ-ACK A and HARQ-ACK B) and drops the other. Which of HARQ-ACK A and HARQ-ACK B is to be transmitted with priority may be specified in the specification. Each of HARQ-ACK A and HARQ-ACK B may be associated with a priority (DCIs that schedule each of PUCCH A and PUCCH B may include a priority indicator field). If the priority of HARQ-ACK A is equal to the priority of PUCCH B, the UE may prioritize one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A is different from the priority of PUCCH B, the UE may prioritize the HARQ-ACK with the higher priority among HARQ-ACK A and HARQ-ACK B.

[0137] [Aspect 3a-3] The UE does not multiplex HARQ-ACK A and HARQ-ACK B (maps HARQ-ACK A to PUCCH A and maps HARQ-ACK B to PUCCH B), and transmits PUCCH A and PUCCH B (simultaneously).

[0138] [Aspect 3a-4] The UE uses (decides / applies / selects) one of aspects 3a-1 to 3a-3 based on the number of bits of each of HARQ-ACK A and HARQ-ACK B or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B).

[0139] [Aspect 3a-5] The UE uses (determines / applies / selects) one of the aspects 3a-1 to 3a-3 based on the PUCCH format of at least one of PUCCH A and PUCCH B.

[0140] [Aspect 3a-6] The UE uses (decides / applies / selects) one of aspects 3a-1 to 3a-3 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0141] [Aspect 3a-7] The UE uses (decides / applies / selects) one of the aspects 3a-1 to 3a-3 based on the HARQ-ACK codebook type.

[0142] In example 3a, communication quality can be maintained or improved when HARQ-ACK A and HARQ-ACK B are multiplexed. In example 3a, UE operation can be simplified when either PUCCH A or PUCCH B is dropped.

[0143] Aspect 3b If PUCCH A including a HARQ-ACK corresponding to a unicast PDSCH collides with a PUSCH in the time domain, and PUCCH B including a HARQ-ACK corresponding to a multicast PDSCH collides with the same PUSCH in the time domain, and PUCCH A and PUCCH B do not collide in the time domain (FIG. 5B, case 2 of problem 3), the UE may follow at least one of the following aspects 3b-1 to 3b-9.

[0144] [Aspect 3b-1] The UE multiplexes HARQ-ACK A and HARQ-ACK B in the PUSCH. The UE maps HARQ-ACK A and HARQ-ACK B to the PUSCH and transmits the PUSCH. The UE may not transmit at least one of PUCCH A and PUCCH B.

[0145] [Aspect 3b-2] The UE drops one of HARQ-ACK A and HARQ-ACK B, maps the other to the PUSCH, and transmits the PUSCH. Which of HARQ-ACK A and HARQ-ACK B is to be transmitted with priority may be specified in the specification. Each of HARQ-ACK A and HARQ-ACK B may be associated with a priority (the DCIs that schedule each of PUCCH A and PUCCH B may include a priority indicator field). If the priority of HARQ-ACK A is equal to the priority of PUCCH B, the UE may prioritize one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A is different from the priority of PUCCH B, the UE may prioritize the HARQ-ACK with the higher priority among HARQ-ACK A and HARQ-ACK B.

[0146] [Aspect 3b-3] The UE does not multiplex HARQ-ACK A and HARQ-ACK B (maps HARQ-ACK A to PUCCH A and maps HARQ-ACK B to PUCCH B), and transmits PUCCH A and PUCCH B and their PUSCH (simultaneously).

[0147] [Aspect 3b-4] The UE does not multiplex HARQ-ACK A and HARQ-ACK B (maps HARQ-ACK A to PUCCH A and maps HARQ-ACK B to PUCCH B), transmits PUCCH A and PUCCH B, and drops the PUSCH.

[0148] [Aspect 3b-5] The UE uses (decides / applies / selects) one of aspects 3b-1 to 3b-4 based on the number of bits of each of HARQ-ACK A and HARQ-ACK B or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B).

[0149] [Aspect 3b-6] The UE uses (determines / applies / selects) one of the aspects 3b-1 to 3b-4 based on the PUCCH format of at least one of PUCCH A and PUCCH B.

[0150] [Aspect 3b-7] The UE uses (decides / applies / selects) one of aspects 3b-1 to 3b-4 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0151] [Aspect 3b-8] The UE uses (decides / applies / selects) one of the aspects 3b-1 to 3b-4 based on the HARQ-ACK codebook type.

[0152] [Aspect 3b-9] The UL DAI in the UL grant (DCI) that schedules the PUSCH is a value corresponding to the HARQ-ACK to be transmitted. For example, in aspect 3b-1, one (one set) UL DAI obtained from both HARQ-ACK A and HARQ-ACK B may be included in the UL grant, or two (two sets) UL DAIs obtained from HARQ-ACK A and HARQ-ACK B, respectively, may be included in the UL grant. The UE may map the HARQ-ACK to the PUSCH based on the UL DAI.

[0153] In example 3b, communication quality can be maintained or improved when HARQ-ACK A and HARQ-ACK B are multiplexed. In example 3b, UE operation can be simplified when any of PUCCH A, PUCCH B, and PUSCH is dropped.

[0154] Aspect 3c If PUCCH A including HARQ-ACK corresponding to a unicast PDSCH and PUCCH C collide in the time domain, and PUCCH B including HARQ-ACK corresponding to a multicast PDSCH and PUCCH C collide in the time domain, and PUCCH A and PUCCH B do not collide in the time domain (FIG. 5C, case 3 of problem 3), the UE may follow at least one of the following aspects 3c-1 to 3c-8.

[0155] [Aspect 3c-1] The UE multiplexes HARQ-ACK A, HARQ-ACK B, and the UCI of PUCCH C, and transmits at least one PUCCH among PUCCH A, PUCCH B, PUCCH C, and another PUCCH D. The UE may map at least two of HARQ-ACK A, HARQ-ACK B, and the UCI of PUCCH C to at least one PUCCH among PUCCH A, PUCCH B, PUCCH C, and PUCCH D, and transmit at least one PUCCH among PUCCH A, PUCCH B, PUCCH C, and PUCCH D. Among PUCCH A, PUCCH B, PUCCH C, and PUCCH D, the PUCCH that maps HARQ-ACK A, HARQ-ACK B, and the UCI of PUCCH C may be specified in the specification, or may be a PUCCH associated with a higher priority. The UE may not transmit at least one of PUCCH A, PUCCH B, and PUCCH C.

[0156] [Aspect 3c-2] The UE drops one of HARQ-ACK A and HARQ-ACK B, maps the other to PUCCH C or another PUCCH D, and transmits PUCCH C or PUCCH D. Which of HARQ-ACK A and HARQ-ACK B is to be transmitted with priority may be specified in the specification. Each of HARQ-ACK A and HARQ-ACK B may be associated with a priority (DCIs that schedule each of PUCCH A and PUCCH B may include a priority indicator field). If the priority of HARQ-ACK A is equal to the priority of PUCCH B, the UE may prioritize one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A is different from the priority of PUCCH B, the UE may prioritize the HARQ-ACK with a higher priority among HARQ-ACK A and HARQ-ACK B.

[0157] [Aspect 3c-3] The UE does not multiplex HARQ-ACK A and HARQ-ACK B (maps HARQ-ACK A to PUCCH A and maps HARQ-ACK B to PUCCH B), and transmits PUCCH A, PUCCH B, and PUCCH C (simultaneously).

[0158] [Aspect 3c-4] The UE does not multiplex HARQ-ACK A and HARQ-ACK B (maps HARQ-ACK A to PUCCH A and maps HARQ-ACK B to PUCCH B), transmits PUCCH A and PUCCH B, and drops PUCCH C.

[0159] [Aspect 3c-5] The UE uses (decides / applies / selects) one of aspects 3c-1 to 3c-4 based on the number of bits of each of HARQ-ACK A and HARQ-ACK B, or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B), or the number of bits of UCI of PUCCH C, or the total number of bits of UCI of HARQ-ACK A, HARQ-ACK B, and PUCCH C, and (UCI of PUCCH A, PUCCH B, and PUCCH C).

[0160] [Aspect 3c-6] The UE uses (determines / applies / selects) one of the aspects 3c-1 to 3c-4 based on the PUCCH format of at least one of PUCCH A and PUCCH B.

[0161] [Aspect 3c-7] The UE uses (decides / applies / selects) one of aspects 3c-1 to 3c-4 based on RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities.

[0162] [Aspect 3c-8] The UE uses (decides / applies / selects) one of the aspects 3c-1 to 3c-4 based on the HARQ-ACK codebook type.

[0163] In example 3c, communication quality can be maintained or improved when HARQ-ACK A and HARQ-ACK B are multiplexed. In example 3c, UE operation can be simplified when any of PUCCH A, PUCCH B, and PUCCH C is dropped.

[0164] <Fourth embodiment> An upper layer parameter (RRC information element) / UE capability corresponding to at least one function (feature) in the first to third embodiments may be defined. The UE capability may indicate that the function is supported.

[0165] It may be specified that a UE for which a higher layer parameter corresponding to the function is configured may perform the function, and a UE for which a higher layer parameter corresponding to the function is not configured does not perform the function.

[0166] It may be specified that a UE that has reported a UE capability indicating that it supports the function may perform the function, and a UE that has not reported a UE capability indicating that it supports the function may not perform the function.

[0167] If the UE reports a UE capability indicating that it supports the function and a corresponding upper layer parameter is configured, the UE may perform the function. It may also be specified that if the UE reports a UE capability indicating that it supports the function or a corresponding upper layer parameter is configured, the UE does not perform the function.

[0168] The functionality may be simultaneous transmission of PUCCH and PUSCH. The functionality may be simultaneous transmission of PUCCH and PUSCH.

[0169] If the same beam / QCL / TCI state / spatial relationship is set / notified / indicated for multiple (e.g., two) channels that transmit simultaneously (the QCL relationship of the beam / QCL / TCI state / spatial relationship of multiple channels that transmit simultaneously is the same, or the QCL source RS of the beam / QCL / TCI state / spatial relationship of multiple channels that transmit simultaneously is common), the UE may perform the function (its simultaneous transmission). According to this condition, the UE does not need to transmit using different beams at the same time. This condition may be limited to frequencies equal to or higher than a specific frequency (e.g., frequency range (FR)2 / FR4). This condition may not be required for frequencies lower than the specific frequency (e.g., FR1). The specific frequency may be any of 7.152 GHz, 24.25 GHz, and 52.6 GHz.

[0170] If the same beam / QCL / TCI state / spatial relationship is not configured / indicated / indicated for multiple (e.g., two) channels to transmit simultaneously, the UE may perform that function (its simultaneous transmission). This behavior is appropriate when the UE can transmit one channel per beam (when the UE has a multi-panel configuration).

[0171] In this embodiment, when a PUSCH can be skipped, for example, when there is no data to be transmitted, the PUSCH may not be skipped, and the HARQ-ACK corresponding to the multicast PDSCH may be mapped (multiplexed) to the PUSCH and transmitted. This operation may be applied regardless of the setting / indication of the NACK-only feedback for the multicast PDSCH.

[0172] According to this embodiment, the UE can achieve the above functions while maintaining compatibility with existing specifications.

[0173] (Wireless communication systems) A configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of the present disclosure.

[0174] 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

[0175] Furthermore, the wireless communication system 1 may support dual connectivity between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0176] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN) and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN and the LTE (E-UTRA) base station (eNB) is the SN.

[0177] The wireless communication system 1 may support dual connectivity between multiple base stations in the same RAT (for example, dual connectivity in which both the MN and the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0178] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged in the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located in at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as a base station 10.

[0179] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0180] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

[0181] Furthermore, the user terminal 20 may perform communication in each CC using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0182] The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0183] The base station 10 may be connected to the core network 30 directly or via another base station 10. The core network 30 may include at least one of, for example, an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

[0184] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0185] In the wireless communication system 1, a wireless access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and the uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

[0186] The radio access scheme may be called a waveform. In the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0187] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as a downlink channel.

[0188] In addition, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), etc. may be used as an uplink channel.

[0189] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0190] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information of at least one of the PDSCH and the PUSCH.

[0191] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

[0192] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0193] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," and "CORESET setting" in the present disclosure may be read as interchangeable terms.

[0194] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and a scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0195] In the present disclosure, a downlink, an uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning of the channels.

[0196] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0197] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and the DMRS for the PBCH) may be called an SS / PBCH block, an SS Block (SSB), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

[0198] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may be called a user equipment specific reference signal (UE-specific reference signal).

[0199] (base station) 7 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0200] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0201] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0202] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0203] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0204] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0205] The transmitting / receiving antenna 130 can be composed of an antenna described based on common understanding in the technical field to which the present disclosure pertains, such as an array antenna.

[0206] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0207] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0208] The transceiver 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0209] The transceiver 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0210] The transceiver unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

[0211] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna .

[0212] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0213] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0214] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data) for the user terminal 20, control plane data, etc.

[0215] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0216] The control unit 110 may determine at least one of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH) and the uplink channel when the PUCCH overlaps with the uplink channel in the time domain. The transceiver unit 120 may receive the channel.

[0217] (User terminal) 8 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0218] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0219] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0220] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission / reception, measurement, etc. using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission / reception unit 220.

[0221] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, which are described based on common understanding in the technical field related to the present disclosure.

[0222] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0223] The transmitting / receiving antenna 230 can be composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

[0224] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0225] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

[0226] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0227] The transceiver 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

[0228] Whether or not to apply the DFT process may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver 220 (transmission processor 2211) may perform the DFT process as the transmission process to transmit the channel using a DFT-s-OFDM waveform, and may not perform the DFT process as the transmission process if transform precoding is enabled for the channel.

[0229] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna 230.

[0230] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna 230.

[0231] The transceiver 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0232] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0233] In addition, the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0234] When a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH) overlaps with an uplink channel in the time domain, the control unit 210 may determine at least one of the PUCCH and the uplink channel. The transceiver unit 220 may transmit the channel.

[0235] The PUCCH resources may be shared among multiple terminals (first embodiment).

[0236] A method of transmitting only a negative acknowledgement (NACK) to the PUCCH may be applied (second embodiment).

[0237] The uplink channel may be either a second PUCCH for transmitting second HARQ-ACK information for a unicast PDSCH or a channel overlapping in the time domain with the second PUCCH (third embodiment).

[0238] (Hardware configuration) The block diagrams 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. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0239] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

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

[0241] In this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0242] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

[0243] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading a specific software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations, controls communications via a communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and the storage 1003.

[0244] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0245] Moreover, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized in a similar manner.

[0246] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0247] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0248] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0249] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0250] In addition, each device such as the processor 1001 and the memory 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.

[0251] Furthermore, the base station 10 and the user 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), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0252] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, a frequency carrier, a carrier frequency, etc.

[0253] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may 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.

[0254] Here, the numerology may be a communication parameter applied to at least one of the transmission and reception of a signal or channel, and may indicate at least one of, for example, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

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

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

[0257] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be read as interchangeable with each other.

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

[0259] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0260] 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) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0261] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

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

[0263] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 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.

[0264] A resource block (RB) is a resource allocation unit in the time domain and the 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 the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0265] In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0266] In addition, one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

[0268] 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 numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0270] 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 replaced with "BWP".

[0271] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols 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, and other configurations can be changed in various ways.

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

[0273] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (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 limiting in any way.

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

[0275] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via a plurality of network nodes.

[0276] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0277] 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 in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0278] The physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified, for example, by using a MAC Control Element (CE).

[0279] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0280] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

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

[0282] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the 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, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0283] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0284] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," and the like may be used interchangeably.

[0285] In this disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

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

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

[0288] A mobile station may also be referred to 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.

[0289] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving 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 include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0290] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment 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 user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user 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, "sidelink"). For example, an uplink channel, a downlink channel, etc. may be read as a sidelink channel.

[0291] Similarly, the user terminal in the present disclosure may be interpreted as a base station. In this case, the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0292] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. It is clear that in a network including one or more network nodes having base stations, various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0293] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. 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.

[0294] Each aspect / embodiment described in the present disclosure may be implemented using any of a wide variety of standards, including Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal point)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems using 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other appropriate wireless communication methods, next-generation systems that are based on these, etc. Also, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

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

[0296] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient 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 precede the second element in some way.

[0297] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, and the like.

[0298] A "determining" may also be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

[0299] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0300] Also, "determine (decide)" may be read as "assume", "expect", "consider", etc.

[0301] The "maximum transmit power" described in this disclosure may mean the maximum value of the transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

[0302] As used in this disclosure, the terms "connected" and "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements "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 "accessed".

[0303] In this disclosure, when two elements are connected, it can be considered that they are "connected" or "coupled" to each other using one or more electric wires, cables, printed electrical connections, etc., and, as some non-limiting and non-exhaustive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, optical (both visible and invisible) region, etc.

[0304] In this disclosure, the term "A and B are different" may mean that "A and B are different from each other". Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted in the same way as "different".

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

[0306] In this disclosure, where articles have been 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.

[0307] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. A receiving unit for receiving feedback configuration based only on a negative acknowledgement (NACK) of a hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) corresponding to a multicast physical downlink shared channel (PDSCH); a control unit configured to control transmission of the HARQ-ACK multiplexed on a second physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) when a first physical uplink control channel (PUCCH) for transmitting the HARQ-ACK when the feedback based only on the NACK is configured overlaps with the second PUCCH or a PUSCH in a time domain; When the first PUCCH overlaps with the second PUCCH or the PUSCH, the control unit multiplexes an ACK for the PDSCH that has been successfully decoded onto the second PUCCH or the PUSCH in accordance with a feedback setting based on ACK / NACK rather than a feedback setting based only on the NACK.

2. The terminal according to claim 1, wherein the control unit controls transmission of a HARQ-ACK corresponding to the multicast PDSCH and a HARQ-ACK corresponding to the unicast PDSCH, which are multiplexed in the second PUCCH, when the second PUCCH is a PUCCH that transmits a HARQ-ACK corresponding to a unicast PDSCH.

3. The terminal of claim 1 , wherein the second PUCCH is a PUCCH that includes channel state information (CSI).

4. receiving a feedback configuration of a hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) corresponding to a multicast physical downlink shared channel (PDSCH) based only on a negative acknowledgement (NACK); When a first physical uplink control channel (PUCCH) for transmitting the HARQ-ACK when the feedback based only on the NACK is configured overlaps with a second PUCCH or a physical uplink shared channel (PUSCH) in a time domain, controlling transmission of the HARQ-ACK multiplexed on the second PUCCH or the PUSCH; and when the first PUCCH overlaps with the second PUCCH or the PUSCH, multiplexing an ACK for the PDSCH that has been successfully decoded into the second PUCCH or the PUSCH in accordance with a feedback setting based on ACK / NACK rather than a feedback setting based only on the NACK.

5. A transmitter for transmitting feedback configuration based only on a negative acknowledgement (NACK) of a hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) corresponding to a multicast physical downlink shared channel (PDSCH); a control unit configured to control reception of the HARQ-ACK multiplexed on a first physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) when a first physical uplink control channel (PUCCH) for transmitting the HARQ-ACK in a case where the feedback based only on the NACK is configured overlaps with a second PUCCH or a PUSCH in a time domain, A base station, in which, when the first PUCCH overlaps with the second PUCCH or the PUSCH, an ACK for the PDSCH that has been successfully decoded is multiplexed onto the second PUCCH or the PUSCH and transmitted in accordance with a feedback setting based on ACK / NACK rather than a feedback setting based only on the NACK.

6. A system including a terminal and a base station, The terminal includes: A receiving unit for receiving feedback configuration based only on a negative acknowledgement (NACK) of a hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) corresponding to a multicast physical downlink shared channel (PDSCH); a control unit configured to control transmission of the HARQ-ACK multiplexed on a second physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) when a first physical uplink control channel (PUCCH) for transmitting the HARQ-ACK when the feedback based only on the NACK is configured overlaps with the second PUCCH or a PUSCH in a time domain; When the first PUCCH overlaps with the second PUCCH or the PUSCH, the control unit multiplexes an ACK for the PDSCH that has been successfully decoded onto the second PUCCH or the PUSCH according to a feedback setting based on an ACK / NACK rather than a feedback setting based only on the NACK; The base station, A transmission unit for transmitting a feedback configuration based only on the NACK; A control unit that controls reception of the HARQ-ACK.

Images