Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure is characterized by including: a reception unit that receives downlink control information (DCI) indicating a PRACH transmission; and a control unit that, on the basis of a specific field in the DCI, determines whether to apply a PL offset value to transmission power calculation of the PRACH. According to the one aspect of the present disclosure, it is possible to appropriately control UL transmission power.

Description

Terminal, wireless communication method and base station

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] In future wireless communication systems, in order to expand UL coverage, high-density UL deployment is being considered, in which UL reception points that mainly perform UL reception are provided in addition to DL transmission points. Also, heterogeneous networks (HetNets) using macro base stations (BSs) and micro BSs are being considered.

[0006] However, when an RS (path loss RS) for path loss (PL) calculation is transmitted from a DL transmission point / macro BS, it is not clear how a terminal (user terminal, User Equipment (UE)) determines the transmission power when transmitting an UL signal to a UL reception point / micro BS. If the UL transmission power cannot be controlled appropriately, there is a risk of a decrease in throughput.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission power.

[0008] A terminal according to one aspect of the present disclosure is characterized by having a receiving unit that receives Downlink Control Information (DCI) that instructs transmission of a PRACH, and a control unit that determines whether to apply a PL offset value to calculation of the transmission power of the PRACH based on a specific field of the DCI.

[0009] According to one aspect of the present disclosure, UL transmission power can be appropriately controlled.

[0010] Figure 1A is a diagram showing an example of a typical arrangement of transmission and reception points. Figure 1B is a diagram showing an example of an UL high-density arrangement. Figure 2 is a diagram showing an example of DL / UL coverage in a Heterogeneous Network (HetNet). Figure 3A is a diagram showing an example of association between RS indices and PL values. Figure 3B is a diagram showing an example of association between RS indices and delta PL values. Figure 4 is a diagram showing an example of Option 1 in UL high-density arrangement. Figure 5 is a diagram showing an example of Option 2 in UL high-density arrangement. Figure 6 is a diagram showing an example of power control parameters related to TCI states. Figure 7 is a diagram showing an example of a TCI-State information element in Rel. 17. Figures 8A and 8B are diagrams showing an example of UL power control parameters in Rel. 17. Figure 9 is a diagram showing a first example of power control parameters (e.g., RRC parameters) related to TCI states. Figure 10 is a diagram showing a second example of power control parameters (e.g., RRC parameters) related to TCI states. FIG. 11 is a diagram illustrating an example of a TCI-State information element setting in Option 2. FIG. 12 is a diagram illustrating an example of a TCI-UL-State information element setting in Option 2. FIG. 13 is a diagram illustrating an example of a PUSCH-PowerControl information element setting in Option 2. FIG. 14 is a diagram illustrating a third example of power control parameters (e.g., RRC parameters) related to the TCI state. FIG. 15 is a diagram illustrating an example of a PL offset setting in the case of DL sTRP / UL mTRP. FIG. 16A is a diagram illustrating an example of a transmit power parameter setting corresponding to DL TRP (TCI state #0). FIG. 16B is a diagram illustrating an example of a transmit power parameter setting corresponding to UL TRP (TCI state #1). FIG. 17 is a diagram illustrating an example of a PL change due to UE movement. FIG. 18A is a diagram illustrating an example of a PL offset update according to application / update timing example 1. FIG. 18B is a diagram illustrating an example of a PL offset update according to application / update timing example 2. 19A and 19B are diagrams illustrating a first and a second example of association between bit information and offsets in a MAC CE, respectively;

[0043] Fig. 20A is a diagram showing a first example of a MAC CE including a field indicating whether the offset is positive (+) or negative (-). Fig. 20B is a diagram showing a second example of a MAC CE including a field indicating whether the offset is positive (+) or negative (-). Fig. 21A is a diagram showing a first example of an association between bit information and a PL offset (a value that does not distinguish between positive and negative). Fig. 21B is a diagram showing a second example of an association between bit information and a PL offset (a value that does not distinguish between positive and negative). Fig. 22 is a diagram showing an example of a MAC CE including an offset value of a PL offset. Fig. 23A is a diagram showing a first example of a MAC CE including offset values ​​of multiple PL offsets. Fig. 23B is a diagram showing a second example of a MAC CE including offset values ​​of multiple PL offsets. Fig. 24 is a diagram showing an example of a MAC CE including a PLO ID and an offset value of a PL offset. Figure 25A is a diagram showing an example of a MAC CE including a TCI state ID and a PL offset value. Figure 25B is a diagram showing an example of a MAC CE including multiple TCI state IDs and multiple PL offset values. Figure 26 is a diagram showing the relationship between SRS resources and PL offsets in the second embodiment. Figure 27A is a diagram showing an example of association between SSB IDs / TCI state IDs and PL offset values. Figure 27B is a diagram showing a first example of correspondence between DCI code points and PL offset values. Figure 27C is a diagram showing a second example of correspondence between DCI code points and PL offset values. Figure 28 is a diagram showing information elements (RACH-ConfigGeneric) related to the RACH in Rel. 18. Figure 29A is a diagram showing a first example of the transmission power of the PRACH according to one PDCCH order. Figure 29B is a diagram showing a second example of the transmission power of the PRACH according to one PDCCH order. Fig. 30A is a diagram showing a first example of PRACH transmission power according to a plurality of PDCCH orders. Fig. 30B is a diagram showing a second example of PRACH transmission power according to a plurality of PDCCH orders. Fig. 31A is a diagram showing a first example of PRACH transmission power to which a PL offset is applied. Fig. 31B is a diagram showing a second example of PRACH transmission power to which a PL offset is applied.FIG. 31C is a diagram illustrating a second example of the transmission power of the PRACH to which a PL offset is applied. FIG. 32 is a diagram illustrating a flow of a 4-step RACH when a UE is an idle UE (a UE in an idle state). FIG. 33 is a diagram illustrating a flow of a 4-step RACH when a UE is a connected UE (a UE in an RRC_CONNECTED state). FIG. 34A is a diagram illustrating an example of a new DCI field. FIG. 34B is a diagram illustrating an example of a transmission spatial domain filter (beam) corresponding to an SRS resource. FIG. 35 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 36 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 37 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 38 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 39 is a diagram illustrating an example of a vehicle according to an embodiment.

[0011] (TCI, spatial relationship, QCL) In NR, it is considered to control the reception processing (e.g., at least one of reception, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmission, mapping, precoding, modulation, and encoding) in a UE of at least one of a signal and a channel (referred to as a signal / channel) based on a transmission configuration indication state (Transmission Configuration Indication (TCI) state).

[0012] The TCI state may represent that which is applied to a downlink signal / channel, and the equivalent of the TCI state that is applied to an uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information about the Quasi-Co-Location (QCL) of signals / channels, and may also be called spatial reception parameters, spatial relation information, etc. The TCI state may be configured in the UE for each channel or signal.

[0014] The QCL is an index indicating the statistical properties of signals / channels. For example, if a signal / channel has a QCL relationship with another signal / channel, it may mean that it can be assumed that at least one of a Doppler shift, a Doppler spread, an average delay, a delay spread, and a spatial parameter (e.g., a spatial Rx parameter) is the same between these different signals / channels (i.e., the signals / channels have a QCL with respect to at least one of these).

[0015] The spatial reception parameters may correspond to a reception beam (e.g., a reception analog beam) of the UE, and the beam may be identified based on a spatial QCL. The QCL (or at least one element of the QCL) in the present disclosure may be replaced with sQCL (spatial QCL).

[0016] A plurality of types (QCL types) of QCL may be defined. For example, four QCL types A to D may be provided, each having different parameters (or parameter sets) that can be assumed to be the same. The parameters (which may be referred to as QCL parameters) are as follows: QCL type A (QCL-A): Doppler shift, Doppler spread, mean delay, and delay spread QCL type B (QCL-B): Doppler shift and Doppler spread QCL type C (QCL-C): Doppler shift and mean delay QCL type D (QCL-D): Spatial reception parameters.

[0017] The UE's assumption that a Control Resource Set (CORESET), channel, or reference signal has a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be referred to as a QCL assumption.

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

[0019] The TCI state may be, for example, information about the QCL between the channel of interest (in other words, the Reference Signal (RS) for that channel) and another signal (e.g., another RS). The TCI state may be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0020] The channel / signal to which the TCI state is applied may be called a target channel / reference signal (target channel / RS), or simply a target, and the other signal may be called a reference reference signal (reference RS), a source RS, or simply a reference.

[0021] The channel for which the TCI state or spatial relationship is set (specified) may be, for example, at least one of a Physical Downlink Shared Channel (PDSCH), a Physical Downlink Control Channel (PDCCH), a Physical Uplink Shared Channel (PUSCH), and a Physical Uplink Control Channel (PUCCH).

[0022] Furthermore, the RS that has a QCL relationship with the channel may be at least one of, for example, a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), a QCL detection reference signal (also called a QRS), a demodulation reference signal (DMRS), etc.

[0023] An SSB is a signal block including at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), and a Physical Broadcast Channel (PBCH). An SSB may also be referred to as an SS / PBCH block.

[0024] An RS of QCL type X in a TCI state may refer to an RS that has a QCL type X relationship with a certain channel / signal (DMRS), and this RS may be called a QCL source of QCL type X in the TCI state.

[0025] (Control of Sounding Reference Signal (SRS) Transmission) In Rel. 15 NR, a terminal (user terminal, User Equipment (UE)) may receive information (SRS configuration information, for example, parameters in the RRC control element "SRS-Config") used for transmitting a measurement reference signal (for example, a sounding reference signal (SRS)).

[0026] Specifically, the UE may receive at least one of information regarding one or more SRS resource sets (SRS resource set information, e.g., the RRC control element "SRS-ResourceSet") and information regarding one or more SRS resources (SRS resource information, e.g., the RRC control element "SRS-Resource").

[0027] An SRS resource set may be associated with (or group together) a predetermined number of SRS resources, each of which may be identified by an SRS Resource Indicator (SRI) or SRS Resource Identifier (ID).

[0028] The SRS resource set information may include an SRS resource set ID (SRS-ResourceSetId), a list of SRS resource IDs (SRS-ResourceId) used in the resource set, an SRS resource type, and information on SRS usage.

[0029] Here, the SRS resource type may indicate any one of periodic SRS (P-SRS), semi-persistent SRS (SP-SRS), and aperiodic CSI (Aperiodic SRS (A-SRS)). Note that the UE may transmit P-SRS and SP-SRS periodically (or periodically after activation), and transmit A-SRS based on an SRS request in the DCI.

[0030] Furthermore, the use ("usage" of the RRC parameter, "SRS-SetUse" of the L1 (Layer-1) parameter) may be, for example, beam management, codebook (CB), non-codebook (NCB), antenna switching, etc. The SRS for codebook or non-codebook use may be used to determine a precoder for codebook-based or non-codebook-based uplink shared channel (Physical Uplink Shared Channel (PUSCH)) transmission based on the SRI.

[0031] For example, in the case of codebook-based transmission, the UE may determine a precoder (precoding matrix) for PUSCH transmission based on the SRI, a Transmitted Rank Indicator (TRI), and a Transmitted Precoding Matrix Indicator (TPMI). In the case of non-codebook-based transmission, the UE may determine a precoder for PUSCH transmission based on the SRI.

[0032] The SRS resource information may include an SRS resource ID (SRS-ResourceId), the number of SRS ports, the SRS port number, a transmission comb, an SRS resource mapping (e.g., time and / or frequency resource position, resource offset, resource period, number of repetitions, number of SRS symbols, SRS bandwidth, etc.), hopping-related information, an SRS resource type, a sequence ID, spatial relationship information of the SRS, etc.

[0033] The spatial relationship information of the SRS (e.g., the RRC information element "spatialRelationInfo") may indicate spatial relationship information between a predetermined reference signal and the SRS. The predetermined reference signal may be at least one of a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Channel State Information Reference Signal (CSI-RS), and an SRS (e.g., another SRS). The SS / PBCH block may be referred to as a Synchronization Signal Block (SSB).

[0034] The spatial relationship information of the SRS may include at least one of an SSB index, a CSI-RS resource ID, and an SRS resource ID as an index of the predetermined reference signal.

[0035] In the present disclosure, the SSB index, SSB resource ID, and SSB Resource Indicator (SSBRI) may be interchangeable. Furthermore, the CSI-RS index, CSI-RS resource ID, and CSI-RS Resource Indicator (CRI) may be interchangeable. Furthermore, the SRS index, SRS resource ID, and SRI may be interchangeable.

[0036] The spatial relationship information of the SRS may include a serving cell index, a BWP index (BWP ID), etc. corresponding to the predetermined reference signal.

[0037] When the UE is configured with spatial relationship information regarding the SRS and an SSB or CSI-RS for a certain SRS resource, the UE may transmit the SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter for receiving the SSB or CSI-RS (spatial domain receive filter). In this case, the UE may assume that the UE receive beam for the SSB or CSI-RS and the UE transmit beam for the SRS are the same.

[0038] When the UE is configured with spatial relationship information between another SRS (reference SRS) and the target SRS for a certain SRS (target SRS), the UE may transmit the target SRS resource using the same spatial domain filter (spatial domain transmit filter) as the spatial domain filter (spatial domain transmit filter) for transmitting the reference SRS. That is, in this case, the UE may assume that the UE transmit beam of the reference SRS and the UE transmit beam of the target SRS are the same.

[0039] The UE may determine the spatial relationship of the PUSCH scheduled by the DCI (e.g., DCI format 0_1) based on the value of a predetermined field (e.g., an SRS resource identifier (SRI) field) in the DCI. Specifically, the UE may use spatial relationship information of the SRS resources (e.g., the RRC information element "spatialRelationInfo") determined based on the value of the predetermined field (e.g., the SRI) for PUSCH transmission.

[0040] (Scenario 1: UL Dense Deployment (UL-Only TRP)) In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. PUSCH coverage is limited, especially at high frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are expected to improve at least one of UL coverage and UL throughput.

[0041] In order to expand UL coverage, the installation of UL reception points in addition to general transmission and reception points is being considered. Therefore, an example of the arrangement of general transmission and reception points and an example of an arrangement with UL reception points (UL high-density arrangement) will be described.

[0042] 1A is a diagram showing an example of a typical arrangement of transmission / reception points. In FIG. 1A, a UE receives a DL signal from a transmission / reception point (TRP) and transmits a UL signal to the TRP. For example, if the UE and the TRP are far apart, the path loss may be large, resulting in a deterioration in communication quality.

[0043] Figure 1B is a diagram showing an example of a high-density UL deployment. To expand UL coverage, it is considered to provide UL reception points as shown in Figure 1B in addition to DL transmission points. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP / Central TRP / DL TRP / Macro TRP) corresponding to a macro cell and transmits UL signals to a UL reception point (e.g., a reception point with a smaller path loss / reception power). However, the UE may be able to perform UL transmission to a DL transmission point.

[0044] By using a high-density UL configuration such as that shown in Figure 1B, it is possible to improve both coverage and UL data rates by reducing path loss, improving UL signaling quality, and obtaining a higher coding rate compared to a general configuration such as that shown in Figure 1A. Furthermore, since the UL reception point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than a transmission / reception point corresponding to a general small cell, making deployment management much easier.

[0045] In scenario 1, UL transmission of multiple TRPs may not be supported. For example, even if there are two TCIs indicated, UL TCI (UL single TRP) may always be indicated to one UE.

[0046] Alternatively, in Scenario 1, multi-TRP UL transmission (e.g., TDM / FDM repetition, SDM / SFN multi-panel simultaneous transmission, or all of them) may be supported. It may be specified that one of the two UL TRPs must be a DL TRP, or one of the two UL TRPs may be a DL TRP.

[0047] (Scenario 2: Decoupling of DL TRP and UL TRP in HetNet) In the present disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (FIG. 2). In a typical HetNet, the transmission power of the macro BS and the micro BS is different. Also, the optimal DL coverage and the optimal UL coverage are different. For example, the DL coverage is determined by the RSRP, and the UL coverage is determined by the path loss (PL).

[0048] In the example of FIG. 2, the UE is included in the optimal DL coverage of the macro BS and the optimal UL coverage of the micro BS. In this case, the UE can receive DL from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals / channels (e.g., SRS with Antenna Switching (AS) usage, used to acquire DL CSI) to the macro BS. Therefore, the UE may require two timing advances (TAs) in this scenario. Note that the AS SRS is transmitted to the macro BS because it is intended for the base station (macro BS) to measure DL CSI (e.g., determine the DL MIMO precoder) based on the reception of the SRS using channel reciprocity. On the other hand, the codebook / non-codebook SRS is transmitted to the micro BS because it is used for determining the precoder / beam of the PUSCH.

[0049] In a HetNet, even if a micro BS has DL transmission capability, it can save energy by turning off the DL function most of the time, in which case the function of the micro BS is similar to a UL-only TRP (UL Reception Point).

[0050] (Receiving Path Loss (PL)) The UE may receive first information indicating a path loss (PL) used for transmission power control (TPC), which is estimated and notified (transmitted) by the network, via DL signaling. The DL signaling may be at least one of higher layer signaling (e.g., RRC or MAC CE) and physical layer signaling (e.g., Downlink Control Information (DCI)).

[0051] The UE receives the path loss (PL ｂ，ｆ，ｃ (q ｄ ), P.L. ｂ，ｆ，ｃ ) (index q ｄ The active UL BWP of carrier f of serving cell c (path loss for b) may be used to calculate the UL signal transmission power (for example, the transmission power of PUSCH / PUCCH / SRS / PRACH) for a reception point that does not transmit downlink data.

[0052] [Option 1] The absolute path loss (PL) value [dB] for each RS index may be reported (transmitted) from the network to the UE, and the UE may use the reported absolute path loss value directly in calculating the transmit power.

[0053] [Option 2] The network may notify (transmit) a relative path loss (delta PL, PL offset) value [dB] for each RS index to the UE. The UE may use the path loss value obtained by applying (adding or subtracting) the received delta PL value to the conventional path loss value estimated from the DL RS transmitted from the macro cell (macro BS / central TRP) for transmission power calculation.

[0054] The PL value / delta PL value in options 1 and 2 is q ｄThe PL value / delta PL value may be notified / configured for each index of the RS / SSB / CSI-RS / SRS resource / SRS resource set. One or more RS indices and the PL value / delta PL value corresponding to each RS index may be notified by DL signaling. The PL value / delta PL value may be interpreted as a PL parameter / delta PL parameter.

[0055] FIG. 3A is a diagram showing an example of the association between RS indexes and PL values. FIG. 3B is a diagram showing an example of the association between RS indexes and delta PL values. The association (correspondence) between RS indexes and PL values / delta PL values ​​is not limited to that shown in FIGS. 3A and 3B. For example, one RS index may correspond to multiple PL values / delta PL values. Note that a quantization table (range and step) for PL values / delta PL values ​​may be predefined in the specifications. The notified PL values / delta PL values ​​may be quantized values ​​or indices of quantized values.

[0056] Figure 4 shows an example of Option 1 in UL dense deployment. The UL reception point receives / measures the UL signal. If the DL transmission point (macro TRP / gNB) knows the transmission power of this UL signal, the DL transmission point can know the exact PL value of the UL reception point. In this case, the DL transmission point can notify the UE of the absolute PL value (X [dB]) of the UL reception point.

[0057] Figure 5 shows an example of Option 2 in a UL dense deployment. When both the DL transmission point (macro TRP / gNB) and the UL reception point measure the same resource, the DL transmission point can recognize the difference between the PL between the DL transmission point and the UE and the PL between the UL reception point and the UE. In this case, the DL transmission point may notify the UE of this difference (relative PL / delta PL). The relative PL / delta PL may also be referred to as PL offset.

[0058] As described above, even if the UE is not notified of the DL RS (RS index) used for path loss estimation, the UE can calculate the transmission power using the notified PL value / delta PL value.

[0059] (UL Power Control Parameters for TCI States) Fig. 6 is a diagram showing examples of power control parameters related to TCI states. As shown in Fig. 6, the power control parameters of the path loss RS and the PUSCH / PUCCH / SRS are associated with the TCI states.

[0060] When the Rel. 17 TCI state is set, the Rel. 15 / 16 TCI state and spatial relationship information (except positioning) cannot be set in the same band. For channels / RSs that do not apply the indicated TCI state, the Rel. 17 TCI state may be set instead of the Rel. 15 / 16 TCI state and spatial relationship information.

[0061] The UE may transmit UE capability information indicating that different power control parameters are associated with each TCI state. If the UE does not support this UE capability, default power control parameters may be used. Figure 7 shows an example of the TCI-State information element in Rel. 17. The default power control parameter is, for example, the pathlossReferenceRS-Id (pathlossReferenceRS-Id-r17) in Figure 7.

[0062] (UL Power Control Parameters for Unified TCI State in Rel. 17) In the unified TCI state in Rel. 17, the UE is provided with UL power control parameters (RRC information element "ul-powerControl-r17") included in the UE-specific UL BWP configuration (RRC information element "BWP-UplinkDedicated") (see Fig. 8A). If the UE is not configured with UL power control (ul-powerControl) for the UL TCI state / joint TCI state of the serving cell, these parameters are used for transmit power control of UL transmissions.

[0063] The UL power control parameter (RRC information element "ul-powerControl-r17") corresponds to a UL power control parameter ID (Uplink-powerControlId-r17), and the UL power control parameter is identified by this ID.

[0064] The UL power control parameters (RRC information element "uplink-powerControl-r17") corresponding to "ul-powerControl-r17" include at least one of a set of P0 and α for PUSCH (p0AlphaSetforPUSCH-r17), a set of P0 and α for PUCCH (p0AlphaSetforPUCCH-r17), and a set of P0 and α for SRS (p0AlphaSetforSRS-r17), and are used for transmission power control of each channel / signal (see FIG. 8B).

[0065] Also, in the Rel. 17 unified TCI framework, the RRC / MAC CE / DCI indicates one joint TCI or one set of {DL TCI, UL TCI} (separate TCI), where the indicated TCI applies to multiple UL / DL channels / RSs.

[0066] (Configuration of UL Power Control Parameter for TCI State) A case where the UL power control parameter is configured (or not configured) for the UL TCI state or the joint TCI state of the serving cell will be described. The UE may receive a configuration of a first path loss value corresponding to a UL reception point (UL TRP) or a configuration of a PL offset (relative PL) value that is a difference between the first path loss value and a second path loss value corresponding to a DL transmission point (DL TRP), and calculate the transmit power of a UL signal to be transmitted to the UL reception point based on the first path loss value or the PL offset value.

[0067] Whether or not a PL value or a PL offset (relative PL) value is set is determined / set for each TCI state ID. Also, the PL value or the relative PL (delta PL / PL offset) value may be determined / set for each TCI state ID. Hereinafter, the UL TCI state / joint TCI state may be simply referred to as a TCI state.

[0068] In the unified TCI state of Rel. 17, an RRC parameter (Uplink-powerControlId-r17) indicating UL power control is configured in the UE for each TCI state or UL TCI state to indicate TPC parameters (excluding PL RS). The UE may additionally be configured with information indicating a PL value or a relative PL (delta PL) value as an optional field for the TCI state (or UL TCI state) or Uplink-powerControlId-r17.

[0069] If no additional information indicating a PL value or a relative PL value is configured for a TCI state or UL TCI state (RRC parameter TCI-State or RRC parameter TCI-UL-State-r17), the UE may determine that the TCI state is associated with a macro TRP (DL transmission point).

[0070] If additional information indicating a PL value or a relative PL value is configured for a TCI state or an UL TCI state (parameter TCI-State or parameter TCI-UL-State-r17), the UE may determine that the TCI state is associated with an UL reception point.

[0071] The TCI state (RRC parameter TCI-State), the UL TCI state (RRC parameter TCI-UL-State-r17), and the RRC parameter indicating UL power control related to the TCI state (Uplink-powerControlId-r17) may be read as interchangeable.

[0072] [Option 1] Fig. 9 is a diagram showing a first example of power control parameters (e.g., RRC parameters) related to the TCI state. As shown in Fig. 7, the TCI state configuration has a parameter (pathlossReferenceRS-Id-r17) indicating a path loss RS and an UL power control parameter (ul-powerControl-r17). As shown in Fig. 8B, Uplink-powerControlId-r17 corresponding to ul-powerControl-r17 indicates the P of PUSCH, PUCCH, and SRS. ０ , parameters indicating α (p0AlphaSetforPUSCH-r17, p0AlphaSetforPUCCH-r17, p0AlphaSetforSRS-r17), and the like.

[0073] In the example shown in Fig. 9, the parameters for the macro TRP (TCI state #1) only include these conventional RRC parameters, but the parameters for the UL reception point (TCI state #3) also include a path loss value (PL value). Since no path loss RS is configured for TCI state #3 but a PL value is configured, the UE can determine the UL transmission power using the PL value as is, even if no path loss RS is configured.

[0074] The UE / base station may determine that the TCI state corresponds to a UL reception point based on at least one of the parameters relating to the TCI state not including a path loss RS and the parameters relating to the TCI state including a PL value. The UE / base station may determine that the TCI state corresponds to a macro TRP based on at least one of the parameters relating to the TCI state including a path loss RS and the parameters relating to the TCI state not including a PL value.

[0075] [Option 2] Fig. 10 is a diagram showing a second example of power control parameters (e.g., RRC parameters) related to TCI states. The example shown in Fig. 10 differs from the example shown in Fig. 9 in that a path loss RS is set for TCI state #3 and a relative PL (PL offset) is set instead of a PL value.

[0076] In the example of Figure 10, the UE may use the PL value obtained by applying (adding or subtracting) the received relative PL (PL offset) value to the PL value estimated from the DL RS transmitted from the macro TRP to calculate the transmission power.

[0077] The UE / base station may determine that the TCI state corresponds to a UL reception point based on at least one of the parameters relating to the TCI state including a path loss RS and the parameters relating to the TCI state including a relative PL (PL offset).The UE / base station may determine that the TCI state corresponds to a macro TRP based on at least one of the parameters relating to the TCI state not including a path loss RS and the parameters relating to the TCI state not including a relative PL (PL offset).

[0078] Fig. 11 is a diagram showing an example of the setting of the TCI-State information element in Option 2. As shown in Fig. 11, identification information indicating the PL offset value (pathlossOffset-Id-r18) may be included in the TCI-State information element.

[0079] Fig. 12 is a diagram showing an example of the setting of the TCI-UL-State information element in Option 2. As shown in Fig. 12, identification information indicating the PL offset value (pathlossOffset-Id-r18) may be included in the TCI-UL-State information element.

[0080] FIG. 13 is a diagram illustrating an example of setting a PUSCH-PowerControl information element in Option 2. As illustrated in FIG. 13, in the PUSCH-PowerControl information element, lists (pathlossOffsetToAddModList, pathlossOffsetToReleaseList) including multiple parameters (pathlossOffset-Id-r18) indicating PL offset values ​​may be configured. maxNrofPathlossOffsets-r18 indicates the number (maximum number) of UL reception points, i.e., the number (maximum number) of PL offset values, and is set to, for example, 2 or 4. Furthermore, any value between −16 and 15 is set as the PL offset value (pathlossOffset) corresponding to pathlossOffset-Id-r18. Note that the values ​​of maxNrofPathlossOffsets-r18 and pathlossOffset are not limited to the example illustrated in FIG. 13 .

[0081] [Option 3] Fig. 14 is a diagram showing a third example of power control parameters (e.g., RRC parameters) related to the TCI state. The UE may receive information (such as a flag) indicating the UL reception point as a parameter corresponding to the TCI state of the UL reception point. In the example shown in Fig. 14, an explicit indication of the UL reception point (UL only TRP) (UL only TRP flag) is set as a parameter corresponding to the UL reception point (TCI state #3).

[0082] The UE may determine that a TCI state corresponds to a UL reception point if the parameters for the TCI state include an explicit indication of a UL reception point, and may determine that a TCI state corresponds to a macro TRP if the parameters for the TCI state do not include an explicit indication of a UL reception point.

[0083] The example of Fig. 14 may be combined with the examples of Fig. 9 and Fig. 10. For example, an explicit indication of a UL reception point (UL only TRP) may be added as a parameter for the UL reception point (TCI state #3) in Fig. 9 and Fig. 10.

[0084] (Asymmetric DL sTRP / UL mTRP) When the PL-RS is transmitted to the UE from the DL sTRP, the PL offset for the PL calculation may be set to the UL TRP(s).

[0085] The channels / RS for which PL offset is supported may be all UL channels / RS after RRC connection setup, such as SRS, PUSCH, PUCCH, and PRACH (PDCCH order for UL TRP, PRACH may be used when two TAs are applied).

[0086] For PUSCH / PUCCH / SRS, a PL offset value may be configured for each UL TCI state. If the PL offset is configured for each UL TCI state, the UE may calculate the PL using the PL offset value.

[0087] For the PRACH, a set of PL offset values ​​may be configured in the PRACH configuration (PRACH-Config in RRC). The PDCCH may indicate one of the PL offset values ​​for the PDCCH-ordered PRACH.

[0088] Figure 15 shows an example of setting a PL offset in the case of DL sTRP / UL mTRP. In the example of Figure 15, since the PL-RS is transmitted from the DL TRP to the UE, the PL offset does not need to be set (absent). Since the PL-RS is not transmitted from the UL TRP to the UE, the PL offset is set for each UL TRP / TCI (X1, X2).

[0089] 16A is a diagram showing an example of setting a transmission power parameter corresponding to DL TRP (TCI state #0). As shown in FIG. 16A, the PL offset does not need to be set (absent) for DL ​​TRP (TCI state #0).

[0090] 16B is a diagram showing an example of setting a transmission power parameter corresponding to UL TRP (TCI state #1). As shown in FIG. 16B, a PL offset (X1) may be set for UL TRP (TCI state #1).

[0091] (PRACH PL Setting) The UE may control the transmission power when transmitting the PRACH to the UL reception point based on the configured (received) PL value. When the UL is the PRACH, the UE can transmit the PRACH to the UL reception point in the RRC connected state. In this case, the UE may control the transmission power of the PRACH based on the configured PL value. Therefore, the UE may determine the transmission power control of the PRACH based on the RRC configuration that sets the PL value or PL offset.

[0092] The PRACH configuration in the present disclosure may refer to the configuration regarding the PRACH in the RRC / MAC CE / DCI.

[0093] [Option 1] The TCI state may be configured for each PRACH resource / PRACH configuration.

[0094] [Option 2] The PL value or PL offset may be configured in the UE for each PRACH configuration.

[0095] In the case of a PDCCH-ordered PRACH, for example, a 1-bit reserved field in the DCI may indicate whether a PL value or a PL offset should be applied to the triggered PRACH, which may then imply that the PRACH is transmitted to a UL reception point.

[0096] If the field is 0, the UE may measure the PL based on the configured PL RS. If the field is 1, the UE may use the PL value or PL offset associated with the UL reception point to control the UL (PRACH) transmit power.

[0097] (Analysis) As mentioned above, in order to expand UL coverage, UL high-density deployment is being considered, in which UL reception points that mainly perform UL reception are provided in addition to DL transmission points. Also, Heterogeneous Networks (HetNets) using macro Base Stations (BSs) and micro BSs are being considered.

[0098] However, when a path loss (PL) calculation RS (path loss RS) is transmitted from a DL transmission point / macro BS, it is not clear how to determine the transmission power when a terminal transmits UL to a UL reception point / micro BS. If the UL transmission power cannot be controlled appropriately, there is a risk that the throughput will decrease.

[0099] Therefore, the present inventors have conceived a method for appropriately controlling UL transmission power.

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

[0101] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

[0102] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0103] In the present disclosure, terms such as notify, activate, deactivate, indicate (or indicate), select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0104] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, fields, information elements (IEs), settings, etc. may be interchangeable. In the present disclosure, Medium Access Control (MAC) control elements (CEs), update commands, activation / deactivation commands, etc. may be interchangeable.

[0105] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

[0106] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0107] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0108] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0109] In the present disclosure, the terms single TRP, channel / signal using single TRP, channel using one TCI state / spatial relationship, multi-TRP not enabled by RRC / DCI, multiple TCI states / spatial relationships not enabled by RRC / DCI, a CORESETPoolIndex value of 1 not set for any CORESET, and no code point in the TCI field mapped to two TCI states may be read interchangeably.

[0110] In the present disclosure, multi-TRP, channel / signal using multi-TRP, channel using multiple TCI states / spatial relationships, multi-TRP enabled by RRC / DCI, multiple TCI states / spatial relationships enabled by RRC / DCI, and at least one of multi-TRP based on a single DCI and multi-TRP based on multiple DCI may be read interchangeably.

[0111] The present disclosure may assume at least one of single TRP, multi-TRP with multi-DCI, multi-TRP with single DCI, scenario 1 or scenario 2 above.

[0112] In the present disclosure, TCI, TCI state, TCI state ID, TCI state list / set / pool / group, and TCI state list / set / pool / group ID may be interchangeable. TCI and UL / joint TCI may be interchangeable.

[0113] The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless. The UL reception point may be treated as a network (NW) or a base station. The UL reception point may be capable of transmitting downlink (DL) signals (e.g., PL values) and may be applied to base stations forming a macrocell. For example, the UL reception point may not transmit downlink data but may transmit control signals / channels.

[0114] In the present disclosure, the terms base station, TRP, UL receiving point, UL TRP, UL only TRP, micro cell, micro BS, and micro TRP may be interchangeable. An UL receiving point primarily performs UL reception. An UL receiving point may perform only UL reception, or may perform UL reception and DL transmission.

[0115] In the present disclosure, the terms base station, TRP, DL transmission point, DL TRP, DL only TRP, UL / DL TRP, macro cell, macro BS, macro TRP, and central TRP may be interchangeable. A DL transmission point primarily performs DL transmission. A DL transmission point may perform only DL transmission, or may perform UL reception and DL transmission.

[0116] In the present disclosure, UL high density deployment, distributed TRP mode, separated location mode of transmitting / receiving points, distributed transmitting / receiving mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be read interchangeably.

[0117] In the present disclosure, the terms absolute PL, path loss (PL), PL value, PL parameter, PL RS, and PL RSID may be interchangeable. Ｏ The offset, the offset of α, the offset of power / power density [x dBm], the path loss (PL), the PL value, and the PL parameter may be read interchangeably.

[0118] In the present disclosure, using / applying a PL offset may mean using a PL value obtained by applying (adding or subtracting) a PL offset to a PL value estimated / calculated based on a DL RS transmitted from a DL transmission point / DL TRP or a received PL value in calculating the transmission power of a UL signal (e.g., PUCCH / PUSCH / PRACH / SRS) to be transmitted to a UL reception point / UL TRP. The PL offset and the PL offset value may be interchangeable.

[0119] The gNB (base station) in the present disclosure may be a DL transmission point or a UL reception point, or may be a base station above the DL transmission point or UL reception point (capable of communicating with the DL transmission point / UL reception point).

[0120] (Wireless communication method) <Problem 1> After a PL offset is set for a TCI state, the UE may move. In this case, the PL offset before and after the movement should be different.

[0121] Figure 17 shows an example of PL changes due to UE movement. In Figure 17, the UE is located between the DL TRP and the UL TRP. Assume that the PL for this UE's DL TRP is PL #1 and the PL for the UL TRP is PL #2. In this case, the PL offset is PL #2 - PL #1 [dB].

[0122] After that, when the UE moves a predetermined distance (distance corresponding to PL Δ) toward the DL TRP side, the PL for the UE's DL TRP becomes PL #1-Δ, and the PL for the UL TRP becomes PL #2+Δ. In this case, the PL offset is (PL #2+Δ)-(PL #1-Δ) = PL #2-PL #1+2Δ [dB]. In other words, the PL offset has increased by 2Δ [dB] compared to before the movement. In such a case, the UE needs to update the PL offset.

[0123] However, as shown in the examples of Figures 11 to 13, when the PL offset is included in the RRC information element, RRC reconfiguration is required to update the PL offset, which increases the overhead due to RRC reconfiguration. Therefore, updating the PL offset based on the MAC CE (or DCI) will be considered.

[0124] <First Embodiment> <<1-1>> A UE may receive a MAC CE / DCI indicating a PL offset value corresponding to a UL / joint TCI state and directly update the PL offset value. In this case, many MAC CE / DCIs may be required to update different PL offset values ​​for different UL / joint TCI states.

[0125] <<1-2>> The UE may receive a MAC CE / DCI including information indicating a difference between the configured PL offset and the latest PL offset (PL offset), and may update the PL offset value based on the PL offset. The UE may apply the updated PL offset to determine the UL transmit power for the UL reception point. The PL offset may correspond to [some or all] UL / joint TCI states.

[0126] Hereinafter, the offset of the PL offset may be simply referred to as the offset (or the offset value). Hereinafter, the offset instruction by the MAC CE will be mainly described, but the instruction by the DCI may be the same (MAC CE may be read as DCI). The offset and the difference may be read as each other.

[0127] The offset of the PL offset may indicate a difference between the PL offset previously set by RRC signaling (e.g., any of Figures 11 to 13) and the latest PL offset. The offset of the PL offset may indicate a difference between the PL offset previously set by MAC CE / DCI and the latest PL offset.

[0128] The MAC CE / DCI may include the offset of one PL offset for one UL / joint TCI state.

[0129] The MAC CE / DCI may include offsets for one PL offset for all / multiple UL / joint TCI states.

[0130] If an offset for the PL offset is indicated, the UE adds / subtracts the indicated offset value to / from the PL offset value set for each UL / joint TCI. For example, if the PL offset for the UL / joint TCI state is X1 dB and x dB is indicated as the offset for the PL offset, the UE updates the new PL offset to X1+x dB (or X1-x dB).

[0131] Alternatively, the UE may update the new PL offset to X1+2x dB (or X1-2x dB). This is because, as shown in the example of Figure 17, when the UE moves a predetermined distance (a distance equivalent to PLΔ) toward the DL TRP, the PL offset increases by 2Δ [dB] compared to before the movement.

[0132] The timing of updating the PL offset using the offset of the PL offset indicated by the MAC CE / DCI will be described below.

[0133] The UE may use the updated value of the PL offset for TPC calculation / decision based on the timing of updating / applying the PL offset.

[0134] For example, the UE may determine the timing of applying / updating the PL offset based on the timing of applying / updating the TCI state (e.g., indicated TCI state, UL / joint TCI) by the MAC CE / DCI.

[0135] The "MAC CE" in the following application / update timing example 1 and application / update timing example 2 may be a MAC CE including a PL offset offset. Also, the PDSCH that transmits the MAC CE may be interpreted as a PDSCH scheduled by DCI that includes a PL offset offset.

[0136] <<<<Application / Update Timing Example 1>>> For example, the UE may determine to apply / update the PL offset at the same timing as the update / application timing of the indicated TCI state (e.g., UL / joint TCI).

[0137] For example, the UE may receive a PDSCH carrying a MAC CE and determine to apply / update the PL offset after a certain period of time (e.g., 3 ms) has elapsed since the UE received the PDSCH carrying a MAC CE and transmitted a positive HARQ-ACK for the PDSCH.

[0138] 18A is a diagram showing an example of updating the PL offset according to application / update timing example 1. In the example shown in FIG. 18A, the UE receives a PDSCH carrying a MAC CE for updating the PL offset and transmits a positive HARQ-ACK for the PDSCH. The UE determines to update the PL offset 3 ms after transmitting the HARQ-ACK.

[0139] According to application / update timing example 1, the specific period is a fixed value, which can facilitate implementation in the UE.

[0140] <<<<Application / Update Timing Example 2>>> Furthermore, for example, the UE may determine to apply / update the PL offset at a timing based on the timing related to the update / application timing of the indicated TCI state (e.g., UL / joint TCI) and a specific time offset (e.g., Y symbols / ms).

[0141] The value Y may be specified in advance in a specification, may be configured / instructed to the UE using RRC / MAC CE / DCI, may be determined based on a report of UE capability information, or may be determined based on a combination of at least two of these.

[0142] For example, the UE may determine to apply / update the PL offset at a timing obtained by adding (or subtracting) a specific time offset to the timing related to the update / application timing of the indicated TCI state.

[0143] For example, the UE may receive a PDSCH carrying a MAC CE and determine to apply / update the PL offset after a specific period (e.g., 3 ms) plus (or minus) a specific time offset has elapsed since the UE received the PDSCH carrying a MAC CE and transmitted a positive HARQ-ACK for the PDSCH.

[0144] 18B is a diagram showing an example of updating the PL offset according to application / update timing example 2. In the example shown in FIG. 18B, the UE receives a PDSCH carrying a MAC CE for updating the PL offset and transmits a positive HARQ-ACK for the PDSCH. The UE determines to update the PL offset after (3+Y) ms have elapsed since the transmission of the HARQ-ACK.

[0145] According to application / update timing example 2, the PL offset can be applied / updated at an appropriate timing.

[0146] <<<<Setting Example of PL Offset>>> The offset of the PL offset may be a positive value or a negative value, because the UE may move in the direction of the DL TRP or the direction of the UL TRP.

[0147] Alternatively, only positive values ​​or only negative values ​​may be set for the offset of the PL offset.

[0148] A method for setting / indicating an offset by a MAC CE will be described. The association (table) between bit information and offset in a MAC CE may be defined in a specification or may be set in advance by higher layer signaling (e.g., RRC signaling).

[0149] 19A is a diagram showing a first example of association between bit information and offsets in a MAC CE. For 5-bit information (value=0,...31) in a MAC CE, offsets are set from -15 to 16 in 1 dB steps.

[0150] 19B is a diagram showing a second example of association between bit information and offsets in a MAC CE. For 4-bit information (value=0,...15) in a MAC CE, offsets are set from -7 to 8 in 1 dB steps.

[0151] Any of multiple associations (tables) of bit information and offsets may be used. For example, multiple tables may be set / defined, and the UE may select one of the tables based on a predetermined rule (such as a band or SCS), or may select one of the tables according to a setting / instruction of higher layer signaling / physical layer signaling.

[0152] To determine a table such as that shown in Figures 19A / 19B, at least three of the offset's "start value (e.g., -15)," "end value (e.g., 16)," "step size (1)," and "bit size (5)" may be set / defined.

[0153] <<<<Variations>>> The association between the bit information indicated by the MAC CE / DCI and the offset of the PL offset (a value that does not distinguish between positive and negative) may be defined in the specifications or may be set by higher layer signaling, and the positive or negative offset may be indicated by the MAC CE / DCI.

[0154] The MAC CE / DCI may include a field indicating whether the offset value is positive (+) or negative (-). For example, the positive / negative offset may be indicated by an R bit in the MAC CE indicating the offset of the PL offset (described later).

[0155] 20A is a diagram showing a first example of a MAC CE including a field indicating whether the offset is positive (+) or negative (-). For example, P=0 may indicate positive (+) and P=1 may indicate negative (-). PLO ID indicates the PL offset ID, and offset value indicates the offset value of the PL offset (the same applies to the other drawings).

[0156] 20B is a diagram showing a second example of a MAC CE including a field indicating whether the offset is positive (+) or negative (-). In FIG. 20B, the MAC CE includes multiple offset values, each of which has a corresponding P. For example, P=0 may indicate that the corresponding offset is positive (+), and P=1 may indicate that the corresponding offset is negative (-).

[0157] 21A is a diagram showing a first example of association between bit information and PL offset (values ​​that can be positive or negative). For 5-bit information (value = 0, ... 31) in MAC CE, the offset is set from 0 to 31 in 1 dB steps.

[0158] 21B is a diagram showing a second example of the association between bit information and PL offsets (values ​​that can be positive or negative). For 4-bit information (value = 0, ... 15) in a MAC CE, the offsets are set from 0 to 15 in 1 dB steps.

[0159] For example, after the association of FIG. 21A or FIG. 21B is defined in a specification or configured by higher layer signaling, the UE may be instructed by a MAC CE whether the offset is positive or negative, as shown in the example of FIG. 20.

[0160] The MAC CE including the offset of the PL offset will be described in detail in "MAC CE-based PL offset offset" below. As described below, the offset of the PL offset may be set for each PLO ID and TCI state ID. The TCI state ID may be the ID of the UL / joint TCI state.

[0161] The offset of the PL offset may be indicated per BWP ID / serving cell ID that applies to all PL IDs or all UL / joint TCI states.

[0162] When the UE moves to a DL TRP or UL TRP, the PL offset applies to all TCI states of FR1. For FR2, the PL offset is TCI state specific (i.e., the PL value / PL offset may vary depending on the measured TCI state). Therefore, the following variations are possible for FR1 and FR2: For FR1: The PL offset may be indicated per PLO ID or BWP ID / serving cell ID, which applies to all UL / joint TCI states. For FR2: The PL offset may be indicated per PLO ID, UL / joint TCI state.

[0163] According to the first embodiment (1-2), the PL offset is updated using an offset instruction for the PL offset, which reduces the number of bits used compared to directly instructing the PL offset, thereby suppressing overhead.

[0164] <MAC CE-based PL offset offset> The MAC CE-based PL offset update will be described in detail.

[0165] The UE may update the offset of the PL offset using the MAC CE.

[0166] <<Option 1>> For a UE, a set of PL offset offsets may be configured per BWP / per serving cell / per UE / per CORESET pool index.

[0167] The MAC CE for offset update of PL offset may include fields for at least one of the following: Serving cell ID, BWP ID, PL offset (PLO) ID, offset value of PL offset [corresponding to PLO ID], and reserved bits.

[0168] If a set of offsets is configured for each serving cell, the field related to the BWP ID may be ignored or replaced with a reserved bit.

[0169] If a set of offsets is configured per UE, the field related to the serving cell ID / BWP ID may be ignored or replaced with a reserved bit.

[0170] When a set of offsets is configured for each CORESET pool index, a specific field in the MAC CE (for example, one reserved bit field) may be replaced with a field indicating the value (0 or 1) of the CORESET pool index.

[0171] <<Option 2>> The number of offset values ​​for the PL offset may be set / defined.

[0172] The size of the PLO ID field may be expressed in log2(number of offset values) (or Ceil(log2(number of offset values))). In this disclosure, CeilA may refer to the output of the ceiling function of A.

[0173] For example, if a maximum of four offset values ​​are set, the PLO ID field may be defined as two bits.

[0174] <<Option 3>> The range (e.g., maximum value / minimum value / step size) of the offset value field of the PL offset may be set / defined.

[0175] The size of the field may be expressed in log2(number of distinct values ​​of offset) (or Ceil(log2(number of distinct values ​​of offset))).

[0176] For example, if the range of offset values ​​is specified as {0, 1, ..., 31} dB (i.e., minimum value = 1, maximum value = 31, 1 dB step size), the size of the field may be 5 bits.

[0177] <<Option 4>> The number of offset values ​​of the PL offset indicated by one MAC CE may be set / defined.

[0178] <<<Option 4-A>>> For example, one MAC CE may indicate one offset value corresponding to one PLO ID.

[0179] In this case, the MAC CE may include a field indicating a serving cell ID, a field indicating a BWP ID, a field indicating one PLO ID, a field indicating one offset value, and a reserved bit field (see FIG. 22).

[0180] <<<Option 4-B>>> For example, one MAC CE may indicate multiple offset values, each of which may correspond to one (different) PLO ID.

[0181] For example, as shown in Figure 23A, one MAC CE may include a field indicating four offset values, each of which may correspond to a different PLO ID (e.g., PLO IDs 1-4).

[0182] For example, as shown in Fig. 23B, one MAC CE may have a configuration that does not include some of the reserved bit fields included in the MAC CE described in the above-mentioned Fig. 23A. Note that the positions of the reserved bits in the MAC CE shown in Fig. 23B are not limited to this example.

[0183] Also, for example, one MAC CE may include a PLO ID and an offset value corresponding to the PLO ID, as shown in Fig. 24. The PLO ID field and the corresponding offset value field may be located in the same octet.

[0184] The Cn field located in the same octet as the nth PLO ID / PL offset value shown in Fig. 24 may be a field indicating the presence of a field related to the (n+1)th PLO ID / offset value. When the Cn field indicates a first value (e.g., 0 (or 1)), it may indicate that the field related to the (n+1)th PLO ID / offset value is present, and when the Cn field indicates a second value (e.g., 1 (or 0)), it may indicate that the field related to the (n+1)th PLO ID / offset value is not present.

[0185] <<<Option 4-C>>> For example, one MAC CE may indicate one or more offset values ​​for each TCI state (TCI state ID).

[0186] <<<<Option 4-C-1>>>> One MAC CE may be used to indicate one set of offset values ​​per TCI state [ID].

[0187] For example, as shown in FIG. 25A, one MAC CE includes a TCI state ID and one offset value corresponding to the TCI state ID (i.e., one set of a TCI state ID and an offset value).

[0188] Note that in option 4-C-1, multiple TCI states may be associated with the same offset value / PLO ID.

[0189] In this case, only the offset of the TCI State ID indicated by one MAC CE may be updated.

[0190] In this case, the offsets corresponding to a plurality of (for example, all) TCI state IDs associated with the offset value corresponding to one MAC CE may be updated.

[0191] <<<<<Option 4-C-2>>>> Multiple sets of offset values ​​for each TCI state [ID] may be indicated using one MAC CE.

[0192] For example, as shown in Fig. 25B, one MAC CE includes multiple sets of TCI state IDs and PL offset values ​​corresponding to the TCI state IDs. Note that the Cn field included in the MAC CE shown in Fig. 25B may be a field indicating the same meaning as the Cn field included in the MAC CE shown in Fig. 24 described above.

[0193] <Issue 2> The method of indicating a closed loop index to an SRS resource in the Rel. 17 / 18 TCI framework has been considered as follows: ・If srs-PowerControlAdjustmentStates of the SRS resource set is set to separateClosedLoop, the SRS is associated with a separate closed loop. ・Otherwise, closedLoopIndex-r17 in the UL / joint TCI state indicates the SRS closed loop associated with the PUSCH. In such a case, the candidate values ​​of "i0" and "i1" of closedLoopIndex-r17 of the SRS indicate the first and second closed loops associated with the PUSCH.

[0194] The following specifies how to maintain all SRS resources in the same SRS resource set to use the same power control parameters: If "followUnifiedTCI-StateSRS" is provided for an SRS resource set, there is no possibility of using different P0 / α values ​​for different SRS resources in the same SRS resource set depending on the associated TCI state. If "followUnifiedTCI-StateSRS" is not provided for an SRS resource set, the P0 / α values ​​are the same (based on the lowest SRS resource ID in the SRS resource set).

[0195] That is, all SRS resources in the same SRS resource set use the same P0 / α value, PL RS, and closed-loop index. Therefore, we considered specifying the PL offset in the same way.

[0196] Second Embodiment The PL offset may be set in the UL / joint TCI state (associated with the UL / joint TCI state). The correspondence between the PL offset and the SRS resource in this case will be described.

[0197] The UE may receive a PL offset configuration associated with the UL / joint TCI state and apply the same PL offset to all SRS resources in the same SRS resource set (FIG. 26). This is because all SRS resources included in the same SRS resource set should be transmitted with the same transmission power. The PL offset configuration in this embodiment may use the configuration methods shown in the examples of FIGS. 10 to 13, or may use the PL offset configuration shown in the first embodiment.

[0198] When the parameter "followUnifiedTCI-StateSRS" is set to enabled, the UE applies the indicated UL-only TCI or joint TCI state for the SRS resource set. This parameter is set for aperiodic SRS of beam management or SRS of any time-domain operation such as codebook, non-codebook, and antenna switching. The UE may decide to apply PL offsets to all SRS resources in the SRS resource set depending on whether the parameter "followUnifiedTCI-StateSRS" is provided (enabled or not).

[0199] For example, if "followUnifiedTCI-StateSRS" is provided (enabled) for an SRS resource set, the UE may use the same PL RS and PL offset associated with the indicated UL / joint TCI state for all SRS resources in the SRS resource set.

[0200] For example, if "followUnifiedTCI-StateSRS" is not provided (enabled) for an SRS resource set, the UE may use, for all SRS resources in the SRS resource set, the PL RS and PL offset associated with the UL / joint TCI state of the SRS resource with the lowest SRS resource ID in the SRS resource set.

[0201] For example, if "followUnifiedTCI-StateSRS" is not provided (enabled) for an SRS resource set, the UE may use the PL RS and PL offset value associated with the UL / joint TCI state with the lowest TCI state ID.

[0202] If the PL offset is set to UL / joint TCI state, the UE may use the PL offset to calculate the transmit power. In this case, the PL is updated to "PL + PL offset" or "PL - PL offset".

[0203] If the PL offset is not configured in the UL / joint TCI state, the UE may use the conventional method to calculate the transmit power (without using the PL offset in the transmit power calculation).

[0204] According to the second embodiment, it is possible to determine appropriate transmission power for all SRS resources included in the same SRS resource set.

[0205] Third Embodiment The PL offset may be configured within (associated with) the UL / joint TCI state, in which case the UE may apply the PL offset associated with the UL / joint TCI state to the PUSCH / PUCCH.

[0206] In the Rel. 17 TCI framework (when the UE is configured with a list of DL / joint TCI states (dl-OrJointTCI-StateList) and one of the TCI states is indicated by the MAC CE / DCI), the indicated UL / joint TCI state is always applied to the PUSCH / PUCCH. Therefore, if a PL offset is configured for the UL / joint TCI state, the UE applies the PL offset associated with the indicated UL / joint TCI state to the PUSCH / PUCCH.

[0207] In the Rel. 18 TCI framework (when a list of DL / joint TCI states (dl-OrJointTCI-StateList) is configured in the UE and two of the TCI states are indicated by the MAC CE / DCI), either an indication of the applied TCI state (applyIndicatedTCIState={1st, 2nd, both}) is configured for each resource / resource group of the PUCCH, or the SRS resource set indicator field of the scheduling DCI indicates one or both of the indicated TCI states for the single DCI-based dynamic grant PUSCH.

[0208] If one or both of two UL / joint TCI states are indicated / applied to the PUSCH / PUCCH and a PL offset is configured / associated with the UL / joint TCI state, the UE may apply the PL offset associated with the indicated UL / joint TCI state to the PUSCH / PUCCH.

[0209] The UE may decide that if both of two UL / joint TCI states are indicated / applied to the PUSCH / PUCCH, not to apply the PL offset associated with the indicated UL / joint TCI state to the PUSCH / PUCCH.

[0210] Variation: The PL offset may be set only for either the first or second indicated UL / joint TCI state, or if the PL offset is set / associated with a UL / joint TCI state, the UE may assume / expect that there is only one indicated UL / joint TCI state.

[0211] If the PL offset is set to UL / joint TCI state, the UE may use the PL offset to calculate the transmit power. In this case, the PL is updated to "PL + PL offset" or "PL - PL offset".

[0212] If the PL offset is not configured in the UL / joint TCI state, the UE may use the conventional method to calculate the transmit power (without using the PL offset in the transmit power calculation).

[0213] According to the third embodiment, the PL offset associated with the UL / joint TCI state can be used to appropriately determine the transmit power of the PUSCH / PUCCH.

[0214] <PRACH Transmission Power Control: Physical Layer Procedures for Control / Uplink Power Control / Physical Random Access Channel> The actual PRACH transmission power is determined based on the target preamble reception power, the path loss of the RS, and the maximum output power limit.

[0215] The UE determines the (actual) transmit power P of the PRACH on the active UL BWP b of carrier f of serving cell c based on the DL RS for serving cell c in transmission occasion i. PRACH,b,f,c (i) is determined as follows: P PRACH,b,f,c (i) = min{P CMAX,f,c (i),P PRACH,target,f,c +PL b,f,c} [dBm]

[0216] P CMAX,f,c (i) is the maximum output power configured for the UE for carrier f of serving cell c in transmission occasion i. P PRACH,target,f,c is the PRACH target received power PREAMBLE_RECEIVED_TARGET_POWER provided by higher layers for the active UL BWP b of carrier f of serving cell c. b,f,cis the path loss for the active UL BWP b of carrier f based on the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c, and is calculated by the UE as (reference signal power (ss-PBCH-BlockPower) [dBm] - upper layer filtered RSRP [dBm]) [dB]. If the active DL BWP is the initial DL BWP and is for multiplexing pattern 2 or 3 of the SS / PBCH block and CORESET, the UE calculates the path loss for the active UL BWP b of carrier f based on the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c, and is calculated by the UE as (reference signal power (ss-PBCH-BlockPower) [dBm] - upper layer filtered RSRP [dBm]) [dB]. b,f,c Determine.

[0217] The DL RS used in the path loss calculation may be referred to as a pathloss (PL)-RS, a pathloss reference RS, or the like.

[0218] In the existing RACH process, if a UE sends a PRACH and does not receive a network RAR or contention / conflict resolution Msg 4 within a specific time window, and the random access process is not completed, the UE will retransmit the PRACH after a random backoff time.

[0219] <Configuration of PRACH PL Value or PL Offset Value> The UE may receive configuration information of the PRACH PL value or PL offset value to be transmitted to the UL reception point (UL TRP) via higher layer signaling / physical layer signaling, and control the transmission power of the PRACH based on the configuration information. For example, the configuration of the PL value or PL offset value may be included in an RRC information element (e.g., ServingCellConfigCommon / ServingCellConfig / BWP / PRACH-Config / PDSCH-Config, etc.). The configured PL value or PL offset may be used only for the PRACH, or may be used for all or part of the PRACH / PUSCH / PUCCH / SRS. The RRC information element may be an information element other than the TCI-State information element.

[0220] [Option 1] In the configuration information, the PRACH PL value or PL offset value may be set to only one value (common value) for all configured SSB / TCI states.

[0221] [Option 2] In the configuration information, the PRACH PL value or PL offset value may be set to one value (a different value) for each configured SSB / TCI state, i.e., a list of PL values ​​or PL offset values ​​for the SSB / TCI states may be configured.

[0222] <Number of PL Values ​​or PL Offset Values> The number of PL values ​​or PL offset values ​​set for PRACH (i.e., the number of UL TRPs) will be described. There may be one or more UL TRPs for a PL-RS (DL TRP). Therefore, the number of PL values ​​or PL offset values ​​set may be one or more.

[0223] [Option 1] A different PL value or PL offset value (or set of PL values) may be associated with each SSB / CSI-RS / TCI State ID, i.e., there may be as many PL values ​​or PL offset values ​​as there are SSB / CSI-RS / TCI State IDs.

[0224] 27A is a diagram showing an example of the correspondence between SSB IDs / TCI state IDs and PL offset values. As shown in FIG. 27A, a PL offset value is defined for each SSB ID / TCI state ID. The UE may determine each PL offset value based on the set SSB ID / TCI state ID. Alternatively, a PL value may be set instead of each PL offset value.

[0225] [Option 2-2] The UE may receive a PDCCH order (DCI indicating PRACH transmission) including multiple bits indicating which PL offset value to apply. In option 2, the PL offset value may be replaced with the PL value.

[0226] The PDCCH order may include bits indicating a PL offset value. The number of bits (X bits) may be fixed (e.g., X=2) or may be variable depending on the number of PL values ​​or PL offset values ​​to be set. For example, the number of bits may be log ２ It may be (Y) bits, where Y is the number of PL values ​​or PL offset values ​​to be set.

[0227] 27B is a diagram showing a first example of correspondence between DCI code points and PL offset values. In the example of FIG. 27B, a 2-bit DCI code point is assigned to four PL offset values. A PL value may be set instead of each PL offset value.

[0228] Figure 27C is a diagram showing a second example of the correspondence between DCI code points and PL offset values. In the example of Figure 27C, one bit of the DCI code point is assigned to two PL offset values. A PL value may be set instead of each PL offset value.

[0229] The PL offset value for a DCI code point may be fixed or may be changeable by higher layer signaling (e.g., RRC / MAC CE).

[0230] The UE may report the maximum number of PL offset values ​​set for each SSB / CSI-RS / TCI state as UE capability information. The UE may report the maximum number of SSB / CSI-RS / TCI states for which PL offset values ​​are set as UE capability information.

[0231] <PRACH Power Ramping> Figure 28 is a diagram showing information elements (RACH-ConfigGeneric) related to the RACH in Rel. 18. The powerRampingStep included in RACH-ConfigGeneric in Figure 28 is directly related to the power control mechanism during the random access procedure. If the first preamble transmission fails (the UE does not receive a response from the gNodeB), the UE increases the transmission power for the next preamble transmission.

[0232] For example, "dB4" indicates a power ramp step size of 4 dB. Each subsequent preamble transmission increases by this step size until a response is received or the maximum number of attempts is reached.

[0233] <Problem 3> It is unclear whether a PL offset is applied to a PRACH (especially a PRACH ordered by a PDCCH). It is also unclear whether the PL offset is applied only to the first transmission or to retransmissions, and if so, how the PL offset relates to the implementation of power ramping.

[0234] <Fourth Embodiment> <<PRACH Transmission with One DCI>> A UE may receive one DCI (PDCCH order) that triggers one or more PRACH transmissions, transmit PRACHs, and autonomously perform PRACH retransmissions for one PRACH procedure (e.g., in the event of a transmission failure). The UE may or may not apply a PL offset to the PRACH retransmissions.

[0235] <<<Application of PL Offset>>> Regarding whether or not to apply a PL offset to a PRACH of a PDCCH order, any of the following examples (1) to (3) may be applied.

[0236] (1) PL offset is not applied to PRACH in PDCCH order.

[0237] (2) The PL offset is applied to the PRACH of the PDCCH order. Each DCI does not need to include a field indicating whether a PL offset is applied to each PRACH. In this case, whether a PL offset is applied may be determined in advance, configured / indicated by the RRC / MAC CE, or transmitted / reported as UE capability information.

[0238] (3) PL offset is applicable to PRACHs ordered by PDCCHs. A field indicating whether a PL offset is applied to each PRACH may be included in each DCI.

[0239] <<<Application of Power Ramping>>> Regarding whether or not power ramping is applied to a PRACH of a PDCCH order, any of the following examples (1) to (3) may be applied.

[0240] (1) Power ramping may not be applied to the PDCCH-ordered PRACH (FIG. 29A), i.e., the UE may not increase the transmit power of the retransmitted PRACH from the transmit power of the initial PRACH.

[0241] (2) Power ramping may be applied to PDCCH-ordered PRACHs (FIG. 29B). That is, the UE may increase the transmission power of retransmitted PRACHs (second and subsequent PRACHs) from the transmission power of the initial PRACH. The DCI may not include a field indicating whether power ramping is applied to each PRACH. In this case, whether power ramping is applied may be determined in advance, configured / indicated by the RRC / MAC CE, or transmitted / reported as UE capability information.

[0242] (3) Power ramping is applicable to PDCCH-ordered PRACHs. The DCI may include a field indicating whether power ramping is applied to each PRACH.

[0243] <<PRACH Transmission with Multiple DCIs>> A UE may receive one DCI (PDCCH order) that triggers one PRACH transmission, transmit a PRACH, and then perform a PRACH retransmission for one PRACH procedure (e.g., in the event of a transmission failure) as instructed by another DCI. The UE may or may not apply a PL offset to the PRACH retransmission.

[0244] <<<Application of PL Offset>>> Regarding whether or not to apply a PL offset to a PRACH of a PDCCH order, any of the following examples (1) to (3) may be applied.

[0245] (1) PL offset is not applied to PRACH in PDCCH order.

[0246] (2) The PL offset is applied to the PRACH of the PDCCH order. Each DCI does not need to include a field indicating whether a PL offset is applied to each PRACH. In this case, whether a PL offset is applied may be determined in advance, configured / indicated by the RRC / MAC CE, or transmitted / reported as UE capability information.

[0247] (3) PL offset is applicable to PRACHs ordered by PDCCHs. A field indicating whether a PL offset is applied to each PRACH may be included in each DCI.

[0248] <<<Application of Power Ramping>>> Regarding whether or not power ramping is applied to a PRACH of a PDCCH order, any of the following examples (1) to (3) may be applied.

[0249] (1) Power ramping may not be applied to the PDCCH-ordered PRACH (FIG. 30A), i.e., the UE may not increase the transmit power of the retransmitted PRACH from the transmit power of the initial PRACH.

[0250] (2) Power ramping may be applied to PDCCH-ordered PRACHs (see FIG. 30B ). That is, the UE may increase the transmission power of retransmitted PRACHs (second and subsequent PRACHs) from the transmission power of the initial PRACH. Each DCI may not have a field indicating whether power ramping is applied to each PRACH. In this case, whether power ramping is applied may be determined in advance, configured / indicated by the RRC / MAC CE, or transmitted / reported as UE capability information.

[0251] If the first DCI indicates a PDCCH order PRACH associated with SSB #1 and the second DCI indicates a PDCCH order PRACH associated with SSB #2, power ramping is not applied to the second PDCCH order PRACH (FIG. 30A) because the second PDCCH indicates a first transmission. That is, the UE does not need to apply power ramping to the PRACH when an SSB different from the SSB of the previous PDCCH order PRACH is indicated.

[0252] If the first DCI indicates a PDCCH order PRACH associated with SSB #1 and the second DCI indicates a PDCCH order PRACH associated with SSB #1, power ramping may be applied to the second PDCCH order PRACH (FIG. 30B) because the second PDCCH indicates a second transmission. That is, the UE may apply power ramping to the PRACH if the SSB indicated is the same as the SSB of the previous PDCCH order PRACH.

[0253] (3) Power ramping is applicable to PDCCH-ordered PRACHs. Each DCI may include a field indicating whether power ramping is applied to each PRACH.

[0254] <<Application of PL Offset and Power Ramping>> The PL offset may be applied only to the PDCCH-ordered PRACH, or to all PRACHs.

[0255] The PL offset may be applied to only contention-free random access (CFRA), only contention-based random access (CBRA), or both CFRA and CBRA.

[0256] If a PL offset is indicated / configured for the PRACH, the PL offset may be applied.

[0257] The UE may apply a PL offset to the PRACH regardless of whether or not power ramping is performed for the PRACH to be retransmitted, or may decide whether or not to apply a PL offset to the PRACH depending on whether or not power ramping is performed for the PRACH to be retransmitted. For example, one of the following options may be applied:

[0258] <<<Option 1-1>>> A PL offset is applied to all PRACH transmissions (with or without power ramping) (Figure 31A), which simplifies UE processing and eliminates concerns about exceeding the receive target power range.

[0259] <<<Option 1-2>>> The PL offset is applied only to the first PRACH transmission (without power ramping) (FIG. 31B). For subsequent PRACH transmissions (with power ramping), the conventional transmit power (without PL offset) is used. In this case, the first transmit power may be too low, so it is preferable to increase the transmit power from the second transmission onwards.

[0260] <<<Options 1-3>>> The PL offset may be applied only to the first PRACH transmission (without power ramping) (FIG. 31C), the second transmission is the same as the conventional first PRACH transmission (without power ramping), and the third transmission is the same as the conventional second PRACH transmission (with power ramping).

[0261] For PDCCH-ordered PRACH, the DCI may indicate for each PRACH transmission whether to apply a PL offset to the triggered PRACH.

[0262] According to the fourth embodiment, whether to apply a PL offset is determined depending on whether power ramping is performed or not, so that the UL transmission power can be determined appropriately.

[0263] <Contention-Based Random Access (CBRA)> In NR, contention-based random access (CBRA) includes a four-step CBRA procedure defined in Rel. 15 and a two-step CBRA procedure defined in Rel. 16. The former may be called a four-step RACH, and the latter may be called a two-step RACH.

[0264] <<Case when UE is in idle state>> Figure 32 is a diagram showing the flow of 4-step RACH when the UE is an idle UE (idle state UE). In 4-step RACH, the UE first transmits message 1 (random access preamble). The base station (gNB) returns message 2 to the UE, including a response (random access response (RAR))) in response to message 1.

[0265] Note that the DCI format that schedules the RAR has a CRC that is scrambled by the RNTI for random access (RA-RNTI).

[0266] Based on the UL grant indicated by the RAR, the UE sends a UE Identifier (ID) for contention resolution in message 3. The UE ID may be, for example, a Short (or SAE)-Temporary Mobile Subscriber Identity (S-TMSI).

[0267] Message 3 encapsulates a Common Control Channel Service Data Unit (CCCH SDU). The CCCH is a logical channel used when no RRC connection exists. The CCCH SDU may carry an RRC message (e.g., an RRC connection request) that includes the UE ID.

[0268] If the UE ID notified by message 3 does not collide with that of another UE, the base station returns message 4 including a contention resolution ID to the UE. Message 4 is scrambled by the TC-RNTI.

[0269] The UE sends a HARQ-ACK for message 4 on the PUCCH. The C-RNTI is set to the value of the TC-RNTI.

[0270] If message 4 is successfully decoded and the contention resolution ID of message 4 matches the CCCH SDU sent in message 3, then CBRA is determined to be successful.

[0271] <<Case when UE is connected>> Figure 33 is a diagram showing the flow of a four-step RACH when the UE is a connected UE (connected UE, UE in RRC_CONNECTED state). In the four-step RACH, the UE first transmits message 1 (random access preamble). The base station (gNB) replies to the UE with message 2 including a response (random access response (RAR))) in response to message 1.

[0272] Note that the DCI format that schedules the RAR has a CRC that is scrambled by the RNTI for random access (RA-RNTI).

[0273] Based on the UL grant indicated by the RAR, the UE sends a UE Identifier (ID) for contention resolution using message 3. The UE ID may be, for example, a Short (or SAE)-Temporary Mobile Subscriber Identity (S-TMSI). Message 3 may include a MAC CE for notifying the C-RNTI.

[0274] If the UE ID notified by message 3 does not collide with another UE, the base station returns message 4 containing a contention resolution ID to the UE. Message 4 contains an UL grant for the new transmission and is scrambled by the C-RNTI.

[0275] If the PDCCH in message 4 corresponds to the C-RNTI, the CBRA (collision resolution) is determined to be successful.

[0276] In the above CBRA procedure, it is not clear whether the PL offset is applied in the HARQ-ACK for message 1 (message A), message 3, and message 4, so it is preferable to clarify this.

[0277] <Fifth Embodiment> In Contention-based Random Access (CBRA), the UE may apply a PL offset to HARQ-ACK for message 1 / message 3 (message A) / message 4 (message B). Note that message 3 may refer to a PUSCH scheduled by an RAR UL grant (DCI). For example, when a two-step RACH is applied, message 3 in this embodiment may be replaced with message A, and message 4 may be replaced with message B.

[0278] The RAR UL grant may indicate whether to apply a PL offset to the PUSCH (message 3) scheduled by the RAR UL grant. For example, the RAR UL grant may have a field indicating the absolute value of the PL offset. Alternatively, the RAR UL grant may have a field of several bits to indicate whether to apply a PL offset or a PL offset value set by the RRC.

[0279] Whether to apply a PL offset to Message 3 may depend on whether a PL offset is applied to Message 1. That is, if the UE applies a PL offset to Message 1 (if instructed to do so), it may also apply a PL offset to Message 3.

[0280] Regarding the application of a PL offset to the HARQ-ACK for message 4, at least one of the following may be applied: (a) No PL offset is applied to the HARQ-ACK for message 4. That is, the UE may always transmit the HARQ-ACK for message 4 on the DL TRP. (b) Whether to apply a PL offset to the HARQ-ACK for message 4 is indicated by the scheduling DCI (the DCI in message 4 or the DCI scheduling message 4). (c) Whether to apply a PL offset to the HARQ-ACK for message 4 depends on whether a PL offset is applied to message 1 / message 3 (message A). That is, if the UE applies a PL offset to message 1 / message 3 (message A), it applies a PL offset to the HARQ-ACK for message 4.

[0281] According to the fifth embodiment, the UE can appropriately determine whether to apply a PL offset to the HARQ-ACK for message 3 (message A) / message 1 / message 4 (message B).

[0282] Problem 4: Conventionally, the spatial domain filter (transmit beam) of the PRACH is not specified. However, the associated DL RS is specified. This means that the PL-RS is used to calculate the PL of the TPC and to determine the transmit beam (assuming beam correspondence).

[0283] Regarding the SSB indicated by the PDCCH order, the existing specifications state the following:

[0284] If the CRC of DCI format 1_0 is scrambled by the C-RNTI and the frequency domain resource allocation field is all ones, then DCI format 1_0 is for a random access procedure initiated by a PDCCH order and all remaining fields are set as follows: SS / PBCH index - 6 bits. If the value of "Random Access Preamble Index" is not all zeros, this field indicates the SS / PBCH used to determine the RACH opportunity for PRACH transmission.

[0285] However, for FR1, there is no problem because the UE has only one spatial domain filter. However, in FR2, when transmitting PRACH to the UL TRP, it is preferable to further consider how the transmission beam to the UL TRP can be determined without beam correspondence.

[0286] <Application of PL Offset to PRACH by PDCCH Order> The UE may receive DCI instructing (triggering) PRACH transmission (e.g., a PDCCH order instructing PRACH transmission to a UL reception point) and may determine whether to apply a PL offset value to the PRACH transmit power calculation based on a specific field of the DCI. In the case of a PDCCH-ordered PRACH, at least one of the following options may be applied to a method of determining which PL offset value (PL value when PL-RS is not configured / PL offset value) is applied (or not applied) to the PRACH.

[0287] In this disclosure, PL-RS refers to the PL b,f,c In the present disclosure, the PL offset value and the PL value may be interchangeable. The DL / UL reception point and the DL / UL TRP may be interchangeable.

[0288] [Option 1] Option 1 describes the case where the Rel. 15 PDCCH order is used (the Rel. 18 PDCCH order is not configured).

[0289] The UE may use a PDCCH-ordered QCL source RS (i.e., a PDCCH QCL source) as a PRACH PL-RS. The PDCCH-ordered QCL source RS may be an SSB or a CSI-RS / TRS.

[0290] The UE may determine whether to transmit the PRACH to a DL TRP (DL transmission point) or a UL TRP (UL reception point) based on the QCL source RS in the PDCCH order (DCI).

[0291] The UE may apply the PL offset value to the transmit power calculation of the PRACH when transmitting the PRACH to a UL TRP (UL Reception Point) (i.e., when the QCL source RS of the PDCCH order is in the SSB / CSI-RS / TCI state of the UL TRP or is associated with a PL offset value > 0).

[0292] If the UE transmits the PRACH to a DL TRP (DL Transmission Point) (i.e., if the QCL source RS of the PDCCH order is in the SSB / CSI-RS / TCI state of the DL TRP or is associated with a PL offset value = 0), the PL offset value may not be applied to the PRACH transmit power calculation.

[0293] As shown in Figure 27A, a PL offset value for each SSB ID / TCI state ID may be defined in the specifications or may be configured / instructed to the UE. The UE may determine the PL offset value based on the definition / configuration / instruction. The SSB ID may be replaced with CSI-RS or DL-RS. The TCI state ID may be DL / joint TCI state.

[0294] [Option 2] When the PDCCH order of Rel. 18 is used (when the PDCCH order of Rel. 18 is configured / triggered), the 1-bit indication field of the PDCCH order may indicate either 2-1 or 2-2 below: 2-1 is used when the PRACH is transmitted to the TRP from which the PDCCH order was transmitted, and 2-2 may be used otherwise.

[0295] 2-1: The PL-RS of the PRACH is the QCL source RS of the PDCCH order (i.e., the QCL source of the PDCCH) (e.g., indicated by bit: 0). This means that the PRACH is transmitted in the DL TRP, and the PL offset value is not applied to the transmit power control of the PRACH.

[0296] 2-2: The PL-RS of the PRACH is the SSB indicated in the PDCCH order (e.g., indicated by bit: 1). This means that the PRACH is transmitted on the UL TRP, and the PL offset value corresponding to the PL-RS is applied to the PRACH transmission power calculation.

[0297] Variation: Bit: 1 may indicate that the PL-RS of the PRACH is a QCL source RS of the PDCCH order (i.e., a QCL source of the PDCCH). This also means that the PRACH is transmitted to the UL TRP, and the PL offset value may be applied to the transmit power control of the PRACH. In other words, both Bit: 0 and Bit: 1 mean that the PL-RS of the PRACH is a QCL RS of the PDCCH order, and the only difference between Bit: 0 and Bit: 1 may be whether the PL offset value is applied.

[0298] The bit indicating whether the PL-RS of the PRACH is a QCL source RS of a PDCCH order or whether the PL-RS of the PRACH is an SSB indicated in a PDCCH order and the bit indicating whether the PL offset value is applied to the PRACH transmission power calculation may be separate bits.

[0299] The UE may receive the setting of the PL value or PL offset value corresponding to the PL-RS through higher layer signaling / physical layer signaling, and apply the PL value or PL offset value corresponding to the PL-RS to the transmission power calculation of the PRACH.

[0300] Sixth Embodiment In this embodiment, the above-described process of <Application of PL offset to PRACH by PDCCH order> may be applied, and further, the following process may be applied.

[0301] If the PL offset is not indicated / applied to the PDCCH order PRACH (i.e., if the PRACH is transmitted in a DL TRP), the previous specifications (e.g., pre-Rel. 18) may be reused.

[0302] If a PL offset is indicated / applied to the PDCCH-ordered PRACH (i.e., if the PRACH is transmitted on a UL TRP), the transmit power of the PRACH is calculated by the PL and PL offset of the associated DL RS.

[0303] There is no problem with the transmit spatial domain filter of the PRACH in FR1. That is, the spatial domain filter is not specified. Alternatively, the UE can derive the spatial domain filter according to the associated DL RS. The terms transmit spatial domain filter and spatial domain filter may be interchangeable.

[0304] For FR2, the UE may receive a DCI containing an indication of the QCL source RS of the transmit spatial domain filter of the PRACH, which may be an SRS resource or another RS ​​(e.g., CSI-RS or SSB).

[0305] The above-mentioned SS / PBCH index (6 bits) may be used to indicate the associated DL RS, and another field (e.g., a 1-bit indication field) may be used to indicate whether a PL offset is applied.

[0306] Figure 34A shows an example of a new DCI field. Figure 34B shows an example of a transmit spatial domain filter (beam) corresponding to an SRS resource. The new DCI field indicates the QCL source RS (SRS resource) corresponding to the transmit beam of the PRACH. As shown in Figure 34A, for example, each 3-bit DCI field indicates eight SRS resources. As shown in Figure 34B, each SRS resource indicates a different transmit spatial domain filter (beam) (purpose: beam management (BM)). The UE may transmit (control transmission of) the PRACH using the same transmit spatial domain filter as the indicated SRS resource.

[0307] For example, if "010" (SRS resource #1) is indicated in the new DCI field, the UE transmits the PRACH using a beam (transmission spatial domain filter) corresponding to SRS resource #1.

[0308] Variation: A new DCI field may be applied to indicate the spatially related TCI state or QCL source RS of the PRACH. For example, the TCI state may be either the DL or UL TCI state (TCI state pool). The QCL source RS may be an SSB / CSI-RS / SRS. For example, if an SSB is indicated as the QCL source RS, the UE may assume that an SSB different from the SSB indicated in the SSB indicated for PL-RS determination field is indicated. The gNB can perform appropriate UL beam direction indication by setting the SSB closest to the UL TRP as the QCL source RS. Here, SSB #1 for PL-RS determination is received from the DL TRP, and SSB #2 for the QCL source RS is transmitted from another TRP in the direction of the UL TRP, so it may be assumed that SSB #1 and SSB #2 are necessarily different.

[0309] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information to the UE [from a Network (NW) (e.g., a Base Station (BS))] (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0310] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0311] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0312] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0313] In this patent, the UE can receive information as the following QCL rules from the NW: QCL Type A QCL Type B QCL Type C QCL Type D

[0314] The QCL resource RS for each QCL type in the present disclosure may be at least one of SSB, CSI-RS (with or without repetition), TRS, and DMRS of PDCCH / PDSCH.

[0315] In the present disclosure, information from the NW may be set / instructed as follows: UE common / UE dedicated; cell specific / cell common; per UE, per CC, per BWP, per band, per cell, per CG.

[0316] <<Notification of Information from UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0317] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0318] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0319] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0320] <<Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: - A higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured; - The specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters; - The specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS; - A specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported; - The application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions; - The RS measured in the present disclosure may be a QCL source RS in an active TCI state / indicated TCI state.

[0321] The specific UE capability may indicate at least one of the following ("supporting" may be read as "whether to support"): - Supporting the specific processing / operation / control / assumption / information; - Supporting Scenario 1 (UL dense deployment); - Supporting Scenario 2 (HetNet); - Supporting MAC CE-based PL offset update; - Supporting UL transmission (SRS / PUSCH / PUCCH / PRACH) to UL reception points; - Number of supported UL reception points (UL TRP) / DL transmission points (DL TRP).

[0322] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0323] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0324] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0325] (Supplementary Notes) The following inventions are supplementary notes regarding the first embodiment of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives a Medium Access Control Element (MAC CE) or Downlink Control Information (DCI) including information indicating a difference between a configured pathloss (PL) offset and a latest PL offset; and a control unit that updates a PL offset based on the information and determines a UL transmit power for a UL reception point using the updated PL offset. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the MAC CE or the DCI includes the information for one or all Uplink (UL) or joint Transmission Configuration Indication (TCI) states. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit updates the PL offset a specific period after transmission of a Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) for a Physical Downlink Shared Channel (PDSCH) that carries the MAC CE. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the MAC CE or the DCI includes a field indicating whether the difference value is positive or negative.

[0326] (Supplementary Notes) The following inventions are supplemented with respect to the second and third embodiments of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives a configuration of a PL offset associated with an uplink (UL) or a joint Transmission Configuration Indication (TCI) state; and a control unit that uses the same PL offset for all SRS resources in the same Sounding Reference Signal (SRS) resource set based on the configuration. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein, if a parameter indicating that a designated UL or joint TCI state applies to the SRS resource set is valid, the control unit uses the PL offset associated with the designated UL or joint TCI state for all SRS resources in the SRS resource set. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein, if a parameter indicating that a designated UL or joint TCI state applies to the SRS resource set is not valid, the control unit uses the PL offset associated with the UL or joint TCI state corresponding to the SRS resource with the lowest SRS resource ID in the SRS resource set. [Supplementary Note 4] The terminal according to any one of Supplementary Notes 1 to 3, wherein the controller applies a PL offset associated with an indicated TCI state in the list of UL or joint TCI states to a Physical Uplink Shared Channel (PUSCH) and a Physical Uplink Control Channel (PUCCH).

[0327] (Supplementary Notes) The following inventions are supplementary notes regarding the fourth and fifth embodiments of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiving unit that receives Downlink Control Information (DCI) that triggers transmission of a Physical Random Access Channel (PRACH); a transmitting unit that transmits the PRACH; and a control unit that applies the PL offset to the PRACH to be retransmitted when the PRACH is retransmitted. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit determines whether to apply a PL offset to the PRACH to be retransmitted depending on whether power ramping is performed for the PRACH to be retransmitted. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit applies the PL offset to at least one of HARQ-ACK for message 1, message 3, and message 4 in Contention-based Random Access (CBRA). [Supplementary Note 4] When the control unit applies a PL offset to message 1, the control unit applies a PL offset to message 3, and when the control unit applies a PL offset to message 1 or message 3, the control unit applies a PL offset to HARQ-ACK for message 4. The terminal according to any one of Supplementary Note 1 to Supplementary Note 3.

[0328] (Supplementary Note) The following inventions are supplementary notes regarding the sixth embodiment of <Application of a PL offset to a PRACH by a PDCCH order> of the present disclosure. [Supplementary Note 1] A terminal having: a receiving unit that receives Downlink Control Information (DCI) that instructs transmission of a PRACH; and a control unit that determines, based on a specific field of the DCI, whether to apply a PL offset value to transmit power calculation of the PRACH. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the control unit determines, based on a Quasi-Co-Location (QCL) source Reference Signal (RS) of the DCI, whether to transmit the PRACH to a Downlink (DL) transmission point or an Uplink (UL) reception point, and, when transmitting the PRACH to the UL reception point, determines to apply the PL offset value to transmit power calculation of the PRACH. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the receiver receives DCI including an indication of a QCL source RS of a transmission spatial domain filter of the PRACH. [Supplementary Note 4] The terminal according to any of Supplementary Notes 1 to 3, wherein the QCL source RS is an SRS resource, and the controller controls transmission of the PRACH using the same transmission spatial domain filter as the SRS resource.

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

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

[0331] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0332] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (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.

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

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

[0335] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

[0338] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

[0341] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

[0344] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

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

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

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

[0349] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

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

[0351] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

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

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

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

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

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

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

[0358] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

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

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

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

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

[0363] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0365] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

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

[0374] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0375] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0376] The transceiver 120 may transmit a Medium Access Control Element (MAC CE) or Downlink Control Information (DCI) including information indicating the difference between the configured pathloss (PL) offset and the latest PL offset.

[0377] If the PL offset is updated based on the information, the control unit 110 may assume that the UL transmit power for the UL reception point is determined using the updated PL offset. If the base station 10 is a UL reception point, the transceiver unit 120 may receive the UL signal transmitted using the updated PL offset.

[0378] The transceiver 120 may transmit the configuration of the PL offset associated with the Uplink (UL) or joint Transmission Configuration Indication (TCI) state.

[0379] Based on the setting, the control unit 110 may assume that the same PL offset is used for all SRS resources in the same SRS resource set. When the base station 10 is an UL reception point, the transceiver unit 120 may receive an UL signal (SRS) transmitted using a PL offset.

[0380] The transceiver 120 may transmit Downlink Control Information (DCI) that triggers transmission of a Physical Random Access Channel (PRACH).

[0381] When the PRACH is retransmitted, the control unit 110 may assume that the PL offset is applied to the retransmitted PRACH. If the base station 10 is an UL reception point, the transceiver unit 120 may receive the transmitted PRACH using the updated PL offset.

[0382] The transceiver 120 may transmit Downlink Control Information (DCI) instructing transmission of the PRACH.

[0383] The control unit 110 may determine whether to apply a PL offset value to the PRACH transmit power calculation based on a specific field of the DCI. If the base station 10 is an UL receiving point, the transceiver unit 120 may receive the PRACH transmitted using the updated PL offset.

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

[0385] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0386] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

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

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

[0390] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0392] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

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

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

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

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

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

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

[0400] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

[0401] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0402] The transmitting / receiving unit 220 may perform at least one of the processes of the transmitting unit and receiving unit of the terminal in the above appendix.

[0403] The control unit 210 may perform at least one of the processes of the control unit of the terminal in the above appendix.

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

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

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

[0407] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0408] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0409] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

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

[0411] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0412] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

[0415] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

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

[0418] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

[0419] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

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

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

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

[0424] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

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

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

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

[0428] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

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

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

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

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

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

[0435] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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

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

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

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

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

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

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

[0444] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

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

[0446] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

[0448] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

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

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

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

[0453] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0454] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0455] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0456] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0457] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0458] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0459] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

[0460] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0461] 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 partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0462] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

[0465] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc.

[0466] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0467] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0468] 39 is a diagram showing an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0469] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by a user.

[0470] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0471] The signals from the various sensors 50-58 include a current signal from a current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheels 46 / rear wheels 47 obtained by a rotation speed sensor 51, an air pressure signal of the front wheels 46 / rear wheels 47 obtained by an air pressure sensor 52, a vehicle speed signal obtained by a vehicle speed sensor 53, an acceleration signal obtained by an acceleration sensor 54, a depression amount signal of the accelerator pedal 43 obtained by an accelerator pedal sensor 55, a depression amount signal of the brake pedal 44 obtained by a brake pedal sensor 56, an operation signal of the shift lever 45 obtained by a shift lever sensor 57, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 58.

[0472] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0473] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0474] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0475] The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0476] The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0477] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

[0478] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on an information service unit 59 provided in the vehicle. The information service unit 59 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 60 (or data / information decoded from the PDSCH)).

[0479] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 may control the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, various sensors 50-58, and the like provided in the vehicle 40.

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

[0481] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

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

[0483] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0484] Each aspect / embodiment described in the present disclosure may be a technology other than 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 (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0489] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0490] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0491] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

[0498] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0499] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0500] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0501] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0502] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having: a receiving unit that receives Downlink Control Information (DCI) that instructs transmission of a PRACH; and a control unit that determines whether to apply a PL offset value to calculation of the transmission power of the PRACH based on a specific field of the DCI.

2. The terminal of claim 1, wherein the control unit determines whether to transmit the PRACH to a Downlink (DL) transmission point or an Uplink (UL) reception point based on a Quasi-Co-Location (QCL) source Reference Signal (RS) of the DCI, and when transmitting the PRACH to the UL reception point, determines to apply the PL offset value to calculation of the transmission power of the PRACH.

3. The terminal according to claim 1, wherein the receiver receives DCI including an indication of a QCL source RS of a transmit spatial domain filter for the PRACH.

4. The terminal according to claim 3, wherein the QCL source RS is an SRS resource, and the control unit controls the transmission of the PRACH using the same transmission spatial domain filter as the SRS resource.

5. A wireless communication method for a terminal, comprising: a step of receiving Downlink Control Information (DCI) instructing transmission of a PRACH; and a step of determining whether to apply a PL offset value to calculation of the transmission power of the PRACH based on a specific field of the DCI.

6. A base station having: a transmitting unit that transmits Downlink Control Information (DCI) that instructs the transmission of a PRACH; and a control unit that assumes that whether to apply a PL offset value to the transmission power calculation of the PRACH is determined based on a specific field of the DCI.

Images