Terminals, wireless communication methods, base stations and systems

Abstract

A terminal, according to one embodiment of the present disclosure, includes: a reception unit that receives an instruction as to a transmission configuration indication (TCI) state to be applied to a plurality of types of channels, and first information relating to a control resource set (CORESET) configured using a system information block or a master information block; and a control unit that determines the TCI state to be applied to the CORESET on the basis of the instruction and / or the first information. According to this embodiment of the present disclosure, the TCI state can be appropriately identified.

Description

Technical Field

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

Background Art

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

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] In future wireless communication systems (e.g., NR), it is being considered that 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 relationships).

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

[0007] Therefore, this disclosure relates to a terminal for appropriately determining the TCI state and a wireless communication method. 、 base station and system One of the objectives is to provide [this]. [Means for solving the problem]

[0008] A terminal relating to one aspect of this disclosure is a control resource set (CORESET (Control Resource Set) ) for multiple transmission setting instructions (TCI (Transmission Configuration Indication) ) Set the state List for Radio Resource Control (RRC) parameters as Received And receive Downlink Control Information (DCI). The receiving unit, when it does not receive a Medium Access Control control element (MAC CE) indicating one of the multiple TCI states, determines the physical downlink shared channel (PDSCH (Physical Downlink Shared Channel) ) demodulation reference signal (DM-RS (DeModulation Reference Signal)), Physical Downlink Control Channel (PDCCH) (Physical Downlink Control Channel) ) DM-RS and channel status information reference signal (CSI-RS (Channel State Information Reference Signal) ) is the synchronization signal / broadcast channel (SS) identified during the initial access procedure. (Synchronization Signal) / PBCH (Physical Broadcast Channel) ) Block and QCL (Quasi-Co-Location) A control unit which is assumed to be, Furthermore, the control unit, upon receiving the MAC CE, applies the DCI and the TCI state indicated by the MAC CE from among the plurality of TCI states to both the downlink and uplink signals, including PDSCH and PDCCH. do. [Effects of the Invention]

[0009] According to one aspect of this disclosure, the TCI state can be appropriately recognized. [Brief explanation of the drawing]

[0010] [Figure 1] Figures 1A and 1B show an example of a unified / common TCI framework. [Figure 2] Figure 2 shows an example of how to determine the application of the TCI state according to the first embodiment. [Figure 3] Figure 3 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 4] Figure 4 shows an example of the configuration of a base station according to one embodiment. [Figure 5] Figure 5 shows an example of the configuration of a user terminal according to one embodiment. [Figure 6] Figure 6 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 7] Figure 7 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

[0011] (TCI, spatial relations, QCL) In NR, it is considered to control at least one of signal and channel (expressed as signal / channel) 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 based on a transmission configuration indication state (Transmission Configuration Indication state (TCI state)).

[0012] The TCI state may represent what is applied to the downlink signal / channel. What corresponds to the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0013] The TCI state is information regarding the quasi-co-location (QCL) of a signal / channel and may be referred to as a spatial reception parameter, spatial relation information, etc. The TCI state may be set for each channel or each signal in the UE.

[0014] QCL is an index indicating the statistical properties of a signal / channel. For example, when a certain signal / channel and another signal / channel are in a QCL relationship, it may mean that at least one of Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter) is the same (QCL with respect to at least one of these) among these different signals / channels.

[0015] The spatial reception parameters may correspond to the UE's received beam (e.g., the received analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0016] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • QCL Type A (QCL-A): Doppler shift, Doppler spread, mean delay and delay spread, • QCL Type B (QCL-B): Doppler shift and Doppler spread, • QCL Type C (QCL-C): Doppler shift and mean delay, • QCL Type D (QCL-D): Spatial reception parameters.

[0017] The assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

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

[0019] The TCI state may, for example, be information regarding the QCL between the target channel (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 upper-layer signaling, physical layer signaling, or a combination thereof.

[0020] Physical layer signaling may include, for example, Downlink Control Information (DCI).

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

[0022] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: 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)), or a QCL detection reference signal (also called a QRS).

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

[0024] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (or its DMRS) and a QCL type X, and this RS may also be called the QCL source of the QCL type X in that TCI state.

[0025] (Unified / Common TCI Framework) According to the Unified TCI Framework, UL and DL channels can be controlled by a common framework. Rather than defining 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 be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0026] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams in total) are being considered.

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

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

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

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

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

[0033] For example, if N=M=1 is written, it may mean that the UE is notified / set / instructed to have a TCI state common to one UL and DL for a single TRP (a joint TCI state for a single TRP).

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

[0035] Furthermore, for example, if N=M=2 is written, it may mean that the UE is notified / set / instructed to have a common TCI state for multiple (two) TRPs and multiple (two) ULs and DLs (a joint TCI state for multiple TRPs).

[0036] Furthermore, if it is written as N=2, M=2, for example, it may mean that the UE is notified / configured / instructed to have multiple (two) UL TCI states and multiple (two) DL TCI states for multiple (two) TRPs (separate TCI states for multiple TRPs).

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

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

[0039] In the example in Figure 1A, the RRC parameter (information element) sets up multiple TCI states for both DL and UL. MAC CE may activate multiple TCI states from the set up TCI states. DCI may indicate one of the activated TCI states. DCI may be a UL / DL DCI. The indicated TCI state may be applied to at least one (or all) of the UL / DL channels / RS. A single DCI may indicate both UL TCI and DL TCI.

[0040] In the example shown in this diagram, one point may represent a single TCI state that applies to both UL and DL, or it may represent two TCI states that apply to UL and DL respectively.

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

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

[0043] In the example in Figure 1B, the RRC parameter sets up multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE may activate multiple TCI states (active TCI pool) from the set up multiple TCI states. Separate active TCI pools for UL and DL may be set up / activated.

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

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

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

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

[0048] The QCL rules for the unified TCI state of Rel.17 may differ depending on whether the unified TCI state of Rel.17 is shared with individual UE receptions on the PDSCH / PDCCH.

[0049] For DL ​​channels / RS that do not share the same instructed Rel.17 TCI state as individual UE receptions on PDSCH / PDCCH, all QCL rules specified in the existing specification (options B1 to B3 described below) may be supported. For example, for DL ​​channels / RS that share the same Rel.17 unified TCI state as individual UE receptions on PDSCH / PDCCH, at least one of the following QCL rules from options A1 and A2 may be supported with respect to source RS and QCL type. [Option A1] A tracking RS (TRS) is configured for the QCL type A source RS, and a CSI-RS (CSI-RS with repetition) for beam management (BM) is configured for the QCL type D source RS. [Option A2] TRS is configured for source RS of QCL type A and source RS of QCL type D.

[0050] QCL rules are defined in the existing specifications. For example, for PDSCH / PDCCH, the following options B1 to B3 are permitted. [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 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 without trs-info and without repetition, the UE assumes that the TCI state (TCI-State) indicates one or more of the following QCL types: Type A, which includes CSI-RS resources within the NZP-CSI-RS resource set configured with trs-Info, and Type D, which includes the same CSI-RS resources, if applicable. Type A, which includes CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info, and Type D, which includes SS / PBCH blocks, if applicable. Type A, which includes CSI-RS resources in an NZP-CSI-RS resource set configured with trs-Info, and Type D, which includes CSI-RS resources in an NZP-CSI-RS resource set configured with repetition, if applicable. If Type D is not applicable, Type B is used with CSI-RS resources in the NZP-CSI-RS resource set configured with trs-Info.

[0052] Explicit RRC parameters may be specified to indicate whether the unified TCI state of Rel.17 is shared with individual UE reception on PDSCH / PDCCH, or with dynamic grant / configured grant PUSCH and all individual PUCCH resources.

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

[0054] A UE monitors PDCCH candidates within one or more SS sets. These one or more SS sets may include at least one of the SS sets common to one or more UEs (common search space (CSS) sets) and SS sets specific to a UE (UE-specific search space (UE-specific search space (USS)) sets).

[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 CSS used for monitoring DCI formatted data scrambled for Cyclic Redundancy Check (CRC) by a 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 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 within a Master Information Block (MIB) transmitted over a Broadcast Channel (Physical Broadcast Channel (PBCH)) (for example, the Radio Resource Control (RRC) parameter "pdcch-ConfigSIB1").

[0058] Alternatively, the type 0-PDCCH CSS set may be configured based on information within cell-specific PDCCH information (e.g., the RRC parameter "PDCCH-ConfigCommon"), such as the RRC parameter "searchSpaceSIB1" or "searchSpaceZero".

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

[0060] A Type 0A-PDCCH CSS set may represent a set of CSS used for monitoring DCI formatted CRC scrambled by SI-RNTI in a given cell (e.g., a primary cell). A Type 0A-PDCCH CSS set may be configured based on information within cell-specific PDCCH information (e.g., the RRC parameter "searchSpaceOtherSystemInformation"). In this disclosure, a Type 0A-PDCCH CSS set may be referred to as a Type 0A CSS / CSS set.

[0061] A Type 1-PDCCH CSS set may represent a set of CSS used for monitoring DCI format data scrambled with Random Access (RA)-RNTI or TC-RNTI in a given cell (e.g., a primary cell). A Type 1-PDCCH CSS set may be configured based on information within cell-specific PDCCH information (e.g., the RRC parameter "ra-SearchSpace"). In this disclosure, a Type 1-PDCCH CSS set may be referred to as a Type 1 CSS / CSS set.

[0062] A Type 2-PDCCH CSS set may represent a set of CSS used for monitoring DCI formatted 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 within cell-specific PDCCH information (e.g., the RRC parameter "pagingSearchSpace"). In this disclosure, the Type 2-PDCCH CSS set may be referred to as a Type 2 CSS / CSS set.

[0063] A Type 3-PDCCH CSS set may represent a set of CSS used for at least one monitor of DCI formats that are CRC scrambled with Slot Format Indicator (SFI)-RNTI, INT-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. A Type 3-PDCCH CSS set may be configured based on information within UE-specific PDCCH information (e.g., the RRC parameter "SearchSpace"), which is UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config"). This UE-specific PDCCH information may be communicated to the UE through UE-specific RRC signaling (e.g., an RRC reconfiguration message). In this disclosure, a Type 3-PDCCH CSS set may be referred to as a Type 3 CSS / CSS set.

[0064] The USS set may represent a set of USS used for monitoring DCI format data that is CRC scrambled by C-RNTI or CS-RNTI. The USS set may be configured based on information within the UE-specific PDCCH information (e.g., the "SearchSpace" RRC parameter).

[0065] Each SS set as described above is associated with a Control Resource Set (CORESET). A CORESET may contain multiple types (for example, CORESET#0, a CORESET common to one or more UEs (cell-specific) (common CORESET), and a CORESET specific to a UE (individual CORESET)).

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

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

[0068] UE-specific CORESETs may be configured based on information within the UE-specific PDCCH information (e.g., the RRC parameter "PDCCH-Config") (e.g., the RRC parameter "ControlResourceSet"). Such CORESETs 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) within a cell may be, for example, 3.

[0069] (analysis) With respect to Rel.17TCI states, the unified / common TCI state may mean the indicated Rel.17TCI state using DCI / MAC CE / RRC (of Rel.17). In this disclosure, the indicated Rel.17TCI state and the indicated TCI state and the common TCI state may be interchangeable.

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

[0071] With respect to Rel.17TCI states, TCI states other than the unified / common TCI state may mean Rel.17TCI states configured using MAC CE / RRC (of Rel.17). In this disclosure, the configured Rel.17TCI state may be interpreted as a configured TCI state, and a TCI state other than the common TCI state.

[0072] The configured Rel.17TCI state does not have to be shared with at least one of the following: UE-specific reception in PDSCH / PDCC (updated using Rel.17 DCI / MAC CE / RRC), dynamic grant (DCI) / configured grant PUSCH, and multiple (e.g., all) dedicated PUCCH resources.

[0073] In Rel.15, whether or not to instruct CORESET#0 to enter the TCI state depended on the base station's implementation.

[0074] In Rel.15, for CORESET#0 that has been instructed to have a TCI state, that instructed TCI state will be applied. For CORESET#0 that has not been instructed to have a TCI state, the SSB and QCL selected during the most recent PRACH transmission will be applied.

[0075] The Common TCI State Framework of Rel.17 examines the TCI state related to CORESET#0. However, the behavior when a Rel.17 TCI state is specified for CORESET#0 and when it is not is not sufficiently examined. Specifically, for example, it is unclear whether, when a Rel.17 TCI state is not specified for CORESET#0, it will perform the actions defined up to Rel.15 or a different action.

[0076] Furthermore, the behavior of the UE regarding the Rel.17TCI state is unclear in cases where the TCI state (including the Rel.17TCI state) is not set using the RRC parameter, and in cases where an activation command indicating at least one TCI state using MAC CE is not received.

[0077] If these operations are not clearly understood, it may be impossible to properly set, instruct, and apply the TCI state, potentially leading to a decrease in throughput and communication quality.

[0078] Therefore, the inventors conceived of a method for applying the TCI state.

[0079] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

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

[0081] In this disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be interpreted interchangeably. In this disclosure, terms such as support, control, controllable, operate, and operable may be interpreted interchangeably.

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

[0083] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

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

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

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

[0087] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relationship group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, 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 assumptions, etc., may be interpreted interchangeably.

[0088] In this disclosure, common beam, common TCI, common TCI state, Rel.17 TCI state, TCI state after Rel.17, unified TCI, unified TCI state, TCI state applicable to multiple types of channel / RS, TCI state applicable to multiple (multiple types) of channel / RS, TCI state applicable to multiple types of channel / RS, TCI state for multiple types of signals, TCI state for multiple types of channel / 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 DL ​​and UL respectively may be interpreted as one another.

[0089] In this disclosure, the TCI states of Rel.15 / 16, the TCI states / spatial relationships applicable only to specific channels / RSs, and the TCI states / spatial relationships applicable to one type of channel / RS may be interpreted as mutually exclusive.

[0090] In this disclosure, multiple TCI states set by RRC IE, multiple TCI states activated by MAC CE, information about one or more TCI states, TCI state setting, 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, separate UL TCI state pool may be interpreted as one another.

[0091] In this disclosure, DL TCI, DL only TCI, separate DL only TCI, DL common TCI, DL unified TCI, common TCI, and unified TCI may be interpreted interchangeably. In this disclosure, UL TCI, UL only TCI, separate UL only TCI, UL common TCI, UL unified TCI, common TCI, and unified TCI may be interpreted interchangeably.

[0092] In this disclosure, the channels / RS to which the Unified TCI status applies may be PDSCH / PDCCH / CSI-RS / PUSCH / PUCCH / SRS.

[0093] In this disclosure, UE-specific reception on PDSCH / PDCCH, PDSCH / PDCCH reception based on PDSCH configuration (PDSCH-Config) / PDCCH configuration (PDCCH-Config), UE-specific PDSCH / PDCCH, and UE-specific PDSCH / PDCCH resources may be interpreted interchangeably. In this disclosure, PUSCH based on dynamic grant / configured grant, PUSCH based on PUSCH configuration (PUSCH-Config) / configured grant configuration (ConfiguredGrantConfig), UE-specific PUSCH, and UE-specific PUSCH resources may be interpreted interchangeably. In this disclosure, individual PUCCH resources, PUCCH resources based on PUCCH configuration (PUCCH-Config), UE-specific PUCCH, and UE-specific PUCCH resources may be interpreted interchangeably.

[0094] (Wireless communication method) In each embodiment, the unified TCI state, the shared TCI state, the indicated Rel.17TCI state, and the indicated Rel.17TCI state may be interpreted as being interchangeable.

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

[0096] This disclosure defines CORESET A / B / C. The names of each CORESET are merely examples and are not exhaustive.

[0097] In this disclosure, CORESET A may mean a CORESET related to a UE-specific reception other than a specific CORESET (e.g., CORESET#0). Such UE-specific reception may be a UE-specific reception in a PDCCH within a CC (cell).

[0098] CORESET A may be associated with USS and a specific type of CSS (e.g., type 3 CSS). Alternatively, CORESET A may be associated with USS only. Furthermore, CORESET A may be associated with a specific type of CSS (e.g., type 3 CSS) only.

[0099] In this disclosure, CORESET B may mean a CORESET associated with a non-UE specific reception other than a particular CORESET (e.g., CORESET#0). Such non-UE specific reception may be a non-UE specific reception in a PDCCH within a CC (cell).

[0100] CORESET B may be associated with USS and CSS of types other than specific types (e.g., type 3). CORESET B may also be associated with any CSS (e.g., CSS containing type 3).

[0101] In this disclosure, CORESET C may mean a CORESET relating to UE-specific and non-UE-specific receptions other than a specific CORESET (e.g., CORESET#0). Such UE-specific receptions may be UE-specific and non-UE-specific receptions in a PDCCH within a CC (cell).

[0102] As described above, by defining CORESET A / B / C, even if the framework is updated from a Rel.15 / 16 TCI state to a Rel.17 TCI state, the behavior of the UE can be defined without prohibiting settings that were permitted in Rel.15 / 16.

[0103] For any PDCCH and each PDSCH received in CORESET A, the UE may apply the indicated Rel.17TCI state.

[0104] For any PDCCH and each PDSCH received in CORESET B, the UE may use RRC (RRC IE) to receive information on whether or not to apply the indicated Rel.17TCI state associated with the serving cell, which is determined for each CORESET.

[0105] The UE may receive at least one of the following using upper-layer signaling (RRC signaling / MAC CE): configuration information for one or more CORESETs (which may be called first configuration information) and configuration information for one or more search spaces (search space sets) (which may be called second configuration information).

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

[0107] <First Embodiment> The first embodiment relates to CORESET#0 (CORESET 0).

[0108] If the Rel.17TCI state is indicated for CORESET#0, the UE may follow at least one of the following options 1-3:

[0109] 《Option 1》 If the Rel.17TCI state is indicated for CORESET#0, the UE may follow the rules applicable to CORESET B.

[0110] For example, if a Rel.17TCI state is specified for CORESET#0, the UE may use RRC (RRC IE) to receive information on whether or not to apply the specified Rel.17TCI state. The specified Rel.17TCI state is determined per CORESET and may be related to the serving cell.

[0111] In this case, if the indicated Rel.17TCI state is not to be applied (for example, if the information indicates that the indicated Rel.17TCI state is not to be applied), the UE may determine which TCI state to apply to CORESET#0 based on the signaling of the existing MAC CE (i.e., based on the MAC CE that activates the TCI state).

[0112] 《Option 2》 If a Rel.17 TCI state is indicated for CORESET#0, the UE may determine which TCI state to apply to CORESET#0 based on the signaling of existing MAC CEs (i.e., based on the MAC CEs that activate the TCI state for that CORESET).

[0113] 《Option 3》 If the Rel.17TCI state is indicated for CORESET#0, the UE may follow the rules applicable to CORESET A.

[0114] For example, if a Rel.17TCI state is specified for CORESET#0, the UE may always apply the specified Rel.17TCI state.

[0115] Option 3 may apply, for example, when the indicated Rel.17TCI state is associated with the physical cell ID (PCID) of the serving cell.

[0116] For any of the above options 1-3, one action may be specified in the specification. Alternatively, for any of the above options 1-3, multiple actions may be specified in the specification, and the UE may be configured / notified of which action to perform using higher-layer signaling.

[0117] Additionally, if the Rel.17TCI state is indicated for CORESET#0, the UE may follow option 4 below.

[0118] 《Option 4》 If no Rel.17TCI status is indicated for CORESET#0, the UE may determine that CORESET#0 follows the QCL of the serving cell's SSB.

[0119] [Variations of the first embodiment] If no Rel.17TCI state is indicated for CORESET#0, the UE may determine the TCI state / QCL for CORESET#0 based on specific cases (e.g., cases 1 and 2 below).

[0120] [[Case 1]] If no Rel.17TCI state is indicated for CORESET#0, the UE may follow one of the above options 1-3.

[0121] For any of the above options 1-3, one action may be specified in the specification. Alternatively, for any of the above options 1-3, multiple actions may be specified in the specification, and the UE may be configured / notified of which action to perform using higher-layer signaling.

[0122] [[Case 2]] If no Rel.17TCI status is indicated for CORESET#0, the UE may determine that CORESET#0 follows the QCL of the serving cell's SSB.

[0123] The application of either Case 1 or 2 above may be configured / instructed to the UE using higher-layer signaling. The UE may determine whether either Case 1 or 2 applies based on such higher-layer signaling.

[0124] For example, if a Rel.17TCI state is indicated for any CORESET / Signal (RS) / Channel / Resource / Search Space, the UE may determine that Case 1 above applies. Otherwise, the UE may determine that Case 2 above applies.

[0125] For example, in the example shown in Figure 2, the UE determines whether the Rel.17TCI state is indicated for any of the CORESET / signal (RS) / channel / resource / search space (S110). If the indication is indicated, the UE determines that it falls under Case 1 (S120). If the indication is not indicated, the UE determines that it falls under Case 2 (S130).

[0126] According to the first embodiment described above, the QCL / TCI state of CORESET#0 can be appropriately determined. For example, even if the Rel.17TCI state is not (or is) specified for CORESET#0, the existing operation and the operation of Rel.17 can be appropriately switched.

[0127] <Second Embodiment> The second embodiment relates to a case in which RRC settings related to the TCI state are not made, or a case in which RRC settings related to the Rel.17TCI state are made, but the Rel.17TCI state is not indicated using MAC CE.

[0128] The UE may determine / assume, based on specific conditions, which TCI state / QCL / spatial domain filters to apply to specific DL channels / RS and UL channels / RS.

[0129] For example, the following may apply in at least one of the following cases: when no TCI state RRC parameters (e.g., tci-StatesPDCCH-ToAddList, tci-StatesPDCCH-ToReleaseList) are set for CORESET (Condition 1), or when one or more TCI state initials are provided for CORESET by TCI state RRC parameters (e.g., tci-StatesPDCCH-ToAddList, tci-StatesPDCCH-ToReleaseList, TCI-StateID_r17), but a MAC CE for an activation command for one or more of those TCI states is not received (Condition 2).

[0130] In at least one of conditions 1 and 2, the UE may assume / determine that a given DM-RS antenna port / RS are quasi-co-located with the SS / PBCH block the UE identified during the initial access procedure, or for a most recent configured grant push transmission for a same HARQ process. That configured grant push transmission may be a configured grant push transmitted by a UE in an RRC_INACTIVE state. That configured grant push transmission may be associated with an SS / PBCH block.

[0131] The specific DMRS antenna port may be at least one of the following: a DMRS antenna port for PDCCH reception, or a DMRS antenna port for the PDSCH / PDCCH DMRS in a certain CC in the case where the RRC parameter (TCI-StateID_r17) of the Rel.17TCI state is set. The specific RS may be a CSI-RS that conforms to the indicated Rel.17TCI state.

[0132] Furthermore, in at least one of conditions 1 and 2, the UE may assume / determine that the UL transmit space domain filter for a particular UL channel / RS is the same as the UL transmit space domain filter for PUSCH scheduled by the RAR UL grant during the initial access procedure.

[0133] The specific UL channel / RS may be, for example, at least one of the following: a dynamic grant (DCI) / configured grant-based PUSCH and PUCCH (resource) in a certain CC, and an SRS that follows the indicated Rel.17TCI state.

[0134] For example, the following may apply when CORESET is provided with one or more TCI state initials by TCI state RRC parameters (e.g., tci-StatesPDCCH-ToAddList, tci-StatesPDCCH-ToReleaseList, TCI-StateID_r17) as part of a reconfiguration associated with a synchronization procedure, but does not receive a MAC CE for an activation command for one or more of those TCI states (Condition 3).

[0135] In condition 3, the UE may assume / determine that a particular DMRS antenna port / RS is the UE's SS / PBCH block or CSI-RS resource and QCL identified during a random access procedure initiated by a reconfiguration associated with the synchronization procedure.

[0136] The specific DMRS antenna port may be at least one of the following: a DMRS antenna port for PDCCH reception, or a DMRS antenna port for the PDSCH / PDCCH DMRS in a certain CC in the case where the RRC parameter (TCI-StateID_r17) of the Rel.17TCI state is set. The specific RS may be a CSI-RS that conforms to the indicated Rel.17TCI state.

[0137] Furthermore, under condition 3, the UE may assume / determine that the UL transmit space domain filter for a particular UL channel / RS is the same as the UL transmit space domain filter for PUSCH scheduled by a RAR UL grant during a random access procedure initiated by a reconfiguration associated with the synchronization procedure.

[0138] The specific UL channel / RS may be, for example, at least one of the following: a dynamic grant (DCI) / configured grant-based PUSCH and PUCCH (resource) in a certain CC, and an SRS that follows the indicated Rel.17TCI state.

[0139] For example, the following may apply in at least one of the following cases: when one TCI state is applied to one CORESET (Condition 4), and when the UE receives a MAC CE that activates one or two TCI states provided for one CORESET (Condition 5).

[0140] If the Rel.17TCI state is indicated in at least one of conditions 4 and 5 (i.e., TCI-StateID_r17 is set), the UE may assume / determine that a particular DMRS antenna port / RS is QCL with the TCI state provided by the RRC parameter (TCI-StateID_r17) of the Rel.17TCI state.

[0141] The specific DMRS antenna port may be at least one of the following: a DMRS antenna port for PDCCH reception, or a DMRS antenna port for the PDSCH / PDCCH DMRS in a certain CC in the case where the RRC parameter (TCI-StateID_r17) of the Rel.17TCI state is set. The specific RS may be a CSI-RS that conforms to the indicated Rel.17TCI state.

[0142] Furthermore, in at least one of conditions 4 and 5, the UE may assume / determine that the UL transmit space domain filter for a particular UL channel / RS is determined based on a reference signal of the UL space relationship in the TCI state provided by the RRC parameter (TCI-StateID_r17) of the Rel.17TCI state.

[0143] The specific UL channel / RS may be, for example, at least one of the following: a dynamic grant (DCI) / configured grant-based PUSCH and PUCCH (resource) in a certain CC, and an SRS that follows the indicated Rel.17TCI state.

[0144] In addition, the (Rel.17)TCI state in the second embodiment described above may be a separate (DL / UL)TCI state.

[0145] Furthermore, if the (Rel.17)TCI state in the second embodiment is a joint (UL / DL)TCI state, the specific DMRS antenna port / RS and the specific UL channel / RS may be common. In other words, if the (Rel.17)TCI state in the second embodiment is a joint (UL / DL)TCI state, the specific DMRS antenna port / RS and the specific UL channel / RS may be common RS and QCL.

[0146] For example, the common RS may be a specific SSB (e.g., at least one of the SS / PBCH blocks for a UE identified during the initial access procedure, and the most recent configuration grant push transmission for the same HARQ process).

[0147] According to the second embodiment described above, even if the Rel.17TCI state is not set / indicated using RRC / MAC CE, the appropriate TCI state / QCL to apply to each channel / signal can be determined.

[0148] <Other Embodiments> 《UE Ability Information / Higher Layer Parameters》 Higher layer parameters (RRC IE) / UE capabilities may be defined corresponding to the features in each of the above embodiments. The higher layer parameters may indicate whether or not to enable the feature. The UE capabilities may indicate whether or not the UE supports the feature.

[0149] A UE that has the corresponding higher-level parameter set may perform that function. It may also be stipulated that "a UE that does not have the corresponding higher-level parameter set may not perform that function (for example, according to Rel. 15 / 16)."

[0150] A UE that reports / submits UE capability indicating support for that function may perform that function. It may be stipulated that "a UE that has not reported UE capability indicating support for that function shall not perform that function (e.g., in accordance with Rel. 15 / 16)."

[0151] If the UE reports / sends a UE capability indicating support for that function, and the corresponding higher-layer parameters are set, the UE may perform that function. It may also be stipulated that "if the UE does not report / send a UE capability indicating support for that function, or if the corresponding higher-layer parameters are not set, the UE shall not perform that function (e.g., in accordance with Rel. 15 / 16)."

[0152] Which of the above multiple embodiments / modes / options / choices / functions is used may be set by higher-layer parameters, reported by the UE as UE capability, specified in the specification, or determined by the reported UE capability and the setting of the higher-layer parameters.

[0153] UE capability may indicate whether the UE supports at least one of the following features: • Unified TCI framework (at least one of the following: joint TCI state pool, separate TCI state pool, beam indication for the joint TCI state pool, beam indication for the separate TCI state). UE capability may include at least one of the following: maximum number of unified TCI states set by the RRC IE (number supported by the UE), maximum number of TCI states set for joint beam indication, maximum number of UL TCI states for separate beam indication (number supported by the UE), maximum number of DL TCI states for separate beam indication. UE capability may also include at least one of the following: maximum number of active TCI states for unified TCI states (common beam indication) (number supported by the UE), maximum number of active TCI states for joint beam indication (number supported by the UE), maximum number of active UL TCI states for separate beam indication (number supported by the UE), maximum number of active DL TCI states for separate beam indication (number supported by the UE). • Setting whether or not to apply Rel.17TCI status for each CORESET / searchspace set.

[0154] Based on the above UE capabilities / higher layer parameters, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

[0160] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0161] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

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

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

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

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

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

[0167] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

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

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

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

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

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

[0173] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

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

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

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

[0177] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

[0179] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0180] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0181] (base station) Figure 4 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

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

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

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

[0185] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

[0191] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

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

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

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

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

[0196] The transmission path interface 140 may send and receive signals (backhaul signaling) with 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.

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

[0198] The transmitting / receiving unit 120 may transmit an instruction for a transmission configuration indication (TCI) state (common TCI state) applicable to multiple types of channels, and first information relating to a control resource set (CORESET, e.g., CORESET#0) set using a system information block or a master information block. The control unit 110 may use at least one of the instruction and the first information to instruct a TCI state to be applied to the CORESET (first embodiment).

[0199] (User terminal) Figure 5 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

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

[0201] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

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

[0204] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

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

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

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

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

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

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

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

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

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

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

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

[0216] The transmitting / receiving unit 220 may receive an instruction for a transmission configuration indication (TCI) state (common TCI state) applicable to multiple types of channels, and first information relating to a control resource set (CORESET, e.g., CORESET#0) set using a system information block or a master information block. The control unit 210 may determine the TCI state to apply to the CORESET based on at least one of the instruction and the first information (first embodiment).

[0217] The transmitting / receiving unit 220 may receive second information regarding whether or not to apply the TCI state based on the instruction. The control unit 210 may apply the TCI state based on the instruction to the CORESET according to the second information (first embodiment).

[0218] The control unit 210 may apply a TCI state to the CORESET, which is instructed using a Medium Access Control element (MAC Control Element (CE)) (first embodiment).

[0219] When the TCI state is related to the physical cell ID of the serving cell, the control unit 210 may apply the TCI state based on the instruction to the CORESET (first embodiment).

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

[0221] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0223] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0224] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

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

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

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

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

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

[0231] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

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

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

[0236] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

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

[0238] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

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

[0240] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0241] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

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

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

[0244] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

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

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

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

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

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

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

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

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

[0253] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

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

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

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

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

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

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

[0261] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0262] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

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

[0266] 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", "transmission 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. can be used interchangeably.

[0267] 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. can be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0268] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

[0269] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" can be used interchangeably.

[0270] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

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

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

[0273] The mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

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

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

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

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

[0279] The information service unit 59 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

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

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

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

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

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

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

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

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

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

[0289] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be rearranged as long as there is no contradiction. For example, regarding the methods described in the present disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0290] Each aspect / embodiment described in the present disclosure may be applied to systems that utilize 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 a decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable wireless communication methods, and next-generation systems extended, modified, created, or defined based on these. Also, multiple systems may be combined (for example, a combination of LTE or LTE-A and 5G, etc.) and applied.

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

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

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

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

[0295] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0296] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0297] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0298] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

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

[0300] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

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

[0303] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives a list of multiple transmission configuration indication (TCI) states for a control resource set (CORESET) as Radio Resource Control (RRC) parameters, and receives downlink control information (DCI), The system includes a control unit that, when it does not receive a Medium Access Control element (MAC CE) indicating one of the multiple TCI states, assumes that the demodulation reference signal (DM-RS) of the Physical Downlink Shared Channel (PDSCH), the DM-RS of the Physical Downlink Control Channel (PDCCH), and the Channel State Information Reference Signal (CSI-RS) are the synchronization signal / broadcast channel (SS / PBCH) block and QCL (Quasi-Co-Location) identified during the initial access procedure. The terminal is characterized in that, when the control unit receives the MAC CE, it applies the TCI state indicated by the DCI and the MAC CE from among the plurality of TCI states to both the downlink and uplink signals, including the PDSCH and PDCCH.

2. The terminal according to claim 1, characterized in that, when the MAC CE is not received, the spatial domain filters for the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Sounding Reference Signal (SRS) are the same as the spatial domain filters for the PUSCH scheduled by the UL (Uplink) grant during the initial access procedure.

3. The steps include receiving a list of multiple Transmission Configuration Indication (TCI) states for a Control Resource Set (CORESET) as Radio Resource Control (RRC) parameters, and receiving Downlink Control Information (DCI), The procedure includes the step of assuming that, if a Medium Access Control element (MAC CE) indicating one of the multiple TCI states is not received, the demodulation reference signal (DM-RS) of the Physical Downlink Shared Channel (PDSCH), the DM-RS of the Physical Downlink Control Channel (PDCCH), and the Channel State Information Reference Signal (CSI-RS) are the synchronization signal / broadcast channel (SS / PBCH) block and QCL (Quasi-Co-Location) identified during the initial access procedure, A wireless communication method for a terminal, characterized in that, when receiving the MAC CE, the TCI state indicated by the DCI and the MAC CE from among the plurality of TCI states is applied to both the downlink and uplink signals, including the PDSCH and PDCCH.

4. A transmission unit that transmits a list of multiple transmission configuration indication (TCI) states for a control resource set (CORESET) as Radio Resource Control (RRC) parameters, and transmits downlink control information (DCI), The system includes a control unit that, when it does not transmit a Medium Access Control element (MAC CE) indicating one of the multiple TCI states, determines that the demodulation reference signal (DM-RS) of the Physical Downlink Shared Channel (PDSCH), the DM-RS of the Physical Downlink Control Channel (PDCCH), and the Channel State Information Reference Signal (CSI-RS) are QCLs (Quasi-Co-Location) with the synchronization signal / broadcast channel (SS / PBCH) block identified during the initial access procedure. The base station is characterized in that, when the control unit transmits the MAC CE, it applies the TCI state indicated by the DCI and the MAC CE from among the plurality of TCI states to both the downlink and uplink signals, including the PDSCH and PDCCH.

5. A system having terminals and base stations, The aforementioned terminal is A receiving unit that receives a list of multiple transmission configuration indication (TCI) states for a control resource set (CORESET) as Radio Resource Control (RRC) parameters, and receives downlink control information (DCI), The system includes a control unit that, when it does not receive a Medium Access Control element (MAC CE) indicating one of the multiple TCI states, assumes that the demodulation reference signal (DM-RS) of the Physical Downlink Shared Channel (PDSCH), the DM-RS of the Physical Downlink Control Channel (PDCCH), and the Channel State Information Reference Signal (CSI-RS) are the synchronization signal / broadcast channel (SS / PBCH) block and QCL (Quasi-Co-Location) identified during the initial access procedure. When the control unit receives the MAC CE, it applies the TCI state indicated by the DCI and the MAC CE from among the plurality of TCI states to both the downlink and uplink signals, including the PDSCH and PDCCH. The aforementioned base station is A system characterized by having a transmitting unit that transmits the RRC parameters and the DCI.

Images