Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure has: a reception unit that receives a configuration relating to 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, on the basis of the configuration, a transmission / reception point (TRP) from which a synchronization signal block (SSB) is received. According to one aspect of the present disclosure, it is possible to suitably control UL transmission / DL reception even when DL sTRP / UL mTRP is applied.

Description

Terminal, Wireless Communication Method, and Base Station

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

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was specified for the purpose of achieving higher data rates, lower latency, etc. (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) was specified for the purpose of further increasing capacity and enhancing performance of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Release (Rel.) 8, 9).

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

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

[0005] In future wireless communication systems, it is being considered to apply the Downlink single transmission / reception point (DL sTRP) / Uplink multi transmission / reception point (UL mTRP) scenario.

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

[0007] Therefore, one of the objectives of this 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.

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

[0009] According to one aspect of this disclosure, UL transmission / DL reception can be appropriately controlled.

[0010] Figure 1A shows an example of a typical transmit / receive point arrangement. Figure 1B shows an example of a UL high-density arrangement. Figure 2 shows an example of DL / UL coverage for a Heterogeneous Network (HetNet). Figure 3 shows an example of setting TAGs for cells. Figures 4A and 4B show examples of MAC CE for timing advance commands. Figure 5A shows an example of associating RS index with PL value. Figure 5B shows an example of associating RS index with delta PL value. Figure 6 shows an example of option 1 in a UL high-density arrangement. Figure 7 shows an example of option 2 in a UL high-density arrangement. Figure 8 is a conceptual diagram showing an example of an asymmetric DL sTRP / UL mTRP arrangement scenario. Figure 9 is a conceptual diagram showing an example of SRS transmission. Figure 10 shows an example of SRS configuration. Figures 11A and 11B show examples of TPC command (DCI) fields. Figure 12 shows an example of a method for determining the bit size of a PRACH-related indicator field. Figures 13A and 13B show an example of SSB reception from a UL TRP. Figure 14 shows an example of a schematic configuration of a wireless communication system according to one embodiment. Figure 15 shows an example of a base station configuration according to one embodiment. Figure 16 shows an example of a user terminal configuration according to one embodiment. Figure 17 shows an example of the hardware configuration of a base station and user terminal according to one embodiment. Figure 18 shows an example of a vehicle according to one embodiment.

[0011] (Scenario 1: UL high-density configuration (UL only TRP)) In Rel. 15 NR, the coverage (range) of PUSCH, PUCCH, PRACH, PDSCH, PDCCH, and PBCH is not uniform. PUSCH coverage is particularly limited at high frequencies. Future wireless communication systems (e.g., Rel. 18, Rel. 19, or later) are being considered to improve at least one of UL coverage and UL throughput.

[0012] To expand UL coverage, the addition of UL receiving points in addition to general transmit / receive points is being considered. Therefore, examples of general transmit / receive point arrangements and arrangements with UL receiving points (UL high-density arrangement) are described below.

[0013] Figure 1A shows an example of a typical transmission and reception point arrangement. In Figure 1A, the UE receives a DL signal from the transmission / reception point (TRP) and transmits a UL signal to the TRP. For example, if the UE and TRP are far apart, path loss may be large, potentially degrading communication quality.

[0014] Figure 1B shows an example of a high-density UL (ultraluminescence) arrangement. To expand UL coverage, it is being considered to provide UL receiving points as shown in Figure 1B, in addition to TRPs (DL transmission points) as shown in Figure 1A. In Figure 1B, the UE receives DL signals from DL transmission points (TRP / central TRP / DL TRP) corresponding to macrocells and transmits UL signals to UL receiving points (e.g., receiving points with lower path loss / received power). However, the UE can also perform UL transmission to DL transmission points.

[0015] By using a high-density UL configuration as shown in Figure 1B, compared to a general configuration as shown in Figure 1A, both coverage and UL data rate can be improved by reducing path loss, improving UL signaling quality, and achieving a higher coding rate. Furthermore, since UL receiving points primarily perform reception, they require fewer functions (such as power amplifiers) compared to transmitting and receiving points corresponding to typical small cells, resulting in lower costs and significantly easier deployment management.

[0016] (Scenario 2: Decoupling of DL TRP and UL TRP in HetNet) In this disclosure, a Heterogeneous Network (HetNet) using macro Base Stations (BS) (DL TRP) and micro BS (UL TRP) may be applied (Figure 2). In a typical HetNet, the transmit power of the macro BS and micro BS are 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 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 from the macro BS and transmit UL to the micro BS. However, the UE may transmit some reference signals / channels (e.g., SRS with usage Antenna switching (AS) used for acquiring DL CSI) to the macro BS. Therefore, the UE may require two Timing Advances (TA) in this scenario. Note that the SRS with AS is transmitted to the macro BS because it is used to enable the base station (macro BS) to perform DL CSI measurement (e.g., determine the MIMO precoder of the DL) based on the reception of the SRS using the channel reciprocity. On the other hand, the SRS with usage Codebook / Non-codebook is transmitted to the micro BS because it is used for PUSCH precoder / beam determination.

[0018] In HetNet, even if a microBS has DL transmission capabilities, turning off DL for most of the time can conserve energy on the microBS. In this case, the microBS functions similarly to a UL-only TRP (UL receiving point).

[0019] (Timing Advance) Timing Advance (TA) is used for UL timing adjustment. Up to the existing specification (Rel. 17), the UL frame number i for transmission from the UE starts a specific time (e.g., T ＴＡ ) before the start of the corresponding DL frame.

[0020] The specific time may be, 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 the present disclosure when used in NTN (Non-Terrestrial Network).

[0021] Here, N TA is the timing advance between DL and UL, N TA,offset is the fixed offset used for calculating the timing advance, N common TA,adj is the network-controlled timing correction value, N UE TA,adj is the UE-derived timing correction value, T Ｃ is the basic time unit for NR (Basic time unit for NR), respectively.

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

[0023] (Timing Advance Group) When using multiple TRPs, there may be cases where the distance between the UE and each TRP is different. Multiple TRPs may be included in the same cell (e.g., a serving cell). Alternatively, among the multiple TRPs, one TRP may correspond to a serving cell and the others to non-serving cells. Multiple TRPs may include DL transmission points and UL reception points. In this case, it is conceivable that the distance between each TRP and the UE may be different.

[0024] In existing systems, the transmission timing of UL (Uplink) channels and / or UL signals (UL channels / signals) is adjusted by Timing Advance (TA). The reception timing of UL channels / signals from different user terminals (UEs) is adjusted at the base station (TRP: Transmission and Reception Point, also known as gNodeB, etc.).

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

[0026] When applying multiple timing advances, Timing Advance Groups (TAGs) are supported, categorized by transmission timing. 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 applying Multiple Timing Advance, the UE can independently adjust the transmission timing of the cells belonging to each TAG, allowing the radio base station to synchronize the uplink signal reception timing from the UE, even when using multiple cells.

[0028] TAGs (for example, serving cells belonging to the same TAG) may be set by higher-level layer parameters. The same timing advance value may be applied to serving cells belonging to the same TAG (for example, serving cells to which UL is set). A timing advance group containing a MAC entity's SpCell may be called a primary timing advance group (PTAG), and other TAGs may be called secondary timing advance groups (STAG). The maximum number of TAGs may also be X (for example, X=4) per cell group (for example, MCG / SCG).

[0029] In existing systems (e.g., Rel. 16 NR), the setting of up to four TAGs is supported for each cell group (e.g., MCG / SCG) (see Figure 3). Figure 3 shows a case where three TAGs are set for a cell group containing SpCell and SCell #1 to #4. Here, 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 belong to the third TAG (TAG #2).

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

[0031] A MAC CE for timing advance commands may include a field for the timing advance group index (e.g., TAG ID) and a field for the timing advance command (see Figure 4A). This MAC CE may consist of one octet (= 8 bits).

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

[0033] Figure 4B shows another example of a MAC CE for timing advance commands. The MAC CE shown in Figure 4B may also be called an absolute TAC MAC CE. The MAC CE may consist of two octets (= 16 bits). Specifically, the MAC CE may include a field for reserve bits (R bit field) and a field for timing advance commands (TAC field). The R bit field (R=0) may consist of, for example, 4 bits. The TAC field may span two octets and consist of, for example, 12 bits. The TAC field in Figure 4B may show an index value used to control the actual amount / value (absolute amount / absolute value) of TA that the MAC entity must apply, similar to Figure 4A. Also, the absolute TAC MAC CE does not have to include the TAG ID field shown in Figure 4A.

[0034] The MAC CE shown in Figure 4A may be used after initial access has been established. On the other hand, the MAC CE shown in Figure 4B is used only during initial access and may include RAR, etc. Each field included in the MAC CE for the timing advance command described above may be called a field related to TA. Among these, the TAC field shown in Figure 4A may be called a TA adjustment field / field for instructing TA adjustment / field related to TA adjustment, and the TAC field shown in Figure 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 higher-layer parameters. For example, a parameter such as a time alignment timer (e.g., timeAlignmentTimer) may be set for each TAG ID. Alternatively, the TAG ID for each serving cell may be set by higher-layer parameters (e.g., tag-ID included in ServingCellConfig). Note that the TAG ID / parameter may be updated by MAC CE after being set by higher-layer parameters.

[0036] Time alignment timers may be maintained for UL time alignment. In Rel. 17, time alignment timers may be set / associated for each 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 timers associated with the indicated timing advance group (e.g., TAG).

[0037] The MAC entity receives a TAC MAC CE and a predetermined value (N) between it and the instructed TAG. ＴＡ If the specified value (N) is maintained, apply the timing advance command to the specified TAG, or start or restart the time alignment timer associated with the specified TAG. ＴＡ ) may also be a timing advance between DL and UL.

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

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

[0040] For example, if the time alignment timer expires, the following actions (e.g., a predetermined PTAG action / a predetermined STAG action) may be performed.

[0041] [Specific PTAG Operation] If the time alignment timer is associated with the PTAG: - Flushes all HARQ buffers for all serving cells. - Notifies the RRC to release PUCCH for all serving cells, if configured. - Notifies the RRC to release SRS, if configured. - Clears all configured DL and UL allocations. - Clears PUCCH resources for semi-persistent CSI reporting. - Allows all running time alignment timers to expire. - N for all TAGs ＴＡ Maintain.

[0042] [Operation for a specified STAG] If a time alignment timer is associated with a STAG, for all serving cells belonging to that TAG: - Flushe all HARQ buffers. - Notify RRC to release PUCCH if configured. - Notify RRC to release SRS if configured. - Clear all configured DL and UL allocations. - Clear PUCCH resources for semi-persistent CSI reporting. - Clear N of the TAG ＴＡ Maintain.

[0043] (PRACH-related indicators of Rel. 18) PRACH-related indicators consist of 0 or 1 bit. In this disclosure, PRACH-related indicators, PRACH-related indicator fields, etc., may be interpreted as interchangeable.

[0044] The PRACH-related indicator is 1 bit if the following conditions are met: - When the UE provides specific parameters (tag-Id2 and SSB-MTC-AdditionalPCI); - When the UE does not provide coresetPoolIndex, or provides coresetPoolIndex (value = 0) for the first CORESET; - When provides coresetPoolIndex (value = 1) for the second CORESET.

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

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

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

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

[0049] If none of the above conditions are met (otherwise), the PRACH-related indicator is 0 bits.

[0050] (Reference signal power in PRACH transmission of Rel. 18) The UE provides the parameter referenceSignalPower for reference signal power by the corresponding parameter ss-PBCH-BlockPower if at least one of the following conditions is met:

[0051] When a PRACH transmission from a 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 the DL RS that is QCL'd, then at least one of the following conditions is met: • No PRACH-related indicator exists in the PDCCH order; • No cell indicator field exists in the PDCCH order, or the value of the field is 0; • The value of the PRACH-related indicator field in the PDCCH order is 0 when the UE has not provided SSB-MTC-AdditionalPCI; • The PRACH-related indicator field in the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order, or depends on the indicated SS / PBCH block; • The PRACH transmission is sent in a non-serving cell indicated by the cell indicator field in the PDCCH order. - When the UE does not provide SSB-MTC-AdditionalPCI, and the value of the PRACH-related indicator field in the PDCCH order is 1. - When the PRACH-related indicator field in the PDCCH order indicates a physCellId that is different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

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

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

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

[0055] [Option 2] The relative path loss (delta PL) value [dB] for each RS index may be notified (transmitted) from the network 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 macrocell (macro BS / central TRP) to calculate the transmit power.

[0056] In options 1 and 2, the PL value / Delta PL value is q ｄ Notifications / settings may be made for each index of / SSB / CSI-RS / SRS Resource / SRS Resource Set. DL signaling may notify one or more RS indexes and the PL value / Delta PL value corresponding to each RS index. PL value / Delta PL value may be interpreted as PL parameter / Delta PL parameter.

[0057] Figure 5A shows an example of the association between an RS index and a PL value. Figure 5B shows an example of the association between an RS index and a delta PL value. The association (correspondence) between an RS index and a PL value / delta PL value is not limited to Figures 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 defined in advance in the specification. 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 configuration. The UL receiving point receives / measures the UL signal. If the DL transmitting point (macro TRP / gNB) knows the transmission power of this UL signal, the DL transmitting point can know the exact PL value of the UL receiving point. In this case, the DL transmitting point can notify the UE of the absolute PL value (X [dB]) of the UL receiving point.

[0059] Figure 7 shows an example of Option 2 in a UL high-density configuration. When both the DL transmit point (macro TRP / gNB) and the UL receive point measure the same resource, the DL transmit point can recognize the difference between the PL between the DL transmit point and the UE and the PL between the UL receive point and the UE. In this case, the DL transmit point may notify the UE of this difference (relative PL / delta PL). The relative PL / delta PL may also be called the PL offset.

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

[0061] (Unified / Common TCI Framework) According to the Unified TCI Framework, multiple types of channels / RS (UL / DL) can be controlled by a common framework. The Unified TCI Framework does not define TCI states or spatial relationships for each channel, as in Rel. 15, but may specify a common beam (common TCI state) and apply it to all UL and DL channels, or 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 a common beam for DL ​​and a common beam for UL (two common beams in total) are being considered.

[0063] UE may assume the same TCI state (joint TCI state, joint TCI pool, joint common TCI pool, joint TCI state set) for UL and DL. Alternatively, UE may assume different TCI states for UL and DL respectively (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 by beam management based on MAC CE (MAC CE level beam instruction). Alternatively, the default TCI status of PDSCH may be updated to match 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 MAC CE. UL / DL DCI may select one from the X active TCI states. The selected TCI state may be applied to both UL and DL channels / RS.

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

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

[0068] The RRC parameter (information element) sets up multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the set up TCI states. DCI may indicate one of the activated TCI states. DCI may be a UL / DL DCI. The indicated TCI state may be applied 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, one point may be a single TCI state that applies to both UL and DL, or it may be two TCI states that apply to UL and DL respectively.

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

[0071] In this disclosure, the higher-layer parameters (RRC parameters) that set up multiple TCI states may also be referred to as setting information that sets up multiple TCI states, or simply as "setting information." Furthermore, in this disclosure, being instructed to select one of multiple TCI states using DCI may mean receiving instruction information that instructs one of the multiple TCI states included in DCI, or simply receiving "instruction information."

[0072] The RRC parameter sets up multiple TCI states (joint common TCI pools) for both DL and UL. MAC CE may activate multiple TCI states (active TCI pools) from among the set up TCI states. Separate active TCI pools for UL and DL may be set up / activated.

[0073] A DL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) DL channels / RSs. 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. A UL DCI, or a new DCI format, may select (instruct) one or more (e.g., one) TCI states. The selected TCI state may be applied to one or more (or all) UL channels / RSs. UL channels may be PUSCH / SRS / PUCCH. Thus, different DCIs may instruct UL TCI and DL DCI separately.

[0074] From Rel. 17 NR onward, MAC CE / DCI is expected to support beam activation / instruction to TCI states associated with different physical cell identifiers (PCIs). Furthermore, from Rel. 18 NR onward, MAC CE / DCI is expected to support instruction to change serving cells to cells with different PCIs.

[0075] [SRS to which the indicated TCI state in Rel. 17 applies] The indicated TCI state by MAC CE / DCI may apply to SRSs that satisfy the following conditions: The indicated TCI state applies to SRS resource sets for beam management applications (A-SRS) and codebook (CB) / non-codebook (NCB) / antenna switching applications (A / SP / P-SRS) if they are configured to follow a unified TCI state. For other SRSs, the configured TCI state within their SRS resource set applies.

[0076] [SRS to which the indicated TCI state in Rel. 18 applies] When single DCI multi-TRP is applied, the indicated TCI state may be applied to SRS that satisfy the following conditions. Note that applyIndicatedTCIState={1st,2nd,both} in the following description is a parameter that indicates that the first TCI state, the second TCI state, or both the first and second TCI states will be applied. • For SRS resource sets for A-SRS whose application is beam management and A / SP / P-SRS whose application is codebook (CB) / non-codebook (NCB) / antenna switching, if it is set to follow a unified TCI state, applyIndicatedTCIState={1st,2nd,both} is set for each SRS resource set to indicate that the indicated TCI state will be applied. For other SRS, the configured TCI state within that SRS resource set will be applied.

[0077] In this disclosure, the terms "indicator TCI state," "unified TCI state," "TCI state applied to a channel / signal configured to conform to a unified TCI state," "TCI state applied to UE individual PDSCH and CORESET / PDCCH associated with USS," and "TCI state applied to PUCCH and PUSCH" may be interpreted interchangeably.

[0078] (SRS Transmit Power Control) Using the power control adjustment state (closed-loop state) index l, the SRS transmit power (P) during the SRS transmission occasion (also called the transmission period, etc.) i for the active UL BWP b of the carrier f of serving cell c is determined. ＳＲＳ、ｂ，ｆ，ｃ (i, q ｓ ,l)) is P ＣＭＡＸ，ｆ，ｃ (i), P Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), M ＳＲＳ，ｂ，ｆ，ｃ (i), α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ), PL ｂ，ｆ，ｃ (q ｄ ), h ｂ，ｆ，ｃ Based on (i, l), it is given by the following equation.

[0079]

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

[0081] Here, P ＣＭＡＸ，ｆ，ｃ (i) is, for example, the maximum UE output power for the carrier f of the serving cell c in an SRS transmission opportunity i. Ｏ＿ＳＲＳ，ｂ，ｆ，ｃ (q ｓ ) is the active UL BWP b of the carrier f of serving cell c and the SRS resource set q ｓ These are parameters related to the target received power (also known as parameters related to the transmit power offset, transmit power offset P0, or target received power parameters, etc.) provided by p0 for (provided by SRS-ResourceSet and SRS-ResourceSetId).

[0082] M ＳＲＳ，ｂ，ｆ，ｃ (i) is the SRS bandwidth expressed as the number of resource blocks for SRS transmission opportunities i on the active UL BWP b of serving cell c and carrier f with subcarrier spacing μ.

[0083] α ＳＲＳ，ｂ，ｆ，ｃ (q ｓ) is an active UL BWP b of the serving cell c and carrier f with subcarrier spacing μ, and an SRS resource set q ｓ This is provided by α (e.g., alpha) for , where α (e.g., alpha) may be defined as a path loss compensation coefficient for UL power control.

[0084] PL ｂ，ｆ，ｃ (q ｄ ) is the active DL BWP of serving cell c and SRS resource set q ｓ And, in contrast, RS resource index q ｄ This is the DL path loss estimate [dB] (path loss estimate [dB], path loss compensation) calculated by UE using the RS resource index q. ｄ is SRS resource set q ｓ It is an associated path loss reference RS (provided by pathlossReferenceRS, pathloss(PL)-RS, pathlossMeasurementDL-RS, e.g., pathlossReferenceRS), and is an SS / PBCH block index (e.g., ssb-Index) or a CSI-RS resource index (e.g., csi-RS-Index).

[0085] If the UE is not provided with pathlossReferenceRSs, or before the UE is provided with individual higher-layer parameters, the UE uses the RS resources obtained from the SS / PBCH block that the UE uses to obtain the MIB to perform PL ｂ，ｆ，ｃ (q ｄ ) calculate.

[0086] h ｂ，ｆ，ｃ (i, l) is the SRS power control adjustment state for the active UL BWP of the carrier f of serving cell c during an SRS transmission opportunity i. If the SRS power control adjustment state setting (e.g., srs-PowerControlAdjustmentStates) indicates the same power control adjustment state for SRS transmission and PUSCH transmission, then the current PUSCH power control adjustment state f is... ｂ，ｆ，ｃ(i, l). On the other hand, if the setting of the SRS power control adjustment state indicates an independent power control adjustment state for SRS transmission and PUSCH transmission, the SRS power control adjustment state h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ (m) may also be used as a basis.

[0087] If TPC accumulation is enabled, h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ It may also be based on the cumulative value of (m).

[0088] If TPC accumulation is invalid, h ｂ，ｆ，ｃ (i) is δ ＳＲＳ，ｂ，ｆ，ｃ (i) The absolute value may also be used.

[0089] Here, δ ＳＲＳ，ｂ，ｆ，ｃ (m) may be a TPC command value encoded in combination with other TPC commands within a PDCCH having DCI (e.g., DCI format 2_3). Σ m=0 C(Si)-1 δ SRS,b,f,c (m) is on the active UL BWP b of the serving cell c and carrier f with subcarrier spacing μ, SRS transmission opportunity i-i ０ K ＳＲＳ (i-i ０ )-1 symbol before and K of SRS transmission opportunity i ＳＲＳ (i) The cardinality C(S) that the UE receives between the symbol and the symbol. ｉ A set of TPC command values ​​S that have ) ｉ The sum of the TPC commands within may also be used. Here, i ０ is SRS transmission opportunity i-i ０ K ＳＲＳ (i-i ０ ) - 1 symbol before, SRS transmission opportunity i K ＳＲＳ (i) The smallest positive integer that is faster than the symbol before it.

[0090] If SRS transmission is aperiodic, K SRS(i) may be the number of symbols in the active UL BWP b of the 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 in the active UL BWP b of the carrier f of serving cell c, N symb slot The product of the minimum value of the k2 in the PUSCH Common Configuration Information (PUSCH-ConfigCommon) and K is equal to the product of the minimum value of the k2 and in the PUSCH Common Configuration Information (PUSCH-ConfigCommon). SRS,min It could also be the number of symbols.

[0091] (DCI Format 2_3) DCI Format 2_3 is used to send a group of TPC commands for SRS transmission by one or more UEs. An SRS request may also be sent along with the TPC commands.

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

[0093] If the UE has set the upper layer parameter srs-TPC-PDCCH-Group=typeA for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control, the upper layer sets a block in the UE, and that block defines the following fields: • SRS request: 0 or 2 bits. If this field exists, 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 the respective UL carrier, provided by the upper layer parameter cc-IndexInOneCC-Set.

[0094] If the UE is configured with the upper 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, the upper layer configures the UE with one or more blocks, each block of which is applied to the UL carrier, and defines the following fields for each block: • SRS Request: 0 or 2 bits. If this field exists, it is interpreted according to a specific table. • TPC Command: 2 bits.

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

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

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

[0098] (2) The index of the serving cell from which the UE will interrupt transmission in order to send SRS in one or more other serving cells, as specified by the parameter srs-SwitchFromServCellIndex.

[0099] (3) An instruction by the parameter srs-SwitchFromCarrier for an uplink carrier on which the UE will interrupt transmission in order to transmit SRS on one or more other serving cells.

[0100] (4) DCI format 2_3 field setting type by type A or type B. In type A, the index of the serving cell set is provided by cc-SetIndex, the index of the serving cells within 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 type B, the DCI format 2_3 field includes a TPC command for the serving cell index and may also include an SRS request for SRS transmission on the serving cell.

[0101] (5) An instruction to the serving cell indicating whether the DCI format 2_3 field contains an SRS request in fieldTypeFormat2-3. A value of 0 or 1 in this instruction indicates the absence or 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) An 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, according to startingBitOfFormat2-3.

[0103] (7) An index for the position in DCI Format 2_3 of the first bit of the field for the supplemental uplink carrier of the serving cell, according to startingBitOfFormat2-3SUL-v1530.

[0104] Note that in existing specifications (up to Rel. 18), startingBitOfFormat2-3 / startingBitOfFormat2-3SUL-v1530 is defined as an integer between 1 and 31.

[0105] (Two Closed Loop Power Control (CL-PC) adjustment states for PUSCH) The higher-level parameter for PUSCH power control (PUSCH-PowerControl) includes the size of twoPUSCH-PC-AdjustmentStates and sri-PUSCH-PowerControlId. The higher-level parameter for SRI-PUSCH power control (SRI-PUSCH-PowerControl) includes sri-PUSCH-PowerControlId and sri-PUSCH-ClosedLoopIndex. If twoPUSCH-PC-AdjustmentStates is set, the UE may set l = {0, 1} in sri-PUSCH-ClosedLoopIndex.

[0106] sri-PUSCH-ClosedLoopIndex applies only to PUSCH. The UE determines whether the closedLoopIndex of a 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 are configured with usage = CB / NCB, each SRS resource set corresponds to l = {0, 1}. That is, one SRS resource set corresponds to l = 0, and the other SRS resource set corresponds to l = 1.

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

[0109] Furthermore, regardless of the above cases, UE may apply a unique (different from PUSCH) CL-PC tuning state to SRS. Here, a new index k = {0, 1} may be introduced to indicate a CL-PC tuning state specific to SRS that is different from PUSCH.

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

[0111] (Asymmetric DL sTRP / UL mTRP Placement Scenario) In this disclosure, when extending the asymmetric DL sTRP / UL mTRP placement scenario, the following may be assumed: - No changes to existing cell definitions. - No need for new cell definitions (e.g., UL-only cells). - Unified TCI framework (Rel. 17 / 18). - Use of existing QCL / UL space relationship provisions. - Targeting FR1 / FR2.

[0112] (Conceptual Scenarios) The following scenarios may be assumed in this disclosure: - A UE receives a DL signal (including, for example, PL-RS) from one DL TRP. - A 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 configuration scenario. As shown in Figure 8, the UE receives a DL signal from one DL TRP. The UE may also transmit UL signals to that DL TRP / multiple UL TRPs (UL TRP #1 / #2). In this case, the UE may dynamically switch which TRP to which it transmits the UL signal, for example, according to the indicated TCI state.

[0114] (Unified TCI Framework) In this disclosure (in the asymmetric DL sTRP / UL mTRP deployment scenario), the Unified TCI Framework for Rel. 17 / 18 may be supported. The supported scenarios (intra-cell / inter-cell) are exemplified below.

[0115] <In-cell scenarios> - A unified TCI for single TRP (Rel. 17) may be supported for only one UL TRP. - A unified TCI for single DCI multi-TRP (Rel. 18) may be supported for multiple UL TRPs. - A unified TCI for multi-DCI multi-TRP (Rel. 18) may not be supported.

[0116] <Inter-cell scenarios> - The unified TCI for single TRP (Rel. 17) may be supported in inter-cell scenarios (Inter cell beam management (ICBM) of Rel. 17). - The unified TCI for single DCI multi-TRP (Rel. 18) does not need to be supported. - The unified TCI for multi-DCI multi-TRP (Rel. 18) may be supported for inter-cell multi-TRP of Rel. 17.

[0117] (DCI Format 2_3) As mentioned above, DCI Format 2_3 may be used only for SRS carrier switching. For example, DCI Format 2_3 may be used under the following conditions:

[0118] <Condition 1> The UE is set to the upper layer parameter srs-TPC-PDCCH-Group=typeA for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control. <Condition 2> The UE is set to the upper layer parameter srs-TPC-PDCCH-Group=typeB for ULs that do not have PUCCH and PUSCH, or for ULs where SRS power control is not associated with PUSCH power control.

[0119] Alternatively, <Condition A> Carrier switching without PUCCH / PUSCH on the carrier. <Condition B> Carrier switching with a power control adjustment state set that is different from PUSCH (independent / individual) for the SRS.

[0120] Furthermore, DCI format 2_3 may be used for any purpose, not just in the case of SRS carrier switching. 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 specification of Rel. 18, when srs-PowerControlAdjustmentStates = separateClosedLoop is set, there is only one closed-loop power control (CL-PC) adjustment state for the SRS, separate from PUSCH. This CL-PC adjustment state can be controlled by DCI format 2_3.

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

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

[0124] In other words, the upper-layer parameter srs-PowerControlAdjustmentStates may indicate which CL-PC adjustment state to follow when the SRS follows the CL-PC adjustment state of the PUSCH, and there are two CL-PC adjustment states for the PUSCH.

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

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

[0127] Regardless of the settings related to PUSCH and the settings for SRS carrier switching, UE can be configured with multiple (two) CL-PC adjustment states separate from PUSCH.

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

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

[0130] UE may send SRS#2 to UL TRP#2 with the same CL-PC adjustment state (l=1) as PUSCH#2.

[0131] The UE may also transmit SRS#3 to DL TRP by applying a first CL-PC adjustment state (k=0) that is different from (independent of) PUSCH. The UE may then transmit the UL (SRS#3) to obtain DL CSI.

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

[0133] In the transmission of SRS#4, any direction may mean a predetermined angular range (for example, 180 degrees or 360 degrees) in which a certain TRP is assumed to exist. The UE may transmit multiple beams for BM in that any direction. The SRS for BM may be used for SRS-based beam sweeping.

[0134] Thus, the UE may set multiple (two) CL-PC adjustment states (l=0,1) for SRS (#1 to #2) as in PUSCH, and set a different CL-PC adjustment state (k=0,1) for SRS (#3 to #4) than that of PUSCH.

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

[0136] Figure 10 shows an example of SRS settings according to Embodiment 1. As shown in Figure 10, SRS resource set #1 (for example, use is 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, use is 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, use is 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, with the application beam management (BM)), and the power control adjustment state may be set to, for example, a second CL-PC (srs-PowerControlAdjustmentStates = separateClosedLoop).

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

[0138] These settings may be supported for each SRS resource set / SRS resource. Furthermore, these settings may be supported regardless of whether the corresponding CC / BWP is configured for PUSCH or SRS antenna switching.

[0139] As mentioned above, a separate SRS-specific CL-PC adjustment state (an additional CL-PC adjustment state) from that of PUSCH may be introduced (for example, k = 0, 1).

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

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

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

[0143] Figures 11A and 11B show examples of TPC command (DCI) fields. Figure 11A corresponds to the case srs-TPC-PDCCH-Group = typeA, and Figure 11B corresponds to srs-TPC-PDCCH-Group = typeB. Note that the order of the fields in the TPC command in this 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 Figure 11A, the group-common DCI may include instructions for TPC commands for multiple CCs after the SRS request field. In other words, the group-common DCI may include TPC commands for each CC. The setting order of the TPC command fields may be set in ascending (or descending) order of cells (CCs), and if the cells are the same, in ascending (or descending) order of CL-PC adjustment status (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 given CC (cell) may consist of one field (as existing) to indicate the TPC command for any of the TRPs. In this case, an X bit may be added to indicate which TRP the TPC command is associated with (a CL-PC tuning state other than PUSCH). For example, if there are two CL-PC tuning states other than PUSCH, X = 1.

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

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

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

[0149] (Alt2-2) It may be implicitly indicated using an existing bit field (e.g., SRS request field) that either of the first or second CL-PC adjustment states, separate from PUSCH, is associated with the TPC command.

[0150] According to this embodiment, the UE can control SRS transmission by applying the same CL-PC adjustment state as PUSCH, or a different SRS-specific CL-PC adjustment state from PUSCH, regardless of the SRS carrier switching settings.

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

[0152] Option 1: The CL-PC adjustment state for SRS is associated with the SRS resource set. Option 2: If the upper layer parameter srs-PowerControlAdjustmentStates is set to separateClosedLoop, the closedLoopIndex-r17 in the TCI state indicates one CL-PC adjustment state for SRS. Option 3: Add a parameter to P0AlphaSet-r17 in the TCI state that indicates one of the two CL-PC adjustment states for SRS. Option 4: The CL-PC adjustment state for SRS is associated with the use [type] of the SRS resource.

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

[0154] (Extension of DCI Format 2_3) Assuming that existing SRS carrier switching functions cannot be configured simultaneously within the same CC (simultaneous configuration is not supported), both srs-TPC-PDCCH-Group = typeA and typeB may be supported.

[0155] (Introduction of additional TPC commands) For each CC having 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 simultaneously. In this case, only one bit is needed compared to a one-bit closed-loop-indicator field.

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

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

[0159] In cases 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 specify two (first / second) CL-PC adjustment states for SRS in the TCI state.

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

[0161] (Analysis) The DL sTRP / UL mTRP scenario is being considered for application in future wireless communication systems. In this case, it is being considered that two TA / TAGs will be indicated.

[0162] For example, in further extensions to the deployment scenarios for asymmetric DL sTRP / UL mTRP, we envision non-co-located multi-TRPs within bands / cells, and further envision a unified TCI framework for multi-TRPs targeting FR1 and FR2. In this case, it is not necessary to change the definitions of existing cells or to define new cells (e.g., UL-only cells).

[0163] In this extension, for example, when path loss RS is transmitted from DL sTRP, it is necessary to clarify the two closed-loop power control adjustment states for SRS (both independent of PUSCH) or the path loss offset setting in order to calculate the path loss toward UL TRP.

[0164] The two TAs in the deployment scenario of asymmetric DL sTRP / UL mTRP need to be supported in the following frameworks, for example: • 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] <Problem 1> For example, when supporting two TAs in a single DCI-based intra-cell multi-TRP / inter-cell single-TRP, it is necessary to extend the fields of the PRACH-related indicators in the DCI (e.g., DCI format 1_0).

[0167] For example, in existing specifications, for a PRACH triggered by a PDCCH order, the fields of the PRACH-related indicators within the PDCCH order indicate that the PL-RS of the corresponding PRACH transmission is the QCL-RS of the PDCCH order, or that it is the SSB indicated in the PDCCH order.

[0168] Specifically, if the UE is provided with the specific parameter SSB-MTC-AdditionalPCI, the fields in the PRACH-related indicator will show the PCI associated with the PRACH transmission. On the other hand, if the UE is not provided with the specific parameter SSB-MTC-AdditionalPCI, the fields in the PRACH-related indicator will show the PL-RS for the PRACH transmission.

[0169] The existing specifications described above are for multi-DCI based intra-cell multi-TRPs; therefore, it is necessary to extend them for single-DCI / inter-cell single-TRPs.

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

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

[0172] The aforementioned constraints require further extensions to be supported in single DCI-based inter-cell beam management (ICBM) / inter-cell single TRP.

[0173] <Problem 4> As described above, in a multi-DCI-based intracellular multi-TRP of Rel. 18, the PRACH-related indicator indicates whether PRACH (transmit) is associated with the PCI of the serving cell or with an active additional cell (additional PCI).

[0174] In a multi-DCI-based intra-cell multi-TRP, only one active additional cell (additional PCI) can be associated with a PRACH (transmit).

[0175] On the other hand, in single DCI-based inter-cell beam management (ICBM) / inter-cell single TRP from Rel. 19 onwards, it is expected that up to seven active additional cells (additional PCIs) can be associated with PRACH (transmit).

[0176] In this case, it will be necessary to further extend the PRACH-related indicators for single DCI-based inter-cell ICBMs and inter-cell single TRPs.

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

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

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

[0180] However, the methods for setting up new fields and PRACH-related indicator fields have not been sufficiently considered.

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

[0182] Therefore, the inventors have conceived a method that allows for appropriate control of UL transmission and DL reception even when DL sTRP / UL mTRP is applied.

[0183] (Various Modifications, etc.) Hereinafter, embodiments relating to this disclosure will be described in detail with reference to the drawings. Each wireless communication method according to each embodiment may be applied individually or in combination.

[0184] In this disclosure, "A / B" and "at least one of A and B" may be interpreted as mutually exclusive. In this disclosure, "A / B / C" may mean "at least one of A, B, and C".

[0185] In this disclosure, terms such as notice, activate, deactivate, indicate (or specify), select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and capable of operating may be interpreted interchangeably.

[0186] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IE), settings, etc., may be interpreted interchangeably. In this disclosure, Medium Access Control elements (MAC Control Elements (CE)), update commands, activation / deactivation commands, etc., may be interpreted interchangeably.

[0187] In this disclosure, the upper layer signaling may be any or a combination thereof, such as Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and other messages (e.g., messages from the core network, such as positioning protocol messages (e.g., NR Positioning Protocol A (NRPPPa) / LTE Positioning Protocol (LPP)) messages).

[0188] In this disclosure, MAC signaling may include, for example, MAC Control Elements (MAC CEs) and MAC Protocol Data Units (PDUs). Broadcast information may include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), and Other System Information (OSIs).

[0189] In this disclosure, physical layer signaling may include, for example, Downlink Control Information (DCI) and Uplink Control Information (UCI).

[0190] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0191] In this disclosure, base station, gNB, network (NW), RS group, antenna port group, and control resource set (CORESET) group may be interpreted interchangeably. In this disclosure, terminal, user terminal, and User Equipment (UE) may be interpreted interchangeably.

[0192] In this disclosure, terms such as index, identifier (ID), indicator, and resource ID may be interpreted interchangeably. In this disclosure, terms such as sequence, list, set, group, cluster, subset, etc., may be interpreted interchangeably.

[0193] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, 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 Relationship Group, Code Division Multiplexing (CDM) Group, Reference Signal Group, CORESET Group, Physical Uplink Control The following terms may be interchangeable: 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.

[0194] In this disclosure, the following can be interpreted interchangeably: sTRP, single TRP, channel / signal using a single TRP, one SRS resource set being indicated by DCI, channel using one TCI state / spatial relationship, multi-TRP not being activated by RRC / DCI, multiple TCI state / spatial relationships not being activated by RRC / DCI, no CORESETPoolIndex value being set for any CORESET, and no code point in a TCI field being mapped to two TCI states.

[0195] In this disclosure, mTRP, multi-TRP, two SRS resource sets being directed by DCI, channel / signal using multi-TRP, channel using multiple TCI state / spatial relationships, multi-TRP being activated by RRC / DCI, multiple TCI state / spatial relationships being activated by RRC / DCI, and at least one of single-DCI-based multi-TRP and multi-DCI-based multi-TRP may be interpreted as mutually exclusive.

[0196] In this 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 up a specific index (e.g., a TRP index, a CORESET pool index, or an index corresponding to a TRP) for a particular channel / CORESET may be interpreted as mutually exclusive.

[0197] In this disclosure, the following can be interpreted interchangeably: setting up multi-DCI, mDCI, multi-PDCCH, multi-TRP based on multi-DCI, mDCI-based mTRP, two CORESET pool indexes or CORESET pool index = 1 (or one or more values), and setting up multiple specific indexes (e.g., TRP index, CORESET pool index, or index corresponding to TRP) for a specific channel / CORESET.

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

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

[0200] In this disclosure, UL high-density arrangement, distributed TRP mode, separated location mode for transmit / receive points, distributed transmit / receive mode, separated TRP mode, TRP type 1, TRP type 2, TRP type A, and TRP type B may be interpreted as interchangeable.

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

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

[0203] In this disclosure, base station, UL receiving point, UL TRP, UL only TRP, and microBS may be interpreted interchangeably. A UL receiving point may only perform UL receiving, or may perform DL transmission if certain conditions are met.

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

[0205] In this disclosure, TA, TAG, and TA offset values ​​may be interpreted as interchangeable. DL reference timing and DL reception timing may be interpreted as interchangeable. Two TA / TAGs may be interpreted as more than two TA / TAGs.

[0206] In this disclosure, coresetPoolIndex, CORESET Pool Index, and the RRC parameter indicating CORESET Pool Index may be interpreted as interchangeable. n-TimingAdvanceOffset and TA Offset may be interpreted as interchangeable. TCI-UL-State, UL TCI State, and the RRC parameter indicating UL TCI State may be interpreted as interchangeable. dl-OrJointTCI-StateList, List of DL or Joint TCI States, and the RRC parameter indicating List of DL or Joint TCI States may be interpreted as interchangeable. ul-TCI-StateList, List of UL TCI States, and the RRC parameter indicating List of UL TCI States may be interpreted as interchangeable. n-TimingAdvanceOffset and n-TimingAdvanceOffset2 may be interpreted as TA Offset and the RRC parameter indicating TA Offset. In this disclosure, dl-OrJointTCI-StateList, ul-TCI-StateList, list relating to unified TCI states, list of unified TCI states, etc., may be interpreted interchangeably.

[0207] DL sTRP / UL mTRP may mean, for example, a scenario applied in Rel. 19. DL sTRP / UL mTRP may also mean, for example, Scenario 1 (Figure 1B) or Scenario 2 (Figure 2) above. Asymmetric DL sTRP / UL mTRP and DL sTRP / UL mTRP may be interpreted as each other.

[0208] In this disclosure, terms such as 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 interpreted interchangeably.

[0209] (Wireless Communication Method) In this disclosure, when an inter-cell single TRP is set up / applied, one indicator TCI state of a first cell (e.g., a serving cell) may be updated / changed to one indicator 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 one indicator TCI state of the first cell during the period until the update / change of the indicator TCI state by RRC signaling / MAC CE / DCI is completed. The UE may also transmit / receive signals / channels using one indicator TCI state of the second cell during the period after the update / change of the indicator TCI state by RRC signaling / MAC CE / DCI is completed. The first cell [one indicator TCI state] may correspond to a first TA, and the second cell [one indicator TCI state] may correspond to a second TA. The first TA may be updated / changed to the second TA in conjunction with the update / change of the indicated TCI status by RRC signaling / MAC CE / DCI.

[0210] In this disclosure, each embodiment / option may be applied individually or in combination with others.

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

[0212] PRACH-related indicators may indicate PCI (Serving Cell / Additional Cell) associated with a PRACH transmission, or PL-RS for a PRACH transmission.

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

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

[0215] For example, the UE may apply the same (common) behavior to single TRP scenarios (e.g., inter-cell single TRP), single DCI-based scenarios, and multi-DCI-based scenarios with respect to the above determination.

[0216] Alternatively, the UE may apply different behaviors to the above determination for single TRP scenarios (e.g., inter-cell single TRP), single DCI-based scenarios, and multi-DCI-based scenarios. That is, the UE may apply the above determination in any of the cases of single TRP scenarios (e.g., inter-cell single TRP), single DCI-based scenarios, or multi-DCI-based scenarios.

[0217] [Aspect 1-1] In order to support two TAs in a single DCI-based intracellular multi-TRP framework / intercellular 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] In other words, the UE may determine / assume the number of bits for a PRACH-related indicator based on at least one of the following conditions (see Figure 12).

[0219] (Condition 1) When the UE provides a specific parameter (tag-Id2). This specific parameter may be a parameter that indicates a timing advance group.

[0220] (Condition 2) When the UE provides specific parameters (new higher-layer parameters). These new higher-layer parameters may be, for example, parameters that enable 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 provides specific parameters (new higher-layer parameters). The new higher-layer parameters may be, for example, parameters that provide settings for path loss offsets for a specific scenario (DL sTRP / UL mTRP deployment scenario).

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

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

[0224] (Condition 6) When 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 a single DCI-based multi-TRP in a unified TCI state. For example, condition 6 may be rephrased as, "When the UE is provided with dl-OrJointTCI-StateList or TCI-UL-State and has a first TCI-State or TCI-UL-State and a second TCI-State or TCI-UL-State indicated."

[0225] (Condition 7) When UE is set to dl-OrJointTCI-StateList or ul-TCI-StateList.

[0226] (Condition 8) When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has one indicative TCI state (when the UE is configured with a [Cell-to-Cell] Single TRP).

[0227] Furthermore, if a UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has two indicator TCI states, and at least one of the two indicator TCI states is associated with a PCI different from the physical cell ID (PCI) of the serving cell (for example, the PCI of a non-serving cell), then the PRACH-related indicator in DCI format 1_0 does not need to exist (it may be 0 bits).

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

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

[0230] (Example of specification description 1) A new field consists 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] A new field consists of either 0 or 1 bit.

[0232] The new field indicates the PL-RS for a PRACH transmission. Index 0 of this field maps to the DL-RS, which is quasi-collocated to the DM-RS of the PDCCH order. Index 1 of this field maps to the SS / PBCH indicated by the SS / PBCH index field in this DCI format (1_0).

[0233] If none of the above conditions are met (otherwise), the new field is 0 bits.

[0234] (Example of specification description 2) If at least one of the following conditions is met, the UE provides the parameter referenceSignalPower relating to the reference signal power by the corresponding parameter ss-PBCH-BlockPower.

[0235] When a PRACH transmission from a 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 the DL RS that is QCL'd, then at least one of the following conditions is met: • The PDCCH order does not have a PRACH-related indicator; • The PDCCH order does not have a cell indicator field, or the value of that field is 0; • The UE has not provided SSB-MTC-AdditionalPCI, and the value of the PRACH-related indicator field of the PDCCH order is 0; • The PRACH-related indicator field of the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order; • The value of a new field in the PDCCH order is 0; • It depends on the indicated SS / PBCH block. - When a PRACH transmission is sent in a non-serving cell indicated by the cell indicator field of the PDCCH order; - When the UE has not provided SSB-MTC-AdditionalPCI and the value of the PRACH-related indicator field of the PDCCH order is 1; - When the PRACH-related indicator field of the PDCCH order indicates a physCellId different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order; - When the value of the new field of the PDCCH order is 1.

[0236] [Aspect 1-2] In deployment scenarios of a single DCI-based intracellular multi-TRP framework, intercellular single TRP, or DL ​​sTRP / UL mTRP, two TAs may not be supported.

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

[0238] - Multiple (two or more) tags are set for a single serving cell. - Multiple (two or more) DL reference timings are set for a single serving cell. Here, each DL reference timing may be associated with a tag. - Multiple (two or more) n-TimingAdvanceOffset values ​​are set for each serving cell. Here, each timing advance offset value may be associated with a tag. - A correspondence (mapping / association) between the tag ID and the 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 a certain TRP / cell / PCI / TCI state triggers a PRACH for a different TRP / cell / PCI / TCI state than the PDCCH order. - A PRACH-related indicator within the PDCCH order that triggers the PRACH (the PDCCH order must contain a PRACH-related indicator). - A TAG ID is indicated within the PDCCH order. - The TAG is associated with an SSB / CSI-RS.

[0239] In Embodiment 1-2, "when a deployment scenario of a single DCI-based intracellular multi-TRP framework, intercellular single TRP, or DL ​​sTRP / UL mTRP is configured" may mean that at least one of the following conditions is met.

[0240] - When a new higher-level parameter is provided to the UE that enables the DL sTRP / UL mTRP deployment scenario. - When a new higher-level parameter is provided to the UE regarding the setting of the path loss offset for the DL sTRP / UL mTRP deployment scenario. - When the UE is provided with at least one TCI code point indicating two TCI states, and the UE is not provided with two different CORESETPoolIndexes (i.e., single DCI-based). - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has two indicating TCI states, and the UE is not provided with two different CORESETPoolIndexes. - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has one indicating TCI state, and the UE is not provided with two different CORESETPoolIndexes. - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and does not provide two different CORESETPoolIndexes. - When the UE is configured with dl-OrJointTCI-StateList or ul-TCI-StateList and has one indicated TCI state.

[0241] According to this embodiment, the UE can support two TAs in a single DCI-based intracellular multi-TRP framework, intercellular single TRP, or DL ​​sTRP / UL mTRP deployment scenario. Furthermore, even if the UE does not support the two TAs, it can appropriately control corresponding operations depending on the 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 a single DCI-based inter-cell beam management / inter-cell single TRP, the following extensions may be applied to support two TAs. That is, when a UE supports two TAs in a single DCI-based inter-cell beam management / inter-cell single TRP, it may expect / assume at least one of the following:

[0244] - Multiple (two or more) tags may be set for a single serving cell. - Multiple (two or more) DL reference timings may be set for a single serving cell. Here, each DL reference timing may be associated with a tag. - Multiple (two or more) n-TimingAdvanceOffset values ​​may be set for each serving cell. Here, each timing advance offset value may be associated with a tag. - A correspondence (mapping / association) between the tag ID and the 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). A TAC (Timing Advance Command) in MAC RAR may be applied to the specified TAG ID. - Receiving (setting) PRACH settings for each additional cell / PCI (the PCI being different from the serving cell's PCI). - A PRACH-related indicator in the PDCCH order that triggers PRACH (the PDCCH order must contain a PRACH-related indicator). As described above, the PRACH-related indicator indicates the PCI (serving cell / additional cell) associated with the PRACH transmission. In other words, the PRACH-related indicator indicates whether the PRACH transmission is associated with the serving cell or with which additional cell. - A PDCCH order in a certain TRP / cell / PCI / TCI state triggers a PRACH for a TRP / cell / PCI / TCI state different from the PDCCH order. - The TAG ID is specified within the PDCCH order. - The TAG is associated with the SSB / CSI-RS.

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

[0246] (Condition 1) When the UE provides specific parameters (new higher-layer parameters). These new higher-layer parameters may be, for example, parameters that enable multiple (two) TAs in a DL sTRP / UL mTRP deployment scenario, a single DCI-based ICBM, or an inter-cell single TRP.

[0247] (Condition 2) When the UE provides specific parameters (new higher-layer parameters). These new higher-layer parameters may be, for example, parameters relating to the setting of path loss offsets for DL ​​sTRP / UL mTRP deployment scenarios.

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

[0249] (Condition 4) The UE is provided with specific parameters (SSB-MTC-AdditionalPCI) and not with two different CORESETPoolIndexes (i.e., meaning a single DCI-based ICBM or a single inter-cell TRP).

[0250] Based on conditions 1 to 4, the UE can determine / assume support for two TAs in a single DCI-based ICBM / inter-cell single TRP.

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

[0252] If a deployment scenario is set up for a single DCI-based ICBM framework, a single inter-cell TRP, or DL ​​sTRP / UL mTRP, the UE does not need to expect at least one of the contents of aspect 2-1 (configuration / instruction / behavior).

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

[0254] - When the UE is provided with specific parameters (SSB-MTC-AdditionalPCI) and not with two different CORESETPoolIndexes (i.e., meaning it supports single DCI-based ICBMs or single inter-cell TRPs). - When the UE is provided with new higher-layer parameters that enable DL sTRP / UL mTRP deployment scenarios. - When the UE is provided with new higher-layer parameters regarding path loss offset settings for DL ​​sTRP / UL mTRP deployment scenarios.

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

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

[0257] In deployment scenarios for single DCI-based ICBMs, single inter-cell TRPs, or DL ​​sTRP / UL mTRPs, if multiple (two) TAs are enabled, the UE does not expect that the TCI states / UL TCI states associated with a given cell / PCI will correspond to two / more TAGs.

[0258] Alternatively, according to UE capabilities, the TCI states / UL states associated with a given cell / PCI may correspond to two or more 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 within the serving cell).

[0261] (Condition 2) When the UE is provided with a second n-TimingAdvanceOffset value (i.e., when the UE is provided with multiple (two) timing advance offset values ​​within the serving cell).

[0262] (Condition 3) When the UE provides a correspondence (mapping / association) between the TAG ID and the TCI status.

[0263] (Condition 4) When a new upper-layer parameter is provided to the UE that enables multiple (two) TAs in a single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP deployment scenario.

[0264] (Condition 5) If a new higher-level parameter for setting the path loss offset is provided to the UE for the DL sTRP / UL mTRP deployment scenario.

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

[0266] (Condition 7) The UE is provided with specific parameters (SSB-MTC-AdditionalPCI) and not with two different CORESETPoolIndexes (i.e., corresponding to a single DCI-based ICBM or a single inter-cell TRP).

[0267] [Modification] In deployment scenarios for single DCI-based ICBMs, inter-cell single TRPs, or DL ​​sTRP / UL mTRPs, if multiple (two) TAs are enabled, the UE does not expect the same index TAG to be associated with multiple indicator TCI state indices. That is, in this case, the UE does not expect the same TAG index to be associated with each indicator TCI state index. In other words, the UE does not expect a common TAG to be associated with multiple indicator TCI states.

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

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

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

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

[0272] More specifically, in the above case, the UE will determine, based on options 1 and 2 below, whether it can trigger PRACH only on active PCI / serving cells, or on configured PCI cells (either active or inactive).

[0273] (Option 1) PRACH may be triggered only for active add-on cells or serving cells. That is, UE may trigger PRACH only for active add-on cells or serving cells.

[0274] (Option 2) PRACH may be triggered on any configured additional cell (either an active or inactive additional cell). That is, UE may trigger PRACH on any configured additional cell (either an active or inactive additional cell).

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

[0276] According to this embodiment, the UE can appropriately determine which cells (additional cells / serving cells) are subject to the PRACH trigger.

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

[0278] In other words, the UE may determine the cell associated with the PRACH transmission (additional cell / serving cell) according to the following options 1 and 2.

[0279] (Option 1) Use the PRACH-related indicator field in the PDCCH order (DCI format 1_0) that triggers the PRACH transmission. That is, 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) Utilize a new field added to the PDCCH order (DCI format 1_0) that triggers the PRACH transmission. That is, the UE may use (assuming that the new field will be added) the cell associated with the PRACH transmission (additional cell / serving cell).

[0281] According to this embodiment, 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 be determined according to 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 bits. With this number of bits, a maximum of 8 PCIs (including 1 serving cell and 7 additional cells) can be configured / enabled. In other words, 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, number of bits = ceil(log ２ It may be expressed as (NrofadditionalPCI + 1). In this disclosure, ceil(X) may mean multiplying X by a ceiling function. NrofadditionalPCI may represent the number of additional cells (or active additional cells).

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

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

[0287] According to Alt2, the number of bits can be flexibly controlled 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 be in accordance with Alt1 to Alt2 below. The UE may determine / assume the mapping (correspondence with cells (PCI)) of the code points of the PRACH-related indicator / new field in accordance with Alt1 to Alt2 below.

[0289] (Alt1) One code point (e.g., indicated by bit field index 0) may be mapped to the PCI of a serving cell. (Other) NrofadditionalPCI code points (e.g., indicated by bit field indices 1 to NrofadditionalPCI) may be mapped to the PCI of an additional cell. The PCI of such additional cell may be set by upper layer signaling (RRC) in descending / ascending order of the additional cell's index.

[0290] (Alt2) One code point (e.g., indicated by bitfield index 0) may be mapped to the PCI of the serving cell. (Other) NrofadditionalPCI code points (e.g., indicated by bitfield index 1 to NrofadditionalPCI) may be mapped to the PCI of the active additional cell (the PCI of the additional cell associated with the active TCI state) in descending / ascending order of the additional cell index.

[0291] According to this embodiment, the UE can appropriately recognize / determine the correspondence between the code points of the PRACH-related indicator / new field and the cell (PCI) according to Alt1 to Alt2.

[0292] In Embodiment 0D, "when multiple (two) TAs are enabled in a deployment scenario of a single DCI-based ICBM, inter-cell single TRP, or DL ​​sTRP / UL mTRP" 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 the multi-DCI-based inter-cell multi-TRP of Rel. 18, if the PRACH-related indicator field in the PDCCH order indicates the same PCI as the cell receiving the PDCCH order, the PL-RS of the PRACH transmission corresponds to the DL-RS of the PDCCH order, which is quasi-collocated (QCLed).

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

[0295] These correspondences may also apply to single DCI-based ICBM / inter-cell single TRP systems where multiple (two) TAs are enabled.

[0296] Furthermore, the "PRACH-related indicator (field)" in the existing specifications may be interpreted interchangeably with the "new field" in this disclosure.

[0297] For example, some of the conditions under which the UE provides the parameter referenceSignalPower for reference signal power by the corresponding parameter ss-PBCH-BlockPower may be interpreted as at least one of the following: • When a new field in the PDCCH order indicates a physical cell ID (physCellId) associated with the cell receiving the PDCCH order; or • When a new field in the PDCCH order indicates a physCellId different from the physical cell ID (physCellId) associated with the cell receiving the PDCCH order.

[0298] This modified version makes it possible to simplify UE implementation by effectively utilizing existing specifications.

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

[0300] The UL TRP may follow at least one of the following scenarios: Scenario A: The UL TRP does not transmit DL signals / channels. Scenario B: The UL TRP may transmit specific DL signals / channels (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), one joint TCI state may be set for FR1, or one DL TCI state and one UL TCI state may be set.

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

[0304] In Rel. 18 Unified TCI Framework, up to two (or less) joint TCI states may be set for FR1, or one DL TCI state and up to two (or less) UL TCI states may be set.

[0305] In the Rel. 18 Unified TCI Framework, one DL TCI state and up to two (or less) UL TCI states may be set for FR2.

[0306] Rel. 17 In ICBM (Cell-to-Cell Single TRP), the SSB [setting] 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. The SSB / CSI-RS may be indicated as PL-RS / QCL-RS in the UL TCI state. The UE may measure its SSB / CSI-RS. The CSI-RS may be set by the serving cell (DL TRP) or transmitted by the UL TRP.

[0307] The following explanation uses the example of a specific DL signal / channel transmitted by UL TRP being SSB, but the specific DL signal / channel is not limited to this.

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

[0309] In this disclosure, the following can be interpreted interchangeably: setting a PL offset, a UE having a PL offset, setting a PL offset with a non-zero value, a UE having a PL offset with a non-zero value, setting a PL offset with a value of 0, a UE having a PL offset with a value of 0, setting a PL offset with a specific value, a UE having a PL offset with a specific value, etc.

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

[0311] <<Receiving SSB from UL TRP>> The UE may receive settings (from the base station / DL TRP) regarding PL offsets for joint TCI states / UL TCI states. The UE may determine / assume whether to receive SSB from the UL TRP or DL ​​TRP based on whether such settings configure one or more PL offsets for one or more joint TCI states / UL TCI states.

[0312] If the UE has set up one or more PL offsets for one or more joint TCI states / UL TCI states, the UE does not need to assume that it will receive SSBs from the UL TRP (see Figure 13A). Otherwise (i.e., if the UE does not have set up 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, the absence of the assumption that the UE receives SSB from the UL TRP may also mean the assumption that the UE receives SSB from the DL TRP.

[0314] <<Association between Indicator TCI State and Physical Cell ID (PCI)>> If a UE sets one or more PL offsets in one or more Indicator Joint TCI states / Indicator UL TCI states in a single BWP / Component Carrier (CC), the UE does not need to assume that those one or more Indicator Joint TCI states / Indicator UL TCI states are associated with a PCI different from the Physical Cell ID (PCI) of the serving cell (e.g., a PCI of a non-serving cell).

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

[0316] In this disclosure, the absence of the assumption that one or more UE designating joint TCI states / designating UL TCI states are associated with a PCI different from the PCI of the serving cell (e.g., a PCI of a non-serving cell) may mean that the assumption that one or more UE designating joint TCI states / designating 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 features 2 / 3, the 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 capability information: - Support for the Single TRP Inter-Cell [Rel. 17] Unified TCI Framework (Inter-Cell Single TRP). - Support for two Inter-Cell TAs (e.g., a first TA for the first cell (e.g., a serving cell) and a second TA for the second cell (e.g., a non-serving cell)). - Support for the SSB corresponding to an additional PCI (e.g., a PCI corresponding to a non-serving cell) to be PRACH's PL-RS.

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

[0319] <Embodiment 2> Embodiment 2 addresses the above-mentioned problem 6 and relates to instructions for PL offset for PRACH (hereinafter also referred to as PDCCH order PRACH) for a PDCCH order.

[0320] To indicate the PL offset for the PDCCH order PRACH, it is being considered to introduce a new field (e.g., a 1-bit field) within a specific DCI format (e.g., DCI format 1_0).

[0321] The new field may exist if at least one of the following conditions is met: • The corresponding RRC parameter (for example, an RRC parameter that instructs whether or not the new field exists) is set to enabled. • A PL offset is set in at least one TCI state.

[0322] The new field may be a one-bit field indicating either a first value (e.g., 0) [index] or a second value (e.g., 1) [index].

[0323] When a joint TCI state / UL TCI state is indicated / set in Rel. 17 Unified TCI Framework, the first value [index] of the new field may indicate that the PL offset is not included in the calculation of the PRACH's transmit power. In other words, when a joint TCI state / UL TCI state is indicated / set in Rel. 17 Unified TCI Framework, the UE may determine / confirm, based on the fact that the new field is the first value, that the PL offset is not included (the PL offset is not used) in the calculation of the PRACH's transmit power.

[0324] When a joint TCI state / UL TCI state is indicated / set in Rel. 17 Unified TCI Framework, the second value [index] of the new field may indicate that the calculation of the PRACH's transmit power includes the PL offset associated with that joint TCI state / UL TCI state. In other words, when a joint TCI state / UL TCI state is indicated / set in Rel. 17 Unified TCI Framework, the UE may determine / confirm, based on the fact that the new field is a second value, that the calculation of the PRACH's transmit power includes (or uses) the PL offset associated with that joint TCI state / UL TCI state.

[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) are indicated / set in the Rel. 18 Unified TCI Framework, the first value [index] of the new field may indicate that the calculation of the PRACH's transmit power includes the PL offset associated with the first joint TCI state / UL TCI state. In other words, when two joint TCI states / UL TCI states are indicated / set in the Rel. 18 Unified TCI Framework, the UE may determine / confirm, based on the fact that the new field is the first value, that the calculation of the PRACH's transmit power includes the PL offset associated with the first joint TCI state / UL TCI state (i.e., uses the PL offset associated with the first joint TCI state / UL TCI state).

[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) are indicated / set in the Rel. 18 Unified TCI Framework, the second value (e.g., 1) [index] of the new field may indicate that the calculation of the PRACH's transmit power includes a PL offset associated with the second joint TCI state / UL TCI state. In other words, when two joint TCI states / UL TCI states are indicated / set in the Rel. 18 Unified TCI Framework, the UE may determine / confirm, based on the fact that the new field is a second value, that the calculation of the PRACH's transmit power includes a PL offset associated with the second joint TCI state / UL TCI state (i.e., uses a PL offset associated with the second joint TCI state / UL TCI state).

[0327] Therefore, the new field may also be called a field that indicates whether the PL offset is included in the calculation of the PRACH's transmit power, a field that indicates whether the PL offset is used (or applied) in the calculation of the PRACH's transmit power, a field that indicates the TCI state associated with the PL offset used (or applied) in the calculation of the PRACH's transmit power, and so on.

[0328] Here, Feature 1 described above is available in intra-cell cases (e.g., multi-DCI based intra-cell multi-TRP framework, single-DCI based intra-cell multi-TRP framework). Feature 3 described above is available in both intra-cell cases (e.g., multi-DCI based intra-cell multi-TRP framework, single-DCI based intra-cell multi-TRP framework) and inter-cell cases (e.g., multi-DCI based inter-cell multi-TRP framework, single-DCI based inter-cell multi-TRP framework, inter-cell single TRP). Therefore, in a specific case (e.g., an intra-cell case), Feature 1 and Feature 3 may be set simultaneously.

[0329] The new field described above may be configured according to at least one of the following options. These options are preferably applied when features 1 and 3 described above are configured simultaneously, but may also be applied in other cases.

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

[0331] For example, if both the first and second RRC parameters are set to disabled, neither the new field nor the PRACH-related indicator field needs to 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 for these fields is 0.

[0332] For example, if the first RRC parameter is set to enabled and the second RRC parameter is set to disabled, a new field may be set, but 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 bits, so the total number of bits for these is 1 bit.

[0333] For example, if 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 for these is 1 bit.

[0334] For example, if both the first and second RRC parameters 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 for these is 2 bits.

[0335] <<Option 2>> New fields and PRACH-related indicator fields may be defined by a single (common) RRC parameter. The UE may determine whether new fields and PRACH-related indicator fields are included in a particular DCI format based on a single (common) RRC parameter.

[0336] For example, if one RRC parameter is set to disabled, both the new field and the PRACH-related indicator field do not need to 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 for these is 0.

[0337] For example, if 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 for these is 2 bits.

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

[0339] For example, if one RRC parameter is set to disabled, the common field does not need to be set. In this case, the common field is 0 bits.

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

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

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

[0343] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new Logical Channel ID (LCID) not defined in existing standards in the MAC subheader.

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

[0345] Furthermore, the notification of arbitrary information to the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0346] <<Notification of Information from UE>> Notification of any information from the UE to the NW in the embodiments described above (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] If the above notification is made by a MAC CE, the MAC CE may be identified by the inclusion of a new LCID not specified in existing standards in the MAC subheader.

[0348] If the above notice is made by the UCI, the notice may be transmitted using PUCCH or PUSCH.

[0349] Furthermore, the notification of any information from the UE in the above-described embodiment may be periodic, semi-persistent, or aperiodic.

[0350] <<Regarding the application of each embodiment>> In UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the embodiments described above may be applied (or used) if any or more of the following conditions are met: - A higher-layer parameter indicating the specific process / operation / control / assumption / information is set; - The specific process / operation / control / assumption / information is determined based on the relevant higher-layer parameter; - The specific process / operation / control / assumption / information is designated / activated / triggered by MAC CE / DCI / UCI / Resource / Channel / RS; - A specific UE capability indicating (or related to) the specific process / operation / control / assumption / information is reported or supported; - The application of the specific process / operation / control / assumption / information is determined based on specific conditions.

[0351] The above-mentioned specific UE capabilities may represent at least one of the following: supporting the above-mentioned specific processing / operation / control / assumment / information; supporting inter-cell single TRP [2TA in]; and supporting specific fields of a specific DCI format (e.g., supporting the new / common fields of Embodiment 2).

[0352] Furthermore, the above-mentioned specific UE capability may be a capability that applies across all frequencies (commonly regardless of frequency), a capability per frequency (e.g., one or a combination thereof, such as cell, band, band combination, BWP, component carrier, etc.), a capability per frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), a capability per subcarrier spacing (SCS), or a capability per feature set (FS) or feature set per component-carrier (FSPC).

[0353] Furthermore, the specific UE capabilities described above may be capabilities that apply across all duplexing schemes (common to all duplexing schemes regardless of the duplexing scheme), or they may be capabilities specific to each duplexing scheme (e.g., Time Division Duplex (TDD), Frequency Division Duplex (FDD)).

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

[0355] (Note) The following inventions are noted with respect to one embodiment of the present disclosure (in particular, Embodiment 0A): [Note 1] A terminal having: a receiving unit that receives a physical downlink control channel (PDCCH) order including a physical random access channel (PRACH) related indicator field; and a control unit that determines the bit size of the PRACH related indicator field based on a specific condition for two timing advances (TAs) at a single transmit / receive point (TRP) between different cells. [Note 2] The terminal according to Note 1, wherein the specific condition is whether a list of Unified Transmit Setting Instruction (TCI) states is set and one TCI state is indicated. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit determines that the bit size of the PRACH related indicator field is 1 bit if a list of Unified Transmit Setting Instruction (TCI) states is set and one TCI state is indicated. [Note 4] The terminal according to any one of Notes 1 to 3, wherein the control unit determines that the bit size of the PRACH-related indicator field is 0 bits when a list relating to Unified Transmission Instruction (TCI) states is set, two TCI states are indicated, and at least one of the two TCI states is associated with a PCI different from the physical cell ID (PCI) of the serving cell.

[0356] (Note) The following inventions are noted with respect to one embodiment of the present disclosure (in particular, Embodiment 1 and Embodiment 2). [Note 1] A terminal having: a receiving unit that receives a setting relating to a path loss (PL) offset for a joint transmit setting instruction (TCI) state or an uplink (UL) TCI state; and a control unit that determines, based on the setting, from which transmit / receive point (TRP) to receive a synchronization signal block (SSB). [Note 2] The terminal according to 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. [Note 3] The terminal according to Note 1 or Note 2, wherein the control unit does not assume that the joint TCI state or UL TCI state will be associated with a PCI different from the physical cell ID (PCI) of the serving cell when the PL offset is set by the setting. [Note 4] The terminal according to any one of Notes 1 to 3, wherein when the PL offset is set by the setting, the control unit determines, based on specific parameters, whether the downlink control information includes a specific field that indicates whether the PL offset is included in the calculation of the transmission power of the physical random access channel (PRACH) and a PRACH-related indicator field.

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

[0358] Figure 14 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 (which may also be simply called system 1) may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0359] Furthermore, the wireless communication system 1 may 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)), and the like.

[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 where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0362] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement, number, shape, size, etc., of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, 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 by multiple antennas / base stations 10. One [virtual] cell (which may be called a supercell, for example) may be composed of multiple [virtual] cells (which may be called subcells, for example). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell whose physical range fluctuates quasi-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 the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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. Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may be in a frequency band higher than FR2.

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

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

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

[0369] The core network 30 may include network functions (NF) such as User Plane Function (UPF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Unified Data Management (UDM), Application Function (AF), Data Network (DN), Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). Multiple functions may be provided by a single network node. Furthermore, communication with an external network (e.g., the Internet) may occur via the DN.

[0370] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0371] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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-OFDM), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0372] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0374] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0375] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0377] Furthermore, the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Furthermore, PDSCH may be read as DL data, and PUSCH may be read as UL data.

[0378] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. A UE may monitor CORESETs associated with a given search space based on the search space configuration.

[0379] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

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

[0381] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted from the names of various channels.

[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, the DL-RS may include 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.

[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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0384] Furthermore, in the wireless communication system 1, the uplink reference signal (UL-RS) may include a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. The DMRS may also be called a user-specific reference signal (UE-specific Reference Signal).

[0385] (Base Station) Figure 15 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transmitting / receiving unit 120, the transmitting / receiving antenna 130, and the transmission line interface 140 may be provided.

[0386] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0387] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0389] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0390] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0391] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

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

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

[0395] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

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

[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 130.

[0398] The transmitting / receiving unit 120 (receiving 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 (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.

[0399] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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 send and receive signals (backhaul signaling) with devices included in the core network 30 (e.g., network nodes providing NF), other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0401] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0402] Note that the base station 10 may be separated into three elements: a Radio Unit (RU), a Distributed Unit (DU), and a Central Unit (CU). For example, the RU may implement RF processing (such as digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-layer functions of the physical layer (such as precoding, IFFT, FFT, etc.). The DU may implement upper-layer functions of the physical layer (such as from coding to resource element mapping, etc.), functions of the MAC layer, and functions of the RLC layer. The CU may implement functions of the PDCP layer, the Service Data Adaptation Protocol (SDAP) layer, and the RRC layer.

[0403] In the present disclosure, the base station 10 may include one device that realizes all the functions of the RU, DU, and CU, or may include a plurality of devices that respectively realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be readably replaced with RU / DU / CU.

[0404] The transmitting and receiving unit 120 may transmit a Physical Downlink Control Channel (PDCCH) order including a Physical Random Access Channel (PRACH) related indicator field.

[0405] The control unit 110 may determine the bit size of the PRACH related indicator field based on specific conditions for two Timing Advance (TA) at a single transmit and receive point (TRP) between different cells.

[0406] The transmitting and receiving unit 120 may transmit a setting regarding a path loss (PL) offset for a Joint Transmission Configuration Indicator (TCI) state or an Uplink (UL) TCI state.

[0407] The control unit 110 may determine from which transmit and receive point (TRP) to transmit a Synchronization Signal Block (SSB) based on the setting.

[0408] (User Terminal) FIG. 16 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. Note that one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may be provided.

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

[0410] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

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

[0412] The transmission / reception 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 transmission / reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

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

[0414] The transmission / reception antenna 230 can be composed of an antenna, such as an array antenna, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[0415] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

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

[0417] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210 to generate a bit sequence to be transmitted.

[0418] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0419] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0420] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band 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 transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (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 transmitting / receiving unit 220 (measuring unit 223) may perform measurements related to the received signal. For example, the measuring unit 223 may perform RRM measurement, CSI measurement, etc., based on the received signal. The measuring unit 223 may also measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0424] The measurement unit 223 may derive channel measurements for CSI calculation based on channel measurement resources. 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 interference measurement resources. Interference measurement resources may be at least one of the following: NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. CSI-IM may also be called CSI-Interference Management (IM), and may be interpreted interchangeably with Zero Power (ZP) CSI-RS. In this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., may be interpreted interchangeably.

[0425] In this disclosure, the transmitting unit and receiving unit of the user terminal 20 may be composed of at least one of a transmitting / receiving unit 220 and a transmitting / receiving antenna 230.

[0426] The transmitting / receiving unit 220 may receive a physical downlink control channel (PDCCH) order that includes a physical random access channel (PRACH) related 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) at a single transmit / receive point (TRP) between different cells (e.g., a first cell and a second cell) (e.g., an inter-cell single TRP).

[0428] The aforementioned specific conditions may also include whether a list of Unified Transmitting Instruction (TCI) states (e.g., dl-OrJointTCI-StateList or ul-TCI-StateList) is set and whether 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 if a list relating to Unified Transmitting Instruction (TCI) states (for example, 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 relating to Unified Transmitting Instruction (TCI) states (e.g., dl-OrJointTCI-StateList or ul-TCI-StateList) is set, two TCI states are indicated, and at least one of the two TCI states is associated with a PCI different from the physical cell ID (PCI) of the serving cell (e.g., a PCI of a non-serving cell).

[0431] The transmitting / receiving unit 220 may receive settings relating to the path loss (PL) offset for the Joint Transmit Instruction (TCI) state or the Uplink (UL) TCI state.

[0432] The control unit 210 may determine, based on the above settings, which transmission / reception point to receive the synchronization signal block (SSB).

[0433] The control unit 210 does not need to assume that the SSB will be received from the uplink TRP when the PL offset is set according to the above setting.

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

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

[0436] (Hardware Configuration) The block diagram used in the description of the above embodiment shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0437] Here, functions include, but are not limited to, judgment, decision-making, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection determination, establishment, comparison, assumption, expectation, consideration, broadcasting, notification, communication, forwarding, configuration, reconfiguration, allocation (mapping), assignment, etc. For example, a functional block (component) that enables transmission may be referred to as a transmitting unit, a transmitter, etc. In any case, as described above, the implementation method is not particularly limited.

[0438] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs the processing of the wireless communication method of the present disclosure. FIG. 17 is a diagram showing 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 physically be 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 the present disclosure, the terms such as device, circuit, device, section, unit, etc. can be read interchangeably with each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without including some devices.

[0440] For example, although only one processor 1001 is shown in the figure, there may be a plurality of processors. Also, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or using other methods. Note that the 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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or control at least one of reading and writing data in the memory 1002 and storage 1003.

[0442] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0443] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0444] The memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be called a register, cache, or main memory. The memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of the present disclosure.

[0445] The storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a Compact Disk (Compact Disc ROM (CD-ROM)), a Digital Use Disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. The storage 1003 may also be called an auxiliary storage device.

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

[0447] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., 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 different buses may be configured for 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0450] Furthermore, devices included in the core network 30 (for example, network nodes that provide NF) may also be implemented using the functional block / hardware configuration described above.

[0451] (Variations) Terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0452] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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 neurology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neurology may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

[0456] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0457] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, and one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing a TTI may be called a slot, mini-slot, 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, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

[0460] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0461] A TTI with a time length of 1 ms may be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0462] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0463] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0464] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0465] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0466] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0467] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. These common RBs may be identified by an index of the RBs relative to a common reference point of the carrier. The PRBs may be defined and numbered within a given BWP.

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

[0469] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0470] The structures of wireless frames, subframes, slots, minislots, and symbols described above are merely examples. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

[0472] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements using these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0474] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0475] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0476] Any information described in this disclosure (e.g., variables, constants, parameters) may be communicated from any first device (e.g., UE / base station) to any second device (e.g., base station / UE) that indicates / specifies (or relates to) the value of such any information, even if not specifically stated in the embodiments described above.

[0477] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

[0478] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Elements (CEs).

[0479] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, 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 as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0481] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0482] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0483] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0484] In this disclosure, terms such as “precoding,” “precoder,” “weight (precoding weight),” “quasi-co-location (QCL),” “transmission configuration indication state (TCI state),” “spatial relation,” “spatial domain filter,” “transmit power,” “phase rotation,” “antenna port,” “layer,” “number of layers,” “rank,” “resource,” “resource set,” “beam,” “beam width,” “beam angle,” “antenna,” “antenna element,” “panel,” “UE panel,” “transmitting entity,” and “receiving entity” may be used interchangeably.

[0485] In this disclosure, "antenna port" may be interpreted interchangeably with "antenna port for any signal / channel" (e.g., a Demodulation Reference Signal (DMRS) port). In this disclosure, "resource" may be interpreted interchangeably with "resource for any signal / channel" (e.g., a reference signal resource, an SRS resource, etc.). Resources may include time / frequency / code / spatial / power resources. Furthermore, a spatial domain transmit filter may include at least one of a spatial domain transmit filter and a spatial domain receive filter.

[0486] The above group may include, for example, at least one of the following: 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, or a panel group.

[0487] Furthermore, in this disclosure, terms such as beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), and RS may be interpreted interchangeably.

[0488] Furthermore, in this disclosure, 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 interpreted interchangeably.

[0489] Furthermore, in this disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interpreted interchangeably.

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

[0491] Furthermore, the spatial relationship information Identifier (ID) (TCI state ID) and spatial relationship information (TCI state) may be interpreted as mutually exclusive. "Spatial relationship information (TCI state)" may be interpreted as mutually exclusive as "a set of spatial relationship information (TCI state)," "one or more pieces of spatial relationship information," etc. TCI state and TCI may be interpreted as mutually exclusive. Spatial relationship information and spatial relationship may be interpreted as mutually exclusive.

[0492] In this disclosure, terms such as “Base Station (BS),” “wireless base station,” “fixed station,” “NodeB,” “eNB (eNodeB),” “gNB (gNodeB),” “access point,” “Transmission Point (TP),” “Reception Point (RP),” “Transmission / Reception Point (TRP),” “panel,” “cell,” “sector,” “cell group,” “carrier,” and “component carrier” may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0493] A base station may house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station may be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0494] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform a control / operation based on said information.

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

[0496] A mobile station may also be called 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 appropriate term.

[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. At least one of the base station and the mobile station may also be a device mounted on a moving object, the moving object itself, etc.

[0498] The term "mobile object" refers to any movable object, regardless of its speed, and naturally includes cases where the mobile object is stationary. Examples of such mobile objects include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items carried on them. Furthermore, such mobile objects may be autonomously driven objects operating based on operational commands.

[0499] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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] Figure 18 shows an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed sensor 51, a pneumatic 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 consists of, for example, at least one of an engine, a motor, or an engine-motor hybrid. 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 consists of a microprocessor 61, memory (ROM, RAM) 62, and communication ports (e.g., input / output (IO) ports) 63. Signals from various sensors 50-58 installed in the vehicle are input to the electronic control unit 49. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

[0503] Signals from various sensors 50-58 include current signals from current sensor 50 for sensing motor current, rotational speed signals of front wheels 46 / rear wheels 47 acquired by rotational speed sensor 51, air pressure signals of front wheels 46 / rear wheels 47 acquired by air pressure sensor 52, vehicle speed signals acquired by vehicle speed sensor 53, acceleration signals acquired by acceleration sensor 54, accelerator pedal depression amount signals acquired by accelerator pedal sensor 55, brake pedal depression amount signals acquired by brake pedal sensor 56, operation signals of shift lever 45 acquired by shift lever sensor 57, and detection signals acquired by object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc.

[0504] The information service unit 59 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, display, television, and radio, and one or more ECUs that control these devices. The information service unit 59 uses information acquired from external devices via a communication module 60 or the like to provide various types of 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 that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0506] The driver assistance system unit 64 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, 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 Unit (IMU), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driver 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 sends and receives data (information) via the communication port 63 to 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, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

[0510] The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 59 installed in the vehicle. The information service unit 59 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 60).

[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, axle 48, various sensors 50-58, etc., which are provided in the vehicle 40.

[0512] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel, downlink channel, etc., may be interpreted as sidelink channel.

[0513] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

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

[0515] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0516] Each aspect / embodiment described in this disclosure is 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 (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, systems utilizing Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, and next-generation systems extended, modified, created, or defined based thereon may also be applied. Furthermore, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0517] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0518] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0519] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to mean judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0520] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0521] Furthermore, “judgment (decision)” may be considered as “judgment (decision)” of resolving, selecting, choosing, establishing, comparing, etc. In other words, “judgment (decision)” may be considered as “judgment (decision)” of some action. In this disclosure, “judgment (decision)” may be interpreted as mutually interchangeable with the actions described above.

[0522] Furthermore, in this disclosure, “determine / determining” may be interpreted as “assume / assuming,” “expect / expecting,” or “consider / considering.” In addition, in this disclosure, “not expecting to do…” may be interpreted as “expecting not to do….”

[0523] In this disclosure, "expect" may be rephrased as "be expected." For example, "expect(s) ..." (where "..." may be expressed as a that clause, an infinitive, etc.) may be rephrased as "be expected ..." or "do (the verb without "to" if "..." is an infinitive)." Similarly, "does not expect ..." may be rephrased as "be not expected ..." or "do not (the verb without "to" if "..." is an infinitive)." Furthermore, "An apparatus A is not expected ..." may be rephrased 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 term "maximum transmit power" as used in this disclosure may mean the maximum 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,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0526] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0527] In this 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 "combine" may be interpreted similarly to "different."

[0528] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0529] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0530] In this disclosure, "less than or equal to," "less than," "greater than or equal to," "more than," and "equal to" may be interpreted interchangeably. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees. In addition, in this disclosure, words meaning "good," "bad," "big," "small," "high," "low," "early," "slow," "wide," and "narrow" may be interpreted interchangeably, not limited to the positive, comparative, and superlative degrees, by adding "i-th" (where i is any integer) to the expression (for example, "highest" may be interpreted interchangeably with "i-th highest").

[0531] In this disclosure, "of," "for," "regarding," "related to," and "associated with" may be interpreted as being interchangeable.

[0532] In this disclosure, phrases 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. Furthermore, A, B, etc., may be replaced with appropriate expressions such as nouns, gerunds, or regular sentences depending on the context. The time difference between A and B may be approximately zero (immediately after or immediately before). Additionally, a time offset may be applied to the time when A occurs. For example, "A" may be interpreted as "before / after the time offset when A occurs". The time offset (e.g., one or more symbols / slots) may be predetermined or determined by the UE based on notified information.

[0533] In this disclosure, timing, time, duration, time instance, any unit of time (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc., may be interpreted interchangeably.

[0534] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The descriptions herein are illustrative and not intended to be restrictive in any way to the invention described herein.

[0535] This application is based on Japanese Patent Application No. 2024-195431, filed on November 7, 2024. All of its contents are included here.

Claims

1. A terminal having a receiving unit that receives settings relating to path loss (PL) offset for joint transmission setting instruction (TCI) status or uplink (UL) TCI status, and a control unit that determines from which transmission / reception point (TRP) to receive the synchronization signal block (SSB) based on the settings.

2. The terminal according to claim 1, wherein the control unit does not anticipate receiving the SSB from the 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 UL TCI state is associated with a PCI different from the physical cell ID (PCI) of the serving cell when the PL offset is set by the setting.

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

5. A wireless communication method for a terminal, comprising the steps of: receiving a setting relating to a path loss (PL) offset for a Joint Transmit Setting Instruction (TCI) state or an Uplink (UL) TCI state; and determining, based on the setting, from which transmit / receive point (TRP) to receive a synchronization signal block (SSB).

6. A base station comprising: a transmitting unit that transmits a setting relating to a path loss (PL) offset for a Joint Transmitting Instruction (TCI) state or an Uplink (UL) TCI state; and a control unit that determines, based on the setting, from which transmit / receive point (TRP) to transmit a synchronization signal block (SSB).

Images