Terminal, wireless communication method, base station and system

Abstract

A TCI state is appropriately determined. A terminal according to an aspect of the present disclosure includes: a receiving unit that receives an instruction for a transmission configuration indication (TCI) state to be applied to multiple types of channels, and setting information relating to a control resource set (CORESET); and a control unit that, on the basis of a first terminal capability related to whether or not to support an operation of setting whether or not the TCI state is applied for each CORESET among other CORESETs excluding CORESETs having a predetermined index, and / or a second terminal capability related to whether or not to support the operation of setting whether or not the TCI state is applied for each CORESET among CORESETs having the predetermined index, controls at least one monitor of the CORESETs having the predetermined index and the other CORESETs.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

[0006] A unified TCI state is being considered, which applies the configured / activated / indicated TCI state to multiple types of channels / reference signals (RSs). However, the relationship between the TCI state of a control resource set (CORESET) and the unified TCI state is unclear. If this relationship is unclear, it may lead to degradation of communication quality, degradation of throughput, etc.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately determine the TCI state.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives an indication of a transmission configuration indication (TCI) state to be applied to multiple types of channels and configuration information regarding a control resource set (CORESET), and a control unit that controls monitoring of at least one of a CORESET having a predetermined index and the other CORESETs based on at least one of a first terminal capability regarding whether or not the terminal supports an operation of setting whether or not the TCI state is applied for each CORESET for other CORESETs other than the CORESET having the predetermined index, and a second terminal capability regarding whether or not the terminal supports an operation of setting whether or not the TCI state is applied for each CORESET for the CORESET having the predetermined index.

[0009] According to one aspect of the present disclosure, the TCI state can be appropriately determined.

[0010] 1A and 1B are diagrams illustrating an example of a unified / common TCI framework. FIG. 2 is a diagram illustrating an example of determining whether a TCI state applies according to a first embodiment. FIG. 3 is a diagram illustrating an example of determining whether a TCI state applies according to a third embodiment. FIG. 4 is a diagram illustrating another example of determining whether a TCI state applies according to the third embodiment. FIG. 5 is a diagram illustrating an example of determining whether a TCI state applies according to a fourth embodiment. FIG. 6 is a diagram illustrating another example of determining whether a TCI state applies according to the fourth embodiment. FIG. 7 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 8 is a diagram illustrating an example of a configuration of a base station according to an embodiment. FIG. 9 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment. FIG. 10 is a diagram illustrating an example of hardware configurations of a base station and a user terminal according to an embodiment. FIG. 11 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

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

[0020] The 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 tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

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

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

[0025] (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 a common beam for UL may apply to all UL channels and a common beam for DL ​​may apply to all DL channels.

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

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

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

[0029] DCI-based beam management (DCI-level beam indication) may indicate a common beam / unified TCI state from the same TCI pool for both UL and DL (joint common TCI pool, joint TCI pool, set). 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.

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

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

[0032] 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 / indicated 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 / indicated to the UE.

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

[0034] Also, for example, when N=1 and M=1 are written, this 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).

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

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

[0037] In the above example, the values ​​of N and M are 1 or 2, but the values ​​of N and M may be 3 or more, and N and M may be different.

[0038] It is being considered that N=M=1 will be supported in Rel. 17. It is being considered that other cases will be supported in Rel. 18 and later.

[0039] In the example of Figure 1A, 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. A 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.

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

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

[0042] 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 may simply mean receiving "instruction information."

[0043] In the example of Figure 1B, 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 each of the UL and DL may be configured / activated.

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

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

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

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

[0048] 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 dedicated reception on the PDSCH / PDCCH.

[0049] For DL ​​channels / RSs that do not share the same indicated Rel. 17 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 of the QCL rules in 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 source RS of QCL type A, and a CSI-RS for beam management (BM) (CSI-RS with repetition) is configured for the source RS of QCL type D. [Option A2] A TRS is configured for the source RS of QCL type A and the source RS of QCL type D.

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

[0051] For CSI-RS resources in a non-zero power (NZP)-CSI-RS resource set (NZP-CSI-RS-ResourceSet) configured with trs-Info and without repetition, the UE assumes 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, if applicable, Type D with SS / PBCH blocks. 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, and Type B with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info if Type D is not applicable.

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

[0053] (Search Space Set) In NR, one or more search space (SS) sets are configured in the UE. The SS set is a set of PDCCH candidates (PDCCH candidates) that the UE monitors. The SS set is also called a PDCCH search space set, search space, etc.

[0054] The UE monitors PDCCH candidates in one or more SS sets, which may include at least one of an SS set common to one or more UEs (common search space (CSS) set) and a SS set specific to a UE (UE-specific search space (USS) set).

[0055] The CSS set may include, for example, at least one of the following: Type 0 - PDCCH CSS set Type 0A - PDCCH CSS set Type 1 - PDCCH CSS set Type 2 - PDCCH CSS set Type 3 - PDCCH CSS set

[0056] A Type-0-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are Cyclic Redundancy Check (CRC)-scrambled with the System Information-Radio Network Temporary Identifier (SI-RNTI) in a given cell (e.g., a primary cell). In this disclosure, a Type-0-PDCCH CSS set may also be referred to as a Type-0 CSS / CSS set.

[0057] The Type 0-PDCCH CSS set may be configured in the UE based on information in a Master Information Block (MIB) transmitted on a Physical Broadcast Channel (PBCH) (e.g., the Radio Resource Control (RRC) parameter "pdcch-ConfigSIB1").

[0058] Alternatively, the Type 0-PDCCH CSS set may be configured based on information (e.g., the RRC parameters "searchSpaceSIB1" or "searchSpaceZero") in information about a cell-specific PDCCH (cell-specific PDCCH information, e.g., the RRC parameter "PDCCH-ConfigCommon").

[0059] The cell-specific PDCCH information may be signaled to the UE via system information (e.g., System Information Block (SIB) 1) or UE-specific RRC signaling (e.g., configuration information for synchronization in an RRC reconfiguration message (e.g., the RRC parameter "ReconfigurationWithSync")).

[0060] The Type 0A-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with SI-RNTI in a given cell (e.g., a primary cell). The Type 0A-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "searchSpaceOtherSystemInformation"). In this disclosure, the Type 0A-PDCCH CSS set may also be referred to as a Type 0A CSS / CSS set.

[0061] The Type 1-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with the Random Access (RA)-RNTI or TC-RNTI in a given cell (e.g., a primary cell). The Type 1-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "ra-SearchSpace"). In this disclosure, the Type 1-PDCCH CSS set may also be referred to as a Type 1 CSS / CSS set.

[0062] The Type 2-PDCCH CSS set may represent a set of CSSs used to monitor DCI formats that are CRC-scrambled with Paging (P)-RNTI in a given cell (e.g., a primary cell). The Type 2-PDCCH CSS set may be configured based on information in cell-specific PDCCH information (e.g., the RRC parameter "pagingSearchSpace"). In this disclosure, the Type 2-PDCCH CSS set may also be referred to as a Type 2 CSS / CSS set.

[0063] The Type 3-PDCCH CSS set may represent a set of CSSs used to monitor at least one of DCI formats CRC-scrambled with Slot Format Indicator (SFI)-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, and TPC-SRS-RNTI. The Type 3-PDCCH CSS set may be configured based on information (e.g., the RRC parameter "SearchSpace") in UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config"). The UE-specific PDCCH information may be notified to the UE by UE-specific RRC signaling (e.g., an RRC reconfiguration message). In the present disclosure, the Type 3-PDCCH CSS set may also be referred to as a Type 3 CSS / CSS set.

[0064] The USS set may represent a set of USSs used to monitor DCI formats that are CRC-scrambled by the C-RNTI or CS-RNTI. The USS set may be configured based on information in the UE-specific PDCCH information (e.g., the RRC parameter "SearchSpace").

[0065] Each SS set is associated with a control resource set (CORESET). The CORESET may include multiple types (e.g., CORESET #0, a CORESET common to one or more UEs (cell-specific) (common CORESET), and a UE-specific CORESET (individual CORESET)).

[0066] CORESET#0 may be configured based on information (e.g., the RRC parameter "ControlResourceSetzero") in the MIB or the cell-specific PDCCH information (e.g., the RRC parameter "PDCCH-ConfigCommon"). CORESET#0 may be associated with either a CSS set or a USS set.

[0067] The common CORESET may be configured based on information (e.g., the RRC parameter "commonControlResourceSet") in the cell-specific PDCCH information (e.g., the RRC parameter "PDCCH-ConfigCommon"). The common CORESET may be associated with either a CSS set or a USS set.

[0068] A UE-specific CORESET may be configured based on information (e.g., the RRC parameter "ControlResourceSet") in the UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config"). The CORESET may be associated with either a CSS set or a USS set. The maximum number of such CORESETs that can be configured per bandwidth part (BWP) in a cell may be, for example, three.

[0069] (Analysis) Regarding the Rel. 17 TCI state, the unified / common TCI state may refer to the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC. In the present disclosure, the indicated Rel. 17 TCI state may be interchangeably read as the indicated TCI state or the common TCI state.

[0070] The indicated Rel. 17 TCI state may be shared with at least one of the UE-specific reception of PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The TCI state indicated by DCI / MAC CE / RRC may be referred to as the common TCI state.

[0071] Regarding the Rel. 17 TCI state, a TCI state other than the unified / common TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC. In the present disclosure, the term "configured Rel. 17 TCI state" may be interchangeably read as a configured TCI state or a TCI state other than the common TCI state.

[0072] The configured Rel. 17 TCI state may not be shared with at least one of UE-specific reception in PDSCH / PDCC (updated using Rel. 17 DCI / MAC CE / RRC), PUSCH of dynamic grant (DCI) / configured grant, and multiple (e.g., all) dedicated PUCCH resources. The configured Rel. 17 TCI state may be configured by RRC / MAC CE for each CORESET / resource / resource set, and may not be updated even if the indicated Rel. 17 TCI state (common TCI state) is updated.

[0073] <CORESET #0> In Rel. 15, whether to instruct the TCI state for CORESET #0 was up to the implementation of the base station. In Rel. 15, for CORESET #0 for which a TCI state is instructed, the instructed TCI state is applied. For CORESET #0 for which a TCI state is not instructed, the SSB and QCL selected at the time of the latest (most recent) PRACH transmission are applied.

[0074] In the common TCI state framework for Rel. 17 and later, the TCI state for CORESET #0 is considered.

[0075] For example, in the framework of common TCI states for Rel. 17 and later, whether to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication of COESET #0 is configured by RRC for each CORESET, and if not, the legacy MAC CE / RACH signaling mechanism may be used.

[0076] Note that the CSI-RS associated with the Rel. 17 TCI state applied to CORESET #0 may be QCL with the SSB associated with the serving cell PCI (physical cell ID) (similar to Rel. 15). CORESET #0 may support only CSS configuration, or both CSS and USS configuration. Alternatively, only USS configuration may be supported.

[0077] On the other hand, regarding the Rel. 17 TCI status indication of COESET #0, how to control the TCI status becomes an issue when a UE does not support RRC indicating whether the indicated Rel. 17 status associated with the serving cell is applicable or when RRC is not configured.

[0078] <CORESET #A / #B / #C> In Rel. 17 and later, it is being considered to introduce / support CORESET classification based on predetermined conditions (e.g., whether reception is UE-specific / non-UE-specific, etc.).

[0079] For example, it is being considered that the indicated Rel. 17 TCI state be applied to UE-specific channels / signals (RS), and that the UE be notified by higher layer signaling (RRC signaling) whether the indicated Rel. 17 TCI state or the configured Rel. 17 TCI state be applied to non-UE-specific channels / signals.

[0080] It is being considered that the RRC parameters for the Rel. 17 TCI state (TCI state ID) to be configured will have the same configuration as the RRC parameters for the TCI state in Rel. 15 / 16. It is also being considered that the Rel. 17 TCI state to be configured / indicated per CORESET / per resource / per resource set using RRC / MAC CE. It is also being considered that the UE will determine the setting / indication based on specific parameters.

[0081] It is considered that the UE updates the indicated TCI state and the configured TCI state separately. For example, if the common TCI state for the indicated TCI state is updated, the configured TCI state may not be updated. It is also considered that the UE determines whether to update the TCI state based on a specific parameter.

[0082] Furthermore, regarding the PDCCH / PDSCH, it is being considered to use higher layer signaling (RRC / MAC CE) to switch whether the indicated Rel. 17 TCI state is applied or not (the configured Rel. 17 TCI state is applied, or a TCI state configured separately from the indicated Rel. 17 TCI state is applied).

[0083] Regarding intra-cell beam indication (TCI state indication), it is being considered to support Rel. 17 TCI states indicated for a UE-specific CORESET and a PDSCH associated with the CORESET, and a non-UE-specific CORESET and a PDSCH associated with the CORESET.

[0084] Also, for inter-cell beam indication (e.g., L1 / L2 inter-cell mobility), it is considered to support Rel. 17 TCI state indication for UE-specific CORESET and its associated PDSCH.

[0085] Regarding the operation of these Rel. 17 TCI states, there is insufficient consideration of the definitions of UE-specific and non-UE-specific channels / signals, UE capabilities, etc.

[0086] Thus, if the definitions of UE-specific channels / signals and non-UE-specific channels / signals, and the support / configuration of UE capabilities are not clear, the TCI state cannot be set / indicated / applied appropriately, which may result in a decrease in throughput / communication quality.

[0087] Therefore, the present inventors have studied methods for applying / setting the TCI state and have come up with the idea for this embodiment.

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

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

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

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

[0092] 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, etc., or a combination thereof.

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

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

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

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

[0097] In the present disclosure, the terms common beam, common TCI, common TCI state, Rel. 17 TCI state, TCI state for Rel. 17 or later, unified TCI, unified TCI state, TCI state applicable 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, and separate TCI state for each of DL and UL may be interpreted as interchangeable.

[0098] In the present disclosure, the terms TCI states of Rel. 15 / 16, TCI states / spatial relationships that apply only to specific channels / RSs, and TCI states / spatial relationships that apply to one type of channel / RS may be interpreted interchangeably.

[0099] In the present disclosure, the terms 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.

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

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

[0102] In the present disclosure, UE-specific reception on PDSCH / PDCCH, reception of PDSCH / PDCCH based on 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 based on dynamic grant / configuration grant, PUSCH based on PUSCH configuration (PUSCH-Config) / configuration grant configuration (ConfiguredGrantConfig), UE-specific PUSCH, and UE-specific PUSCH resource may be interchangeable. In the present disclosure, individual PUCCH resource, PUCCH resource based on PUCCH configuration (PUCCH-Config), UE-specific PUCCH, and UE-specific PUCCH resource may be interchangeable.

[0103] (Wireless Communication Method) In each embodiment, the unified TCI state, the shared TCI state, the indicated Rel. 17 TCI state, and the indicated Rel. 17 TCI state may be read as interchangeable.

[0104] In each embodiment, a search space, a search space set, a search space setting, and a CORESET associated with a search space set may be interchangeable. In each embodiment, a UE-specific search space set and a terminal-specific search space set may be interchangeable. In each embodiment, a CSS set and a CSS set of type 0 / 0A / 1 / 2 / 3 may be interchangeable.

[0105] In this disclosure, CORESET A / B / C are defined. The names of each CORESET are merely examples and are not limited to these descriptions.

[0106] In this disclosure, CORESET A may refer to a CORESET related to UE-specific reception other than a specific CORESET (e.g., CORESET #0), which may be UE-specific reception on PDCCH in a certain CC (cell).

[0107] CORESET A may be associated with USS and a specific type of CSS (e.g., type 3 CSS) (e.g., CORESET with USS + CSS type 3), or CORESET A may be associated with USS only (e.g., CORESET with USS only), or CORESET A may be associated with a specific type of CSS (e.g., type 3 CSS) only (e.g., CORESET with CSS type 3 only).

[0108] In this disclosure, CORESET B may refer to a CORESET related to non-UE-specific reception other than a specific CORESET (e.g., CORESET #0), which may be non-UE-specific reception on PDCCH in a certain CC (cell).

[0109] CORESET B may be associated with CSS (e.g., CORESET with CSS only), or with a type of CSS other than a specific type (e.g., type 3) (e.g., CORESET with CSS other than CSS type 3), or CORESET B may be associated with any CSS (e.g., CSS including type 3).

[0110] In this disclosure, CORESET C may refer to a CORESET related to UE-specific and non-UE-specific reception other than a specific CORESET (e.g., CORESET #0). The UE-specific reception may be UE-specific and non-UE-specific reception on PDCCH in a CC (cell). Alternatively, CORESET C may be a CORESET that includes both the contents / elements of CORESET A and the contents / elements of CORESET B.

[0111] The definitions of CORESET A / B / C are not limited to this, and each of CORESET A / B / C may be defined to correspond to at least a different USS / CSS or a different CSS type.

[0112] By defining CORESET A / B / C as described above, even when the TCI state framework of Rel. 15 / 16 is updated to the TCI state framework of Rel. 17, it is possible to specify the UE operation without prohibiting the settings allowed in Rel. 15 / 16.

[0113] For reception of any PDCCH and respective PDSCH in CORESET A, the UE may apply the indicated Rel. 17 TCI state.

[0114] For reception of any PDCCH and respective PDSCH in CORESET B, the UE may receive information using RRC (RRC IE) regarding whether the indicated Rel. 17 TCI state associated with the serving cell, determined per CORESET, applies or not.

[0115] The UE may receive, using higher layer signaling (RRC signaling / MAC CE), at least one of configuration information (which may be referred to as first configuration information) regarding one or more CORESETs (e.g., CORESET #0 / A / B / C) and configuration information (which may be referred to as second configuration information) regarding one or more search spaces (search space sets).

[0116] For example, the first configuration information may include at least information about a CORESET monitored by the UE, and the second configuration information may include information about a search space set corresponding to the CORESET. The information about the CORESET and the information about the search space set corresponding to the CORESET may be included in the same RRC parameter. In this case, the first configuration information and the second configuration information may be collectively regarded as one configuration information.

[0117] The Rel. 17 TCI state for CORESET #0 may be indicated to the UE using RRC / MAC CE.

[0118] First Embodiment The first embodiment relates to CORESET #0 (CORESET 0).

[0119] In the framework of common TCI states for Rel. 17 and later, whether to apply the indicated Rel. 17 TCI state associated with the serving cell for the Rel. 17 TCI state indication of COESET #0 may be configured by RRC for each CORESET (Rule 1-1). This RRC configuration may be configured from the base station to the UE.

[0120] If the Rel. 17 TCI state does not apply (or if the configuration by RRC does not apply), the base station / UE may apply the legacy MAC CE / RACH signaling mechanism (rule 1-2). Note that the Rel. 17 TCI state may also be called the TCI state after Rel. 17.

[0121] When the RRC configures whether to apply the indicated Rel. 17 TCI state related to the serving cell for each CORESET, whether the RRC (or an RRC parameter) is configured or whether the RRC supports the configuration may be reported from the UE to the base station by a UE capability (e.g., UE capability).

[0122] If the UE capability corresponding to the function related to Rule 1-1 (e.g., configured by the RRC) is not reported, Rule 1-2 may be applied.

[0123] Alternatively, if the UE capability corresponding to the function related to Rule 1-1 (e.g., the configuration by the RRC) is not reported, another Rule 1-3 different from Rule 1-2 may be applied. Rule 1-3 may be, for example, a rule that the indicated Rel. 17 TCI state is always applied.

[0124] 2 is a diagram showing an example of determining the application of the TCI state according to the first embodiment. It is determined whether the UE capability corresponding to the function related to Rule 1-1 (e.g., the RRC configuration) is reported / supported (S110). If the UE capability is reported / supported, the RRC determines the Rel. 17 TCI state for each CORESET (S120). On the other hand, if the UE capability corresponding to the function related to Rule 1-1 is not reported / supported, Rule 1-2 or Rule 1-3 is applied.

[0125] In this way, by defining UE capabilities corresponding to Rule 1-1 and controlling the setting / application of the TCI state based on whether or not the UE capabilities are reported, it becomes possible to appropriately set / apply the TCI state according to the UE capabilities of each terminal.

[0126] Second Embodiment The second embodiment relates to CORESET C.

[0127] In the common TCI framework for Rel. 17 and later, CORESET A / B / C may be supported if the indicated Rel. 17 TCI state for PDCCH reception and corresponding PDSCH reception applies.

[0128] For Rel. 17 TCI state indications, the following rules may be supported for each CORESET decision: Rule 2-1 may apply to CORESET A (e.g., USS / Type 3 CSS), Rule 2-2 may apply to CORESET B (e.g., CSS or non-Type 3 CSS), and Rule 2-3 may apply to CORESET C (e.g., CSS and USS).

[0129] For PDCCH reception and corresponding PDSCH reception for CORESET A, the UE always applies the indicated Rel. 17 TCI state (first rule 2-1).

[0130] For PDCCH reception and corresponding PDSCH reception for CORESET B, whether the UE applies the indicated Rel. 17 TCI state associated with the serving cell is determined by RRC for each CORESET (second rule 2-2).

[0131] For PDCCH reception and corresponding PDSCH reception for CORESET C, the third rule 2-3 may be applied.

[0132] [Option 2-1] The third rule 2-3 applied to CORESET C may be the same / common to the rule applied to other CORESETs (eg, CORESET B, CORESET #0).

[0133] For example, the third rule 2-3 may be the same as the second rule 2-2 applied to CORESET B. That is, for PDCCH reception and corresponding PDSCH reception for CORESET C, whether the UE applies the indicated Rel. 17 TCI state associated with the serving cell may be determined by RRC on a per-CORESET basis.

[0134] Specifically, it is assumed that in the Rel. 17 common TCI framework, application of the indicated Rel. 17 TCI state to PDCCH reception and respective PDSCH reception of a CORESET other than CORESET #0 (e.g., CORESET C) associated with both UE-dedicated and non-UE-dedicated reception of PDCCHs within a CC is supported. In this case, whether to apply the indicated Rel. 17 TCI state associated with the serving cell may be determined by RRC for each CORESET.

[0135] If the Rel. 17 TCI state does not apply (or if the RRC configuration does not apply), the base station / UE may apply the legacy MAC CE / RACH signaling mechanism.

[0136] When Option 2-1 is applied, the same behavior (rules) can be applied to CORESET#0 and CORESET C, which support CSS and USS.

[0137] [Option 2-2] The third rule 2-3 applied to CORESET C may be the same / common to the rule applied to another CORESET (eg, CORESET A).

[0138] For example, the third rule 2-3 may be the same as the second rule 2-1 applied to CORESET A. That is, for PDCCH reception and corresponding PDSCH reception for CORESET C, the UE may always apply the indicated Rel. 17 TCI state.

[0139] Specifically, in the Rel. 17 common TCI framework, it is assumed that application of the indicated Rel. 17 TCI state is supported for PDCCH reception and respective PDSCH reception of a CORESET other than CORESET #0 (e.g., CORESET C) associated with both UE-specific (UE-dedicated) and non-UE-specific (non-UE-dedicated) reception of PDCCHs within a CC. In this case, the UE always applies the indicated Rel. 17 TCI state.

[0140] In option 2-1, UE capabilities (for example, UE capability) related to rule 2-3 (or rule 2-2 / rule 1-1) applied to CORESET C may be set, and the UE may report the UE capabilities to the base station.

[0141] For example, the UE may report whether or not it supports Rule 2-3 (or Rule 2-2 / Rule 1-1) applied to CORESET C by using UE capabilities. The UE capabilities may be reported based on a predetermined unit. The predetermined unit may be at least one of per UE (per UE), per band (per band), per band combination (per band combination), per band in a band combination (per band in band combination), or per CC and per band in a band combination (per CC per band in band combination).

[0142] A UE that does not support Rule 2-3 (or Rule 2-2 / Rule 1-1) applied to CORESET C shown in Option 2-1 may apply another rule. The other rule may be, for example, Rule 2-3 (or Rule 2-1) applied to CORESET C shown in Option 2-1.

[0143] This allows a terminal with a predetermined UE capability to apply the same rules / operations to CORESET #0 and CORESET C, and a terminal without the predetermined UE capability to apply rules / operations that impose a smaller UE load.

[0144] [Variation] Option 2-1 and Option 2-2 may be applied by switching between them. For example, higher layer signaling (RRC signaling) that instructs switching between Option 2-1 and Option 2-2 may be defined, and the UE may apply Option 2-1 and Option 2-2 by switching between them by the higher layer signaling. This makes it possible to appropriately (or flexibly) determine the TCI state of CORESET C based on the UE capability of each terminal.

[0145] Although the second embodiment has been described with respect to CORESET C, it may also be applied to other CORESETs (for example, CORESET B / CORESET #0). Furthermore, the UE capabilities / RRC signaling described in the second embodiment may be reported / configured separately in a plurality of CORESETs (for example, CORESET C / CORESET B / CORESET #0), or may be reported / configured commonly for a plurality of CORESETs.

[0146] This embodiment may be commonly applied / set to intra-cell and inter-cell, or may be applied / set separately.

[0147] <Third Embodiment> The third embodiment relates to the configuration of multiple search space set types (USS+CSS) for CORESET and UE capabilities.

[0148] In the Rel. 17 common TCI framework, it is assumed that application of the indicated Rel. 17 TCI state is supported for PDCCH reception and respective PDSCH reception of a CORESET other than CORESET #0 (e.g., CORESET C) associated with both UE-specific and non-UE-specific PDCCH reception within a CC. In this case, whether or not to apply the indicated Rel. 17 TCI state associated with the serving cell is configured by RRC for each CORESET. If not, the existing MAC CE / RRC / RACH signaling mechanism is used. The CSI-RS associated with the Rel. 17 TCI state applied to the CORESET may be QCL'd with the SSB associated with the serving cell PCI. Support for this feature is optional for UEs.

[0149] Furthermore, for a specific CORESET (e.g., CORESET #0), both USS and CSS settings are supported. In this case, support of both USS and CSS may be optional for other CORESETs (e.g., CORESET C) other than the specific CORESET. UE capability information indicating whether or not the settings of both USS and CSS are supported for the other CORESET may be defined.

[0150] For example, at least one of the following two UE capabilities 3-1 to UE capability 3-2 may be defined, and if the UE capability is not reported (or the UE capability is not supported), the UE may be controlled to perform a predetermined action.

[0151] [UE Capability 3-1] In intra-cell and inter-cell beam management (intra-cell and inter-cell BM), UE capability information indicating whether to apply the Rel. 17 TCI state (e.g., the indicated Rel. 17 TCI state) for each CORESET by RRC to other CORESETs (or all other CORESETs) except CORESET #0 may be introduced / defined. In other words, the UE optionally supports RRC configuration of whether to apply the Rel. 17 TCI state (e.g., the indicated Rel. 17 TCI state) for each CORESET to all other CORESETs except CORESET #0.

[0152] If the UE does not have the UE capability information (e.g., does not support whether to apply the Rel. 17 TCI state per CORESET based on RRC), the UE may always apply the indicated Rel. 17 TCI state to all other CORESETs. For example, the UE may control to apply the indicated Rel. 17 TCI state to all other CORESETs except CORESET #0 and the corresponding scheduled PDSCHs.

[0153] 3 shows an example of determining the application of the TCI state based on UE capability 3-1. It is determined whether UE capability 3-1 is reported / supported (S210). If it is reported / supported, the RRC determines the Rel. 17 TCI state for each CORESET (S220). On the other hand, if UE capability 3-1 is not reported / supported, the indicated Rel. 17 TCI state may always be applied to all other CORESETs / corresponding PDSCHs (S230).

[0154] The other CORESETs (or all other CORESETs) except CORESET #0 may be, for example, CORESET A / B / C. Alternatively, all other CORESETs except CORESET #0 may be a specific CORESET.

[0155] A specific CORESET may be, for example, a CORESET (e.g., CORESET C) that supports both USS and CSS settings, and may be configured not to include CORESET A / B. In this case, UE capability 3-1 may not be applied to CORESET A that supports only USS / CORESET C that supports only CSS.

[0156] [UE Capability 3-2] At least for intra-cell beam management (intra-cell BM), UE capability information indicating whether the UE supports applying a Rel. 17 TCI state (e.g., an indicated Rel. 17 TCI state) per CORESET by RRC for CORESET #0 may be introduced / defined. In other words, the UE optionally supports RRC configuration of whether to apply a Rel. 17 TCI state (e.g., an indicated Rel. 17 TCI state) per CORESET for CORESET #0.

[0157] If the UE does not have the UE capability information (e.g., does not support whether to apply the Rel. 17 TCI state per CORESET based on RRC), the UE may always apply the indicated Rel. 17 TCI state for CORESET #0. For example, the UE may control to apply the indicated Rel. 17 TCI state to CORESET #0 and the corresponding scheduled PDSCH.

[0158] 4 shows an example of determining the application of the TCI state based on UE capability 3-2. It is determined whether UE capability 3-2 is reported / supported (S310). If it is reported / supported, the RRC determines the Rel. 17 TCI state for CORESET#0 for each CORESET (S320). On the other hand, if UE capability 3-2 is not reported / supported, the indicated Rel. 17 TCI state may always be applied to CORESET#0 / corresponding PDSCH (S330).

[0159] Both UE capability 3-1 and UE capability 3-2 (or both the behavior when UE capability 3-1 is not met and the behavior when UE capability 3-2 is not met) may be defined / supported, or only one of them may be supported.

[0160] Although UE capability 3-1 and UE capability 3-2 are defined for CORESET C and CORESET #0, respectively, this is not limitative. UE capability 3-1 and UE capability 3-2 may be applied to both CORESET C and CORESET #0, or to only one of them.

[0161] Also, when applied to CORESET C and CORESET #0, respectively, UE capabilities corresponding to each CORESET (e.g., UE capabilities 3-1 / 3-2) may be reported (e.g., a feature group (FG) reporting supportability may be specified for each of CORESET C and CORESET #0). Alternatively, when applied to CORESET C and CORESET #0, respectively, UE capabilities (e.g., FG) common to CORESET C and CORESET #0 may be reported.

[0162] <Fourth embodiment> The fourth embodiment relates to the configuration of CORESET when a predetermined UE capability is not reported (or not supported). Note that the fourth aspect may be applied in combination with the first to third aspects.

[0163] If a certain UE capability is not reported (or not supported), the certain CORESET may not be configured. The certain CORESET may be, for example, CORESET C.

[0164] In this case, if the UE does not report (or does not support) a certain UE capability, it may not assume that CORESET C is configured. That is, the UE may assume that either CORESET A or CORESET B is configured.

[0165] For example, at least one of the following two UE capabilities 4-1 to 4-2 may be defined, and if the UE does not report the UE capability (or does not support the UE capability), the UE may be controlled to perform a predetermined operation (for example, CORESET C is not set).

[0166] [UE Capability 4-1] In intra-cell and inter-cell beam management (intra-cell and inter-cell BM), UE capability information indicating whether to apply the Rel. 17 TCI state (e.g., the indicated Rel. 17 TCI state) for each CORESET by RRC for all CORESETs except CORESET #0 may be introduced / defined. In other words, the UE optionally supports RRC configuration of whether to apply the Rel. 17 TCI state (e.g., the indicated Rel. 17 TCI state) for each CORESET for all CORESETs except CORESET #0.

[0167] If the UE does not have the relevant UE capability information (e.g., does not support whether to apply Rel. 17 TCI status per RRC-based CORESET), the UE may not expect / assume that a CORESET other than CORESET #0 that supports both CSS and USS will be configured.

[0168] 5 shows an example of determining the application of the TCI state based on UE capability 4-1. It is determined whether UE capability 4-1 is reported / supported (S410). If it is reported / supported, the RRC determines the Rel. 17 TCI state for each CORESET for other CORESETs (S420). On the other hand, if UE capability 4-1 is not reported / supported, the UE does not need to expect / assume that a CORESET supporting both CSS and USS will be configured, except for CORESET #0 (S430).

[0169] [UE Capability 4-2] At least for intra-cell beam management (intra-cell BM), UE capability information indicating whether the UE supports applying a Rel. 17 TCI state (e.g., an indicated Rel. 17 TCI state) per CORESET by RRC for CORESET #0 may be introduced / defined. In other words, the UE optionally supports RRC configuration of whether to apply a Rel. 17 TCI state (e.g., an indicated Rel. 17 TCI state) per CORESET for CORESET #0.

[0170] If the UE does not have the relevant UE capability information (e.g., does not support whether to apply Rel. 17 TCI status per RRC-based CORESET), the UE may not expect / assume that a CORESET supporting both CSS and USS is configured for CORESET #0.

[0171] For example, in this case, the UE may assume that only CSS / only USS is configured in CORESET#0.

[0172] 6 shows an example of determining the application of the TCI state based on UE capability 4-2. It is determined whether UE capability 4-2 is reported / supported (S510). If it is reported / supported, the RRC determines the Rel. 17 TCI state for CORESET#0 on a per-CORESET basis (S520). On the other hand, if UE capability 4-2 is not reported / supported, the UE does not need to expect / assume that a CORESET supporting both CSS and USS will be configured for CORESET#0 (S530).

[0173] <<When both UE capability 4-1 and UE capability 4-2 are defined>> Both UE capability 4-1 (or operation when UE capability 4-1 is not met) and UE capability 4-2 (or operation when UE capability 4-2 is not met) may be defined / supported.

[0174] If the UE does not report UE capability 4-1 (or does not support UE capability 4-1), the UE does not assume that both CSS and USS are configured in a CORESET other than CORESET #0. In other words, the UE may assume that only either CSS or USS is configured in a CORESET other than CORESET #0.

[0175] If the UE does not report UE capability 4-2 (or does not support UE capability 4-2), the UE does not assume that both CSS and USS are configured in a certain CORESET in CORESET #0. In other words, the UE may assume that only either CSS or USS is configured in CORESET #0.

[0176] <<When either UE capability 4-1 or UE capability 4-2 is defined>> Only one of UE capability 4-1 (or operation when UE capability 4-1 is not met) and UE capability 4-2 (or operation when UE capability 4-2 is not met) may be defined / supported.

[0177] Assume that only UE capability 4-1 (or the operation when UE capability 4-1 is not satisfied) is defined.

[0178] If the UE does not report UE capability 4-1 (or does not support UE capability 4-1), the UE does not assume that both CSS and USS are configured in a certain CORESET in a CORESET other than CORESET #0. That is, the UE may assume that only either CSS or USS is configured in a CORESET other than CORESET #0. In this case, the UE may assume that both CSS and USS are configured in a certain CORESET in CORESET #0. That is, regardless of whether UE capability is reported, both CSS and USS may be supported for CORESET #0.

[0179] Alternatively, if the UE does not report UE capability 4-1 (or does not support UE capability 4-1), the UE may not assume that both CSS and USS are configured in a certain CORESET in all CORESETs (for example, CORESET #0 / A / B / C). In other words, the UE may assume that only either CSS or USS is configured in one CORESET. In this case, the UE does not assume that both CSS and USS are configured in a certain CORESET. In other words, it assumes that only either CSS or USS is configured in one CORESET #0. Therefore, depending on whether or not UE capability is reported (or the reported value), it is possible to switch whether or not both CSS and USS can be configured in both CORESET #0 and other CORESETs. This operation may also be applied when only UE capability 4-2 is defined and the UE capability 4-2 is not reported (or the UE capability 4-1 is not supported).

[0180] In the above embodiment, CORESET A / B / C may be included as the CORESETs excluding CORESET #0 (or all CORESETs). Alternatively, only CORESET C (or all CORESETs C) may be applied as the CORESETs excluding CORESET #0.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0207] (Base Station) Fig. 8 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0224] The transceiver 120 may transmit an indication of the transmission configuration indication (TCI) state applied to multiple types of channels and configuration information regarding a control resource set (CORESET). The configuration information may include, for example, at least the CORESET monitored by the UE, and may also include information regarding a search space set corresponding to the CORESET.

[0225] The control unit 110 may control the setting of the CORESET having a predetermined index and other CORESETs, and the TCI states corresponding to the CORESET having a predetermined index and other CORESETs, based on at least one of a first terminal capability regarding whether or not the operation of setting whether or not the TCI state is applied for each CORESET is supported for other CORESETs other than the CORESET having a predetermined index, and a second terminal capability regarding whether or not the operation of setting whether or not the TCI state is applied for each CORESET is supported for the CORESET having a predetermined index.

[0226] (User Terminal) Fig. 9 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0243] The transceiver 220 may receive an indication of the transmission configuration indication (TCI) state that applies to multiple types of channels and configuration information regarding a control resource set (CORESET). The configuration information may include, for example, at least the CORESET that the UE monitors, and may also include information regarding a search space set that corresponds to the CORESET.

[0244] The control unit 210 may control the monitoring of at least one of the CORESET having a specified index and other CORESETs based on at least one of a first terminal capability regarding whether or not the operation of setting whether or not the TCI state is applied for each CORESET is supported for other CORESETs other than the CORESET having a specified index, and a second terminal capability regarding whether or not the operation of setting whether or not the TCI state is applied for each CORESET is supported for the CORESET having a specified index.

[0245] If the first terminal capability information is not supported, the controller 210 may control the other CORESET to apply the TCI state.

[0246] If the first terminal capability information is not supported, the control unit 210 may assume that no CORESET that supports both a UE-specific search space set and a common search space set is configured, except for a CORESET having a predetermined index.

[0247] If the second terminal capability information is not supported, the controller 210 may control the TCI state to be applied to a CORESET having a predetermined index.

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

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

[0250] For example, a base station, a user terminal, or the like 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. 10 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, and the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0332] This application is based on Japanese Patent Application No. 2022-028484, filed February 25, 2022, the contents of which are incorporated herein in their entirety.

Claims

1. a receiving unit for receiving a transmission configuration indication (TCI) state indication applied to a plurality of types of channels and information about other control resource sets (CORESETs) except for a CORESET having a predetermined index; A terminal having a control unit that determines the TCI state to be applied to the other CORESET based on a terminal capability related to support of an operation of setting whether or not the instructed TCI state is applied for each CORESET.

2. The terminal according to claim 1 , wherein if the terminal does not have the terminal capability, the control unit applies the TCI state indicated for the other CORESET.

3. receiving an indication of a transmission configuration indication (TCI) state that applies to a plurality of types of channels and information about other control resource sets (CORESETs) except for a CORESET having a predetermined index; and determining the TCI state to be applied to the other CORESET based on the terminal capability regarding support for an operation of setting whether or not the instructed TCI state is applied for each CORESET.

4. a transmitter for transmitting a transmission configuration indication (TCI) state indication applicable to a plurality of types of channels and information on other control resource sets (CORESETs) except for a CORESET having a predetermined index; A base station having: a control unit that controls the instruction of the TCI state to be applied to the other CORESET based on a terminal capability regarding support for an operation of setting whether or not the instructed TCI state is applied for each CORESET.

5. A system having a terminal and a base station, The terminal a receiving unit for receiving a transmission configuration indication (TCI) state indication applied to a plurality of types of channels and information about other control resource sets (CORESETs) except for a CORESET having a predetermined index; a control unit that determines a TCI state to be applied to the other CORESET based on a terminal capability related to support of an operation of setting whether or not the instructed TCI state is applied for each CORESET; The base station A system comprising a transmitter for transmitting an indication of the TCI status and information regarding the other CORESET.