Terminal, wireless communication method, and base station

CN116803148BActive Publication Date: 2026-11-03NTT DOCOMO INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202080108384.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-03
Publication Date
2026-11-03
Estimated Expiration
2040-12-03

AI Technical Summary

Technical Problem

In future wireless communication systems, the lack of clear methods for determining power control parameters leads to reduced communication quality and throughput.

Method used

Without providing information on the spatial relationships of the physical uplink control channel, the terminal determines two values ​​for the power control parameters through the control unit, and associates these values ​​with the control resource set pool index and the index for sending the setting indication status, and then sends the PUCCH.

Benefits of technology

This enabled the appropriate determination of power control parameters, improving communication quality and throughput.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116803148B_ABST
    Figure CN116803148B_ABST
Patent Text Reader

Abstract

A terminal according to one embodiment of the present disclosure includes a control unit that decides two values of a power control parameter in a case where physical uplink control channel (PUCCH) spatial relation information is not provided, and a transmission unit that transmits a PUCCH using at least one of the two values of the power control parameter, and one or more transmission occasions, the two values being associated with any one of two index values of a control resource set (CORESET) pool index, and two index values of a transmission configuration indication (TCI) state associated with one code point of a field within downlink control information. According to one embodiment of the present disclosure, a power control parameter can be appropriately decided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

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

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

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 36.300V8.12.0 "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)", April 2010 Summary of the Invention

[0007] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., NR), research is underway on how user terminals (terminals, user equipment (UE)) can control uplink (UL) transmission (UL channels / UL signals) based on information related to quasi-co-location (QCL) (QCL concept / transmission configuration indication (TCI) status / spatial relationship) and power control parameters.

[0009] However, there are situations where the method for determining power control parameters is unclear. If the power control parameters are unclear, there are concerns that this may lead to a decrease in communication quality and throughput.

[0010] Therefore, one of the purposes of this disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately determines power control parameters.

[0011] Methods for solving problems

[0012] One aspect of this disclosure relates to a terminal comprising: a control unit that determines two values ​​of power control parameters without being provided with physical uplink control channel (PUCCH) spatial relationship information; and a transmission unit that transmits a PUCCH using at least one of the two values ​​of the power control parameters and at one or more transmission timings, the two values ​​being associated with two indices, the two indices being either two index values ​​of a control resource set (CORESET) pool index or two index values ​​of a transmit setting indication (TCI) state associated with a code point of a field within downlink control information.

[0013] Invention Effects

[0014] According to one method of this disclosure, power control parameters can be appropriately determined. Attached Figure Description

[0015] Figures 1A to 1C This is a diagram illustrating an example of the PUCCH setting using P0 in mode 1-1.

[0016] Figures 2A to 2C This is a diagram illustrating an example of the PUCCH setting using PLRS involved in methods 1-2.

[0017] Figures 3A to 3C This is a diagram illustrating an example of the recurring association between PUCCH and TRP involved in mode 2-2.

[0018] Figures 4A to 4CThis is a diagram illustrating an example of the mapping pattern involved in mode 2-2.

[0019] Figures 5A to 5C This is a diagram illustrating an example of the PUSCH setting using P0 / alpha as described in mode 4-1.

[0020] Figures 6A to 6C This is a diagram illustrating an example of the PUSCH setting using P0 as described in mode 4-2.

[0021] Figures 7A to 7C This is a diagram illustrating an example of the PUSCH setting using PLRS as described in mode 4-3.

[0022] Figures 8A to 8C This is a diagram illustrating an example of the recurring association between PUCCH and TRP involved in mode 5-2.

[0023] Figures 9A to 9C This is a diagram illustrating an example of the mapping pattern involved in mode 5-2.

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

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

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

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

[0028] (TCI, Spatial Relations, QCL)

[0029] In NR, research is being conducted on the reception processing (e.g., at least one of receiving, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmitting, mapping, precoding, modulation, and encoding) of at least one of control signals and channels (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0030] TCI states can also represent the states of signals / channels applied to the downlink. States equivalent to the TCI states of signals / channels applied to the uplink can also be described as spatial relations.

[0031] TCI status is information related to the quasi-co-location (QCL) of signals / channels, and can also be referred to as spatial reception parameters, spatial relation information, etc. TCI status can also be set to the UE on a per-channel or per-signal basis.

[0032] QCL is an indicator of the statistical properties of a signal / channel. For example, it can also mean that, given a QCL relationship between a signal / channel and other signals / channels, it can be assumed that at least one of the following is the same (QCL): Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0033] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL(spatial QCL).

[0034] Regarding QCL, multiple types (QCL types) can also be specified. For example, four QCL types AD can be set, in which the parameters (or parameter sets) that can be assumed to be the same are different. The parameters (also referred to as QCL parameters) are represented as follows:

[0035] • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread.

[0036] • QCL Type B (QCL-B): Doppler shift and Doppler extension.

[0037] • QCL Type C (QCL-C): Doppler shift and average delay,

[0038] • QCL type D (QCL-D): Space reception parameters.

[0039] The situation in which a UE envisions a relationship between a certain Control Resource Set (CORESET), a channel, or a reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D) can also be referred to as a QCL assumption.

[0040] The UE may also determine at least one of the transmit beam (Tx beam) and receive beam (Rx beam) of the signal / channel based on the TCI state or QCL assumption of the signal / channel.

[0041] The TCI state can also be information related to the QCL between the channel being targeted (in other words, the reference signal (RS) used by that channel) and other signals (e.g., other RS). The TCI state can also be set (indicated) by higher-layer signaling, physical-layer signaling, or a combination thereof.

[0042] Physical layer signaling can also be, for example, downlink control information (Downlink Control Information (DCI)).

[0043] The channel that is set (specified) to TCI state or spatial relationship can be, for example, at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0044] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), or a QCL Detection Reference Signal (also known as a QRS).

[0045] An SSB is a block of signals that contains at least one Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and broadcast channel (Physical Broadcast Channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0046] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and this RS can also be called the QCL source of QCL type X in TCI state.

[0047] For PDCCH and PDSCH, QCL type A RS must be set, and QCL type D RS is additionally set. Since it is difficult to estimate Doppler offset, delay, etc., through single-trigger reception of DMRS, QCL type A RS is used to improve channel estimation accuracy. QCL type D RS is used in receive beam determination during DMRS reception.

[0048] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is notified as a QCL type C / D RS via the TCI status of the PDSCH. By being notified of the TCI status, the UE can utilize information obtained from the results of past periodic TRS1-1 reception / measurements in the PDSCH reception / channel estimation using DMRS. In this case, the QCL source of the PDSCH is TRS1-1, and the QCL target is the PDSCH using DMRS.

[0049] (Multiple TRPs)

[0050] In NR, research is underway on using one or more Transmission / Reception Points (TRPs) (multi-TRPs (MTRPs)) to perform DL (Low-Level Transmission) to the UE using one or more faces (multi-faces). Additionally, research is underway on the UE using one or more faces to perform UL (Low-Level Transmission) to one or more TRPs.

[0051] Furthermore, multiple TRPs can correspond to the same cell identifier (cell Identifier(ID)) or different cell IDs. This cell ID can be either a physical cell ID or a virtual cell ID.

[0052] Multiple TRPs (e.g., TRP #1, #2) can also be connected via ideal / non-ideal backhaul to exchange information, data, etc. Different codewords (CWs) and different layers can also be sent from each TRP within a multi-TRP network. As a method of multi-TRP transmission, non-coherent joint transmission (NCJT) can also be used.

[0053] In NCJT, for example, TRP#1 modulates and maps the first codeword and performs layer mapping, thereby transmitting the first PDSCH using the first precoding for a first number of layers (e.g., 2 layers). Furthermore, TRP#2 modulates and maps the second codeword and performs layer mapping, thereby transmitting the second PDSCH using the second precoding for a second number of layers (e.g., 2 layers).

[0054] Furthermore, multiple PDSCHs (multiple PDSCHs) of NCJT can also be defined as partially or completely overlapping in terms of at least one of the time domain and frequency domain. That is, at least one of the time and frequency resources of the first PDSCH from the first TRP and the second PDSCH from the second TRP can also overlap.

[0055] It can also be envisioned that these first PDSCHs and second PDSCHs are not in a quasi-co-location (QCL) relationship (not quasi-co-located). The reception of multiple PDSCHs can also be rewritten as the simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0056] Multiple PDSCHs from multiple TRPs (also known as multiple PDSCHs) can be scheduled using a single DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Alternatively, multiple PDSCHs from multiple TRPs can be scheduled separately using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

[0057] Research is underway to support PDSCH (Transport Block (TB) or Codeword (CW)) repetition across multiple TRPs in URLLC for multiple TRPs. Research is also underway to support repetition across multiple TRPs in the frequency, layer (spatial), or time domains (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4). In scheme 1, multiple PDSCHs from multiple TRPs are space-division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency-division multiplexing (FDM). In scheme 2a, for multiple TRPs, the redundancy version (RV) is the same. In scheme 2b, for multiple TRPs, the RV can be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time-division multiplexing (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted within a single time slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different time slots.

[0058] In such a multi-TRP scenario, more flexible transmission control is possible when using high-quality channels.

[0059] To support multi-TRP transmission within a cell (with the same cell ID) and between cells (with different cell IDs) based on multiple PDCCHs, a control resource set (CORESET) within the PDCCH configuration information (PDCCH-Config) can also correspond to a TRP in the RRC configuration information used to link multiple pairs of PDCCHs and PDSCHs with multiple TRPs.

[0060] The UE can also be determined to be a multi-TRP based on multiple DCI if at least one of conditions 1 and 2 is met. In this case, the TRP can also be rewritten as the CORESET pool index.

[0061] [Condition 1]

[0062] The CORESET pool index is set to 1.

[0063] [Condition 2]

[0064] Two distinct values ​​(e.g., 0 and 1) are set for the CORESET pool index.

[0065] The UE can also be determined as a multi-TRP based on a single DCI if the following conditions are met. In this case, the two TRPs can also be rewritten as two TCI states indicated by the MAC CE / DCI.

[0066] [condition]

[0067] To indicate one or two TCI states for a code point within a TCI field in the DCI, use "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE".

[0068] The DCI used for common beam indication can be either a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)) or a UE-group common DCI format.

[0069] (Path Loss RS)

[0070] The path loss PL of PUSCH, PUCCH, and SRS under their respective transmit power control b,f,c (q d [dB] is the index q of the reference signal (RS, Path Loss Reference RS) used by the UE to associate with the active UL BWP b of the carrier f of the serving cell c. d And is calculated. In this disclosure, path loss reference RS, pathloss(PL)-RS, PLRS, index q dThe RS used in path loss calculation and the RS resources used in path loss calculation can also be rewritten. In this disclosure, calculation, estimation, measurement, and tracking can also be rewritten.

[0071] We are investigating whether to update the existing mechanism for path loss measurement, the higher layer filtered RSRP, when the path loss RS is updated via MAC CE.

[0072] When the path loss RS is updated via MAC CE, path loss measurement based on L1-RSRP can also be applied. Alternatively, at a time available after the MAC CE for updating the path loss RS, the higher-layer filter RSRP can be used for path loss measurement; before the application of the higher-layer filter RSRP, L1-RSRP is used for path loss measurement. Similarly, at a time available after the MAC CE for updating the path loss RS, the higher-layer filter RSRP of the previous path loss RS is used for path loss measurement; before that time, the higher-layer filter RSRP of the previous path loss RS is used. Similar to the operation in Rel.15, the higher-layer filter RSRP can also be used for path loss measurement, and the UE can track all path loss RS candidates set via RRC. The maximum number of path loss RS that can be set via RRC can also depend on the UE's capabilities. When the maximum number of path loss RS that can be set via RRC is X, path loss RS candidates below X can also be set via RRC, and a path loss RS can be selected from the set path loss RS candidates via MAC CE. The maximum number of path loss RS that can be set via RRC can be 4, 8, 16, 64, etc.

[0073] In this disclosure, the layer 3 filter RSRP, the filtered RSRP, and the layer 3 filtered RSRP can also be rewritten in relation to each other.

[0074] (Default TCI status / Default spatial relationship / Default PL-RS)

[0075] In RRC connection mode, whether the TCI information within the DCI (higher-layer parameter TCI-PresentInDCI) is set to "enabled" or not, if the time offset between the reception of the DL DCI (the DCI that schedules the PDSCH) and the corresponding PDSCH (the PDSCH scheduled through this DCI) is less than a threshold (timeDurationForQCL) (application condition, first condition), in the case of non-cross-carrier scheduling, the TCI state of the PDSCH (default TCI state) can also be the TCI state of the lowest CORESET ID in the latest timeslot within the active DL BWP of the CC (for that specific UL signal). Otherwise, the TCI state of the PDSCH (default TCI state) can also be the TCI state of the lowest TCI state ID of the PDSCH within the active DL BWP of the scheduled CC.

[0076] In Rel.15, each MAC CE is required for the activation / deactivation of the PUSCH spatial relation and the activation / deactivation of the SRS spatial relation. The PUSCH spatial relation follows the SRS spatial relation.

[0077] In Rel.16, at least one of the MAC CEs for activation / deactivation of PUCCH spatial relations and SRS spatial relations may not be used.

[0078] In FR2, if neither the spatial relationship nor the PL-RS for PUCCH is set (application condition, second condition), the default assumptions for the spatial relationship and PL-RS for PUCCH are applied (default spatial relationship and default PL-RS). In FR2, if neither the spatial relationship nor the PL-RS for SRS (SRS resources for SRS or SRS resources corresponding to SRIs within DCI format 0_1 ​​for scheduling PUSCH) is set (application condition, second condition), the default assumptions for the spatial relationship and PL-RS for PUSCH and SRS scheduled via DCI format 0_1 ​​are applied (default spatial relationship and default PL-RS).

[0079] When a CORESET is set within the active DL BWP on the CC (application condition), the default spatial relationship and default PL-RS can also be the TCI state or QCL assumption of the CORESET with the lowest CORESET ID within the active DL BWP. When no CORESET is set within the active DL BWP on the CC, the default spatial relationship and default PL-RS can also be the active TCI state of the PDSCH with the lowest ID within the active DL BWP.

[0080] In Rel.15, the spatial relationships of PUSCHs scheduled via DCI format 0_0 follow the spatial relationships of the PUCCH resources with the lowest PUCCH resource ID in the active spatial relationships of PUCCHs on the same CC. Even if no PUCCH is sent on a SCell, the network needs to update the PUCCH spatial relationships on all SCells.

[0081] In Rel.16, the PUCCH setting for PUSCHs scheduled via DCI format 0_0 is not required. For PUSCHs scheduled via DCI format 0_0, if there is no active PUCCH space relation or no PUCCH resource on the active UL BWP within that CC (application condition, second condition), the default space relation and default PL-RS are applied to the PUSCH.

[0082] The application conditions for SRS using the default spatial relationship / default PL-RS can also include: the SRS using the default beam path loss activation information element (higher-layer parameter enableDefaultBeamPlForSRS) is set to valid. The application conditions for PUCCH using the default spatial relationship / default PL-RS can also include: the PUCCH using the default beam path loss activation information element (higher-layer parameter enableDefaultBeamPlForPUCCH) is set to valid. The application conditions for PUSCH scheduled via DCI format 0_0 using the default spatial relationship / default PL-RS can also include: the PUSCH scheduled via DCI format 0_0 using the default beam path loss activation information element (higher-layer parameter enableDefaultBeamPlForPUSCH0_0) is set to valid.

[0083] The aforementioned thresholds can also be referred to as QCL time duration, "timeDurationForQCL", "threshold", "threshold for offset between aDCI indicating a TCIstate and a PDSCH scheduled by the DCI", "threshold-Sched-Offset", scheduling offset threshold, scheduling offset threshold, etc.

[0084] (PUCCH power control)

[0085] In NR, the transmission power of PUCCH is controlled based on the TPC command (also known as value, increment / decrement value, correction value, indication value, etc.) represented by the value of the field (also known as the TPC command field, first field, etc.) in DCI.

[0086] For example, using index l of the power control adjustment state (PUCCH power control adjustment state), the transmission power (P) of the PUCCH in the PUCCH transmission opportunity (transmission occasion) (also known as transmission period, etc.) i of the active UL BWP b of carrier f of serving cell c is... PUCCH、b,f,c (i,q u ,q d [dBm] can also be based on P CMAX,f,c (i), P O_PUCCH,b,f,c (q u M PUCCH RB,b,f,c (i) PL b,f,c (q d ), Δ F_PUCCH (F), Δ TF,b,f,c (i), g b,f,c At least one of (i, l). The power control adjustment state can also be referred to as the value of the TPC command based on the power control adjustment state index l, the cumulative value of the TPC command, or the value based on the closed loop. l can also be referred to as the closed loop index.

[0087] Furthermore, the PUCCH transmission opportunity i is the period during which PUCCH can be transmitted, and it can also consist of more than one symbol, more than one time slot, etc.

[0088] P CMAX,f,c (i) For example, the transmit power of the user terminal (also known as maximum transmit power, UE maximum output power, etc.) is set for the carrier f of the serving cell c in transmission opportunity i. O_PUCCH,b,f,c (q u For example, the parameters involved in the target receive power set for the activation of the UL BWP b of the carrier f of the serving cell c in the transmission opportunity i (also known as parameters related to transmit power offset, transmit power offset P0, or target receive power parameters, etc.).

[0089] M PUCCH RB,b,f,c (i) For example, the number of resource blocks (bandwidth) allocated to the PUCCH for transmission opportunities i in the activation ULBWP b of the serving cell c and the carrier f with subcarrier spacing μ. b,f,c (q d For example, the index q of the reference signal (path loss reference RS, path loss reference RS, path loss measurement DL-RS, PUCCH-PathlossReference RS) used by the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c. d The path loss (path loss estimate [dB], path loss compensation) is calculated in the user terminal.

[0090] If the UE is not provided with path loss reference RSs, or before the UE is provided with dedicated higher-layer parameters, the UE uses RS resources obtained from the SS / PBCH block used by the UE to obtain the MIB to calculate the path loss PL. b,f,c (q d ).

[0091] When the UE is provided with path loss reference RSs (pathlossReferenceRSs within PUCCH-PowerControl information) but not with PUCCH-SpatialRelationInfo information, the UE obtains the value of the reference signal within the PUCCH-Path loss reference RS with index 0 (PUCCH-PathlossReferenceRS-Id). The resource of this reference signal is located in either the same serving cell or, if provided, indicated by the value of path loss reference linking information. Path loss reference linking information indicates which of the special cell (SpCell) and the secondary cell (SCell) corresponding to the UL the UE uses as the path loss reference. SpCell can be either the primary cell (PCell) in a master cell group (MCG) or the primary secondary cell (PSCell) in a secondary cell group (SCG). Path loss reference RS information represents the set of reference signals (e.g., CSI-RS structure or SS / PBCH block) used in PUCCH path loss estimation.

[0092] Δ F_PUCCH (F) are high-level parameters provided for each PUCCH format. Δ TF,b,f,c (i) is the transmission power adjustment component (offset) used by the UL BWP b of the carrier f of the serving cell c.

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

[0094] Here, δ PUCCH,b,f,c (i,l) is a TPC command value that can be included in the DCI format 1_0 or DCI format 1_1 detected by the UE in the PUCCH transmission opportunity i of the active ULBWP b on the carrier f of the serving cell c, or it can be combined with other TPC commands in DCI format 2_2 that have a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier) ​​(e.g., TPC-PUSCH-RNTI) and encoded.

[0095] Σ m=0 C(Ci)-1 δ PUCCH,b,f,c (m,l) can also be a concentration (cardinality) C(C i The set C of TPC command values i The total of TPC command values ​​within. C i It could also be the UE's adjustment of the PUCCH power control state l in the serving cell c on carrier f, with the activation of UL BWP b and PUCCH transmission opportunities i-i0. PUCCH (i-i0)-1 symbol preceding the PUSCH transmission opportunity i of K PUCCH (i) The set of TPC command values ​​received between the symbol inputs. i0 can also be K of the PUSCH transmission opportunities i-i0. PUCCH (i-i0) K symbols that are earlier than the PUSCH transmission opportunity i PUCCH (i) The smallest positive integer preceding the code element.

[0096] When the PUCCH sends a response to the UE's detection of DCI format 1_0 or DCI format 1_1, K PUCCH (i) It can also be the number of symbols in the active UL BWP b of the carrier f of serving cell c, after the last symbol received by the corresponding PDCCH and before the first symbol transmitted by the PUCCH. When the PUCCH transmission is configured through the configured grant configuration information (ConfiguredGrantConfig), K PUSCH (i) could also be the number of symbols N per slot in the active UL BWP b of the carrier f of the serving cell c. symb slot K is equal to the product of the minimum value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). PUCCH,min The number of code elements.

[0097] 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), then l can be {0,1}. If the UE is not provided with information indicating the use of two PUCCH power control adjustment states or PUCCH spatial relationship information, then l can be 0.

[0098] When the UE obtains the TPC command value from DCI format 1_0 or 1_1, and when the UE is provided with PUCCH spatial relationship information, the UE can also obtain the mapping between the PUCCH spatial relationship information ID (pucch-SpatialRelationInfoId) value and the closed-loop index (closedLoopIndex, power adjustment state index l) through the index provided by the PUCCH P0 ID (p0-PUCCH-Id in p0-Set within PUCCH-Config). When the UE receives an activation command containing the value of the PUCCH spatial relationship information ID, the UE can also determine the value of the closed-loop index that provides the value of l by sending a link with the corresponding PUCCH P0 ID.

[0099] When the UE activates UL BWP b for carrier f of serving cell c, P is provided by higher layers for the corresponding PUCCH power adjustment state l. O_PUCCH,b,f,c (q u With the value set, g b,f,c (i,l)=0, k=0,1,…,i. When the UE is provided with PUCCH spatial relationship information, the UE can also base its relationship on the information corresponding to q. u The PUCCH spatial relationship information is associated with the P0 ID and the corresponding closed-loop index value of l, based on q. u The value of l is determined by the value of .

[0100] q u It can also be represented as P0ID (p0-PUCCH-Id) of P0 (P0-PUCCH) in the P0 set (p0-Set).

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

[0102] Even when the UE is provided with path loss references (RSs) but not with PUCCH spatial relation information (PUCCH-SpatialRelationInfo), the UE can still obtain the value of the reference signal within the PUCCH path loss references (RSs) based on the PUCCH path loss references (RSs) with index 0 (pucch-PathlossReferenceRS-Id). The obtained RS resource is located on the primary cell, or, if path loss reference linking is provided, on the serving cell indicated by the value of the path loss reference linking.

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

[0104] That is, when the UE is not provided with PUCCH spatial relationship information, P0, PL-RS, and closed-loop index are determined according to rules. In this case, the PUCCH with the smallest P0-ID is applied, the PUCCH path loss reference RS-ID = 0 is applied, and l = 0 is applied.

[0105] Within the RRC Information Element (IE), the PUCCH Power Control Information Element (PUCCH-PowerControl) contains a set of PUCCH P0s (P0-PUCCH), i.e., the P0 set (p0-Set), and a set of PUCCH Pathloss Reference RSs (PUCCH-PathlossReferenceRSs), i.e., the pathloss Reference RSs. The PUCCH P0 contains the PUCCH P0-ID (P0-PUCCH-Id) and the PUCCH P0 value (p0-PUCCH-Value). The PUCCH Pathloss Reference RS contains the PUCCH Pathloss Reference RS-ID (PUCCH-PathlossReferenceRS-Id) and the reference signal (referenceSignal, SSB index, or NZP-CSI-RS resource ID).

[0106] (PUSCH power control)

[0107] In NR, the transmit power of PUSCH is controlled based on the TPC command (also known as value, increment / decrement value, correction value, etc.) represented by the value of the field (also known as the TPC command field, etc.) in DCI.

[0108] For example, when a UE transmits PUSCH on the active UL BWP b of carrier f in serving cell c using a parameter set (open loop parameter set) with index j and a power control adjustment state (PUSCH power control adjustment state) with index l, the transmission power (P) of PUSCH in the PUSCH transmission opportunity (transmission occasion) (also known as transmission period, etc.) i is... PUSCH、b,f,c (i,j,q d [dBm] can also be based on PUSCH、b,f,c (i,j,q d ,l)P O_PUSCH,b,f,c (j), M PUSCH RB,b,f,c (i), α b,f,c (j), PL b,f,c (q d ), Δ TF,b,f,c (i), f b,f,c At least one of (i, l). The power control adjustment state can also be referred to as the value of the TPC command based on the power control adjustment state index l, the cumulative value of the TPC command, or the value based on the closed loop. l can also be referred to as the closed loop index.

[0109] Furthermore, the PUSCH transmission opportunity i is the period during which PUSCH is transmitted, and it can also consist of more than one symbol, more than one time slot, etc.

[0110] P CMAX,f,c(i) For example, the transmit power of the user terminal (also known as maximum transmit power, UE maximum output power, etc.) is set for the carrier f of the serving cell c in transmission opportunity i. O_PUSCH,b,f,c (j) For example, parameters related to the target receive power set for the activation of the UL BWP b of the carrier f of the serving cell c in transmission opportunity i (e.g., also referred to as parameters related to transmit power offset, transmit power offset P0, target receive power parameter, etc.).

[0111] M PUSCH RB,b,f,c (i) For example, the number of resource blocks (bandwidth) allocated to the PUSCH for transmission opportunities i in the activation ULBWP b of the serving cell c and the subcarrier spacing μ of the carrier f. α b,f,c (j) is the value provided by higher-level parameters (e.g., also known as msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0112] PL b,f,c (q d For example, in the user terminal, the index q of the reference signal (reference signal (RS), path loss reference RS, path loss reference RS, path loss measurement DL-RS, PUSCH-PathlossReference RS) used for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c is used. d The path loss is calculated (path loss estimate [dB], path loss compensation).

[0113] If the UE is not provided with a path loss reference RS (e.g., PUSCH-PathlossReferenceRS) or if the UE is not provided with dedicated higher-layer parameters, the UE can also use RS resources from the synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) used to obtain the Master Information Block (MIB) to calculate PL. b,f,c (q d ).

[0114] When the UE is configured with a number of RS resource indices up to the maximum value of the path loss reference RS (e.g., maxNrofPUSCH-PathlossReferenceRSs), and a set of individual RS settings configured for the RS resource indices via the path loss reference RS, the set of RS resource indices may also include one or both of the set of SS / PBCH block indices and the set of channel state information (CSI) - reference signal (RS) resource indices. The UE may also identify RS resource index q within the set of RS resource indices. d .

[0115] When a PUSCH transmission is scheduled with a Random Access Response (RAR) UL grant, the UE can also use the same RS resource index q as the corresponding PRACH transmission. d .

[0116] When the UE is provided with a power control setting for the PUSCH based on a sounding reference signal (SRS) resource indicator (SRI) (e.g., SRI-PUSCH-PowerControl) and is provided with more than one value for the path loss reference RS ID, a mapping between the set of SRI field values ​​in DCI format 0_1 ​​and the set of path loss reference RS ID values ​​can also be obtained based on higher-layer signaling (e.g., sri-PUSCH-PowerControl-Id within SRI-PUSCH-PowerControl). The UE can also determine the RS resource index q based on the path loss reference RS ID mapped to the SRI field values ​​in DCI format 0_1 ​​of the scheduling PUSCH. d .

[0117] If the PUSCH transmission is scheduled via DCI format 0_0 and the UE is not provided with PUCCH spatial relationship information for a PUCCH resource with the lowest index for each carrier f and the serving cell c, the UE may also use the same RS resource index q as the PUCCH transmission within that PUCCH resource. d .

[0118] In cases where PUSCH transmission is scheduled via DCI format 0_0 and the UE is not provided with spatial settings for PUSCH transmission, or where PUSCH transmission is scheduled via DCI format 0_1 ​​without an SRI field, or where SRI-based PUSCH power control settings are not provided to the UE, the UE may also use the RS resource index q with the ID of the path loss reference RS. d .

[0119] When sending a PUSCH that is configured by setting a permission setting (e.g., ConfiguredGrantConfig), where the permission setting includes specific parameters (e.g., rrc-ConfiguredUplinkGrant), the RS resource index q d It can also be provided to the UE via a path loss reference index (e.g., pathlossReferenceIndex) within specific parameters.

[0120] For PUSCH transmissions configured through permission settings, where the permission settings do not include specific parameters, the UE can also determine the RS resource index q based on the value of the path loss reference RS ID, which is mapped to the SRI field in the DCI format used to activate the PUSCH transmission. d Even when the DCI format does not include an SRI field, the UE can still determine the RS resource index q with a path loss reference RS ID. d .

[0121] Δ TF,b,f,c (i) is the transmission power adjustment component (offset, transmission format compensation) used by the UL BWP b of the carrier f of the serving cell c.

[0122] f b,f,c (i,l) represents the PUSCH power control adjustment state of the active UL BWP b for carrier f of serving cell c in transmission opportunity i. b,f,c (i,l) can also be based on δ PUSCH,b,f,c (i,l).

[0123] δ PUSCH,b,f,c(i,l) can also be a TPC command value contained in DCI format 0_0 or DCI format 0_1 ​​that schedules the PUSCH transmission opportunity i on the active UL BWP b of carrier f of serving cell c, or a TPC command value that is encoded in combination with other TPC commands in DCI format 2_2 that have a CRC scrambled by a specific RNTI (Radio Network Temporary Identifier) ​​(e.g., TPC-PUSCH-RNTI).

[0124] Σ m=0 C(Di)-1 δ PUCCH,b,f,c (m,l) can also be a concentration (cardinality) C(D) i The set D of TPC command values i The total of TPC command values ​​within. D i It could also be the UE adjusting the PUSCH power control state l, on the active UL BWP b of carrier f in serving cell c, with PUSCH transmission opportunities i-i0. PUSCH (i-i0)-1 symbol preceding the PUSCH transmission opportunity i of K PUSCH (i) The set of TPC command values ​​received between the symbol inputs. i0 can also be K of the PUSCH transmission opportunities i-i0. PUSCH (i-i0) K symbols that are earlier than the PUSCH transmission opportunity i PUSCH (i) The smallest positive integer preceding the code element.

[0125] In the case where PUSCH transmission is scheduled via DCI format 0_0 or DCI format 0_1, K PUSCH (i) It can also be the number of symbols in the active UL BWP b of the carrier f of the serving cell c, after the last symbol received by the corresponding PDCCH and before the first symbol transmitted by the PUSCH. When the PUSCH transmission is configured through the configured grant configuration information (ConfiguredGrantConfig), K PUSCH (i) could also be the number of symbols N per slot in the active UL BWP b of the carrier f of the serving cell c. symb slot K is equal to the product of the minimum value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). PUSCH,min The number of code elements.

[0126] The power control adjustment state can also be set to have multiple states (e.g., two states) or a single state via higher-level parameters. Furthermore, in the case of multiple power control adjustment states being set, one of the multiple power control adjustment states can be identified by an index l (e.g., l∈{0,1}).

[0127] In cases 1 through 4 below, the P0 / α / PL-RS / closed-loop index is determined according to the rules.

[0128] [Scenario 1]

[0129] If a PUSCH transmission other than a PUSCH retransmission corresponding to a RAR UL license is scheduled via a DCI format that does not include a SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, j=2, the UE follows the following operation 1.

[0130] [[Operation 1]]

[0131] When the PUSCH is provided to the UE using the P0 set (P0-PUSCH-Set-r16) and the DCI format includes an open-loop power control parameter set indication field, the UE determines the P based on any one of the following values ​​1, 2, or 3. O_PUSCH,b,f,c The value of (j). Otherwise, the UE determines P based on the value of the initial set (P0-PUSCH-AlphaSet) within the P0-Alpha set (p0-AlphaSets). O_PUSCH,b,f,c The value of (j).

[0132] [[[Value 1]]] The initial set (P0-PUSCH-AlphaSet) within the P0-Alpha set (p0-AlphaSets) when the value of the open-loop power control parameter set indication field is '0' or '00'.

[0133] [[[Value 2]]] When the value of the open-loop power control parameter set indication field is '1' or '01', it is the initial value in the PUSCH set (P0-PUSCH-Set-r16) with the lowest PUSCH set ID (p0-PUSCH-SetID) value.

[0134] [[[Value 3]]] When the value of the open-loop power control parameter set indication field is '11', it is the second value in the PUSCH set (P0-PUSCH-Set-r16) with the lowest PUSCH set ID (p0-PUSCH-SetID) value.

[0135] Thus, there exists a case where the initial PUSCH set with P0-Alpha (P0-PUSCH-AlphaSet) is applied, and the PUSCH set with P0 (P0-PUSCH-Set-r16) with the lowest PUSCH set ID (p0-PUSCH-SetID) value is applied.

[0136] [Scenario 2]

[0137] In cases where PUSCH transmissions other than those corresponding to the RAR UL license are scheduled via a DCI format without an SRI field, or where the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, j=2, the UE determines α from the initial PUSCH within the P0-Alpha set using the P0-Alpha set. b,f,c (j).

[0138] [Scenario 3]

[0139] If the UE is not configured with PUSCH Pathloss Reference RS and SRS Activation with Default Beam PL (enableDefaultBeamPL-ForSRS-r16), or before the UE applies dedicated higher-layer parameters, the UE uses RS resources based on the same SS / PBCH block index used by the UE to obtain the MIB to calculate the PL. b,f,c (q d If the PUSCH transmission is scheduled via DCI format 0_0 and the UE is not provided with space settings for PUSCH transmission, or if the PUSCH transmission is scheduled via DCI format 0_0 without an SRI field, or if the SRI-PUSCH-PowerControl information element is not provided to the UE, the UE uses the PUSCH-PathlossReferenceRS-Id, which is equal to zero, to determine the RS resource index q. d Here, the RS resource is located on the serving cell if it is being served by cell c, or on the serving cell indicated by the value of path loss reference linking.

[0140] [Scenario 4]

[0141] The closed-loop index l is determined based on the value of j. If j > 1 and the UE is not provided with a SRI-PUSCH power control information element (SRI-PUSCH-PowerControl), or if j = 0, l = 0.

[0142] Thus, there exists a situation where the initial PUSCH application uses the P0-Alpha set (P0-PUSCH-AlphaSet), and the PUSCH path loss reference for application 0 is RS-ID (PUSCH-PathlossReferenceRS-Id).

[0143] Within the RRC Information Element (IE), the PUSCH Configuration contains the PUSCH Power Control Information Element (PUSCH-PowerControl) and the PUSCH Power Control Information Element for Rel.16 (PUSCH-PowerControl-v1610). The PUSCH Power Control Information Element contains a list of PUSCH P0-Alpha Sets (P0-PUSCH-AlphaSets) and a list of PUSCH Path Loss Reference RSs (PUSCH-PathlossReferenceRS). The PUSCH P0-Alpha Set contains the PUSCH P0-Alpha Set ID (P0-PUSCH-AlphaSetId), P0, and Alpha. The PUSCH Path Loss Reference RS contains the PUSCH Path Loss Reference RS-ID (PUSCH-PathlossReferenceRS-Id) and a reference signal (referenceSignal, SSB index, or NZP-CSI-RS resource ID).

[0144] The Rel.16 PUSCH power control information element contains a list of Rel.16PUSCH P0 sets (P0-PUSCH-Set-r16) (P0-PUSCH-SetList-r16). The Rel.16PUSCH P0 set contains the Rel.16PUSCH P0 set ID (P0-PUSCH-SetId-r16) and a list of Rel.16PUSCH P0s (P0-PUSCH-r16).

[0145] Research is underway on supporting independent power control for different TRPs as a multi-TRP extension of PUCCH within frequency range (FR) 1.

[0146] To support independent power control for different TRPs in FR1, without providing the UE with PUCCH spatial relationship information, it is unclear how the UE determines at least one of the following for different TRPs: PUCCH P0, PUCCH path loss reference RS, and closed-loop index. Furthermore, it is unclear which TRP the UE decides to send the PUCCH to.

[0147] To support independent power control for different TRPs, it is unclear how the UE determines whether to use PUSCH with P0, PUCCH path loss reference RS, or closed-loop index for different TRPs when PUSCH is scheduled via DCI without an SRI field, or when the UE is not provided with an SRI-PUSCH empty power control information element. Furthermore, it is unclear which TRP the UE decides to send PUSCH to.

[0148] Therefore, the inventors of this invention conceived of a method for determining the power control parameters of the UL channel.

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

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

[0151] In this disclosure, configure, activate, update, indicate, enable, specify, and select can also be overridden with each other.

[0152] In this disclosure, the functions of linking, associating, corresponding, and mapping can be overridden. Similarly, the functions of allocating, assigning, monitoring, and mapping can also be overridden.

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

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

[0155] In this disclosure, MAC CE and activation / deactivation commands can also be rewritten.

[0156] In this disclosure, beam, spatial domain filter, spatial settings, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI concept, QCL concept, QCL parameters, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D in TCI state / QCL concept, RS of QCL type A in TCI state / QCL concept, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS can also be mutually modified. In this disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, source of DL-RS, SSB, CSI-RS, and SRS can also be mutually modified.

[0157] In this disclosure, the panel, uplink (UL) transmitting entity, TRP, spatial relationship, control resource set (CORESET), PDSCH, codeword, base station, antenna port of a signal (e.g., DeModulation Reference Signal (DMRS) port), antenna port group of a signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV)), and layer (MIMO layer, transmitting layer, spatial layer) can also be overridden. Furthermore, the panel identifier (Identifier (ID)) and the panel can also be overridden. In this disclosure, the TRP index, TRP ID, CORESET pool index, ordinal numbers of the TCI states in two TCI states (first, second), and TRP can also be overridden.

[0158] In this disclosure, the TRP, the transmitting point, the panel, the DMRS port group, the CORESET pool, and one of the two TCI states associated with a code point in the TCI field can also be overwritten.

[0159] In this disclosure, a single TRP, a single TRP system, a single TRP transmission, and a single PDSCH can also be mutually rewritten. In this disclosure, multiple TRPs, multiple TRP systems, multiple TRP transmissions, and multiple PDSCHs can also be mutually rewritten. In this disclosure, a single DCI, a single PDCCH, multiple TRPs based on a single DCI, and two TCI states activated at least one TCI code point can also be mutually rewritten.

[0160] In this disclosure, single TRP, channels using single TRP, channels using one TCI state / spatial relationship, multiple TRPs not activated by RRC / DCI, multiple TCI states / spatial relationships not activated by RRC / DCI, and CORESET pool index (CORESETPoolIndex) values ​​not set to 1 for any CORESET and no code points in the TCI field being mapped to two TCI states can also be overridden.

[0161] In this disclosure, at least one of the following can be rewritten: multiple TRP, channel using multiple TRP, channel using multiple TCI state / spatial relationships, multiple TRP activated by RRC / DCI, multiple TCI state / spatial relationships activated by RRC / DCI, multiple TRP based on single DCI, and multiple TRP based on multiple DCI.

[0162] In this disclosure, multiple TRPs based on multiple DCIs, multiple TRPs based on multiple DCIs, a CORESET pool index (CORESETPoolIndex) value set to 1 for a CORESET, and a CORESET pool index set for more than one CORESET with different CORESET pool indices set to 0 or 1 for each CORESET can also be overridden.

[0163] In this disclosure, multiple TRPs based on a single DCI, multiple TRPs based on a single DCI, at least one code point of the TCI field being mapped to two TCI states, no CORESET pool index being set for CORESET, and the same CORESET pool index being set for all CORESETs can also be overridden.

[0164] In this disclosure, TRP1 (first TRP) can correspond to either CORESET pool index = 0 or the first TCI state among two TCI states corresponding to a code point of the TCI field. TRP2 (second TRP) can correspond to either CORESET pool index = 1 or the second TCI state among two TCI states corresponding to a code point of the TCI field.

[0165] In this disclosure, PUCCH, PUSCH, repetition, and occasion can also be rewritten.

[0166] (Wireless communication method)

[0167] The DCI field of the PUCCH command using the TPC command can also be extended. The two DCI fields of the TPC command can also correspond to the first TRP and the second TRP.

[0168] The DCI fields of the PUSCH command using the TPC command / PUSCH using the SRI can also be extended. The two DCI fields of this TPC command / SRI can also correspond to the first TRP and the second TRP.

[0169] Even without PUCCH spatial relationship information, the UE can determine two values ​​of the power control parameters and use at least one and more of the two values ​​of the power control parameters to transmit the PUCCH.

[0170] When the PUSCH is scheduled through downlink control information that does not include the SRI field, or when no SRI-PUSCH power control information element is provided, the UE can also determine the two values ​​of the power control parameters and use at least one and more of the two values ​​of the power control parameters to send the PUSCH.

[0171] Two values ​​can also be associated with two separate indexes (e.g., an index associated with the TRP). The two indexes can also be either two index values ​​from the CORESET pool index or either two index values ​​from the TCI state associated with a code point in a field within the downlink control information.

[0172] <First Implementation>

[0173] The method for the UE to determine at least one of the following for different TRPs: P0 for PUCCH, PUCCH path loss reference RS (PLRS for PUCCH), and closed-loop index is explained.

[0174] Even if the UE is not provided with PUCCH spatial relationship information, the UE can still determine the power control parameters to be applied in PUCCH transmissions to a specific TRP by following the methods below. The power control parameters can also be at least one of PUCCH P0, PUCCH PLRS, or the closed-loop index.

[0175] Method 1-1: PUCCH uses P0

[0176] If the UE is not provided with PUCCH spatial relationship information, the UE can also use P0 for PUCCH in any of the following ways 1-1-1 to 1-1-4.

[0177] [Method 1-1-1]

[0178] Two P0 sets are set for each of the two TRPs. For PUCCH transmissions to each TRP, the UE uses the P0 set with the smallest ID from the corresponding P0 set.

[0179] Figure 1A This is a diagram illustrating an example of the PUCCH setting using P0 in mode 1-1-1.

[0180] In this example, a set of P0 is set for TRP1 (P0-Set-TRP1) and a set of P0 is set for TRP2 (P0-Set-TRP2). The set of P0 for TRP1 contains PUCCH P0 with ID (P0-PUCCH-ID) = 0 and PUCCH P0 with ID = 1. The set of P0 for TRP2 contains PUCCH P0 with ID = 2 and PUCCH P0 with ID = 3. The PUCCH P0 with the smallest ID (0) in the set of P0 for TRP1 is used in the PUCCH transmission to TRP1. The PUCCH P0 with the smallest ID (2) in the set of P0 for TRP2 is used in the PUCCH transmission to TRP2.

[0181] [Method 1-1-2]

[0182] A set of P0s is set. From this set of P0s, based on rules, the P0 for each PUCCH of the two TRPs is determined. For example, for a PUCCH transmission to the first TRP, the UE uses the PUCCH with the smallest ID (e.g., 0) as the P0, and for a PUCCH transmission to the second TRP, it uses the PUCCH with the second smallest ID (e.g., 1) as the P0.

[0183] Figure 1B This is a diagram illustrating an example of the PUCCH setting using P0 as described in mode 1-1-2.

[0184] In this example, a P0 set is set. This P0 set contains P0s with ID=0, P0s with ID=1, P0s with ID=2, and P0s with ID=3. The P0 with the smallest ID (0) in this P0 set is used for PUCCH transmission to TRP1. The P0 with the second smallest ID (1) in this P0 set is used for PUCCH transmission to TRP2.

[0185] [Method 1-1-3]

[0186] A set of P0 is set. From this set of P0, for two TRPs, two subsets of PUCCH P0 are explicitly / implicitly set respectively. For example, for the first TRP, the initial K PUCCHs are set with P0 (first subset), and for the second TRP, the (K+1)th to the largest number of PUCCHs are set with P0 (second subset). For PUCCH transmissions to each TRP, the UE applies the PUCCH P0 with the smallest ID from the corresponding subset.

[0187] K can be set, specified in the standard, or depend on UE capabilities.

[0188] Figure 1C This is a diagram illustrating an example of the PUCCH setting using P0 as described in mode 1-1-3.

[0189] In this example, a set P0 is defined. This set P0 contains a subset for TRP1 and a subset for TRP2. The subset for TRP1 contains PUCCH P0 with ID=0 and PUCCH P0 with ID=1. The subset for TRP2 contains PUCCH P0 with ID=2 and PUCCH P0 with ID=3. The PUCCH P0 with the smallest ID (0) in the subset for TRP1 is used in PUCCH transmissions to TRP1. The PUCCH P0 with the smallest ID (2, K) in the subset for TRP2 is used in PUCCH transmissions to TRP2.

[0190] [Method 1-1-4]

[0191] In a multi-TRP scenario, the two values ​​of PUCCH P0 used are explicitly set for each of the two TRPs. The UE applies the corresponding (set) PUCCH P0 for each TRP's PUCCH transmission.

[0192] Regarding which TRP1 (first TRP) and TRP2 (second TRP) the UE sends the PUCCH to, the second implementation method can also be followed.

[0193] Method 1-2: PUCCH uses PLRS

[0194] If the UE is not provided with PUCCH spatial relationship information, the UE can also use PLRS for PUCCH in any of the following ways 1-2-1 to 1-2-4.

[0195] [Method 1-2-1]

[0196] The PUCCH is configured for each of the two TRPs using two sets of PLRS. For each TRP, the UE applies the PLRS with the smallest ID (e.g., 0) from the corresponding set when sending PUCCH.

[0197] Figure 2A This is a diagram illustrating an example of the PUCCH setting using PLRS as described in mode 1-2-1.

[0198] In this example, a set of PLRS (pathlossRS-TRP1) is set for TRP1, and a set of P0 (pathlossRS-TRP2) is set for TRP2. The PLRS set for TRP1 contains PLRS for PUCCH with ID=0 and PLRS for PUCCH with ID=1. The PLRS set for TRP2 contains PLRS for PUCCH with ID=2 and PLRS for PUCCH with ID=3. The PLRS for PUCCH with the smallest ID (0) in the PLRS set for TRP1 is used in PUCCH transmissions to TRP1. The PLRS for PUCCH with the smallest ID (2) in the PLRS set for TRP2 is used in PUCCH transmissions to TRP2.

[0199] [Method 1-2-2]

[0200] A set of PUCCH PLRS is configured. From this set, based on rules, two PUCCH PLRS are determined for each of the two TRPs. For example, for PUCCH transmission to the first TRP, the UE applies the PUCCH PLRS with the smallest ID (e.g., 0), and for PUCCH transmission to the second TRP, it applies the PUCCH PLRS with the second smallest ID (e.g., 1).

[0201] Figure 2B This is a diagram illustrating an example of the PUCCH setting using PLRS as described in mode 1-2-2.

[0202] In this example, a set of PUCCH PLRS (pattlossRS) is configured. This set contains PUCCH PLRS with ID=0, PUCCH PLRS with ID=1, PUCCH PLRS with ID=2, and PUCCH PLRS with ID=3. The PUCCH PLRS with the smallest ID (0) in this set is used for PUCCH transmission to TRP1. The PUCCH PLRS with the second smallest ID (1) in this set is used for PUCCH transmission to TRP2.

[0203] [Methods 1-2-3]

[0204] A set of PUCCH PLRS is configured. From this set, for two TRPs, two subsets of PUCCH PLRS are explicitly / implicitly configured respectively. For example, the first K PUCCH PLRS (first subset) are configured for the first TRP, and the (K+1)th to the largest numbered PUCCH PLRS (second subset) are configured for the second TRP. The UE applies the PUCCH PLRS with the smallest ID from the corresponding subset for PUCCH transmissions to each TRP.

[0205] K can be set, specified in the standard, or depend on UE capabilities.

[0206] Figure 2C This is a diagram illustrating an example of the PUCCH setting using PLRS involved in methods 1-2-3.

[0207] In this example, a set of pathlossRS (PLRS) for PUCCH is configured. This set contains a subset for TRP1 and a subset for TRP2. The TRP1 subset contains PUCCH PLRS with ID=0 and PUCCH PLRS with ID=1. The TRP2 subset contains PUCCH PLRS with ID=2 and PUCCH PLRS with ID=3. The PUCCH PLRS with the smallest ID (0) in the TRP1 subset is used in PUCCH transmissions to TRP1. The PUCCH PLRS with the smallest ID (2, K) in the TRP2 subset is used in PUCCH transmissions to TRP2.

[0208] [Methods 1-2-4]

[0209] In a multi-TRP scenario, the two PUCCHs used are explicitly configured with PLRS for each TRP. The UE applies the corresponding (configured) PUCCH PLRS for each TRP's PUCCH transmission.

[0210] Regarding which TRP1 (first TRP) and TRP2 (second TRP) the UE sends the PUCCH to, the second implementation method can also be followed.

[0211] Methods 1-3: PUCCH uses a closed-loop index

[0212] If the UE is not provided with PUCCH spatial relationship information, the UE can also follow any of the following methods 1-3-1 to 1-3-3 for the closed-loop index l of PUCCH.

[0213] [Method 1-3-1]

[0214] Even if the UE is not provided with PUCCH spatial relationship information, the UE can also apply l=0 in the PUCCH transmission to the first TRP and l=1 in the PUCCH transmission to the second TRP.

[0215] [Method 1-3-2]

[0216] For the multi-TRP scenario, the candidate values ​​for the closed-loop index can also be extended to l = {0_0, 0_1, 1_0, 1_1}. Here, {0_0, 0_1} can also be candidate values ​​used by the first TRP. {1_0, 1_1} can also be candidate values ​​used by the second TRP. If the UE is not provided with PUCCH spatial relationship information, the UE can also apply l = 0_0 in the PUCCH transmission to the first TRP and l = 1_0 in the PUCCH transmission to the second TRP.

[0217] [Method 1-3-3]

[0218] Closed-loop power control adjustment state g b,f,c (i,l) can also be extended to g b,f,c (i,l,x). TPC command value δ PUCCH,b,f,c (m,l) can also be extended to δ PUCCH,b,f,c (m,l,x). Here, x can also represent the TRP index. If the UE is not provided with PUCCH spatial relationship information, the UE can also use l=0 and x=0 in the PUCCH transmission to the first TRP, and use l=0 and x=1 in the PUCCH transmission to the second TRP.

[0219] According to this implementation, the UE can apply appropriate power control parameters in the PUCCH transmission to a specific TRP.

[0220] <Second Implementation>

[0221] The method for determining which TRP the UE sends the PUCCH to is explained.

[0222] The UE may also apply at least one of the following parameters determined based on the first embodiment for the TRP in the PUCCH transmission to a TRP based on the second embodiment: PUCCH P0, PUCCH path loss reference RS, and closed-loop index.

[0223] Method 2-1: Send PUCCH without repetition

[0224] For non-repeating PUCCH transmissions, the UE can also follow any of the following methods 2-1-1 to 2-1-6 to determine the association between PUCCH transmissions and TRP.

[0225] [Method 2-1-1]

[0226] This association is determined based on the CORESET pool index of the CORESET of the DCI used by the UE for dynamic PUCCH resource selection (PUCCH resource indication). The DCI can also be, for example, a DCI format 1_0 / 1_1 / 1_2.

[0227] This approach can also be applied only to multi-TRP based on multiple DCI.

[0228] [Method 2-1-2]

[0229] The TRP index and CORESET pool index are explicitly set for each PUCCH resource / PUCCH resource set / PUCCH resource group / PUCCH format.

[0230] [Method 2-1-3]

[0231] Along with the PUCCH resource ID for PUCCH resources that are periodically / semi-persistently set, the TRP index / CORESET pool index is explicitly set. Here, the PUCCH resource that is periodically / semi-persistently set can also be a PUCCH resource used for CSI reporting (PUCCH-CSI-Resource) or an SR resource.

[0232] [Method 2-1-4]

[0233] Within the DL scheduling DCI used for dynamic PUCCH resource selection (PUCCH resource indication), the TRP index / CORESET pool index is explicitly indicated. This DCI can also be, for example, a DCI format 1_0 / 1_1 / 1_2.

[0234] [Method 2-1-5]

[0235] This association is implicitly set through grouping of PUCCH resources / PUCCH resource sets. PUCCH resources / PUCCH resource sets within the first group can also be used in PUCCH transmissions to the first TRP. Similarly, PUCCH resources / PUCCH resource sets within the second group can also be used in PUCCH transmissions to the second TRP.

[0236] [Method 2-1-6]

[0237] The TRP index / CORESET pool index is set via RRC / activated via MAC CE and applied until RRC is reset or a new MAC CE is received.

[0238] Any of methods 2-1-2 to 2-1-6 can also be applied to both single-DCI-based multi-TRP and multi-DCI-based multi-TRP.

[0239] When TRP index / CORESET pool index = 0, the UE can also apply the P0 / PLRS / closed-loop index for the first TRP in the first embodiment. When TRP index / CORESET pool index = 1, the UE can also apply the P0 / PLRS / closed-loop index for the second TRP in the first embodiment.

[0240] Method 2-2: Repeated PUCCH

[0241] Regarding PUCCH repetitions, whether multiple repetitions are associated with a single TRP or multiple TRPs, this can be done using any of the following methods 2-2-1 to 2-2-5.

[0242] [Method 2-2-1]

[0243] Whether multiple recurring events are associated with a single TRP or with multiple TRPs is explicitly set for each PUCCH resource / each PUCCH resource set / each PUCCH resource group / each PUCCH format.

[0244] [Method 2-2-2]

[0245] Whether multiple recurring events are associated with a single TRP or multiple TRPs can be explicitly set along with the PUCCH resource ID for periodically / semi-persistently configured PUCCH resources. Here, the periodically / semi-persistently configured PUCCH resource can also be a PUCCH resource used for CSI reporting (PUCCH-CSI-Resource) or an SR resource.

[0246] [Method 2-2-3]

[0247] Whether multiple PUCCH resources are associated with a single TRP or with multiple TRPs is implicitly set through the grouping of PUCCH resources / PUCCH resource sets. PUCCH resources / PUCCH resource sets within the first group can also be used for PUCCH transmissions to a single TRP. Similarly, PUCCH resources / PUCCH resource sets within the second group can also be used for PUCCH transmissions to multiple TRPs.

[0248] [Method 2-2-4]

[0249] Whether multiple recurring events are associated with a single TRP or with multiple TRPs is explicitly indicated within the DCI used for dynamic PUCCH resource selection (PUCCH resource indication). This DCI can also be, for example, a DCI format 1_0 / 1_1 / 1_2.

[0250] [Method 2-2-5]

[0251] Whether multiple recurring connections are associated with a single TRP or multiple TRPs is determined by setting the RRC / activating the MAC CE and is applied until the RRC is reset or a new MAC CE is received.

[0252] Any of methods 2-2-1 to 2-2-5 can also be applied to both single-DCI-based multi-TRP and multi-DCI-based multi-TRP.

[0253] In the case where multiple PUCCHs are repeatedly associated with a single TRP based on any one of methods 2-2-1 to 2-2-5, the same method as in method 2-1 can be used to determine which TRP the multiple PUCCHs are repeatedly associated with.

[0254] exist Figure 3A In the example, PUCCH repeatedly associates #1 through #4 with TRP1 (single TRP). Figure 3B In the example, PUCCH repeatedly associates #1 through #4 with TRP2 (single TRP). Figure 3C In the example, PUCCH repetitions #1 and #3 are associated with TRP1, and PUCCH repetitions #2 and #4 are associated with TRP2. For PUCCH repetitions, TRP1 and TRP2 (multiple TRPs) can also be associated through the cyclic mapping described later.

[0255] When multiple PUCCHs are repeatedly associated with multiple TRPs, the mapping between PUCCHs and TRPs can also follow any of the following mappings 1 to 3.

[0256] [Mapping 1] Cyclic Mapping

[0257] Cyclic mapping mode: The first and second beam mappings (TRPs) are applied in the first and second PUCCH repetitions, respectively. The same beam mapping mode continues for the remaining PUCCH repetitions.

[0258] Figure 4AThis example illustrates mapping 1. In this example, the PUCCH repetition count is 4. PUCCH repetitions #1 and #3 are associated with TRP1, and PUCCH repetitions #2 and #4 are associated with TRP2.

[0259] [Mapping 2] Sequential Mapping

[0260] Continuous beam mapping mode: The first beam (TRP) is applied to the first and second PUCCH repetitions. The second beam is applied to the third and fourth PUCCH repetitions. The same beam mapping mode continues to the remaining PUCCH repetitions.

[0261] Figure 4B This example illustrates mapping 2. In this example, the PUCCH repetition count is 8. PUCCH repetitions #1 and #2 are associated with TRP1, and PUCCH repetitions #3 and #4 are associated with TRP2. This mapping pattern applies to PUCCH repetitions #5 through #8 being repeated.

[0262] [Mapping 3] Half-half mapping

[0263] In multiple PUCCH repetitions, the first half of the PUCCH repetition is mapped to the first TRP (beam). In multiple PUCCH repetitions, the second half of the PUCCH repetition is mapped to the second TRP.

[0264] Figure 4C The following is an example of mapping 3. In this example, the PUCCH repetition number is 8. PUCCH repetitions #1 to #4 are associated with TRP1, and PUCCH repetitions #5 to #8 are associated with TRP2.

[0265] Alternatively, one or more of these mapping modes may be supported, and a mapping mode may be set via RRC.

[0266] According to this implementation, the UE is able to send PUCCH transmissions to the appropriate TRP (using the appropriate beam).

[0267] <Third Implementation Method>

[0268] Alternatively, a UE capability corresponding to at least one function (feature) in the first to second embodiments can be specified. When the UE reports this UE capability, the UE can also perform the corresponding function. When the UE reports this UE capability and a higher-level parameter corresponding to the function is set, the UE can also perform the corresponding function. Alternatively, a higher-level parameter (RRC information element) corresponding to the function can be specified. When this higher-level parameter is set, the UE can also perform the corresponding function.

[0269] UE capabilities can also indicate whether the UE supports the function.

[0270] The UE capability can also be that, even when the UE is not provided with PUCCH spatial relationship information, for non-repeating PUCCH transmissions, the UE supports different P0 / PLRS / closed-loop indices for PUCCH transmissions to different TRPs.

[0271] The UE capability can also be such that, even without PUCCH spatial relationship information provided to the UE, for PUCCH repetition, the UE supports different P0 / PLRS / closed-loop indices for PUCCH repetition to different PUCCHs on different TRPs. For PUCCH repetition of the same PUCCH, the UE can also apply the same power control parameters. For example, the UE can also support... Figure 3A Examples and Figure 3B Examples, but not supported Figure 3C Examples.

[0272] The UE capability can also be such that, even without providing PUCCH spatial relationship information, for repeated PUCCH calls to the same PUCCH on different TRPs, the UE supports different P0 / PLRS / loop-closed indices. For example, the UE can also support... Figure 3C Examples.

[0273] The UE capability can also be that, in the absence of PUCCH spatial relationship information provided to the UE, in at least one of the scenarios of multiple TRPs based on a single DCI and multiple TRPs based on multiple DCIs, the UE supports different P0 / PLRS / closed-loop indexes for different multiple TRPs.

[0274] According to this implementation, the UE can maintain compatibility with existing specifications and can achieve the functions described above.

[0275] <Fourth Implementation>

[0276] The method for the UE to determine at least one of the following for different TRPs: PUSCH using P0, alpha, Rel.16 PUSCH using P0, PUSCH path loss reference RS (PUSCH using PLRS), and closed-loop index.

[0277] If PUSCH transmissions are scheduled via a DCI format that does not include the SRI field, or if the SRI-PUSCH Power Control information element is not provided to the UE, the UE may also determine the power control parameters applied in PUSCH transmissions to a specific TRP using the following method. The power control parameters may also be at least one of PUSCH P0, alpha, Rel.16 PUSCH P0, PUSCH PLRS, or closed-loop index.

[0278] Method 4-1: PUSCH uses P0 / alpha

[0279] If the PUSCH P0 set (P0-PUSCH-Set-r16) is not provided to the UE and the PUSCH transmission is scheduled through a DCI format that does not include the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE (the same conditions as in case 2 above), the UE may also follow any of the following methods 4-1-1 to 4-1-4 for PUSCH P0 / alpha.

[0280] [Method 4-1-1]

[0281] Two P0-Alpha sets (p0-AlphaSets) are set for each of the two TRPs. For PUSCH transmission to each TRP, the UE uses the initial (with the smallest ID) PUSCH from the corresponding P0-Alpha set (P0-PUSCH-AlphaSet) with P0 and alpha.

[0282] Figure 5A This is a diagram illustrating an example of the PUSCH setting using P0 / alpha as described in mode 4-1-1.

[0283] In this example, multiple sets of P0-Alpha are set for TRP1 (p0-AlphaSets-TRP1) and multiple sets of P0-Alpha are set for TRP2 (p0-AlphaSets-TRP2). The multiple sets of P0-Alpha for TRP1 contain a PUSCH P0-Alpha set with ID (P0-PUSCH-AlphaSetId-r16) = 0 and a PUSCH P0-Alpha set with ID = 1. The multiple sets of P0-Alpha for TRP2 contain a PUSCH P0-Alpha set with ID = 2 and a PUSCH P0-Alpha set with ID = 3. The initial PUSCH P0-Alpha set from the multiple sets of P0-Alpha for TRP1 is used in the PUSCH transmission to TRP1. The initial PUSCH P0-Alpha set from the multiple sets of P0-Alpha for TRP2 is used in the PUSCH transmission to TRP2.

[0284] [Method 4-1-2]

[0285] A set of P0-Alpha values ​​(p0-AlphaSets) is set. From this set of P0-Alpha values, according to rules, two values ​​for PUSCH P0 and alpha are determined for each of the two TRPs (two sets of PUSCH P0-Alpha values ​​(p0-PUSCH-AlphaSet)). For example, for a PUSCH transmission to the first TRP, the UE applies the first PUSCH P0-Alpha set (with the smallest ID), and for a PUSCH transmission to the second TRP, it applies the second PUSCH P0-Alpha set (with the second smallest ID).

[0286] Figure 5B This is a diagram illustrating an example of the PUSCH setting using P0 / alpha as described in mode 4-1-2.

[0287] In this example, a set of P0-Alpha sets is configured. This set of P0-Alpha sets includes a PUSCH P0-Alpha set with ID=0, a PUSCH P0-Alpha set with ID=1, a PUSCH P0-Alpha set with ID=2, and a PUSCH P0-Alpha set with ID=3. The first PUSCH P0-Alpha set from this set is used in the PUSCH transmission to TRP1. The second PUSCH P0-Alpha set from this set is used in the PUSCH transmission to TRP2.

[0288] [Method 4-1-3]

[0289] A set of P0-Alphas (p0-AlphaSets) is configured. From this set, for two TRPs, two subsets of the PUSCH P0-Alpha set (P0-PUSCH-AlphaSet) are explicitly / implicitly configured respectively. For example, for the first TRP, the initial K PUSCH P0-Alpha sets (first subset) are configured, and for the second TRP, the PUSCH P0-Alpha sets from the (K+1)th to the largest number are configured (second subset). For PUSCH transmissions to each TRP, the UE applies the initial PUSCH P0-Alpha set (with the smallest ID) within the corresponding subset.

[0290] K can be set, specified in the standard, or depend on UE capabilities.

[0291] Figure 5C This is a diagram illustrating an example of the PUSCH setting using P0 / alpha involved in mode 4-1-3.

[0292] In this example, multiple sets of P0-Alpha are set. These sets contain a subset for TRP1 and a subset for TRP2. The TRP1 subset contains a PUSCH P0-Alpha set with ID=0 and a PUSCH P0-Alpha set with ID=1. The TRP2 subset contains a PUSCH P0-Alpha set with ID=2 and a PUSCH P0-Alpha set with ID=3. The initial PUSCH P0-Alpha set in the TRP1 subset is used in PUSCH transmissions to TRP1. The initial PUSCH P0-Alpha set in the TRP2 subset is used in PUSCH transmissions to TRP2.

[0293] [Method 4-1-4]

[0294] In a multi-TRP scenario, the PUSCH used is explicitly set with two values, P0 and alpha, for each of the two TRPs. The UE applies the corresponding (set) PUSCH values ​​P0 and alpha for each TRP's PUSCH transmission.

[0295] The fifth implementation method can also be followed regarding which TRP1 (first TRP) and TRP2 (second TRP) the UE sends the PUSCH to.

[0296] Method 4-2: PUSCH uses P0

[0297] When the Rel.16PUSCH P0 set (P0-PUSCH-Set-r16, P0 set for open-loop power control PUSCH) is provided to the UE and PUSCH transmission is scheduled through a DCI format containing an open-loop power control parameter set indication field, if the DCI format does not contain an SRI field or the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE (the same conditions as in case 1 above), the UE may also follow any of the following methods 4-2-1 to 4-2-4 for PUSCH P0.

[0298] [Method 4-2-1]

[0299] Rel.16PUSCH uses two sets (list, P0-PUSCH-SetList-r16) of the P0 set (P0-PUSCH-Set-r16) set, which are set separately for the two TRPs. For PUSCH transmissions to each TRP, the UE applies the initial (with the smallest ID) Rel.16PUSCH from the corresponding list using the P0 set.

[0300] Figure 6A This is a diagram illustrating an example of the PUSCH setting using P0 as described in mode 4-2-1.

[0301] In this example, a PUSCH set list (p0-PUSCH-SetList-TRP1) and a PUSCH set list (p0-PUSCH-SetList-TRP2) are set up for TRP1 and TRP2 respectively. The TRP1 PUSCH set list contains a PUSCH set with ID (P0-PUSCH-SetId) = 0 and a PUSCH set with ID = 1. The TRP2 PUSCH set list contains a PUSCH set with ID = 2 and a PUSCH set with ID = 3. The initial PUSCH set in the TRP1 PUSCH set list is used in PUSCH transmissions to TRP1. The initial PUSCH set in the TRP2 PUSCH set list is used in PUSCH transmissions to TRP2.

[0302] [Method 4-2-2]

[0303] A set (list, P0-PUSCH-SetList-r16) of P0 sets (P0-PUSCH-Set-r16) is set for Rel.16PUSCH. From this list, two Rel.16PUSCH P0 sets are determined for each of the two TRPs based on rules. For example, for PUSCH transmissions to the first TRP, the UE applies the first Rel.16PUSCH P0 set (with the smallest ID), and for PUSCH transmissions to the second TRP, it applies the second Rel.16PUSCH P0 set (with the second smallest ID).

[0304] Figure 6B This is a diagram illustrating an example of the PUSCH setting using P0 as described in mode 4-2-2.

[0305] In this example, a PUSCH set list (p0-PUSCH-SetList) is set. This PUSCH set list contains a PUSCH set with ID=0, a PUSCH set with ID=1, a PUSCH set with ID=2, and a PUSCH set with ID=3. The first PUSCH set in this list is used for PUSCH transmission to TRP1. The second PUSCH set in this list is used for PUSCH transmission to TRP2.

[0306] [Method 4-2-3]

[0307] A set (list, P0-PUSCH-SetList-r16) of P0 sets (P0-PUSCH-Set-r16) is set for Rel.16PUSCH. From this list, for two TRPs, two subsets of the Rel.16PUSCH P0 sets are explicitly / implicitly set respectively. For example, for the first TRP, the initial K Rel.16PUSCH P0 sets (first subset) are set, and for the second TRP, the Rel.16PUSCH P0 sets from the (K+1)th to the largest number are set (second subset). For PUSCH transmissions to each TRP, the UE applies the initial (with the smallest ID) Rel.16PUSCH P0 set within the corresponding subset.

[0308] K can be set, specified in the standard, or depend on UE capabilities.

[0309] Figure 6C This is a diagram illustrating an example of the PUSCH setting using P0 as described in mode 4-2-3.

[0310] In this example, a PUSCH set list (p0-PUSCH-SetList) is set. This PUSCH set list contains a subset for TRP1 (Sub-set-TRP1) and a subset for TRP2 (Sub-set-TRP2). The TRP1 subset contains the PUSCH set with ID=0 and the PUSCH set with ID=1. The TRP2 subset contains the PUSCH set with ID=2 and the PUSCH set with ID=3. The initial PUSCH set from the TRP1 subset is used in PUSCH transmissions to TRP1. The initial PUSCH set from the TRP2 subset is used in PUSCH transmissions to TRP2.

[0311] [Method 4-2-4]

[0312] In a multi-TRP scenario, the two Rel.16PUSCH sets (P0-PUSCH-Set-r16) used are explicitly set for each of the two TRPs. The UE applies the corresponding (set) Rel.16PUSCH set for each TRP's PUSCH transmission.

[0313] The fifth implementation method can also be followed regarding which TRP1 (first TRP) and TRP2 (second TRP) the UE sends the PUSCH to.

[0314] Method 4-3: PUSCH using PLRS

[0315] If PUSCH transmission is scheduled via DCI format 0_0 and the UE is not provided with space settings for PUSCH transmission, or if PUSCH transmission is scheduled via DCI format 0_0 without the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE (the same conditions as in case 3 above), the UE may use PLRS for PUSCH in any of the following ways 4-3-1 to 4-3-4.

[0316] [Method 4-3-1]

[0317] Two sets of PLRS are configured for PUSCH of each of the two TRPs. For PUSCH transmissions to each TRP, the UE applies the PLRS with the smallest ID (e.g., 0) in the corresponding set.

[0318] Figure 7A This is a diagram illustrating an example of the PUSCH setting using PLRS as described in mode 4-3-1.

[0319] In this example, a PLRS set (pathlossRS-TRP1) is set for TRP1, and a P0 set (pathlossRS-TRP2) is set for TRP2. The PLRS set for TRP1 contains PUSCH PLRS with ID (PUSCH-PLRS-ID) = 0 and PUSCH PLRS with ID = 1. The PLRS set for TRP2 contains PUSCH PLRS with ID = 2 and PUSCH PLRS with ID = 3. The PUSCH PLRS with the smallest ID (0) in the PLRS set for TRP1 is used in PUSCH transmissions to TRP1. The PUSCH PLRS with the smallest ID (2) in the PLRS set for TRP2 is used in PUSCH transmissions to TRP2.

[0320] [Method 4-3-2]

[0321] A set of PUSCH PLRS is configured. From this set, based on rules, two values ​​for the PUSCH PLRS are determined for each of the two TRPs. For example, for PUSCH transmission to the first TRP, the UE applies the PUSCH PLRS with the smallest ID (e.g., 0), and for PUSCH transmission to the second TRP, it applies the PUSCH PLRS with the second smallest ID (e.g., 1).

[0322] Figure 7B This is a diagram illustrating an example of the PUSCH setting using PLRS as described in mode 4-3-2.

[0323] In this example, a set of PUSCH PLRS (pattlossRS) is configured. This set contains PUSCH PLRS with ID=0, PUSCH PLRS with ID=1, PUSCH PLRS with ID=2, and PUSCH PLRS with ID=3. The PUSCH PLRS with the smallest ID (0) in this set is used for PUSCH transmission to TRP1. The PUSCH PLRS with the second smallest ID (1) in this set is used for PUSCH transmission to TRP2.

[0324] [Method 4-3-3]

[0325] A set of PUSCH PLRSs is configured. From this set, for two TRPs, two subsets of PUSCH PLRSs are explicitly / implicitly configured respectively. For example, the first K PUSCH PLRSs (first subset) are configured for the first TRP, and the PUSCH PLRSs from the (K+1)th to the largest number are configured for the second TRP (second subset). The UE applies the PUSCH PLRS with the smallest ID from the corresponding subset for PUSCH transmissions to each TRP.

[0326] K can be set, specified in the standard, or depend on UE capabilities.

[0327] Figure 7C This is a diagram illustrating an example of the PUSCH setting using PLRS as described in mode 4-3-3.

[0328] In this example, a set of PUSCH PLRS (pathlossRS) is set. This set contains a subset for TRP1 and a subset for TRP2. The TRP1 subset contains PUSCH PLRS with ID=0 and PUSCH PLRS with ID=1. The TRP2 subset contains PUSCH PLRS with ID=2 and PUSCH PLRS with ID=3. The PUSCH PLRS with the smallest ID (0) in the TRP1 subset is used in PUSCH transmissions to TRP1. The PUSCH PLRS with the smallest ID (2, K) in the TRP2 subset is used in PUSCH transmissions to TRP2.

[0329] [Method 4-3-4]

[0330] In a multi-TRP scenario, the two PUSCHs used are explicitly configured with PLRS for each TRP. The UE applies the corresponding (configured) PUSCH PLRS for each TRP's PUSCH transmission.

[0331] The fifth implementation method can also be followed regarding which TRP1 (first TRP) and TRP2 (second TRP) the UE sends the PUSCH to.

[0332] Method 4-4: PUSCH uses a closed-loop index

[0333] If the PUSCH transmission is scheduled through a DCI format that does not include the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, the UE may use a closed-loop index l for the PUSCH, or follow any of the following methods 4-4-1 to 4-4-3.

[0334] [Method 4-4-1]

[0335] If PUSCH transmission is scheduled via a DCI format that does not include the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, the UE may also apply l=0 in PUSCH transmission to the first TRP and l=1 in PUSCH transmission to the second TRP.

[0336] [Method 4-4-2]

[0337] For multi-TRP scenarios, the candidate values ​​for the closed-loop index can also be extended to l = {0_0, 0_1, 1_0, 1_1}. Here, {0_0, 0_1} can also be candidate values ​​used for the first TRP. {1_0, 1_1} can also be candidate values ​​used for the second TRP. If PUSCH transmission is scheduled via a DCI format that does not include the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, the UE can also apply l = 0_0 in PUSCH transmissions to the first TRP and l = 1_0 in PUSCH transmissions to the second TRP.

[0338] [Method 4-4-3]

[0339] Closed-loop power control adjustment state f b,f,c (i,l) can also be extended to f b,f,c (i,l,x). TPC command value δ PUSCH,b,f,c (m,l) can also be extended to δ PUSCH,b,f,c (m,l,x). Here, x can also represent the TRP index. If the PUSCH transmission is scheduled through a DCI format that does not include the SRI field, or if the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl) is not provided to the UE, the UE may also apply l=0 and x=0 in the PUSCH transmission to the first TRP, and apply l=0 and x=1 in the PUSCH transmission to the second TRP.

[0340] According to this implementation, the UE can apply appropriate power control parameters in the PUSCH transmission to a specific TRP.

[0341] <Fifth Implementation>

[0342] The method for determining which TRP the UE sends the PUSCH to is explained.

[0343] The UE may also apply at least one of the following parameters determined based on the fourth embodiment for the TRP in the PUSCH transmission to a TRP based on the fifth embodiment: PUSCH using P0, alpha, PUSCH path loss reference RS, and closed-loop index.

[0344] Method 5-1: Send PUSCH without repetition

[0345] For non-repeating PUSCH transmissions, the UE can also follow any of the following methods 5-1-1 to 5-1-3 to determine the association between PUSCH transmissions and TRP.

[0346] [Method 5-1-1]

[0347] This association is determined based on the CORESET pool index of the CORESET of the UL scheduling DCI detected by the UE. The UL scheduling DCI can also be, for example, a DCI format 0_0 / 0_1 / 0_2.

[0348] This approach can also be applied only to multi-TRP based on multiple DCI.

[0349] [Method 5-1-2]

[0350] The TRP index / CORESET pool index is explicitly set via the UL scheduling DCI. This UL scheduling DCI can also be, for example, a DCI format 0_0 / 0_1 / 0_2.

[0351] [Method 5-1-3]

[0352] The TRP index / CORESET pool index is semi-statically set via RRC / activated via MACCE and applied until RRC is reset or a new MACCE is received.

[0353] Any of methods 5-1-2 to 5-1-3 can also be applied to both single-DCI-based multi-TRP and multi-DCI-based multi-TRP.

[0354] When TRP index / CORESET pool index = 0, the UE can also apply the P0 / alpha / PLRS / closed-loop index for the first TRP in the fourth embodiment. When TRP index / CORESET pool index = 1, the UE can also apply the P0 / alpha / PLRS / closed-loop index for the second TRP in the fourth embodiment.

[0355] Method 5-2: Repeated PUSCH

[0356] Regarding PUSCH repetitions, whether multiple repetitions are associated with a single TRP or multiple TRPs, this can be done using any of the methods in 5-2-1 to 5-2-2.

[0357] [Method 5-2-1]

[0358] Whether multiple recurring events are associated with a single TRP or multiple TRPs can be explicitly set within the UL scheduling DCI.

[0359] [Method 5-2-2]

[0360] Whether multiple recurring connections are associated with a single TRP or with multiple TRPs is determined by setting the RRC / activating the MACCE and applied until the RRC is reset or a new MACCE is received.

[0361] Any of methods 5-2-1 to 5-2-2 can also be applied to both single-DCI-based multi-TRP and multi-DCI-based multi-TRP.

[0362] In the case where multiple PUSCHs are repeatedly associated with a single TRP based on any of methods 5-2-1 to 5-2-2, the same method as in method 5-1 can be used to determine which TRP the multiple PUSCHs are repeatedly associated with.

[0363] exist Figure 8A In the example, PUSCH repeatedly associates #1 through #4 with TRP1 (single TRP). Figure 8B In the example, PUSCH repeatedly associates #1 through #4 with TRP2 (single TRP). Figure 8C In the example, PUSCH repetitions #1 and #3 are associated with TRP1, and PUSCH repetitions #2 and #4 are associated with TRP2. For PUSCH repetitions, TRP1 and 2 (multiple TRPs) can also be associated through the cyclic mapping described later.

[0364] When multiple PUSCHs are repeatedly associated with multiple TRPs, the mapping between the PUSCHs and TRPs can also follow any of the following mappings 1 to 3.

[0365] [Mapping 1] Cyclic Mapping

[0366] Cyclic mapping mode: The first and second beam mappings (TRPs) are applied in the first and second PUSCH repetitions, respectively. The same beam mapping mode continues for the remaining PUSCH repetitions.

[0367] Figure 9A This example illustrates mapping 1. In this example, the PUSCH repetition count is 4. PUSCH repetitions #1 and #3 are associated with TRP1, and PUSCH repetitions #2 and #4 are associated with TRP2.

[0368] [Mapping 2] Sequential Mapping

[0369] Continuous mapping mode: The first beam (TRP) is applied to the first and second pusch repetitions. The second beam is applied to the third and fourth pusch repetitions. The same beam mapping mode continues to the remaining pusch repetitions.

[0370] Figure 9B This example illustrates mapping 2. In this example, the PUSCH repetition count is 8. PUSCH repetitions #1 and #2 are associated with TRP1, and PUSCH repetitions #3 and #4 are associated with TRP2. This mapping pattern applies to PUSCH repetitions #5 through #8.

[0371] [Mapping 3] Half-half mapping

[0372] In multiple pusch repetitions, the first half of the pusch repetition is mapped to the first TRP (beam). In multiple pusch repetitions, the second half of the pusch repetition is mapped to the second TRP.

[0373] Figure 9C The following is an example of mapping 3. In this example, the PUSCH repetition number is 8. PUSCH repetitions #1 to #4 are associated with TRP1, and PUSCH repetitions #5 to #8 are associated with TRP2.

[0374] Alternatively, one or more of these mapping modes may be supported, and a mapping mode may be set via RRC.

[0375] According to this implementation, the UE can send PUSCH to the appropriate TRP (using the appropriate beam).

[0376] <Sixth Implementation Method>

[0377] Alternatively, a UE capability corresponding to at least one function (feature) in the fourth to fifth embodiments can be specified. When the UE reports this UE capability, the UE can also perform the corresponding function. When the UE reports this UE capability and a higher-level parameter corresponding to the function is set, the UE can also perform the corresponding function. A higher-level parameter (RRC information element) corresponding to the function can also be specified. When this higher-level parameter is set, the UE can also perform the corresponding function.

[0378] UE capabilities can also indicate whether the UE supports the function.

[0379] The UE capability can also be that, when the PUSCH is scheduled in DCI format without the SRI field, or when the UE is not provided with the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl), the UE supports different P0 / alpha / Rel.16 PUSCHs for non-repeating PUSCH transmissions, and supports different P0 / alpha / Rel.16 PUSCHs with P0 set (P0-PUSCH-Set-r16) / PLRS / closed-loop indexes for PUSCH transmissions to different TRPs.

[0380] The UE capability can also include, when the PUSCH is scheduled via DCI format without the SRI field, or when the UE is not provided with SRI-PUSCH power control information elements (SRI-PUSCH-PowerControl), supporting different P0 / alpha / Rel.16 PUSCHs using P0 sets (P0-PUSCH-Set-r16) / PLRS / closed-loop indexes for PUSCH repetition, for PUSCH repetition to different PUSCHs at different TRPs. For PUSCH repetition of the same PUSCH, the UE can also apply the same power control parameters. For example, the UE can also support... Figure 8A Examples and Figure 8B Examples, but not supported Figure 8C Examples.

[0381] The UE capability can also be that, when the PUSCH is scheduled via DCI format without the SRI field, or when the UE is not provided with the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl), the UE repeatedly supports different P0 / alpha / Rel.16 PUSCHs using the P0 set (P0-PUSCH-Set-r16) / PLRS / closed-loop index for the same PUSCH to different TRPs. For example, the UE can also support... Figure 8C Examples.

[0382] The UE capability can also be that, when the PUSCH is scheduled in a DCI format without the SRI field, or when the UE is not provided with the SRI-PUSCH power control information element (SRI-PUSCH-PowerControl), the UE supports different P0 / alpha / Rel.16PUSCH with P0 set (P0-PUSCH-Set-r16) / PLRS / closed-loop index for different TRPs in at least one of the single-DCI-based multi-TRP scenarios and the multi-DCI-based multi-TRP scenarios.

[0383] According to this implementation, the UE can maintain compatibility with existing specifications and can achieve the functions described above.

[0384] (Wireless Communication System)

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

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

[0387] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0403] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

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

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

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

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

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

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

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

[0411] (Base station)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0426] The transmitting / receiving unit 120 (measurement unit 123) can also perform measurements related to the received signal. For example, the measurement unit 123 can also perform radio resource management (RRM) measurements, channel state information (CSI) measurements, etc., based on the received signal. The measurement unit 123 can also measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results can also be output to the control unit 110.

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

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

[0429] Even when the physical uplink control channel (PUCCH) spatial relationship information is not provided to the terminal, the control unit 110 can still determine two values ​​for the power control parameters. The transmit / receive unit 120 can also receive PUCCHs transmitted using at least one of the two values ​​of the power control parameters and at one or more transmission times. The two values ​​can also be associated with two indices respectively. The two indices can also be either two index values ​​of the control resource set (CORESET) pool index, or either two index values ​​of a transmission configuration indication (TCI) state associated with a code point in a field within the downlink control information.

[0430] When the Physical Uplink Shared Channel (PUSCH) is scheduled without downlink control information containing a Sounding Reference Signal Resource Indicator (SRI) field, or when the SRI-PUSCH power control information element is not provided to the terminal, the control unit 110 may also determine two values ​​for the power control parameters. The transmit / receive unit 120 may also receive PUSCHs transmitted using at least one and more transmission opportunities with the two values ​​of the power control parameters. The two values ​​may also be associated with two indices respectively. The two indices may be either two index values ​​of the Control Resource Set (CORESET) pool index, or either two index values ​​of the Transmission Configuration Indication (TCI) state associated with a code point in a field within the downlink control information.

[0431] (User terminal)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0449] Even when the physical uplink control channel (PUCCH) spatial relationship information is not provided, the control unit 210 can still determine two values ​​for the power control parameters. The transmit / receive unit 220 can also transmit the PUCCH using at least one and more transmission timings based on the two values ​​of the power control parameters. The two values ​​can also be associated with two indices respectively. The two indices can also be either two index values ​​of the control resource set (CORESET) pool index, or either two index values ​​of the transmission configuration indication (TCI) state associated with a code point in a field within the downlink control information (first to third embodiments).

[0450] The control unit 210 may also determine the two values ​​from either of the two sets of the power control parameters, one set of the power control parameters, or any one of the two subsets within the one set of the power control parameters (first embodiment).

[0451] The control unit 210 may also associate at least one of the two values ​​with the one or more transmission timings based on at least one of the downlink control information indicating the resources of the PUCCH, the resources of the PUCCH, the radio resource control information element, and the medium access control (MAC) control element (CE) (second embodiment).

[0452] The power control parameters can also be at least one of P0, a path loss reference signal, and a closed-loop index (first embodiment).

[0453] When the Physical Uplink Shared Channel (PUSCH) is scheduled without downlink control information containing a Sounding Reference Signal Resource Indicator (SRI) field, or when the SRI-PUSCH power control information element is not provided, the control unit 210 may also determine two values ​​for the power control parameters. The transmit / receive unit 220 may also transmit the PUSCH using at least one and more transmission opportunities with the two values ​​of the power control parameters. The two values ​​may also be associated with two indices respectively. The two indices may also be either two index values ​​of the Control Resource Set (CORESET) pool index, or either two index values ​​of the Transmission Configuration Indication (TCI) state associated with a code point in a field within the downlink control information (fourth to sixth embodiments).

[0454] The control unit 210 may also determine the two values ​​from either of the two sets of the power control parameters, one set of the power control parameters, or any one of the two subsets within the one set of the power control parameters (fourth embodiment).

[0455] The control unit 210 may also associate at least one of the two values ​​with the one or more transmission timings based on at least one of the downlink control information, radio resource control information element, and medium access control (MAC) control element (CE) for scheduling the PUSCH (fifth embodiment).

[0456] The power control parameters can also be at least one of P0, alpha, path loss reference signal, and closed-loop index (fourth embodiment).

[0457] (Hardware Structure)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0472] (Modified Example)

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

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

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

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

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

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

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

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

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

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

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

[0484] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0505] In this disclosure, the terms "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL)", "transmission configuration indication state (TCI state)", "spatial relation", "spatial domain filter", "transmit power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beamwidth", "beam angle", "antenna", "antenna element", and "panel" are used interchangeably.

[0506] In this disclosure, the terms "Base Station (BS)", "Wireless Base Station", "Fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access Point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Panel", "Cell", "Sector", "Cell Group", "Carrier", and "Component Carrier" are used interchangeably. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

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

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

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

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

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

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

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

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

[0515] The various methods / implementations described in this disclosure can also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile Communications (GSM (registered trademark))), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi, registered trademark), IEEE 802.16 (WiMAX, registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

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

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

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

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

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

[0521] In addition, "judgment (decision)" can also be rewritten as "assuming", "expecting", "considering", etc.

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

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

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

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

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

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

[0528] The invention disclosed herein has been described in detail above. However, it will be apparent to those skilled in the art that the invention is not limited to the embodiments described herein. The invention can be implemented in modified and altered ways without departing from the spirit and scope of the invention as defined by the claims. Therefore, the description in this disclosure is for illustrative purposes and does not imply any limitation on the invention.

Claims

1. A terminal, comprising: The control unit, without being provided with physical uplink control channel spatial relationship information (PUCCH spatial relationship information), determines the values ​​of a first power control parameter and a second power control parameter, which are applied to repeated transmissions of the PUCCH for multiple transmit / receive points (TRPs); and The transmitting unit repeatedly transmits the PUCCH using the values ​​of the first power control parameter and the second power control parameter, and at one or more transmission opportunities. Whether the repeated transmission of the PUCCH using a specific PUCCH resource is associated with a first TRP, a second TRP, or both of the first and second TRPs is set for each PUCCH resource including the specific PUCCH resource.

2. The terminal according to claim 1, wherein, The power control parameter is at least one of PUCCH P0, PUCCH path loss reference signal, and closed-loop index.

3. The terminal according to claim 1, wherein, The transmitting unit reports UE capabilities, which indicate support for the first power control parameters and the second power control parameters applied to repeated transmissions of the PUCCH.

4. The terminal according to claim 1, wherein, The control unit applies cyclic mapping or continuous mapping to the mapping of the values ​​of the PUCCH repeated transmission and the first power control parameter and the second power control parameter.

5. The terminal according to claim 1, wherein, When the number of repeated PUCCH transmissions is 4 and the number of the plurality of TRPs is 2, the control unit applies the following mapping: that is, the value of the first power control parameter is applied to the repeated transmissions of the first PUCCH and the third PUCCH for the first TRP, and the value of the second power control parameter is applied to the repeated transmissions of the second PUCCH and the fourth PUCCH for the second TRP; or, the value of the first power control parameter is applied to the repeated transmissions of the first PUCCH and the second PUCCH for the first TRP, and the value of the second power control parameter is applied to the repeated transmissions of the third PUCCH and the fourth PUCCH for the second TRP.

6. A wireless communication method for a terminal, comprising: In the absence of physical uplink control channel spatial relationship information (PUCCH spatial relationship information), the values ​​of a first power control parameter and a second power control parameter are determined. These first and second power control parameters are applied to the repeated transmission of PUCCH for multiple transmit / receive points (TRPs). The process of repeatedly transmitting the PUCCH using the values ​​of the first power control parameter and the second power control parameter, and at one or more transmission opportunities. Whether the repeated transmission of the PUCCH using a specific PUCCH resource is associated with a first TRP, a second TRP, or both of the first and second TRPs is set for each PUCCH resource including the specific PUCCH resource.

7. A base station, comprising: The control unit, when the physical uplink control channel spatial relationship information (PUCCH spatial relationship information) is not provided to the terminal, determines the values ​​of a first power control parameter and a second power control parameter, which are applied to the repeated transmission of PUCCH for multiple transmit / receive points (TRPs); and The receiving unit receives repeated transmissions of the PUCCH using the values ​​of the first power control parameter and the second power control parameter, and at one or more transmission opportunities. Whether the repeated transmission of the PUCCH using a specific PUCCH resource is associated with a first TRP, a second TRP, or both of the first and second TRPs is set for each PUCCH resource including the specific PUCCH resource.

8. A system having a terminal and a base station, wherein, The terminal has: The control unit determines the values ​​of a first power control parameter and a second power control parameter when no physical uplink control channel spatial relationship information, i.e., PUCCH spatial relationship information, is provided. The first power control parameter and the second power control parameter are applied to the repeated transmission of PUCCH for multiple transmit-receive points (TRPs). as well as The transmitting unit repeatedly transmits the PUCCH using the values ​​of the first power control parameter and the second power control parameter, and at one or more transmission opportunities. The base station has: The control unit determines the values ​​of the first power control parameter and the second power control parameter when the PUCCH spatial relationship information is not provided to the terminal. as well as The receiving unit receives repeated transmissions of the PUCCH using the values ​​of the first power control parameter and the second power control parameter, and at one or more transmission timings. Whether the repeated transmission of the PUCCH using a specific PUCCH resource is associated with a first TRP, a second TRP, or both of the first and second TRPs is set for each PUCCH resource including the specific PUCCH resource.

Citation Information

Patent Citations

  • Method and equipment for performing power control on PUCCH (Physical Uplink Control Channel) repetition

    CN115299121A