Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a plurality of settings corresponding to a plurality of cells; and a control unit that, for each of the cells, applies a transmission configuration indication (TCI) state indicated by a corresponding one of the settings. Each of the settings includes whether the corresponding TCI state is to be applied to both a downlink and an uplink and / or whether the corresponding TCI state is to be applied to a plurality of types of channels and / or signals. According to one aspect of the present disclosure, it is possible to appropriately recognize the relationship among joint TCI states, an RS for at least one of wireless link monitoring, beam obstacle detection, and new beam detection, and a specific channel / RS TCI state.

Description

[Technical Field]

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

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

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

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

[0005] In future wireless communication systems (e.g., NR), it is being considered that user terminals (UEs) will control transmission and reception processing based on information about quasi-co-location (QCL) (QCL assumptions / Transmission Configuration Indication (TCI) states / spatial relationships).

[0006] A unified TCI state, which applies the configured / activated / instructed TCI state to multiple types of channels / reference signals (RSs), is being considered. However, the relationship between the TCI state of a specific channel / RS, the RS for at least one of radio link monitoring, beam fault detection, and new beam detection, and the unified TCI state is unclear. If such a relationship is unclear, it may lead to degradation of communication quality, degradation of throughput, etc.

[0007] Therefore, the present disclosure provides a terminal and a wireless communication method that appropriately recognize the relationship between the TCI state of a specific channel / RS, the RS for at least one of radio link monitoring, beam failure detection, and new beam detection, and the unified TCI state. 、 base station and systems One of the aims is to provide [Means for solving the problem]

[0008] A terminal according to one aspect of the present disclosure includes: a receiver that receives a configuration of a list of transmission configuration indication (TCI) states applicable to a plurality of types of channels and reference signals, and a Radio Resource Control (RRC) information element that indicates whether the TCI state is to be applied to a downlink (DL) and an uplink (UL) or whether the TCI state is to be applied to either the DL or the UL; and a controller that, when a reference signal for beam failure detection and radio link monitoring is not configured, determines the reference signal for beam failure detection and radio link monitoring based on the RRC information element and a TCI state in the list of TCI states, and the controller applies a new Quasi-Co-Location (QCL) source reference signal to at least one of specific channels and signals to which the TCI state in the list of TCI states is applied, a specific symbol after receiving a response to beam failure recovery. The list of TCI states is included in a Physical Downlink Shared Channel (PDSCH) configuration, and the receiving unit receives an activation information element not included in the PDSCH configuration, which indicates whether the TCI state in the list of TCI states is valid for a specific signal. The control unit determines whether the TCI state in the list of TCI states is valid for the specific signal based on the activation information element. do. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, the relationship between the TCI state of a particular channel / RS, the RS for at least one of radio link monitoring, beam failure detection, and new beam detection, and the unified TCI state can be properly recognized. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of simultaneous beam updating for multiple CCs. [Figure 2] 2A and 2B are diagrams illustrating an example of a unified / common TCI framework. [Figure 3] 3A and 3B are diagrams showing an example of a CC-specific TCI state pool and a CC-common TCI state pool. [Figure 4] 4A and 4B are diagrams showing an example of a TCI state in a CC-specific TCI state pool. [Figure 5] 5A and 5B are diagrams showing an example of TCI states in a CC common TCI state pool. [Figure 6] 6A and 6B are diagrams illustrating an example of a CC-specific RS in a TCI state. [Figure 7] 7A and 7B are diagrams showing an example of a CC common RS in a TCI state. [Figure 8] FIG. 8 is a diagram illustrating an example of a BFR procedure. [Figure 9] FIG. 9 is a diagram showing an example of instruction method 1-1. [Figure 10] FIG. 10 is a diagram showing an example of a list of resources / resource sets according to aspect 1-2. [Figure 11] 11A to 11C are diagrams showing an example of an enabler according to instruction method 2-1. [Figure 12] FIG. 12 is a diagram showing an example of a joint TCI state according to instruction method 2-1. [Figure 13] FIG. 13 is a diagram showing an example of a separate TCI state according to instruction method 2-1. [Figure 14] FIG. 14 is a diagram showing an example of instruction method 2-2. [Figure 15] FIG. 15 is a diagram showing an example of instruction method 2-3. [Figure 16] FIG. 16 is a diagram showing an example of instruction method 2-4. [Figure 17] FIG. 17 is a diagram showing another example of instruction method 2-4. [Figure 18] FIG. 18 is a diagram showing an example of the relationship between the value of the TCI field and whether or not it is shared according to instruction method 2-4. [Figure 19] FIG. 19 is a diagram illustrating an example of a joint TCI state according to aspect 2-1. [Figure 20] FIG. 20 is a diagram showing an example of a separate TCI state according to aspect 2-1. [Figure 21] FIG. 21 is a diagram showing an example of aspect 3-2. [Figure 22] FIG. 22 is a diagram showing another example of aspect 3-2. [Figure 23]FIG. 23 is a diagram illustrating an example of the fourth embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 25] FIG. 25 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 26] FIG. 26 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 27] FIG. 27 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 28] FIG. 28 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

[0020] The physical layer signaling may be, for example, Downlink Control Information (DCI).

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

[0022] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), a CSI-RS for tracking (also called a Tracking Reference Signal (TRS)), and a QCL detection reference signal (also called a QRS).

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

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

[0025] (Simultaneous beam update of multiple CCs) In Rel.16, one MAC CE can update the beam index (TCI state) of multiple CCs.

[0026] The UE can be configured by RRC with up to two applicable CC lists (e.g., applicable-CC-list). When two applicable CC lists are configured, the two applicable CC lists may correspond to in-band CA in FR1 and in-band CA in FR2, respectively.

[0027] The network may activate and deactivate the configured TCI states of a serving cell or of a set of serving cells configured in simultaneous TCI update list 1 (simultaneousTCI-UpdateList1) or simultaneous TCI update list 2 (simultaneousTCI-UpdateList2) by sending a TCI States Activation / Deactivation for UE-specific PDSCH MAC CE. If the indicated serving cell is configured as part of simultaneous TCI update list 1 or simultaneous TCI update list 2, the MAC CE applies to all serving cells configured in the set of simultaneous TCI update list 1 or simultaneous TCI update list 2.

[0028] The network may indicate the configured TCI states of a serving cell or of a set of serving cells configured in simultaneous TCI update list 1 (simultaneousTCI-UpdateList1) or simultaneous TCI update list 2 (simultaneousTCI-UpdateList2) by sending a TCI States Indication for UE-specific PDCCH MAC CE. If the indicated serving cell is configured as part of simultaneous TCI update list 1 or simultaneous TCI update list 2, the MAC CE applies to all serving cells configured in the set of simultaneous TCI update list 1 or simultaneous TCI update list 2.

[0029] Activation of TCI states on PDCCH The MAC CE activates the TCI states associated with the same CORESET ID on all BWP / CCs in the applicable CC list.

[0030] Activation of TCI states for PDSCH The MAC CE activates the TCI states on all BWP / CCs in the applicable CC list.

[0031] A-SRS / SP-SRS Spatial Relationship Activation The MAC CE activates spatial relationships associated with the same SRS resource ID on all BWPs / CCs in the applicable CC list.

[0032] In the example of Figure 1, the UE is configured with an applicable CC list indicating CCs #0, #1, #2, and #3, and a list indicating 64 TCI states for the CORESET or PDSCH of each CC. When one TCI state of CC #0 is activated by the MAC CE, the corresponding TCI states are activated in CCs #1, #2, and #3.

[0033] Such simultaneous beam updating is considered applicable only to the single TRP case.

[0034] For PDSCH, the UE may follow procedure A. [Step A] The UE receives activation commands to map up to eight TCI states to codepoints in the DCI field (TCI field) within one CC / DL BWP or within one set of CC / BWPs. If one set of TCI state IDs is activated for one set of CC / DL BWPs, then the applicable list of CCs is determined by the CC indicated in the activation command, and the same set of TCI states applies to all DL BWPs within the indicated CC. A set of TCI state IDs can be activated for one set of CC / DL BWPs only if the UE is not provided with multiple different values ​​of the CORESETPoolIndex in the CORESET information element (ControlResourceSet) and at least one TCI codepoint that maps to two TCI states.

[0035] For PDCCH, the UE may follow procedure B. [Step B] If the UE is provided with up to two lists of cells for simultaneous TCI state activation by the simultaneous TCI cell list (simultaneousTCI-CellList) via the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList-r16 and simultaneousTCI-UpdateListSecond-r16), the UE applies antenna port quasi co-location (QCL) provided by TCI states with the same activated TCI state ID value to the CORESET with index p in all configured DL BWPs of all configured cells in one list determined from the serving cell index provided by the MAC CE command. A simultaneous TCI cell list can be provided for simultaneous TCI state activation only if the UE is not provided with different values ​​of the CORESET pool index (CORESETPoolIndex) in the CORESET information element (ControlResourceSet) and at least one TCI codepoint that maps to two TCI states.

[0036] For semi-persistent (SP) / aperiodic (AP)-SRS, the UE may follow procedure C. [Step C] For one set of CCs / BWPs, when the spatial relationship information (spatialRelationInfo) for the SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) is activated / updated by the MAC CE, then the applicable list of the CC is indicated by the simultaneous spatial update list (higher layer parameter simultaneousSpatial-UpdateList-r16 or simultaneousSpatial-UpdateListSecond-r16), and the spatial relationship information is applied to the SP or AP-SRS resources with the same SRS resource ID in all BWPs within the indicated CC. The spatial relation information (spatialRelationInfo) for the SP or AP-SRS resources configured by the SRS resource information element (higher layer parameter SRS-Resource) for one set of CC / BWP is activated / updated by the MAC CE only if the UE is not provided with multiple different values ​​of the CORESET pool index (CORESETPoolIndex) in the CORESET information element (ControlResourceSet) and is not provided with at least one TCI codepoint that maps to two TCI states.

[0037] The simultaneous TCI cell list (simultaneousTCI-CellList) and the simultaneous TCI update list (at least one of simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16) are lists of serving cells whose TCI relationships can be updated simultaneously using the MAC CE. simultaneousTCI-UpdateList1-r16 and simultaneousTCI-UpdateList2-r16 do not include the same serving cell.

[0038] The simultaneous spatial update list (at least one of the upper layer parameters simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16) is a list of serving cells whose spatial relationships can be updated simultaneously using the MAC CE. simultaneousSpatial-UpdatedList1-r16 and simultaneousSpatial-UpdatedList2-r16 do not contain the same serving cell.

[0039] Here, the simultaneous TCI update list and the simultaneous spatial update list are configured by the RRC, the CORESET pool index of the CORESET is configured by the RRC, and the TCI codepoint mapped to the TCI state is indicated by the MAC CE.

[0040] In the present disclosure, CC list, new CC list, simultaneous TCI cell list, simultaneousTCI-CellList, simultaneous TCI update list, simultaneousTCI-UpdateList1-r16, simultaneousTCI-UpdateList2-r16, simultaneous spatial update list, simultaneousSpatial-UpdatedList1-r16, simultaneousSpatial-UpdatedList2-r16 may be read as interchangeable.

[0041] In the present disclosure, simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList1-r16, and simultaneousTCI-UpdateList-r16 may be interchangeable. In the present disclosure, simultaneousTCI-UpdateList2, simultaneousTCI-UpdateList2-r16, and simultaneousTCI-UpdateListSecond-r16 may be interchangeable.

[0042] In the present disclosure, simultaneousSpatial-UpdatedList1, simultaneousSpatial-UpdatedList1-r16, and simultaneousSpatial-UpdateList-r16 may be interchangeable. In the present disclosure, simultaneousSpatial-UpdatedList2, simultaneousSpatial-UpdatedList2-r16, and simultaneousSpatial-UpdateListSecond-r16 may be interchangeable.

[0043] (Unified / Common TCI Framework) The unified TCI framework allows UL and DL channels to be controlled by a common framework. Instead of specifying TCI states or spatial relationships for each channel as in Rel. 15, the unified TCI framework may specify a common beam (common TCI state) and apply it to all UL and DL channels, or may apply a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

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

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

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

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

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

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

[0050] In the present disclosure, when N=M=X (X is any integer), it may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / instructed to the UE. Also, when N=X (X is any integer) and M=Y (Y may be any integer, Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (i.e., separate TCI states) (corresponding to Y TRPs) are notified / configured / instructed to the UE.

[0051] For example, when N=M=1 is written, this may mean that a TCI state common to one UL and DL for a single TRP is notified / configured / indicated to the UE (joint TCI state for a single TRP).

[0052] Also, for example, when N=1 and M=1, it may mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / configured / instructed to the UE (separate TCI states for a single TRP).

[0053] Also, for example, when N=M=2 is written, this may mean that a TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs is notified / configured / instructed to the UE (joint TCI state for multiple TRPs).

[0054] Also, for example, when N=2 and M=2, this may mean that the UE is notified / configured / instructed to have multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs (separate TCI states for multiple TRPs).

[0055] In the above example, the case where the values ​​of N and M are 1 or 2 has been described, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0056] Support for N=M=1 is being considered for Rel. 17. Support for other cases is being considered for Rel. 18 and later.

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

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

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

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

[0061] In the example of Figure 2B, the RRC parameters configure multiple TCI states (joint common TCI pools) for both DL and UL. The MAC CE may activate multiple TCI states (active TCI pools) from the configured multiple TCI states. Separate active TCI pools for UL and DL may be configured / activated.

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

[0063] The beam instruction DCI for the unified / common TCI state may be DCI format 1_1 / 1_2 with DL assignment (scheduling).

[0064] The beam instruction DCI for the unified / common TCI state may be DCI format 1_1 / 1_2 without DL assignment (scheduling) or a new DCI format, which is useful when there is no DL data but there is beam instruction for the unified / common TCI state.

[0065] (Uniform TCI State Pool in CA) In the unified TCI framework of Rel. 17, the following assumptions 1-1 to 1-4 are considered for the update and activation of the common TCI state ID to provide at least one of common QCL information for UE-dedicated PDCCH / PDSCH and common UL TX spatial filter for UE-dedicated PUSCH / PUCCH across multiple CC / multiple BWP sets.

[0066] [Assumption 1-1] The RRC-configured TCI state pool may be configured in the PDSCH-Config for each BWP / CC, as in Rel. 15 / 16. Such RRC-configured TCI state pool configuration does not imply that separate DL / UL TCI state pools are excluded or supported.

[0067] [Assumption 1-2] The RRC-configured TCI state pool may not be in the PDSCH configuration (PDSCH-Config) for each BWP / CC, but may be replaced by a reference to the RRC-configured TCI state pool in the reference BWP / CC. The RRC-configured TCI state pool is configured in the PDSCH configuration (PDSCH-Config) of the reference BWP / CC. For a BWP / CC whose PDSCH configuration includes a reference to the RRC-configured TCI state pool in the reference BWP / CC, the UE applies the RRC-configured TCI state pool in the reference BWP / CC.

[0068] [Assumption 1-3] If there is no BWP / CC ID (bwp-Id / cell) for a source RS of QCL type A / D in the QCL information (QCL-Info) of the TCI state, the UE assumes that source 1-RS of QCL type A / D is within the BWP / CC for which the TCI state applies.

[0069] [Assumption 1-4] A UE capability is introduced to report the maximum number of TCI state pools it supports across multiple BWPs and multiple CCs within a band, with candidate values ​​including at least 1.

[0070] In the unified TCI framework of Rel.17, the following assumptions 2-1 to 2-3 are considered for the update and activation of the common TCI state ID to provide at least one of common QCL information for UE-dedicated PDCCH / PDSCH and common UL TX spatial filter for UE-dedicated PUSCH / PUCCH across multiple CC / multiple BWP sets.

[0071] [Assumption 2-1] The source RS determined from the indicated common TCI state ID to provide a QCL type D indication to the target CC and determine the UL TX spatial filter may be configured in the target CC or another CC.

[0072] [Assumption 2-2] For intra-band CA, configurations 1 to 2 below may be supported without additional QCL rules. [[Configuration 1]] A single source RS across multiple CCs may be determined from a common TCI state ID indicated to provide QCL Type D indication and determine the UL TX spatial filter for a set of configured CCs. [[Configuration 2]] One source RS per CC may be determined from a common TCI State ID indicated for the set of configured CCs to provide QCL Type D indication and determine the UL TX spatial filter. Multiple CC-specific source RSs may be associated with the same QCL Type D RS.

[0073] [Assumption 2-3] The set of configured CC / BWPs includes all BWPs within the configured CC.

[0074] In a CA, a CC-specific TCI state pool / configuration (case 1) and a CC-common TCI state pool / configuration (case 2) may be supported.

[0075] [Case 1] 3A shows an example of a CC-specific TCI state pool. In this example, a TCI state list in a PDSCH configuration is configured for BWP1 in CC1, and a TCI state list in a PDSCH configuration is configured for BWP1 in CC2. One MAC CE / DCI indicates the TCI state ID.

[0076] [Case 2] 3B shows an example of a CC common TCI state pool. In this example, the TCI state list in the PDSCH configuration for BWP1 in CC1 is configured, and the TCI state list in the PDSCH configuration for BWP1 in CC2 is absent. One MAC CE / DCI indicates a TCI state ID (e.g., TCI state #2).

[0077] One TCI state information element (TCI-State) in the TCI state pool may include a TCI state ID, a QCL type 1 (QCL information, QCL-Info), and a QCL type 2 (QCL information, QCL-Info).

[0078] [Case 1] 4A shows an example in which a TCI state in a CC-specific TCI state pool indicates a CC-specific QCL Type D RS. QCL Type 1 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeA). QCL Type 2 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeD).

[0079] Figure 4B shows an example in which the TCI state in the CC-specific TCI state pool indicates a CC-common QCL Type D RS. QCL Type 1 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeA). QCL Type 2 includes a cell ID (cell=#1), a BWP ID (bwp-Id=#1), a reference signal (referenceSignal=NZP-CSI-RS#5), and a QCL type (qcl-Type=typeD).

[0080] [Case 2] 5A shows an example in which a TCI state in the CC-common TCI state pool indicates a CC-specific QCL Type D RS. QCL Type 1 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeA). QCL Type 2 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeD).

[0081] Figure 5B shows an example in which the TCI state in the CC-common TCI state pool indicates a CC-common QCL Type D RS. QCL Type 1 does not include a cell ID or BWP ID, but includes a reference signal (referenceSignal=NZP-CSI-RS#5) and a QCL type (qcl-Type=typeA). QCL Type 2 includes a cell ID (cell=#1), a BWP ID (bwp-Id=#1), a reference signal (referenceSignal=NZP-CSI-RS#5), and a QCL type (qcl-Type=typeD).

[0082] In both cases 1 and 2, the TCI state may indicate a CC-specific (BWP / CC-specific) RS (eg, a QCL Type A RS) on each BWP / CC.

[0083] [Case 1] 6A shows an example where TCI states in a CC-specific TCI state pool indicate CC-specific RSs: A TCI state set for BWP1 in CC1 indicates a CC-specific RS for BWP1 in CC1; a TCI state set for BWP1 in CC2 indicates a CC-specific RS for BWP1 in CC2.

[0084] [Case 2] 6B shows an example where a TCI state in a CC common TCI state pool indicates a CC-specific RS. The TCI state configured for BWP1 in CC1 indicates (the same RS ID of) a CC-specific RS for BWP1 in CC1 and a CC-specific RS for BWP1 in CC2. The TCI state configured for BWP1 in CC1 may not include a BWP / CC ID.

[0085] In both cases 1 and 2, the TCI state may indicate CC-common (BWP / CC-common) RS on each BWP / CC (eg, QCL type D RS of CSI-RS with repetition).

[0086] [Case 1] 7A shows an example where TCI states in a CC-specific TCI state pool indicate CC-common RSs: a TCI state set for BWP1 in CC1 indicates a CC-common RS for BWP1 in CC1, and a TCI state set for BWP1 in CC2 indicates the (same) CC-common RS for BWP1 in CC2.

[0087] [Case 2] 7B shows an example where a TCI state in the CC-common TCI state pool indicates a CC-common RS: The TCI state set for BWP1 in CC1 indicates a CC-common RS for all CCs / BWPs.

[0088] In the present disclosure, the TCI state may include QCL Type A RS / QCL Type D RS, or may include QCL Type A RS for frequency range (FR)1, or may include QCL Type A RS / QCL Type D RS for FR2.

[0089] (Multi-TRP PDSCH) In NR, one or more Transmission / Reception Points (TRPs) (multi-TRPs (MTRPs)) are considered to perform DL transmission to a UE using one or more panels (multi-panels). Also, it is considered that a UE performs UL transmission to one or more TRPs using one or more panels.

[0090] Note that multiple TRPs may correspond to the same cell identifier (ID), or different cell IDs. The cell ID may be a physical cell ID or a virtual cell ID.

[0091] Multi-TRPs (e.g., TRPs #1 and #2) may be connected by ideal / non-ideal backhauls to exchange information, data, etc. Each TRP of the multi-TRP may transmit a different code word (CW) and a different layer. Non-Coherent Joint Transmission (NCJT) may be used as a form of multi-TRP transmission.

[0092] In the NCJT, for example, TRP#1 performs modulation mapping and layer mapping on a first codeword to transmit a first PDSCH using a first number of layers (e.g., two layers) with a first precoding, and TRP#2 performs modulation mapping and layer mapping on a second codeword to transmit a second number of layers (e.g., two layers) with a second precoding.

[0093] Note that multiple PDSCHs (multi-PDSCHs) that are non-coherent may be defined as partially or completely overlapping in at least one of the time and frequency domains, i.e., a first PDSCH from a first TRP and a second PDSCH from a second TRP may overlap in at least one of the time and frequency resources.

[0094] The first PDSCH and the second PDSCH may be assumed to be not quasi-co-located (Quasi-Co-Location (QCL)). Reception of multiple PDSCHs may be interpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0095] Multiple PDSCHs from multiple TRPs (which may also be referred to as multiple PDSCHs) may be scheduled using one DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from multiple TRPs may also be scheduled using multiple DCIs (multiple DCI, multiple PDCCHs) (multi-master mode, multi-DCI based multi-TRP).

[0096] In Ultra-Reliable and Low Latency Communications (URLLC) for multiple TRPs, it is considered that PDSCH (transport block (TB) or codeword (CW)) repetition across multiple TRPs is supported. Repetition schemes (URLLC schemes, reliability enhancement schemes, e.g., schemes 1a, 2a, 2b, 3, and 4) across multiple TRPs in the frequency domain, layer (spatial) domain, or time domain are considered to be supported. In scheme 1a, multiple PDSCHs from multiple TRPs are space division multiplexed (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are frequency division multiplexed (FDM). In scheme 2a, the redundancy version (RV) is the same for multiple TRPs. In scheme 2b, the RVs for multiple TRPs may be the same or different. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are time division multiplexed (TDM). In scheme 3, multiple PDSCHs from multiple TRPs are transmitted in one slot. In scheme 4, multiple PDSCHs from multiple TRPs are transmitted in different slots.

[0097] Such a multi-TRP scenario allows for more flexible transmission control using good quality channels.

[0098] To support intra-cell (having the same cell ID) and inter-cell (having different cell IDs) multi-TRP transmission based on multiple PDCCHs, in the RRC configuration information for linking multiple pairs of PDCCHs and PDSCHs with multiple TRPs, one control resource set (CORESET) in the PDCCH configuration information (PDCCH-Config) may correspond to one TRP.

[0099] If at least one of the following conditions 1 and 2 is satisfied, the UE may determine that the transmission is a multi-TRP transmission based on the multi-DCI transmission. In this case, the TRP may be replaced with a CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​of the CORESET pool index (for example, 0 and 1) are set.

[0100] If the following condition is met, the UE may determine that the state is multi-TRP based on a single DCI, in which case the two TRPs may be interpreted as two TCI states indicated by the MAC CE / DCI. [conditions] "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to indicate one or two TCI states for one codepoint of the TCI field in the DCI.

[0101] The DCI for common beam instruction may be a UE-specific DCI format (e.g., DL DCI format (e.g., 1_1, 1_2), UL DCI format (e.g., 0_1, 0_2)), or may be a UE-group common DCI format.

[0102] (Unified TCI Framework for Carrier Aggregation (CA)) The introduction of a unified TCI state framework for CA is being considered for NR Rel. 17 and later. The common TCI state indicated to the UE is expected to be common across CCs (cells) (at least between CCs, QCL type D). This is because the existing specifications (Rel. 15 / 16) do not support simultaneous reception of different DL channels / RSs in QCL type D, or simultaneous transmission of UL channels / RSs with different spatial relationships, except for cases such as transmission and reception using multiple TRPs.

[0103] In addition, in the unified TCI framework, common TCI state ID update / activation is being considered to provide common QCL information / common UL transmit spatial filter across a set of configured CCs.

[0104] The following options 1 and 2 are being considered for the TCI state pool for CA.

[0105] [Option 1] A single TCI state pool configured by RRC for a set of configured multiple CCs (cells) / BWPs may be shared (configured). For example, a cell group TCI state may be defined, or the TCI state pool for PDSCH in the reference cell may be reused. In the TCI state, there may be no CC (cell) ID for the QCL type-A RS, and the CC (cell) ID for the QCL type-A RS may be determined according to the target CC (cell) of the TCI state.

[0106] In option 1, a common TCI state pool is configured for each of multiple CC / BWPs, so that when one common TCI state is indicated in the MAC CE / DCI, the indicated common TCI state may be applied to all CC / BWPs (all CC / BWPs included in the pre-configured CC / BWP list).

[0107] [Option 2] For each individual CC, a TCI state pool may be configured by the RRC.

[0108] In Option 2, as in Rel. 16, the applicable CC / BWP list for simultaneous beam updates is pre-configured by RRC, and if a beam update is performed in MAC CE / DCI for any CC / BWP included in the CC / BWP list, the update may be applied to all CC / BWPs.

[0109] In option 1, a common TCI state pool is configured (shared) by RRC for multiple CCs, the TCI states in the common TCI state pool are indicated by a common TCI state ID, and one RS determined based on that TCI state is used to indicate QCL type D across the set of multiple configured CCs (Constraint 1).

[0110] In option 2, a separate common TCI state pool is configured by RRC for each CC, the TCI states in the common state pool are indicated by a common TCI state ID, and one RS determined based on the TCI state is used to indicate QCL type D across the set of multiple configured CCs (Constraint 2).

[0111] (beam application time(BAT)) In the DCI-based beam indication in Rel. 17, the following considerations 1 and 2 are being considered regarding the application time (BAT) of the beam / unified TCI status indication.

[0112] [Consideration 1] It is contemplated that the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the acknowledgement (ACK) for the joint or separate DL / UL beam indication. It is contemplated that the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the ACK / negative acknowledgement (NACK) for the joint or separate DL / UL beam indication. Y symbols may be configured by the base station based on the UE capabilities. The UE capabilities may be reported on a symbol-by-symbol basis.

[0113] According to Study 1, the BAT is determined based on the Y symbol, but if the SCS differs among multiple CCs, the value of the Y symbol also differs, and therefore the BAT differs among multiple CCs.

[0114] [Consideration 2] For the CA case, the application time of the beam instruction may follow any of the following options 1 to 3. [Option 1] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam direction applies. [Option 2] Both the first slot and Y symbol are determined on the carrier with the smallest SCS among the one or more carriers to which the beam direction applies and the UL carrier carrying the ACK. [Option 3] Both the first slot and Y symbols are determined on the UL carrier that carries the ACK.

[0115] As part of the CC simultaneous beam update function in Rel. 17, the sharing of beams between multiple CCs in CA is being considered. According to Study 2, the BAT between multiple CCs will be shared.

[0116] (Radio Link Monitoring (RLM)) In NR, Radio Link Monitoring (RLM) is used.

[0117] In NR, a base station may configure a Radio Link Monitoring Reference Signal (Radio Link Monitoring RS (RLM-RS)) for a UE for each BWP using higher layer signaling. The UE may receive configuration information for RLM (e.g., the "RadioLinkMonitoringConfig" information element of RRC).

[0118] The configuration information for the RLM may include fault detection resource configuration information (e.g., the upper layer parameter "failureDetectionResourcesToAddModList") and parameters related to the RLM-RS (e.g., the upper layer parameter "RadioLinkMonitoringRS").

[0119] The parameters related to the RLM-RS may include information indicating that it corresponds to the purpose of RLM, an index corresponding to the resource of the RLM-RS (e.g., an index included in the upper layer parameter "failureDetectionResources" (RadioLinkMonitoringRS in failureDetectionResourcesToAddModList)), etc. The index may be, for example, an index of the CSI-RS resource configuration (e.g., a non-zero power CSI-RS resource ID) or an SS / PBCH block index (SSB index). The purpose information may indicate a beam failure, a (cell-level) Radio Link Failure (RLF), or both.

[0120] The UE may identify the RLM-RS resource based on the index corresponding to the resource of the RLM-RS, and perform RLM using the RLM-RS resource.

[0121] In the Rel. 16 RLM procedure, the UE follows the following implicit RLM-RS determination (implicit RS determination) procedure.

[0122] [Implicit RLM-RS determination procedure] If the UE is not provided with a Radio Link Monitoring RS (RLM-RS) and the UE is provided with a TCI state including one or more CSI-RS for PDCCH reception, the UE shall follow steps 1 to 4 below.

[0123] Step 1 If the active TCI state for PDCCH reception includes only one RS, the UE uses the RS provided for the active TCI state for PDCCH reception for RLM. Step 2 If the active TCI state for PDCCH reception includes two RSs, the UE assumes that one RS has QCL type D, and the UE uses that RS with QCL type D for RLM. The UE does not assume that both RSs have QCL type D. Step 3 The UE is not required to use aperiodic or semi-persistent RS for RLM. Step 4 L max For =4, the UE selects N provided for the active TCI state for PDCCH reception in the multiple CORESETs associated with the multiple search space sets in order of the smallest monitoring periodicity. RLM If more than one CORESET is associated with multiple search space sets with the same monitoring period, the UE determines the order of the CORESETs from the highest CORESET index.

[0124] where L maxis the maximum number of SS / PBCH block indexes in a cell. The maximum number of SS / PBCH blocks transmitted in a half-frame is L max is.

[0125] In this way, if the UE is not provided with an RLM-RS, the UE makes an implicit RLM-RS decision and uses the active TCI state for PDCCH reception for RLM. max If = 4, the UE first sorts the search space sets in ascending order of monitoring period, then in descending order of CORESET index, N RLM Select RS. Select CORESET.

[0126] The UE must be connected to the N LR-RLM Up to N RLM-RSs can be configured. LR-RLM From RLM-RS, L max Depends on N RLM Up to RLM-RSs are used for RLM. In Rel. 16, as shown in Figure 1, max N if =4 RLM = 2, and L max N when =8 RLM = 4, and L max = 64, N RLM =8.

[0127] (Beam Failure Detection(BFD) / Beam Failure Recovery(BFR)) In NR, communication is performed using beamforming. For example, a UE and a base station (e.g., a gNB (gNodeB)) may use a beam used to transmit a signal (also called a transmit beam or Tx beam) and a beam used to receive a signal (also called a receive beam or Rx beam).

[0128] When beamforming is used, it is expected that radio link quality will deteriorate due to increased susceptibility to interference from obstacles. This deterioration in radio link quality may lead to frequent radio link failures (RLF). Since RLF requires cell reconnection, frequent RLF occurrences will result in a degradation of system throughput.

[0129] In NR, in order to suppress the occurrence of RLF, when the quality of a specific beam deteriorates, a procedure for switching to another beam (which may also be called Beam Recovery (BR), Beam Failure Recovery (BFR), or L1 / L2 (Layer 1 / Layer 2) beam recovery) is performed. The BFR procedure may also be simply called BFR.

[0130] Note that a beam failure (BF) in this disclosure may also be referred to as a link failure.

[0131] 8 is a diagram showing an example of a beam recovery procedure in Rel.15 NR. The number of beams is merely an example and is not limited to this. In the initial state (step S101), the UE performs measurements based on Reference Signal (RS) resources transmitted using two beams.

[0132] The RS may be at least one of a Synchronization Signal Block (SSB) and a Channel State Information RS (CSI-RS). The SSB may also be called an SS / PBCH (Physical Broadcast Channel) block.

[0133] The RS may be at least one of a Primary Synchronization Signal (PSS), a Secondary Synchronization Signal (SSS), a Mobility Reference Signal (MRS), a signal included in an SSB, an SSB, a CSI-RS, a Demodulation Reference Signal (DMRS), a beam-specific signal, etc., or a signal configured by extending or modifying any of these. The RS measured in step S101 may also be called an RS for beam failure detection (Beam Failure Detection RS (BFD-RS)), an RS for use in a beam recovery procedure (BFR-RS), etc.

[0134] In step S102, the UE cannot detect the BFD-RS (or the reception quality of the RS is degraded) due to radio wave jamming from the base station. Such jamming can be caused by, for example, obstacles, fading, interference, etc. between the UE and the base station.

[0135] The UE detects a beam failure when a predetermined condition is met. The UE may detect the occurrence of a beam failure, for example, when the Block Error Rate (BLER) is less than a threshold for all configured BFD-RS (BFD-RS resource configurations). When the occurrence of a beam failure is detected, the lower layer (physical (PHY) layer) of the UE may notify (indicate) a beam failure instance to the upper layer (MAC layer).

[0136] The criteria for the determination are not limited to BLER, but may be Layer 1 Reference Signal Received Power (L1-RSRP) in the physical layer. Also, instead of or in addition to RS measurement, beam failure detection may be performed based on a downlink control channel (PDCCH). The BFD-RS may be expected to be quasi-co-located (QCL) with the DMRS of the PDCCH monitored by the UE.

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

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

[0139] Information about BFD-RS (e.g., RS index, resource, number, number of ports, precoding, etc.), information about beam fault detection (BFD) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. Information about BFD-RS may also be referred to as information about BFR resources, etc.

[0140] When a higher layer (e.g., MAC layer) of the UE receives a beam failure instance notification from the PHY layer of the UE, it may start a predetermined timer (which may be called a beam failure detection timer). If the MAC layer of the UE receives a certain number of beam failure instance notifications (e.g., beamFailureInstanceMaxCount configured by RRC) before the timer expires, it may trigger a BFR (e.g., start one of the random access procedures described below).

[0141] If there is no notification from the UE, or if the base station receives a predetermined signal (beam recovery request in step S104) from the UE, the base station may determine that the UE has detected a beam failure.

[0142] In step S103, the UE starts searching for a new candidate beam (candidate beam detection (CBD)) to be used for new communication in order to recover the beam. The UE may select a new candidate beam corresponding to a predetermined RS by measuring the RS. The RS measured in step S103 may be called a new candidate RS, an RS for new candidate beam identification, an NCBI-RS (New Candidate Beam Identification RS), an RS for new beam identification, an RS for new beam identification, an NBI-RS (New Beam Identification RS), a CBI-RS (Candidate Beam Identification RS), a CB-RS (Candidate Beam RS), a candidate beam detection RS (CBD-RS), or the like. The NBI-RS may be the same as or different from the BFD-RS. Note that the new candidate beam may simply be called a candidate beam or candidate RS.

[0143] The UE may determine a beam corresponding to an RS that satisfies a predetermined condition as a new candidate beam (new beam, q_new). The UE may determine a new candidate beam, for example, based on an RS among the configured NBI-RSs whose L1-RSRP exceeds a threshold. Note that the criteria for determination are not limited to L1-RSRP. The L1-RSRP for SSB may be called SS-RSRP. The L1-RSRP for CSI-RS may be called CSI-RSRP.

[0144] Information about the NBI-RS (e.g., RS resources, number of ports, precoding, etc.), information about new beam identification (NBI) (e.g., the above-mentioned threshold), etc. may be configured (notified) to the UE using higher layer signaling, etc. Information about the new candidate RS (or NBI-RS) may be acquired based on information about the BFD-RS. Information about the NBI-RS may be referred to as information about resources for NBI, etc.

[0145] Note that BFD-RS, NBI-RS, etc. may be interchangeably read as Radio Link Monitoring RS (RLM-RS).

[0146] In step S104, the UE that has identified the new candidate beam transmits a beam failure recovery request (BFRQ). The beam recovery request may also be called a beam recovery request signal, a beam failure recovery request signal, or the like.

[0147] The BFRQ may be transmitted using, for example, at least one of an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), an uplink shared channel (Physical Uplink Shared Channel (PUSCH)), and a configured grant (CG) PUSCH.

[0148] The BFRQ may include information of the new candidate beam / new candidate RS identified in step S103. Resources for the BFRQ may be associated with the new candidate beam. The beam information may be notified using a beam index (BI), a port index of a predetermined reference signal, an RS index, a resource index (e.g., a CSI-RS resource indicator (CRI) or an SSB resource indicator (SSBRI)), etc.

[0149] In Rel. 15 NR, contention-based BFR (CB-BFR), which is a BFR based on a contention-based random access (RA) procedure, and contention-free BFR (CF-BFR), which is a BFR based on a contention-free random access procedure, are under consideration. In CB-BFR and CF-BFR, a UE may transmit a preamble (also referred to as an RA preamble, a random access channel (Physical Random Access Channel (PRACH)), a RACH preamble, etc.) as a BFRQ using a PRACH resource.

[0150] In CB-BFR, a UE may transmit a preamble randomly selected from one or more preambles. In CF-BFR, a UE may transmit a preamble assigned specifically to the UE by the base station. In CB-BFR, a base station may assign the same preamble to multiple UEs. In CF-BFR, a base station may assign a preamble individually to each UE.

[0151] Note that CB-BFR and CF-BFR may be referred to as CB PRACH-based BFR (CBRA-BFR) and CF PRACH-based BFR (CFRA-BFR), respectively. CBRA-BFR may be referred to as CBRA for BFR. CFRA-BFR may be referred to as CFRA for BFR.

[0152] Regardless of whether CB-BFR or CF-BFR is used, information about the PRACH resource (RA preamble) may be notified by, for example, higher layer signaling (such as RRC signaling). For example, the information may include information indicating a correspondence relationship between the detected DL-RS (beam) and the PRACH resource, and a different PRACH resource may be associated with each DL-RS.

[0153] In step S105, the base station that has detected the BFRQ transmits a response signal (which may be referred to as a gNB response, etc.) to the BFRQ from the UE. The response signal may include reconfiguration information (e.g., DL-RS resource configuration information) for one or more beams.

[0154] The response signal may be transmitted, for example, in the UE common search space of the PDCCH. The response signal may be signaled using a PDCCH (DCI) scrambled with a cyclic redundancy check (CRC) by a UE identifier (e.g., a Cell-Radio RNTI (C-RNTI)). The UE may determine at least one of a transmit beam and a receive beam to use based on the beam reconfiguration information.

[0155] The UE may monitor the response signal based on at least one of a control resource set (CORESET) for BFR and a search space set for BFR.

[0156] For CB-BFR, contention resolution may be determined to be successful if the UE receives a PDCCH corresponding to the C-RNTI associated with the UE.

[0157] Regarding the process of step S105, a period for the UE to monitor a response to the BFRQ from a base station (e.g., a gNB) may be set. This period may be referred to as, for example, a gNB response window, a gNB window, a beam recovery request response window, etc. If no gNB response is detected within this window period, the UE may retransmit the BFRQ.

[0158] In step S106, the UE may transmit a message indicating that the beam reconfiguration is complete to the base station. The message may be transmitted, for example, via the PUCCH or the PUSCH.

[0159] A beam recovery success (BR success) may indicate, for example, that step S106 has been reached, whereas a beam recovery failure (BR failure) may indicate, for example, that a predetermined number of BFRQ transmissions have been made or that a beam-failure-recovery-timer has expired.

[0160] Rel.15 supports the use of a random access procedure to perform beam recovery procedures (e.g., BFRQ notification) for beam failures detected in an SpCell (PCell / PSCell). On the other hand, Rel.16 supports the use of at least one of PUCCH (e.g., Scheduling Request (SR)) transmission for BFR and MAC CE (e.g., UL-SCH) transmission for BFR to perform beam recovery procedures (e.g., BFRQ notification) for beam failures detected in an SCell.

[0161] For example, the UE may transmit information about beam failure using MAC CE-based two-step. The information about beam failure may include information about the cell that detected the beam failure and information about new candidate beams (or new candidate RS indices).

[0162] [Step 1] If a BF is detected, a PUCCH-BFR (scheduling request (SR)) may be transmitted from the UE to the PCell / PSCell. Then, an UL grant (DCI) for step 2 below may be transmitted from the PCell / PSCell to the UE. If a beam failure is detected and there is a MAC CE (or UL-SCH) for transmitting information about a new candidate beam, step 1 (e.g., PUCCH transmission) may be omitted and step 2 (e.g., MAC CE transmission) may be performed.

[0163] [Step 2] Then, the UE may transmit information about the cell where beam failure was detected (failed) (e.g., cell index) and information about the new candidate beam to the base station (PCell / PSCell) via an uplink channel (e.g., PUSCH) using MAC CE. After that, through the BFR procedure, the QCL of the PDCCH / PUCCH / PDSCH / PUSCH may be updated to the new beam after a predetermined period (e.g., 28 symbols) after receiving a response signal from the base station.

[0164] Note that the numbers of these steps are for explanatory purposes only, and multiple steps may be combined or the order may be reversed. Furthermore, whether to perform BFR may be configured in the UE using higher layer signaling.

[0165] (BFD-RS / NBI-RS) In BFD, the UE may be configured with an explicit BFD-RS (e.g., SSB / CSI-RS) through higher layer signaling or the like. Alternatively, in BFD, the UE may be configured with an implicit BFD-RS based on the TCI state of PDCCH / CORESET (the UE may determine the BFD-RS based on the TCI state). Also, in BFR, the UE may be configured with an explicit NBI-RS (e.g., SSB / CSI-RS) through higher layer signaling or the like. Explicit BFD-RS, implicit BFD-RS, explicit NBI-RS, etc. will be specifically described below.

[0166] In Rel. 16, for each BWP of a serving cell, a UE may be provided with a set of periodic (P)-CSI-RS resource configuration indices (q0) via a failure detection resource list (failureDetectionResourcesToAddModList) for radio link quality measurements on that BWP of the serving cell. For each BWP of a serving cell, a UE may be provided with at least one set of P-CSI-RS resource configuration indices and SS / PBCH block indices (q1) via a candidate beam RS list (candidateBeamRSList), an extended candidate beam RS list (candidateBeamRSListExt), or a candidate beam RS list for an SCell (candidateBeamRSSCellList) for radio link quality measurements on that BWP of the serving cell.

[0167] A q0 bar is written as "q0" with an overline. Hereinafter, a q0 bar will be written simply as "q0." A q1 bar is written as "q1" with an overline. Hereinafter, a q1 bar will be written simply as "q1."

[0168] The set q0 of P-CSI-RS resources provided by the failure detection resources may be referred to as explicit BFD-RS, and the set q1 may be referred to as explicit New Beam Identification (NBI)-RS.

[0169] In other words, the UE can be explicitly configured with a BFD-RS set q0 for per-cell BFR.

[0170] The UE may perform L1-RSRP measurements, etc., using RS resources corresponding to indices included in at least one of set q0 and set q1 to detect beam failure.

[0171] In the present disclosure, providing the above-described higher layer parameters indicating information on indexes corresponding to BFD resources may be interchangeable with configuring BFD resources, configuring BFD-RS, etc. In the present disclosure, BFD resources, periodic CSI-RS resource configuration index, or SSB index set q0, BFD-RS may be interchangeable.

[0172] If the UE is not provided with q0 by failure detection resources (failureDetectionResources) for one BWP of its serving cell, it determines to include in set q0 a P-CSI-RS resource configuration index that has the same value as an RS index in the RS set indicated by the TCI-State (TCI-State) for the corresponding CORESET that the UE uses to monitor the PDCCH. If there are two RS indices in one TCI state, set q0 includes RS indices that have a QCL type D configuration for the corresponding TCI state. The UE assumes that set q0 includes up to two RS indices. The UE assumes single-port RSs in set q0.

[0173] This set q0 may be called the implicit BFD-RS.

[0174] The physical layer in the UE measures the radio link quality according to the set of resource configurations q0 by a threshold Q out,LRFor set q0, the UE evaluates the radio link quality only according to the SS / PBCH blocks on the PCell or PSCell quasi-colocated with the DM-RS of the PDCCH reception monitored by the UE or the P-CSI-RS resource configuration quasi-colocated with the DM-RS of the PDCCH reception monitored by the UE.

[0175] In other words, for set q0, the UE evaluates the radio link quality according to the DMRS of PDCCH / CORESET and the QCL'd BFD-RS.

[0176] (Per-cell BFR and per-TRP BFR) The BFR described above (Rel. 15 / 16) is performed for each cell, so it may be called per-cell BFR. In contrast, BFR performed for each TRP is being considered.

[0177] It is considered that new RRC configuration parameters (e.g., TRP-ID, group ID, new ID, etc.) are configured for single DCI-based multi-TRP. The new RRC configuration parameters may follow either of the following options 1 and 2. [Option 1] Each CORESET is associated with a new ID. If two sets of BFD-RS for per-TRP BFR are configured by the upper layer, the BFD-RS and QCL-enabled CORESETs in one set may be associated with the same new ID, and the BFD-RS and QCL-enabled CORESETs in a different set may be associated with different new IDs. [Option 2] Each TCI state is associated with a new ID. If two sets of BFD-RS for per-TRP BFR are configured by higher layers, the BFD-RS and QCL'd TCI states / CORESETs in one set may be associated with the same new ID, and the BFD-RS and QCL'd TCI states / CORESETs in a different set may be associated with different new IDs.

[0178] Explicit BFD-RS set configuration considering CORESET with two TCI states and / or single DCI-based multi-TRP has not been fully explored.

[0179] Regarding the explicit BFD-RS set configuration, the following cases #1 to #5 are considered: [Case #1] In single cell / single TRP operation, one BFD-RS set is configured for per-cell BFR when using SFN CORESET with two TCI states. [Case #2] In single DCI based multi-TRP operation, one BFD-RS set is configured for per-cell BFR when all CORESETs are with one TCI state. [Case #3] In single DCI based multi-TRP operation, up to two BFD-RS sets are configured for per-TRP BFR where every CORESET has one TCI state. [Case #4] In single DCI based multi-TRP operation, one BFD-RS set is configured for per-cell BFR when using SFN CORESET with two TCI states. [Case #5] In single DCI based multi-TRP operation, up to two BFD-RS sets are configured for per-TRP BFR when using an SFN CORESET with two TCI states.

[0180] The SFN PDCCH scheme 1 is being considered to include HST and URLLC. In the present disclosure, the SFN PDCCH scheme 1, the SFN PDCCH scheme, the SFN PDCCH, and the TRP-based pre-compensation scheme may be read as each other.

[0181] For implicit BFD-RS, the SFN PDCCH scheme may include both one and two TCI states. If the SFN PDCCH scheme is set and two TCI states are activated for at least one CORESET, it is being considered that the RS of the CORESET with one and two TCI states is used for the implicit setting of the RS for BFD.

[0182] (Transmission Power Control) <PUSCH Transmission Power Control> In NR, the transmission power of PUSCH is controlled based on the TPC command (also referred to as value, increment / decrement value, correction value, etc.) indicated by the value of the field (also referred to as TPC command field, etc.) in DCI.

[0183] For example, when the UE transmits PUSCH on the active UL BWP b of carrier f of serving cell c using the parameter set (open-loop parameter set) with index j and the index l of the power control adjustment state (PUSCH power control adjustment state), the transmission power (P PUSCH、b,f,c (i,j,q d ,l)) [dBm] of PUSCH at the PUSCH transmission occasion (also referred to as transmission period, etc.) i is P CMAX,f,c(i) , P O_PUSCH,b,f,c (j), M PUSCH RB,b,f,c (i), α b,f,c (j), PL b,f,c (q d ), Δ TF,b,f,c (i), f b,f,c(i, l), may be based on at least one of:

[0184] The power control adjustment state may be referred to as a closed loop (CL)-power control (PC) state, a value based on TPC commands of a power control adjustment state index l, an accumulated value of TPC commands, or a value due to a closed loop. l may also be referred to as a closed loop index.

[0185] Furthermore, the PUSCH transmission opportunity i is a period during which the PUSCH is transmitted, and may be configured, for example, by one or more symbols, one or more slots, or the like.

[0186] P CMAX,f,c(i) is, for example, the transmission power of the user terminal (also referred to as maximum transmission power, UE maximum output power, etc.) set for carrier f of serving cell c at transmission opportunity i.

[0187] P O_PUSCH,b,f,c (j) is a parameter related to the target received power (e.g., a parameter related to the transmit power offset, also referred to as a transmit power offset P0, a target received power parameter, etc.) set for the active UL BWP b of the serving cell c on the carrier f at the transmission opportunity i. O_UE_PUSCH,b,f,c (j) is P O_NOMINAL_PUSCH,f,c (j) and P O_UE_PUSCH,b,f,c It may be a sum of (j).

[0188] M PUSCH RB,b,f,c (i) is the number of resource blocks (bandwidth) allocated to PUSCH for transmission opportunity i in active UL BWP b of carrier f with serving cell c and subcarrier spacing μ. b,f,c (j) is a value provided by a higher layer parameter (e.g., also called msg3-Alpha, p0-PUSCH-Alpha, fractional factor, etc.).

[0189] PL b,f,c (q d) is, for example, the index q of the reference signal (RS, path loss reference RS, pathloss (PL)-RS, path loss reference RS, DL-RS for path loss measurement, PUSCH-PathlossReferenceRS) for the downlink BWP associated with the active UL BWP b of the carrier f of the serving cell c. d is the path loss (path loss estimation [dB], path loss compensation) calculated at the user terminal using

[0190] If the UE is not provided with a pathloss reference RS (e.g., PUSCH-PathlossReferenceRS) or if the UE is not provided with individual upper layer parameters, the UE may use RS resources from the synchronization signal (SS) / physical broadcast channel (PBCH) block (SS block (SSB)) used to obtain the Master Information Block (MIB) to derive the PL. b,f,c (q d ) may be calculated.

[0191] When the UE is configured with a number of RS resource indices up to the value of the maximum number of pathloss reference RSs (e.g., maxNrofPUSCH-PathlossReferenceRSs) and a set of RS configurations for the RS resource indices according to the pathloss reference RSs, the set of RS resource indices may include one or both of a set of SS / PBCH block indices and a set of channel state information (CSI)-reference signal (RS) resource indices. The UE may select RS resource index q in the set of RS resource indices. d may be identified.

[0192] If a PUSCH transmission is scheduled by a Random Access Response (RAR) UL grant, the UE uses the same RS resource index q as for the corresponding PRACH transmission. d may also be used.

[0193] When a UE is provided with a power control configuration for a PUSCH by a sounding reference signal (SRS) resource indicator (SRI) (e.g., SRI-PUSCH-PowerControl) and with one or more values ​​of the ID of the pathloss reference RS, the UE may obtain a mapping between a set of values ​​for the SRI field in DCI format 0_1 ​​and a set of ID values ​​of the pathloss reference RS from higher layer signaling (e.g., sri-PUSCH-PowerControl-Id in SRI-PUSCH-PowerControl). The UE may obtain an RS resource index q from the ID of the pathloss reference RS mapped to the SRI field value in DCI format 0_1 ​​that schedules the PUSCH. d may be determined.

[0194] If a PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with PUCCH spatial relationship information for the PUCCH resource with the lowest index for the active UL BWP b of each carrier f and serving cell c, the UE shall select the PUCCH resource with the same RS resource index q as the PUCCH transmission in that PUCCH resource. d may also be used.

[0195] If the PUSCH transmission is scheduled by DCI format 0_0 and the UE is not provided with spatial settings for PUCCH transmission, or if the PUSCH transmission is scheduled by DCI format 0_1 ​​that does not include an SRI field, or if the UE is not provided with settings for PUSCH power control by SRI, the UE shall select RS resource index q with an ID of a path loss reference RS of zero. d may also be used.

[0196] For PUSCH transmission configured by a configured grant configuration (e.g., ConfiguredGrantConfig), if the configured grant configuration includes a specific parameter (e.g., rrc-ConfiguredUplinkGrant), the RS resource index q is determined by the path loss reference index (e.g., pathlossReferenceIndex) in the specific parameter. d may be provided to the UE.

[0197] For the PUSCH transmission configured by the configuration grant configuration, if the configuration grant configuration does not include a specific parameter, the UE shall determine the RS resource index q from the value of the ID of the path loss reference RS mapped to the SRI field in the DCI format that activates the PUSCH transmission. d If the DCI format does not include an SRI field, the UE may determine an RS resource index q with the ID of the path loss reference RS set to zero. d may be determined.

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

[0199] f b,f,c (i,l) is the PUSCH power control adjustment state for the active UL BWP b of carrier f of serving cell c at transmission opportunity i. b,f,c (i,l) is δ PUSCH,b,f,c It may be based on (i,l).

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

[0201] If TPC accumulation is disabled, f b,f,c (i,l) is δ PUSCH,b,f,cIt may be (i,l) (absolute value).

[0202] If information indicating that TPC accumulation is disabled (TPC-Accumulation) is not set (if information indicating that TPC accumulation is disabled is not provided, and TPC accumulation is set to enabled), the UE accumulates TPC command values ​​and determines the transmit power based on the accumulation result (power control state) (applies the TPC command values ​​via accumulation).

[0203] When information indicating that TPC accumulation is disabled (TPC-Accumulation) is set (when information indicating that TPC accumulation is disabled is provided, or when TPC accumulation is set to disabled), the UE does not accumulate TPC command values ​​and determines the transmission power based on the TPC command values ​​(power control state) (applies the TPC command values ​​without using accumulation).

[0204] δ PUSCH,b,f,c (i,l) may be a TPC command value included in DCI format 0_0 or DCI format 0_1 ​​that schedules a PUSCH transmission opportunity i on active UL BWP b of carrier f of serving cell c, or a TPC command value jointly coded with other TPC commands in DCI format 2_2 with a CRC scrambled by a specific Radio Network Temporary Identifier (RNTI) (e.g., TPC-PUSCH-RNTI).

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

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

[0207] The power control adjustment state may be set to have a plurality of states (e.g., two states) or a single state by upper layer parameters. Also, when a plurality of power control adjustment states are set, one of the plurality of power control adjustment states may be identified by an index l (e.g., l ∈ {0, 1}).

[0208] <PUCCH Transmission Power Control> In NR, the transmission power of the PUCCH is controlled based on the TPC command (also referred to as value, increase / decrease value, correction value, indication value, etc.) indicated by the value of the field (also referred to as TPC command field, first field, etc.) in the DCI.

[0209] For example, the power control adjustment state index l is used to calculate the PUCCH transmission power (P PUCCH、b,f,c (i,q u ,q d ,l))[dBm] is P CMAX,f,c (i), P O_PUCCH,b,f,c (q u ), M PUCCH RB,b,f,c (i), P.L. b,f,c (q d ), Δ F_PUCCH (F), Δ TF,b,f,c (i), g b,f,c (i, l), may be based on at least one of:

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

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

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

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

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

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

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

[0217] If TPC accumulation is enabled, g b,f,c (i,l) is δ PUCCH,b,f,c It may be based on the cumulative value of (i,l).

[0218] If TPC accumulation is disabled, g b,f,c (i,l) is δ PUCCH,b,f,c It may be (i,l) (absolute value).

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

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

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

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

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

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

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

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

[0227] If the UE is provided with pathloss reference RSs (pathlossReferenceRSs) but not with PUCCH spatial relation information (PUCCH-SpatialRelationInfo), the UE derives the value of the reference signal (referenceSignal) in the PUCCH pathloss reference RS from the PUCCH pathloss reference RS-ID (pucch-PathlossReferenceRS-Id) with index 0 in the PUCCH pathloss reference RS (PUCCH-PathlossReferenceRS). The derived RS resource is on the primary cell or, if pathloss reference linking (pathlossReferenceLinking) is provided, on the serving cell indicated by the value of pathloss reference linking.

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

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

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

[0231] <SRS Transmission Power Control> For example, using the index l of the power control adjustment state, the transmission power (P SRS、b,f,c (i,q s ,l)) of the SRS in the SRS transmission occasion (also referred to as a transmission period, etc.) i for the active UL BWP b of the carrier f of the serving cell c may be based on at least one of P CMAX,f,c (i), P O_SRS,b,f,c (q s ), M SRS,b,f,c (i), α SRS,b,f,c (q s ), PL b,f,c (q d ), h b,f,c (i,l).

[0232] Also, the SRS transmission occasion i is a period during which the SRS is transmitted, and may be composed of, for example, one or more symbols, one or more slots, etc.

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

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

[0235] α SRS,b,f,c (q s ) is the active UL BWP b of serving cell c and carrier f with subcarrier spacing μ and SRS resource set q s and α (e.g., alpha) for

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

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

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

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

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

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

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

[0243] (QCL rules) The unified TCI state in Rel.17 (indicated / updated by MAC CE / DCI in Rel.17) may or may not be shared with UE-dedicated reception on PDSCH / PDCCH.

[0244] The QCL rules for the Rel. 17 unified TCI state may differ depending on whether the Rel. 17 unified TCI state is shared with UE-specific reception on the PDSCH / PDCCH. For example, for DL ​​channels / RSs that do not share the same Rel. 17 unified TCI state as UE-specific reception on the PDSCH / PDCCH, all QCL rules specified in existing specifications (Options B1 to B3, described below) may be supported. For example, for DL ​​channels / RSs that share the same Rel. 17 unified TCI state as UE-specific reception on the PDSCH / PDCCH, at least one QCL rule from Options A1 and A2 below may be supported for the source RS and QCL type. [Option A1] A tracking RS (TRS) is configured for the QCL type A source RS, and a CSI-RS for beam management (BM) (CSI-RS with repetition) is configured for the QCL type D source RS. [Option A2] A TRS is set for the source RS of QCL type A and the source RS of QCL type D.

[0245] QCL rules are defined in existing specifications. For example, the following options B1 to B3 are allowed for PDSCH / PDCCH: [Option B1] The QCL type-A RS is a TRS (CSI-RS with TRS information (trs-Info)), and the type-D RS is a CSI-RS with repetition (CSI-RS for BM). [Option B2] The QCL Type A RS is a TRS (CSI-RS with trs-Info), and the Type D RS is the same as the QCL Type A RS. [Option B3] A QCL Type A RS is a CSI-RS without trs-Info and without repetition, and a Type D RS is the same as a QCL Type A RS.

[0246] For CSI-RS resources in a non-zero power (NZP)-CSI-RS resource set (NZP-CSI-RS-ResourceSet) configured without trs-info and without repetition, the UE shall assume that the TCI-State indicates one of one or more of the following QCL types: Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and, if applicable, Type D with the same CSI-RS resources. Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and Type D with SS / PBCH blocks, if applicable. Type A with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info and, if applicable, Type D with CSI-RS resources in the NZP-CSI-RS resource set configured with repetition. If Type D is not applicable, Type B with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info.

[0247] An explicit RRC parameter may be defined to indicate whether the unified TCI state of Rel.17 is shared with UE dedicated reception on PDSCH / PDCCH or with PUSCH and dedicated PUCCH resources in a dynamic / configured grant.

[0248] However, it is unclear how to indicate whether the unified TCI state is shared with UE-specific reception on the PDSCH / PDCCH or with PUSCH and dedicated PUCCH resources in dynamic / configured grants, which may result in degradation of throughput / communication quality.

[0249] Therefore, the present inventors have conceived a method of indicating the sharing of TCI state.

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

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

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

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

[0254] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, and the like, or a combination thereof.

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

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

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

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

[0259] In the present disclosure, common beam, common TCI, common TCI state, TCI state of Rel. 17, TCI state after Rel. 17, unified TCI, unified TCI state, TCI state applied to multiple types of channels / RS, TCI state applied to multiple (multiple types) of channels / RS, TCI state applicable to multiple types of channels / RS, TCI state for multiple types of signals, TCI state for multiple types of channels / RS, TCI state, unified TCI state, UL and DL TCI state for joint TCI indication, UL-only TCI state for separate TCI indication, DL-only TCI state for separate TCI indication, joint TCI state for DL ​​and UL, separate TCI state for each of DL and UL may be read interchangeably.

[0260] In the present disclosure, the TCI states of Rel. 15 / 16, the TCI states / spatial relationships that apply only to a specific channel / RS, and the TCI states / spatial relationships that apply to one type of channel / RS may be read interchangeably.

[0261] In the present disclosure, multiple TCI states configured by an RRC IE, multiple TCI states activated by a MAC CE, information regarding one or more TCI states, TCI state configuration, TCI state pool, active TCI state pool, common TCI state pool, unified TCI state pool, TCI state list, unified TCI state list, joint TCI state pool, separate TCI state pool, separate DL / UL TCI state pool, DL TCI state pool, UL TCI state pool, separate DL TCI state pool, and separate UL TCI state pool may be read as interchangeable.

[0262] In the present disclosure, DL TCI, DL only TCI, separate DL only TCI, DL common TCI, DL unified TCI, common TCI, and unified TCI may be interchangeable. In the present disclosure, UL TCI, UL only TCI, separate UL only TCI, UL common TCI, UL unified TCI, common TCI, and unified TCI may be interchangeable.

[0263] In the present disclosure, the channels / RS to which the unified TCI state applies may be PDSCH / PDCCH / CSI-RS / PUSCH / PUCCH / SRS.

[0264] In the present disclosure, BWP, CC(cell), and CC(cell) / BWP may be read interchangeably.

[0265] (Wireless communication method) In each embodiment, the Rel.17 TCI state / unified TCI state may be simply referred to as the TCI state. In each embodiment, when it is necessary to distinguish the Rel.17 TCI state / unified TCI state from the Rel.15 / 16 TCI state, it may be referred to as the Rel.17 TCI state / unified TCI state.

[0266] In each embodiment, the target channel may be at least one of UE individual reception on PDSCH / PDCCH and PUSCH and individual PUCCH resources of a dynamic grant / configuration grant, or at least one of UE individual reception on PDSCH / PDCCH and PUSCH and all individual PUCCH resources of a dynamic grant / configuration grant, or a UE individual channel / UE individual reception / UE individual transmission / UE individual RS / UE individual channel resource, or a channel / RS to which a unified TCI state applies.

[0267] In the present disclosure, UE-specific reception on PDSCH / PDCCH, reception of PDSCH / PDCCH configured by PDSCH configuration (PDSCH-Config) / PDCCH configuration (PDCCH-Config), UE-specific PDSCH / PDCCH, and UE-specific PDSCH / PDCCH resources may be interchangeable. In the present disclosure, PUSCH of dynamic grant / configuration grant, PUSCH configured by PUSCH configuration (PUSCH-Config) / configuration grant configuration (ConfiguredGrantConfig), UE-specific PUSCH, and UE-specific PUSCH resource may be interchangeable. In the present disclosure, dedicated PUCCH resource, PUCCH resource configured by PUCCH configuration (PUCCH-Config), UE-specific PUCCH, and UE-specific PUCCH resource may be interchangeable.

[0268] In each embodiment, a specific channel / signal, a specific channel / signal / resource / resource set, a specific signal, a specific channel, a specific resource, a resource / resource set of a specific channel / RS, a specific channel / RS / resource / resource set, and one of PDSCH / PDCCH / CSI-RS / PUSCH / PUCCH / SRS / CORESET may be read as interchangeable.

[0269] In each embodiment, the following may be interpreted interchangeably: a specific channel / RS sharing the same TCI state as the target channel; a specific channel / RS sharing the TCI state indicated for the target channel; the TCI state of a specific channel / RS being set / indicated together with the TCI state of the target channel; the TCI state of a specific channel / RS referring to the TCI state of the target channel; a TCI state being shared between a specific channel / RS and the target channel; the same TCI state being applied between a specific channel / RS and the target channel; the TCI state of a specific channel / RS being the same as the TCI state of the target channel; the TCI state of a specific channel / RS being the same as the unified TCI state; and the TCI state of a specific channel / RS being updated / indicated / set by the unified TCI state.

[0270] In each embodiment, the TCI state for a specific channel / RS may be a TCI state for only the specific channel / RS, or may be a unified TCI state.

[0271] First Embodiment This embodiment relates to indicating / setting whether the TCI state of a particular channel / RS is shared with the target channel (whether the TCI state of a particular channel / RS is the same as the unified TCI state).

[0272] The instructions may be in accordance with at least one of the following aspects 1-1 to 1-4.

[0273] <<Aspect 1-1>> The indication / setting of whether the TCI status of a specific channel / RS is shared with the target channel is performed in the TCI status (TCI status information element, TCI status for a specific channel / RS). This indication may follow at least one of the following indication methods 1-1 to 1-4.

[0274] [Instruction method 1-1] The indication may be an explicit indication by RRC configuration for each TCI state ID indicating that the TCI state is shared with the target channel, which may be an ID of a joint DL and UL TCI state, an ID of a DL-only TCI state, or an ID of a UL-only TCI state.

[0275] The explicit indication may be a bit or a flag (FIG. 9). For example, an indication of 0 may indicate that the TCI state is not shared with the target channel, and an indication of 1 may indicate that the TCI state is shared with the target channel. Each value of the indication may indicate the opposite.

[0276] The explicit indication may be more than one bit. The explicit indication may indicate which channel / RS / resource / resource set the TCI state applies to / is shared with. For example, if the explicit indication indicates CORESET#1 / #2 and CSI-RS resource#2 / #3, the TCI state applies to the indicated resources.

[0277] [Instruction method 1-2] The indication may be an explicit indication by RRC configuration of a list of TCI states that are shared with the target channel. The TCI states in the list may be IDs of joint DL and UL TCI states, or IDs of DL-only TCI states, or IDs of UL-only TCI states. For example, if the explicit indication is a list of TCI state IDs #1, #3, and #5, those TCI states are shared with the target channel.

[0278] [Instruction method 1-3] No explicit indication may be required. A TCI state ID may be configured for each specific channel / RS (downstream / upstream channel / RS). The TCI state ID may be a joint DL and UL TCI state ID, a DL-only TCI state ID, or a UL-only TCI state ID. If the TCI state of a specific channel / RS is configured with the same ID as the TCI state of a target channel, it may mean that the TCI state is shared with the target channel. For example, if the same ID of a TCI state is configured for a CSI-RS and a UE-specific CORESET, it may mean that the TCI state is shared between the CSI-RS and the UE-specific CORESET.

[0279] [Instruction method 1-4] The indication may only indicate / set whether the TCI state for a specific channel / RS is shared with the target channel (sharing indication). The indication may not include an explicit association with the TCI state. The indication may be a single bit indicating whether the TCI state is shared with the target channel. The indication may apply to all TCI states for a specific channel / RS, or to all TCI states for a specific channel / RS that satisfy the QCL rules (e.g., options A1 / A2 / B1 / B2 / B3 described above). The UE may assume that only TCI states that satisfy the QCL rules are shared with the target channel.

[0280] <<Aspect 1-2>> The indication / setting of whether the TCI state of a particular channel / RS is shared with the target channel may be made outside of each TCI state (TCI state information element, TCI state for a particular channel / RS), or the indication of whether the TCI state of a particular channel / RS is shared with the target channel may be an implicit indication.

[0281] The indication may be an explicit indication by RRC configuration of a list of resources / resource sets (specific resources / resource sets, resources / resource sets of specific channels / RSs) that share a TCI state with the target channel. The TCI state for the specific resources / resource sets may be shared with the target channel. The specific resources / resource sets may be resources / resource sets for specific channels / RSs.

[0282] The specific resource / resource set may include at least one of aperiodic (AP)-CSI-RS for the BM, AP-CSI-RS for CSI, DL DMRS for non-UE-dedicated (cell-specific) PDCCH / PDSCH from the serving cell, and AP-SRS for the BM.

[0283] 10 shows an example of a list of specific resources / resource sets. In this example, the list includes CSI-RS resource (set) #1, #2, #3. The TCI state of the target channel may be applied to CSI-RS resource (set) #1, #2, #3 in the list.

[0284] For each DL / UL channel / RS or each resource / resource set, a TCI state or a list of TCI states may be configured in the TCI state framework of Rel.15. In Rel.15 / 16, for each resource / resource set / channel / CORESET, a TCI state ID / list is configured by an RRC IE and indicated by a MAC CE / DCI. The UE uses the indicated TCI state. For the UL, spatial relationships may be used instead of TCI states.

[0285] For each DL / UL channel / RS or each resource / resource set, in the unified TCI state framework of Rel. 17, the TCI state or list of TCI states may be configured according to at least one of the following indication methods 2-1 to 2-5.

[0286] [Instruction method 2-1] An enabler (enablement information element) of the Rel.17 TCI state (specific channels / RSs / resources / resource sets sharing a unified TCI state for the target channel) may be configured by an RRC parameter. An enabler (enable / disable the Rel.17 TCI state) may be configured for each specific channel / RS / resource / resource set.

[0287] When this enabler is configured, there is no need to specify a Rel.17 TCI state ID for a specific channel / RS / resource / resource set / CORESET. To specify a Rel.17 TCI state for a specific channel / RS / resource / resource set / CORESET, a TCI state pool spanning multiple channels / RS / resources / resource sets / CORESET (target channel and specific channel / RS) can be configured.

[0288] In the example of Figure 11A, the PDSCH configuration (PDSCH-Config) may include at least one of a Rel.15 TCI state list and a Rel.17 TCI state list. If multiple Rel.17 TCI states are configured, the MAC CE / DCI may indicate one of the configured Rel.17 TCI states. The indicated TCI state may be used for multiple channels / RSs for which the Rel.17 TCI state is enabled by higher layer signaling.

[0289] In the example of FIG. 11B, the CORESET configuration (ControlResourceSet) #1 may include at least one of the Rel.15 TCI state and the enablement of the Rel.17 TCI state. In Rel.15, a TCI state ID is configured for each CORESET. Since the TCI state pool for the Rel.17 TCI state is configured in the PDSCH configuration, a flag to enable the Rel.17 TCI state is sufficient in the CORESET configuration. If multiple Rel.17 TCI states are configured, one of the multiple Rel.17 TCI states in which the MAC CE / DCI is configured may be indicated. There is no need to indicate a TCI state ID for Rel.17 in the CORESET configuration other than the configuration of the TCI state pool (e.g., in the PDSCH configuration).

[0290] In the example of FIG. 11C , the CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet) #1 may include at least one of a Rel.15 TCI state and an enabled Rel.17 TCI state. In Rel.15, a TCI state ID is configured for each CSI-RS resource set. For the Rel.17 TCI state, a TCI state pool is configured in the PDSCH configuration, so a flag to enable the Rel.17 TCI state is sufficient in the CSI-RS resource set configuration. If multiple Rel.17 TCI states are configured, one of the multiple Rel.17 TCI states in which the MAC CE / DCI is configured may be indicated. Other than configuring a TCI state pool (e.g., in the PDSCH configuration), there is no need to indicate a TCI state ID for Rel.17 in the CSI-RS resource set configuration.

[0291] If an enabler is configured, the indicated unified TCI state may be applied to a particular channel / RS / resource / resource set. An enabler may be configured per channel / RS / resource / resource set.

[0292] Rel.17 TCI states may not be applied to channels / RSs / resources / resource sets for which Rel.15 TCI states / spatial relationships are configured.

[0293] 12 and 13, an enabler for the Rel.17 TCI state is configured for each of the first resources (specific resources, CORESET#2, CORESET#3, CSI-RS resource sets#2, CORESET#3, SRS resource sets#2, CORESET#3). A Rel.15 TCI state (TCI state #A) is configured for CORESET#1, a Rel.15 TCI state (TCI state #B) is configured for CSI-RS resource set #1, and a Rel.15 spatial relationship (SRS resource #C) is configured for SRS resource set #1.

[0294] FIG. 12 shows an example of a joint TCI state.

[0295] In this example, the RRC IE configures a joint TCI state pool for DL ​​and UL, the MAC CE indicates / activates a joint TCI state ID for each value (codepoint) of the TCI field, and the DCI indicates one value (011) of the TCI field, which corresponds to TCI state #3. The indicated TCI state #3 applies to multiple channels / RSs / resources / resource sets (PDSCH, CORESET #2, CORESET #3, CSI-RS resource sets #2, CORESET #3, SRS resource sets #2, CORESET #3).

[0296] The Rel.17 TCI state may not be applied to the second resources (other than specific resources, CORESET#1, CSI-RS resource set#1, SRS resource set#1) for which the Rel.15 TCI state / spatial relationship is set.

[0297] FIG. 13 shows an example of a separate TCI state.

[0298] In this example, the RRC IE configures separate TCI state pools for DL ​​and UL, the MAC CE indicates / activates a DL TCI state ID / UL TCI state ID for each value (code point) of the TCI field, and the DCI indicates one value (100) of the TCI field, which corresponds to TCI state #4 for DL ​​and TCI state #5 for UL. TCI state #4 applies to multiple channels / RSs / resources / resource sets for DL ​​(PDSCH, CORESETs #2 and #3, CSI-RS resource sets #2 and #3). TCI state #5 applies to multiple channels / RSs / resources / resource sets for UL (SRS resource sets #2 and #3).

[0299] The Rel.17 TCI state may not be applied to the second resources (other than specific resources, CORESET#1, CSI-RS resource set#1, SRS resource set#1) for which the Rel.15 TCI state / spatial relationship is set.

[0300] The TCI state pool may be CC specific or CC common.

[0301] The TCI state pool may be configured outside of the PDSCH configuration.

[0302] [Instruction method 2-2] Activation of Rel. 17 TCI states (specific channels / RS / resources / resource sets sharing a unified TCI state for the target channel) may be indicated without using an enabler.

[0303] If the Rel.15 / 16 TCI state does not exist (is not configured), the joint TCI state or the DL TCI state may be applied to a specific channel / RS / resource / resource set. If the Rel.15 / 16 spatial relationship does not exist (is not configured) (and the default beam and PL-RS enabler do not exist), the joint TCI state or the UL TCI state may be applied to a specific channel / RS / resource / resource set.

[0304] At least one of the channel / RS to which the Rel.17 TCI state applies and the ID of the resource / resource set of the channel / RS may be configured by higher layer signaling. The Rel.17 TCI state may be applied to the configured channel / RS / resource / resource set. It may be specified that the channel / RS / resource / resource set to which the Rel.17 TCI state is configured is not configured with the Rel.15 / 16 TCI state / spatial relationship.

[0305] In the example of Figure 14, the Rel.15 TCI state / spatial relationship is not configured for each of the first resources (specific resources, CORESET#2, #3, CSI-RS resource sets #2, #3, SRS resource sets #2, #3). The Rel.15 TCI state (TCI state #A) is configured for CORESET#1, the Rel.15 TCI state (TCI state #B) is configured for CSI-RS resource set #1, and the Rel.15 spatial relationship (SRS resource #C) is configured for SRS resource set #1.

[0306] In this example, the RRC IE configures a joint TCI state pool for DL ​​and UL, the MAC CE indicates / activates a joint TCI state ID for each value (codepoint) of the TCI field, and the DCI indicates one value (011) of the TCI field, which corresponds to TCI state #3. The indicated TCI state #3 applies to channels / RSs / resources / resource sets for which no Rel. 15 TCI state / spatial relationship is configured (PDSCH, CORESET #2, CORESET #3, CSI-RS resource sets #2, CORESET #3, SRS resource sets #2, CORESET #3).

[0307] [Instruction method 2-3] Activation of Rel. 17 TCI states for specific channels / RSs / resources / resource sets (specific channels / RSs / resources / resource sets sharing a unified TCI state for the target channels) may be indicated without using an enabler.

[0308] As with Rel.15 / 16, a TCI state ID / list may be configured for each specific channel / RS / resource / resource set / CORESET.

[0309] At least one (first resource) of a specific channel / RS to which the Rel.17TCI state applies and an ID of a resource / resource set of the specific channel / RS may be configured by higher layer signaling (FIG. 15).

[0310] A particular channel / RS / resource / resource set configured by higher layer signaling (to which Rel. 17 TCI state applies) may be configured with a Rel. 15 / 16 TCI state / spatial relationship, in which case the Rel. 15 / 16 TCI state / spatial relationship configured for the particular channel / RS / resource / resource set may be ignored and the Rel. 17 TCI state may apply to that channel / RS / resource / resource set.

[0311] [Instruction method 2-4] Based on the indication method 1-1, it may be indicated / set whether a specific channel / RS / resource / resource set shares the unified TCI state of Rel. 17 with the target channel. Whether a specific channel / RS / resource / resource set shares the unified TCI state of Rel. 17 with the target channel may differ depending on which TCI state is indicated for the specific channel / RS (e.g., the value of the TCI field, the TCI state ID) or depending on the resource / resource set applied to the specific channel / RS.

[0312] 16 and 17, enablers that enable the Rel. 17 TCI state are configured for each of CORESET#2, CSI-RS resource set#2, and SRS resource set#2. The RRC IE configures a joint TCI state pool, and the MAC CE indicates / activates a TCI state from the joint TCI state pool for each value of the TCI field.

[0313] Figure 16 shows the case where the indicated joint TCI state for a particular channel / RS / resource / resource set is not shared with the target channel. In this example, the DCI indicates a value (100) in the TCI field. The indicated TCI state #4 is not shared with the target channel. TCI state #4 applies to PDSCH and CORESET #2, but not to CSI-RS resource set #2 or SRS resource set #2. The previously used TCI state is maintained for each of CSI-RS resource set #2 and SRS resource set #2.

[0314] Figure 17 shows a case where the joint TCI state indicated for a particular channel / RS is not shared with the target channel. In this example, the DCI indicates a single value (011) in the TCI field. The indicated TCI state #3 is shared with the target channel. TCI state #3 applies to PDSCH, CORESET #2, CSI-RS resource set #2, and SRS resource set #2.

[0315] The QCL rules (e.g., options A1 / A2 / B1 / B2 / B3 above) may be different for cases 1 and 2 below. [Case 1] The TCI state of Rel. 17 for a particular channel / RS is shared / set / indicated with the target channel. [Case 2] The TCI state of Rel.17 for a particular channel / RS is not shared / configured / indicated with the target channel.

[0316] In the example of Figure 18, the RRC IE configures a joint TCI state pool for DL ​​and UL, the MAC CE indicates / activates a joint TCI state ID for each value (codepoint) of the TCI field, and the DCI indicates one value of the TCI field. TCI states corresponding to a first range of values ​​of the TCI field (e.g., 000 to 011) are shared with the target channel, and TCI states corresponding to a second range of values ​​of the TCI field (e.g., 100 to 111) are not shared with the target channel. If the DCI indicates a value of 001 within the first range, the aforementioned options A1 / A2 are allowed for the corresponding TCI state #1. The TCI state #1 applies to the target channel / RS / resource / resource set of the Rel. 17 TCI state and is shared with the target channel. If the DCI indicates a value of 100 within the second range, the QCL rules in the existing specifications (e.g., the aforementioned options B1 / B2 / B3) are allowed for the corresponding TCI state #4. The TCI state #4 applies to the target channel / RS / resource / resource set of the Rel.17 TCI state and is not shared with the target channel. Note that in this example, separate TCI states (DL TCI state / UL TCI state) may be used instead of the joint TCI state.

[0317] [Instruction method 2-5] Only an indication / setting (sharing indication) of whether the TCI state for a specific channel / RS is shared with the target channel may be set. The indication may not include an explicit association with a resource / resource set. The resource / resource set (specific resource / resource set, default resource) to which the indication applies may be specified in the specification. The indication may be a single bit indicating whether the TCI state is shared with the target channel for each channel / RS / BWP / CC. If the TCI state for a specific channel / RS is set to be shared with the target channel, the TCI states for all resources / resource sets of the specific channel / RS may be updated / indicated by the Rel.17 TCI state, or the TCI state for a specific resource / resource set among the resources / resource sets of the specific channel / RS may be updated / indicated by the Rel.17 TCI state.

[0318] According to this embodiment, the UE can properly determine whether the TCI state for a particular channel / RS is shared with the target channel.

[0319] <Second embodiment> This embodiment relates to BFD / RLM.

[0320] A unified TCI state ID (indicating at least one of a joint TCI state for DL ​​and UL, a TCI state for DL, and a TCI state for UL) may be configured / indicated by an RRC IE / MAC CE / DCI.

[0321] In the unified TCI framework, how the UE determines the RLM / BFD RS may follow at least one of the following RLM / BFD RS determination methods 1 and 2.

[0322] [RLM / BFD RS determination method 1] The BFD / RLM RS (explicit BFD / RLM RS) may be indicated by L1 signaling (DCI). If the BFD / RLM RS is not configured, the BFD / RLM RS (implicit BFD / RLM RS) may be derived from the QCL assumed / TCI state of the CORESET or from the QCL assumed / TCI state of the unified / common TCI state.

[0323] [RLM / BFD RS determination method 2] The BFD / RLM RS may not be indicated by L1 signaling (DCI). If the BFD / RLM RS is not configured, the BFD / RLM RS (implicit BFD / RLM RS) may be derived from the QCL assumed / TCI state of the CORESET or from the QCL assumed / TCI state of the unified / common TCI state.

[0324] These RLM / BFD RS determination methods need to take into account joint TCI states and separate TCI states. These RLM / BFD RS determination methods do not consider whether the unified TCI state used to determine the RLM / BFD RS is shared / configured / indicated together with the target channel.

[0325] <<Aspect 2-1>> The BFD / RLM RS may be derived from the unified TCI state.

[0326] In Rel.17, the joint TCI state or the separate TCI state may be switched by an RRC IE (the joint TCI state or the separate TCI state may be set). In Rel.18, both the joint TCI state and the separate TCI state may be set. The MAC CE / DCI may select one of them.

[0327] If a joint TCI state is configured, the BFD / RLM RS may be derived / determined from the joint TCI state.

[0328] The method for determining the BFD / RLM RS from the TCI state may follow either of the following determination methods 1 and 2.

[0329] [Decision method 1] The UE may use the QCL source RS in the TCI state as the BFD / RLM RS. If there are two QCL source RSs (e.g., a QCL Type-A RS and a QCL Type-D RS), the UE may use the QCL Type-D RS as the BFD / RLM RS.

[0330] [Decision method 2] The UE may use the QCL Type D source RS for the BFD / RLM RS.

[0331] Determination method 1 may be applied to both frequency range (FR) 1 and FR 2. Determination method 1 can appropriately determine the BFD / RLM RS even when the QCL type D RS is not configured or in FR 1.

[0332] FIG. 19 shows an example in which a joint TCI state is configured. In this example, an RRC IE configures a joint TCI state pool, a MAC CE indicates / activates a TCI state from the joint TCI state pool corresponding to each value of the TCI field, and a DCI indicates one value of the TCI field. In this example, a value of 011 in the TCI field indicates TCI state #3. TCI state #3 is applied to the PDSCH. TCI state #3 includes a first QCL RS (first QCL type) and a second QCL RS (second QCL type). The first QCL RS indicates QCL type A and CSI-RS #3, and the second QCL RS indicates QCL type D and CSI-RS #3. The UE may use CSI-RS #3 for the BFD RS or may use CSI-RS #3 for the RLM RS.

[0333] If separate TCI states for DL / UL are configured, the BFD / RLM RS may be derived / determined from the DL TCI state of the separate TCI states for DL / UL.

[0334] FIG. 20 shows an example in which separate TCI states are configured. In this example, an RRC IE configures a separate TCI state pool, and a MAC CE indicates / activates a DL TCI state / UL TCI state corresponding to each value of the TCI field from the separate TCI state pool, and a DCI indicates one value of the TCI field. In this example, a value of 100 in the TCI field indicates DL TCI state #4 and UL TCI state #5. TCI state #4 is applied to the PDSCH. TCI state #4 includes a first QCL RS (first QCL type) and a second QCL RS (second QCL type). The first QCL RS indicates QCL type A and CSI-RS #4, and the second QCL RS indicates QCL type D and CSI-RS #4. The UE may use CSI-RS #4 for the BFD RS or for the RLM RS.

[0335] This aspect may only apply if no explicit BFD / RLM RS is configured.

[0336] <<Aspect 2-2>> For a given unified TCI state, there may be two cases: [Case 1] The unified TCI state is shared / set / indicated along with the target channel. [Case 2] The unified TCI state is not shared / configured / indicated with the target channel.

[0337] An explicit RRC parameter may be configured to indicate whether a unified TCI state is shared with the target channel.

[0338] The unified TCI state of case 1 only may be considered as the BFD / RLM RS, in which case, if there is a failure in the unified TCI state used for the target channel, the failure can be detected by the BFD / RLM.

[0339] The unified TCI state in case 2 only may be considered as a BFD / RLM RS.

[0340] The unified TCI state for both cases 1 and 2 may be considered as the BFD / RLM RS. Whatever TCI state is indicated, the latest TCI state is used for the BFD / RLM RS.

[0341] Since BFD / RLM is performed by the DL RS, the unified TCI state may be a joint TCI state for DL ​​and UL, or a TCI state for DL ​​only.

[0342] For CORESET with unified TCI state in Rel. 17, the RS within that TCI state may be considered as BFD / RLM RS.

[0343] For a CORESET with a TCI state of Rel. 15 / 16, the RS within that TCI state may be considered as a BFD / RLM RS.

[0344] Regardless of whether the TCI state for a CORESET is a Rel. 17 unified TCI state or a Rel. 15 / 16 TCI state, all RSs within that TCI state may be considered as BFD / RLM RSs.

[0345] If the number of TCI states from CORESET exceeds a maximum number (e.g., 2), the UE may give higher priority to CORESET with Rel. 17 unified TCI states in selecting BFD / RLM RS.

[0346] According to this embodiment, the UE can make proper BFD / RLM decisions even when using a unified TCI state.

[0347] <Third embodiment> This embodiment relates to new beam detection (NBI).

[0348] In the existing specifications, the CORESET / PUCCH beam is updated to q_new 28 symbols after BFR completion. If BFR is not completed, BFR will be performed again based on the failing beam, and the UE may not be able to transmit or receive control information on the failing beam.

[0349] The beam application timing based on BFR completion (receiving a BFR response from the base station) may follow at least one of the following timings 1 to 4.

[0350] [Timing 1] For BFR (Rel. 15) on SpCell, 28 symbols after the last symbol of the DCI format with cyclic redundancy check (CRC) scrambled by cell (C)-radio network temporally identifier (RNTI) or modulation and coding scheme (MCS)-C-RNTI within the BFR search space.

[0351] [Timing 2] In contention-based random access (CBRA)-based BFR (Rel.16) on the SpCell, 28 symbols after the last symbol of the DCI format with CRC scrambled by the C-RNTI within any search space.

[0352] [Timing 3] BFR MAC on SCell In CE-based BFR (Rel.16), schedule a PUSCH with the same HARQ process number as the HARQ process number of the first PUSCH, 28 symbols after the last symbol of the DCI format with the new data indicator (NDI) field toggled.

[0353] [Timing 4] In TRP-specific BFR (Rel. 17) on SpCell / SCell, after receiving a BFR response, updating the QCL assumption for a CORESET with two activated TCI states may be, for per-cell BFR, updating a CORESET with two activated TCI states to have one TCI state; for per-TRP BFR in single-DCI-based multi-TRP, updating the TCI state associated with the faulty BFD-RS set; or for per-TRP BFR in multi-DCI-based multi-TRP, updating the TCI state associated with the faulty BFD-RS set / CORESET pool index after receiving a BFR response.

[0354] The beam application timing within the unified TCI state may be Y symbols after the ACK for the beam direction (the first slot at least Y symbols after the last symbol of the ACK for the joint or separate DL / UL beam direction). For CA, Y may be based on the minimum subcarrier spacing (SCS) within the CC (cell) to which the beam is applied. Y may be given by the RRC parameter Beam Application Time (BAT, e.g., BeamAppTime_r17).

[0355] In the present disclosure, BFR completion, receipt of a response to BFR (BFR response (BFRR)), and the last symbol of a specific DCI format for BFR may be interchangeable. The specific DCI format may be a DCI format at at least one of the above-described timings 1 to 3.

[0356] In the unified TCI framework of Rel. 17, X symbols after the reception of BFFR, a new / updated QCL source RS may be applied to the target channel within the CC and the channels / signals (specific channels / RSs) configured to share the Rel. 17 TCI state.

[0357] <<Aspect 3-1>> Y for Y symbols from BFR completion to unified TCI status update may be configured by RRC, reported as UE capability, or specified in a specification. Y may be common to multiple SCSs or may have different values ​​depending on the SCS. Y may be the same value as Y for beam application timing. In other words, Y symbols after the UE receives the BFR response, the new / updated QCL source RS may be applied to all or part of the PDCCH / PDSCH / PUCCH / PUSCH.

[0358] <<Aspect 3-2>> In the CA case, q_new may be applied to all BWPs / CCs in the CC list, all BWPs / CCs in the TCI state pool, or all BWPs / CCs in the BFR MAC CE. The CA case may be when a simultaneous beam update list (CC list) is configured, when a CC common TCI state pool is configured, or when the BFR MAC CE includes multiple CCs with beam failures.

[0359] The q_new may be applied to all BWP / CCs within the CC reported as a faulty CC within the BFR MAC CE.

[0360] In the example of Figure 21, the UE detects beam failures in each of CCs #1, #2, and #3, and reports CSI-RSs #1-1, #2-1, and #3-1 as NBIs for CCs #1, #2, and #3, respectively, within the BFR MAC CE. After Y symbols from the completion of BFR, the UE applies CSI-RSs #1-1, #2-1, and #3-1 as unified TCI states for CCs #1, #2, and #3, respectively.

[0361] The RS of q_new may be a CC-common RS (e.g., BFR RS) or a CC-specific RS. For a CC-specific RS, the NBI RS for each CC reported in the BFR MAC CE may be used for q_new.

[0362] If a simultaneous beam update list (CC list) is configured or a CC common TCI status pool is configured, and beam failure is detected in some CCs within the same CC as a CC in the list / pool, but not in other CCs, the UE may follow either update operation 1 or 2.

[0363] [Update action 1] Only the beam of the CC where the beam obstruction is detected may be updated to q_new.

[0364] [Update action 2] The beams of all CCs in the CC list / TCI state pool may be updated to q_new. The UE may determine q_new for each BWP / CC according to at least one of the following derivation methods 1 and 2. [[Derivation method 1]] CC common q_new: The RS of q_new of the BWP / CC with beam obstruction is used for all BWPs / CCs in the same CC list / TCI state pool. [[Derivation method 2]] CC-specific q_new: The index of the RS in q_new of the BWP / CC with a beam obstruction is used for all BWPs / CCs in the same CC list / TCI status pool. For example, if CSI-RS#1 in BWP#1 in CC#1 is determined for CC#1, the same index of CSI-RS in BWP#1 of each BB may be used for all other CCs.

[0365] In the example of Figure 22, the CC list / TCI status pool indicates CC#1, #2, and #3. The UE detects a beam failure in CC#1, and reports CSI-RS#1-1 (CSI-RS with index #1 in CC#1) as the NBI for CC#1 in the BFR MAC CE. Y symbols after the BFR completion, the reported CSI-RS#1-1 is applied as the unified TCI status for CC#1, CSI-RS#2-1 (CSI-RS with the same index #1 in CC#2) is applied as the unified TCI status for CC#2, and CSI-RS#3-1 (CSI-RS with the same index #1 in CC#3) is applied as the unified TCI status for CC#3. The UE may report the failed CC and NBI via contention-free random access (CFRA) or CBRA BFR instead of the BFR MAC CE.

[0366] <<Aspect 3-3>> For a given unified TCI state, there may be two cases: [Case 1] The unified TCI state is shared / set / indicated along with the target channel. [Case 2] The unified TCI state is not shared / configured / indicated with the target channel.

[0367] An explicit RRC parameter may be configured to indicate whether a unified TCI state is shared with the target channel.

[0368] Aspects 3-1 / 3-2 may be applied to the unified TCI state for only Case 1. In this case, the unified TCI state used for the target channel (e.g., UE-dedicated PDCCH / PUCCH) is updated to q_new in the same manner as the TCI state in Rel. 15 / 16.

[0369] Aspects 3-1 / 3-2 may be applied to the unified TCI state of Case 2 only.

[0370] Aspects 3-1 / 3-2 may be applied to the unified TCI state in both cases 1 and 2. Any unified TCI state may be updated to q_new.

[0371] For CORESET / PUCCH with unified TCI state in Rel. 17, the QCL assumption may be updated to q_new.

[0372] For CORESET / PUCCH with TCI state of Rel.15 / 16, the QCL assumption may be updated to q_new.

[0373] Regardless of whether the TCI state for CORESET is the unified TCI state in Rel. 17 or the TCI state in Rel. 15 / 16, the QCL assumption for CORESET / PUCCH may be updated to q_new.

[0374] <<Aspect 3-4>> If the joint TCI state is set, the joint TCI state may be updated to q_new.

[0375] If a separate TCI state is set, the UE may follow any of the following separate TCI state update actions 1 to 3. [Separate TCI status update operation 1] Only DL TCI state is updated to q_new. [Separate TCI status update operation 2] Only the UL TCI state is updated to q_new. [Separate TCI status update operation 3] Both the DL TCI state and the UL TCI state are updated to q_new.

[0376] Considering that both PDCCH and PUCCH beams are updated to q_new, separate TCI state update operation 3 is preferred.

[0377] In Rel. 17, either the joint TCI state or the separate TCI state can be set. In Rel. 18, both the joint TCI state and the separate TCI state can be set, and switching between the joint TCI state and the separate TCI state may be performed by MAC CE / DCI.

[0378] Aspects 3-5 After completing BFR, the UE may set (initialize) all or some of the power control parameters of the PUCCH / PUSCH / SRS to specific values ​​(initial values).

[0379] In the existing specifications, after BFR is completed, the power control parameters of the PUCCH are initialized.

[0380] After BFR is completed, the UE may set (initialize) the power control parameters of the PUCCH / PUSCH / SRS for which the unified TCI state of Rel. 17 is set (associated with) to specific values.

[0381] The specific values ​​of the power control parameters may be q_u=0, q_d=q_new, and l=0.

[0382] The specific values ​​of the power control parameters for the PUSCH may be j=0, q_d=q_new, and l=0.

[0383] The specific values ​​of the power control parameters for the PUCCH may be q_u=0, q_d=q_new, and l=0.

[0384] The specific values ​​of the power control parameters for the SRS may be q_s=0, q_d=q_new, and l=0.

[0385] After the BFR is completed, the accumulated value of the TPC commands for closed-loop power control of the PUCCH / PUSCH / SRS may be set to 0 (initialized).

[0386] According to this embodiment, the UE can make proper BFD / RLM decisions even when using a unified TCI state.

[0387] <Fourth embodiment> This embodiment relates to a method for setting a unified TCI state (joint TCI state or separate TCI state).

[0388] In Rel.17, either a joint TCI state or a separate TCI state can be configured. The TCI state pool can be configured for each CC (as a CC-specific TCI state pool) or across multiple CCs (as a CC-common TCI state pool).

[0389] Either the joint TCI state or the separate TCI state can be set by an RRC IE for each UE / cell group / CC / BWP. In the example of Fig. 23, the joint TCI state (pooled) is set for BWP#1 in CC#1, and the separate TCI state (pooled) is set for BWP#1 in CC#2.

[0390] If either the joint TCI state or the separate TCI state is configured for each cell group or each UE, there is no problem in Rel. 17, but in Rel. 18, it may become difficult to allow switching between the joint TCI state and the separate TCI state based on MAC CE / DCI.

[0391] If one of the joint TCI state and the separate TCI state is set for each BWP or each CC, at least one of the following restrictions 1 and 2 may be required. [Restriction 1] It may be specified that if a joint TCI state pool is configured for a BWP / CC, then separate TCI states cannot be configured for any BWP / CC that shares / configures that (same) TCI state pool. [Restriction 2] It may be specified that if a separate TCI state pool is configured for a BWP / CC, then joint TCI states cannot be configured for any BWP / CC that shares / configures that (same) TCI state pool.

[0392] According to this embodiment, the unified TCI state can be set appropriately.

[0393] <Fifth embodiment> This embodiment relates to a method for setting the TCI state in the BWP / CC.

[0394] Whether or not both the TCI state / spatial relationship of Rel. 15 / 16 and the unified TCI state of Rel. 17 are set may be determined according to either of the following TCI state setting methods 1 and 2.

[0395] [TCI status setting method 1] Both the Rel.15 / 16 TCI state / spatial relationship and the Rel.17 unified TCI state can be set in the same BWP / CC or different BWP / CCs.

[0396] [TCI status setting method 2] Both the Rel.15 / 16 TCI state / spatial relationship and the Rel.17 unified TCI state cannot be configured for the same BWP / CC or different BWP / CC. It may be specified that if the Rel.17 unified TCI state for any CC is configured for a UE, the Rel.15 / 16 TCI state / spatial relationship is not configured for that UE.

[0397] According to this embodiment, the TCI state can be set appropriately.

[0398] <Other embodiments> 《UE capability information / upper layer parameters》 Higher layer parameters (RRC IEs) / UE capabilities corresponding to the functions (features) in each of the above embodiments may be defined. The higher layer parameters may indicate whether the functions are enabled. The UE capabilities may indicate whether the UE supports the functions.

[0399] A UE for which higher layer parameters corresponding to the function are configured may perform the function. It may also be specified that "a UE for which higher layer parameters corresponding to the function are not configured shall not perform the function (for example, in accordance with Rel. 15 / 16)."

[0400] A UE that reports / transmits a UE capability indicating that it supports the function may perform the function. It may also be specified that "a UE that does not report a UE capability indicating that it supports the function shall not perform the function (e.g., in accordance with Rel. 15 / 16)."

[0401] If the UE reports / transmits a UE capability indicating that it supports the function and the corresponding upper layer parameter is configured, the UE may perform the function. It may also be specified that "if the UE does not report / transmit a UE capability indicating that it supports the function or if the corresponding upper layer parameter is not configured, the UE shall not perform the function (e.g., in accordance with Rel. 15 / 16)."

[0402] Which embodiment / option / choice / function of the above multiple embodiments is used may be configured by higher layer parameters, may be reported by the UE as a UE capability, may be specified in a specification, or may be determined by the reported UE capability and the configuration of higher layer parameters.

[0403] The UE capabilities may indicate whether the UE supports at least one of the following functions: Unified TCI framework (at least one of joint TCI state pool, separate TCI state pool, beam direction for joint TCI state pool, beam direction for separate TCI state). The UE capabilities may include at least one of the following: a maximum number of unified TCI states configured by an RRC IE (number supported by the UE), a maximum number of TCI states configured for joint beam direction, a maximum number of UL TCI states for separate beam direction (number supported by the UE), and a maximum number of DL TCI states for separate beam direction. The UE capabilities may include at least one of the following: a maximum number of active TCI states for unified TCI states (common beam direction) (number supported by the UE), a maximum number of active TCI states for joint beam direction (number supported by the UE), a maximum number of active UL TCI states for separate beam direction (number supported by the UE), and a maximum number of active DL TCI states for separate beam direction (number supported by the UE). Rel.17 TCI state (unified TCI state) shared with specific resources. The specific resources may be at least one of UE dedicated reception on PDSCH / PDCCH, PUSCH of dynamic grant / configuration grant, and dedicated PUCCH resource. Rel.17 TCI state (unified TCI state) that is not shared with specific resources. The specific resources may be at least one of UE dedicated reception on PDSCH / PDCCH, PUSCH of dynamic grant / configuration grant, and dedicated PUCCH resource. · BFR for Unified TCI state. -q_new update after BFR completion for unified TCI state.

[0404] The above UE capabilities / upper layer parameters allow the UE to achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0448] The transceiver 120 may transmit a setting regarding a transmission configuration indication (TCI) state that applies to at least one of a plurality of types of channels and signals. The controller 110 may determine whether the TCI state is shared with a particular signal.

[0449] The transceiver 120 may transmit an instruction regarding a transmission configuration indication (TCI) state applied to at least one of a plurality of types of channels and signals. The controller 110 may control beam failure detection and radio link monitoring using a reference signal based on the TCI state.

[0450] The transceiver 120 may transmit a plurality of configurations corresponding to a plurality of cells, respectively. The controller 110 may apply a transmission configuration indication (TCI) state indicated in the corresponding configuration to each cell. Each configuration may include at least one of whether the corresponding TCI state applies to both the downlink and the uplink, and whether the corresponding TCI state applies to multiple types of at least one of channels and signals.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0468] The transceiver 220 may receive a setting regarding a transmission configuration indication (TCI) state that applies to at least one of a plurality of types of channels and signals, and the controller 210 may determine whether the TCI state is shared with a particular signal.

[0469] The setting may indicate whether the TCI status is shared with the specific signal, and the controller 210 may determine whether the TCI status is shared with the specific signal based on the setting.

[0470] The configuration may indicate a resource or set of resources that the TCI state shares with the particular signal.

[0471] The setting may indicate that no TCI state applies to one type of channel or signal.

[0472] The transceiver 220 may receive an indication regarding a transmission configuration indication (TCI) state that applies to at least one of a plurality of types of channels and signals. The controller 210 may determine a reference signal for beam obstruction detection and radio link monitoring based on the TCI state.

[0473] When the indication indicates a joint TCI state to be applied to the downlink and the uplink, the reference signal may be the joint TCI state.

[0474] When the indication indicates a downlink TCI state to be applied to a downlink and an uplink TCI state to be applied to an uplink, the reference signal may be the downlink TCI state.

[0475] When the transceiver unit 220 receives a list of multiple cells, detects a failure in at least one of the multiple cells, and reports a new beam, the control unit 210 may determine multiple TCI states to be used for each of the multiple cells based on the new beam.

[0476] The transceiver 220 may receive a plurality of configurations corresponding to a plurality of cells, respectively. The controller 210 may apply a transmission configuration indication (TCI) state indicated in the corresponding configuration to each cell. Each configuration may include at least one of whether the corresponding TCI state applies to both the downlink and the uplink, and whether the corresponding TCI state applies to multiple types of at least one of channels and signals.

[0477] Each configuration may indicate either a TCI state that applies to both the downlink and the uplink, or a downlink TCI state that applies to the downlink and an uplink TCI state that applies to the uplink.

[0478] The plurality of settings may include a setting indicating a TCI state to be applied to a plurality of types of at least one of channels and signals, and a setting indicating a TCI state to be applied to one type of channel or signal.

[0479] When the plurality of settings includes a setting indicating a TCI state to be applied to at least one of a plurality of types of channels and signals, the plurality of settings may not include a setting indicating a TCI state to be applied to one type of channel or signal.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0520] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0555] Also, "decision" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "decision" may be considered to be "deciding" on some action.

[0556] Furthermore, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," or the like.

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

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

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

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

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

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

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

Claims

1. a receiver that receives a list of transmission configuration indication (TCI) states applicable to multiple types of channels and reference signals, and a Radio Resource Control (RRC) information element that indicates whether the TCI state is applicable to a downlink (DL) and an uplink (UL), or whether the TCI state is applicable to either the DL or the UL; a control unit that determines a reference signal for the beam failure detection and radio link monitoring based on the RRC information element and a TCI state in the TCI state list when a reference signal for the beam failure detection and radio link monitoring is not configured; The control unit applies a new Quasi-Co-Location (QCL) source reference signal to at least one of a specific channel and a signal to which the TCI state in the list of TCI states applies, after a specific symbol from the reception of a response to the beam fault recovery; The list of TCI states is included in a Physical Downlink Shared Channel (PDSCH) configuration, the receiving unit receives an activation information element not included in the PDSCH configuration, which indicates whether the TCI state in the list of TCI states is valid for a specific signal, and the control unit determines whether the TCI state in the list of TCI states is valid for the specific signal based on the activation information element.

2. 2. The terminal according to claim 1, wherein, when the RRC information element indicates the TCI state applied to the DL and UL, the control unit applies the new QCL source reference signal to at least one of the specific channels and signals to which the TCI state applied to the DL and UL applies.

3. 2. The terminal according to claim 1, wherein, when the RRC information element indicates the TCI state applied to either the DL or the UL, the control unit applies the new QCL source reference signal to at least one of the specific channel and signal to which the TCI state applied to the DL applies.

4. receiving a Radio Resource Control (RRC) information element indicating a list of transmission configuration indication (TCI) states applicable to multiple types of channels and reference signals, and a TCI state applicable to both a downlink (DL) and an uplink (UL), or a TCI state applicable to either a DL or an UL; receiving an activation information element not included in a Physical Downlink Shared Channel (PDSCH) configuration, the list of TCI states being included in the PDSCH configuration, the activation information element indicating whether the TCI states in the list of TCI states are valid for a particular signal; If a reference signal for beam failure detection and radio link monitoring is not configured, determining a reference signal for the beam failure detection and radio link monitoring based on the RRC information element and a TCI state in the list of TCI states; applying a new Quasi-Co-Location (QCL) source reference signal to at least one of the specific channels and signals to which the TCI state in the list of TCI states applies, a specific symbol after receiving a response to the beam failure recovery; and determining whether the TCI state in the list of TCI states is valid for the particular signal based on the validation information element.

5. a transmitter configured to transmit a list of transmission configuration indication (TCI) states applicable to a plurality of types of channels and reference signals, and a Radio Resource Control (RRC) information element indicating whether the TCI state is applicable to a downlink (DL) and an uplink (UL), or whether the TCI state is applicable to either the DL or the UL; a control unit that controls determination of a reference signal for beam failure detection and radio link monitoring based on the RRC information element and a TCI state in the TCI state list when a reference signal for beam failure detection and radio link monitoring is not configured; The control unit applies a new Quasi-Co-Location (QCL) source reference signal to at least one of a specific channel and a signal to which the TCI state in the list of TCI states applies, after a specific symbol from the reception of a response to the beam fault recovery; A base station, wherein the list of TCI states is included in a Physical Downlink Shared Channel (PDSCH) configuration, the transmitter transmits an activation information element not included in the PDSCH configuration, which indicates whether the TCI state in the list of TCI states is valid for a specific signal, and the controller determines whether the TCI state in the list of TCI states is valid for the specific signal based on the activation information element.

6. A system having a terminal and a base station, The terminal includes a receiving unit that receives a list of transmission configuration indication (TCI) states applicable to a plurality of types of channels and reference signals, and a Radio Resource Control (RRC) information element that indicates whether the TCI state is applicable to a downlink (DL) and an uplink (UL), or whether the TCI state is applicable to either the DL or the UL; a control unit of the terminal that determines a reference signal for the beam failure detection and radio link monitoring based on the RRC information element and a TCI state in the TCI state list when a reference signal for the beam failure detection and radio link monitoring is not configured; A control unit of the terminal applies a new Quasi-Co-Location (QCL) source reference signal to at least one of a specific channel and a signal to which the TCI state in the list of TCI states applies, after a specific symbol from the reception of a response to the beam fault recovery; The list of TCI states is included in a Physical Downlink Shared Channel (PDSCH) configuration, the receiving unit receives an activation information element not included in the PDSCH configuration, the activation information element indicating whether the TCI state in the list of TCI states is valid for a specific signal, and a control unit of the terminal determines whether the TCI state in the list of TCI states is valid for the specific signal based on the activation information element; The base station includes a transmitter that transmits the TCI state list configuration and the RRC information element; a control unit of the base station that controls determination of a reference signal for the beam failure detection and radio link monitoring based on the RRC information element and the TCI state in the TCI state list when the reference signal for the beam failure detection and radio link monitoring is not configured; a control unit of the base station, after the specific symbol from the reception of the response, applying the new QCL source reference signal to at least one of the specific channel and signal to which the TCI state in the list of TCI states is applied; The transmitting unit transmits the activation information element, and the control unit of the base station determines whether the TCI state in the list of TCI states is valid for the specific signal based on the activation information element.

Images