Terminal, wireless communication method and base station

Abstract

Properly recognize TCI conditions using AI-assisted beam prediction. [Solution] The terminal of the present invention has a receiving unit that receives configuration information including settings regarding transmission configuration indication (TCI) states to be applied to multiple types of channels and an instruction regarding the TCI state to be applied to the multiple types of channels, and a control unit that determines the start timing of application of the TCI state for AI-assisted beam prediction based on information regarding the start timing of application of the TCI state included in the configuration information and the instruction, and predicts beam quality using AI using the determined start timing of application of the TCI state.

Description

[Technical Field]

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

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

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

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

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

[0006] A unified TCI state is being considered, which applies the configured / activated / instructed TCI state to multiple types of channels / reference signals (RS). However, there are cases where it is unclear how to apply the unified TCI state. If such relationships are not clear, it may lead to degradation of communication quality, throughput, etc.

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

[0008] A terminal according to one embodiment of the present disclosure has a receiving unit that receives configuration information including settings regarding transmission configuration indication (TCI) states to be applied to multiple types of channels and an instruction regarding the TCI state to be applied to the multiple types of channels, and a control unit that determines the start timing of application of the TCI state for AI-assisted beam prediction based on information regarding the start timing of application of the TCI state included in the configuration information and the instruction, and predicts beam quality using AI using the determined start timing of application of the TCI state. [Effects of the Invention]

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

[0010] [Figure 1] 1A and 1B are diagrams showing an example of a common beam. [Figure 2] FIG. 2 is a diagram showing an example of a MAC CE defined in Rel. 16. [Figure 3] FIG. 3 is a diagram showing another example of MAC CE defined in Rel.16. [Figure 4] FIG. 4 is a diagram showing another example of MAC CE defined in Rel.16. [Figure 5] 5A and 5B are diagrams showing an example of an indication of a joint / separate TCI state. [Figure 6] FIG. 6 is a diagram showing an example of the timing until the application of the instructed TCI state. [Figure 7] FIG. 7 is a diagram illustrating an example of a criterion for starting a BAT according to the first embodiment. [Figure 8] 8A and 8B are diagrams illustrating an example of application of the TCI state according to option 1-1-1. [Figure 9] 9A and 9B are diagrams illustrating an example of application of the TCI state according to option 1-1-3. [Figure 10] FIG. 10 is a diagram illustrating an example of application of the TCI state according to option 1-1-4. [Figure 11] FIG. 11 is a diagram illustrating an example of application of the TCI state according to Variation 1 of Option 1-1-4. [Figure 12] FIG. 12 is a diagram illustrating an example of application of the TCI state according to Variation 2 of Option 1-1-4. [Figure 13] FIG. 13 is a diagram illustrating an example of the configuration of a MAC CE according to option 1-1-5-1. [Figure 14] FIG. 14 is a diagram illustrating an example of the configuration of a MAC CE according to option 1-1-5-2. [Figure 15]15A and 15B are diagrams illustrating an example of application of the TCI state according to option 1-2-1. [Figure 16] FIG. 16 is a diagram illustrating an example of application of the TCI state according to option 1-2-2. [Figure 17] Fig. 17A is a diagram showing an example of the association of BAT values ​​related to option 1-3-1, and Fig. 17B is a diagram showing an example of the association of BAT values ​​related to option 1-3-2. [Figure 18] 18A and 18B are diagrams illustrating an example of application of the TCI state according to the second embodiment. [Figure 19] FIG. 19 is a diagram illustrating another example of application of the TCI state according to the second embodiment. [Figure 20] FIG. 20 is a diagram showing an example of parameters of the TCI state according to option 2-1-1. [Figure 21] Fig. 21A is a diagram showing an example of application of the TCI state according to Variation 2-1-1-1, and Fig. 21B is a diagram showing an example of application of the TCI state according to Variation 2-1-1-2. [Figure 22] Fig. 22A is a diagram showing an example of application of the TCI state according to Variation 2-1-1-3, and Fig. 22B is a diagram showing an example of application of the TCI state according to Variation 2-1-1-4. [Figure 23] FIG. 23 is a diagram showing an example of parameters of the TCI state according to option 2-1-2. [Figure 24] FIG. 24 is a diagram illustrating an example of the configuration of a MAC CE according to option 2-1-3-1. [Figure 25] FIG. 25 is a diagram illustrating an example of the configuration of a MAC CE according to option 2-1-3-2. [Figure 26] 26A and 26B are diagrams showing an example of application of the TCI state according to option 2-2-1. [Figure 27] 27A and 27B are diagrams showing an example of application of the TCI state according to option 2-2-2. [Figure 28]FIG. 28 is a diagram illustrating an example of application of the TCI state according to aspect 5-1. [Figure 29] FIG. 29 is a diagram showing another example of application of the TCI state according to aspect 5-1. [Figure 30] FIG. 30 is a diagram illustrating an example of application of the TCI state according to aspect 5-3. [Figure 31] FIG. 31 is a diagram illustrating an example of application of the TCI state according to option 5-5-1. [Figure 32] FIG. 32 is a diagram illustrating an example of application of the TCI state according to option 5-5-2. [Figure 33] FIG. 33 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 34] FIG. 34 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 35] FIG. 35 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 36] FIG. 36 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 37] FIG. 37 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0025] A QCL Type A RS is always configured for PDCCH and PDSCH, and a QCL Type D RS may be configured additionally. Because it is difficult to estimate Doppler shift, delay, etc. by one-shot reception of a DMRS, a QCL Type A RS is used to improve channel estimation accuracy. A QCL Type D RS is used to determine the receiving beam when receiving a DMRS.

[0026] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is indicated as a QCL type C / D RS according to the TCI status of the PDSCH. By indicating the TCI status, the UE can use information obtained from past periodic reception / measurement results of TRS1-1 for reception / channel estimation of the DMRS for PDSCH. In this case, the QCL source of the PDSCH is TRS1-1, and the QCL target is the DMRS for PDSCH.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] In the present disclosure, when N=M=X (X is any integer) is stated, this may mean that X TCI states (joint TCI states) common to UL and DL (corresponding to X TRPs) are notified / configured / instructed to the UE.

[0048] Furthermore, when N=X (X is any integer) and M=Y (Y is any integer, or Y=X) are written, this may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) are notified / configured / instructed to the UE. The UL TCI state and the DL TCI state may mean a TCI state common to UL and DL (i.e., a joint TCI state), or may mean a TCI state for each of UL and DL (i.e., a separate TCI state).

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

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

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

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

[0053] Furthermore, for example, when N=2 and M=1, this may mean that two TCI states common to UL and DL are notified / configured / instructed to the UE. In this case, the UE may use the two configured / instructed TCI states as UL TCI states and one TCI state of the two configured / instructed TCI states as a DL TCI state.

[0054] Also, for example, when N=2 and M=1, this may mean that two UL TCI states and one DL TCI state are notified / configured / instructed to the UE as separate TCI states.

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

[0056] The case where M>1 / N>1 may indicate at least one of TCI status indications for multiple TRPs and multiple TCI status indications for inter-band CA.

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

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

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

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

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

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

[0063] The existing DCI formats 1_1 / 1_2 may be used to indicate the common TCI status.

[0064] The DCI format indicating the TCI state may be a specific DCI format, for example, DCI format 1_1 / 1_2 (defined in Rel. 15 / 16 / 17).

[0065] The DCI format (DCI format 1_1 / 1_2) indicating the TCI state may be a DCI format without a DL assignment. In the present disclosure, these may be interchangeably read as a DCI format without a DL assignment, a DCI format (DCI format 1_1 / 1_2) that does not schedule a PDSCH, a DCI format (DCI format 1_1 / 1_2) that does not include one or more specific fields, a DCI format (DCI format 1_1 / 1_2) in which one or more specific fields are set to fixed values, etc.

[0066] For a DCI format without DL assignment (a DCI format that does not include one or more specific fields), the specific fields may be fields other than the TCI field, the DCI format identifier field, the carrier indicator field, the bandwidth fraction (BWP) indicator field, the Time Domain Resource Assignment (TDRA) field, the Downlink Assignment Index (DAI) field (if configured), the Transmission Power Control (TPC) command field (for the scheduled PUCCH), the PUCCH resource indicator field, and the PDSCH-to-HARQ feedback timing indicator field (if present). The specific fields may be set as reserved fields or ignored.

[0067] For DCI formats without DL assignment (DCI formats in which one or more specific fields are set to fixed values), the specific fields may be a Redundancy Version (RV) field, a Modulation and Coding Scheme (MCS) field, a New Data Indicator field, and a Frequency Domain Resource Assignment (FDRA) field.

[0068] The RV field may be set to all ones. The MCS field may be set to all ones. The NDI field may be set to zero. The FDRA field of type 0 may be set to all zeros. The FDRA field of type 1 may be set to all ones. The FDRA field for a dynamic switch (upper layer parameter dynamicSwitch) may be set to all zeros.

[0069] The common TCI framework may have separate TCI states for DL ​​and UL.

[0070] (MAC CE) In Rel. 16, MAC CE (TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) is used for UE-specific TCI state activation / deactivation (see FIG. 2).

[0071] The MAC CE is identified by a MAC subheader that has a Logical Channel ID (LCID).

[0072] The MAC CE may be used in an environment using a single TRP or multiple TRPs based on multiple DCIs.

[0073] The MAC CE may include a Serving Cell ID field, a BWP ID field, a field (Ti) for indicating activation / deactivation of the TCI state, and a CORESET Pool ID field.

[0074] The Serving Cell ID field may be a field for indicating a serving cell to which the MAC CE applies. The BWP ID field may be a field for indicating a DL BWP to which the MAC CE applies. The CORESET Pool ID field may be a field for indicating that the correspondence (mapping) between the activated TCI state and the code point of the TCI field indicated by the DCI set in the field Ti (the code point of the DCI TCI) is specific to the ControlResourceSetId set by the CORESET Pool ID.

[0075] In addition, in Rel. 16, MAC CE (Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE) is used for activating / deactivating the TCI states of a UE-specific PDSCH (see FIG. 3).

[0076] The MAC CE is identified in the MAC PDU subheader with the eLCID.

[0077] The MAC CE may be used in an environment using multiple TRPs based on a single DCI.

[0078] The MAC CE may include a Serving Cell ID field, a BWP ID field, a field for indicating the TCI state identified by TCI-StateID (TCI state IDi,j (i is an integer from 0 to N, j is 1 or 2)), a field (Ci) indicating whether TCI state IDi,2 is present in the corresponding octet, and a Reserved Bit field (R, set to 0).

[0079] "i" may correspond to the index of the codepoint of the TCI field indicated by the DCI. "TCI state IDi,j" may indicate the j-th TCI state of the codepoint of the i-th TCI field.

[0080] Furthermore, in Rel. 16, MAC CE (TCI State Indication for UE-specific PDCCH MAC CE) is used for activation / deactivation of the TCI state of UE-specific PDCCH / CORESET (see FIG. 4).

[0081] The MAC CE is identified by a MAC subheader with an LCID.

[0082] The MAC CE may include a Serving Cell ID field, a field indicating the CORESET (CORESET ID) for which the TCI state is to be indicated, and a field (TCI state ID) for indicating the TCI state applicable to the CORESET identified by the CORESET ID.

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

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

[0085] The ACK may be an ACK for a PDSCH scheduled by a beam instruction DCI. The PDSCH may not be scheduled by a beam instruction DCI. In this case, the ACK may be an ACK for the beam instruction DCI.

[0086] For DCI-based beam direction in Rel. 17, it is being considered that at least one Y symbol per BWP / CC will be configured in the UE.

[0087] If the SCS differs between multiple CCs, the value of the Y symbol also differs, and therefore the application time may differ between multiple CCs.

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

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

[0090] The application time (Y symbols) of beam direction for CA may be determined on the carrier with the smallest SCS among the carriers to which beam direction applies. Rel.17 MAC CE based beam direction (when only a single TCI codepoint is activated) may follow the Rel.16 application timeline for MAC CE activation.

[0091] Based on these considerations, the following behaviors are being considered for inclusion in the specifications: [Operation] When a UE transmits the last symbol of a PUCCH with HARQ-ACK information corresponding to a DCI carrying a TCI state indication, the indicated TCI state with the Rel.17 TCI state may start to apply from the first slot that is at least Y symbols after the last symbol of the PUCCH. Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbols]). Both the first slot and Y symbols may be determined on the carrier with the smallest SCS among the carriers to which the beam indication applies. At a given time, the UE may assume one indicated TCI state with the Rel.17 TCI state for both DL and UL, or one indicated TCI state with the Rel.17 TCI state for UL (separate from DL).

[0092] X[ms] may be used instead of Y[symbols].

[0093] For application time, it is considered that the UE reports at least one of the following UE capabilities 1 and 2: [UE ability 1] Minimum application time per SCS (minimum of Y symbols between the last symbol of the PUCCH carrying the ACK and the first slot in which the beam is applied). [UE ability 2] Minimum time gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied. The gap between the last symbol of the beam indication PDCCH (DCI) and the first slot in which the beam is applied may meet the UE capabilities (minimum time gap).

[0094] UE capability 2 may be an existing UE capability (eg, timeDurationForQCL).

[0095] The relationship between the beam indication and the channel / RS to which the beam is applied may satisfy at least one of UE capabilities 1 and 2.

[0096] (Application of Artificial Intelligence (AI) technology to wireless communications) Regarding future wireless communication technologies, the use of AI technologies such as machine learning (ML) for network / device control and management is being considered.

[0097] For example, for future wireless communication technologies, it is being considered to use beam quality predicted using AI / ML for future beam direction. AI / ML can make beam quality prediction possible.

[0098] It is considered that the BAT from the HARQ-ACK related to the beam instruction is set / (pre-)defined to at least one value for the TCI state defined in Rel. 17 or later.

[0099] In Rel. 17, it is being considered that beam pattern instructions (TCI status series) will not be supported.

[0100] (analysis) As mentioned above, in Rel. 17 and later, it is being considered that one or more TCI states (common TCI states) will be indicated to a UE using a TCI state field (TCI field, maximum 3 bits) included in a DCI format (e.g., DCI format 1_1 / 1_2 without / with DL assignment).

[0101] 5A is a diagram illustrating an example of a joint TCI state indication. As illustrated in FIG. 5A, in the joint TCI state indication, one joint TCI state (DL / UL joint TCI state) may correspond to one code point of a TCI field. The UE may determine the TCI states (DL / UL joint TCI states) to apply to the DL channel / signal and the UL channel / signal based on the indicated code points of the TCI field.

[0102] 5B is a diagram illustrating an example of a separate TCI state indication. As illustrated in FIG. 5B, in the separate TCI state indication, one or two TCI states correspond to a code point in one TCI field. The two TCI states may be a DL (separate) TCI state and a UL (separate) TCI state, respectively. The UE determines the TCI state to apply to the DL channel / signal and the TCI state to apply to the UL channel / signal based on the indicated code point in the TCI field. When the UE is notified of a code point in the TCI field corresponding to only one TCI state (e.g., code point "000" in FIG. 10B), the UE may continue / indicate the UL TCI state that is applied until the indication for the non-indicated TCI state (e.g., the UL TCI state in the case of code point "000" in FIG. 5B).

[0103] Furthermore, in Rel. 17 and later, a timeline from the instruction of a TCI state (which may be referred to as a "beam instruction") to the application of the instructed TCI state has been considered. The timing from the reception of a beam instruction to the application of a TCI state (which may be referred to as beam application timing (BAT)) may be the timing from the transmission of a HARQ-ACK for a PDSCH scheduled by a DCI instructing the TCI state until a specific time (e.g., K symbols) has elapsed (see FIG. 6). The timing may be at least the first slot after the specific time (e.g., K symbols). In the present disclosure, BAT, beam application start timing, K symbols, Y symbols, X [ms], time offset, and timing offset may be interchangeable.

[0104] The K may be determined based on higher layer signaling (RRC parameters) based on capability information (UE Capability Information, for example, "timeDurationForQCL-rel18") reported by the UE. Note that the BAT for a specific subcarrier spacing may be set for multiple (e.g., all) CCs / BWPs to which a common TCI state ID of a common TCI state in carrier aggregation (CA) is set.

[0105] However, there are cases where the application of the unified TCI state has not been sufficiently considered. For example, there has been insufficient consideration of the dynamic instruction of the timeline (e.g., the above-mentioned BAT) from the instruction of the beam (TCI state) to its application. Also, for example, there has been insufficient consideration of the instruction of the beam pattern for the unified TCI state. If such consideration is insufficient, there is a risk of deterioration in communication quality, reduction in throughput, etc.

[0106] Therefore, the present inventors have devised a method for appropriately setting / indicating / applying the TCI state. Note that each embodiment of the present disclosure may be applied when AI / prediction is not used.

[0107] In one embodiment of the present disclosure, a terminal (user equipment (UE)) / base station (BS) trains an ML model in a training mode and executes the ML model in a test mode (also referred to as a test mode, etc.). In the test mode, the accuracy of the ML model trained in the training mode may be validated.

[0108] In the present disclosure, the UE / BS may input channel state information, reference signal measurements, etc. to the ML model and output highly accurate channel state information / measurements / beam selection / position, future channel state information / radio link quality, etc.

[0109] In this disclosure, AI may be interpreted as an object (also referred to as a subject, object, data, function, program, etc.) that has (performs) at least one of the following characteristics: · inferences based on observed or collected information; · making choices based on information observed or collected; · Predictions based on observed or collected information.

[0110] In the present disclosure, the object may be, for example, an apparatus, a device, etc., such as a terminal or a base station. The object may also correspond to a program included in the apparatus.

[0111] In addition, in the present disclosure, an ML model may be interpreted as an object having (implementing) at least one of the following characteristics: - Producing estimates by feeding information, · Predicting estimates by giving information, · Discover features by providing information, · Selecting behavior by providing information.

[0112] In the present disclosure, the term "ML model" may be read as at least one of a model, an AI model, predictive analytics, a predictive analysis model, etc. The term "ML model" may be derived using at least one of regression analysis (e.g., linear regression analysis, multiple regression analysis, logistic regression analysis), a support vector machine, a random forest, a neural network, deep learning, etc. In the present disclosure, the term "model" may be read as at least one of an encoder, a decoder, a tool, etc.

[0113] Based on input information, the ML model outputs at least one piece of information, such as an estimate, a prediction, a selected action, or a classification.

[0114] ML models may include supervised learning, unsupervised learning, and reinforcement learning. Supervised learning may be used to learn general rules that map inputs to outputs. Unsupervised learning may be used to learn features of data. Reinforcement learning may be used to learn behaviors to maximize a goal.

[0115] Each embodiment described below will be mainly described assuming that supervised learning is used for the ML model, but is not limited to this.

[0116] In this disclosure, terms such as implementing, operating, operating, and executing may be interchangeable. Also, in this disclosure, terms such as testing, after-training, live use, and actual use may be interchangeable. Signal may be interchangeable with signal / channel.

[0117] In this disclosure, the training mode may refer to a mode in which the UE / BS transmits / receives signals for an ML model (i.e., a mode of operation during training). In this disclosure, the test mode may refer to a mode in which the UE / BS implements an ML model (e.g., implements a trained ML model to predict outputs) (i.e., a mode of operation during testing).

[0118] In the present disclosure, the training mode may refer to a mode in which a particular signal transmitted in the test mode is transmitted with a large overhead (e.g., a large amount of resources).

[0119] In the present disclosure, a training mode may refer to a mode that refers to a first configuration (e.g., a first DMRS configuration or a first CSI-RS configuration). In the present disclosure, a test mode may refer to a mode that refers to a second configuration (e.g., a second DMRS configuration or a second CSI-RS configuration) that is different from the first configuration. The first configuration may be configured with at least one of more time resources, frequency resources, code resources, and ports (antenna ports) related to measurements than the second configuration.

[0120] In this disclosure, estimation, prediction, and inference may be used interchangeably. Also, in this disclosure, estimate, predict, and infer may be used interchangeably.

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

[0122] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, sequence, list, set, group, group, cluster, subset, etc. may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0123] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0124] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), RRC messages, and settings may be read interchangeably.

[0125] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. In the present disclosure, the MAC CE, an update command, and an activation / deactivation command may be read interchangeably.

[0126] The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI, SIB1), Other System Information (OSI), etc.

[0127] In this disclosure, the terms beam, spatial-domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial-domain receive filter, UE spatial-domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS for QCL type D in TCI state / QCL assumption, RS for QCL type A in TCI state / QCL assumption, spatial relationship, spatial-domain transmit filter, UE spatial-domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be interchangeable. In this disclosure, the terms QCL type X-RS, DL-RS associated with QCL type X, DL-RS with QCL type X, source of DL-RS, SSB, CSI-RS, and SRS may be interchangeable.

[0128] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, uplink (UL) transmitting entity, transmission / reception point (TRP), base station, spatial relation information (SRI), spatial relation, SRS resource indicator (SRI), control resource set (CONTROLLER RESOLUTION SET (CORESET)), physical downlink shared channel (PDSCH), codeword (CW), transport block (TB), reference signal (Reference Signal (RS)), base station, antenna port of a certain signal (e.g., demodulation reference signal (DMRS) port), DMRS, antenna port group of a certain signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), Physical Uplink Control The terms PUCCH group, PUCCH resource group, resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, CORESET subset, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, redundancy version (RV), and layer (multi-input multi-output (MIMO) layer, transmission layer, spatial layer) may be read as interchangeable.In addition, a panel identifier (ID) and a panel may be interchangeable. In the present disclosure, a TRP ID and a TRP may be interchangeable.

[0129] Furthermore, a panel identifier (ID) and a panel may be interchangeable. That is, a TRP ID and a TRP, a CORESET group ID and a CORESET group, etc. may be interchangeable.

[0130] In the present disclosure, the terms TRP, transmission point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in a TCI field may be read interchangeably.

[0131] Each embodiment of the present disclosure may be used for at least one of transmission and reception using a single TRP based on a single DCI, transmission and reception using multiple TRPs based on a single DCI, and transmission and reception using multiple TRPs based on multiple DCIs.

[0132] In this disclosure, a single PDCCH (DCI) may be assumed to be supported when multiple TRPs utilize an ideal backhaul. Multiple PDCCHs (DCIs) may be assumed to be supported when multiple TRPs utilize a non-ideal backhaul.

[0133] The ideal backhaul may be called DMRS port group type 1, reference signal associated group type 1, antenna port group type 1, CORESET pool type 1, etc. The non-ideal backhaul may be called DMRS port group type 2, reference signal associated group type 2, antenna port group type 2, CORESET pool type 2, etc. The names are not limited to these.

[0134] In this disclosure, the terms "single TRP," "single TRP system," "single TRP transmission," and "single PDSCH" may be interchangeable. In this disclosure, the terms "multiple TRPs," "multiple TRP system," "multiple TRP transmission," and "multiple PDSCH" may be interchangeable. In this disclosure, the terms "single DCI," "single PDCCH," "multiple TRPs based on a single DCI," and "activating two TCI states on at least one TCI codepoint" may be interchangeable.

[0135] In the present disclosure, single TRP, channel using single TRP, channel using one TCI state / spatial relationship, no multi-TRP enabled by RRC / DCI, no multiple TCI states / spatial relationships enabled by RRC / DCI, no CORESETPoolIndex value of 1 set for any CORESET, and no codepoint in the TCI field mapped to two TCI states may be read interchangeably.

[0136] In the present disclosure, "multi-TRP," "channel using multi-TRP," "channel using multiple TCI states / spatial relationships," "multi-TRP being enabled by RRC / DCI," "multiple TCI states / spatial relationships being enabled by RRC / DCI," and "at least one of multi-TRP based on a single DCI" and "multi-TRP based on multiple DCI" may be interchangeable. In the present disclosure, "multi-TRP based on multiple DCI," and "setting a CORESET pool index (CORESETPoolIndex) value of 1 for the CORESET" may be interchangeable. In the present disclosure, "multi-TRP based on a single DCI," and "at least one code point in the TCI field is mapped to two TCI states" may be interchangeable.

[0137] In the present disclosure, TRP#1 (first TRP) may correspond to CORESET pool index = 0 or may correspond to the first of two TCI states corresponding to one code point in the TCI field. TRP#2 (second TRP) TRP#1 (first TRP) may correspond to CORESET pool index = 1 or may correspond to the second of two TCI states corresponding to one code point in the TCI field.

[0138] In the present disclosure, single DCI (sDCI), single PDCCH, multi-TRP system based on single DCI, sDCI-based MTRP, and activation of two TCI states on at least one TCI codepoint may be read interchangeably.

[0139] In the present disclosure, multi-DCI (mDCI), multi-PDCCH, multi-TRP system based on multi-DCI, mDCI-based MTRP, and setting two CORESET pool indices or CORESET pool index=1 (or a value greater than or equal to 1) may be read interchangeably.

[0140] The QCL of the present disclosure may be interchangeably read as QCL Type D.

[0141] In the present disclosure, expressions such as "TCI state A is QCL type D, which is the same as TCI state B," "TCI state A is the same as TCI state B," and "TCI state A is QCL type D with TCI state B" may be read interchangeably.

[0142] In the present disclosure, the code point of the DCI field 'Transmission Configuration Indication', the TCI code point, the DCI code point, and the code point of the TCI field may be read interchangeably.

[0143] In this disclosure, the terms single TRP and single frequency network (SFN) may be interchangeable. In this disclosure, the terms high speed train (HST), HST scheme, high speed movement scheme, scheme 1, scheme 2, NW pre-compensation scheme, HST scheme 1, HST scheme 2, and HST NW pre-compensation scheme may be interchangeable.

[0144] In the present disclosure, a PDSCH / PDCCH using a single TRP may be interpreted as a PDSCH / PDCCH based on a single TRP, a single TRP PDSCH / PDCCH, etc. Also, in the present disclosure, a PDSCH / PDCCH using SFN may be interpreted as a PDSCH / PDCCH using SFN in multi-hop transmission, a PDSCH / PDCCH based on SFN, or an SFN PDSCH / PDCCH.

[0145] In the present disclosure, receiving DL signals (PDSCH / PDCCH) using SFN may mean receiving the same data (PDSCH) / control information (PDCCH) from multiple transmission / reception points using the same time / frequency resources, and / or receiving DL signals using SFN may mean receiving the same data / control information using the same time / frequency resources and / or multiple TCI states / space-domain filters / beams / QCLs.

[0146] In the present disclosure, at least one of HST-SFN scheme, SFN scheme after Rel. 17, new SFN scheme, new HST-SFN scheme, HST-SFN scenario after Rel. 17, HST-SFN scheme for HST-SFN scenario, SFN scheme for HST-SFN scenario, scheme 1, HST-SFN scheme A / B, HST-SFN type A / B, Doppler pre-compensation scheme, scheme 1 (HST scheme 1), and Doppler pre-compensation scheme may be read interchangeably.

[0147] In the present disclosure, the terms Doppler pre-compensation scheme, base station pre-compensation scheme, TRP pre-compensation scheme, pre-Doppler compensation scheme, Doppler pre-compensation scheme, NW pre-compensation scheme, HST NW pre-compensation scheme, TRP pre-compensation scheme, TRP-based pre-compensation scheme, HST-SFN scheme A / B, and HST-SFN type A / B may be interchangeable. In the present disclosure, the terms pre-compensation scheme, reduction scheme, improvement scheme, and correction scheme may be interchangeable.

[0148] In the present disclosure, a PDCCH / search space (SS) / CORESET with linkage, a linked PDCCH / SS / CORESET, and a PDCCH / SS / CORESET pair may be interchangeable. In the present disclosure, a PDCCH / SS / CORESET without linkage, an unlinked PDCCH / SS / CORESET, and a single PDCCH / SS / CORESET may be interchangeable.

[0149] In the present disclosure, two linked CORESETs for PDCCH repetition, and two CORESETs respectively associated with two linked SS sets may be read interchangeably.

[0150] In the present disclosure, SFN-PDCCH repetition, PDCCH repetition, two linked PDCCHs, and one DCI being received across the two linked search spaces (SS) / CORESETs may be read interchangeably.

[0151] In the present disclosure, PDCCH repetition, SFN-PDCCH repetition, PDCCH repetition for higher reliability, PDCCH for higher reliability, PDCCH for reliability, and two linked PDCCHs may be read interchangeably.

[0152] In the present disclosure, the terms PDCCH reception method, PDCCH repetition, SFN-PDCCH repetition, HST-SFN, and HST-SFN scheme may be read interchangeably.

[0153] In the present disclosure, the PDSCH reception method, the single DCI-based multi-TRP, and the HST-SFN scheme may be read interchangeably.

[0154] In the present disclosure, the single DCI-based multi-TRP repetition may be an NCJT for an enhanced mobile broadband (eMBB) service (low priority, priority 0) or a repetition of a URLLC service (high priority, priority 1) for an ultra-reliable and low latency communications service.

[0155] In each embodiment of the present disclosure, a PDSCH for multiple TRPs based on a single DCI may be interchangeably read as a PDSCH to which TDM / FDM / SDM for multiple TRPs (defined in Rel. 16) is applied.

[0156] In each embodiment of the present disclosure, a PDSCH for multiple TRPs may be interchangeably read as a PDSCH to which TDM / FDM / SDM for multiple TRPs based on a single DCI (defined in Rel. 16) is applied.

[0157] In each embodiment of the present disclosure, PUSCH / PUCCH / PDCCH for multiple TRPs based on a single DCI may be interchangeably read as repeated transmission (repetition) of PUSCH / PUCCH / PDCCH for multiple TRPs (defined in Rel. 17 and later).

[0158] In each embodiment of the present disclosure, the SFN PDSCH / PDCCH may be interchangeably read as the SFN PDSCH / PDCCH defined in Rel. 17 and later.

[0159] In each embodiment of the present disclosure, configuring the use of multiple TRPs based on multiple DCIs may mean configuring a CORESET pool index of 1. Also, configuring the use of multiple TRPs based on multiple DCIs may mean configuring a CORESET pool index of two different values ​​(e.g., 0 and 1).

[0160] In each embodiment of the present disclosure, UL transmission using multiple panels may refer to a UL transmission scheme using multiple panels of a UE with DCI enhancement.

[0161] In each embodiment of the present disclosure, if a joint TCI state / separate TCI state in the unified TCI state framework is not applicable to each channel / signal, the aforementioned default TCI state / QCL / spatial relationship may be used to determine the TCI state / QCL / spatial relationship of each channel.

[0162] The following embodiments of the present disclosure may be applied to transmission and reception of any channel / signal to which the unified TCI state framework defined in the above-mentioned Rel. 17 and later is applicable.

[0163] In the present disclosure, applying a TCI state to each channel / signal / resource may mean applying a TCI state to transmission and reception of each channel / signal / resource.

[0164] In the present disclosure, small, few, short, and low may be read as interchangeable. Also, in the present disclosure, ignore, drop, etc. may be read as interchangeable.

[0165] In the present disclosure, "highest (maximum)" and "lowest (minimum)" may be interpreted interchangeably. Also, in the present disclosure, "maximum" may be interpreted interchangeably as "nth (n is any natural number)" largest, larger, higher, etc. Also, in the present disclosure, "minimum" may be interpreted interchangeably as "nth (n is any natural number) smallest," smaller, lower, etc.

[0166] In the present disclosure, repetition, repeated transmission, and repeated reception may be read interchangeably.

[0167] In the present disclosure, the terms channel, signal, and channel / signal may be interchangeable. In the present disclosure, the terms DL channel, DL signal, DL signal / channel, transmission / reception of DL signal / channel, DL reception, and DL transmission may be interchangeable. In the present disclosure, the terms UL channel, UL signal, UL signal / channel, transmission / reception of UL signal / channel, UL reception, and UL transmission may be interchangeable.

[0168] In the present disclosure, a first TRP may correspond to a first TCI state. In the present disclosure, a second TRP may correspond to a second TCI state. In the present disclosure, an nth TRP may correspond to an nth TCI state.

[0169] In the present disclosure, a first CORESET pool index value (e.g., 0), a first TRP index value (e.g., 1), and a first TCI state (first DL / UL (joint / separate) TCI state) may correspond to each other. In the present disclosure, a second CORESET pool index value (e.g., 1), a second TRP index value (e.g., 2), and a second TCI state (second DL / UL (joint / separate) TCI state) may correspond to each other.

[0170] In the present disclosure, timing, time, duration, time instance, slot, subslot, symbol, subframe, etc. may be read interchangeably.

[0171] (Wireless communication method) Each embodiment / aspect / option / alternative / variation of the present disclosure may be used under at least one of the following conditions: · (Explicitly) set the corresponding upper layer parameters. (Implicitly) setting related higher layer parameters. · MAC CE / DCI (fields included in) indication. · (Reported) UE Capability. -As specified in the specifications. · Specific conditions set out in the specifications. · Configuration / indication by at least one of higher layer parameters, MAC CE, DCI and (reported) UE capabilities.

[0172] Each embodiment / aspect / option / alternative / variation of the present disclosure may be used alone or in combination.

[0173] First Embodiment The first embodiment relates to the indication of the BAT.

[0174] The UE may refer to an RS with an indicated TCI state as an RS configured with a particular QCL type (e.g., QCL type D) for a particular signal (if applicable). The UE may apply the TCI state to transmitting and receiving one or more channels / signals.

[0175] The specific signal may be, for example, at least one of a DMRS for PDSCH, a DMRS for PDCCH, and a CSI-RS.

[0176] The UE may determine to apply the TCI state indicated using the beam indication (DCI) from a specific time resource (e.g., a specific symbol / slot) at the first symbol / slot after the BAT has elapsed.

[0177] The particular time resource may be at least one of the following options 1-0-1 to 1-0-3.

[0178] The specific time resource may be at least one of the first / last symbol of a PUCCH with HARQ-ACK scheduled by a DCI (beam indication DCI) including an indication of the TCI state, and a slot (e.g., the first / last slot) of the PUCCH (option 1-0-1).

[0179] In the present disclosure, a HARQ-ACK scheduled by a certain DCI may be interchangeably read as a HARQ-ACK related to a certain DCI. Also, in the present disclosure, a DCI of a beam instruction may be in a DCI format with a DL assignment or a DCI format without a DL assignment.

[0180] The specific time resource may be at least one of the first / last symbol of the PDCCH of the DCI (beam indication DCI) containing an indication of the TCI state and the slot (e.g., the first / last slot) of the PDCCH (option 1-0-2).

[0181] The specific time resource may be a designated symbol / slot / subframe (option 1-0-3), which may be represented by at least one of a symbol (index) within a slot, a slot index within a subframe, and a subframe index.

[0182] The time resources in at least one of the above options 1-0-1 to 1-0-3 may be specified in advance, may be set / instructed to the UE using higher layer signaling (RRC / MAC CE) / DCI (beam indication DCI / DCI other than beam indication DCI), or may be determined based on UE capability information reported by the UE.

[0183] 7 is a diagram illustrating an example of a criterion for starting a BAT according to the first embodiment. In the example illustrated in FIG. 7, a UE receives a beam instruction DCI. According to the above option 1-0-1, a specific period from the transmission of a HARQ-ACK related to the DCI becomes the BAT. According to the above option 1-0-2, a specific period from the reception of the DCI becomes the BAT.

[0184] According to the above options 1-0-1 to 1-0-3, the time resource that marks the start of the BAT period can be appropriately determined.

[0185] The following explains BAT.

[0186] The UE may decide to apply the beam indication (TCI state) after a certain period of time has elapsed from the time resources described in at least one of options 1-0-1 to 1-0-3 above.

[0187] The specific period may be expressed in terms of a specific (for example, X (X is an arbitrary integer)) number of symbols / slots / subframes, or Y [ms] (Y is an arbitrary number).

[0188] The specific period may be determined according to at least one of the following options 1-1-1 to 1-1-7.

[0189] 《Option 1-1-1》 The specific period may be a value that is predefined in the specifications.

[0190] The value may be determined based on, for example, reported UE capability information and configured higher layer parameters (RRC parameters / MAC CE field).

[0191] For example, the RRC parameter may be an RRC parameter indicating whether beam indication for multiple beam application times (BATs) is enabled / disabled.

[0192] The value may be determined for each specific number (for example, N (N is an integer greater than 0)) of TCI code points in the TCI field included in the DCI.

[0193] N may be specified in advance in a specification, may be set / instructed to the UE using higher layer signaling (RRC / MAC CE) / DCI (beam instruction DCI / DCI other than beam instruction DCI), or may be determined based on UE capability information reported by the UE.

[0194] The value may be determined for each TCI state / source RS in a specific QCL (QCL information), which may be a QCL corresponding to a specific number (e.g., N) of TCI codepoints in the TCI field included in the DCI.

[0195] 8A and 8B are diagrams illustrating an example of application of the TCI state according to Option 1-1-1. As shown in Fig. 8A, an association between a TCI codepoint and a BAT (a TCI state (joint DL / UL TCI state in the example of Fig. 8A)) is established for a UE.

[0196] Note that the association between TCI code points and TCI states described in each embodiment of the present disclosure is merely an example, and the number of bits of the code points and the indicated TCI states are not limited to the examples shown. Furthermore, although the TCI states described in the association will be mainly described using a joint DL / UL TCI state as an example, the TCI state included in the association may also be a separate DL / UL TCI state.

[0197] In the example shown in Fig. 8B, when the TCI code point "000" is instructed to the UE using the beam instruction DCI, the UE determines that the BAT is BAT #1. Also, when the TCI code point "100" is instructed to the UE using the beam instruction DCI, the UE determines that the BAT is BAT #2.

[0198] 《Option 1-1-2》 The particular period may be determined / set based on particular RRC parameters.

[0199] The particular RRC parameter may be an RRC parameter that is not related to (independent of) a codepoint in the DCI (for example, a TCI codepoint).

[0200] The particular RRC parameter may be an RRC parameter related to the application time of the beam (TCI state) (e.g., "BeamAppTime").

[0201] 《Option 1-1-3》 The particular period may be determined / set based on particular RRC parameters.

[0202] For example, the specific RRC parameter may be an RRC parameter that sets the specific period for each of a specific number (for example, N (N is an integer greater than 0)) of TCI code points in the TCI field included in the DCI.

[0203] 9A and 9B are diagrams illustrating an example of application of the TCI state according to Option 1-1-3. As shown in Fig. 9A, an association between a TCI codepoint and a BAT (a TCI state (joint DL / UL TCI state in the example of Fig. 9A)) is established for a UE.

[0204] In the example shown in FIG. 9A, a BAT is configured for every two (N=2) TCI code points. That is, four BATs are configured for a UE by RRC parameters. This configuration may be performed in the configuration of specific RRC parameters. In the example shown in FIG. 9B, a parameter (beamApptimeperTCIlist) related to a beam application time for each TCI state (TCI list) is included in a PDSCH configuration (PDSCH-Config). The parameter (beamApptimeperTCIlist) related to the beam application time includes an ID (beamApptimeId) of the beam application time for the maximum number of code points (maxNrofcodepointsinTCI-StateField) in the corresponding TCI field. The ID (beamApptimeId) of the beam application time may be a parameter for identifying an RRC parameter (e.g., "beamApptime") related to the application time of a beam (TCI state).

[0205] In the present disclosure, the indication of the BAT may be indicated by an index (number) of the BAT or an index related to the BAT. The association between the index related to the BAT and the value of the BAT may be set by higher layer signaling (RRC / MAC CE) or may be predefined in a specification.

[0206] The maximum number of codepoints in a TCI field (maxNrofcodepointsinTCI-StateField) may be a specific number. For example, if N is 1, the maximum number of codepoints in the corresponding TCI field (maxNrofcodepointsinTCI-StateField) may be a first value (e.g., 8). For example, if N is 2, the maximum number of codepoints in the corresponding TCI field (maxNrofcodepointsinTCI-StateField) may be a second value (e.g., 4).

[0207] 《Option 1-1-4》 The particular period may be determined / set based on particular RRC parameters.

[0208] For example, the specific RRC parameter may be a setting parameter of a TCI state ("TCI-State"), which may include an RRC parameter (e.g., "beamApptime") related to the application time of a beam (TCI state).

[0209] Fig. 10 is a diagram showing an example of application of the TCI state according to option 1-1-4. In the example shown in Fig. 10, the setting parameter of the TCI state ("TCI-State") includes an RRC parameter (e.g., "beamApptime") related to the application time of the beam (TCI state). The RRC parameter (e.g., "beamApptime") related to the application time of the beam (TCI state) may indicate one value from among multiple values ​​(n1, n2, n4, n8, or n16 in the example of Fig. 10). Note that the multiple values ​​shown in the diagram are merely examples and are not limited to these.

[0210] [Option 1-1-4 Variation 1] For example, the specific RRC parameter may be a QCL information parameter ("QCL-Info") included in a TCI state setting parameter ("TCI-State"), and the QCL information parameter ("QCL-Info") may include an RRC parameter (e.g., "beamApptime") related to the application time of the beam (TCI state).

[0211] The parameter of the QCL information ("QCL-Info") may be indicated by at least one of a parameter indicating the first QCL type ("qcl-Type1") and a parameter indicating the second QCL type ("qcl-Type2").

[0212] Fig. 11 is a diagram showing an example of application of a TCI state according to Variation 1 of Option 1-1-4. In the example shown in Fig. 11, a setting parameter for the TCI state ("TCI-State") includes a parameter for QCL information ("QCL-Info"), and the parameter for QCL information ("QCL-Info") includes an RRC parameter (e.g., "beamApptime") related to the application time of a beam (TCI state). The RRC parameter (e.g., "beamApptime") related to the application time of a beam (TCI state) may indicate one value from among multiple values ​​(n1, n2, n4, n8, or n16 in the example of Fig. 11). Note that the multiple values ​​shown in the diagram are merely examples and are not limited to these.

[0213] According to this modification, it becomes possible to set independent (different) BATs depending on different QCL types (for example, QCL types A / B / C / D), allowing flexible setting of the BAT.

[0214] [Option 1-1-4 Variation 2] In at least one of the above Option 1-1-4 and the above Modification 1, the UE may be configured / notified with information regarding the correspondence (mapping) between the TCI state ID and the BAT ID.

[0215] The BAT ID may be a parameter for specifying the value of the BAT. The correspondence between the BAT ID and the BAT value may be specified in advance in a specification, may be configured / instructed to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be determined based on the UE capability information to be reported.

[0216] The information on the correspondence (mapping) between the TCI state ID and the ID of the BAT may be information that associates the TCI state ID with the ID of the BAT, and the information may be notified to the UE using higher layer signaling (RRC / MAC CE).

[0217] Fig. 12 is a diagram showing an example of application of a TCI state according to Variation 2 of Option 1-1-4. In the example shown in Fig. 12, associations relating to N TCI state IDs and associations relating to M BATs are described. Information relating to each association and the correspondence (mapping) between the TCI state ID and the ID of the BAT is configured for the UE. At this time, the UE determines the BAT relating to application of the TCI state based on these correspondences and the specified TCI state (ID).

[0218] According to this modification, it is not necessary to specify the BAT related to the TCI state each time, and the candidate values ​​for the BAT value for each TCI state ID can be limited, thereby reducing overhead.

[0219] 《Option 1-1-5》 The particular period may be determined / set / indicated based on a parameter / field indicated in the MAC CE.

[0220] The MAC CE may be, for example, a MAC CE of at least one of the following options 1-1-5-1 and 1-1-5-2.

[0221] [Option 1-1-5-1] The MAC CE may be a new MAC CE (defined in Rel. 17 and later).

[0222] A new Logical Channel ID (LCID) may be included in the subheader of the MAC CE.

[0223] The MAC CE may include a field indicating the activation of the TCI state.

[0224] FIG. 13 is a diagram showing an example of the configuration of a MAC CE according to option 1-1-5-1. The MAC CE shown in FIG. 13 includes a field indicating a CORESET pool ID, a field indicating a serving cell ID, a field indicating a BWP ID, and a field indicating activation / deactivation of TCI state i (T i (described as "incomplete information").

[0225] The MAC CE shown in Figure 13 further includes a field indicating the BAT corresponding to each activated TCI codepoint. The UE determines the BAT corresponding to the indicated TCI state based on the field indicating the BAT.

[0226] [Option 1-1-5-2] The MAC CE may be an existing MAC CE (for example, one defined by Rel. 15 / 16).

[0227] For this MAC CE, a reserved bit included in an existing MAC CE (e.g., defined up to Rel. 15 / 16) may be used as a field indicating whether to interpret the MAC CE as having a field for activating a list of TCI states with a BAT (time offset).

[0228] The MAC CE may be a MAC CE in which a new field / octet is added to an existing MAC CE (for example, defined up to Rel. 15 / 16).

[0229] The existing MAC CE (for example, defined by Rel. 15 / 16) may be, for example, a MAC CE for UE-specific PDSCH TCI state activation / deactivation (Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE).

[0230] Fig. 14 is a diagram showing an example of the configuration of MAC CE according to option 1-1-5-2. The MAC CE shown in Fig. 14 includes a Serving Cell ID field, a BWP ID field, a field for indicating the TCI state identified by TCI-StateID (TCI state IDi,j (i is an integer from 0 to N, j is 1 or 2)), and a field indicating whether or not TCI state IDi,2 exists in the corresponding octet (C i ), and a reserved bit field (R, set to 0).

[0231] "i" may correspond to the index of the codepoint of the TCI field indicated by the DCI. "TCI state IDi,j" may indicate the j-th TCI state of the codepoint of the i-th TCI field.

[0232] The MAC CE shown in FIG. 14 further includes a field (D i ) and a field (E i (described as "and"), and

[0233] Above D i When the field indicates a first value (for example, 0 (or 1)), the UE may determine that the field indicating the BAT corresponding to the TCI state IDi,1 is included. i When the field indicates a second value (eg, 1 (or 0)), the UE may determine that a field indicating a BAT corresponding to TCI state IDi,1 is not included.

[0234] Above E iWhen the field indicates a first value (for example, 0 (or 1)), the UE may determine that the field indicating the BAT corresponding to the TCI state IDi,2 is included. i When the field indicates a second value (eg, 1 (or 0)), the UE may determine that a field indicating a BAT corresponding to TCI state IDi,2 is not included.

[0235] In the example shown in FIG. 14, the UE determines the BAT corresponding to the indicated TCI state based on the field indicating the BAT.

[0236] 《Option 1-1-6》 The particular period may be determined / indicated based on a particular field included in the DCI.

[0237] For that DCI, you may follow at least one of options 1-1-6-1 through 1-1-6-4 below.

[0238] [Option 1-1-6-1] The DCI may be an existing DCI (format A_B (A and B are any positive numbers)).

[0239] For the DCI, the cyclic redundancy check (CRC) of the DCI may be scrambled by an existing radio network temporary identifier (RNTI).

[0240] The DCI may include a new DCI field, which may indicate a BAT.

[0241] In addition, for the DCI, under certain conditions, an existing field may be used / interpreted as a field to indicate BAT.

[0242] The specific condition may be, for example, a condition in which specific fields (e.g., at least one of the FDRA field, the TDRA field, the MCS field, the RV field, and the NDI field) are (all) set to a specific value (e.g., 0 (or 1)).

[0243] [Option 1-1-6-2] The DCI may be an existing DCI (format A_B (A and B are any positive numbers)).

[0244] For this DCI, the CRC of the DCI may be scrambled with a new RNTI defined in Rel. 17 and later.

[0245] The DCI may include a new DCI field, which may indicate a BAT.

[0246] In addition, for the DCI, under certain conditions, an existing field may be used / interpreted as a field to indicate BAT.

[0247] The specific condition may be, for example, a condition in which specific fields (e.g., at least one of the FDRA field, the TDRA field, the MCS field, the RV field, and the NDI field) are (all) set to a specific value (e.g., 0 (or 1)).

[0248] [Option 1-1-6-3] The DCI may be a new DCI (format A_B (A and B are any positive numbers)) defined in Rel. 17 or later.

[0249] For this DCI, the CRC attached to the DCI may be scrambled by the existing RNTI.

[0250] [Option 1-1-6-4] The DCI may be a new DCI (format A_B (A and B are any positive numbers)) defined in Rel. 17 or later.

[0251] For this DCI, the CRC attached to the DCI may be scrambled with a new RNTI defined in Rel. 17 and later.

[0252] 《Option 1-1-7》 The UE may apply a combination of at least two of the above options 1-1-1 to 1-1-6.

[0253] For example, if the code point of the TCI field is not mapped to the BAT as shown in the above options 1-1-3 / 1-1-4, the above options 1-1-1 / 1-1-2 may be used.

[0254] According to the above options 1-1-1 to 1-1-7, the length (period) of the BAT can be appropriately determined.

[0255] Also, for example, a BAT common to multiple (e.g., all) TCI codepoints and a differential BAT for some of the multiple TCI codepoints may be configured / instructed to the UE. The UE may determine a BAT based on the differential BAT. This example may follow at least one of Options 1-2-1 and 1-2-2 below.

[0256] Option 1-2-1 The UE may calculate / derive / determine the BAT based on differential values ​​(differential BATs) associated with each of a specific number (e.g., N (N is an integer greater than or equal to 1)) of TCI code points and the common BAT.

[0257] The common BAT may be configured by specific higher layer signaling (RRC parameters), may be predefined in specifications, or may be indicated using MAC CE / DCI. The specific RRC parameters may be, for example, RRC parameters related to the application time of a beam (TCI state) (e.g., "BeamAppTime").

[0258] Option 1-2-2 The UE may calculate / derive / determine the BAT based on the differential values ​​associated with each of a specific number (e.g., N (N is an integer greater than or equal to 1)) of TCI codepoints and the BAT associated with the specific TCI codepoint.

[0259] For example, the UE may calculate / derive / determine the BAT based on a BAT value associated with a particular TCI codepoint and a differential value associated with the other TCI codepoints.

[0260] For example, the BAT corresponding to each TCI codepoint may be calculated / derived / determined from the sum of the BAT value associated with the specific TCI codepoint, the BATs associated with each TCI codepoint, and (a common BAT).

[0261] The particular TCI codepoint may be, for example, the TCI codepoint corresponding to the highest (or lowest) codepoint index among lower (or higher) codepoint indexes associated with different values.

[0262] The value of the differential BAT may be determined based on at least one of the methods (options) described in the first embodiment. In addition, the value of the differential BAT may be a positive or negative value.

[0263] According to Option 1-2-2, it is sufficient to set a difference value with a smaller bit width than in Option 1-2-1, and therefore the overhead required for setting the BAT can be reduced.

[0264] 15A and 15B are diagrams illustrating an example of application of the TCI state according to Option 1-2-1. In the example illustrated in Fig. 15A and 15B, the UE receives a beam instruction DCI and applies the TCI state indicated in the DCI.

[0265] In the example shown in Fig. 15A, a correspondence relationship between a TCI code point, a TCI state (a joint DL / UL TCI state is shown in the example of Fig. 15A, but a separate TCI state may also be used), and a BAT (differential BAT) is configured for the UE. Also, a common BAT is configured / defined for the UE.

[0266] In the example shown in Figure 15B, when 000 / 001 / 010 is specified as the TCI code point to the UE, the UE determines that the common BAT is the BAT. Also, when 011 / 100 is specified as the TCI code point to the UE, the UE determines that the value obtained by adding the common BAT and (the value corresponding to) BAT#1 is the BAT. Also, when 101 / 110 / 111 is specified as the TCI code point to the UE, the UE determines that the value obtained by adding the common BAT and (the value corresponding to) BAT#2 is the BAT.

[0267] Fig. 16 is a diagram showing an example of application of the TCI state according to option 1-2-2. In the example shown in Fig. 16, a UE receives a beam instruction DCI and applies the TCI state instructed by the DCI. Note that the example shown in Fig. 16 shows an example in which the above-mentioned option 1-2-1 is also applied in addition to option 1-2-2.

[0268] In the example shown in Fig. 16, a common BAT is configured / defined for the UE, and a correspondence relationship between TCI codepoints, TCI states, and the BAT is configured for the UE.

[0269] In the example shown in Figure 16, when the largest BAT (corresponding TCI code point) among the BATs in the correspondence is instructed to the UE, the UE determines that the sum of the largest BAT (BAT#1 in the example of Figure 16) and the common BAT is the BAT. Also, when the UE is instructed to the UE that a BAT (corresponding TCI code point) other than the largest BAT is instructed, the UE determines that the sum of the common BAT, the value of the largest BAT (BAT#1), and the BAT other than the largest BAT (BAT#2 in the example of Figure 16) is the BAT.

[0270] According to the above options 1-2-1 and 1-2-2, it is possible to set / instruct the BAT with reduced overhead.

[0271] The following describes the quantization of fields related to the BAT.

[0272] The UE may determine the value of the time offset (BAT) based on the BAT (bit field) with quantized bits. For this example, at least one of options 1-3-1 and 1-3-2 below may be followed.

[0273] Option 1-3-1 The association between the bit field / BAT ID of the BAT and the value of the BAT may be configured in the UE using higher layer signaling (RRC signaling).

[0274] For example, the UE may be configured with (an association including) multiple BAT values ​​using RRC signaling, and then the UE may determine one (or more) BAT values ​​from the multiple BAT values.

[0275] If an association containing only one BAT value is established for a UE using RRC signaling, the UE may not receive quantized bits indicating the BAT value (bit field indicating BAT).

[0276] 17A is a diagram showing an example of association of BAT values ​​according to Option 1-3-1. The UE may determine the BAT based on the indicated quantized bits (bit field indicating the BAT) when the association between the bit field (or BAT ID) and the BAT value is set as shown in FIG. 17A.

[0277] Note that the values ​​and field names in the correspondence relationships shown in FIG. 17A are merely examples and are not limited to these.

[0278] 《Option 1-3-2》 The association between the bit field / BAT ID of the BAT and the value of the BAT may be determined / defined based on a specific rule.

[0279] The particular rules / associations may be, for example, predefined in a specification.

[0280] The UE may receive quantized bits (a bit field indicating the BAT) indicating the BAT value based on the particular rule.

[0281] 17B is a diagram showing an example of association of BAT values ​​according to Option 1-3-2. The association between the bit field (or BAT ID) and the BAT value as shown in FIG. 17B is predefined / determined. The UE may determine the BAT based on the association and the indicated quantized bits (bit field indicating the BAT).

[0282] Note that the values ​​and field names in the correspondence relationships shown in FIG. 17B are merely examples and are not limited to these.

[0283] According to the above options 1-3-1 and 1-3-2, BAT notification can be carried out appropriately.

[0284] <<Modification of the First Embodiment>> For example, at least one option of this embodiment may be applied when no BAT is associated with at least one code point of the TCI field. Note that this modification is also applicable to the second embodiment described below.

[0285] For example, even when the UE performs an operation using multi-panel / multi-TRP / multi-cell, at least one option (for example, option 1-2-1 / 1-2-2) of this embodiment may be applied to determine the BAT.

[0286] For example, a common BAT may be configured for the UE. The common BAT may be configured by specific higher layer signaling (RRC parameters), may be predefined in a specification, or may be indicated using MAC CE / DCI. The specific RRC parameters may be, for example, an RRC parameter (e.g., "BeamAppTime") related to the application time of a beam (TCI state).

[0287] Furthermore, a differential BAT may be set / instructed to the UE according to information related to specific information.

[0288] The specific information may be, for example, at least one of a physical cell ID (PCI), information on a panel to be used, information on whether a single panel or a multi-panel is to be used, and information on a TRP. The information on a TRP may be, for example, at least one of information on a CORESET pool index (RRC parameter "coresetPoolIndex"), information on which TCI state to refer to when multiple (two) TCI states are indicated for a CORESET, and information on which spatial relationship to refer to when multiple (two) spatial relationships are set for each PUCCH resource. By configuring / instructing a differential BAT according to the specific information, the UE may derive / calculate a BAT when the specific information is applied / configured, using a common BAT and the differential BAT.

[0289] According to the first embodiment, the BAT can be determined / set / instructed appropriately.

[0290] <Second embodiment> The second embodiment relates to the mapping between the BAT and the TCI state.

[0291] The UE may refer to multiple RSs indicated by the code points in the TCI field of the beam indication DCI at the first symbol / slot after a specific time resource has elapsed since receiving the beam indication DCI and after a specific period of time has elapsed.

[0292] The UE may apply one or more TCI states indicated by the code point in the TCI field of the beam indication DCI at the first symbol / slot after a specific time resource and a specific period of time has elapsed since receiving the beam indication DCI.

[0293] This embodiment may be applied in combination with at least one of the methods described in the first embodiment above.

[0294] The particular time resource may be in accordance with at least one of options 1-0-1 to 1-0-3 above.

[0295] The specific period may be the BAT / time offset in the first embodiment.

[0296] One TCI state (common TCI state / joint (DL / UL) TCI state / separate (DL / UL) TCI state) may be mapped to one BAT. In other words, if one TCI codepoint indicates multiple TCI states, a BAT may be mapped to each of the TCI states.

[0297] By configuring in this way, it is possible to use one DCI (TCI code point) to indicate beam (TCI state) patterns and BATs across multiple time domains.

[0298] In this disclosure, the application method for two TCI states, the first TCI state and the second TCI state, will be mainly described, but the number of TCI states is not limited to two and may be three or more.

[0299] In addition, in the present disclosure, a beam pattern, a TCI state pattern, a sequence of TCI states, a correspondence relationship between multiple TCI states, and a correspondence relationship between multiple TCI states and a BAT may be interpreted as being interchangeable. In addition, in the present disclosure, a beam pattern may mean a correspondence relationship for indicating multiple TCI states across multiple time domains using one TCI code point.

[0300] 18A and 18B are diagrams illustrating an example of application of TCI states according to the second embodiment. In the example illustrated in Fig. 18A, for a UE, a correspondence relationship between a TCI code point, a TCI state (a first joint DL / UL TCI state and a second joint DL / UL TCI state), and a BAT corresponding to the TCI state is configured / defined.

[0301] In the example shown in Figure 18B, the UE receives a TCI field indicating a code point of 000 using a beam instruction DCI. Based on the TCI field, the UE applies a first TCI state (TCI#0) based on BAT#1 and a second TCI state (TCI#1) based on BAT#2.

[0302] Fig. 19 is a diagram showing another example of application of TCI states according to the second embodiment. As shown in the example of Fig. 19, the correspondence relationship between TCI code points, TCI states, and BATs corresponding to the TCI states configured in the UE may include at least one of a joint DL / UL TCI state and a separate DL / UL TCI state. Of the separate DL / UL TCI states, the DL TCI state and the UL TCI state may indicate the same TCI state or different TCI states. In such an example, at least one of the methods of the first embodiment may be applied.

[0303] The following describes how to set the correspondence between the BAT and the TCI state.

[0304] The UE may apply multiple TCI states (reference to multiple RSs) indicated using one TCI codepoint according to at least one of options 2-1-1 to 2-1-3 described below.

[0305] Option 2-1-1 A TCI state parameter ("TCI-State") may be configured for the UE using RRC, which includes multiple QCL information ("QCL-info") of the same type.

[0306] Fig. 20 is a diagram showing an example of parameters of the TCI state related to Option 2-1-1. In the example shown in Fig. 20, the RRC parameter ("TCI-State") includes a TCI state ID, multiple types of Type 1 QCL information (first Type 1 QCL information "qcl-Type1", second Type 1 QCL information "Secondqcl-Type1", and third Type 1 QCL information "Thirdqcl-Type1"), type 2 QCL information (first Type 2 QCL information "qcl-Type2", second Type 2 QCL information "Secondqcl-Type2", and third Type 2 QCL information "Thirdqcl-Type2"), and parameters ("beamApptime", "SecondbeamApptime", and "ThirdbeamApptime") that set the beam application time corresponding to the QCL information. "beamApptime" corresponds to "qcl-Type1" and "qcl-Type2", "SecondbeamApptime" corresponds to "Secondqcl-Type1" and "Secondqcl-Type2", and "ThirdbeamApptime" corresponds to "Thirdqcl-Type1" and "Thirdqcl-Type2".

[0307] 20 shows an example in which the number of pieces of QCL information is three, but the number is not limited to this example and may be more than 3. Furthermore, the names of each parameter are merely examples and are not limited to these examples.

[0308] In the example shown in Figure 20, for the application of the first TCI state among multiple TCI states indicated using one TCI code point, the UE may determine the timing of application of the indicated TCI state based on a parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information.

[0309] In addition, for the application of the second TCI state among multiple TCI states indicated using one TCI code point, the UE may determine the timing of application of the indicated TCI state based on a parameter ("SecondbeamApptime") that sets the beam application time corresponding to the second Type 1 / Type 2 QCL information.

[0310] In addition, for the application of the third TCI state among multiple TCI states indicated using one TCI code point, the UE may determine the timing of application of the indicated TCI state based on a parameter ("ThirdbeamApptime") that sets the beam application time corresponding to the third Type 1 / Type 2 QCL information.

[0311] The determination of the BAT based on the parameters that set the application times of these multiple beams may follow at least one of the following variations 2-1-1-1 to 2-1-1-4.

[0312] [Variation 2-1-1-1] The UE may determine that the BAT set by a parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information is a common BAT. The UE may apply the first TCI state corresponding to the first Type 1 / Type 2 QCL information at a timing based on the common BAT.

[0313] The UE may apply the first TCI state corresponding to the nth Type 1 / Type 2 QCL information at a timing based on a BAT set by parameters that set the beam application time corresponding to the nth (n is an integer greater than or equal to 2) Type 1 / Type 2 QCL information and a common BAT.

[0314] 21A is a diagram showing an example of application of the TCI state according to Variation 2-1-1-1. In the example shown in Fig. 21A, the UE determines that the BAT set by the parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information is a common BAT, and applies the first TCI state.

[0315] In addition, in the example shown in Figure 21A, the UE applies to the second TCI state at the timing obtained by adding up the BAT (BAT#1 in Figure 21A) set by the parameter ("SecondbeamApptime") that sets the beam application time corresponding to the second Type 1 / Type 2 QCL information and the common BAT.

[0316] [Variation 2-1-1-2] The UE may determine that the BAT set by the parameters that set the beam application time corresponding to the mth (m is a positive integer) Type 1 / Type 2 QCL information is the BAT for applying the mth TCI state.

[0317] 21B is a diagram showing an example of application of the TCI state according to Variation 2-1-1-2. In the example shown in FIG. 21B, the UE determines that the BAT set by the parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information is BAT#1 (which may be a common BAT), and applies the first TCI state.

[0318] Also, in the example shown in Figure 21B, the UE determines that the BAT set by the parameter ("SecondbeamApptime") that sets the beam application time corresponding to the second Type 1 / Type 2 QCL information is BAT#2, and applies the second TCI state.

[0319] [Variation 2-1-1-3] The UE may determine that the BAT set by a parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information is a common BAT. The UE may apply the first TCI state corresponding to the first Type 1 / Type 2 QCL information at a timing based on the common BAT.

[0320] The UE may apply the first TCI state corresponding to the nth type 1 / type 2 QCL information at a timing based on a BAT set with parameters that set the beam application time corresponding to the nth (n is an integer greater than or equal to 2) type 1 / type 2 QCL information, and a BAT set with parameters that set the beam application time corresponding to the n-1th type 1 / type 2 QCL information.

[0321] In this case, the period from the application timing of the (n-1)th TCI state to the application timing of the nth TCI state may be set using a parameter that sets the beam application time corresponding to the nth Type 1 / Type 2 QCL information.

[0322] Alternatively, the RRC parameters for the TCI state ("TCI-State") may not include parameters for setting the beam application time corresponding to the nth Type 1 / Type 2 QCL information (e.g., the above-mentioned "SecondbeamApptime" and "ThirdbeamApptime"), but may instead include parameters indicating the switching gap.

[0323] The parameter indicating the switching gap may be a parameter indicating the period / gap from the application timing of the (n-1)th TCI state to the application timing of the nth TCI state.

[0324] 22A is a diagram showing an example of application of the TCI state according to Variation 2-1-1-3. In the example shown in FIG. 22A, the UE determines that the common BAT is set by a parameter ("beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information, and applies the first TCI state.

[0325] In the example shown in Fig. 22A, a parameter indicating a switching gap is set for the UE. The UE determines the application timing of the second TCI state and the third TCI state based on the timing indicated by the switching gap parameter (BAT#1 in Fig. 22A).

[0326] [Variation 2-1-1-4] The UE may determine that the BAT set by a parameter (e.g., "beamApptime") that sets the beam application time corresponding to the first Type 1 / Type 2 QCL information is a parameter that indicates the switching gap from the application timing of the m-1th TCI state to the application timing of the mth TCI state.

[0327] In variation 2-1-1-4, the RRC parameters for the TCI state ("TCI-State") may not include parameters for setting the beam application time corresponding to the mth Type 1 / Type 2 QCL information (for example, the above-mentioned "beamApptime", "SecondbeamApptime", and "ThirdbeamApptime"), but may instead include parameters indicating a switching gap.

[0328] Fig. 22B is a diagram showing an example of application of the TCI state according to Variation 2-1-1-4. In the example shown in Fig. 22B, the UE determines the application timing of the first, second, or third TCI state based on a BAT (BAT#1 in Fig. 22B) set by a parameter indicating a switching gap.

[0329] According to option 2-1-1-4, overhead can be reduced by narrowing down the BAT for application of multiple TCI states to one.

[0330] Option 2-1-2 For a UE, QCL information ("QCL-info") containing information about multiple source RSs may be configured using RRC.

[0331] In Option 2-1-2, the QCL information in the parameters of one TCI state may include information about multiple source RSs. Therefore, the UE may receive an indication of one TCI codepoint (TCI state ID) and determine BATs to apply to multiple TCI states based on information about multiple source RSs included in the indicated TCI state.

[0332] The information regarding multiple source RSs may be, for example, an RRC parameter indicating a first reference signal (e.g., "referenceSignal"), an RRC parameter indicating a second reference signal (e.g., "SecondreferenceSignal"), and an RRC parameter indicating a third reference signal (e.g., "ThirdreferenceSignal").

[0333] The parameter indicating each reference signal may indicate the index of the reference signal (for example, CSI-RS / SSB) to which it refers.

[0334] The number of pieces of information about the source RS is not limited to 3, and may be any number. The names of the parameters are merely examples, and are not limited to these examples.

[0335] 23 is a diagram showing an example of TCI state parameters related to Option 2-1-2. In the example shown in Fig. 23, the RRC parameter ("TCI-State") includes Type 1 QCL information ("qcl-Type1"), Type 2 QCL information ("qcl-Type2"), and a parameter ("beamApptime") that sets the beam application time.

[0336] In addition, in the example shown in Figure 23, the parameters of the QCL information ("QCL-Info") referenced by Type 1 QCL information ("qcl-Type1") and Type 2 QCL information ("qcl-Type2") include an RRC parameter ("referenceSignal") indicating the first reference signal and an RRC parameter ("SecondreferenceSignal") indicating the second reference signal.

[0337] Although FIG. 23 shows an example in which the number of parameters related to the reference signal in the QCL information is two, the number is not limited to this example and may be three or more.

[0338] In the example shown in Fig. 23, the UE determines whether to apply a first TCI state among multiple TCI states indicated by one TCI codepoint based on information about a first source RS, and also determines whether to apply a second TCI state among multiple TCI states indicated by one TCI codepoint based on information about a second source RS.

[0339] At this time, the application timing of the first and second TCI states may be determined based on a parameter ("beamApptime") that sets the beam application time included in the parameters of the TCI states.

[0340] In the example shown in Figure 23 above, a parameter for setting the beam application time ("beamApptime") is included in the parameters of the TCI state, but the parameter for setting the beam application time ("beamApptime") may also be included in the parameters of the QCL information ("QCL-Info").

[0341] When a parameter for setting a beam application time is included in the parameter of QCL information ("QCL-Info"), there may be multiple parameters for setting the beam application time. In this case, each of the parameters for multiple source RSs included in the parameter of QCL information ("QCL-Info") may correspond to each of the parameters for setting the beam application time. The UE may apply a BAT corresponding to the parameter for the source RS to apply a TCI state corresponding to the parameter for the source RS.

[0342] The determination of the BAT based on the parameters that set the beam application time in option 2-1-2 may be appropriately performed using at least one of the above variations 2-1-1-1 to 2-1-1-4.

[0343] 《Option 2-1-3》 The UE may receive an activation / deactivation command (MAC CE) that includes fields related to multiple TCI states for multiple (different) BATs.

[0344] The multiple BATs may be BATs corresponding to the application of each of multiple TCI states associated with one TCI code point.

[0345] The MAC CE may be a MAC CE described in at least one of options 2-1-3-1 and 2-1-3-2 below.

[0346] [Option 2-1-3-1] The MAC CE may be a new MAC CE (defined in Rel. 17 and later).

[0347] A new Logical Channel ID (LCID) may be included in the subheader of the MAC CE.

[0348] The MAC CE may include a field indicating the activation of the TCI state.

[0349] The number of fields / octets included in the MAC CE may be configured using RRC signaling or may be determined based on reported UE capability information, which may be defined, for example, by the maximum number of BATs associated with one codepoint.

[0350] FIG. 24 is a diagram showing an example of the configuration of a MAC CE according to option 2-1-3-1. The MAC CE shown in FIG. 24 includes a field indicating a CORESET pool ID, a field indicating a serving cell ID, a field indicating a BWP ID, and a field indicating the activation of the TCI state (T N (described as "incomplete information").

[0351] In the MAC CE shown in FIG. 24, a field indicating activation of a TCI state may correspond to a BAT. For example, in the MAC CE, a field that activates a first TCI state among a plurality of TCI states corresponding to one TCI state corresponds to a first BAT (e.g., BAT#1). Also, in the MAC CE, a field that activates a second TCI state among a plurality of TCI states corresponding to one TCI state corresponds to a second BAT (e.g., BAT#2). In other words, the UE may refer to a field related to a first TCI state when the first BAT is applied, and may refer to a field related to a second TCI state when the second BAT is applied.

[0352] The MAC CE shown in Figure 24 further includes a field indicating BAT#1 and a field indicating BAT#2 corresponding to each TCI state. The UE determines the BAT corresponding to the indicated TCI state based on the field indicating the BAT.

[0353] In the example shown in FIG. 24, the field indicating the BAT may be added / deleted according to, for example, the LCID.

[0354] [Option 2-1-3-2] The MAC CE may be an existing MAC CE (for example, one defined by Rel. 15 / 16).

[0355] For this MAC CE, a reserved bit included in an existing MAC CE (e.g., defined up to Rel. 15 / 16) may be used as a field indicating whether to interpret the MAC CE as having a field for activating a list of TCI states with a BAT (time offset).

[0356] The MAC CE may be a MAC CE in which a new field / octet is added to an existing MAC CE (for example, defined up to Rel. 15 / 16).

[0357] The existing MAC CE (for example, defined by Rel. 15 / 16) may be, for example, a MAC CE for UE-specific PDSCH TCI state activation / deactivation (Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE).

[0358] 25 is a diagram showing an example of the configuration of a MAC CE according to option 2-1-3-2. The MAC CE shown in FIG. 25 includes a Serving Cell ID field, a BWP ID field, a field for indicating a TCI state identified by a TCI-StateID corresponding to each BAT (BAT#1 / #2) (TCI state IDi,j (i is an integer from 0 to N, j is 1 or 2)), and a field (C i ), and a reserved bit field (R, set to 0). Note that the field for indicating the TCI status corresponding to each BAT may also mean a field for indicating the TCI status to be referenced after each BAT has elapsed.

[0359] "i" may correspond to the index of the codepoint of the TCI field indicated by the DCI. "TCI state IDi,j" may indicate the j-th TCI state of the codepoint of the i-th TCI field.

[0360] The MAC CE shown in FIG. 25 further includes a field (D iY ) and a field (E iY (described as "and"), and

[0361] Above D iY When the field indicates a first value (for example, 0 (or 1)), the UE may determine that a field for indicating the TCI state corresponding to the TCI state ID i,1 corresponding to the BAT#Y is included. iY When the field indicates a second value (for example, 1 (or 0)), the UE may determine that a field for indicating the TCI state corresponding to the TCI state IDi,1 corresponding to BAT#Y is not included.

[0362] Above E iY When the field indicates a first value (for example, 0 (or 1)), the UE may determine that a field indicating a BAT corresponding to the TCI state IDi,2 corresponding to BAT#Y is included. iY When the field indicates a second value (for example, 1 (or 0)), the UE may determine that a field indicating a BAT corresponding to TCI state IDi,2 corresponding to BAT#Y is not included.

[0363] In the example shown in FIG. 25, the UE determines the BAT corresponding to the indicated TCI state based on the field indicating the BAT.

[0364] 25 shows the case where the number of BATs is two, but the number may be three or more. Also, the MAC CE in option 2-1-3-2 may include a field indicating each BAT (for example, BAT#1 / #2 in the example of FIG. 25) corresponding to the TCI state ID, as described in option 1-1-5-2 of the first embodiment.

[0365] According to the above options 2-1-1 to 2-1-3, even if multiple TCI states are associated with one TCI code point, the TCI state / BAT can be set appropriately.

[0366] The following describes the timing (symbol / slot) at which the UE starts applying the TCI state / referencing the RS when one TCI codepoint is mapped to multiple TCI states / source RSs with multiple BATs.

[0367] If one TCI code point is mapped to multiple TCI states / source RSs with multiple BATs, the UE may determine the start timing (symbol / slot) for referencing the RS for the indicated TCI state based on a specific method.

[0368] The particular method may follow at least one of the following options 2-2-1 and 2-2-2.

[0369] Option 2-2-1 The UE may start to reference the RS for the indicated TCI state based on the configured / indicated BAT after a specific time resource determined based on at least one of the methods described in the first embodiment above.

[0370] In other words, the UE may start applying the indicated TCI state based on the configured / indicated BAT after a certain time resource determined based on at least one of the methods described in the first embodiment above.

[0371] The set / indicated BAT may indicate a period from the particular time resource.

[0372] 26A and 26B are diagrams illustrating an example of application of the TCI state according to option 2-2-1. As shown in the example of Fig. 26A, the UE is configured to associate a TCI code point with multiple TCI states (first TCI state / second TCI state) and a BAT corresponding to each TCI state.

[0373] In the example shown in FIG. 26B, the UE receives a beam instruction DCI indicating a TCI code point "000." At this time, the UE determines that the application of the first TCI state (TCI#0) will start at a timing after BAT#1 has elapsed since the transmission of the HARQ-ACK associated with the beam instruction DCI. The UE also determines that the application of the second TCI state (TCI#1) will start at a timing after BAT#2 has elapsed since the transmission of the HARQ-ACK associated with the beam instruction DCI.

[0374] Option 2-2-2 The UE may start to reference the RS for the indicated TCI state based on the configured / indicated BAT after a specific time resource determined based on at least one of the methods described in the first embodiment above.

[0375] In other words, the UE may start applying the indicated TCI state based on the configured / indicated BAT after a certain time resource determined based on at least one of the methods described in the first embodiment above.

[0376] The set / instructed BAT may indicate at least one of a period from the specific time resource and a period to be added (ie, a differential BAT).

[0377] For example, the UE may determine that, for a first TCI state among multiple TCI states and multiple BATs corresponding to one TCI code point, application starts after the BAT corresponding to the first TCI state (first BAT) has elapsed from the specific time resource. At this time, the UE may determine that, for a second TCI state, application starts after the specific time resource has elapsed from the first BAT and further after the BAT corresponding to the second TCI state (second BAT) has elapsed. In this way, the start of application of the nth TCI state may be determined / determined based on the start timing of application of the (n-1)th TCI state and the specified BAT.

[0378] 27A and 27B are diagrams illustrating an example of application of the TCI state according to option 2-2-2. As shown in the example of Fig. 27A, the UE is configured to associate a TCI code point with multiple TCI states (first TCI state / second TCI state) and a BAT corresponding to each TCI state.

[0379] In the example shown in FIG. 27B, the UE receives a beam instruction DCI instructing a TCI code point "000." At this time, the UE determines that the start of application of the first TCI state (TCI#0) is the timing after BAT#1 has elapsed since the transmission of the HARQ-ACK associated with the beam instruction DCI. The UE also determines that the start of application of the second TCI state (TCI#1) is the timing after BAT#2 has elapsed since the start of application of the first TCI state (the timing after BAT#1 has elapsed since the transmission of the HARQ-ACK associated with the beam instruction DCI).

[0380] In this embodiment, the UE may assume that application of the first TCI state begins before application of the second TCI state. In this embodiment, the UE may assume that application of the nth TCI state begins before application of the (n+1)th TCI state.

[0381] In this embodiment, the UE may assume that the first BAT and the second BAT have the same value. In this case, information indicating the value of one BAT may be notified to the UE. This method can reduce the overhead of notifying the UE of the BAT.

[0382] According to the second embodiment described above, even when a plurality of TCI states correspond to one TCI code point, it is possible to appropriately apply a TCI state and determine the timing of application of the TCI state.

[0383] <Third embodiment> The third embodiment relates to the number of TCI states to activate for the UE.

[0384] <<Aspect 3-1>> The UE may receive activation commands (MAC CEs) corresponding to a certain number (eg, up to X) of TCI state combinations / pairs.

[0385] For example, the MAC CE may activate up to eight TCI state combinations / pairs.

[0386] In the present disclosure, one TCI state combination may correspond to a TCI state (a pair of TCI states) indicated by one TCI codepoint.

[0387] <<Aspect 3-2>> The UE may receive activation commands (MAC CEs) corresponding to combinations of TCI states, consisting of a certain number (eg, up to X) of TCI states (pairs of TCI states) in total.

[0388] For example, the MAC CE may activate a maximum of eight TCI states (TCI state pairs) in total. By limiting the maximum TCI states in this way, the number of active TCI states can be limited.

[0389] <<Aspect 3-3>> The UE may receive activation commands (MAC CEs) corresponding to TCI state combinations / pairs that total a certain number (eg, up to X) of source RSs of QCL information.

[0390] For example, the MAC CE may activate TCI states (TCI state pairs) that include a total of up to eight source RSs.

[0391] The X may be determined / set for each QCL type.

[0392] X may be determined / set for each specific QCL type (e.g., QCL type D).

[0393] The X may represent the maximum number of source RSs of a particular QCL type (eg, QCL type A / B / C) relative to the total number of source RSs.

[0394] In at least one of the above aspects 3-1 to 3-3, X may be a value defined in advance in a specification, may be determined based on higher layer signaling (RRC / MAC CE) / DCI, or may be determined based on reported UE capability information.

[0395] Although the above example shows that X is 8, numbers greater than 8 may be supported for X.

[0396] According to the third embodiment described above, it is possible to appropriately determine the number of TCI states to be activated for the UE.

[0397] <Fourth embodiment> The fourth embodiment relates to the maximum / minimum values ​​of the BAT.

[0398] The maximum / minimum values ​​of the BAT set / instructed to the UE may be values ​​defined in advance in the specifications, may be determined based on higher layer signaling (RRC / MAC CE) / DCI, or may be determined based on reported UE capability information.

[0399] <<Aspect 4-1>> The UE may not expect / anticipate receiving an indication / activation / configuration that includes a BAT value greater than the maximum BAT value specified / determined.

[0400] The UE may assume / expect not to receive an indication / activation / configuration that includes a BAT value greater than the specified / determined maximum BAT value.

[0401] If the UE is notified of an instruction / activation / configuration that includes a BAT value that is greater than the maximum value of the specified / determined BAT, the UE may decide to use the maximum value of the specified / determined BAT.

[0402] <<Aspect 4-2>> The UE may not expect / anticipate receiving an indication / activation / configuration that includes a BAT value that is less than the specified / determined minimum BAT value.

[0403] The UE may assume / expect not to receive an indication / activation / configuration that includes a BAT value that is less than the specified / determined minimum BAT value.

[0404] If the UE is notified of an instruction / activation / configuration that includes a BAT value that is smaller than the specified / determined minimum BAT value, the UE may decide to use the specified / determined minimum BAT value.

[0405] According to the fourth embodiment, it is possible to appropriately determine the maximum and minimum values ​​of the BAT and to appropriately perform the operation of the UE related to the maximum and minimum values.

[0406] <Fifth embodiment> The fifth embodiment relates to the operation when a UE receives multiple beam instruction DCIs.

[0407] <<Aspect 5-1>> The UE may not expect / expect to receive any particular DCI / MAC CE after receiving a DCI / MAC CE indicating the TCI state.

[0408] The particular DCI / MAC CE may be a DCI / MAC CE that indicates a BAT at a timing prior to the last BAT (beam application timing) indicated using the received DCI / MAC CE.

[0409] 28 is a diagram illustrating an example of application of the TCI state according to aspect 5-1. In the example illustrated in FIG. 28, the UE receives beam instruction DCI#1 instructing it to refer to RS#0 after BAT#0 has elapsed and to refer to RS#1 after BAT#1 has elapsed.

[0410] In the present disclosure, the referred RS may be interchangeably read as the source RS (reference RS) of the TCI state used at a certain time.

[0411] 28 shows beam instruction DCI#2 instructing to refer to RS#2 after BAT#2 has elapsed. Beam instruction DCI#2 exists after the reception of beam instruction DCI#1, and BAT#2 indicates a timing before BAT#1 (i.e., the last BAT indicated by beam instruction DCI#1).

[0412] In such a case, the UE does not assume / expect to receive beam instruction DCI#2.

[0413] 29 is a diagram illustrating another example of application of the TCI state according to aspect 5-1. In the example illustrated in FIG. 29, the UE receives beam instruction DCI#1 instructing it to refer to RS#0 after BAT#0 has elapsed and to refer to RS#1 after BAT#1 has elapsed.

[0414] 29 shows beam instruction DCI#2 instructing to refer to RS#2 after BAT#2 has elapsed. Beam instruction DCI#2 exists after the reception of beam instruction DCI#1, and BAT#2 indicates a timing after BAT#1 (i.e., the last BAT indicated by beam instruction DCI#1).

[0415] In such a case, the UE determines to refer to RS#2 in accordance with the beam instruction DCI#2.

[0416] <<Aspect 5-2>> After receiving a DCI / MAC CE indicating a TCI state, the UE may ignore some / all of the indications given by the particular DCI / MAC CE.

[0417] The particular DCI / MAC CE may be a DCI / MAC CE that indicates a BAT at a timing prior to the last BAT (beam application timing) indicated using the received DCI / MAC CE.

[0418] Regarding the instruction by the beam instruction DCI#2 as shown in FIG. 28, the UE ignores part or all of the instruction.

[0419] Aspect 5-3 The UE may not expect / expect to receive any particular DCI / MAC CE after receiving a DCI / MAC CE indicating the TCI state.

[0420] The particular DCI / MAC CE may be a DCI / MAC CE that indicates a TCI state / RS that is different from the TCI state / RS at a timing prior to the last BAT (beam application timing) indicated using the received DCI / MAC CE.

[0421] 30 is a diagram illustrating an example of application of the TCI state according to aspect 5-3. In the example illustrated in FIG. 30, the UE receives beam instruction DCI#1 instructing it to refer to RS#0 after BAT#0 has elapsed and to refer to RS#1 after BAT#1 has elapsed.

[0422] 30 describes beam instruction DCI#2 instructing to refer to RS#0 in a specific period from after BAT#0 has elapsed until before BAT#1 has elapsed, to refer to RS#1 in a specific period from after BAT#1 has elapsed until after BAT#2 has elapsed, and to refer to RS#2 after BAT#2 has elapsed. The instructions for RS#0 and RS#1 by beam instruction DCI#2 include instructions with the same content as the instructions of beam instruction DCI#1.

[0423] In such a case, the UE determines to refer to RS#2 (and RS#0 / #1) in accordance with the beam instruction DCI#2.

[0424] On the other hand, with regard to beam instruction DCI#2 as shown in FIG. 28 above, the UE does not assume / expect to receive this beam instruction DCI.

[0425] Aspect 5-4 After receiving a DCI / MAC CE indicating a TCI state, the UE may ignore some / all of the indications given by the particular DCI / MAC CE.

[0426] The particular DCI / MAC CE may be a DCI / MAC CE that indicates a TCI state / RS that is different from the TCI state / RS at a timing prior to the last BAT (beam application timing) indicated using the received DCI / MAC CE.

[0427] The part of the information that the UE ignores may be specified in advance in a specification, may be determined based on higher layer signaling (RRC / MAC CE) / DCI, or may be determined based on reported UE capability information.

[0428] Aspect 5-5 In example 5-5, an operation will be described in which the UE receives a specific DCI / MAC CE after receiving a DCI / MAC CE indicating the TCI state.

[0429] The particular DCI / MAC CE may be a DCI / MAC CE that indicates a TCI state / RS that is different from the TCI state / RS at a timing prior to the last BAT (beam application (start) timing) indicated using the received DCI / MAC CE.

[0430] If the UE receives a specific DCI / MAC CE after receiving a DCI / MAC CE indicating a TCI state, the UE may apply (change) the TCI state based on the instruction of the later received DCI / MAC CE, and in this case, the UE does not need to refer to the TCI state / source RS to be applied after a specific timing for the instruction of the previously received DCI / MAC CE.

[0431] The specific timing may be at least one of the following options 5-5-1 and 5-5-2.

[0432] [Option 5-5-1] The specific timing may be a timing after a specific period (for example, X symbols / slots / subframes / Y [ms]) has elapsed after receiving the (later received) DCI / MAC CE.

[0433] Furthermore, the specific timing may be the transmission timing of a HARQ-ACK associated with the DCI / MAC CE (to be received later).

[0434] 31 is a diagram showing an example of application of the TCI state according to option 5-5-1. In the example shown in Fig. 31, the UE receives beam instruction DCI#1 instructing it to refer to RS#0 after BAT#0 has elapsed, to refer to RS#1 after BAT#1 has elapsed, and to refer to RS#2 after BAT#2 has elapsed.

[0435] 31, the UE receives beam instruction DCI#2 instructing it to refer to RS#3 after BAT#3 has elapsed. BAT#3 exists between BAT#1 and BAT#2.

[0436] In the example shown in Figure 31, the UE does not follow the reference to RS (application of TCI state) by beam instruction DCI#1 after a specific timing (for example, after transmission of HARQ-ACK related to beam instruction DCI#2). That is, the UE determines to refer to RS#0 (does not determine to refer to RS#1) from after transmission of HARQ-ACK related to beam instruction DCI#2 until BAT#3. After BAT#3 has elapsed, the UE determines to refer to RS#3.

[0437] [Option 5-5-2] The particular timing may be the time resource (symbols) for the first TCI state / RS application / reference indicated by the (later received) DCI / MAC CE.

[0438] 32 is a diagram showing an example of application of the TCI state according to option 5-5-2. In the example shown in Fig. 32, the UE receives beam instruction DCI#1 instructing it to refer to RS#0 after BAT#0 has elapsed, to refer to RS#1 after BAT#1 has elapsed, and to refer to RS#2 after BAT#2 has elapsed.

[0439] 32, the UE receives beam instruction DCI#2 instructing it to refer to RS#3 after BAT#3 has elapsed. BAT#3 exists between BAT#1 and BAT#2.

[0440] In the example shown in Figure 32, the UE does not follow the reference to the RS (application of the TCI state) by the beam instruction DCI#1 after a specific timing (for example, the symbol for the first TCI state / RS application / reference (i.e., BAT#3) indicated by the beam instruction DCI). That is, before BAT#3, the UE determines to refer to RS#0 / #1 based on the indication of the beam instruction DCI#1, and after BAT#3 has elapsed, determines to refer to RS#3.

[0441] In the above aspects 5-1 to 5-5, "a timing before the last BAT" may be read as "a timing before a specific period of time has elapsed after the last BAT."

[0442] The specific period may be specified in advance in a specification, may be determined based on a specific rule, may be determined based on higher layer signaling (RRC / MAC CE) / DCI, or may be determined based on reported UE capability information (e.g., capability information regarding the application time of QCL ("timedurationForQCL")). The specific period may be expressed as X symbols / slots / subframes / Y [ms].

[0443] According to the fifth embodiment described above, even when multiple beam instructions are received, it is possible to appropriately control the application of the TCI state and the reference operation of the source RS.

[0444] <Other embodiments> At least one of the above embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0445] The specific UE capabilities may indicate (and may be defined by) at least one of the following: · Capabilities for operations / information regarding each embodiment / aspect. ·Ability to understand the behavior / information regarding each option / combination of options. ·Ability to understand the behavior / information associated with each option / combination of options. · The maximum number of TCI states associated with one TCI codepoint (supported). · Maximum number of source RSs with the same QCL type associated with one TCI codepoint (supported). · Maximum number of activated TCI states (supported). · Max / Min BAT values ​​(supported).

[0446] The above UE capabilities may be defined, for example, by whether or not the UE supports at least one of the following: determining BAT (for AI-assisted beam prediction), configuring / instructing BAT, configuring / activating / instructing beam patterns (multiple TCI states), the maximum number of TCI states (combinations / pairs) included in a MAC CE, the maximum / minimum value of BAT, and behavior upon receiving multiple beam instructions.

[0447] The UE capabilities may also be defined as the maximum supported N / M / n / m / X / Y values ​​(described in each embodiment).

[0448] The UE capabilities may be reported per frequency, per frequency range (e.g., Frequency Range 1 (FR1), Frequency Range 2 (FR2), FR2-1, FR2-2), per cell, or per subcarrier spacing (SubCarrier Spacing (SCS)).

[0449] The UE capabilities may be reported jointly for Time Division Duplex (TDD) and Frequency Division Duplex (FDD), or may be reported independently.

[0450] Furthermore, at least one of the above-described embodiments may be applied when the UE is configured with specific information related to the above-described embodiments by higher layer signaling.

[0451] According to the above and other embodiments, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0495] The transceiver 120 may transmit configuration information including settings related to transmission configuration indication (TCI) states to be applied to a plurality of types of channels, and an instruction for the TCI states to be applied to the plurality of types of channels. The control unit 110 may use information related to a start timing of application of the TCI states, included in the configuration information, and the instruction to indicate the start timing of application of the TCI states (first embodiment).

[0496] The transceiver 120 may transmit configuration information including settings related to transmission configuration indication (TCI) states to be applied to multiple types of channels, and an instruction of the TCI states. Code points of the TCI field included in the instruction may be associated with multiple TCI states. The controller 110 may use information related to the start timing of application of the TCI states included in the configuration information and the instruction to indicate the start timing of application of the TCI states (second embodiment).

[0497] The transceiver 120 may transmit at least one of configuration information including settings related to transmission configuration indication (TCI) states to be applied to multiple types of channels, a first instruction related to the TCI state, and a second instruction related to the TCI state. The control unit 110 may instruct application of a first TCI state based on the first instruction and application of a second TCI state based on the second instruction, using at least one of information related to a start timing of application of a TCI state included in the configuration information, the first instruction, and the second instruction (fifth embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0515] The transceiver 220 may receive configuration information including settings related to transmission configuration indication (TCI) states to be applied to a plurality of types of channels, and instructions regarding the TCI states to be applied to the plurality of types of channels. The controller 210 may determine the timing to start applying the TCI states based on the instructions and information regarding the timing to start applying the TCI states included in the configuration information (first embodiment).

[0516] The configuration information may be a Radio Resource Control (RRC) parameter. The information regarding the timing at which the TCI state starts to be applied may be included in at least one of a configuration parameter for a physical downlink shared channel, a configuration parameter for a TCI state, and a configuration parameter for quasi-co-location (first embodiment).

[0517] The setting information may be a Medium Access Control (MAC) Control Element (CE). The information regarding the timing at which the TCI state starts to be applied may be a specific field included in the MAC CE (first embodiment).

[0518] The setting information may include information regarding a first application start timing corresponding to a first TCI state among the TCI states, and information regarding a second application start timing corresponding to a second TCI state among the TCI states. When applying the first TCI state, the control unit 210 may determine the application start timing of the first TCI state based on the information regarding the first application start timing. When applying the second TCI state, the control unit 210 may determine the application start timing of the second TCI state based on the information regarding the first application start timing and the information regarding the second application start timing.

[0519] The transceiver 220 may receive configuration information including settings related to transmission configuration indication (TCI) states to be applied to multiple types of channels, and an instruction regarding the TCI states. Code points in the TCI field included in the instruction may be associated with multiple TCI states. The controller 210 may determine the timing to start applying the TCI states based on information related to the start timing of the TCI states included in the configuration information and the instruction (second embodiment).

[0520] The setting information may include information regarding a first application start timing corresponding to a first TCI state among the plurality of TCI states, and information regarding a second application start timing corresponding to a second TCI state among the plurality of TCI states. When applying the first TCI state, the control unit 210 may determine the application start timing of the first TCI state based on the information regarding the first application start timing. When applying the second TCI state, the control unit 210 may determine the application start timing of the second TCI state based on the information regarding the first application start timing and the information regarding the second application start timing (second embodiment).

[0521] The configuration information may be a Medium Access Control (MAC) Control Element (CE). The MAC CE may activate TCI states included in a maximum of a specific number of TCI state pairs or combinations (third embodiment).

[0522] The control unit 210 does not need to assume receipt of at least one of an instruction regarding an application start timing that is greater than the maximum value regarding the application start timing and an instruction regarding an application start timing that is less than the minimum value regarding the application start timing (fourth embodiment).

[0523] The transceiver 220 may receive at least one of configuration information including settings related to transmission configuration indication (TCI) states to be applied to multiple types of channels, a first instruction related to the TCI state, and a second instruction related to the TCI state. The controller 210 may determine whether to apply a first TCI state based on the first instruction or a second TCI state based on the second instruction, based on at least one of information related to a start timing of application of a TCI state included in the configuration information, the first instruction, and the second instruction (fifth embodiment).

[0524] The control unit 210 may not anticipate receiving the second instruction instructing the start timing of application of the second TCI state to be earlier than a specific timing related to the start timing of application of the first TCI state, and may also ignore at least a part of the second instruction instructing the start timing of application of the second TCI state to be earlier than the specific timing (fifth embodiment).

[0525] The control unit 210 may not anticipate receiving the second instruction instructing the application of a TCI state other than the first TCI state during the period in which the first TCI state based on the first instruction is applied, and may also ignore at least a part of the second instruction instructing the application of a TCI state other than the first TCI state during the period (fifth embodiment).

[0526] The control unit 210 may determine, after a specific period of time has elapsed since receiving the second instruction, to change the application of the first TCI state based on the first instruction and apply the second TCI state based on the second instruction (fifth embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiving unit that receives configuration information including settings related to transmission configuration indication (TCI) states applied to a plurality of types of channels and an indication of the TCI states applied to the plurality of types of channels; A terminal having a control unit that determines the start timing of application of the TCI state for AI-assisted beam prediction based on information regarding the start timing of application of the TCI state included in the setting information and the instruction, and predicts beam quality using AI using the determined start timing of application of the TCI state.

2. the configuration information is a Radio Resource Control (RRC) parameter, The terminal according to claim 1 , wherein the information regarding the timing at which the TCI state starts to be applied is included in at least one of a configuration parameter for a physical downlink shared channel, a configuration parameter for the TCI state, and a configuration parameter for quasi-colocation.

3. the setting information is a Medium Access Control control element (MAC Control Element (CE)), The terminal according to claim 1 , wherein the information regarding the timing at which the TCI state starts to be applied is a specific field included in the MAC CE.

4. the setting information includes information on a first application start timing corresponding to a first TCI state among the TCI states, and information on a second application start timing corresponding to a second TCI state among the TCI states; When applying the first TCI state, the control unit determines an application start timing of the first TCI state based on information related to the first application start timing; The terminal according to claim 1, wherein, when the second TCI state is applied, the control unit determines the application start timing of the second TCI state based on information regarding the first application start timing and information regarding the second application start timing.

5. receiving configuration information including configurations related to transmission configuration indication (TCI) states to be applied to a plurality of types of channels and an indication of the TCI states to be applied to the plurality of types of channels; A wireless communication method for a terminal, comprising: a step of determining the start timing of application of the TCI state for AI-assisted beam prediction based on information regarding the start timing of application of the TCI state included in the setting information and the instruction; and a step of predicting beam quality using AI using the determined start timing of application of the TCI state.

6. a transmitter that transmits configuration information including settings related to transmission configuration indication (TCI) states applied to a plurality of types of channels and an indication of the TCI states applied to the plurality of types of channels; A base station having a control unit that instructs the start timing of application of the TCI state for AI-assisted beam prediction using information regarding the start timing of application of the TCI state included in the setting information and the instruction.

Images