Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present disclosure comprises: a control unit for determining the transmission power of physical uplink control channels (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for multicast physical downlink shared channels (PDSCH), on the basis of at least one of an upper-layer parameter and a transmission power control (TPC) command; and a transmission unit for transmitting the PUCCH using the transmission power. According to one embodiment of the present disclosure, the transmission power of downlink control channels for multicast downlink data can be appropriately determined.

Description

[Technical field]

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

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

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

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

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

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

[0007] However, in the NR specifications up to now, the transmission power of the downlink control channel for multicast downlink data from the UE has not been sufficiently considered. If the transmission power is not appropriately determined, there is a risk of degradation in system performance, such as deterioration of communication quality and reduction in throughput.

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

[0009] A terminal according to one aspect of the present disclosure a receiving unit for receiving first downlink control information (DCI) that schedules a unicast physical downlink shared channel (PDSCH) and includes a transmit power control (TPC) command field, and a receiving unit for receiving second downlink control information (DCI) that schedules a multicast PDSCH and does not include a TPC command field; Ruchicast Top DSC h associated with H The transmission power of the Physical Uplink Control Channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information is , the T included in the first DCI P C Man The cumulative value shown in the and a transmission unit that transmits the PUCCH using the transmission power. Effect of the Invention

[0010] According to one aspect of the present disclosure, the transmission power of a downlink control channel for multicast downlink data can be appropriately determined. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing an example of a PTM transmission method 1. [Diagram 2] FIG. 2 is a diagram showing an example of the PTM transmission method 2. [Diagram 3] 3A and 3B are diagrams showing an example of a TPC command according to aspect 1-1. [Figure 4] FIG. 4 is a diagram showing an example of a TPC command according to aspect 1-2. [Diagram 5] FIG. 5 is a diagram illustrating an example of a PUCCH configuration according to aspect 4a-1. [Figure 6] FIG. 6 is a diagram illustrating an example of a PUCCH configuration according to aspect 4a-2. [Figure 7] FIG. 7 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

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

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

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

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

[0019] (PUCCH power control) In NR, the transmission power of the PUCCH is controlled based on the TPC command (also called a value, an increment / decrement value, a correction value, an instruction value, etc.) indicated by the value of a field in the DCI (also called a TPC command field, a first field, etc.).

[0020] For example, the index l of the power control adjustment state (PUCCH power control adjustment state) is used to calculate the PUCCH transmission power (P PUCCH、b,f,c (i,qu ,q d ,l))[dBm] is P CMAX,f,c (i), P O_PUCCH,b,f,c (q u ), M PUCCH RB,b,f,c (i), P.L. b,f,c (q d ), Δ F_PUCCH (F), Δ TF,b,f,c (i), g b,f,c (i, l), the power control adjustment state may be referred to as a TPC command-based value of power control adjustment state index l, an accumulated value of TPC commands, or a closed-loop value. l may be referred to as a closed-loop index.

[0021] Furthermore, a PUCCH transmission opportunity i is a period during which a PUCCH is transmitted, and may be composed of, for example, one or more symbols, one or more slots, and so on.

[0022] P PUCCH、b,f,c (i,q u ,q d , l) may be expressed by the following formula (1):

number

[0023] P CMAX,f,c (i) is, for example, the transmission power of the user equipment (also called maximum transmission power, UE maximum output power, etc.) set for carrier f of serving cell c at transmission opportunity i. O_PUCCH,b,f,c (q u ) is, for example, a parameter related to a target received power set for an active UL BWP b of a carrier f of a serving cell c at a transmission opportunity i (e.g., a parameter related to a transmit power offset, also referred to as a transmit power offset P0 or a target received power parameter, etc.).

[0024] M PUCCH RB,b,f,c(i) is the number of resource blocks (bandwidth) allocated to PUCCH for transmission opportunity i in active UL BWP b of carrier f with serving cell c and subcarrier spacing μ. b,f,c (q d ) is, for example, an index q of a reference signal for a downlink BWP (path loss reference RS, path loss reference RS, DL-RS for path loss measurement, PUCCH-PathlossReferenceRS) associated with an active UL BWP b of a carrier f of a serving cell c. d is the path loss (path loss estimate [dB], path loss compensation) calculated at the user terminal using

[0025] If the UE is not provided with pathloss reference RSs (pathlossReferenceRSs) or before the UE is provided with dedicated higher layer parameters, the UE shall calculate the pathloss PL using RS resources obtained from the SS / PBCH block that the UE uses to acquire the MIB. b,f,c (q d ) to calculate

[0026] If the UE is given pathloss reference RS information (pathlossReferenceRSs in PUCCH power control information (PUCCH-PowerControl)) and not given PUCCH spatial relation information (PUCCH-SpatialRelationInfo), the UE obtains the value of the reference signal in the pathloss reference RS for PUCCH from the pathloss reference RS-ID for PUCCH (PUCCH-PathlossReferenceRS-Id) with index 0 in the pathloss reference RS information for PUCCH (PUCCH-PathlossReferenceRS). The resource of this reference signal is either on the same serving cell or on the serving cell indicated by the value of the pathloss reference association information (pathlossReferenceLinking), if given. The pathloss reference association information indicates which DL the UE applies as a pathloss reference: a special cell (SpCell) or a secondary cell (SCell) corresponding to this UL. The SpCell may be a primary cell (PCell) in a master cell group (MCG) or a primary secondary cell (PSCell) in a secondary cell group (SCG). The path loss reference RS information indicates a set of reference signals (e.g., CSI-RS configurations or SS / PBCH blocks) used for PUCCH path loss estimation.

[0027] Δ F_PUCCH (F) is a higher layer parameter given for each PUCCH format. Δ TF,b,f,c (i) is the transmission power adjustment component (offset) for UL BWP b of carrier f of serving cell c.

[0028] g b,f,c(i,l) is the TPC command-based value (e.g., power control adjustment state, accumulated value of TPC commands, value by closed loop, PUCCH power adjustment state) of the power control adjustment state index l of the active UL BWP of carrier f of serving cell c and transmission opportunity i. For example, g b,f,c (i,l) is δ PUCCH,b,f,c It may be based on.

[0029] g b,f,c (i, l) may be expressed by the following equation (2).

number

[0030] Here, δ PUCCH,b,f,c (i,l) is a TPC command value, which may be included in DCI format 1_0 or DCI format 1_1 detected by the UE in PUCCH transmission opportunity i of active UL BWP b of carrier f of serving cell c, or may be jointly coded with other TPC commands in DCI format 2_2 with CRC scrambled by a specific Radio Network Temporary Identifier (RNTI) (e.g., TPC-PUSCH-RNTI). PUCCH,b,f,c may be a cumulative value (e.g., -1, 0, 1, or 3) that maps to the value of the TCI command field.

[0031] Σ m=0 C(Ci)-1 δ PUCCH,b,f,c (m,l) is the cardinality C(C i ) a set of TPC command values ​​C i It may be the sum of the TPC command values ​​in C i is the K PUCCH transmission opportunity i-i0 of active UL BWP b of carrier f of serving cell c for PUCCH power control adjustment state l of the UE. PUCCH (i-i0)-1 symbols ago and K PUCCH(i) may be the set of TPC command values ​​received between symbols i and i0 for PUSCH transmission opportunity i-i0. PUCCH (i-i0) symbols ago is K of PUSCH transmission opportunity i PUCCH (i) It may be the smallest positive integer that is earlier than the symbol.

[0032] If the PUCCH transmission is in response to detection of DCI format 1_0 or DCI format 1_1 by the UE, K PUCCH (i) may be the number of symbols in the active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUCCH transmission. If the PUCCH transmission is configured by the configured grant configuration information (ConfiguredGrantConfig), then K PUSCH (i) is the number of symbols per slot, N, in the active UL BWP b of carrier f of serving cell c symb slot and the minimum of the value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). PUCCH,min It may be the number of symbols.

[0033] If the UE is provided with information indicating the use of two PUCCH power control adjustment states (twoPUCCH-PC-AdjustmentStates) and PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), l={0,1}; if the UE is not provided with information indicating the use of two power control adjustment states for PUCCH or spatial relationship information for PUCCH, l=0.

[0034] If the UE obtains the TPC command values ​​from DCI format 1_0 or 1_1, and if the UE is provided with PUCCH spatial relation information, the UE may obtain a mapping between the PUCCH spatial relation information ID (pucch-SpatialRelationInfoId) value and the closed-loop index (closedLoopIndex, power adjustment state index l) by an index provided by the P0 ID for PUCCH (p0-PUCCH-Id in p0-Set in PUCCH-PowerControl in PUCCH-Config). If the UE receives an activation command including a value of the PUCCH spatial relation information ID, the UE may determine the value of the closed-loop index that provides the value of l through a link to the corresponding P0 ID for PUCCH.

[0035] If the UE has an active UL BWP b for carrier f in serving cell c, then it has P O_PUCCH,b,f,c (q u ) value setting is provided by a higher layer, b,f,c (i,l)=0, k=0,1,...,i. If the UE is provided with PUCCH spatial relationship information, the UE u Based on the P0 ID for PUCCH corresponding to l, the closed-loop index value corresponding to l, and the PUCCH spatial relationship information associated with q u The value of l may be determined from the value of

[0036] q u may be a P0 ID for PUCCH (p0-PUCCH-Id) indicating P0 for PUCCH (P0-PUCCH) in the P0 set for PUCCH (p0-Set).

[0037] If the UE is not provided with PUCCH spatial relation information (PUCCH-SpatialRelationInfo), the UE derives the P0 value for PUCCH (p0-PUCCH-Value) from the value of P0-ID for PUCCH (p0-PUCCH-Id) that is equal to the minimum value of P0-ID for PUCCH (p0-PUCCH-Id) in the P0 set (p0-Set).

[0038] If the UE is provided with pathloss Reference RSs and not with PUCCH-SpatialRelationInfo, the UE derives the value of referenceSignal in the PUCCH pathloss Reference RS from PUCCH-PathlossReferenceRS-Id with index 0 in PUCCH-PathlossReferenceRS. The derived RS resource is on the primary cell or on the serving cell indicated by the value of pathlossReferenceLinking if pathlossReferenceLinking is provided.

[0039] If the UE is provided with the number of PUCCH power control adjustment states maintained by the UE being two (twoPUCCH-PC-AdjustmentStates) and with PUCCH spatial relationship information, then PUCCH power control adjustment state (closed-loop) index l ∈ {0,1}. If the UE is not provided with the number of PUCCH power control adjustment states maintained by the UE being two or with PUCCH spatial relationship information, then PUCCH power control adjustment state (closed-loop) index l = 0.

[0040] That is, if the UE is not provided with PUCCH spatial relationship information, P0, PL-RS, and closed-loop index are determined according to the rule, in which the smallest P0-ID for PUCCH is applied, PUCCH path loss reference RS-ID=0 is applied, and l=0 is applied.

[0041] In the RRC information element (IE), the PUCCH power control information element (PUCCH-PowerControl) includes a P0 set (p0-Set) which is a set of P0 for PUCCH (P0-PUCCH) and a pathloss reference RS (pathlossReferenceRSs) which is a set of PUCCH pathloss reference RS (PUCCH-PathlossReferenceRS). The P0 for PUCCH includes a P0-ID for PUCCH (P0-PUCCH-Id) and a P0 value for PUCCH (p0-PUCCH-Value). The PUCCH pathloss reference RS includes a PUCCH pathloss reference RS-ID (PUCCH-PathlossReferenceRS-Id) and a reference signal (referenceSignal, SSB index or NZP-CSI-RS resource ID).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] However, the UE operation related to the TPC of the PUCCH for transmitting the HARQ-ACK corresponding to the multicast PDSCH is not clear. For example, the following problems 1 to 4 may occur.

[0056] [Question 1] It is not clear how to handle TPC commands in PTM transmission method 1.

[0057] [Question 2] It is not clear how to accumulate the TPC commands of the PUCCH for transmitting HARQ-ACK corresponding to the unicast PDSCH and the TPC commands of the PUCCH for transmitting HARQ-ACK corresponding to the multicast PDSCH.

[0058] [Question 3] It is unclear how to accumulate TPC commands without feedback when NACK-only feedback is used.

[0059] [Question 4] It is unclear whether open loop power control (OLPC) parameters are shared. For example, it is unclear whether OLPC parameters are shared between a PUCCH for HARQ-ACK transmission corresponding to a unicast PDSCH and a PUCCH for HARQ-ACK transmission corresponding to a multicast PDSCH. For example, it is unclear whether OLPC parameters are shared between an ACK / NACK feedback and a NACK-only feedback.

[0060] If the UE behavior related to the TPC of the PUCCH for transmitting HARQ-ACK corresponding to the multicast PDSCH is not clear, this may result in degradation of communication quality, increased power consumption, and the like.

[0061] Therefore, the present inventors have devised a power control method for multicast PDSCH / unicast PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0078] (Wireless communication method) The UE may determine a transmit power of a PUCCH for transmitting HARQ-ACK information for a multicast PDSCH based on at least one of a higher layer parameter and a TPC command, and transmit the PUCCH using the transmit power.

[0079] <First embodiment> In the PTM transmission method 1, for the TPC command field in the DCI, the UE may follow at least one of the following aspects 1-1 to 1-3.

[0080] [Aspect 1-1] In the DCI that schedules the multicast PDSCH, the TPC command field contains a single TPC command that the UE uses to transmit the PUCCH for HARQ-ACK corresponding to the multicast PDSCH.

[0081] In the example of Figure 3A, the DCI for scheduling the multicast PDSCH for UE #1 and #2 includes a single TPC command, which may be a group-wide DCI.

[0082] The TPC command value corresponding to each code point in the TPC command field may be set for each UE (individually for each UE), in which case different TPC command values ​​can be instructed to multiple UEs by a common TPC command field.

[0083] In the example of Fig. 3B, the TPC command value corresponding to each code point in the TPC command field is set for each UE by a higher layer parameter. The TPC command value for UE#1 and the TPC command value for UE#2 may be different from each other.

[0084] [Aspect 1-2] The TPC command field, or a combination of the TPC command field and other fields, in the DCI scheduling the multicast PDSCH includes multiple TPC commands, one of which is used by the UE for transmitting the PUCCH for HARQ-ACK corresponding to the multicast PDSCH.

[0085] In the example of Fig. 4, the DCI for scheduling the multicast PDSCH for UE#1 and #2 includes a TPC command for UE#1 and a TPC command for UE#2. The DCI may be a group-common DCI.

[0086] The UE may follow either option 1 or 2 below.

[0087] [[Option 1]] Which of the multiple TPC commands is used for transmitting the PUCCH for HARQ-ACK corresponding to the multicast PDSCH may be specified in the specification or may be set by a higher layer parameter. For example, it may be set to use the second of the multiple TPC commands, and the second TPC command may be used for transmitting the PUCCH for HARQ-ACK corresponding to the multicast PDSCH. For example, the DCI includes a block (closed loop indicator and TPC command) with the same structure as the group TPC command (DCI format 2_2), and which of the multiple blocks is used for transmitting the PUCCH for HARQ-ACK corresponding to the multicast PDSCH may be set by a higher layer parameter. The higher layer parameter may be the same as the parameter for DCI format 2_2.

[0088] When an RNTI (for example, TPC-PUCCH-RNTI) used for scrambling the CRC of DCI format 2_2 is set, the RNTI used for scrambling the CRC of that DCI may be set. The RNTI used for scrambling the CRC of that DCI may be associated with the RNTI used for scrambling the CRC of DCI format 2_2, or may be the same as the RNTI used for scrambling the CRC of DCI format 2_2.

[0089] [[Option 2]] Which of the multiple TPC commands to use for transmitting a PUCCH for HARQ-ACK corresponding to a multicast PDSCH may be determined based on at least one of the PUCCH format, UCI payload size, PUCCH resource, PUCCH resource set, and number of symbols of that PUCCH.

[0090] [Aspect 1-3] The DCI that schedules the multicast PDSCH in PTM transmission method 1 does not include a TPC command field.

[0091] The transmission power of the PUCCH for HARQ-ACK corresponding to the multicast PDSCH may be determined based on the group TPC command. It may be specified that a UE capable of PTM transmission method 1 (or multicast PDSCH) must be capable of receiving DCI format 2_2.

[0092] Closed loop power control (CLPC) may not be applied to the PUCCH for HARQ-ACK corresponding to the multicast PDSCH.

[0093] The UE may use the accumulated TPC command value of the PUCCH for HARQ-ACK corresponding to the unicast PDSCH for the PUCCH for HARQ-ACK corresponding to the multicast PDSCH. The UE may assume that the TPC command in the DCI for PTM transmission method 1 is 0.

[0094] According to this embodiment, the TPC in the PTM transmission method 1 becomes clear.

[0095] <Second embodiment> A UE that receives both a TPC command A for PUCCH A for transmitting HARQ-ACK A corresponding to a unicast PDSCH and a TPC command B for PUCCH B for transmitting HARQ-ACK B corresponding to a multicast PDSCH determines the transmission power of each PUCCH according to at least one of the following aspects 2-1 to 2-3.

[0096] [Aspect 2-1] The UE separately accumulates TPC command A and TPC command B. The UE may determine the transmit power of PUCCH A based on the accumulated value of TPC command A, and may determine the transmit power of PUCCH B based on the accumulated value of TPC command B.

[0097] For example, separate values ​​of the PUCCH power control adjustment state (closed-loop index, l) may be used for PUCCH A and PUCCH B. Three or more values ​​of the PUCCH power control adjustment state (0, 1, 2, ...) may be used.

[0098] For example, m in formula (2) may be restricted to the same cast type.

[0099] [Aspect 2-2] The UE may accumulate TPC command A and TPC command B together. The UE may determine the transmit power of PUCCH A and PUCCH B based on the accumulated values ​​of TPC command A and TPC command B.

[0100] For example, for PUCCH A and PUCCH B, the same value of the PUCCH power control adjustment state may be used.

[0101] [Aspect 2-3] The UE uses (decides / applies / selects) either of the aspects 2-1 and 2-2 based on at least one of the following states 1 to 3. [[State 1]] RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / / search space / UE capabilities. [[State 2]] Whether to map (multiplex) HARQ-ACK A and HARQ-ACK B to the same PUCCH. [[State 3]] Whether the PUCCH resource setting for PUCCH A and the PUCCH resource setting for PUCCH B are the same or not.

[0102] According to this embodiment, the method of accumulating the TPC commands of the PUCCH for transmitting HARQ-ACK corresponding to the unicast PDSCH and the TPC commands of the PUCCH for transmitting HARQ-ACK corresponding to the multicast PDSCH becomes clear.

[0103] <Third embodiment> In the case where NACK-only feedback is used, the UE may process TPC commands corresponding to PUCCH transmission occasions for which no PUCCH transmission was performed according to at least one of the following aspects 3-1 to 3-3.

[0104] [Aspect 3-1] The UE includes the TPC commands in the DCI corresponding to that PUCCH transmission in the accumulated transmit power calculation to calculate the transmit power of subsequent PUCCH transmissions. In other words, the UE accumulates the TPC commands in the DCI that indicate the resources for that PUCCH transmission.

[0105] [Aspect 3-2] The UE does not include the TPC commands in the DCI corresponding to that PUCCH transmission in the accumulated transmit power calculation, and calculates the transmit power of subsequent PUCCH transmissions. In other words, the UE does not accumulate the TPC commands in the DCI that indicate the resources of that PUCCH transmission.

[0106] [Aspect 3-3] The UE uses (decides / applies / selects) either of the aspects 3-1 and 3-2 based on at least one of the following states 1 and 2. [[State 1]] RRC parameters / MAC CE / DCI format / DCI fields / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capabilities. [[State 2]] Whether the PUCCH resource is shared among multiple UEs.

[0107] According to this embodiment, when NACK-only feedback is used, the UE can properly process the TPC commands even if no PUCCH is transmitted in the PUCCH transmission occasion.

[0108] <Fourth embodiment> The OLPC parameters of the PUCCH for transmitting HARQ-ACK corresponding to the multi-PDSCH may be in accordance with at least one of the following aspects 4a to 4c. The OLPC parameters may include at least one of P0 (p0-nominal / p0-Set / P0-PUCCH), α (Alpha), pathloss reference RS (pathlossReferenceRSs / PUCCH-PathlossReferenceRS), and offset for each PUCCH format (deltaF-PUCCH-f0 / deltaF-PUCCH-f1 / ...).

[0109] Aspect 4a The OLPC parameters A of PUCCH A for transmitting HARQ-ACK A corresponding to the unicast PDSCH and the OLPC parameters B of PUCCH B for transmitting HARQ-ACK B corresponding to the multicast PDSCH may follow at least one of the following aspects 4a-1 to 4a-5.

[0110] [Aspect 4a-1] Parameter A and parameter B are configured separately. The UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively.

[0111] In the example of FIG. 5, the PUCCH configuration for unicast (PUCCH-Config) includes an OLPC parameter set (e.g., a P0 set (p0-Set), a pathloss reference RS list (pathlossReferenceRSs), etc.) and one or more PUCCH resource sets (PUCCH resource sets #0, #1, ...). Each PUCCH resource set includes one or more PUCCH resources. Each PUCCH resource is associated with a PUCCH spatial relation (PUCCH-SpatialRelationInfo). The PUCCH spatial relation includes an ID of P0 in the P0 set (P0-PUCCH-Id).

[0112] If the number of UCI bits is equal to or less than N0 bits, PUCCH resource set #0 (first PUCCH resource set, PUCCH resource set ID=0) may be used. If the number of UCI bits is greater than N0 and equal to or less than N1 bits, PUCCH resource set #1 (second PUCCH resource set, PUCCH resource set ID=1) may be used. If the number of UCI bits is greater than N1 bits, PUCCH resource set #2 (third PUCCH resource set, PUCCH resource set ID=2) may be used. N0 may be 2. N1 may be set by higher layer signaling or may be a value defined in the specifications.

[0113] In the example of FIG. 5, the PUCCH configuration for multicast includes an OLPC parameter set (e.g., a P0 set (p0-Set), a pathloss reference RS list (pathlossReferenceRSs), etc.) and one or more PUCCH resource sets (PUCCH resource sets #0, #1, ...). Each PUCCH resource set includes one or more PUCCH resources. Each PUCCH resource is associated (by at least one of the PUCCH configuration and the MAC CE) with a PUCCH spatial relation (PUCCH-SpatialRelationInfo). The PUCCH spatial relation includes an ID of P0 in the P0 set (P0-PUCCH-Id).

[0114] [Aspect 4a-2] Parameter A and parameter B are configured as the same (common) parameter. The UE may use the common parameter for both PUCCH A and PUCCH B.

[0115] In the example of FIG. 6, a PUCCH configuration (e.g., PUCCH-Config) common to two cast types includes an OLPC parameter set (e.g., P0 set (p0-Set), pathloss reference RS list (pathlossReferenceRSs), etc.) and one or more PUCCH resource sets (PUCCH resource sets #0, #1, ...). Each PUCCH resource set includes one or more PUCCH resources. Each PUCCH resource is associated with a PUCCH spatial relation (PUCCH-SpatialRelationInfo) (by at least one of the PUCCH configuration and the MAC CE). The PUCCH spatial relation includes an ID (P0-PUCCH-Id) of P0 in the P0 set.

[0116] [Aspect 4a-3] Multiple parameter sets are configured commonly for the two cast types (unicast PDSCH and multicast PDSCH). The UE may use (decide / apply / select) one of the multiple parameter sets based on the RRC parameters / MAC CE / DCI format / DCI field / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capability.

[0117] [Aspect 4a-4] If parameter B is configured (parameters A and B are configured), the UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively. If parameter B is not configured (only parameter A is configured), the UE may use parameter A for PUCCH A and PUCCH B.

[0118] [Aspect 4a-5] The UE uses (decides / applies / selects) either aspect 4a-1 or 4a-2 based on whether the PUCCH resource configuration for PUCCH A and the PUCCH resource configuration for PUCCH B are the same or not.

[0119] According to example 4a, OLPC parameters are made clear for a PUCCH for transmitting HARQ-ACK corresponding to a unicast PDSCH and a PUCCH for transmitting HARQ-ACK corresponding to a multicast PDSCH.

[0120] Aspect 4b For HARQ-ACK transmission corresponding to a multicast PDSCH, the OLPC parameter A related to a UE-specific PUCCH resource configuration and the OLPC parameter B related to a group-common PUCCH resource configuration may be in accordance with at least one of the following aspects 4b-1 to 4b-5. The UE may transmit PUCCH A for HARQ-ACK transmission corresponding to the multicast PDSCH based on the OLPC parameter A related to the UE-specific PUCCH resource configuration. The UE may transmit PUCCH B for HARQ-ACK transmission corresponding to the multicast PDSCH based on the OLPC parameter B related to the group-common PUCCH resource configuration.

[0121] [Aspect 4b-1] Parameter A and parameter B are configured separately. The UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively.

[0122] [Aspect 4b-2] Parameter A and parameter B are configured as the same (common) parameter. The UE may use the common parameter for both PUCCH A and PUCCH B.

[0123] [Aspect 4b-3] Multiple parameter sets are configured in common for two PUCCH resource configurations (UE-specific PUCCH resource configuration and group-common PUCCH resource configuration). The UE may use (decide / apply / select) one of the multiple parameter sets based on the RRC parameters / MAC CE / DCI format / DCI field / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capability.

[0124] [Aspect 4b-4] If parameter B is configured (parameters A and B are configured), the UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively. If parameter B is not configured (only parameter A is configured), the UE may use parameter A for PUCCH A and PUCCH B.

[0125] [Aspect 4b-5] The UE uses (decides / applies / selects) either aspect 4b-1 or 4b-2 based on whether the PUCCH resource configuration for PUCCH A and the PUCCH resource configuration for PUCCH B are the same or not.

[0126] According to example 4b, OLPC parameters are made clear for UE-specific PUCCH resource configuration and group-common PUCCH resource configuration.

[0127] Aspect 4c For HARQ-ACK transmission corresponding to a multicast PDSCH, the OLPC parameter A related to PUCCH resource configuration for ACK / NACK feedback and the OLPC parameter B related to PUCCH resource configuration for NACK-only feedback may be according to at least one of the following aspects 4c-1 to 4c-5. The UE may transmit PUCCH A for HARQ-ACK transmission corresponding to the multicast PDSCH based on the OLPC parameter A related to PUCCH resource configuration for ACK / NACK feedback. The UE may transmit PUCCH B for HARQ-ACK transmission corresponding to the multicast PDSCH based on the OLPC parameter B related to PUCCH resource configuration for NACK-only feedback.

[0128] [Aspect 4c-1] Parameter A and parameter B are configured separately. The UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively.

[0129] [Aspect 4c-2] Parameter A and parameter B are configured as the same (common) parameter. The UE may use the common parameter for both PUCCH A and PUCCH B.

[0130] [Aspect 4c-3] Multiple parameter sets are configured in common for two PUCCH resource configurations (PUCCH resource configuration for ACK / NACK feedback, and PUCCH resource configuration and PUCCH resource configuration for NACK-only feedback). The UE may use (decide / apply / select) one of the multiple parameter sets based on the RRC parameters / MAC CE / DCI format / DCI field / PDCCH (CRC of DCI) scrambling RNTI / CORESET / search space / UE capability.

[0131] [Aspect 4c-4] If parameter B is configured (parameters A and B are configured), the UE may use parameter A and parameter B for PUCCH A and PUCCH B, respectively. If parameter B is not configured (only parameter A is configured), the UE may use parameter A for PUCCH A and PUCCH B.

[0132] [Aspect 4c-5] The UE uses (decides / applies / selects) either of the aspects 4c-1 and 4c-2 based on whether the PUCCH resource configuration for PUCCH A and the PUCCH resource configuration for PUCCH B are the same or not.

[0133] According to example 4c, OLPC parameters are made clear for the PUCCH resource configuration for ACK / NACK feedback and the PUCCH resource configuration for NACK-only feedback.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0182] The control unit 110 may determine at least one of higher layer parameters and a transmit power control (TPC) command for determining a transmit power of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH). The transceiver unit 120 may transmit at least one of the higher layer parameters and the TPC command.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0200] The control unit 210 may determine a transmission power of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information for a multicast physical downlink shared channel (PDSCH) based on at least one of a higher layer parameter and a transmission power control (TPC) command. The transceiver unit 220 may transmit the PUCCH using the transmission power.

[0201] The multicast PDSCH may be scheduled by group common downlink control information (first embodiment).

[0202] The control unit 210 may determine the transmission power based on at least one of a TPC command for the PUCCH and a second TPC command for a second PUCCH for transmitting second HARQ-ACK information for a unicast PDSCH (second embodiment).

[0203] When a method of transmitting only a negative acknowledgement (NACK) is applied to the PUCCH and the PUCCH is not transmitted, the control unit 210 may determine the cumulative value of the TPC command after the PUCCH (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

[0216] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

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

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

[0219] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

[0224] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

[0226] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

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

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

[0229] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0230] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

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

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

[0233] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

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

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

[0236] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0237] The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

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

[0239] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

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

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

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

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

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

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

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

[0247] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0248] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

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

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

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

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

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

[0254] A mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

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

[0256] Furthermore, the base station in the present disclosure may be read as a user terminal. For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, an uplink channel, a downlink channel, etc. may be read as a sidelink channel.

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

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

[0259] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

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

[0261] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0262] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

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

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

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

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

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

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

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

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

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

[0272] In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

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

Claims

1. A method and apparatus for providing a wireless LAN base station comprising: a receiving unit for receiving first downlink control information (DCI) that schedules a unicast physical downlink shared channel (PDSCH) and includes a transmit power control (TPC) command field; and a receiving unit for receiving second DCI that schedules a multicast PDSCH and does not include a TPC command field. a control unit that determines a transmission power of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information associated with the multicast PDSCH based on an accumulated value indicated by the TPC command field included in the first DCI; A terminal comprising: a transmitter that transmits the PUCCH using the transmission power.

2. 2. The terminal of claim 1, wherein configuration of at least one of ACK / negative acknowledgement (NACK)-based feedback and NACK-only-based feedback for the PUCCH for transmitting the HARQ-ACK information associated with the multicast PDSCH is supported, and separate parameters are configured for the ACK / NACK-based feedback and the NACK-only-based feedback.

3. The terminal as described in claim 2, wherein the separate parameters respectively include p0-Set, pathlossReferenceRSs, and parameters for each PUCCH format.

4. A method for receiving a first downlink control information (DCI) for scheduling a unicast physical downlink shared channel (PDSCH) and including a transmit power control (TPC) command field, and receiving a second DCI for scheduling a multicast PDSCH and not including a TPC command field; determining a transmission power of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information associated with the multicast PDSCH based on an accumulated value indicated by the TPC command field included in the first DCI; and transmitting the PUCCH using the transmission power.

5. A transmitter that schedules a unicast physical downlink shared channel (PDSCH) and transmits a first downlink control information (DCI) that includes a transmit power control (TPC) command field, and schedules a multicast PDSCH and transmits a second DCI that does not include a TPC command field; and a control unit that controls reception of a physical uplink control channel (PUCCH) transmitted using a transmission power of the PUCCH for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information associated with the multicast PDSCH, the PUCCH being determined based on an accumulated value indicated by the TPC command field included in the first DCI.

6. A system including a terminal and a base station, The terminal includes: A receiving unit that schedules a unicast physical downlink shared channel (PDSCH) and receives a first downlink control information (DCI) including a transmit power control (TPC) command field, and schedules a multicast PDSCH and receives a second DCI not including a TPC command field; a control unit that determines a transmission power of a physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgement (HARQ-ACK) information associated with the multicast PDSCH based on an accumulated value indicated by the TPC command field included in the first DCI; a transmission unit that transmits the PUCCH using the transmission power, The base station, a transmitter that transmits the first DCI and transmits the second DCI; A control unit that controls reception of the PUCCH.

Images