Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit configured to receive a multicast physical downlink shared channel (PDSCH), and a control unit configured to control repeated transmission of a physical uplink control channel (PUCCH) for transmitting acknowledgement information for the multicast PDSCH, based on information notified from a base station.

Description

Technical Field

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. Background Technology

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300V8.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

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., NR), it is envisioned that multiple user terminals (user terminals, user equipment (UE)) communicate in an environment with ultra-high density and high traffic volume.

[0009] In NR, we envision an environment where downlink data using multicast / broadcast / downlink shared channels is transmitted to multiple UEs.

[0010] However, the communication control for downlink data transmission using multicast has not been adequately studied in the NR specifications to date. If communication control for downlink data transmission utilizing multicast is not properly implemented, there are concerns about reduced system performance, such as decreased throughput.

[0011] Therefore, one of the purposes of this disclosure is to provide a means of appropriately controlling the communication terminal, wireless communication method, and base station even when multicast downlink data transmission is being performed.

[0012] Methods for solving problems

[0013] The terminal involved in one aspect of this disclosure is characterized by having: a receiving unit for receiving a multicast physical downlink shared channel (PDSCH); and a control unit for controlling the repeated transmission of a physical uplink control channel (PUCCH) for transmitting delivery confirmation information for the multicast PDSCH based on information notified from a base station.

[0014] The effects of the invention

[0015] According to one aspect of this disclosure, communication can be appropriately controlled even when multicast downlink data transmission is being performed. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating an example of PTM transmission mode 1.

[0017] Figure 2 This is a diagram illustrating an example of PTM transmission mode 2.

[0018] Figure 3 This is a diagram illustrating an example of the transmission of the PUCCH corresponding to the multicast PDSCH.

[0019] Figure 4 This is a diagram illustrating an example of repeated transmission control of the PUCCH corresponding to the multicast PDSCH according to the first embodiment.

[0020] Figures 5A-5CThis is a diagram illustrating an example of the correspondence between the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH in the first embodiment.

[0021] Figure 6 This is a diagram illustrating an example of repeated transmission control of the PUCCH corresponding to the multicast PDSCH according to the second embodiment.

[0022] Figures 7A-7C This is a diagram illustrating an example of the correspondence between the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH in the second embodiment.

[0023] Figures 8A-8C This is a diagram illustrating an example of the correspondence between the number of repetitions of the PUCCH corresponding to the initially transmitted multicast PDSCH and the number of repetitions of the PUCCH corresponding to the retransmitted multicast PDSCH, as described in the fourth embodiment.

[0024] Figure 9 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0025] Figure 10 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0026] Figure 11 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0027] Figure 12 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. Detailed Implementation

[0028] (PUCCH format)

[0029] In future wireless communication systems (e.g., Rel.15 and later, 5G, NR, etc.), the structure (also called format, PUCCH format (PF), etc.) of the uplink control channel (e.g., PUCCH) used in the transmission of uplink control information (UCI) is being studied. For example, in Rel.15NR, support for five types of PF0 to 4 is being studied. Furthermore, the names of the PFs shown below are merely illustrative and different names may be used.

[0030] For example, PF0 and PF1 are PFs used in the transmission of UCIs of 2 bits or less (up to 2 bits). For example, the UCI can also be at least one of a delivery acknowledgment message (also known as Hybrid Automatic Repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgment (ACK), or negative-acknowledgment (NACK)) and a scheduling request (SR). PF0 can be assigned to 1 or 2 symbols, and is therefore also called a short PUCCH or a sequence-based short PUCCH. On the other hand, PF1 can be assigned to 4-14 symbols, and is therefore also called a long PUCCH. PF0 can also transmit a sequence obtained by cyclically shifting a base sequence using a cyclic shift based on at least one of the initial cyclic shift (CS) index, the value of the UCI, the slot number, and the symbol number. In PF1, multiple user terminals can also be code-division multiplexed (CDM) within the same physical resource block (PRB) by using time-domain block extensions of at least one of CS and time-domain (TD) orthogonal cover code (OCC).

[0031] PF2-4 are PFs used in the transmission of more than 2 bits of UCI (e.g., Channel State Information (CSI) or at least one of CSI, HARQ-ACK, and SR). PF2 can be assigned to 1 or 2 symbols, and is therefore also called short PUCCH, etc. On the other hand, PF3 and PF4 can be assigned to 4-14 symbols, and are therefore also called long PUCCH, etc. In PF4, multiple user terminals can also be CDMed using pre-DFT (Frequency Domain (FD)-OCC) block expansion.

[0032] Intra-slot frequency hopping can also be applied to PF1, PF3, and PF4. The length of the PUCCH is set to N. symb The length before the frequency hopping (first hop) can also be floor(N) symb / 2), the length after the frequency hopping (second hop) can also be ceil(N symb / 2).

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

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

[0035] Furthermore, in NR, the number of symbols allocated to the PUCCH (also referred to as PUCCH allocation symbols, PUCCH symbols, etc.) can be determined by any one or a combination of time slot-specific, cell-specific, and user terminal-specific factors. Since it is expected that increasing the number of PUCCH symbols will extend the communication distance (coverage), for example, the following application is envisioned: the further the user terminal is from the base station (e.g., eNB, gNB), the more symbols are added.

[0036] (HARQ-ACK Feedback)

[0037] In NR, a mechanism is being studied for user terminal (user equipment) feedback (also known as report or send, etc.) of delivery confirmation information (also known as Hybrid Automatic Repeat reQuest-ACKknowledge (HARQ-ACK), ACKknowledge / Non-ACK (ACK / NACK), HARQ-ACK information or A / N, etc.) for downlink shared channel (also known as physical downlink shared channel (PDSCH)).

[0038] For example, in NR Rel.15, the value of a specific field within the DCI (e.g., DCI format 1_0 or 1_1) used in PDSCH scheduling represents the feedback timing of the HARQ-ACK for that PDSCH. If the UE transmits a HARQ-ACK for a PDSCH received in time slot #n+k in time slot #n, the value of this specific field can also be mapped to the value of k. This specific field is, for example, referred to as the PDSCH-HARQ feedback timing indicator field.

[0039] Furthermore, in NR Rel.15, the PUCCH resource used in the HARQ-ACK feedback for a PDSCH is determined based on the value of a specific field within the DCI (e.g., DCI format 1_0 or 1_1) used in the PDSCH scheduling. This specific field may also be referred to as the PUCCH resource indicator (PRI) field, the ACK / NACK resource indicator (ARI) field, etc. The value of this specific field may also be referred to as PRI, ARI, etc.

[0040] The PUCCH resources mapped to the values ​​of this specific field can also be pre-configured to the UE via higher-level parameters (e.g., ResourceList within PUCCH-ResourceSet). Furthermore, the PUCCH resources can also be configured to the UE for each set (PUCCH resource set) containing more than one PUCCH resource.

[0041] Furthermore, in NR Rel.15, it is being studied that UEs do not expect to transmit more than one uplink control channel (Physical Uplink Control Channel (PUCCH)) with HARQ-ACK in a single time slot.

[0042] Specifically, in NR Rel.15, more than one HARQ-ACK in a single time slot can also be mapped to a single HARQ-ACK codebook, which is transmitted via the PUCCH resource indicated by the most recent (last) DCI.

[0043] Here, the HARQ-ACK codebook can also be composed of HARQ-ACK bits in at least one unit of the time domain (e.g., time slot), frequency domain (e.g., component carrier (CC)), spatial domain (e.g., layer), transport block (TB), and code block group (CBG) constituting the TB. Additionally, CC is also referred to as cell, serving cell, carrier, etc. Furthermore, this bit is also referred to as HARQ-ACK bit, HARQ-ACK information, or HARQ-ACK information bit, etc.

[0044] The HARQ-ACK codebook is also known as the PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), codebook, HARQ codebook, HARQ-ACK size, etc.

[0045] The number of bits (size) in a HARQ-ACK codebook can be determined semi-statically or dynamically. A semi-static HARQ-ACK codebook is also called a Type-1 HARQ-ACK codebook or a semi-static codebook. A dynamic HARQ-ACK codebook is also called a Type-2 HARQ-ACK codebook or a dynamic codebook.

[0046] The type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook can also be set in the UE via a higher-level parameter (e.g., pdsch-HARQ-ACK-Codebook).

[0047] In the case of a Type 1 HARQ-ACK codebook, the UE can also feed back HARQ-ACK bits corresponding to a specific range (e.g., a range set based on higher-layer parameters) regardless of whether PDSCH scheduling is present or not.

[0048] This specific range can also be determined based on at least one of the following: a specific period (e.g., a specific number of opportunities (occasions) for becoming a candidate PDSCH receiver, or a specific number of monitoring opportunities (monitoring occasions) for PDCCH); the number of CCs set or activated for the UE; the number of TBs (layers or ranks); the number of CBGs per 1TB; and the presence or absence of spatially bound applications. This specific range is also referred to as the HARQ-ACK binding window, HARQ-ACK feedback window, binding window, feedback window, etc.

[0049] In the Type 1 HARQ-ACK codebook, if within a certain range, the UE will feed back NACK bits even without PDSCH scheduling for the UE. Therefore, when using the Type 1 HARQ-ACK codebook, it is also assumed that the number of HARQ-ACK bits fed back will increase.

[0050] On the other hand, in the case of a type 2 HARQ-ACK codebook, the UE can also feed back HARQ-ACK bits for the scheduled PDSCH within the aforementioned specific range.

[0051] Furthermore, if the UE is not configured to transmit based on a code block group (CBG) (with HARQ-ACK codebook determination based on CBG) via higher-layer parameters (PDSCH code block group transmission information element, PDSCH-CodeBlockGroupTransmission), the UE envisions transmitting based on a transport block (TB) (with HARQ-ACK codebook determination based on TB). That is, the UE generates HARQ-ACK information bits for each TB.

[0052] When higher-layer parameters of the PDSCH code block group transmission information element are provided for the serving cell (component carrier (CC)), the UE receives a PDSCH containing multiple CBGs within one TB. The PDSCH code block group transmission information element contains the maximum number of CBGs within one TB (maxCodeBlockGroupsPerTransportBlock). For the TB reception of the serving cell, the UE generates HARQ-ACK information bits for each of the multiple CBGs and generates a HARQ-ACK codebook containing the maximum number of HARQ-ACK information bits for each CBG.

[0053] The UE may also use at least one of the uplink control channel (Physical Uplink Control Channel (PUCCH)) and the uplink shared channel (Physical Uplink Shared Channel (PUSCH)) to send one or more HARQ-ACK bits determined (generated) based on the HARQ-ACK codebook of type 1 or type 2 above.

[0054] (NR Multicast / Broadcast)

[0055] In NR up to Rel.16, the transmission of at least one of the signals and channels (hereinafter referred to as signals / channels) from the NW to the UE is essentially unicast transmission. In this case, it is envisioned that each UE uses multiple reception opportunities (reception timings) corresponding to multiple beams (or panels) of the NW to receive the same downlink (DL) data signals / channels (e.g., downlink shared channel (PDSCH)) transmitted from the NW to multiple UEs.

[0056] Furthermore, in extremely high-density and high-traffic environments such as geographically dense UEs (e.g., stadiums), consider the scenario where multiple UEs simultaneously receive the same signal / channel. In this case, multiple UEs exist in the same area, each receiving the same signal / channel. Therefore, while unicast reception of the signal / channel by each UE can ensure communication reliability, it reduces resource utilization efficiency.

[0057] The structure for group scheduling for multicast / broadcast service (MBS) to be received in multiple UEs is under investigation.

[0058] For example, research is underway on scheduling multicast PDSCH using more than one DCI. In this case, there is a concern that the size of the DCI (payload size, overhead) will increase.

[0059] In Point-to-Point (PTP) transmission (publishing method), the RAN node (e.g., a base station) wirelessly transmits individual copies of MBS data packets to each UE. In Point-to-Multipoint (PTM) transmission (publishing method), the RAN node (e.g., a base station) wirelessly transmits a single copy of the MBS data packets to a set of UEs. PTP transmission can also be referred to as unicast transmission.

[0060] Investigating: PTP transmission for multiple RRC-connected UEs (RRC_CONNECTED UEs), using UE-specific PDCCH for scheduling UE-specific PDSCH, and UE-specific PDCCH having cyclic redundancy check (CRC) scrambled by UE-specific radionetwork temporary identifier (RNTI) (e.g., C-RNTI), and UE-specific PDSCH being scrambled using the same UE-specific RNTI.

[0061] Under investigation: PTM transmission mode 1 for multiple RRC connected UEs within the same MBS group, using a group-common PDCCH for scheduling group-common PDSCH, and the group-common PDCCH having a CRC scrambled via a group-common RNTI, the group-common PDSCH being scrambled using the same group-common RNTI. Figure 1 ).

[0062] Under investigation: PTM transmission method 2 for multiple RRC-connected UEs within the same MBS group, using UE-specific PDCCH for scheduling group common PDSCH, and the UE-specific PDCCH having a CRC scrambled by UE-specific RNTI (e.g., C-RNTI), while the group common PDSCH is scrambled using the group common RNTI. Figure 2 ).

[0063] Here, a UE-specific PDCCH / PDSCH can be identified by the target UE, but not by other UEs within the same MBS group. Group-wide PDCCH / PDSCH can be transmitted in the same time / frequency resources and identified by all UEs within the same MBS group.

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

[0065] For RRC-connected UEs receiving multicast, at least PTM transmission mode 1 can also support at least one of the following feedback methods 1 and 2.

[0066] [Feedback Method 1] Based on HARQ-ACK feedback for multicast ACK / NACK (ACK / NACK based HARQ-ACK feedback, ACK / NACK based PUCCH, ACK / NACK transmission, ACK / NACK feedback, HARQ-ACK information containing ACK or NACK)

[0067] A UE that successfully decodes the PDSCH sends an ACK. A UE that fails to decode the PDSCH sends a NACK.

[0068] [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 containing only NACK)

[0069] A UE that successfully decodes the PDSCH does not send an ACK. A UE that fails to decode the PDSCH sends a NACK.

[0070] (Send repeatedly)

[0071] In Rel.15, repeated transmission is supported during data transmission. For example, the base station (network (NW), gNB) can also repeatedly transmit DL data (e.g., downlink shared channel (PDSCH)) a specific number of times. Alternatively, the UE can also repeatedly transmit UL control channel (e.g., uplink control channel (PUCCH)) or UL data (e.g., uplink shared channel (PUSCH)) a specific number of times.

[0072] The number of repetitions is also called the repetition factor (K), aggregation factor (K), or time slot number (N). PUCCH repeat Furthermore, the nth repetition can also be referred to as the nth transmission opportunity (transmission occasion), etc. The UE can also semi-statically receive information related to the number of PUCCH repetitions via higher-layer signaling (e.g., nrofSlots).

[0073] In Rel.15, when repeated transmission is applied to the PUCCH corresponding to the unicast PDSCH, the parameters for repeated PUCCH transmission are set via higher-layer signaling. Repeated PUCCH transmission can also be referred to as PUCCH repetition.

[0074] Based on the repeated transmission of PUCCH, an improvement in network-side reception quality can be expected. However, in the current Rel.15 / 16NR, PUCCH transmission corresponding to unicast PDSCH is supported, but PUCCH transmission corresponding to multicast PDSCH is not supported. Therefore, in Rel.17 and later, when multicast PDSCH is supported, how to control the repeated transmission of PUCCH corresponding to the multicast PDSCH (e.g., application presence or parameter settings, etc.) becomes a problem (see...). Figure 3 ).

[0075] There are concerns that repeated transmissions may occur if the PUCCH used for HARQ-ACK transmission corresponding to the multicast PDSCH is not properly applied / configured, leading to a decrease in throughput.

[0076] Therefore, the inventors of this invention studied the UE operation for repeated transmission of PUCCH corresponding to multicast PDSCH and came up with this embodiment.

[0077] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0078] In this disclosure, "A / B / C" and "at least one of A, B, and C" can be substituted for each other. In this disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band domain can also be substituted for each other. In this disclosure, index, ID, indicator, and resource ID can also be substituted for each other. In this disclosure, support, control, capable of control, operation, and capable of operation can also be substituted for each other.

[0079] In this disclosure, configure, activate, update, indicate, enable, specify, and select can also be used interchangeably.

[0080] In this disclosure, the terms use, determine, apply, and select can be used interchangeably.

[0081] In this disclosure, the terms link, associate, correspond, and map can be used interchangeably. Similarly, allocate, assign, monitor, and map can also be used interchangeably.

[0082] In this disclosure, higher-layer signaling may be any one or a combination of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc. In this disclosure, RRC, RRC signaling, RRC parameters, higher layers, higher-layer parameters, RRC information elements (IEs), and RRC messages may also be used interchangeably.

[0083] MAC signaling can also use MAC Control Element (MAC CE) or MAC Protocol Data Unit (PDU). Broadcast information can also be, for example, Master Information Block (MIB), System Information Block (SIB), Remaining Minimum System Information (RMSI), or Other System Information (OSI).

[0084] In this disclosure, MAC CE and activation / deactivation commands can be used interchangeably.

[0085] In this disclosure, PUCCH, PUSCH, repeat, and transmission timing can be interchanged.

[0086] In this disclosure, multicast, broadcast, and MBS can be used interchangeably. In this disclosure, multicast PDSCH and PDSCH scrambled via group common RNTI can also be used interchangeably.

[0087] In this disclosure, delivery confirmation information, HARQ-ACK, HARQ-ACK / NACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, NACK, NACK only, and UCI can also be used interchangeably.

[0088] In this disclosure, the terms specific, dedicated, UE-specific, and UE-dedicated can be used interchangeably.

[0089] In this disclosure, common, shared, group-common, UE common, and UE shared can be used interchangeably.

[0090] In this disclosure, UE-specific DCI and DCI with CEC scrambled via UE-specific RNTI can be interchanged. UE-specific RNTI can also be, for example, C-RNTI.

[0091] In this disclosure, the UE common DCI and the DCI with CEC scrambled via the UE common RNTI can be interchanged. The UE common RNTI can also be, for example, a multicast-RNTI.

[0092] In this disclosure, the broadcast (cast) type of PDSCH can also indicate whether PDSCH is unicast or multicast.

[0093] In this disclosure, mapping HARQ-ACK information to PUSCH, multiplexing HARQ-ACK information and data (UL-SCH) on PUSCH, and sending HARQ-ACK information on PUSCH can also be interchanged. Similarly, mapping HARQ-ACK information to PUCCH, multiplexing HARQ-ACK information and other UCIs on PUCCH, and sending HARQ-ACK information on PUCCH can also be interchanged.

[0094] (Wireless communication method)

[0095] The UE receiving the multicast PDSCH can also be controlled to perform specific operations in response to repeated PUCCH transmissions. The UE receiving the multicast PDSCH can also be a UE with specific higher-layer parameters set (e.g., higher-layer parameters related to the multicast PDSCH) or a UE with the capability to receive the multicast PDSCH.

[0096] Specific operations can also apply PUCCH repetition (e.g., PUCCHRepetition) to the PUCCH corresponding to the multicast PDSCH (specific operation 1). The PUCCH corresponding to the multicast PDSCH can also be replaced with a PUCCH used for sending HARQ-ACK information for that multicast PDSCH.

[0097] Repeated transmission of PUCCH can also involve repeatedly transmitting the same uplink control information in the time domain (e.g., UCI). The time domain can also be different based on symbol units / slot units (e.g., TDM). Whether slot-based repetition (inter-slot repetition) or symbol-based repetition (intra-slot repetition) is applied can be defined in the specification or set by the base station to the UE via higher-layer signaling, etc.

[0098] Repeated PUCCH transmissions can also be replaced by the transmission of a single PUCCH that is encoded / extended across multiple time / frequency / spatial domains using a single UCI.

[0099] The repeated transmission of PUCCH described in this specification can also be applied to PUCCH, where the PUCCH transmission includes at least a UCI for delivery confirmation information for multicast PDSCH. Whether the delivery confirmation information is accompanied by ACK / NACK feedback or NACK-only feedback can be configured by the base station to the UE via higher-layer signaling / DCI. UEs configured for NACK-only only require control to ensure that only NACK feedback is provided.

[0100] The UE can also control the retransmission of the PUCCH to occur when it is configured to retransmit the PUCCH corresponding to the multicast PDSCH, and not to retransmit the PUCCH when it is not configured to retransmit the PUCCH corresponding to the multicast PDSCH. The retransmission of the PUCCH can also be configured by the base station to the UE through higher-layer parameters, etc.

[0101] Alternatively, a specific operation could be to prevent the application of PUCCH repetition to the PUCCH corresponding to the multicast PDSCH (specific operation 2). In this case, the UE may also not anticipate / expect the application of repetitive transmission in the PUCCH corresponding to the multicast PDSCH.

[0102] The following describes the method for applying specific operation 1. Each implementation method can be applied individually or in combination.

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

[0104] Repetition types can be either slot-based (e.g., repetition type A) or symbol-based (e.g., repetition type B). Repetition type A can be controlled in the same way as PUSCH repetition type A, and repetition type B can be controlled in the same way as PUSCH repetition type B.

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

[0106] Furthermore, the repeated transmission of PUCCH corresponding to multicast PDSCH will be described in the following description, but this embodiment is not limited thereto. Settings (e.g., parameters of PUCCH resources) applied to the PUCCH resources corresponding to multicast PDSCH / repeated transmission of PUCCH resources can also be used. The parameters of repeated transmission of PUCCH can also be replaced with the parameters of PUCCH resources.

[0107] <First Implementation>

[0108] When repeated transmissions are applied in the PUCCH corresponding to the multicast PDSCH, some or all of the parameters related to the repeated transmissions of that PUCCH can also be set / indicated for each UE (see reference). Figure 4 ).

[0109] exist Figure 4 The diagram shows a scenario where multicast PDSCH (or group common PDSCH) is scheduled via UE-specific PDCCH, but it can also be scheduled via UE common PDCCH.

[0110] exist Figure 4 In this specification, the settings of some or all of the parameters related to repeated transmission can also be based on at least one of the following methods 1-1 to 1-5. The parameters related to repeated transmission can also be replaced with the conditions applied in repeated transmission.

[0111] Furthermore, in the following description, the number of repetitions (e.g., the number of repetitions) is used as an example, at least for each UE, as a parameter related to repetition, but is not limited to this. It can also be applied to other parameters (e.g., parameters related to repetition on / off, parameters related to frequency hopping, and at least one parameter related to repetition type).

[0112] The parameters related to PUCCH retransmission, such as the retransmission count (e.g., nrofSlots) and other parameters, can be set per UE, or other parameters besides the retransmission count can be set publicly by the UE. The retransmission count can also include 1, which indicates that retransmission is not applied. In this case, the setting of the retransmission count (1 or other values) can also indicate to the UE whether the application of retransmission is specified.

[0113] Method 1-1

[0114] Parameters related to repeated transmissions can also be set per PUCCH. PUCCH settings can also be set via higher layers (PUCCH-Config). PUCCH settings can also be set individually for each UE, each UL portion bandwidth (ULBWP), or each component carrier (CC).

[0115] The UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the parameters related to repeated transmission contained in a certain PUCCH setting.

[0116] Alternatively, parameters related to repeated transmissions can be set individually for each UL BWP or each CC.

[0117] Methods 1-2

[0118] Parameters related to repeated transmission can also be set as each of the specific parameters in a PUCCH setting (PUCCH-Config). Specific parameters can also be parameters related to the PUCCH format (e.g., PUCCH-FormatConfig).

[0119] The base station can also individually configure parameters related to repeated transmission (e.g., nrofSlots) for each PUCCH format (e.g., PUCCH-FormatConfig) included in the PUCCH configuration. The UE can also individually control the repeated transmission of PUCCH (e.g., number of transmissions) for each applied PUCCH format.

[0120] In this scenario, when a PUCCH resource set containing more than one PUCCH resource is configured, the number of repetitions / retransmissions is the same for a specific PUCCH format across these resources. For example, consider the following situation: 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 a repetition count K is set for that specific PUCCH format. In this case, the UE controls the application to ensure that the same repetition count K is applied to PUCCH resource A and PUCCH resource B.

[0121] Therefore, in each UE, parameters related to repetition can be set for each PUCCH format (PUCCH format unit).

[0122] In parameters related to the PUCCH format (e.g., PUCCH-FormatConfig), in addition to parameters related to the number of repetitions, other parameters may be included. In this case, all parameters included in PUCCH-FormatConfig can also be set individually for each UE. Alternatively, some parameters included in PUCCH-FormatConfig can be set commonly among UEs.

[0123] Methods 1-3

[0124] Parameters related to repeated transmissions can also be set for each of the specific parameters in a PUCCH configuration (PUCCH-Config). Specific parameters can also be parameters associated with a PUCCH resource / PUCCH resource set (e.g., PUCCH-Resource / PUCCH-ResourceSet).

[0125] The base station can also individually configure parameters related to repeated transmission (e.g., nrofSlots) for each PUCCH resource (e.g., PUCCH-Resource) / PUCCH resource set (e.g., PUCCH-ResourceSet) included in the PUCCH configuration. The UE can also individually control the repeated transmission of PUCCH (e.g., number of transmissions) for each applied PUCCH resource / PUCCH resource set.

[0126] In parameters related to PUCCH resources / PUCCH resource sets (e.g., PUCCH-Resource / PUCCH-ResourceSet), in addition to parameters related to the number of iterations, other parameters may also be included. In this case, all parameters included in the PUCCH-Resource / PUCCH-ResourceSet can also be set individually for each UE. Alternatively, a subset of the parameters included in the PUCCH-Resource / PUCCH-ResourceSet can be set publicly among UEs.

[0127] By setting the transmission parameters for each PUCCH resource / PUCCH resource set, different parameters can be set for PUCCH resources / PUCCH resource sets that use the same PUCCH format.

[0128] Methods 1-4

[0129] Parameters associated with repeated transmissions may also be indicated per UE based on at least one of MAC control information (e.g., MAC CE) and DCI (or DCI field).

[0130] [MAC CE]

[0131] Parameters related to the repeated transmission of PUCCH can also be indicated to each UE using the MAC CE in the multicast PDSCH. In this case, the MAC CE transmitted via the multicast PDSCH can also contain indications for each UE. Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the MAC CE in the multicast PDSCH.

[0132] By including parameters (e.g., MAC CE) related to the transmission of the PUCCH corresponding to the multicast PDSCH in the multicast PDSCH, it is possible to notify the user of these parameters without sending additional signals / channels.

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

[0134] By including the parameters (e.g., MAC CE) associated with the transmission of the PUCCH corresponding to the multicast PDSCH in a different channel (e.g., unicast PDSCH), the increase in multicast PDSCH overhead can be suppressed.

[0135] [DCI field]

[0136] Parameters related to repeated PUCCH transmissions can also be indicated to each UE using the DCI corresponding to the multicast PDSCH. In this case, the DCI corresponding to the multicast PDSCH can also contain indications for each UE. For example, parameters related to repeated PUCCH transmissions can also be set in a portion of the Time Domain Resource Allocation (TDRA) table used for time domain resource allocation notification / setting of multicast PDSCH.

[0137] Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the DCI corresponding to the multicast PDSCH. In this specification, the DCI corresponding to the multicast PDSCH can also be replaced by the DCI that schedules the multicast PDSCH.

[0138] By including the parameters related to the transmission of the PUCCH corresponding to the multicast PDSCH in the DCI corresponding to the multicast PDSCH, the parameters of the repeated transmission of the PUCCH can be dynamically changed.

[0139] Alternatively, parameters related to repeated PUCCH transmissions can be indicated to each UE using the DCI corresponding to the unicast PDSCH (or UE-specific PDSCH). For example, parameters related to repeated PUCCH transmissions can also be set in a portion of the Time Domain Resource Allocation (TDRA) table used for time domain resource allocation notification / setting of unicast PDSCHs.

[0140] Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the DCI corresponding to its own unicast PDSCH. That is, the UE can also apply the parameters used for transmitting the PUCCH corresponding to the unicast PDSCH to the transmission of the PUCCH corresponding to the multicast PDSCH. The DCI corresponding to the unicast PDSCH can also be the latest / most recent DCI received before the multicast PDSCH is received.

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

[0142] Alternatively, parameters related to the repeated transmission of PUCCH can be indicated to each UE using a DCI common to multiple UEs (e.g., a group common DCI). In this case, the group common DCI can also contain instructions specific to each UE. The group common DCI can be either the DCI format used in TPC command notifications (e.g., DCI format 2_2) or other formats.

[0143] In this way, by setting the transmission parameters (e.g., retransmission parameters) of the PUCCH corresponding to the multicast PDSCH to be individually indicated / notified / set for each UE, it is possible to set or change the presence or absence of retransmission applications / parameters according to the quality of each UE.

[0144] Methods 1-5

[0145] Parameters related to repeated transmissions can also be implicitly indicated on a per-UE basis. For example, parameters related to repeated transmissions of the PUCCH for each UE can also be set corresponding to specific conditions / specific parameters.

[0146] Specific conditions / parameters can also be conditions / parameters applied in multicast PDSCH, for example. In this case, specific conditions / parameters can also be set from the base station to the UE using higher-layer signaling / DCI.

[0147] As an example, the number of repetitions of the PUCCH corresponding to the multicast PDSCH can also be associated with the number of repetitions of the multicast PDSCH. The association between the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH corresponding to the multicast PDSCH can also be set / defined individually for each UE.

[0148] The number of repetitions of a multicast PDSCH and the number of repetitions of the corresponding PUCCH can also be associated as the same (see reference). Figure 5A For example, if the number of repetitions of a multicast PDSCH is X, the UE can also use X as the number of repetitions of the PUCCH corresponding to that multicast PDSCH.

[0149] Alternatively, when the repetition count of the multicast PDSCH is 1, association 1 can be used as the repetition count of the PUCCH corresponding to that multicast PDSCH; when the repetition count of the multicast PDSCH is greater than 1 (>1), association with a value greater than 1 (>1) can be used as the repetition count of the PUCCH corresponding to that multicast PDSCH. In this case, the repetition count of the multicast PDSCH and the repetition count of the PUCCH corresponding to that multicast PDSCH can also be associated differently.

[0150] When the number of repetitions of a multicast PDSCH and the number of repetitions of the corresponding PUCCH are associated differently, either a specific transition rule can be defined, or the transition rule can be indicated to each UE via higher-layer signaling (see reference). Figure 5B ).exist Figure 5BThe following situation is shown: some of the multiple repetitions of the multicast PDSCH (here, 1, 2, 4, 8) are associated with the repetition of the PUCCH in the same way as the repetition of the PUCCH, while the other repetitions (here, 4, 3) are associated with the repetition of the PUCCH in a different way.

[0151] exist Figure 5B The diagram illustrates a case where multiple repetitions of a multicast PDSCH are associated with a repetition count greater than or equal to the repetition count of the corresponding PUCCH. In this case, the repetition count can be set to suit a TDD structure with multiple deep layers (e.g., heavy deep layers). Furthermore, it can also be appropriately applied to cases where the PUCCH quality is better than the PDSCH.

[0152] Alternatively, multiple repetitions of the multicast PDSCH can be associated with a number of repetitions of the corresponding PUCCH (e.g., refer to...). Figure 5C The above structure can also be appropriately applied to situations where the quality of PDSCH is better than that of PUCCH.

[0153] For the conditions / parameters applied in the multicast PDSCH, parameters applied to the repeatedly transmitted PUCCH corresponding to the multicast PDSCH are associated, thereby suppressing the increase of information notified to the UE.

[0154] <Second Implementation>

[0155] When repeated transmissions are applied in the PUCCH corresponding to the multicast PDSCH, some or all of the parameters related to the repeated transmissions can also be set / indicated publicly among the UEs (see [reference]). Figure 6 ).

[0156] exist Figure 6 The diagram shows a scenario where multicast PDSCH (or group common PDSCH) is scheduled via UE-specific PDCCH, but it can also be scheduled via UE common PDCCH.

[0157] exist Figure 6 In this context, the setting of some or all of the parameters related to repeated transmission can also be performed based on at least one of the following methods 2-1 to 2-5.

[0158] Furthermore, in the following description, the number of repetitions (e.g., repetition count) is used as an example of parameters related to repetition, but it is not limited to this. It is possible that the repetition count parameter (e.g., nrofSlots) and other parameters related to PUCCH repetition are all set for each UE, or that other parameters besides the repetition count are set commonly by the UE.

[0159] Method 2-1

[0160] Parameters related to repeated transmissions can also be set per PUCCH. PUCCH settings can also be set via higher layers (PUCCH-Config). PUCCH settings can also be set individually for each UE, each UL portion bandwidth (ULBWP), or each component carrier (CC).

[0161] When a PUCCH setting is configured for each UE, the base station can also control the setting so that the same values ​​are set for parameters related to repeated PUCCH transmission. Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the repeated transmission-related parameters included in a certain PUCCH setting.

[0162] Alternatively, parameters related to repeated transmissions can be set individually for each UL BWP or each CC.

[0163] Method 2-2

[0164] Parameters related to repeated transmission can also be set as each of the specific parameters in a PUCCH setting (PUCCH-Config). Specific parameters can also be parameters related to the PUCCH format (e.g., PUCCH-FormatConfig).

[0165] The base station can also individually configure parameters related to repeated transmission (e.g., nrofSlots) for each PUCCH format (e.g., PUCCH-FormatConfig) included in the PUCCH configuration. The UE can also individually control the repeated transmission of PUCCH (e.g., number of transmissions) for each applied PUCCH format.

[0166] In this scenario, when a PUCCH resource set containing more than one PUCCH resource is configured, the same number of repetitions / retransmissions is applied for a specific PUCCH format within these resources. For example, consider the following situation: PUCCH resource A in PUCCH resource set #1 and PUCCH resource B in PUCCH resource set #2 correspond to a specific PUCCH format, and a repetition count K is set for that specific PUCCH format. In this case, the UE controls the application to ensure that the same repetition count K is applied to PUCCH resource A and PUCCH resource B.

[0167] Therefore, among UEs, parameters related to repetition can be set for each PUCCH format (PUCCH format unit).

[0168] In parameters related to the PUCCH format (e.g., PUCCH-FormatConfig), in addition to parameters related to the number of repetitions, other parameters may be included. In this case, all parameters included in PUCCH-FormatConfig can be set publicly among UEs. Alternatively, a subset of the parameters included in PUCCH-FormatConfig can be set individually for each UE.

[0169] Methods 2-3

[0170] Parameters related to repeated transmissions can also be set for each specific parameter in a PUCCH configuration (PUCCH-Config). Specific parameters can also be parameters related to PUCCH resources / PUCCH resource sets (e.g., PUCCH-Resource / PUCCH-ResourceSet).

[0171] The base station can also individually configure parameters related to repeated transmission (e.g., nrofSlots) for each PUCCH resource (e.g., PUCCH-Resource) / PUCCH resource set (e.g., PUCCH-ResourceSet) included in the PUCCH configuration. The UE can also individually control the repeated transmission of PUCCH (e.g., number of transmissions) for each applied PUCCH resource / PUCCH resource set.

[0172] In parameters related to PUCCH resources / PUCCH resource sets (e.g., PUCCH-Resource / PUCCH-ResourceSet), in addition to parameters related to the number of iterations, other parameters may also be included. In this case, all parameters included in the PUCCH-Resource / PUCCH-ResourceSet can also be set individually for each UE. Alternatively, a subset of the parameters included in the PUCCH-Resource / PUCCH-ResourceSet can be set publicly among UEs.

[0173] When parameters related to repeated transmission are set publicly among UEs for each PUCCH resource / PUCCH resource set, the presence / number of repeated PUCCH transmissions can be controlled based on the quality of each UE by setting PUCCH resources individually for each UE.

[0174] By setting the transmission parameters for each PUCCH resource / PUCCH resource set, different parameters can be set for PUCCH resources / PUCCH resource sets that use the same PUCCH format.

[0175] Methods 2-4

[0176] Parameters related to repeated transmissions may also be publicly indicated among UEs based on at least one of MAC control information (e.g., MAC CE) and DCI (or DCI field).

[0177] [MAC CE]

[0178] Parameters related to the repeated transmission of PUCCH can also be indicated to each UE using the MAC CE in the multicast PDSCH. In this case, the MAC CE transmitted via the multicast PDSCH can also contain indications common to all UEs. Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the MAC CE in the multicast PDSCH.

[0179] The MAC CE sent via multicast PDSCH includes common indications for the UE, thereby suppressing the increase in multicast PDSCH overhead.

[0180] [DCI field]

[0181] Parameters related to repeated PUCCH transmissions can also be publicly indicated among UEs using the DCI corresponding to the multicast PDSCH. In this case, the DCI corresponding to the multicast PDSCH can also contain indications common to all UEs. For example, parameters related to repeated PUCCH transmissions can also be set in a portion of the Time Domain Resource Allocation (TDRA) table used in the notification / setting of time domain resource allocation for multicast PDSCHs.

[0182] Each UE can also control the repeated transmission of the PUCCH corresponding to the multicast PDSCH based on the DCI corresponding to the multicast PDSCH.

[0183] By including parameters related to the transmission of the PUCCH corresponding to the multicast PDSCH in the DCI corresponding to the multicast PDSCH as UE common information, the increase in the overhead of the DCI can be suppressed.

[0184] Alternatively, parameters related to the repeated transmission of PUCCH can be indicated to each UE using a DCI common to multiple UEs (e.g., a group common DCI). In this case, the group common DCI can also contain indications specific to each UE.

[0185] In this way, by setting a structure that publicly indicates / notifies / sets the transmission parameters (e.g., repetitive transmission parameters) of the PUCCH corresponding to the multicast PDSCH among UEs, the increase in overhead can be suppressed.

[0186] Methods 2-5

[0187] Parameters related to repeated transmissions can also be implicitly indicated on a per-UE basis. For example, parameters related to repeated transmissions of the PUCCH for each UE can also be set corresponding to specific conditions / specific parameters.

[0188] Specific conditions / parameters can also be conditions / parameters applied in multicast PDSCH, for example. In this case, specific conditions / parameters can also be set from the base station to the UE using higher-layer signaling / DCI.

[0189] As an example, the number of repetitions of the PUCCH corresponding to the multicast PDSCH can also be associated with the number of repetitions of the multicast PDSCH. The association between the number of repetitions of the multicast PDSCH and the number of repetitions of the PUCCH corresponding to the multicast PDSCH can also be set / defined publicly among UEs.

[0190] The number of repetitions of a multicast PDSCH and the number of repetitions of the corresponding PUCCH can also be associated as the same (see reference). Figure 7AFor example, if the number of repetitions of a multicast PDSCH is X, the UE can also use X as the number of repetitions of the PUCCH corresponding to that multicast PDSCH.

[0191] Alternatively, when the repetition count of the multicast PDSCH is 1, association 1 can be used as the repetition count of the PUCCH corresponding to that multicast PDSCH; when the repetition count of the multicast PDSCH is greater than 1 (>1), association with a value greater than 1 (>1) can be used as the repetition count of the PUCCH corresponding to that multicast PDSCH. In this case, the repetition count of the multicast PDSCH and the repetition count of the PUCCH corresponding to that multicast PDSCH can also be associated differently.

[0192] When the number of repetitions of a multicast PDSCH and the number of repetitions of the corresponding PUCCH are associated differently, either a specific transition rule can be defined, or the transition rule can be indicated to each UE via higher-layer signaling (see reference). Figure 7B ).exist Figure 7B The following situation is shown: some of the multiple repetitions of the multicast PDSCH (here, 1, 2, 4, 8) are associated with the repetition of the PUCCH in the same way as the repetition of the PUCCH, while the other repetitions (here, 4, 3) are associated with the repetition of the PUCCH in a different way.

[0193] exist Figure 7B The diagram illustrates a case where multiple repetitions of a multicast PDSCH are associated with a repetition count greater than or equal to the repetition count of the corresponding PUCCH. In this case, the repetition count can be set to suit a TDD structure with multiple deep layers (e.g., multiple deep layers). Furthermore, it can also be appropriately applied to cases where the PUCCH quality is better than the PDSCH.

[0194] Alternatively, multiple repetitions of the multicast PDSCH can be associated with a number of repetitions of the PUCCH corresponding to that multicast PDSCH (e.g., refer to...). Figure 7C The above structure can also be appropriately applied to situations where the quality of PDSCH is better than that of PUCCH.

[0195] For the conditions / parameters applied in the multicast PDSCH, the parameters applied to the repeatedly transmitted PUCCH corresponding to the multicast PDSCH are associated, thereby suppressing the increase of information notified to the UE.

[0196] <Third Implementation Method>

[0197] Some or all of the parameters related to the repeated transmission of the PUCCH corresponding to the multicast PDSCH can be set / indicated individually for each UE based on specific conditions, or can be set / indicated commonly among UEs. That is, the structures shown in the first embodiment and the second embodiment can also be used separately (or switchedly set / applied) based on specific conditions.

[0198] The UE can also use the structure shown in the first embodiment and the structure shown in the second embodiment, respectively, based on at least one of the following methods 3-1 to 3-5. The structure shown in the first embodiment can also be selected from at least one of methods 1-1 to 1-5. The structure shown in the second embodiment can also be selected from at least one of methods 2-1 to 2-5.

[0199] Method 3-1

[0200] Based on the category / type of the delivery confirmation information sent in the PUCCH, the method for setting the parameters of repeated transmission of the PUCCH (e.g., UE-specific or UE-common) can also be used separately. For example, as a delivery confirmation information for multicast PDSCH, it can also be used based on whether an ACK / NACK structure is applied (e.g., ACK / NACK feedback) or a NACK-only structure is applied (e.g., NACK only, NACK-only feedback).

[0201] As an example, the second implementation method (e.g., method 2-2) can be applied when only a NACK is received, and the first implementation method (e.g., method 1-3) can be applied when both ACK and NACK are received. Of course, the methods applied are not limited to these.

[0202] When receiving an ACK / NACK response, parameters suitable for each UE (e.g., the number of times the PUCCH is repeatedly transmitted) can be set individually for each UE by configuring the parameters for repeated PUCCH transmission on a per-UE basis. When only receiving a NACK response, NACK feedback can be performed across multiple UEs by setting the parameters for repeated PUCCH transmission publicly among UEs, utilizing shared PUCCH resources.

[0203] Method 3-2

[0204] The method for setting parameters for repeated PUCCH transmissions (e.g., UE-specific or UE-common) can also be used based on specific conditions utilized in the communication. Specific conditions can also be at least one of the following: higher-layer parameters, MAC CE, DCI format, DCI fields, PDCCH-scrambling RNTI, control resource set, search space set, and UE capability.

[0205] Method 3-3

[0206] Based on the PTM (Point-to-Multipoint) transmission method, the method for setting the parameters of repeated PUCCH transmissions (e.g., UE-specific or UE-common) can also be used separately. For example, the second implementation method (e.g., method 2-2) can be applied in the case of PTM transmission method 1, and the first implementation method (e.g., method 1-3) can be applied in the case of PTM transmission method 2. Of course, the methods applied are not limited to these.

[0207] Methods 3-4

[0208] Depending on whether the PUCCH resource configuration (e.g., PUCCH resource configuration) is set publicly among UEs, the method for setting the parameters of the repeatedly transmitted PUCCH (e.g., UE-specific or UE-public) can also be used separately.

[0209] For example, the second implementation method (e.g., method 2-2) can be applied when the PUCCH resource settings are commonly set among UEs, and the first implementation method (e.g., method 1-3) can be applied when the PUCCH resource settings are not commonly set among UEs. Of course, the methods applied are not limited to these.

[0210] Alternatively, the second implementation method (e.g., method 2-2) can be applied when the PUCCH resource settings are not commonly set among UEs, and the first implementation method (e.g., method 1-3) can be applied when the PUCCH resource settings are commonly set among UEs. Of course, the methods applied are not limited to these.

[0211] Methods 3-5

[0212] Depending on whether the PUCCH resources used by the UE are set publicly among UEs, the method for setting the parameters of the repeatedly transmitted PUCCH (e.g., UE-specific or UE-public) can also be used separately.

[0213] For example, the second implementation method (e.g., method 2-2) can be applied when the PUCCH resources used by each UE are commonly configured among the UEs, and the first implementation method (e.g., method 1-3) can be applied when the PUCCH resources used by each UE are not commonly configured among the UEs. Of course, the methods applied are not limited to these.

[0214] Alternatively, the second implementation method (e.g., method 2-2) can be applied when the PUCCH resources used by each UE are not publicly configured among UEs, and the first implementation method (e.g., method 1-3) can be applied when the PUCCH resources used by each UE are publicly configured among UEs. Of course, the methods applied are not limited to these.

[0215] <Fourth Implementation>

[0216] The parameters for the repeated transmission of the PUCCH corresponding to the retransmitted multicast PDSCH can also be determined based on specific conditions. The PUCCH corresponding to the retransmitted multicast PDSCH can also be replaced with the PUCCH used in a UCI transmission that includes at least a HARQ-ACK for the retransmitted multicast PDSCH.

[0217] Furthermore, the following explanation uses the case of a retransmission of the multicast PDSCH as an example, but it can also be applied to the case of a retransmission of the PUCCH. In this case, the PUCCH corresponding to the initial multicast PDSCH can also correspond to the initial PUCCH, and the PUCCH corresponding to the retransmission multicast PDSCH can also correspond to the retransmission PUCCH.

[0218] The UE can also determine the parameters for the repeated 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 for determining the parameters for the repeated transmission of the PUCCH corresponding to the first-transmission multicast PDSCH can also be applied. For example, the UE can also determine the parameters for the PUCCH corresponding to the retransmitted multicast PDSCH based on the same method as when the multicast PDSCH is first received.

[0219] Parameters related to the repeated transmission of the PUCCH corresponding to the retransmitted multicast PDSCH can also be implicitly indicated on a per UE basis. For example, parameters (e.g., number of retransmissions) of the PUCCH corresponding to the retransmitted multicast PDSCH can also be determined based on the parameters (e.g., number of retransmissions) of the PUCCH corresponding to the initially transmitted multicast PDSCH.

[0220] The number of repetitions of the PUCCH corresponding to the initial multicast PDSCH and the number of repetitions of the PUCCH corresponding to the retransmitted multicast PDSCH can also be associated with the same number (see reference). Figure 8A For example, if the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the initial transmission is Y, the UE can also use Y as the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the retransmission.

[0221] Furthermore, if the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the initial transmission is 1, then association 1 can be used as the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the retransmission. If the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the initial transmission is greater than 1 (>1), then the value greater than 1 (>1) can be used as the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the retransmission. In this case, the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the initial transmission and the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the retransmission can also be associated differently.

[0222] When the number of repetitions of the PUCCH corresponding to the multicast PDSCH during the initial transmission is different from the number of repetitions of the PUCCH corresponding to the multicast PDSCH during retransmission, either a specific transformation rule can be defined, or the transformation rule can be indicated to each UE through higher-layer signaling.

[0223] For example, association can also be performed by making the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the initial transmission (or the PUCCH at the initial transmission) greater than the number of repetitions of the PUCCH corresponding to the multicast PDSCH at the retransmission (or the PUCCH at the retransmission) (see [reference]). Figure 8B For example, even if the UE fails to receive the initial multicast PDSCH, it can still appropriately apply the technology if there is a high probability that the retransmitted multicast PDSCH can be received correctly. Figure 8B The structure.

[0224] Alternatively, the association can be made in such a way that the number of repetitions of the PUCCH corresponding to the multicast PDSCH during retransmission (or the PUCCH during retransmission) is greater than or equal to the number of repetitions of the PUCCH corresponding to the multicast PDSCH during initial transmission (or the PUCCH during initial transmission) (see [reference]). Figure 8C For example, even in the event of a reception error in the initial multicast PDSCH transmission, the UE can appropriately apply measures to reduce retransmission errors (or to ensure a more secure retransmission). Figure 8C The structure.

[0225] (change)

[0226] The various implementation methods can also be combined. For example, the first implementation method (e.g., methods 1-4) and the second implementation method (e.g., methods 2-2) can also be combined. In this case, parameters (or multiple parameter candidates) can be set publicly among UEs according to each of the PUCCH formats (e.g., PUCCH-FormatConfig) in a certain PUCCH setting (e.g., PUCCHConfig), and specific parameters can be indicated for each UE based on MAC CE / DCI. In this way, common parameters can be set among multiple UEs via higher-layer signaling, and UE-specific parameters can be set via MAC CE / DCI, thereby enabling flexible parameter setting for each UE.

[0227] (Wireless Communication System)

[0228] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0229] Figure 9 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 can also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP).

[0230] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also 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)), etc.

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

[0232] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity of NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0233] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration and number of each cell and the user terminal 20 are not limited to the arrangement shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0234] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

[0235] Each CC can also be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). Macro cell C1 can also be included in FR1, and small cell C2 can also be included in FR2. For example, FR1 can also be a frequency band below 6 GHz (sub-6 GHz), and FR2 can also be a frequency band above 24 GHz (above-24 GHz). Furthermore, the frequency bands and definitions of FR1 and FR2 are not limited to these; for example, FR1 can also be equivalent to a frequency band higher than FR2.

[0236] In addition, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) to communicate in each CC.

[0237] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, base station 11, which is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

[0238] Base station 10 may also be connected to core network 30 via other base stations 10 or directly. Core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0239] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

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

[0241] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0242] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared by each user terminal 20.

[0243] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

[0244] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. Furthermore, the Master Information Block (MIB) can also be transmitted via the PBCH.

[0245] Lower-layer control information can also be transmitted via PDCCH. Lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0246] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can also be replaced with DL data, and PUSCH can also be replaced with UL data.

[0247] In PDCCH detection, a Control Resource Set (CORESET) and a search space can be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0248] A search space can also correspond to one or more PDCCH candidates equivalent to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" used in this disclosure can be used interchangeably.

[0249] Uplink control information (UCI) including at least one of Channel State Information (CSI), delivery confirmation information (such as Hybrid Automatic Repeat reQuest ACK knowledgement (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR) can also be transmitted via PUCCH. Random access preambles used for establishing a connection with the cell can also be transmitted via PRACH.

[0250] Furthermore, in this disclosure, downlink, uplink, etc., may be described without the word "link". Additionally, various channels may be described without the word "physical".

[0251] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. As DL-RS, wireless communication system 1 can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), phase tracking reference signals (PTRS), etc.

[0252] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. Furthermore, SS, SSB, etc., can also be called reference signals.

[0253] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, the DMRS can also be referred to as a user terminal-specific reference signal (UE-specific reference signal).

[0254] (Base station)

[0255] Figure 10 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0256] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it can also be envisioned that the base station 10 also possesses other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0257] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0258] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0259] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 can be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0260] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0261] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0262] The transmitting / receiving unit 120 can also transmit the aforementioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 can also receive the aforementioned uplink channel, uplink reference signal, etc.

[0263] The transmitting and receiving unit 120 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

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

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

[0266] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0267] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0268] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0269] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also 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 can also be output to the control unit 110.

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

[0271] In addition, the transmitting unit and receiving unit of the base station 10 in this disclosure may also be composed of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0272] The transmitting and receiving unit 120 can also transmit the multicast physical downlink shared channel (PDSCH).

[0273] The control unit 110 can also control the transmission of information used in the repeated transmission of the Physical Uplink Control Channel (PUCCH) for sending delivery confirmation information for the multicast PDSCH.

[0274] (User terminal)

[0275] Figure 11 This diagram illustrates an example of the structure of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0276] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0277] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0279] The transmitting / receiving unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0280] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0281] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0282] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

[0283] The transmitting and receiving unit 220 may also use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc., to form at least one of the transmitting beam and the receiving beam.

[0284] The transmitting and receiving unit 220 (transmitting processing unit 2211) may, for example, perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) on the data and control information obtained from the control unit 210, and generate the bit string to be transmitted.

[0285] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output the baseband signal.

[0286] Furthermore, the application of DFT processing can be based on the transform precoding settings. For a specific channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above for transmitting the channel using the DFT-s-OFDM waveform. Otherwise, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above without performing DFT processing.

[0287] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0288] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, and demodulate the baseband signal for the wireless frequency band signal received by the transmitting and receiving antenna 230.

[0289] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data.

[0290] The transmitting / receiving unit 220 (measurement unit 223) can also perform measurements related to the received signal. For example, the measurement unit 223 can also perform RRM measurements, CSI measurements, etc., based on the received signal. The measurement unit 223 can also 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 can also be output to the control unit 210.

[0291] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0292] The transmitting and receiving unit 220 can also receive the multicast physical downlink shared channel (PDSCH).

[0293] The control unit 110 can also control the repeated transmission of the physical uplink control channel (PUCCH) for sending delivery confirmation information for multicast PDSCH based on information notified from the network (e.g., a base station).

[0294] At least one of the parameters associated with the repeated transmission of PUCCH can also be set individually for each terminal (first implementation).

[0295] At least one parameter associated with the repeated transmission of PUCCH can also be set publicly in multiple terminals (second embodiment).

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

[0297] (Hardware Structure)

[0298] Furthermore, the block diagrams used in the description of the above embodiments illustrate functional units. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Moreover, the implementation method of each functional block is not particularly limited. That is, each functional block can be implemented using a single device that is physically or logically combined, or it can be implemented by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. A functional block can also be implemented by combining the aforementioned single device or multiple devices with software.

[0299] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method is not particularly limited.

[0300] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 12 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0301] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0302] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0303] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 can perform calculations and control communication via the communication device 1004, or control at least one of reading out and writing data in the memory 1002 and the storage device 1003.

[0304] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0305] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and performs various processes accordingly. As a program, a program that causes the computer to perform at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and operated in the processor 1001; similar implementations can be made for other functional blocks.

[0306] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0307] Storage device 1003 may also be a computer-readable recording medium, such as comprising at least one of the following: flexible disc, floppy disk, optical disk (e.g., compact disc ROM, CD-ROM, etc.), digital multifunction disk, Blu-ray disc, removable disk, hard disk, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0308] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0309] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., touch panel).

[0310] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses between the devices.

[0311] Furthermore, the base station 10 and the user terminal 20 can also be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field-programmable gate array (FPGA), and can be used to implement some or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0312] (Modified Example)

[0313] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Additionally, a signal may also be a message. A reference signal may also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0314] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0315] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0316] In the time domain, a time slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). Furthermore, a time slot can also be a time unit based on a set of parameters.

[0317] A time slot can also contain multiple mini-time slots. Each mini-time slot can also consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

[0318] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols used in this disclosure can be used interchangeably.

[0319] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0320] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0321] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0322] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also serve as the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0323] A TTI with a duration of 1 ms can also be referred to as a normal TTI (TTI in 3GPP Rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI can also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a mini time slot, a sub-time slot, a time slot, etc.

[0324] In addition, long TTIs (e.g., normal TTIs, subframes, etc.) can be replaced with TTIs with a duration of more than 1 ms, and short TTIs (e.g., shortened TTIs, etc.) can be replaced with TTIs with a duration of less than long TTIs but more than 1 ms.

[0325] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can also contain one or more consecutive subcarriers. The number of subcarriers in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers in an RB can also be determined based on the parameter set.

[0326] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0327] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0328] Furthermore, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0329] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0330] A BWP can also include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). For a UE, one or more BWPs can also be set within a single carrier.

[0331] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, terms such as "cell" and "carrier" in this disclosure can be replaced with "BWP".

[0332] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0333] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0334] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0335] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0336] Furthermore, information, signals, etc., can be output in at least one of the following directions: from higher level (upper layer) to lower level (lower layer), and from lower layer to higher level. Information, signals, etc., can also be input and output via multiple network nodes.

[0337] Input and output information, signals, etc., can be stored in a specific location (e.g., memory) or managed using management tables. Input and output information, signals, etc., can be overwritten, updated, or appended. Output information, signals, etc., can also be deleted. Input information, signals, etc., can also be sent to other devices.

[0338] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), higher layer signaling (e.g., radio resource control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB) etc.), medium access control (MAC) signaling), other signals, or combinations thereof.

[0339] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC connection setup messages, RRC connection reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, the MAC control element (CE).

[0340] Furthermore, notification of specific information (e.g., a notification that “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0341] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0342] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0343] Furthermore, software, instructions, and information can also be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0344] The terms “system” and “network” as used in this disclosure are used interchangeably. “Network” may also mean devices included in a network (e.g., base stations).

[0345] In this disclosure, the terms "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", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" are used interchangeably.

[0346] In this disclosure, the terms "Base Station (BS)", "Wireless 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", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0347] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0348] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "user equipment (UE)", and "terminal" are used interchangeably.

[0349] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0350] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. This mobile body can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and the mobile station also includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0351] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be replaced with sidelink channel.

[0352] Similarly, the user terminal in this disclosure can also be replaced by a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0353] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network containing one or more network nodes having a base station, various operations for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0354] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, with respect to the methods described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0355] The various methods / implementations described in this disclosure can also be applied to 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 This includes 802.11 (Wi-Fi, registered trademark), IEEE 802.16 (WiMAX, registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0356] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0357] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0358] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching in a table, database, or other data structure), and ascertaining.

[0359] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0360] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". In other words, "judgment (decision)" can also refer to certain actions as situations where a "judgment (decision)" is made.

[0361] In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0362] The term "maximum transmit power" as used in this disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0363] As used in this disclosure, the terms "connected," "coupled," or any variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually "connected" or "coupled" elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, "connected" can also be replaced with "access."

[0364] In this disclosure, when two elements are connected, it is possible to use more than one wire, cable, printed electrical connection, etc., and to use electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, light (both visible and invisible) region as several non-limiting and non-inclusive examples, so that they are "connected" or "combined" with each other.

[0365] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0366] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0367] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0368] The invention disclosed herein has been described in detail above. However, it will be apparent to those skilled in the art that the invention is not limited to the embodiments described herein. The invention can be implemented with modifications and variations without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes only and is not intended to limit the invention in any way.

Claims

1. A terminal, characterized in that, have: The receiving unit receives multicast-related information and the multicast physical downlink shared channel (PDSCH). The multicast-related information includes both parameters related to the frequency hopping and repetition count of the physical uplink control channel (PUCCH). as well as The control unit, based on the multicast-related information, controls the repeated transmission of the PUCCH used to send delivery confirmation information for the multicast PDSCH. Both the parameters related to the frequency hopping and the number of repetitions are set individually for each terminal.

2. The terminal as described in claim 1, characterized in that, The parameters related to the number of repetitions for the repeated transmission of the PUCCH are set for each resource of the PUCCH that is repeatedly transmitted.

3. A wireless communication method for a terminal, characterized in that, have: The steps of receiving multicast-related information and the multicast physical downlink shared channel (PDSCH), wherein the multicast-related information includes both parameters related to the frequency hopping and repetition count of the physical uplink control channel (PUCCH); and Based on the multicast-related information, the step of repeatedly sending the PUCCH for sending delivery confirmation information for the multicast PDSCH is controlled. Both the parameters related to the frequency hopping and the number of repetitions are set individually for each terminal.

4. A base station, characterized in that, have: The transmitting unit transmits multicast-related information and the multicast physical downlink shared channel (PDSCH), wherein the multicast-related information includes both parameters related to the frequency hopping and repetition count of the physical uplink control channel (PUCCH). as well as A control unit controls the transmission of the multicast-related information, which is used in the repeated transmission of the PUCCH for sending delivery confirmation information for the multicast PDSCH. Both the parameters related to the frequency hopping and the number of repetitions are set individually for each terminal.

5. A system comprising a terminal and a base station, The terminal has: The receiving unit receives multicast-related information and the multicast physical downlink shared channel (PDSCH), wherein the multicast-related information includes both parameters related to the frequency hopping and repetition count of the physical uplink control channel (PUCCH); and The control unit, based on the multicast-related information, controls the repeated transmission of the PUCCH used to send delivery confirmation information for the multicast PDSCH. Both the parameters related to the frequency hopping and the number of repetitions are set individually for each terminal. The base station has: The sending unit sends the multicast-related information and the PDSCH; and The control unit controls the transmission of the multicast-related information and the PDSCH.

Images