Terminal, wireless communication method, base station and system

The terminal and wireless communication method address the lack of communication control in NR by using PUCCH parameters for multicast PDSCH transmission, ensuring effective system performance in high-density user environments.

JP7583834B2Active Publication Date: 2024-11-14NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2022570863
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-12-23
Publication Date
2024-11-14
Estimated Expiration
2040-12-23

AI Technical Summary

Technical Problem

In future wireless communication systems like NR, the communication control for multicast downlink data transmission has not been sufficiently studied, leading to a risk of deteriorated system performance such as reduced throughput.

Method used

A terminal and wireless communication method that includes parameters for frequency hopping and repetition number of the physical uplink control channel (PUCCH) to control multicast Physical Downlink Shared Channel (PDSCH) transmission, with a receiving unit for acknowledgment information and a control unit for repeated transmission.

Benefits of technology

Enables appropriate communication control during multicast downlink data transmission, enhancing system performance by preventing throughput degradation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007583834000001
    Figure 0007583834000001
  • Figure 0007583834000002
    Figure 0007583834000002
  • Figure 0007583834000003
    Figure 0007583834000003
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure is characterized by comprising: a reception unit that receives a multicast physical downlink shared channel (PDSCH); and a control unit which, on the basis of information notified from a base station, controls a repeated transmission of a physical uplink control channel (PUCCH) for transmission of delivery confirmation information to the multicast PDSCH.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a terminal and a wireless communication method in a next-generation mobile communication system. 、 base station 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 such an environment, it is expected that NR will transmit downlink data / downlink shared channels using multicast / broadcast to multiple UEs.

[0007] However, in the NR specifications up to now, communication control when multicast downlink data transmission is performed has not been sufficiently considered. If communication control is not performed appropriately when multicast downlink data transmission is performed, there is a risk of degradation of system performance, such as a decrease in throughput.

[0008] Therefore, the present disclosure relates to a terminal and a wireless communication method capable of appropriately controlling communication even when multicast downlink data transmission is performed. 、 base station and systems One of the aims is to provide. [Means for solving the problem]

[0009] A terminal according to an embodiment of the present disclosure includes: Information regarding multicasting including at least one parameter related to frequency hopping and repetition count of a physical uplink control channel (PUCCH); Multicast Physical Downlink Shared Channel (PDSCH) and, A receiving unit for receiving the Regarding the multicast for transmitting acknowledgement information for the multicast PDSCH based on the information. The above PUCC H and a control unit that controls the repeated transmission. Effect of the Invention

[0010] According to one aspect of the present disclosure, even when multicast downlink data transmission is performed, communication can be appropriately controlled. [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 transmission of a PUCCH corresponding to a multicast PDSCH. [Figure 4] FIG. 4 is a diagram showing an example of repeat transmission control of a PUCCH corresponding to a multicast PDSCH according to the first embodiment. [Diagram 5] 5A to 5C are diagrams showing an example of a correspondence relationship between the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH according to the first embodiment. [Figure 6] FIG. 6 is a diagram showing an example of repeat transmission control of a PUCCH corresponding to a multicast PDSCH according to the second embodiment. [Figure 7] 7A to 7C are diagrams showing an example of a correspondence relationship between the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH according to the second embodiment. [Figure 8] 8A to 8C are diagrams showing an example of a correspondence relationship between the number of repetitions of a PUCCH corresponding to a multicast PDSCH of an initial transmission and the number of repetitions of a PUCCH corresponding to a retransmission multicast PDSCH according to the fourth embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 12]FIG. 12 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] 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.

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

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

[0036] (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.

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

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

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

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

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

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

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

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

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

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

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

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

[0049] (Repeat sending) In Rel.15, repeated transmission is supported for data transmission. For example, a base station (network (NW), gNB) may repeat transmission of DL data (e.g., downlink shared channel (PDSCH)) a predetermined number of times. Alternatively, a UE may repeat transmission of a UL control channel (e.g., uplink control channel (PUCCH)) or UL data (e.g., uplink shared channel (PUSCH)) a predetermined number of times.

[0050] The number of repetitions is determined by the repetition factor K, the aggregation factor K, and the number of slots (N PUCCH repeat ), etc. The n-th repetition may also be referred to as the n-th transmission occasion, etc. The UE may semi-statically receive information regarding the number of PUCCH repetitions through higher layer signaling (e.g., nrofSlots).

[0051] In Rel.15, when repetitive transmission is applied to a PUCCH corresponding to a unicast PDSCH, the parameters of the PUCCH repetitive transmission are configured by higher layer signaling. The repetitive transmission of the PUCCH may be called PUCCH repetition or PUCCH repetition.

[0052] Repeated transmission of PUCCH is expected to improve the reception quality of PUCCH on the network side. However, in the current Rel.15 / 16 NR, PUCCH corresponding to unicast PDSCH is supported, but PUCCH transmission corresponding to multicast PDSCH is not supported. Therefore, when multicast PDSCH is supported in Rel.17 or later, how to control (for example, whether to apply, or parameter setting, etc.) repeat transmission of PUCCH corresponding to the multicast PDSCH becomes an issue (see FIG. 3).

[0053] If repeat transmission is not appropriately applied / configured to the PUCCH for transmitting HARQ-ACK corresponding to the multicast PDSCH, this may result in a decrease in throughput, etc.

[0054] Therefore, the present inventors have studied UE operations for repeated transmission of a PUCCH corresponding to a multicast PDSCH and have come up with the idea of ​​this embodiment.

[0055] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] (Wireless communication method) The UEs receiving the multicast PDSCH may be controlled to perform a predetermined operation for the repeated transmission of the PUCCH. The UEs receiving the multicast PDSCH may be UEs in which predetermined upper layer parameters (e.g., upper layer parameters related to the multicast PDSCH) are set, or UEs having a receiving capability for the multicast PDSCH.

[0073] The predetermined operation may be to apply PUCCH repetition (for example, PUCCH Repetition) to a PUCCH corresponding to a multicast PDSCH (predetermined operation 1). The PUCCH corresponding to a multicast PDSCH may be read as a PUCCH for transmitting HARQ-ACK information for the multicast PDSCH.

[0074] In the repeated transmission of the PUCCH, the same uplink control information (e.g., UCI) may be repeatedly transmitted in the time domain. The time domain may be a different time domain (e.g., TDM) in units of symbols / slots. Whether the repeated transmission performed on a slot basis (Inter slot repetition) or the repeated transmission performed on a symbol basis (Intra slot repetition) is applied may be defined in the specifications, or may be set from the base station to the UE by higher layer signaling or the like.

[0075] The repeated transmission of the PUCCH may be interpreted as the transmission of a PUCCH in which one UCI is coded / spread across multiple time domains / frequency domains / spatial domains.

[0076] The repeat transmission of the PUCCH in this specification may be applied to the PUCCH that transmits UCI including at least acknowledgement information for the multicast PDSCH. Whether ACK / NACK feedback or NACK only is applied as the acknowledgement information may be set to the UE by the base station using higher layer signaling / DCI. The UE to which NACK only is set may be controlled to feed back only NACK.

[0077] The UE may perform repeated transmission of the PUCCH corresponding to the multicast PDSCH when the repeated transmission of the PUCCH is set, and may control not to apply the PUCCH repeated transmission when the repeated transmission of the PUCCH is not set. The repeated transmission of the PUCCH may be set to the UE by a higher layer parameter or the like from the base station.

[0078] Alternatively, the predetermined operation may be to not apply PUCCH repetition to the PUCCH corresponding to the multicast PDSCH (predetermined operation 2). In this case, the UE may not assume / expect to apply repetitive transmission to the PUCCH corresponding to the multicast PDSCH.

[0079] The following describes a case where the predetermined operation 1 is applied. Each embodiment may be applied alone or in combination.

[0080] In the following description, the parameter related to repetition transmission may be at least one of a parameter related to repetition on / off, a parameter related to the number of repetitions, a parameter related to inter-slot frequency hopping, and a parameter related to repetition type.

[0081] The repetition type may be, for example, a slot-based repetition type (e.g., repetition type A) or a symbol-based repetition type (e.g., repetition type B). Repetition type A may be controlled in the same manner as PUSCH repetition type A, and repetition type B may be controlled in the same manner as PUSCH repetition type B.

[0082] In the following embodiments, at least one of PTM transmission method 1 and PTM transmission method 2 may be applied. The UE may be configured to apply either PTM transmission method 1 or PTM transmission method 2 based on higher layer signaling / DCI.

[0083] In the following description, the repeat transmission of the PUCCH corresponding to the multicast PDSCH will be described, but the present embodiment is not limited thereto. The present embodiment may be applied to the configuration of the PUCCH resource (PUCCH resource) corresponding to the multicast PDSCH / the PUCCH resource to which the repeat transmission is applied (for example, the parameter of the PUCCH resource). The parameter of the repeat transmission of the PUCCH may be read as the parameter of the PUCCH resource.

[0084] <First embodiment> When repeated transmission is applied to a PUCCH corresponding to a multicast PDSCH, some or all of the parameters related to repeated transmission of the PUCCH may be configured / instructed for each UE (see FIG. 4).

[0085] FIG. 4 shows a case where the multicast PDSCH (or the group common PDSCH) is scheduled by a UE-specific PDCCH, but it may also be scheduled by a UE-common PDCCH.

[0086] 4, some or all of the parameters related to the repeated transmission may be set based on at least one of the following aspects 1-1 to 1-5. In this specification, the parameters related to the repeated transmission may be interpreted as conditions applied to the repeated transmission.

[0087] In the following description, the number of repeated transmissions (e.g., the number of repetitions) is set for each UE as a parameter related to repeated transmission, but the present invention is not limited to this. The same may be applied to other parameters (e.g., at least one of a parameter related to repetition on / off, a parameter related to frequency hopping, and a parameter related to a repetition type).

[0088] Among the parameters related to PUCCH repeat transmission, in addition to the parameter of the number of repeat transmissions (e.g., nrofSlots), other parameters may be set for each UE, or parameters other than the number of repeat transmissions may be set commonly for the UE. The number of repeat transmissions may include 1, and when the number of repeat transmissions is 1, it may mean that repeat transmission is not applied. In this case, whether or not repeat transmission is applied may be instructed / set to the UE by setting the number of repeat transmissions (1 or other).

[0089] <<Aspect 1-1>> The parameters related to the repeated transmission may be configured for each PUCCH configuration. The PUCCH configuration may be a parameter (PUCCH-Config) configured by a higher layer. The PUCCH configuration may be configured separately for each UE, for each UL partial band (UL BWP), or for each component carrier (CC).

[0090] The UE may control the repeat transmission of the PUCCH corresponding to the multicast PDSCH based on a parameter related to the repeat transmission included in a certain PUCCH configuration.

[0091] Alternatively, the parameters regarding repeated transmission may be set separately for each UL BWP or for each CC.

[0092] <<Aspect 1-2>> The parameter related to the repeated transmission may be set for each predetermined parameter in a certain PUCCH configuration (PUCCH-Config). The predetermined parameter may be a parameter related to the PUCCH format (for example, PUCCH-FormatConfig).

[0093] The base station may set a parameter (e.g., nrofSlots) related to repeated transmission separately for each PUCCH format (e.g., PUCCH-FormatConfig) included in the PUCCH configuration. The UE may control repeated transmission (e.g., the number of transmissions) of the PUCCH separately for each applied PUCCH format.

[0094] In this case, when a PUCCH resource set including one or more PUCCH resources is configured, the repetition application / repetition transmission count is the same for a specific PUCCH format in one or more PUCCH resources. For example, assume that PUCCH resource A in PUCCH resource set #1 and PUCCH resource B in PUCCH resource set #2 both correspond to a specific PUCCH format, and the repetition count is set to K for the specific PUCCH format. In this case, the UE controls to apply the same repetition count K to PUCCH resource A and PUCCH resource B.

[0095] This allows each UE to set parameters related to repetition for each PUCCH format (in units of PUCCH formats).

[0096] The parameters related to the PUCCH format (for example, PUCCH-FormatConfig) may include other parameters in addition to the parameters related to the number of repetitions. In this case, all the parameters included in PUCCH-FormatConfig may be set separately for each UE. Alternatively, some of the parameters included in PUCCH-FormatConfig may be set commonly between UEs.

[0097] <<Aspect 1-3>> The parameter related to the repeated transmission may be set for each predetermined parameter in a certain PUCCH configuration (PUCCH-Config). The predetermined parameter may be a parameter related to a PUCCH resource / PUCCH resource set (for example, PUCCH-Resource / PUCCH-ResourceSet).

[0098] The base station may separately configure a parameter (e.g., nrofSlots) related to repeated transmission for each PUCCH resource (e.g., PUCCH-Resource) / PUCCH resource set (e.g., PUCCH-ResourceSet) included in the PUCCH configuration. The UE may separately control repeated transmission (e.g., the number of transmissions) of PUCCH for each applicable PUCCH resource / PUCCH resource set.

[0099] The parameters related to the PUCCH resource / PUCCH resource set (e.g., PUCCH-Resource / PUCCH-ResourceSet) may include other parameters in addition to the parameters related to the number of repetitions. In this case, all the parameters included in the PUCCH-Resource / PUCCH-ResourceSet may be set separately for each UE. Alternatively, some of the parameters included in the PUCCH-Resource / PUCCH-ResourceSet may be set commonly between UEs.

[0100] By setting transmission parameters for each PUCCH resource / PUCCH resource set, it is possible to set different parameters for PUCCH resources / PUCCH resource sets to which the same PUCCH format is applied.

[0101] <<Aspect 1-4>> The parameters related to the repeated transmission may be indicated for each UE based on at least one of the MAC control information (eg, MAC CE) and the DCI (or a DCI field).

[0102] [MAC CE] The parameters related to the repeated transmission of the PUCCH may be indicated to each UE using the MAC CE in the multicast PDSCH. In this case, the MAC CE transmitted in the multicast PDSCH may include instructions for each UE. Each UE may control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the MAC CE in the multicast PDSCH.

[0103] By including parameters (eg, MAC CE) related to PUCCH transmission corresponding to a multicast PDSCH in the multicast PDSCH, it is possible to eliminate the need to transmit a separate signal / channel for reporting the parameters.

[0104] Alternatively, the parameters related to the repeated transmission of the PUCCH may be indicated to each UE using the MAC CE in the unicast PDSCH (or the UE-specific PDSCH). Each UE may control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the MAC CE in the unicast PDSCH corresponding to the own terminal.

[0105] By including parameters (eg, MAC CE) related to PUCCH transmission corresponding to a multicast PDSCH in a channel (eg, a unicast PDSCH) other than the multicast PDSCH, it is possible to suppress an increase in overhead of the multicast PDSCH.

[0106] [DCI Field] The parameters related to the repeated transmission of the PUCCH may be indicated to each UE using the DCI corresponding to the multicast PDSCH. In this case, the DCI corresponding to the multicast PDSCH may include instructions for each UE. For example, the parameters related to the repeated transmission of the PUCCH may be set in a part of a time domain resource allocation (TDRA) table used for notifying / setting resource allocation in the time domain of the multicast PDSCH.

[0107] Each UE may control repeated transmission of a PUCCH corresponding to a multicast PDSCH based on the DCI corresponding to the multicast PDSCH. In this specification, the DCI corresponding to the multicast PDSCH may be read as a DCI that schedules the multicast PDSCH.

[0108] By including parameters related to PUCCH transmission corresponding to a multicast PDSCH in the DCI corresponding to the multicast PDSCH, it becomes possible to dynamically change the parameters of the repeat transmission of the PUCCH.

[0109] Alternatively, the parameters related to the repeated transmission of the PUCCH may be indicated to each UE by using DCI corresponding to the unicast PDSCH (or a UE-specific PDSCH). For example, the parameters related to the repeated transmission of the PUCCH may be set in a part of a time domain resource allocation (TDRA) table used for notifying / setting resource allocation in the time domain of the unicast PDSCH.

[0110] Each UE may control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the DCI corresponding to the unicast PDSCH corresponding to the own terminal. That is, the UE may apply the parameters used for the PUCCH transmission corresponding to the unicast PDSCH to the PUCCH transmission corresponding to the multicast PDSCH. The DCI corresponding to the unicast PDSCH may be the latest / most recent DCI received before receiving the multicast PDSCH.

[0111] By including parameters related to PUCCH transmission corresponding to a multicast PDSCH in DCI corresponding to a unicast PDSCH, it is possible to suppress an increase in overhead of DCI corresponding to a multicast PDSCH.

[0112] Alternatively, the parameters related to the repeated transmission of the PUCCH may be indicated to each UE using DCI common to a plurality of UEs (for example, group common DCI). In this case, the group common DCI may include instructions for each UE. The group common DCI may be a DCI format (for example, DCI format 2_2) used for TPC command notification, or may be another format.

[0113] In this way, by configuring the transmission parameters (e.g., repetitive transmission parameters) of the PUCCH corresponding to the multicast PDSCH to be instructed / notified / set separately for each UE, it is possible to set or change whether or not to apply repetitive transmission / parameters depending on the quality of each UE.

[0114] Aspects 1-5 The parameters related to the repeated transmission may be implicitly specified for each UE. For example, the parameters related to the repeated transmission of the PUCCH for each UE may be set in accordance with a predetermined condition / predetermined parameter.

[0115] The predetermined condition / predetermined parameter may be, for example, a condition / parameter applied to a multicast PDSCH. In this case, the predetermined condition / predetermined parameter may be set in the UE from the base station using higher layer signaling / DCI.

[0116] As an example, the number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH. The association between the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH corresponding to the multicast PDSCH may be set / defined separately for each UE.

[0117] The number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH so as to be the same (see FIG. 5A). For example, when the number of repetitions of a multicast PDSCH is X, the UE may apply X as the number of repetitions of a PUCCH corresponding to the multicast PDSCH.

[0118] Furthermore, when the number of repetitions of a multicast PDSCH is 1, the number of repetitions of the PUCCH corresponding to the multicast PDSCH is associated with 1, and when the number of repetitions of a multicast PDSCH is greater than 1 (>1), the number of repetitions of the PUCCH corresponding to the multicast PDSCH may be associated with a value greater than 1 (>1). In this case, the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH corresponding to the multicast PDSCH may be associated with each other in different ways.

[0119] When the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH corresponding to the multicast PDSCH are associated differently, a predetermined conversion rule may be defined, or the conversion rule may be indicated to each UE by higher layer signaling (see FIG. 5B). FIG. 5B shows a case where, among a plurality of repetitions of a multicast PDSCH (here, 1, 2, 4, 8), some repetitions (here, 1 and 2) are associated equally with repeated transmission of a PUCCH, and other repetitions (here, 4 and 3) are associated differently with the number of repetitions of a PUCCH.

[0120] 5B shows a case where the number of repetitions of a multicast PDSCH is greater than or equal to the number of repetitions of the PUCCH corresponding to the multicast PDSCH. In this case, the number of repetitions can be set to a number suitable for a TDD configuration with many DLs (e.g., DL heavy). In addition, this may be preferably applied when the PUCCH quality is better than the PDSCH.

[0121] Alternatively, the number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH (see, for example, FIG. 5C). Such a configuration may be suitably applied when the PDSCH quality is better than the PUCCH quality.

[0122] By associating parameters applied to repeated transmission of a PUCCH corresponding to a multicast PDSCH with conditions / parameters applied to the multicast PDSCH, it is possible to suppress an increase in the amount of information notified to the UE.

[0123] <Second embodiment> When repeated transmission is applied to a PUCCH corresponding to a multicast PDSCH, some or all of the parameters related to repeated transmission may be commonly configured / indicated between UEs (see FIG. 6).

[0124] FIG. 6 shows a case where the multicast PDSCH (or the group common PDSCH) is scheduled by a UE-specific PDCCH, but it may also be scheduled by a UE-common PDCCH.

[0125] In FIG. 6, some or all of the parameters related to the repetitive transmission may be set based on at least one of the following aspects 2-1 to 2-5.

[0126] In the following description, a case will be described in which the number of repetitions (e.g., the number of repetitions) is set for each UE as a parameter related to repetitive transmission, but this is not limiting. Among the parameters related to PUCCH repetitive transmission, in addition to the parameter for the number of repetitions (e.g., (e.g., nrofSlots)), other parameters may be set for each UE, or parameters other than the number of repetitions may be set commonly for UEs.

[0127] <<Aspect 2-1>> The parameters related to the repeated transmission may be configured for each PUCCH configuration. The PUCCH configuration may be a parameter (PUCCH-Config) configured by a higher layer. The PUCCH configuration may be configured separately for each UE, for each UL partial band (UL BWP), or for each component carrier (CC).

[0128] When the PUCCH configuration is configured for each UE, the base station may be controlled to set the same value as the parameter related to the PUCCH repeat transmission. Each UE may control the repeat transmission of the PUCCH corresponding to the multicast PDSCH based on the parameter related to the repeat transmission included in a certain PUCCH configuration.

[0129] Alternatively, the parameters regarding repeated transmission may be set separately for each UL BWP or for each CC.

[0130] "Aspect 2-2" The parameter related to the repeated transmission may be set for each predetermined parameter in a certain PUCCH configuration (PUCCH-Config). The predetermined parameter may be a parameter related to the PUCCH format (for example, PUCCH-FormatConfig).

[0131] The base station may set a parameter (e.g., nrofSlots) related to repeated transmission separately for each PUCCH format (e.g., PUCCH-FormatConfig) included in the PUCCH configuration. The UE may control repeated transmission (e.g., the number of transmissions) of the PUCCH separately for each applied PUCCH format.

[0132] In this case, when a PUCCH resource set including one or more PUCCH resources is configured, the repetition application / repetition transmission count is the same for a specific PUCCH format in one or more PUCCH resources. For example, assume that PUCCH resource A in PUCCH resource set #1 and PUCCH resource B in PUCCH resource set #2 both correspond to a specific PUCCH format, and the repetition count is set to K for the specific PUCCH format. In this case, the UE controls to apply the same repetition count K to PUCCH resource A and PUCCH resource B.

[0133] This makes it possible to set repetition-related parameters for each PUCCH format (PUCCH format unit) between UEs.

[0134] The parameters related to the PUCCH format (for example, PUCCH-FormatConfig) may include other parameters in addition to the parameters related to the number of repetitions. In this case, all the parameters included in PUCCH-FormatConfig may be set commonly between UEs. Alternatively, some of the parameters included in PUCCH-FormatConfig may be set separately for each UE.

[0135] "Aspect 2-3" The parameter related to the repeated transmission may be set for each predetermined parameter in a certain PUCCH configuration (PUCCH-Config). The predetermined parameter may be a parameter related to a PUCCH resource / PUCCH resource set (for example, PUCCH-Resource / PUCCH-ResourceSet).

[0136] The base station may separately configure a parameter (e.g., nrofSlots) related to repeated transmission for each PUCCH resource (e.g., PUCCH-Resource) / PUCCH resource set (e.g., PUCCH-ResourceSet) included in the PUCCH configuration. The UE may separately control repeated transmission (e.g., the number of transmissions) of PUCCH for each applicable PUCCH resource / PUCCH resource set.

[0137] The parameters related to the PUCCH resource / PUCCH resource set (e.g., PUCCH-Resource / PUCCH-ResourceSet) may include other parameters in addition to the parameters related to the number of repetitions. In this case, all the parameters included in the PUCCH-Resource / PUCCH-ResourceSet may be set separately for each UE. Alternatively, some of the parameters included in the PUCCH-Resource / PUCCH-ResourceSet may be set commonly between UEs.

[0138] When parameters related to repeat transmission are configured commonly between UEs for each PUCCH resource / PUCCH resource set, the PUCCH resources can be configured separately for each UE, making it possible to control whether or not PUCCH repeat transmission is applied / how many times it is applied depending on the quality for each UE.

[0139] By setting transmission parameters for each PUCCH resource / PUCCH resource set, it is possible to set different parameters for PUCCH resources / PUCCH resource sets to which the same PUCCH format is applied.

[0140] <<Aspect 2-4>> Parameters related to repeated transmission may be commonly indicated between UEs based on at least one of MAC control information (eg, MAC CE) and DCI (or a DCI field).

[0141] [MAC CE] The parameters related to the repeated transmission of the PUCCH may be indicated to each UE using the MAC CE in the multicast PDSCH. In this case, the MAC CE transmitted in the multicast PDSCH may include an instruction content common to the UEs. Each UE may control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the MAC CE in the multicast PDSCH.

[0142] By including an instruction common to all UEs in the MAC CE transmitted in the multicast PDSCH, it is possible to suppress an increase in the overhead of the multicast PDSCH.

[0143] [DCI Field] The parameters related to the repeated transmission of the PUCCH may be commonly indicated between UEs using the DCI corresponding to the multicast PDSCH. In this case, the DCI corresponding to the multicast PDSCH may include an instruction content common to the UEs. For example, the parameters related to the repeated transmission of the PUCCH may be set in a part of a time domain resource allocation (TDRA) table used for notifying / setting the time domain resource allocation of the multicast PDSCH.

[0144] Each UE may control repeated transmission of a PUCCH corresponding to a multicast PDSCH based on the DCI corresponding to the multicast PDSCH.

[0145] By including parameters related to PUCCH transmission corresponding to a multicast PDSCH as UE common information in the DCI corresponding to the multicast PDSCH, it is possible to suppress an increase in overhead of the DCI.

[0146] Alternatively, the parameters related to the repeated transmission of the PUCCH may be indicated to each UE by using DCI common to a plurality of UEs (for example, group common DCI). In this case, the group common DCI may include instructions for each UE.

[0147] In this manner, by configuring the transmission parameters (eg, repetition transmission parameters) of the PUCCH corresponding to the multicast PDSCH to be commonly indicated / notified / set between UEs, it is possible to suppress an increase in overhead.

[0148] 《Aspect 2-5》 The parameters related to the repeated transmission may be implicitly specified for each UE. For example, the parameters related to the repeated transmission of the PUCCH for each UE may be set in accordance with a predetermined condition / predetermined parameter.

[0149] The predetermined condition / predetermined parameter may be, for example, a condition / parameter applied to a multicast PDSCH. In this case, the predetermined condition / predetermined parameter may be set in the UE from the base station using higher layer signaling / DCI.

[0150] As an example, the number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH. The association between the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH corresponding to the multicast PDSCH may be commonly set / defined between UEs.

[0151] The number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH so as to be the same (see FIG. 7A). For example, when the number of repetitions of a multicast PDSCH is X, the UE may apply X as the number of repetitions of a PUCCH corresponding to the multicast PDSCH.

[0152] Furthermore, when the number of repetitions of a multicast PDSCH is 1, the number of repetitions of the PUCCH corresponding to the multicast PDSCH is associated with 1, and when the number of repetitions of a multicast PDSCH is greater than 1 (>1), the number of repetitions of the PUCCH corresponding to the multicast PDSCH may be associated with a value greater than 1 (>1). In this case, the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH corresponding to the multicast PDSCH may be associated with each other in different ways.

[0153] When the number of repetitions of a multicast PDSCH and the number of repetitions of a PUCCH corresponding to the multicast PDSCH are associated differently, a predetermined conversion rule may be defined, or the conversion rule may be indicated to each UE by higher layer signaling (see FIG. 7B). FIG. 7B shows a case where some of the multiple repetitions of a multicast PDSCH (here, 1, 2, 4, 8) (here, 1 and 2) are associated equally with the repeated transmission of a PUCCH, and other repetitions (here, 4 and 3) are associated differently with the number of repetitions of a PUCCH.

[0154] 7B shows a case where the number of repetitions of a multicast PDSCH is greater than or equal to the number of repetitions of the PUCCH corresponding to the multicast PDSCH. In this case, the number of repetitions can be set to a number suitable for a TDD configuration with many DLs (e.g., DL heavy). In addition, this may be preferably applied when the PUCCH quality is better than the PDSCH quality.

[0155] Alternatively, the number of repetitions of a multicast PDSCH may be associated with the number of repetitions of a PUCCH corresponding to the multicast PDSCH (see, for example, FIG. 7C). Such a configuration may be suitably applied when the PDSCH quality is better than the PUCCH quality.

[0156] By associating parameters applied to repeated transmission of a PUCCH corresponding to a multicast PDSCH with conditions / parameters applied to the multicast PDSCH, it is possible to suppress an increase in the amount of information notified to the UE.

[0157] <Third embodiment> A part or all of parameters related to repeated transmission of PUCCH corresponding to multicast PDSCH may be set / instructed separately for each UE based on a predetermined condition, or may be set / instructed commonly between UEs. That is, the configuration shown in the first embodiment and the configuration shown in the second embodiment may be used (or may be set / applied by switching) based on a predetermined condition.

[0158] The UE may selectively use the configuration shown in the first embodiment and the configuration shown in the second embodiment based on at least one of the following aspects 3-1 to 3-5. The configuration shown in the first embodiment may be selected from at least one of the aspects 1-1 to 1-5. The configuration shown in the second embodiment may be selected from at least one of the aspects 2-1 to 2-5.

[0159] <<Aspect 3-1>> Depending on the type of acknowledgement information transmitted in the PUCCH, a method of setting parameters for repeat transmission of the PUCCH (e.g., UE-specific or UE-common) may be used. For example, depending on whether a configuration in which ACK / NACK is fed back (e.g., ACK / NACK feedback) is applied as acknowledgement information for a multicast PDSCH, or a configuration in which only NACK is fed back (e.g., NACK-only feedback) is applied, the method may be used.

[0160] As an example, the second embodiment (for example, aspect 2-2) may be applied when only NACK is fed back, and the first embodiment (for example, aspect 1-3) may be applied when ACK / NACK is fed back. Of course, the applicable aspects are not limited to this.

[0161] When ACK / NACK is fed back, a parameter suitable for each UE (e.g., the number of times of PUCCH repeated transmission) can be set by setting a parameter of PUCCH repeated transmission separately for each UE. When only NACK is fed back, a parameter of PUCCH repeated transmission is set commonly between UEs, so that NACK feedback can be performed using a common PUCCH resource between multiple UEs.

[0162] "Aspect 3-2" A method of setting parameters for PUCCH repetitive transmission (e.g., UE-specific or UE-common) may be used depending on a predetermined condition used in communication. The predetermined condition may be at least one of a higher layer parameter, a MAC CE, a DCI format, a DCI field, a PDCCH-scrambling RNTI, a control resource set, a search space set, and a UE capability.

[0163] "Aspect 3-3" A method of setting parameters for PUCCH repeated transmission (e.g., UE-specific or UE-common) may be used depending on the PTM (Point-to-Multipoint) transmission method. For example, the second embodiment (e.g., aspect 2-2) may be applied to the PTM transmission method 1, and the first embodiment (e.g., aspect 1-3) may be applied to the PTM transmission method 2. Of course, the applicable aspects are not limited to this.

[0164] "Aspect 3-4" Depending on whether a PUCCH resource configuration (eg, PUCCH resource configuration) is configured in common between UEs, a method of configuring a parameter for repeated transmission of the PUCCH (eg, UE-specific or UE-common) may be used differently.

[0165] For example, the second embodiment (for example, aspect 2-2) may be applied when the PUCCH resource configuration is configured commonly between UEs, and the first embodiment (for example, aspect 1-3) may be applied when the PUCCH resource configuration is not configured commonly between UEs. Of course, the applicable aspects are not limited to this.

[0166] Alternatively, the second embodiment (for example, aspect 2-2) may be applied when the PUCCH resource configuration is not commonly configured between UEs, and the first embodiment (for example, aspect 1-3) may be applied when the PUCCH resource configuration is commonly configured between UEs. Of course, the applicable aspects are not limited to this.

[0167] Aspect 3-5 Depending on whether the PUCCH resource used by the UE is configured in common between UEs, a method of configuring the parameters for the repeated transmission of the PUCCH (for example, UE-specific or UE-common) may be used differently.

[0168] For example, the second embodiment (e.g., aspect 2-2) may be applied when the PUCCH resources used by each UE are configured in common between the UEs, and the first embodiment (e.g., aspect 1-3) may be applied when the PUCCH resources used by each UE are not configured in common between the UEs. Of course, the applicable aspects are not limited to this.

[0169] Alternatively, the second embodiment (for example, aspect 2-2) may be applied when the PUCCH resources used by each UE are not commonly configured between the UEs, and the first embodiment (for example, aspect 1-3) may be applied when the PUCCH resources used by each UE are commonly configured between the UEs. Of course, the applicable aspects are not limited to this.

[0170] <Fourth embodiment> The repeat transmission parameters of the PUCCH corresponding to the retransmitted multicast PDSCH may be determined based on a predetermined condition. The PUCCH corresponding to the retransmitted multicast PDSCH may be read as the PUCCH used for UCI transmission including at least the HARQ-ACK for the retransmitted multicast PDSCH.

[0171] In the following description, a case where a multicast PDSCH is retransmitted is taken as an example, but the present invention may also be applied to a case where a PUCCH is retransmitted. In this case, the PUCCH corresponding to the multicast PDSCH at the time of initial transmission may correspond to the PUCCH at the time of initial transmission, and the PUCCH corresponding to the multicast PDSCH at the time of retransmission may correspond to the PUCCH at the time of retransmission.

[0172] The UE may determine the parameters of the repeat transmission of the PUCCH corresponding to the retransmitted multicast PDSCH based on at least one of the first to third embodiments. In this case, the same method as the method of determining the parameters of the repeat transmission of the PUCCH corresponding to the multicast PDSCH that is the first transmission may be applied. For example, the UE may determine the parameters of the PUCCH corresponding to the retransmitted multicast PDSCH based on the same method as when the multicast PDSCH is received for the first time.

[0173] The parameters for the repeated transmission of the PUCCH corresponding to the retransmitted multicast PDSCH may be implicitly indicated for each UE. For example, the parameters for the repeated transmission of the PUCCH corresponding to the retransmitted multicast PDSCH (e.g., the number of repetitions) may be determined based on the parameters for the repeated transmission of the PUCCH corresponding to the initially transmitted multicast PDSCH (e.g., the number of repetitions).

[0174] The number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission may be associated with the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission so as to be the same (see FIG. 8A). For example, if the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission is Y, the UE may apply Y as the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission.

[0175] Furthermore, when the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission is 1, the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission may be associated with 1, and when the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission is greater than 1 (>1), the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission may be associated with a value greater than 1 (>1). In this case, the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission and the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission may be associated differently.

[0176] When the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission and the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission are associated differently, a predetermined conversion rule may be defined, or the conversion rule may be instructed to each UE by higher layer signaling.

[0177] For example, the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission (or the PUCCH at the time of initial transmission) may be associated with the multicast PDSCH at the time of retransmission so as to be equal to or greater than the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission (or the PUCCH at the time of retransmission) (see FIG. 8B). For example, the configuration of FIG. 8B can be suitably applied when there is a high possibility that the UE can correctly receive the retransmitted multicast PDSCH even if the UE misses receiving the multicast PDSCH at the time of initial transmission.

[0178] Alternatively, the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of retransmission (or the PUCCH at the time of retransmission) may be associated with the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the time of initial transmission (or the PUCCH at the time of initial transmission) (see FIG. 8C). For example, the configuration of FIG. 8C can be suitably applied to reduce retransmission errors (or to transmit retransmissions more safely) when the UE misses receiving the multicast PDSCH at the time of initial transmission.

[0179] (Variations) Each embodiment may be applied in combination. For example, the first embodiment (e.g., aspect 1-4) and the second embodiment (e.g., aspect 2-2) may be applied in combination. In this case, a parameter (or multiple parameter candidates) may be set commonly between UEs for each PUCCH format (e.g., PUCCH-FormatConfig) in a certain PUCCH configuration (e.g., PUCCHConfig), and a specific parameter may be indicated for each UE based on MAC CE / DCI. In this way, a parameter common to multiple UEs is set by higher layer signaling, and a parameter for each UE is set by MAC CE / DCI, thereby making it possible to flexibly set a parameter for each UE.

[0180] (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 of the wireless communication methods according to the above embodiments of the present disclosure or a combination of these methods.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0206] (base station) 10 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 one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0223] The transceiver 120 may transmit a multicast Physical Downlink Shared Channel (PDSCH).

[0224] The control unit 110 may control transmission of information to be applied to repeated transmission of a physical uplink control channel (PUCCH) for transmitting acknowledgement information for a multicast PDSCH.

[0225] (User terminal) 11 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 transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0242] The transceiver 220 may receive a multicast Physical Downlink Shared Channel (PDSCH).

[0243] The control unit 110 may control repeated transmission of a physical uplink control channel (PUCCH) for transmitting acknowledgement information for a multicast PDSCH based on information notified from a network (for example, a base station).

[0244] At least one of the parameters related to repeated transmission of the PUCCH may be set separately for each terminal (first embodiment).

[0245] At least one of the parameters related to repeated transmission of the PUCCH may be set commonly to a plurality of terminals (second embodiment).

[0246] The control unit 110 may separately determine a first parameter related to the repeated transmission of the PUCCH for the initial transmission of the multicast PDSCH and a second parameter related to the repeated transmission of the PUCCH for the retransmission of the multicast PDSCH (fourth embodiment).

[0247] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0261] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0309] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

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

[0311] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0312] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

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

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

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

[0316] 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 receiver for receiving information related to multicast, the information including at least one parameter related to frequency hopping and a number of repetitions of a physical uplink control channel (PUCCH), and a multicast physical downlink shared channel (PDSCH); and a control unit that controls repeated transmission of the PUCCH for transmitting delivery acknowledgement information for the multicast PDSCH based on information related to the multicast.

2. A terminal as described in claim 1, characterized in that at least one of the parameters relating to the frequency hopping and the number of repetitions is set separately for each terminal.

3. The terminal according to claim 1 , wherein a parameter related to the number of repetitions for the repeated transmission of the PUCCH is set for each resource of the PUCCH.

4. A step of receiving information related to multicast, the information including at least one parameter related to frequency hopping and a number of repetitions of a physical uplink control channel (PUCCH) and a multicast physical downlink shared channel (PDSCH); and controlling repeated transmission of the PUCCH for transmitting delivery acknowledgement information for the multicast PDSCH based on information related to the multicast.

5. A transmitter for transmitting information related to multicast, the information including at least one parameter related to frequency hopping and a number of repetitions of a physical uplink control channel (PUCCH), and a multicast physical downlink shared channel (PDSCH); a control unit that controls transmission of information related to the multicast, which is applied to repeated transmission of the PUCCH for transmitting delivery acknowledgement information for the multicast PDSCH.

6. A system including a terminal and a base station, The terminal includes: A receiving unit that receives information related to multicast, the information including at least one parameter related to frequency hopping and a repetition number of a physical uplink control channel (PUCCH), and a multicast physical downlink shared channel (PDSCH); A control unit that controls repeated transmission of the PUCCH for transmitting delivery acknowledgement information for the multicast PDSCH based on information about the multicast, The base station, A transmission unit that transmits information related to the multicast and the PDSCH; A control unit that controls transmission of information related to the multicast and the PDSCH.