Terminal, radio communication method, and base station

Abstract

To appropriately control UL transmission / DL reception even when DL sTRP / UL mTRP is applied.SOLUTION: A terminal has: a receiving section that receives settings related to path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state; and a control section that determines from which of transmission and reception points (TRP) a synchronization signal block (SSB) is received on the basis of the settings.SELECTED DRAWING: Figure 13

Description

[Technical Field]

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) has been specified 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) are also being considered. [Prior art documents] [Non-patent literature]

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

[0005] In future wireless communication systems, it is being considered that a Downlink single transmission / reception point (DL sTRP) / Uplink multi transmission / reception point (UL mTRP) scenario will be applied.

[0006] However, the control of UL transmission / DL reception when DL sTRP / UL mTRP is applied has not been fully considered. Therefore, there is a risk that the UE may not be able to appropriately control UL transmission / DL reception when DL sTRP / UL mTRP is applied.

[0007] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately control UL transmission / DL reception even when DL sTRP / UL mTRP is applied. [Means for solving the problem]

[0008] A terminal according to one embodiment of the present disclosure is characterized by having a receiving unit that receives a setting regarding a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state, and a control unit that determines from which transmission / reception point (TRP) to receive a synchronization signal block (SSB) based on the setting. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, UL transmission / DL reception can be appropriately controlled. [Brief explanation of the drawings]

[0010] [Figure 1] Fig. 1A is a diagram showing an example of a typical arrangement of transmission and reception points, and Fig. 1B is a diagram showing an example of a high-density UL arrangement. [Figure 2]FIG. 2 is a diagram illustrating an example of DL / UL coverage of a Heterogeneous Network (HetNet). [Figure 3] FIG. 3 is a diagram showing an example of setting a TAG for a cell. [Figure 4] 4A and 4B are diagrams illustrating an example of a MAC CE for a timing advance command. [Figure 5] 5A and 5B are diagrams showing examples of associations between RS indexes and PL values, respectively, and FIG. 5B is a diagram showing examples of associations between RS indexes and delta PL values. [Figure 6] FIG. 6 shows an example of Option 1 in a high density UL deployment. [Figure 7] FIG. 7 shows an example of Option 2 in a high density UL deployment. [Figure 8] FIG. 8 is a conceptual diagram illustrating an example of an asymmetric DL sTRP / UL mTRP deployment scenario. [Figure 9] FIG. 9 is a conceptual diagram showing an example of SRS transmission. [Figure 10] FIG. 10 is a diagram illustrating an example of SRS settings. [Figure 11] 11A and 11B are diagrams showing an example of a TPC command (DCI) field. [Figure 12] FIG. 12 is a diagram illustrating an example of a method for determining the bit size of the PRACH-related indicator field. [Figure 13] 13A and 13B are diagrams showing an example of SSB reception from a UL TRP. [Figure 14] FIG. 14 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] (Scenario 1: High-density UL deployment (TRP with only UL)) In Rel. 15 NR, the coverage (reaching distance) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is uneven. The coverage of PUSCH is limited, especially at higher 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.

[0012] In order to expand UL coverage, the installation of UL receiving points in addition to general transmitting and receiving points is being considered. Here, we will explain an example of the layout of general transmitting and receiving points and an example of a layout with UL receiving points (high-density UL layout).

[0013] Figure 1A shows an example of a typical arrangement of transmission / reception points. In Figure 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.

[0014] Figure 1B shows an example of a high-density UL deployment. To expand UL coverage, it is being considered to provide UL reception points as shown in Figure 1B in addition to the TRPs (DL transmission points) shown in Figure 1A. In Figure 1B, a UE receives DL signals from a DL transmission point (TRP / central TRP / DL 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 can also perform UL transmission to a DL transmission point.

[0015] By using a high-density UL deployment like that shown in Figure 1B, both coverage and UL data rates can be improved by reducing path loss, improving UL signaling quality, and obtaining higher coding rates compared to the general deployment like that shown in Figure 1A. Also, since the UL receiving point mainly performs reception, it requires fewer functions (e.g., power amplifiers) and is therefore less costly than the transmitting / receiving points corresponding to typical small cells, making deployment management much easier.

[0016] (Scenario 2: Decoupling of DL TRP and UL TRP in Heterogeneous Networks) In this disclosure, a Heterogeneous Network (HetNet) using a macro Base Station (BS) (DL TRP) and a micro BS (UL TRP) may be applied (Figure 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, DL coverage is determined by RSRP, and UL coverage is determined by path loss (PL).

[0017] In the example shown in Figure 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 signals from the macro BS and transmit UL signals to the micro BS. However, the UE may transmit some reference signals / channels (e.g., an SRS with an antenna switching (AS) usage, used for DL ​​CSI acquisition) 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 used by the base station (macro BS) to measure DL CSI (e.g., to 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 PUSCH precoder / beam determination.

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

[0019] (Timing Advance) Timing Advance (TA) is used for UL timing adjustment. In the existing specification (Rel. 17), the UL frame number i for transmission from the UE is a specific time (e.g., T TA ) before

[0020] The specific time is, for example, T TA =(N TA +N TA,offset +N common TA,adj +N UE TA,adj )T C N common TA,adj and N UE TA,adj may be 0 regardless of the examples of this disclosure when used in an NTN (non-terrestrial network).

[0021] where N TA is the timing advance between DL and UL, TA,offset defines a fixed offset used in calculating the timing advance, N common TA,adj is the network-controlled timing correction, N UE TA,adj is the UE-derived timing correction, T C may denote the Basic time unit for NR, respectively.

[0022] For example, in the random access preamble transmission and the message A PUSCH transmission, N TA is 0 and N TA,offset applies.

[0023] (Timing Advance Group) When multiple TRPs are used, the distances between the UE and each TRP may be different. The multiple TRPs may be included in the same cell (e.g., serving cell). Alternatively, one TRP may correspond to the serving cell and the other TRPs may correspond to non-serving cells. The multiple TRPs may include DL transmission points and UL reception points. In this case, it is assumed that the distances between each TRP and the UE may be different.

[0024] In existing systems, the transmission timing of an uplink (UL) channel and / or an UL signal (UL channel / signal) is adjusted by a timing advance (TA). The reception timing of an UL channel / signal from different user terminals (UE) is adjusted by a radio base station (TRP: Transmission and Reception Point, also known as gNodeB (gNB)).

[0025] The UE may control the timing of UL transmission by applying timing advance (multiple timing advances) for each pre-configured timing advance group (TAG).

[0026] When multiple timing advances are applied, Timing Advance Groups (TAGs) classified by transmission timing are supported. The UE may control the UL transmission timing for each TAG assuming that the same TA offset (or TA value) is applied to each TAG. In other words, the TA offset may be set independently for each TAG.

[0027] When multiple timing advance is applied, the UE independently adjusts the transmission timing of cells belonging to each TAG, allowing the radio base station to synchronize the reception timing of uplink signals from the UE even when multiple cells are used.

[0028] TAGs (e.g., serving cells belonging to the same TAG) may be configured by higher layer parameters. The same timing advance value may be applied to serving cells (e.g., serving cells for which UL is configured) belonging to the same TAG. A timing advance group including an SpCell of a MAC entity may be called a Primary Timing Advance Group (PTAG), and other TAGs may be called Secondary Timing Advance Groups (STAGs). The maximum number of TAGs may be X (e.g., X=4) per cell group (e.g., MCG / SCG).

[0029] Existing systems (e.g., Rel. 16 NR) support the configuration of up to four TAGs per cell group (e.g., MCG / SCG) (see Figure 3). Figure 3 shows a case where three TAGs are configured for a cell group including SpCell and SCells #1 to #4. Here, the case is shown where SpCell and SCell #1 belong to the first TAG (PTAG or TAG #0), SCell #2 and SCell #3 belong to the second TAG (TAG #1), and SCell #4 belongs to the third TAG (TAG #2).

[0030] A timing advance command (TA command) may be notified to the UE using a MAC control element (e.g., MAC CE). The TA command indicates a transmission timing value of an uplink channel and is included in the MAC control element. The TA command (TAC) is signaled from the radio base station to the UE at the MAC layer. The UE controls a predetermined timer (e.g., a TA timer) based on the reception of the TA command.

[0031] The MAC CE for the timing advance command may include a field for a timing advance group index (e.g., TAG ID) and a field for the timing advance command (see FIG. 4A). The MAC CE may be configured by one octet (=8 bits).

[0032] The TAG ID field may consist of, for example, 2 bits. The TAG ID field may be used to indicate the TAG ID of the addressed TAG. The Timing Advance Command field (TAC field) may consist of, for example, 6 bits. The TAC field contains an index value T that is used to control the amount / value (relative amount / relative value) of timing adjustment that the MAC entity must apply. A (0, 1, 2...63). The MAC CE for the timing advance command shown in Figure 4A may be called a TAC MAC CE.

[0033] FIG. 4B is a diagram showing another example of a MAC CE for a timing advance command. The MAC CE shown in FIG. 4B may be called an absolute TAC MAC CE. The MAC CE may be configured with two octets (=16 bits). Specifically, the MAC CE may include a field for reserved bits (R-bit field) and a field for a timing advance command (TAC field). The R-bit field (R=0) may be configured with, for example, 4 bits. The TAC field may be configured with, for example, 12 bits across two octets. The TAC field in FIG. 4B may indicate an index value used to control the amount / value (absolute amount / value) of the actual TA that the MAC entity must apply, as in FIG. 4A. Furthermore, the absolute TAC MAC CE may not include the TAG ID field shown in FIG. 4A.

[0034] The MAC CE shown in Fig. 4A may be used after initial access is established. On the other hand, the MAC CE shown in Fig. 4B is used only during initial access and may include an RAR, etc. Each field included in the MAC CE for the timing advance command described above may be called a TA-related field. Among them, the TAC field shown in Fig. 4A may be called a TA adjustment field / field for instructing TA adjustment / field related to TA adjustment, and the TAC field shown in Fig. 4B may be called an absolute TAC field / field for instructing absolute TAC.

[0035] The parameters corresponding to each TAG ID may be set by a higher layer parameter. For example, a parameter such as a time alignment timer (e.g., timeAlignmentTimer) corresponding to each TAG ID may be set. Alternatively, the TAG ID for each serving cell may be set by a higher layer parameter (e.g., tag-ID included in ServingCellConfig). Note that after being set by the higher layer parameter, the TAG ID / parameter may be updated by the MAC CE.

[0036] A time alignment timer may be maintained for UL time alignment. In Rel. 17, a time alignment timer may be configured / associated per TAG. When the UE receives a MAC CE for a timing advance command (e.g., TAC MAC CE), it starts or restarts the time alignment timer associated with the indicated timing advance group (e.g., TAG), respectively.

[0037] The MAC entity receives the TAC MAC CE and determines whether the TAG is equal to or smaller than the predetermined value (N TA ) is maintained, apply a timing advance command for the indicated TAG or start or restart the time alignment timer associated with the indicated TAG. TA) may be the timing advance between DL and UL.

[0038] The behavior when the time alignment timer expires may be defined separately for PTAG and STAG. Note that the timing advance group (TAG) that includes the SpCell of the MAC entity may be called the primary timing advance group (PTAG), and the other TAGs may be called secondary timing advance groups (STAG).

[0039] For example, in Rel. 17, it is supported that when the timing advance timer corresponding to a PTAG expires, a specified PTAG operation is applied, and when the timing advance timer corresponding to a STAG expires, a specified STAG operation is applied.

[0040] For example, when the time alignment timer expires, the following operations (for example, a predetermined PTAG operation / a predetermined STAG operation) may be performed.

[0041] [Prescribed PTAG Action] If a time alignment timer is associated with the PTAG, ·Flush all HARQ buffers in all serving cells. If configured, notify RRC to release PUCCH for all serving cells. If configured, notify RRC to release SRS. Clear all configured DL allocations and configured UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. - Complete all time alignment timers while running. All TAG N TA Maintain.

[0042] [Prescribed STAG Action] If a time alignment timer is associated with a STAG, for all serving cells belonging to that STAG: Flush all HARQ buffers. If configured, notify RRC to release PUCCH. If configured, notify RRC to release SRS. Clear all configured DL and UL allocations. Clear PUSCH resources for semi-persistent CSI reporting. N of the TAG TA Maintain.

[0043] (PRACH related indicators in Rel.18) The PRACH-related indicator is configured with a bit of 0 or 1. In the present disclosure, the PRACH-related indicator, the PRACH-related indicator field, etc. may be read interchangeably.

[0044] The PRACH-related indicator is 1 bit if the following conditions are met: If the UE is provided with certain parameters (tag-Id2 and SSB-MTC-AdditionalPCI), If the UE is not provided with a coresetPoolIndex or is provided with a coresetPoolIndex (value = 0) for the first CORESET, If coresetPoolIndex (value = 1) for the second CORESET is provided.

[0045] If the UE is provided with a specific parameter SSB-MTC-AdditionalPCI, the corresponding PRACH related indicator field (hereinafter simply referred to as the field) consisting of one bit indicates the PCI associated with the PRACH transmission.

[0046] Specifically, the index 0 of this field is mapped (associated) with the PCI of the serving cell, and the index 1 of this field is mapped with the PCI of the active additional cell.

[0047] On the other hand, if the UE is not provided with the specific parameter SSB-MTC-AdditionalPCI, this field indicates the PL-RS (Path Loss Reference Signal) for PRACH transmission.

[0048] Specifically, index 0 of this field is mapped to the DL RS where the PDCCH-ordered DM-RS is quasi-collocated, and index 1 of this field is mapped to the SS / PBCH indicated by the SS / PBCH index field in this DCI format (1_0).

[0049] Otherwise, if none of the above conditions are met, the PRACH-related indicator is a 0 bit.

[0050] (Reference signal power for PRACH transmission in Rel.18) If at least one of the following conditions is met, the UE is provided with a parameter referenceSignalPower related to the reference signal power by a corresponding parameter ss-PBCH-BlockPower:

[0051] If the PRACH transmission from the UE is a response to the detection of a PDCCH order by the UE that triggers a contention-free random access procedure, and the DM-RS of the PDCCH order depends on a DL RS that is QCL'd, then at least one of the following conditions is met: If there is no PRACH-related indicator in the PDCCH order, If the cell indicator field is not present in the PDCCH order or the value of this field is 0, If the UE is not provided with SSB-MTC-AdditionalPCI and the value of the PRACH-related indicator field of the PDCCH order is 0, If the PRACH related indicator field in the PDCCH order indicates the physical cell ID (physCellId) related to the cell receiving the PDCCH order or depending on the indicated SS / PBCH block, If the PRACH transmission is sent in a non-serving cell indicated by the cell indicator field in the PDCCH order, If the UE is not provided with SSB-MTC-AdditionalPCI and the value of the PRACH-related indicator field in the PDCCH order is 1, ·If the PRACH related indicator field in the PDCCH order indicates a physical cell ID (physCellId) that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

[0052] (Path loss (PL) reception) 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)).

[0053] The UE receives the path loss (PL b,f,c (q d ), P.L. b,f,c )(index q d The UL signal transmit power (e.g., transmit power of PUSCH / PUCCH / SRS / PRACH) for a reception point that does not transmit downlink data may be calculated using the active UL BWP b of carrier f of serving cell c using the path loss for b.

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

[0055] [Option 2] The network may notify (transmit) a relative path loss (Delta PL) 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.

[0056] The PL value / delta PL value in options 1 and 2 is q d The PL value / delta PL value may be signaled / 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 signaled by DL signaling. The PL value / delta PL value may be interpreted as a PL parameter / delta PL parameter.

[0057] FIG. 5A is a diagram showing an example of the association between RS indexes and PL values. FIG. 5B 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. 5A and 5B. 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.

[0058] Figure 6 shows an example of Option 1 in a high-density UL deployment. The UL reception point receives / measures the UL signal. If the DL transmission point (macro TRP / gNB) knows the transmit 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.

[0059] Figure 7 shows an example of Option 2 in a dense UL 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 the difference (relative PL / delta PL). The relative PL / delta PL may also be referred to as a PL offset.

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

[0061] (Unified / Common TCI Framework) The unified TCI framework allows multiple types of channels / RSs (UL / DL) to be controlled by a common framework. The unified TCI framework does not specify the TCI state or spatial relationship for each channel as in Rel. 15. Instead, it specifies a common beam (common TCI state) and applies it to all UL and DL channels. Alternatively, a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0062] One common beam for both DL and UL, or one common beam for DL ​​and one common beam for UL (two common beams overall) are considered.

[0063] The UE may assume the same TCI state for UL and DL (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set). The UE may assume different TCI states for UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0064] The default beams for UL and DL may be aligned via MAC CE based beam management (MAC CE level beam direction). The default TCI state of the PDSCH may be updated to align with the default UL beam (spatial relationship).

[0065] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, set) for both UL and DL. X (>1) TCI states may be activated by the MAC CE. The UL / DL DCI may select one from the X active TCI states. The selected TCI state may apply to both UL and DL channels / RS.

[0066] The TCI pool (set) may be multiple TCI states configured by RRC parameters, or multiple TCI states (active TCI states, active TCI pools, sets) activated by the MAC CE among the multiple TCI states configured by RRC parameters. Each TCI state may be a QCL type A / D RS. SSB, CSI-RS, or SRS may be configured as the QCL type A / D RS.

[0067] The number of TCI states corresponding to each of one or more TRPs may be specified. For example, the number N (≧1) of TCI states applied to UL channels / RSs (UL TCI states) and the number M (≧1) of TCI states applied to DL channels / RSs (DL TCI states) may be specified. At least one of N and M may be notified / configured / instructed to the UE via higher layer signaling / physical layer signaling.

[0068] RRC parameters (information elements) configure multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the configured multiple TCI states. DCI may indicate one of the activated multiple TCI states. DCI may be UL / DL DCI. The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both UL TCI and DL TCI.

[0069] In this example, a point may be one TCI state that applies to both the UL and DL, or two TCI states that apply to the UL and DL, respectively.

[0070] At least one of the multiple TCI states configured by the RRC parameters and the multiple TCI states activated by the MAC CE may be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). The multiple TCI states activated by the MAC CE may be referred to as an active TCI pool (active common TCI pool).

[0071] In the present disclosure, higher layer parameters (RRC parameters) for setting multiple TCI states may be referred to as configuration information for setting multiple TCI states, or simply as "configuration information." Also, in the present disclosure, being instructed to set one of multiple TCI states using DCI may mean receiving indication information instructing one of the multiple TCI states included in DCI, or simply receiving "instruction information."

[0072] The RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for UL and DL may be configured / activated.

[0073] The DL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) DL channels / RSs. The DL channels may be PDCCH / PDSCH / CSI-RS. The UE may determine the TCI state of each DL channel / RS using the TCI state behavior (TCI framework) of Rel. 16. The UL DCI or a new DCI format may select (indicate) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) UL channels / RSs. The UL channels may be PUSCH / SRS / PUCCH. In this way, different DCIs may indicate the UL TCI and the DL DCI separately.

[0074] From Rel.17 NR onwards, it is assumed that the MAC CE / DCI will support beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and from Rel.18 NR onwards, it is assumed that the MAC CE / DCI will support indicating a serving cell change to a cell with a different PCI.

[0075] [SRS to which the TCI status indicated in Rel. 17 applies] The indicated TCI state by the MAC CE / DCI may be applied to an SRS that meets the following: - When the SRS resource set for A-SRS for beam management and A / SP / P-SRS for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state applies. For other SRS, the configured TCI state in the SRS resource set applies.

[0076] [SRS to which the TCI status specified in Rel. 18 applies] When single DCI multi-TRP is applied, the indicated TCI state may be applied to an SRS that satisfies the following: Note that applyIndicatedTCIState={1st, 2nd, both} in the following description is a parameter indicating that the first TCI state, the second TCI state, or both the first TCI state and the second TCI state are applied. When the SRS resource set for A-SRS, whose purpose is beam management, and A / SP / P-SRS, whose purpose is codebook (CB) / non-codebook (NCB) / antenna switching, is configured to follow the unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state applies. For other SRSs, the configured TCI state in that SRS resource set applies.

[0077] In the present disclosure, the indicated TCI state, the unified TCI state, the TCI state applied to channels / signals configured to follow the unified TCI state, the TCI state applied to the UE-dedicated PDSCH and the CORESET / PDCCH associated with the USS, and the TCI state applied to the PUCCH and PUSCH may be read as interchangeable.

[0078] (SRS transmission power control) The power control adjustment state (closed-loop state) index l is used to calculate the SRS transmission power (P SRS、b,f,c (i,q s ,l)) is P CMAX,f,c (i), P O_SRS,b,f,c (q s ), M SRS,b,f,c (i), α SRS,b,f,c (q s ), P.L. b,f,c (q d ), h b,f,c Based on (i,l), it is given by the following formula:

[0079] TIFF2025155695000002.tif31167

[0080] Furthermore, the SRS transmission opportunity i is a period during which the SRS is transmitted, and may be composed of, for example, one or more symbols, one or more slots, or the like.

[0081] where P CMAX,f,c (i) is, for example, the UE maximum output power for carrier f of serving cell c at SRS transmission opportunity i. P O_SRS,b,f,c (q s ) is the active UL BWP b of carrier f in serving cell c and SRS resource set q s (provided by SRS-ResourceSet and SRS-ResourceSetId), and a parameter related to the target received power provided by p0 for (for example, a parameter related to the transmit power offset, also referred to as the transmit power offset P0 or the target received power parameter, etc.).

[0082] M SRS,b,f,c (i) is the SRS bandwidth in number of resource blocks for SRS transmission opportunity i on active UL BWP b of carrier f with serving cell c and subcarrier spacing μ;

[0083] α SRS,b,f,c (q s ) is the active UL BWP b of serving cell c and carrier f with subcarrier spacing μ and SRS resource set q s and α (e.g., alpha) for , where α (e.g., alpha) may be defined as a path loss compensation factor for UL power control.

[0084] PL b,f,c (q d ) is the active DL BWP of serving cell c and SRS resource set q. s and, for RS resource index q d is the DL path loss estimate [dB] (path loss estimate [dB], path loss compensation) calculated by the UE using the RS resource index q d is the SRS resource set q sand a pathloss reference RS (pathloss reference RS, pathloss(PL)-RS, DL-RS for pathloss measurement, e.g., provided by pathlossReferenceRS) associated with the SS / PBCH block index (e.g., ssb-Index) or CSI-RS resource index (e.g., csi-RS-Index).

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

[0086] h b,f,c (i,l) is the SRS power control adjustment state for the active UL BWP of carrier f of serving cell c at SRS transmission opportunity i. If the SRS power control adjustment state configuration (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, the current PUSCH power control adjustment state f b,f,c On the other hand, if the setting of the SRS power control adjustment state indicates independent power control adjustment states for SRS transmission and PUSCH transmission, the SRS power control adjustment state h b,f,c (i) is δ SRS,b,f,c It may also be based on (m).

[0087] If TPC accumulation is enabled, h b,f,c (i) is δ SRS,b,f,c It may be based on the cumulative value of (m).

[0088] If TPC accumulation is disabled, h b,f,c (i) is δ SRS,b,f,c (i) (absolute value) may also be used.

[0089] where δ SRS,b,f,c(m) may be a TPC command value that is jointly coded with other TPC commands in a PDCCH having DCI (e.g., DCI format 2_3). m=0 C(Si)-1 δ SRS,b,f,c (m) is the K of SRS transmission opportunity i-i0 on the active UL BWP b of carrier f with serving cell c and subcarrier spacing μ. SRS (i-i0)-1 symbols ago and K SRS (i) The cardinality C(S i ) a set S of TPC command values i where i0 is the sum of the TPC commands in K for SRS transmission opportunity i-i0. SRS (i-i0)-1 symbols ago is K for SRS transmission opportunity i. SRS (i) It may be the smallest positive integer that is earlier than the symbol before.

[0090] If the SRS transmission is aperiodic, K SRS (i) may be the number of symbols in the active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH that triggers the SRS transmission and before the first symbol of the SRS transmission. If the SRS transmission is semi-persistent or periodic, K SRS (i) is the number of symbols per slot, N, in the active UL BWP b of carrier f of serving cell c. symb slot and the minimum value of the value provided by k2 in the PUSCH common configuration information (PUSCH-ConfigCommon). SRS,min It may also be the number of symbols.

[0091] (DCI format 2_3) DCI format 2_3 is used to transmit a TPC command group for SRS transmission by one or more UEs. An SRS request may also be transmitted along with the TPC command.

[0092] The following information is transmitted by DCI format 2_3 CRC-scrambled by TPC-SRS-RNTI. Block number 1, block number 2, ..., block number B. The starting position of the block is determined by the parameter startingBitOfFormat2-3 or startingBitOfFormat2-3SUL-v1530 provided by the higher layer to the UE that configures the block.

[0093] If the UE is configured with the higher layer parameter srs-TPC-PDCCH-Group=typeA for a UL with no PUCCH and no PUSCH or for a UL where SRS power control is not associated with PUSCH power control, then one block is configured in the UE by higher layers, and the following fields are defined in that block: · SRS Request: 0 or 2 bits. If this field is present, it is interpreted according to a specific table. TPC command number 1, TPC command number 2, ..., TPC command number N. Each TPC command applies to a respective UL carrier, provided by the higher layer parameter cc-IndexInOneCC-Set.

[0094] If the UE is configured with higher layer parameter srs-TPC-PDCCH-Group=typeB for an UL without PUCCH and PUSCH or for an UL where SRS power control is not associated with PUSCH power control, the higher layers configure the UE with one or more blocks, where each block applies to an UL carrier, and the following fields are defined for each block: · SRS Request: 0 or 2 bits. If this field is present, it is interpreted according to a specific table. TPC command: 2 bits.

[0095] The number of information bits of format 2_3 must be less than or equal to the payload size of format 1_0 monitored in the common search space in the same serving cell. If the number of information bits of format 2_3 is less than the payload size of format 1_0 monitored in the common search space in the same serving cell, zeros must be added to format 2_3 until the payload size is equal to the payload size of format 1_0 monitored in the common search space in the same serving cell.

[0096] (SRS switching) DCI format 2_3 is applied to uplink carriers of a serving cell for which the UE is not configured for PUSCH / PUCCH transmission, or for which srs-PowerControlAdjustmentStates indicates separate power control adjustment states between SRS transmission and PUSCH transmission. A UE for which the parameter carrierSwitching is configured by higher layers is provided with the following (1) to (7).

[0097] (1) TPC-SRS-RNTI for DCI format 2_3 with parameter tpc-SRS-RNTI.

[0098] (2) The index of the serving cell from which the UE will discontinue transmission in order to transmit SRS on one or more other serving cells, via the parameter srs-SwitchFromServCellIndex.

[0099] (3) Indication of the uplink carrier from which the UE should suspend transmission in order to transmit SRS in one or more other serving cells, via the parameter srs-SwitchFromCarrier.

[0100] (4) DCI format 2_3 field setting type according to Type A or Type B. In the case of Type A, the index of the serving cell set is provided by cc-SetIndex, the index of the serving cell in the serving cell set is provided by cc-IndexInOneCC-Set, and the DCI format 2_3 field includes a TPC command for each serving cell from the serving cell set and may also include an SRS request for SRS transmission on the serving cell set. In the case of Type B, the DCI format 2_3 field includes a TPC command for the serving cell index and may include an SRS request for SRS transmission on the serving cell.

[0101] (5) An indication to the serving cell whether the field in DCI format 2_3 contains an SRS request in fieldTypeFormat2-3. A value of 0 / 1 in this indication indicates the absence / presence of an SRS request. The mapping between the 2-bit SRS request and the SRS resource set is as specified in the specification.

[0102] (6) startingBitOfFormat2-3 indicates the index for the position in DCI format 2_3 of the first bit of the field for the non-supplementary uplink carrier of the serving cell.

[0103] (7) startingBitOfFormat2-3 Index for the position in DCI format 2_3 of the first bit of the field for the supplementary uplink carrier of the serving cell according to SUL-v1530.

[0104] In the existing specifications (up to Rel. 18), startingBitOfFormat2-3 / startingBitOfFormat2-3SUL-v1530 is specified as an integer between 1 and 31.

[0105] (Two Closed Loop Power Control (CL-PC) Adjustment States for PUSCH) The higher layer parameters related to PUSCH power control (PUSCH-PowerControl) include twoPUSCH-PC-AdjustmentStates and the size of sri-PUSCH-PowerControlId. The higher layer parameters related to PUSCH power control using SRI (SRI-PUSCH-PowerCotrol) include sri-PUSCH-PowerControlId and sri-PUSCH-ClosedLoopIndex. When twoPUSCH-PC-AdjustmentStates is configured, the UE may configure sri-PUSCH-ClosedLoopIndex with l={0,1}.

[0106] sri-PUSCH-ClosedLoopIndex applies only to PUSCH. The UE determines whether the closedLoopIndex of the scheduled PUSCH is 0 or 1 based on the SRI. However, the closedLoopIndex for the SRS of the indicated CB / NCB follows the setting of srs-PowerControlAdjustmentStates.

[0107] When two SRS resource sets with usage = CB / NCB are configured, each SRS resource set corresponds to l={0,1}, i.e., one SRS resource set corresponds to l=0 and the other SRS resource set corresponds to l=1.

[0108] (CL-PC adjustment status for SRS) The CL-PC adjustment state for the SRS is defined according to at least one of the following cases 1 to 3. <Case 1> If srs-PowerControlAdjustmentStates=absent or sameAsFci2 (follows the CL-PC adjustment state of PUSCH), the UE may apply the same CL-PC adjustment state as that of PUSCH. <Case 2> If srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is not provided (SRS-specific CL-PC adjustment state is configured and TPC accumulation is not configured), the UE may determine / decide / apply the CL-PC adjustment state of the SRS taking into account (based on) the sum of the TPC commands for the SRS jointly coded by DCI format 2_3. <Case 3> If srs-PowerControlAdjustmentStates = separateClosedLoop and tpc-Accumulation is provided (SRS-specific CL-PC adjustment state is set and TPC accumulation is set), the TPC command for the SRS jointly coded by DCI format 2_3 may be applied as the CL-PC adjustment state of the SRS.

[0109] Regardless of the above case, the UE may also apply a specific CL-PC adjustment state (separate from PUSCH) for SRS, where a new index k={0,1} may be introduced to indicate the SRS-specific CL-PC adjustment state separate from PUSCH.

[0110] In the present disclosure, the values ​​of l and k may be set / indicated for each SRS resource set / SRS resource.

[0111] (Asymmetric DL sTRP / UL mTRP placement scenario) In this disclosure, the following may be assumed in extending the asymmetric DL sTRP / UL mTRP deployment scenario: Do not change existing cell definitions. No new cell definitions (e.g. UL-only cells) are required. · Unified TCI Framework (Rel.17 / 18). · Utilization of existing QCL / UL spatial relationship provisions. · Targets FR1 / FR2.

[0112] (Possible scenario) The present disclosure may assume the following scenario. · The UE receives DL signals (e.g., including PL-RS) from one DL TRP. ·The UE transmits UL signals to multiple UL TRPs.

[0113] Figure 8 is a conceptual diagram showing an example of an asymmetric DL sTRP / UL mTRP deployment scenario. As shown in Figure 8, a UE receives DL signals from one DL TRP. The UE may also transmit UL signals to the DL TRP / multiple UL TRPs (UL TRP#1 / #2). In this case, the UE may dynamically switch which TRP to transmit UL signals to, for example, according to the indicated TCI state.

[0114] (Unified TCI Framework) In the present disclosure (in asymmetric DL sTRP / UL mTRP deployment scenario), a unified TCI framework for Rel.17 / 18 may be supported. The following are examples of supported scenarios (intra-cell / inter-cell):

[0115] <Intra-cell scenario> · Unified TCI for single TRP (Rel.17) may only be supported for one UL TRP. · Unified TCI for Single DCI Multi-TRP (Rel.18) may be supported for multiple UL TRPs. Unified TCI (Rel.18) for multi-DCI multi-TRP may not be supported.

[0116] <Inter-cell scenario> Unified TCI (Rel.17) for single TRP may be supported in inter-cell scenarios (Inter cell beam management (ICBM) in Rel.17). · Unified TCI (Rel.18) for single DCI multi-TRP may not be supported. Unified TCI for multi-DCI multi-TRP (Rel.18) may be supported for inter-cell multi-TRP in Rel.17.

[0117] (DCI format 2_3) As described above, DCI format 2_3 may be used only for carrier switching of SRS. For example, DCI format 2_3 may be used according to the following conditions:

[0118] <Condition 1> The UE is configured with higher layer parameter srs-TPC-PDCCH-Group=typeA for ULs where there is no PUCCH and PUSCH or where SRS power control is not associated with PUSCH power control. <Condition 2> The UE is configured with higher layer parameter srs-TPC-PDCCH-Group=typeB for ULs without PUCCH and PUSCH or for ULs where SRS power control is not associated with PUSCH power control.

[0119] or, <Condition A> Carrier switching with no PUCCH / PUSCH on the carrier. <Condition B> Carrier switching with power control adjustment state set for SRS separate (independent / separate) from PUSCH.

[0120] DCI format 2_3 may be used for any purpose, not limited to the case of carrier switching of SRS, for example, it may be applied to the case of SRS transmission having a CL-PC adjustment state different from that of PUSCH.

[0121] (SRS specific closed loop power control (CL-PC) adjustment state) <<Aspect 0>> In the Rel.18 specification, when srs-PowerControlAdjustmentStates = separateClosedLoop is set, there is only one closed-loop power control (CL-PC) adjustment state for SRS, separate from PUSCH, and this CL-PC adjustment state can be controlled by DCI format 2_3.

[0122] The UE may be configured with one or more (two) CL-PC adjustment states for the SRS, and the one or more (two) CL-PC adjustment states may be configured separately from the PUSCH.

[0123] The higher layer parameter srs-PowerControlAdjustmentStates indicates whether twoPUSCH-PC-AdjustmentStates (one / two PUSCH power control adjustment states) or another closed-loop power control adjustment state is configured for the SRS. This higher layer parameter may only be applied to the UL where the UE also transmits PUSCH. If this higher layer parameter is absent / released, the UE may apply the value of sameAs-Fci1.

[0124] That is, when the SRS follows the CL-PC adjustment state of the PUSCH, if there are two CL-PC adjustment states in the PUSCH, the upper layer parameter srs-PowerControlAdjustmentStates may indicate which CL-PC adjustment state the SRS follows.

[0125] For example, if srs-PowerControlAdjustmentStates = absent, the SRS follows the CL-PC adjustment state (Fci1) of one PUSCH; if srs-PowerControlAdjustmentStates = absent, the SRS follows the CL-PC adjustment state (Fci1); if srs-PowerControlAdjustmentStates = sameAsFci2, the SRS follows the CL-PC adjustment state (Fci2) of the other PUSCH; if srs-PowerControlAdjustmentStates = separateClosedLoop, the SRS follows a dedicated (unique) CL-PC adjustment state.

[0126] <<Aspect 1>> The UE supports multiple (two) CL-PC adjustment states for SRS, separate from PUSCH, as a function independent of SRS carrier switching.

[0127] The UE may be configured with multiple (two) CL-PC adjustment states separate from the PUSCH, regardless of the configuration for the PUSCH and the configuration for SRS carrier switching.

[0128] Fig. 9 is a conceptual diagram showing an example of SRS transmission according to aspect 1. As shown in Fig. 9, the UE may configure, for SRS#1 / #2, multiple (two) CL-PC adjustment states (l=0, 1) that are the same as those for PUSCH#1 / #2, and multiple (two) CL-PC adjustment states (k=0, 1) that are different from those for PUSCH#1 / #2.

[0129] Specifically, the UE may transmit SRS#1 to UL TRP#1 by applying the same CL-PC adjustment state (l=0) as for PUSCH#1.

[0130] The UE may transmit SRS#2 to UL TRP#2 by applying the same CL-PC adjustment state (l=1) as for PUSCH#2.

[0131] Furthermore, the UE may transmit SRS#3 for DL ​​TRP by applying a first CL-PC adjustment state (k=0) different from that for PUSCH (independent from PUSCH). The UE may perform UL (SRS#3) transmission to acquire DL CSI.

[0132] Furthermore, the UE may transmit SRS#4 for any TRP (any direction) by applying a second CL-PC adjustment state (k=1) different from (independent of) the PUSCH. The UE may perform UL (SRS#4) transmission for beam management.

[0133] In transmitting SRS#4, the arbitrary direction may refer to a predetermined angle range (e.g., a range of 180 degrees or 360 degrees) in which a certain TRP is assumed to exist. The UE may transmit multiple beams for BM in the arbitrary direction. The SRS for BM may be used for SRS-based beam sweeping.

[0134] In this way, the UE may be configured with the same multiple (two) CL-PC adjustment states (l = 0, 1) for SRS (#1 to #2) as for PUSCH, and may be configured with a CL-PC adjustment state (k = 0, 1) for SRS (#3 to #4) that is different from that for PUSCH.

[0135] A new higher layer parameter may be introduced to enable a separate CL-PC adjustment state for SRS than for PUSCH.

[0136] FIG. 10 is a diagram illustrating an example of SRS configuration according to aspect 1. As illustrated in FIG. 10, SRS resource set #1 (for example, used for CB) corresponds to SRS resource #1, and the power control adjustment state may be set to, for example, Fci1 (srs-PowerControlAdjustmentStates = absent). SRS resource set #2 (for example, used for CB) corresponds to SRS resource #2, and the power control adjustment state may be set to, for example, Fci2 (srs-PowerControlAdjustmentStates = sameAsFci2). SRS resource set #3 (for example, used for AS) corresponds to SRS resource #3, and the power control adjustment state may be set to, for example, the first CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop). SRS resource set #4 corresponds to SRS resource #4 (for example, used for beam management (BM)), and the power control adjustment state may be set to, for example, the second CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop).

[0137] According to the above-described aspects 0 to 1, the UE may be configured with one or more (two) SRS resource sets having the same CL-PC adjustment state as the PUSCH, and one or more (two) SRS resource sets having a CL-PC adjustment state different from that of the PUSCH, within a certain CC.

[0138] These configurations may be supported per SRS resource set / SRS resource, and may be supported regardless of whether the corresponding CC / BWP is configured for PUSCH or SRS antenna switching.

[0139] As mentioned above, SRS-specific CL-PC adjustment states (additional CL-PC adjustment states) separate from PUSCH may be introduced (eg, k=0,1).

[0140] In the new higher layer parameters, srs-TPC-PDCCH-Group = {typeA, typeB} may be supported.

[0141] DCI format 2_3 may be used to indicate a TPC command for the first / second CL-PC adjustment state separate from the PUSCH. For example, at least one of the following options 1 and 2 may be applied. That is, the UE may apply at least one of the following options 1 and 2 to determine the first / second CL-PC adjustment state separate from the PUSCH for the SRS.

[0142] (Option 1) One group-common DCI (e.g., DCI format 2_3) may indicate two TPC commands associated with a first / second CL-PC adjustment state different from that of the PUSCH in a certain CC / BWP. Here, a second TPC command (a new / additional TPC command) different from the first TPC command may be introduced to indicate the second CL-PC adjustment state. The second TPC command may be configured with, for example, two bits.

[0143] 11A and 11B are diagrams showing examples of TPC command (DCI) fields. Fig. 11A corresponds to the case where srs-TPC-PDCCH-Group = type A, and Fig. 11B corresponds to the case where srs-TPC-PDCCH-Group = type B. Note that the order of each field in the TPC command of the present disclosure is merely an example and can be changed as appropriate. The same applies to the TPC commands in the other figures below.

[0144] As shown in FIG. 11A, the group-common DCI may include an indication of a TPC command for multiple CCs after (following) the SRS request field. In other words, the group-common DCI may include a TPC command for each CC. The setting order of the TPC command field may be set in ascending (or descending) order of cells (CCs), and if the cells are the same, may be set in ascending (or descending) order of CL-PC adjustment states (e.g., TPC command 1 for {1st CL-PC, CC#1}, TPC command 2 for {2nd CL-PC, CC#1}, ..., TPC command 1 for {1st CL-PC, CC#X}, TPC command 2 for {2nd CL-PC, CC#1}).

[0145] As shown in Figure 11B, the TPC command field for a CC (cell) may be configured with one field (as is) to indicate a TPC command for any TRP. In this case, an X bit may be added to indicate which TRP the TPC command is associated with (a CL-PC adjustment state other than PUSCH). For example, if the number of CL-PC adjustment states other than PUSCH is two, X may be 1.

[0146] As shown in Figure 11B, the group-common DCI may include an indication of a TPC command for one CC after (following) the SRS request field. The setting order of the TPC command field may be set in ascending (or descending) order of the CL-PC adjustment state (e.g., TPC command 1 for {1st CL-PC}, TPC command 2 for {2nd CL-PC}).

[0147] (Option 2) One group-common DCI (for example, DCI format 2_3) may indicate one TPC command associated with a first / second CL-PC adjustment state other than PUSCH in a certain CC / BWP. The indication method can be further classified into the following Alt2-1 to Alt2-2. That is, DCI format 2_3 may explicitly / implicitly indicate whether either the first / second CL-PC adjustment state other than PUSCH is associated with the TPC command.

[0148] (Alt2-1) A new bit field may be added to indicate that either the first or second CL-PC adjustment state, separate from the PUSCH, is associated with the TPC command. The new bit field may consist of, for example, one bit.

[0149] (Alt2-2) An existing bit field (eg, SRS request field) may be used to implicitly indicate that either the first or second CL-PC adjustment state separate from the PUSCH is associated with the TPC command.

[0150] According to this aspect, the UE can control SRS transmission by applying the same CL-PC adjustment state as that for PUSCH or an SRS-specific CL-PC adjustment state separate from that for PUSCH, regardless of the setting of SRS carrier switching.

[0151] <<Aspect 2>> Since the UE supports two CL-PC adjustment states for SRS, at least one of the following options 1 to 4 may be applied.

[0152] Option 1: The CL-PC coordination state for an SRS is associated with an SRS resource set. Alternative 2: If the higher layer parameter srs-PowerControlAdjustmentStates is set to separateClosedLoop, then the TCI state closedLoopIndex-r17 indicates one CL-PC adjustment state for the SRS. Option 3: In TCI state P0AlphaSet-r17, add a parameter indicating one of the two CL-PC adjustment states for SRS. Option 4: The CL-PC coordination state for an SRS is associated with the usage of the SRS resource.

[0153] <<Aspect 3>> (Two CL-PC adjustment states [SRS-specific] separate from PUSCH) The UE may support two CL-PC adjustment states (SRS-specific) separate from PUSCH as an SRS carrier switching independent feature, which may be applied regardless of the PUSCH / SRS carrier switching configuration in CC.

[0154] (Extended DCI format 2_3) Both srs-TPC-PDCCH-Group = type A and type B may be supported, provided that the existing SRS carrier switching function cannot be configured simultaneously within the same CC (simultaneous configuration is not supported).

[0155] (Additional TPC commands introduced) For each CC with two CL-PC adjustment states for SRS, one additional TPC command may be introduced.

[0156] For example, in the case of Type B, one DCI can indicate two TPC commands at the same time, which requires only one additional bit compared to the 1-bit closed-loop-indicator field.

[0157] On the other hand, in the case of Type A, N additional bits are required compared to the 1-bit closed-loop-indicator field corresponding to N CCs.

[0158] Two (first / second) CL-PC coordination states for the SRS may be associated with the SRS resource set.

[0159] In the case where two CL-PC adjustment states are applied, it is assumed that one is for SRS carrier switching and the other is for SRS beam management. Considering this, there is no need to dynamically switch the association. In other words, there is no need to indicate two (first / second) CL-PC adjustment states for SRS in the TCI state.

[0160] Therefore, a new upper layer parameter (separateClosedLoopSecond_r19) may be introduced for each SRS resource set.

[0161] (analysis) It is being considered that a DL sTRP / UL mTRP scenario will be applied to future wireless communication systems. In this case, it is being considered that two TAs / TAGs will be indicated.

[0162] For example, a further extension of the asymmetric DL sTRP / UL mTRP deployment scenario would consider intra-band / intra-cell non-co-located multi-TRPs and further a unified TCI framework for multi-TRPs targeting FR1 and FR2, without requiring changes to existing cell definitions or definitions for new cells (e.g., UL-only cells).

[0163] In this extension, for example, when a path loss RS is transmitted from a DL sTRP, the path loss calculation towards the UL TRP requires specifying two closed-loop power control adjustment states for the SRS (both independent of the PUSCH) or the path loss offset setting.

[0164] The two TAs in the asymmetric DL sTRP / UL mTRP deployment scenario need to be supported, for example, in the following framework: Multi-DCI based intra-cell / inter-cell multi-TRP framework. Single DCI-based intra-cell multi-TRP framework. Single DCI-based inter-cell beam management (ICBM) framework. · Single TRP-based inter-cell ICBM framework.

[0165] At least one of the following issues is being considered:

[0166] <Assignment 1> For example, when two TAs are supported in a single DCI-based intra-cell multi-TRP / inter-cell single-TRP, the PRACH-related indicator field of the DCI (e.g., DCI format 1_0) needs to be extended.

[0167] For example, in existing specifications, for a PRACH triggered by a PDCCH order, the PRACH related indicator field in the PDCCH order indicates that the PL-RS of the corresponding PRACH transmission is the QCL-RS of the PDCCH order or the SSB indicated in the PDCCH order.

[0168] Specifically, if the UE is provided with a specific parameter SSB-MTC-AdditionalPCI, the PRACH-related indicator field indicates the PCI associated with the PRACH transmission, whereas if the UE is not provided with a specific parameter SSB-MTC-AdditionalPCI, the PRACH-related indicator field indicates the PL-RS for the PRACH transmission.

[0169] The above-mentioned existing specifications are for multi-TRP within a cell based on multi-DCI, so the content needs to be extended to single DCI / single TRP between cells.

[0170] <Assignment 2> In addition, even when supporting two TAs in a single DCI-based inter-cell beam management (ICBM) / single inter-cell TRP, further enhancements such as UL timing adjustment are required.

[0171] <Assignment 3> Also, in Rel.18, with two TAs for multi-DCI based intra-cell / inter-cell multi-TRP, the UE does not expect the TCI state (UL TCI state) associated with one coresetPoolIndex to correspond to two TAGs.

[0172] The above constraints also need to be further extended to support single DCI-based inter-cell beam management (ICBM) / inter-cell single TRP.

[0173] <Assignment 4> As mentioned above, in Rel.18 multi-DCI based intra-cell multi-TRP, the PRACH association indicator indicates whether the PRACH (transmission) is associated with the PCI of the serving cell or with an active additional cell (additional PCI).

[0174] Here, in the multi-DCI-based multi-TRP within a cell, only one additional active cell (additional PCI) can be associated with the PRACH (transmission).

[0175] On the other hand, in Rel. 19 and later, with single DCI-based inter-cell beam management (ICBM) / inter-cell single TRP, it is expected that a maximum of seven additional active cells (additional PCIs) can be associated with the PRACH (transmission).

[0176] In this case, it is necessary to further extend the PRACH-related indicators for single DCI-based inter-cell ICBM / inter-cell single TRP.

[0177] <Assignment 5> In asymmetric DL sTRP / UL mTRP, there is insufficient consideration as to whether the UL TRP transmits a specific DL signal / channel (e.g., synchronization signal block (SSB)). Also, if the UL TRP transmits a specific DL signal / channel, there is insufficient consideration as to under what circumstances the UE receives the specific DL signal / channel from the UL TRP.

[0178] <Assignment 6> It is being considered to introduce a new field (e.g., a 1-bit field) in a specific DCI format (e.g., DCI format 1_0) to indicate the PL offset for the PRACH relative to the PDCCH order (PDCCH order PRACH).

[0179] The new field is expected to be set simultaneously with the PRACH-related indicator field in certain cases.

[0180] However, there is insufficient consideration on how to set the new field and the PRACH-related indicator field.

[0181] Unless at least one of these issues is resolved, the UE may not be able to properly control UL transmission / DL reception when DL sTRP / UL mTRP is applied.

[0182] Therefore, the present inventors have conceived a method for appropriately controlling UL transmission / DL reception even when DL sTRP / UL mTRP is applied.

[0183] (Various reading changes, etc.) 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.

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

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

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

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

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

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

[0190] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0191] In the present disclosure, the terms base station, gNB, network (NW), RS group, antenna port group, and control resource set (CORESET) group may be interchangeable. In the present disclosure, the terms terminal, user terminal, and user equipment (UE) may be interchangeable.

[0192] In this disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In this disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0193] In this 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 set, 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.

[0194] In the present disclosure, the following may be read interchangeably: sTRP, single TRP, channel / signal using single TRP, one SRS resource set indicated by DCI, 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 CORESET pool index (CORESETPoolIndex) value of 1 not set for any CORESET, and no codepoint in the TCI field mapped to two TCI states.

[0195] In the present disclosure, mTRP, multi-TRP, two SRS resource sets indicated by DCI, 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 as interchangeable terms.

[0196] In the present disclosure, single DCI, sDCI, single PDCCH, multi-TRP based on single DCI, sDCI-based mTRP, activating two TCI states on at least one TCI code point, mapping at least one code point of a TCI field to two TCI states, and setting a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a specific channel / CORESET may be read as interchangeable.

[0197] In the present disclosure, multi-DCI, mDCI, multi-PDCCH, multi-TRP based on multi-DCI, mDCI-based mTRP, setting two CORESET pool indices or CORESET pool index = 1 (or a value greater than or equal to 1), and setting multiple specific indexes (e.g., TRP index, CORESET pool index, or index corresponding to TRP) for a specific channel / CORESET may be read interchangeably.

[0198] In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index=0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP) TRP#1 (first TRP) may correspond to CORESET pool index=1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field. The first TRP or second TRP may be a DL transmission point or a UL reception point.

[0199] The UL reception point may be connected to a TRP (e.g., a base station) or a core network via wired or wireless connections. 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 and may be applied to a base station forming a macrocell. For example, the UL reception point may not transmit downlink data but may transmit control signals / channels.

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

[0201] In the present disclosure, the SRS may be at least one of an aperiodic (A)-SRS, a periodic (P)-SRS, and a semi-persistent (SP)-SRS.

[0202] In the present disclosure, the path loss reference RS, the path loss reference RS for PUSCH, the path loss reference RS for PUCCH, the path loss reference RS for SRS, SSB, CSI-RS, and RS may be interchangeable. In the present disclosure, the path loss (PL), the path loss value, and the path loss parameter may be interchangeable.

[0203] In this disclosure, the terms base station, UL receiving point, UL TRP, UL only TRP, and micro BS may be interchangeable. An UL receiving point may perform only UL reception, or may perform DL transmission if certain conditions are met.

[0204] In this disclosure, the terms base station, DL transmission point, DL TRP, DL only TRP, macro BS, and central TRP may be interchangeable. A DL transmission point may only perform DL transmission, or may perform UL reception if certain conditions are met.

[0205] In the present disclosure, TA, TAG, and TA offset value may be interchangeable. DL reference timing and DL reception timing may be interchangeable. Two TAs / TAGs may be interchangeable with more than two TAs / TAGs.

[0206] In the present disclosure, coresetPoolIndex, CORESET pool index, and an RRC parameter indicating a CORESET pool index may be interchangeable. n-TimingAdvanceOffset and TA offset may be interchangeable. TCI-UL-State, UL TCI state, and an RRC parameter indicating a UL TCI state may be interchangeable. dl-OrJointTCI-StateList, a list of DL or joint TCI states, and an RRC parameter indicating a list of DL or joint TCI states may be interchangeable. ul-TCI-StateList, a list of UL TCI states, and an RRC parameter indicating a list of UL TCI states may be interchangeable. n-TimingAdvanceOffset and n-TimingAdvanceOffset2 may be interchangeable with a TA offset and an RRC parameter indicating a TA offset. In the present disclosure, dl-OrJointTCI-StateList, ul-TCI-StateList, a list related to unified TCI states, a list of unified TCI states, etc. may be interchangeable.

[0207] DL sTRP / UL mTRP may refer to, for example, the scenario applied in Rel. 19. DL sTRP / UL mTRP may refer to, for example, Scenario 1 ( FIG. 1B ) or Scenario 2 ( FIG. 2 ). Asymmetric DL sTRP / UL mTRP and DL sTRP / UL mTRP may be interchangeable.

[0208] In the present disclosure, inter-cell single TRP [operation / framework / scenario], single TRP [based] inter-cell beam management, single TRP ICBM, Rel. 17 ICBM, single TRP inter-cell [Rel. 17] unified TCI framework, etc. may be read interchangeably.

[0209] (Wireless communication method) In the present disclosure, when an inter-cell single TRP is configured / applied, one indicated TCI state of a first cell (e.g., a serving cell) may be updated / changed to one indicated TCI state of a second cell (e.g., a non-serving cell) by RRC signaling / MAC CE / DCI. The UE may transmit / receive signals / channels using the indicated TCI state of the first cell until the update / change of the indicated TCI state by the RRC signaling / MAC CE / DCI is completed. Furthermore, the UE may transmit / receive signals / channels using the indicated TCI state of the second cell after the update / change of the indicated TCI state by the RRC signaling / MAC CE / DCI is completed. The indicated TCI state of the first cell may correspond to a first TA, and the indicated TCI state of the second cell may correspond to a second TA. The first TA may be updated / changed to the second TA in response to an update / change of the TCI state indicated by RRC signaling / MAC CE / DCI.

[0210] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0211] <Embodiment 0A> Embodiment 0A addresses the above-mentioned problem 1 and relates to an extension of PRACH-related indicators in single DCI-based intra-cell multi-TRP / inter-cell single TRP.

[0212] The PRACH related indicator may indicate the PCI (serving cell / additional cell) associated with the PRACH transmission or the PL-RS for the PRACH transmission.

[0213] The UE may determine the cell (PCI) associated with the PRACH transmission or the PL-RS for the PRACH transmission based on the PRACH-related indicator.

[0214] More specifically, the UE may control the determination depending on whether a specific parameter (SSB-MTC-AdditionalPCI) is provided. The UE may apply the above-mentioned existing specifications to the determination.

[0215] For example, the UE may apply the same (common) behavior regarding the above determination to a single TRP scenario (e.g., inter-cell single TRP) / single DCI-based scenario / multiple DCI-based scenario.

[0216] Alternatively, the UE may apply different operations regarding the above determination to a single TRP scenario (e.g., inter-cell single TRP), a single DCI-based scenario, and a multi-DCI-based scenario, i.e., the UE may apply the above determination in any of the cases of the single TRP scenario (e.g., inter-cell single TRP), the single DCI-based scenario, and the multi-DCI-based scenario.

[0217] [Aspect 1-1] To support two TAs in a single DCI-based intra-cell multi-TRP framework / inter-cell single TRP, the PRACH-related indicator in DCI format 1_0 may be 1 bit if at least one of the following conditions is met:

[0218] That is, the UE may determine / assume the number of bits of the PRACH-related indicator based on at least one of the following conditions (see FIG. 12):

[0219] (Condition 1) When the UE is provided with a specific parameter (tag-Id2), the specific parameter may be a parameter indicating a timing advance group.

[0220] (Condition 2) When the UE is provided with a specific parameter (new higher layer parameter), the new higher layer parameter may be a parameter that enables multiple (two) TAs in a specific scenario (single DCI-based intra-cell multi-TRP framework / single DCI-based inter-cell beam management framework / inter-cell single TRP).

[0221] (Condition 3) When the UE is provided with a specific parameter (new higher layer parameter), the new higher layer parameter may be, for example, a parameter that provides a path loss offset configuration for a specific scenario (DL sTRP / UL mTRP deployment scenario).

[0222] (Condition 4) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario, or multiple (two) TAs in a single DCI-based intra-cell multi-TRP framework, or multiple (two) TAs in an inter-cell single-TRP framework.

[0223] (Condition 5) If the UE is provided with at least one TCI codepoint indicating two TCI states.

[0224] (Condition 6) The UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has two indicated TCI states. Condition 6 may be a condition for single DCI-based multi-TRP in a unified TCI state. For example, condition 6 may be read as "The UE is provided with dl-OrJointTCI-StateList or TCI-UL-State and a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State are indicated."

[0225] (Condition 7) If the UE has dl-OrJointTCI-StateList or ul-TCI-StateList configured.

[0226] (Condition 8) If the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has one indicated TCI state (if the UE is configured with [inter-cell] single TRP).

[0227] In addition, if the UE has dl-OrJointTCI-StateList or ul-TCI-StateList configured, has two indicated TCI states, and at least one of the two indicated TCI states is associated with a physical cell ID (PCI) different from the PCI of the serving cell (e.g., the PCI of a non-serving cell), the PRACH-related indicator in DCI format 1_0 may not be present (may be 0 bit).

[0228] The UE may determine / assume the number of bits of the PRACH-related indicator based on at least one of the above conditions.

[0229] <Modification of Aspect 1-1> To support two TAs in a single DCI-based intra-cell / inter-cell multi-TRP framework / inter-cell single-TRP, a new field having a similar function to the PRACH-related indicator field described above may be introduced. The new field may be referred to as a field for supporting two TAs in a single DCI-based intra-cell / inter-cell multi-TRP framework / inter-cell single-TRP.

[0230] (Specification example 1) The new field is made up of 0 or 1 bit. The new field may be 1 bit if it satisfies at least one of the above conditions 1 to 8.

[0231] The new field consists of 0 or 1 bits.

[0232] A new field indicates the PL-RS for PRACH transmission. Index 0 of this field is mapped to the DL RS where the PDCCH-ordered DM-RS is quasi-collocated. Index 1 of this field is mapped to the SS / PBCH indicated by the SS / PBCH index field in this DCI format (1_0).

[0233] Otherwise, if none of the above conditions are met, the new field is a 0 bit.

[0234] (Specification example 2) If at least one of the following conditions is met, the UE is provided with a parameter referenceSignalPower related to the reference signal power by a corresponding parameter ss-PBCH-BlockPower:

[0235] If the PRACH transmission from the UE is a response to the detection of a PDCCH order by the UE that triggers a contention-free random access procedure, and the DM-RS of the PDCCH order depends on a DL RS that is QCL'd, then at least one of the following conditions is met: If there is no PRACH-related indicator in the PDCCH order, If the cell indicator field of the PDCCH order does not exist or the value of this field is 0, If the UE is not provided with SSB-MTC-AdditionalPCI and the value of the PRACH-related indicator field of the PDCCH order is 0, If the PRACH related indicator field of the PDCCH order indicates a physical cell ID (physCellId) related to the cell receiving the PDCCH order, If the value of the new field in the PDCCH order is 0, -Depending on the indicated SS / PBCH block, If the PRACH transmission is sent in a non-serving cell indicated by the cell indicator field of the PDCCH order, If the UE is not provided with SSB-MTC-AdditionalPCI and the value of the PRACH-related indicator field of the PDCCH order is 1, If the PRACH related indicator field of the PDCCH order indicates a physCellId that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order, ·If the value of the new field in the PDCCH order is 1.

[0236] [Aspect 1-2] In a single DCI based intra-cell multi-TRP framework, inter-cell single-TRP, or DL ​​sTRP / UL mTRP deployment scenario, two TAs may not be supported.

[0237] If a single DCI based intra-cell multi-TRP framework, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario is configured, the UE may not expect at least one of the following configurations / instructions / behaviors:

[0238] Multiple TAGs (two, three or more) can be configured for one serving cell. Multiple (two, three or more) DL reference timings may be configured for one serving cell, where each DL reference timing may be associated with a TAG. Multiple (two, three or more) timing advance offset values ​​(n-TimingAdvanceOffset values) may be configured for each serving cell, where each timing advance offset value may be associated with a TAG. · The correspondence (mapping / association) between TAG ID and TCI state is set. · The TAG ID is indicated in the absolute timing advance MAC CE (absolute TAC MAC CE). -The TAG ID is indicated in the MAC Random Access Response (MAC RAR). · A PDCCH order in one TRP / cell / PCI / TCI state triggers a PRACH for a TRP / cell / PCI / TCI state different from the PDCCH order. PRACH-related indicator in the PDCCH order that triggers the PRACH (the PRACH-related indicator must be included in the PDCCH order). · TAG ID is indicated in the PDCCH order. ·TAG and SSB / CSI-RS are associated.

[0239] In aspect 1-2, "when a single DCI-based intra-cell multi-TRP framework, an inter-cell single TRP, or a DL sTRP / UL mTRP deployment scenario is configured" may mean that at least one of the following conditions is met:

[0240] · If new higher layer parameters enabling DL sTRP / UL mTRP placement scenarios are provided to the UE. ·For DL ​​sTRP / UL mTRP deployment scenarios, new higher layer parameters for configuring path loss offset are provided to the UE. · If the UE is provided with at least one TCI codepoint indicating two TCI states and the UE is not provided with two different CORESETPoolIndex (i.e., single DCI based). · If the UE has dl-OrJointTCI-StateList or ul-TCI-StateList configured and has two indicated TCI states, and the UE is not provided with two different CORESETPoolIndex. · If the UE has dl-OrJointTCI-StateList or ul-TCI-StateList configured and has one indicated TCI state, and the UE is not provided with two different CORESETPoolIndex. · If the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and the UE is not provided with two different CORESETPoolIndex. · If the UE has dl-OrJointTCI-StateList or ul-TCI-StateList configured and has one indicated TCI state.

[0241] According to this embodiment, the UE can support two TAs in a single DCI-based intra-cell multi-TRP framework, an inter-cell single TRP, or a DL sTRP / UL mTRP deployment scenario, and even if the UE does not support the two TAs, it can appropriately control the corresponding behavior according to a specific scenario.

[0242] <Embodiment 0B> Embodiment 0B addresses the above-mentioned problem 2 and relates to an extension for two TAs in single DCI-based inter-cell beam management (ICBM) / inter-cell single TRP.

[0243] [Aspect 2-1] In single DCI-based inter-cell beam management / inter-cell single TRP, the following extensions may be applied to support two TAs: When supporting two TAs in single DCI-based inter-cell beam management / inter-cell single TRP, the UE may expect / assume at least one of the following:

[0244] Multiple TAGs (two, three or more) can be configured for one serving cell. Multiple (two, three or more) DL reference timings may be configured for one serving cell, where each DL reference timing may be associated with a TAG. Multiple (two, three or more) timing advance offset values ​​(n-TimingAdvanceOffset values) may be configured for each serving cell, where each timing advance offset value may be associated with a TAG. · The correspondence (mapping / association) between TAG ID and TCI state is set. In UL transmission, the TAG ID associated with the UL / joint TCI state may be used. · The TAG ID is indicated in the absolute timing advance MAC CE (absolute TAC MAC CE). The TAG ID is indicated in the MAC Random Access Response (MAC RAR). The TAC (Timing Advance Command) in the MAC RAR may be applied to the indicated TAG ID. · Receive (configure) PRACH configuration for each additional cell / PCI (where the PCI is different from the PCI of the serving cell). A PRACH-related indicator in the PDCCH order that triggers the PRACH (the PDCCH order must include a PRACH-related indicator). As described above, the PRACH-related indicator indicates the PCI (serving cell / additional cell) associated with the PRACH transmission. That is, the PRACH-related indicator indicates whether the PRACH transmission is associated with the serving cell or with which additional cell. · A PDCCH order in one TRP / cell / PCI / TCI state triggers a PRACH for a TRP / cell / PCI / TCI state different from the PDCCH order. · TAG ID is indicated in the PDCCH order. ·TAG and SSB / CSI-RS are associated.

[0245] [Aspect 2-2] The UE may apply the content of aspect 2-1 if at least one of the following conditions is satisfied: That is, the UE may determine / assume support for two TAs in single DCI-based ICBM / inter-cell single TRP based on the following conditions 1 to 4.

[0246] (Condition 1) When the UE is provided with specific parameters (new higher layer parameters), such as DL sTRP / UL mTRP deployment scenarios, single DCI-based ICBM, or parameters enabling multiple (two) TAs in an inter-cell single TRP scenario.

[0247] (Condition 2) When the UE is provided with specific parameters (new higher layer parameters), the new higher layer parameters may be parameters related to the configuration of the path loss offset, for example, for a DL sTRP / UL mTRP deployment scenario.

[0248] (Condition 3) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in DL sTRP / UL mTRP deployment scenario, multiple (two) TAs in single DCI-based ICBM, or multiple (two) TAs in inter-cell single TRP.

[0249] (Condition 4) If the UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) and is not provided with two different CORESETPoolIndex (i.e., it supports single DCI-based ICBM or inter-cell single TRP).

[0250] The UE may determine / assume support for two TAs in single DCI-based ICBM / inter-cell single TRP based on conditions 1 to 4.

[0251] [Aspect 2-3] In a single DCI based ICBM framework, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario, two TAs may not be supported.

[0252] When a single DCI-based ICBM framework, an inter-cell single TRP, or a DL sTRP / UL mTRP deployment scenario is configured, the UE may not expect at least one of the contents (configuration / instruction / behavior) of aspect 2-1.

[0253] In aspect 2-3, "when a single DCI-based ICBM framework, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario is configured" may mean that at least one of the following conditions is met:

[0254] · The UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) and is not provided with two different CORESETPoolIndex (meaning it supports single DCI-based ICBM or inter-cell single TRP). · If new higher layer parameters enabling DL sTRP / UL mTRP placement scenarios are provided to the UE. ·For DL ​​sTRP / UL mTRP deployment scenarios, new higher layer parameters for configuring path loss offset are provided to the UE.

[0255] According to this embodiment, the UE can support two TAs in a single DCI-based ICBM framework, an inter-cell single TRP, or a DL sTRP / UL mTRP deployment scenario, and even if the UE does not support the two TAs, it can appropriately control the corresponding operation according to a specific scenario.

[0256] <Embodiment 0C> Embodiment 0C addresses the above-mentioned problem 3 and relates to restrictions when two TAs are supported in a single DCI-based ICBM / inter-cell single TRP.

[0257] When multiple (two) TAs are enabled in a single DCI based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario, the UE does not expect the TCI states (TCI-states) / UL TCI states (TCI-UL-States) associated with a cell / PCI to correspond to two / multiple TAGs.

[0258] Alternatively, depending on the UE capabilities, the TCI-states / UL TCI-states associated with a cell / PCI may correspond to two / multiple TAGs.

[0259] In embodiment 0C, "when multiple (two) TAs are enabled in a single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario" may mean that at least one of the following conditions 1 to 7 is met.

[0260] (Condition 1) When the UE is provided with a specific parameter (tag-Id2) (i.e., when the UE is provided with multiple (two) TAGs in the serving cell).

[0261] (Condition 2) When the UE is provided with the second n-TimingAdvanceOffset value (ie, when the UE is provided with multiple (two) Timing Advance Offset values ​​in the serving cell).

[0262] (Condition 3) The UE is provided with a mapping / association between TAG IDs and TCI states.

[0263] (Condition 4) If the UE is provided with new higher layer parameters to enable multiple (two) TAs in single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenarios.

[0264] (Condition 5) For DL ​​sTRP / UL mTRP deployment scenarios, new higher layer parameters for configuring path loss offset are provided to the UE.

[0265] (Condition 6) When a UE indicates / reports a specific capability (new UE capability), the UE capability may indicate support for multiple (two) TAs in DL sTRP / UL mTRP deployment scenario, multiple (two) TAs in single DCI-based ICBM, or multiple (two) TAs in inter-cell single TRP.

[0266] (Condition 7) If the UE is provided with a specific parameter (SSB-MTC-AdditionalPCI) and is not provided with two different CORESETPoolIndex (i.e., it supports single DCI-based ICBM or inter-cell single TRP).

[0267] [Variations] When multiple (two) TAs are enabled in a single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario, the UE does not expect a TAG with the same index to be associated with multiple indication TCI state indices. That is, in this case, the UE does not expect the same TAG index to be associated with each indication TCI state index. In other words, the UE does not expect a common TAG to be associated with multiple indication TCI states.

[0268] For example, the UE does not expect the first indicated TCI state to be associated with the first TAG (TAG#1) and the second indicated TCI state to be associated with the second TAG (TAG#1).

[0269] According to this embodiment, the UE can appropriately control its behavior when supporting two TAs in a single DCI-based ICBM framework, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario based on certain constraints.

[0270] <Embodiment 0D> Embodiment 0D addresses the above-mentioned problem 4 and relates to an extension of PRACH-related indicators in single DCI-based ICBM / inter-cell single TRP.

[0271] [Aspect 4-1] In the single DCI based ICBM, inter-cell single TRP or DL ​​sTRP / UL mTRP deployment scenarios where multiple (two) TAs are enabled, the UE determines which cell (additional cell / serving cell) should trigger PRACH according to options 1-2 below.

[0272] More specifically, in the above case, the UE determines whether it can trigger PRACH only for the active added cell (PCI) / serving cell, or whether it can trigger PRACH for the configured added cells (either the active added cells or the inactive added cells) based on the following options 1 to 2.

[0273] (Option 1) The PRACH may be triggered only for active additional cells or the serving cell, i.e., the UE may trigger the PRACH only for active additional cells or the serving cell.

[0274] (Option 2) The PRACH may be triggered for a configured added cell (either an active added cell or an inactive added cell), i.e., the UE may trigger the PRACH for a configured added cell (either an active added cell or an inactive added cell).

[0275] In this disclosure, an active PCI (additional cell) may refer to a PCI (additional cell) that is associated with an active TCI state.

[0276] According to this aspect, the UE can appropriately determine the cell (additional cell / serving cell) that is the trigger target of the PRACH.

[0277] [Aspect 4-2] In the case of a single DCI based ICBM, inter-cell single TRP or DL ​​sTRP / UL mTRP deployment scenario where multiple (two) TAs are enabled, at least one of the following options 1-2 may be applied to indicate which cell (PCI) a PRACH transmission is associated with.

[0278] That is, the UE may determine the cell (additional cell / serving cell) associated with the PRACH transmission according to Options 1-2 below.

[0279] (Option 1) The UE may use a PRACH-related indicator field in the PDCCH order (DCI format 1_0) that triggers the PRACH transmission, i.e., the UE may use the PRACH-related indicator field to determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0280] (Option 2) A new field added in the PDCCH order (DCI format 1_0) that triggers the PRACH transmission is used, i.e., the UE may use the new field (assuming the new field is added) to determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0281] According to this aspect, the UE can appropriately determine the cell (additional cell / serving cell) associated with the PRACH transmission.

[0282] [Aspect 4-3] The number of bits (size) of the PRACH-related indicator field / new field in aspect 4-2 may follow Alt1 to Alt3 below: The UE may determine / assume the number of bits of the PRACH-related indicator / new field according to Alt1 to Alt3 below.

[0283] (Alt1) The number of bits may be 3. With this number of bits, up to 8 PCIs (including 1 serving cell and 7 additional cells) can be configured / enabled. That is, the number of bits may be determined based on the number of cells (serving cell and additional cells).

[0284] (Alt2) The number of bits may be determined based on the number of additional cells. More specifically, the number of bits = ceil(log2(Nrof additionalPCI +1). In the present disclosure, ceil(X) may mean multiplying X by a ceiling function. Nrof additionalPCI may represent the number of additional cells (or active additional cells).

[0285] Nrof additionalPCI represents the number of additional cells and may be set by higher layer signaling (RRC) (Alt2-1).

[0286] Nrof additionalPCImay represent the number of active additional cells (i.e., the number of additional cells associated with an active TCI state) (Alt2-2).

[0287] Alt2 allows for flexible control of the number of bits depending on the number of additional cells (or active additional cells).

[0288] [Aspect 4-4] The mapping (association) of the code points of the PRACH-related indicator field / new field in aspect 4-2 may follow Alt1 to Alt2 below: The UE may determine / assume the mapping (association with the cell (PCI)) of the code points of the PRACH-related indicator / new field according to Alt1 to Alt2 below.

[0289] (Alt1) One code point (e.g., indicated by bit field index 0) may be mapped to the PCI of the serving cell. additionalPCI number of code points (e.g. bit field index 1 to Nrof additionalPCI The PCI of the additional cell may be configured by higher layer signaling (RRC) according to the descending / ascending order of the index of the additional cell.

[0290] (Alt2) One code point (e.g., indicated by bit field index 0) may be mapped to the PCI of the serving cell. additionalPCI number of code points (e.g. bit field index 1 to Nrof additionalPCI ) may be mapped to the PCI of the active add-on cell (the PCI of the add-on cell associated with the active TCI state) according to the descending / ascending order of the add-on cell's index.

[0291] According to this aspect, the UE can appropriately recognize / determine the correspondence between the code points of the PRACH-related indicators / new fields and the cells (PCIs) in accordance with Alt1 to Alt2.

[0292] In embodiment 0D, "when multiple (two) TAs are enabled in a single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario" may mean that the same conditions (conditions 1 to 7) as in embodiment 0C described above are met.

[0293] <Modifications of Embodiments 0A to 0D> In Rel.18 multi-DCI based inter-cell multi-TRP, if the PRACH related indicator field in a PDCCH order indicates the same PCI as the cell receiving the PDCCH order, the PL-RS of the PRACH transmission is (corresponds to) the DL RS to which the DM-RS of the PDCCH order is quasi-collocated / QCLed.

[0294] On the other hand, if the PRACH related indicator field in the PDCCH order indicates a PCI different from the cell receiving the PDCCH order, the PL-RS of the PRACH transmission is (corresponds to) the SSB indicated in the PDCCH order.

[0295] These correspondences may also be applied in the case where multiple (two) TAs are enabled in a single DCI-based ICBM / inter-cell single TRP.

[0296] Furthermore, the "PRACH-related indicator (field)" in the existing specifications may be read as the "new field" in the present disclosure.

[0297] For example, some of the conditions provided by the UE using the parameter referenceSignalPower related to reference signal power and the corresponding parameter ss-PBCH-BlockPower may be rephrased as at least one of the following: A new field in the PDCCH order indicates the physical cell ID (physCellId) associated with the cell receiving the PDCCH order. · If the new field in the PDCCH order indicates a physical cell ID (physCellId) that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

[0298] According to this modification, it is possible to effectively utilize existing specifications and simplify the UE implementation.

[0299] <Embodiment 1> The first embodiment addresses the above-mentioned problem 5 and relates to transmission of DL signals / channels from a UL TRP.

[0300] The UL TRP may follow at least one of the following scenarios: · Scenario A: UL TRP does not transmit DL signals / channels. · Scenario B: The UL TRP may transmit a specific DL signal / channel (e.g., SSB).

[0301] For DL ​​sTRP / UL mTRP deployment scenarios, the Rel.17 Unified TCI Framework (Rel.17 ICBM) / Rel.18 Unified TCI Framework may be applied.

[0302] In the Rel. 17 Unified TCI Framework (Rel. 17 ICBM), for FR1, one joint TCI state may be configured, and one DL TCI state and one UL TCI state may be configured.

[0303] In the Rel. 17 Unified TCI Framework (Rel. 17 ICBM), one DL TCI state and one UL TCI state may be configured for FR2.

[0304] In the Rel.18 unified TCI framework, for FR1, up to two (not more than two) joint TCI states may be configured, or one DL TCI state and up to two (not more than two) UL TCI states may be configured.

[0305] In the Rel. 18 unified TCI framework, one DL TCI state and up to two (not more than two) UL TCI states may be configured for FR2.

[0306] In Rel.17 ICBM (Inter-cell Single TRP), SSB corresponding to an additional PCI (PCI corresponding to a non-serving cell) may be supported as PL-RS and QCL-RS in the TCI state. SSB / CSI-RS may be indicated as PL-RS / QCL-RS in the UL TCI state. The UE may measure the SSB / CSI-RS. CSI-RS may be configured by the serving cell (DL TRP) and transmitted by the UL TRP.

[0307] In the following, a case will be described where the specific DL signal / channel transmitted by the UL TRP is SSB, but the specific DL signal / channel is not limited to this.

[0308] The DL sTRP / UL mTRP may have at least one of several characteristics: · Feature 1: (One or more) PL offsets are set. Feature 2: Two closed-loop power control (CL-PC) adjustment states are set for SRS separate from PUSCH. Feature 3: The CORESET pool index is not set and two TAs are set.

[0309] In the present disclosure, a PL offset being set, a UE being set with a PL offset, a PL offset having a non-zero value being set, a UE being set with a PL offset having a non-zero value, a PL offset having a value of zero being set, a UE being set with a PL offset having a value of zero, a PL offset having a specific value being set, a UE being set with a PL offset having a specific value, etc. may be read as interchangeable.

[0310] In relation to the above features 1 to 3, the UE may follow at least one of the following operations / processes.

[0311] < <ul trpからのssbの受信>> The UE may receive (from the base station / DL TRP) a configuration regarding PL offsets for joint TCI states / UL TCI states, and the UE may determine / assume whether to receive SSBs from the UL TRP or the DL TRP based on whether the configuration configures one or more PL offsets for one or more joint TCI states / UL TCI states.

[0312] If the UE is configured with one or more PL offsets for one or more joint TCI states / UL TCI states, the UE may not assume that it will receive SSBs from the UL TRP (see Figure 13A). Otherwise (i.e., if the UE is not configured with one or more PL offsets for one or more joint TCI states / UL TCI states), the UE may assume that it will receive SSBs from the UL TRP (see Figure 13B).

[0313] In this disclosure, not assuming that the UE receives SSBs from the UL TRP may mean that the UE assumes that it receives SSBs from the DL TRP.

[0314] <<Association of Indicated TCI State with Physical Cell ID (PCI)>> When a UE is configured with one or more PL offsets in one or more indicated joint TCI states / indicated UL TCI states in one BWP / component carrier (CC), the UE may not assume that the one or more indicated joint TCI states / indicated UL TCI states are associated with a physical cell ID (PCI) different from the PCI of the serving cell (e.g., the PCI of a non-serving cell).

[0315] If a UE is not configured with a PL offset for an indicated joint TCI state / indicated UL TCI state in a BWP / CC, the UE may assume that the indicated joint TCI state / indicated UL TCI state is associated with a PCI different from the PCI of the serving cell (e.g., the PCI of a non-serving cell).

[0316] In the present disclosure, assuming that the UE does not assume that one or more indicated joint TCI states / indicated UL TCI states are associated with a PCI different from the PCI of the serving cell (e.g., the PCI of a non-serving cell) may mean that the UE assumes that one or more indicated joint TCI states / indicated UL TCI states are associated with the PCI of the serving cell.

[0317] <<Application of Rel.17 Unified TCI Framework>> In relation to the above-mentioned feature 2 / feature 3, a single-TRP inter-cell [Rel.17] unified TCI framework (inter-cell single TRP) may be applied. In this case, the UE may report at least one of the following several pieces of capability information. · Support for the single-TRP inter-cell [Rel.17] unified TCI framework (inter-cell single TRP). · Support for two TAs between cells (e.g., a first TA for a first cell (e.g., a serving cell) and a second TA for a second cell (e.g., a non-serving cell)). · Support that the SSB corresponding to an additional PCI (e.g., the PCI corresponding to a non-serving cell) is the PL-RS of the PRACH.

[0318] According to Embodiment 1 described above, the UE can appropriately determine / judge whether to receive a specific DL signal / channel from the UL TRP. <​​​​​​​​​​

[0321] The new field may be present if at least one of the following conditions is met: The corresponding RRC parameter (for example, the RRC parameter that indicates whether the new field exists or not) is set to enabled. At least one TCI state has a PL offset set.

[0322] The new field may be a 1-bit field that indicates either a first value (for example, 0) [index of] or a second value (for example, 1) [index of].

[0323] When one joint TCI state / UL TCI state in the Rel.17 unified TCI framework is indicated / configured, the first value of the new field may indicate that the PL offset is not included in the calculation of the transmit power of the PRACH. That is, when one joint TCI state / UL TCI state in the Rel.17 unified TCI framework is indicated / configured, the UE may determine / assess that the PL offset is not included (does not use the PL offset) in the calculation of the transmit power of the PRACH based on the first value of the new field.

[0324] When one joint TCI state / UL TCI state in the Rel. 17 unified TCI framework is indicated / configured, the second value of the new field may indicate that the PL offset associated with the one joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH. That is, when one joint TCI state / UL TCI state in the Rel. 17 unified TCI framework is indicated / configured, the UE may determine / assess that the PL offset associated with the one joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH (use the PL offset associated with the one joint TCI state / UL TCI state) based on the second value of the new field.

[0325] When two joint TCI states / UL TCI states (e.g., a first joint TCI state / UL TCI state and a second joint TCI state / UL TCI state) in the Rel. 18 unified TCI framework are indicated / configured, the first value of the new field may indicate that the PL offset associated with the first joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH. That is, when two joint TCI states / UL TCI states in the Rel. 18 unified TCI framework are indicated / configured, the UE may determine / assess that the PL offset associated with the first joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH (use the PL offset associated with the first joint TCI state / UL TCI state) based on the first value of the new field.

[0326] When two joint TCI states / UL TCI states (e.g., a first joint TCI state / UL TCI state and a second joint TCI state / UL TCI state) in the Rel. 18 unified TCI framework are indicated / configured, a second value (e.g., an index of 1) of the new field may indicate that the PL offset associated with the second joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH. That is, when two joint TCI states / UL TCI states in the Rel. 18 unified TCI framework are indicated / configured, the UE may determine / assess that the PL offset associated with the second joint TCI state / UL TCI state is included in the calculation of the transmit power of the PRACH (use the PL offset associated with the second joint TCI state / UL TCI state) based on the second value of the new field.

[0327] Therefore, the new field may be referred to as a field indicating whether a PL offset is included in the calculation of the PRACH transmit power, a field indicating whether a PL offset is used (or applied) in the calculation of the PRACH transmit power, a field indicating the TCI state associated with the PL offset used (or applied) in the calculation of the PRACH transmit power, etc.

[0328] Here, the above-mentioned feature 1 can be used in the intra-cell case (e.g., a multi-DCI-based intra-cell multi-TRP framework, a single-DCI-based intra-cell multi-TRP framework). Also, the above-mentioned feature 3 can be used in both the intra-cell case (e.g., a multi-DCI-based intra-cell multi-TRP framework, a single-DCI-based intra-cell multi-TRP framework) and the inter-cell case (e.g., a multi-DCI-based inter-cell multi-TRP framework, a single-DCI-based inter-cell multi-TRP framework, an inter-cell single-TRP framework). Therefore, in a specific case (e.g., the intra-cell case), feature 1 and feature 3 may be configured simultaneously.

[0329] The new field may be set according to at least one of the following options. Note that the following options are preferably applied when the above-mentioned feature 1 and feature 3 are set simultaneously, but may also be applied in other cases.

[0330] <<Option 1>> The new field and the PRACH-related indicator field may be configured independently. In this case, the new field may be configured by a first RRC parameter, and the PRACH-related indicator field may be configured by a second RRC parameter. The UE may determine whether the new field is included in a specific DCI format based on the first RRC parameter. The UE may determine whether the PRACH-related indicator field is included in a specific DCI format based on the second RRC parameter.

[0331] For example, if both the first RRC parameter and the second RRC parameter are set to disabled, both the new field and the PRACH-related indicator field may not be set. In this case, the new field is 0 bits, and the PRACH-related indicator field is 0 bits, so the total number of bits is 0 bits.

[0332] For example, if the first RRC parameter is set to enabled and the second RRC parameter is set to disabled, the new field may be set and the PRACH-related indicator field may not be set. In this case, the new field is 1 bit and the PRACH-related indicator field is 0 bit, so the total number of bits is 1 bit.

[0333] For example, when the first RRC parameter is set to disabled and the second RRC parameter is set to enabled, the new field may not be set and the PRACH-related indicator field may be set. In this case, the new field is 0 bits and the PRACH-related indicator field is 1 bit, so the total number of bits is 1 bit.

[0334] For example, when both the first RRC parameter and the second RRC parameter are set to enabled, both the new field and the PRACH-related indicator field may be set. In this case, the new field is 1 bit and the PRACH-related indicator field is 1 bit, so the total number of bits is 2 bits.

[0335] <<Option 2>> The new field and the PRACH-related indicator field may be configured by one (common) RRC parameter, and the UE may determine whether the new field and the PRACH-related indicator field are included in a specific DCI format based on one (common) RRC parameter.

[0336] For example, if one RRC parameter is set to disabled, both the new field and the PRACH-related indicator field may not be set. In this case, the new field is 0 bits, and the PRACH-related indicator field is 0 bits, so the total number of bits is 0 bits.

[0337] For example, when one RRC parameter is set to enabled, both the new field and the PRACH-related indicator field may be set. In this case, the new field is 1 bit and the PRACH-related indicator field is 1 bit, so the total number of bits is 2 bits.

[0338] <<Modifications>> The new field and the PRACH-related indicator field may be a common field (a 1-bit field). The common field may be configured by one (common) RRC parameter. The UE may determine whether the common field is included in a specific DCI format based on the one (common) RRC parameter.

[0339] For example, if one RRC parameter is set to disabled, the common field may not be set, in which case the common field is 0 bits.

[0340] For example, if one RRC parameter is set to enabled, the common field may be set, in which case the common field is 1 bit.

[0341] According to Embodiment 2 described above, the UE can appropriately determine / judge the PL offset used for calculating the transmission power of the PDCCH order PRACH based on a specific field in the DCI format.

[0342] <Supplementary> <<Notification of Information to the UE>> Notification of any information from the [network (NW) (for example, base station (BS))] to the UE in the above-described embodiment (in other words, reception of any information from the BS by the UE) may be performed using physical layer signaling (for example, DCI), upper layer signaling (for example, RRC signaling, MAC CE), a specific signal / channel (for example, PDCCH, PDSCH, reference signal), or a combination thereof.

[0343] When the above notification is performed by the MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) not defined in the existing standard in the MAC subheader.

[0344] When the above notification is performed by the DCI, the above notification may be performed by a specific field of the DCI, a radio network temporary identifier (RNTI) used for scrambling the cyclic redundancy check (CRC) bits assigned to the DCI, the format of the DCI, and the like.

[0345] In addition, notification of any information to the UE in the above-described embodiment may be performed periodically, semi-persistently, or aperiodically.

[0346] <<Notification of Information from the UE>> In the above-described embodiments, notification of any information from the UE [to the NW] (in other words, transmission / reporting 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), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

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

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

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

[0350] <<Application of each embodiment>> In a UE / BS, the specific process / operation / control / assumption / information(s) of at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: Upper layer parameters indicating the above specific processing / operation / control / assumment / information are set. The specific processing / action / control / assumption / information is determined based on relevant upper layer parameters; The above specific processes / actions / controls / assumptions / information are specified / activated / triggered by MAC CE / DCI / UCI / resources / channels / RS, Reporting or supporting specific UE capabilities indicating (or relating to) the above specific processes / actions / controls / assumptions / information; · The application of the above specific processing / action / control / assumption / information is judged based on specific conditions.

[0351] The specific UE capabilities may indicate at least one of the following: Supporting the above specific processes / actions / controls / assumptions / information; Support for inter-cell single TRP [2TAs], Supporting specific fields of specific DCI formats (e.g., supporting new / common fields in embodiment 2).

[0352] 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, band, band combination, BWP, 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).

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

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

[0355] (Addendum) The following inventions are noted with respect to one embodiment of the present disclosure (particularly, embodiment 0A). [Appendix 1] a receiver for receiving a Physical Downlink Control Channel (PDCCH) order including a Physical Random Access Channel (PRACH) related indicator field; A terminal having a control unit that determines a bit size of the PRACH-related indicator field based on specific conditions for two timing advances (TAs) in a single transmission / reception point (TRP) between different cells. [Appendix 2] The terminal of Supplementary Note 1, wherein the specific condition is whether a list of unified transmission configuration indication (TCI) states is set and one TCI state is indicated. [Appendix 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit determines that the bit size of the PRACH-related indicator field is 1 bit when a list of unified transmission configuration indication (TCI) states is configured and one TCI state is indicated. [Appendix 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein the control unit determines that the bit size of the PRACH-related indicator field is 0 bits when a list of unified transmission configuration indication (TCI) states is configured, two TCI states are indicated, and at least one of the two TCI states is associated with a physical cell ID (PCI) different from the PCI of the serving cell.

[0356] (Addendum) The following inventions are added regarding one embodiment of the present disclosure (particularly, embodiment 1 and embodiment 2). [Appendix 1] a receiver for receiving a configuration related to a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state; A terminal having a control unit that determines from which transmission / reception point (TRP) to receive a synchronization signal block (SSB) based on the setting. [Appendix 2] The terminal according to Supplementary Note 1, wherein the control unit does not assume that the SSB will be received from a UL TRP when the PL offset is set by the setting. [Appendix 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the control unit does not assume that the joint TCI state or the UL TCI state is associated with a physical cell ID (PCI) different from the PCI of a serving cell when the PL offset is set by the configuration. [Appendix 4] The terminal according to any one of Supplementary Note 1 to Supplementary Note 3, wherein when the PL offset is set by the setting, the control unit determines, based on a specific parameter, whether or not the downlink control information includes a specific field indicating whether or not the PL offset is included in the calculation of the transmission power of a Physical Random Access Channel (PRACH) and a PRACH-related indicator field.

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

[0358] 14 is a diagram illustrating 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), 5th generation mobile communication system New Radio (5G NR), or the like, which are specified by the Third Generation Partnership Project (3GPP).

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

[0360] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN), and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0361] 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 the SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0362] 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 base station 10.

[0363] 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 super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

[0367] The multiple base stations 10 may be connected by wire (for example, optical fiber conforming to the Common Public Radio Interface (CPRI), an X2 / Xn interface, etc.) or wirelessly (for example, 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.

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

[0369] The core network 30 may include network functions (NFs) 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 an Operation, Administration and Maintenance (Management) (OAM). Note that a single network node may provide multiple functions. Furthermore, communication with an external network (e.g., the Internet) may be performed via the DN.

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

[0371] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the radio 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).

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

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

[0374] 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)), etc. may be used as an uplink channel.

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

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

[0377] 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 an UL grant, a UL DCI, etc. Note that the PDSCH may be interpreted as DL data, and the PUSCH may be interpreted as UL data.

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

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

[0380] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), acknowledgement 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.

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

[0382] 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, 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 as DL-RS.

[0383] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including the SS (PSS, SSS) and the PBCH (and 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 reference signals.

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

[0385] (base station) 15 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.

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

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

[0388] 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 to be transmitted as signals, control information, sequences, etc., 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.

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

[0390] The transmitting / receiving unit 120 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 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0391] 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 pertains, such as an array antenna.

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

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

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

[0395] The transceiver 120 (transmission processor 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.

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

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

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

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

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

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

[0402] 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 perform 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 perform higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may perform PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0403] In the present disclosure, the base station 10 may include a single device that implements all of the functions of the RU, DU, and CU, or may include multiple devices that each implement 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.

[0404] The transceiver 120 may transmit a Physical Downlink Control Channel (PDCCH) order that includes a Physical Random Access Channel (PRACH) associated indicator field.

[0405] The controller 110 may determine the bit size of the PRACH-related indicator field based on specific conditions for two timing advances (TAs) in a single transmission / reception point (TRP) between different cells.

[0406] The transceiver 120 may transmit a configuration for a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state.

[0407] The control unit 110 may determine from which transmission / reception point (TRP) to transmit the synchronization signal block (SSB) based on the setting.

[0408] (user terminal) 16 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.

[0409] Note that this example mainly shows functional blocks of the characteristic parts of the present embodiment, 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.

[0410] 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, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0411] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also 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.

[0412] 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 from 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.

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

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

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

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

[0417] The transceiver 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.

[0418] The transceiver 220 (transmission processor 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.

[0419] 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 when transform precoding is not enabled, the transceiver unit 220 may not perform DFT processing as the transmission processing.

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

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

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

[0423] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, 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.

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

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

[0426] The transceiver 220 may receive a Physical Downlink Control Channel (PDCCH) order that includes a Physical Random Access Channel (PRACH) associated indicator field.

[0427] The control unit 210 may determine the bit size of the PRACH-related indicator field based on specific conditions for two timing advances (TAs) in a single transmission / reception point (TRP) (e.g., inter-cell single TRP) between different cells (e.g., a first cell and a second cell).

[0428] The specific condition may be whether a list of unified transmission configuration indication (TCI) states (e.g., dl-OrJointTCI-StateList or ul-TCI-StateList) is set and one TCI state is indicated.

[0429] The control unit 210 may determine that the bit size of the PRACH-related indicator field is 1 bit when a list related to a unified transmission configuration indication (TCI) state (e.g., dl-OrJointTCI-StateList or ul-TCI-StateList) is set and one TCI state is indicated.

[0430] The control unit 210 may determine that the bit size of the PRACH-related indicator field is 0 bits if a list of unified transmission configuration indication (TCI) states (e.g., dl-OrJointTCI-StateList or ul-TCI-StateList) is configured, two TCI states are indicated, and at least one of the two TCI states is associated with a physical cell ID (PCI) different from the PCI of the serving cell (e.g., the PCI of a non-serving cell).

[0431] The transceiver 220 may receive configuration for a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state.

[0432] The control unit 210 may determine from which transmission / reception point the synchronization signal block (SSB) is to be received based on the setting.

[0433] When the PL offset is set by the setting, the control unit 210 may not assume that the SSB will be received from an uplink TRP.

[0434] When the PL offset is set by the setting, the control unit 210 may not assume that the joint TCI state or the UL TCI state is associated with a physical cell ID (PCI) different from the PCI of the serving cell (e.g., the PCI of a non-serving cell).

[0435] When the PL offset is set by the setting, the control unit 210 may determine, based on a specific parameter, whether the downlink control information includes a specific field indicating whether the PL offset is included in the calculation of the transmission power of a physical random access channel (PRACH) and a PRACH-related indicator field.

[0436] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. 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 also be realized by combining the single device or multiple devices with software.

[0437] 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 mentioned above, the implementation method of each is not particularly limited.

[0438] 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. Fig. 17 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.

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

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

[0441] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined 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.

[0442] 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), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0443] 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 realized by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be realized in a similar manner.

[0444] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

[0445] Storage 1003 is a computer-readable recording medium and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact 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, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as a secondary storage device.

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

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

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

[0449] 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 such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0450] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

[0451] (Variation) Note that terms explained 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.

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

[0453] 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, a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), the number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in the frequency domain, and a specific windowing process performed by a transceiver in the time domain.

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

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

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

[0457] 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 a subframe and a 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.

[0458] 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. However, the definition of TTI is not limited to this.

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

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

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

[0462] 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 equal to or greater than 1 ms.

[0463] 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 also be determined based on numerology.

[0464] 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. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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

[0467] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a 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 given BWP and numbered within that BWP.

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

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

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

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

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

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

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

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

[0476] 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 / identifying (or relating to) the value of the any information.

[0477] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, 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.

[0478] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called 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).

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

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

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

[0482] 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), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0484] In the present 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.

[0485] 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. The spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

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

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

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

[0489] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

[0491] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interchangeable. "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 TCI may be interchangeable. The spatial relationship information and spatial relationship may be interchangeable.

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

[0493] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

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

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

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

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

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

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

[0500] 18 is a diagram showing an example of a vehicle according to an embodiment. 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.

[0501] 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 the user.

[0502] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (e.g., 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).

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

[0504] 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 (for example, multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0506] The driving assistance system unit 64 is configured with various devices that provide functions for preventing accidents and reducing 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.

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

[0508] 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 above-mentioned base station 10 or user terminal 20. Furthermore, the communication module 60 may be, for example, at least one of the above-mentioned base station 10 and user terminal 20 (or may function as at least one of the base station 10 and user terminal 20).

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

[0510] The communication module 60 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices 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)).

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

[0512] 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 uplink channel and downlink channel may be read as sidelink channel.

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

[0514] 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) and a Serving-Gateway (S-GW)), or a combination thereof.

[0515] 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 specific order presented.

[0516] 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 The present invention may be applied to systems that use 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

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

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

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

[0521] 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 action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

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

[0523] 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 ...," "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ...," "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).

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

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

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

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

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

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

[0530] 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 the prefix "i-th" (i is any integer) (for example, "highest" may be interchangeable as "i-th highest").

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

[0532] 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 nearly zero (immediately after or immediately before). A time offset may be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after the 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.

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

[0534] 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 receiver for receiving a configuration related to a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state; A terminal having a control unit that determines from which transmission / reception point (TRP) to receive a synchronization signal block (SSB) based on the setting.

2. The terminal according to claim 1 , wherein the control unit does not assume that the SSB will be received from an UL TRP when the PL offset is set by the setting.

3. The terminal according to claim 1 , wherein the control unit does not assume that the joint TCI state or the UL TCI state is associated with a physical cell ID (PCI) different from a PCI of a serving cell when the PL offset is set by the configuration.

4. 2. The terminal according to claim 1, wherein, when the PL offset is set by the setting, the control unit determines, based on a specific parameter, whether the downlink control information includes a specific field indicating whether the PL offset is included in calculation of a transmission power of a physical random access channel (PRACH) and a PRACH-related indicator field.

5. receiving a configuration for a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state; A wireless communication method for a terminal, comprising: a step of determining from which transmission / reception point (TRP) a synchronization signal block (SSB) is to be received based on the setting.

6. a transmitter for transmitting a configuration related to a path loss (PL) offset for a joint transmission configuration indication (TCI) state or an uplink (UL) TCI state; A base station having a control unit that determines from which transmission / reception point (TRP) to transmit a synchronization signal block (SSB) based on the setting.

Images