Terminal, wireless communication method, and base station

Abstract

To appropriately recognize the TCI state using AI-assisted beam prediction. [Solution] The terminal of the present invention has a control unit which has setting information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, a receiving unit which receives at least one of a first instruction and a second instruction regarding the TCI state, and a control unit which determines whether to apply a first TCI state based on the first instruction and whether to apply a second TCI state based on the second instruction, based on information regarding the timing of the start of application of the TCI state included in the setting information, and at least one of the first instruction and the second instruction, and predicts beam quality using AI based on the result of the determination.

Description

[Technical Field]

[0001] This disclosure relates to terminals, wireless communication methods, and base stations in next-generation mobile communication systems. [Background technology]

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

[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being considered. [Prior art documents] [Non-patent 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 [Overview of the project] [Problems that the invention aims to solve]

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

[0006] A unified TCI state is being considered that applies the configured / activated / instructed TCI state to multiple types of channels / reference signals (RS). However, there are cases where the method for applying the unified TCI state is unclear. If such relationships are unclear, it may lead to a decrease in communication quality, throughput, etc.

[0007] Therefore, one of the objectives of this 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 aspect of the present disclosure includes a control unit that receives configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, a first instruction regarding the TCI state, and a second instruction regarding the TCI state, and that determines whether to apply a first TCI state based on the first instruction and a second TCI state based on the second instruction, based on information regarding the timing of the start of application of the TCI state included in the configuration information, and at least one of the first instruction and the second instruction, and predicts beam quality using AI based on the result of the determination. [Effects of the Invention]

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

Brief Description of the Drawings

[0010] [Figure 1] Figures 1A and 1B are diagrams showing an example of a common beam. [Figure 2] Figure 2 is a diagram showing an example of the MAC CE defined in Rel.16. [Figure 3] Figure 3 is a diagram showing another example of the MAC CE defined in Rel.16. [Figure 4] Figure 4 is a diagram showing another example of the MAC CE defined in Rel.16. [Figure 5] Figures 5A and 5B are diagrams showing an example of an indication of a joint / separate TCI state. [Figure 6] Figure 6 is a diagram showing an example of the timing until the application of the indicated TCI state. [Figure 7] Figure 7 is a diagram showing an example of the criteria for starting the BAT according to the first embodiment. <� [Figure 8] Figures 8A and 8B are diagrams showing an example of the application of the TCI state according to Option 1-1-1. [Figure 9] Figures 9A and 9B are diagrams showing an example of the application of the TCI state according to Option 1-1-3. [Figure 10] Figure 10 is a diagram showing an example of the application of the TCI state according to Option 1-1-4. [Figure 11] Figure 11 is a diagram showing an example of the application of the TCI state according to Modification 1 of Option 1-1-4. [Figure 12] Figure 12 is a diagram showing an example of the application of the TCI state according to Modification 2 of Option 1-1-4. [Figure 13] Figure 13 is a diagram showing an example of the configuration of the MAC CE according to Option 1-1-5-1. [Figure 14] Figure 14 is a diagram showing an example of the configuration of the MAC CE according to Option 1-1-5-2. [Figure 15] Figures 15A and 15B are diagrams showing an example of the application of the TCI state according to Option 1-2-1. [Figure 16] Figure 16 is a diagram showing an example of the application of the TCI state according to Option 1-2-2. [Figure 17] Figure 17A is a diagram showing an example of the association of BAT values according to Option 1-3-1. Figure 17B is a diagram showing an example of the association of BAT values according to Option 1-3-2. [Figure 18] Figures 18A and 18B are diagrams showing an example of the application of the TCI state according to the second embodiment. [Figure 19] Figure 19 is a diagram showing another example of the application of the TCI state according to the second embodiment. [Figure 20] Figure 20 is a diagram showing an example of the parameters of the TCI state according to Option 2-1-1. [Figure 21] Figure 21A is a diagram showing an example of the application of the TCI state according to Variation 2-1-1-1. Figure 21B is a diagram showing an example of the application of the TCI state according to Variation 2-1-1-2. [Figure 22] Figure 22A is a diagram showing an example of the application of the TCI state according to Variation 2-1-1-3. Figure 22B is a diagram showing an example of the application of the TCI state according to Variation 2-1-1-4. [Figure 23] Figure 23 is a diagram showing an example of the parameters of the TCI state according to Option 2-1-2. [Figure 24] Figure 24 is a diagram showing an example of the configuration of the MAC CE according to Option 2-1-3-1. [Figure 25] Figure 25 is a diagram showing an example of the configuration of the MAC CE according to Option 2-1-3-2. [Figure 26] Figures 26A and 26B are diagrams showing an example of the application of the TCI state according to Option 2-2-1. [Figure 27] Figures 27A and 27B are diagrams showing an example of the application of the TCI state according to Option 2-2-2. [Figure 28]Figure 28 shows an example of the application of the TCI state according to embodiment 5-1. [Figure 29] Figure 29 shows another example of the application of the TCI state according to embodiment 5-1. [Figure 30] Figure 30 shows an example of the application of the TCI state according to embodiment 5-3. [Figure 31] Figure 31 shows an example of the application of the TCI status related to option 5-5-1. [Figure 32] Figure 32 shows an example of the application of the TCI status related to option 5-5-2. [Figure 33] Figure 33 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 34] Figure 34 shows an example of the configuration of a base station according to one embodiment. [Figure 35] Figure 35 shows an example of the configuration of a user terminal according to one embodiment. [Figure 36] Figure 36 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Figure 37] Figure 37 shows an example of a vehicle according to one embodiment. [Modes for carrying out the invention]

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

[0012] The TCI state may represent the one applied to the downlink signal / channel. The equivalent of the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0013] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set for each channel or signal in the UE.

[0014] QCL is an index that indicates the statistical properties of a signal / channel. For example, if two signals / channels have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

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

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

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

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

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

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

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

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

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

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

[0025] QCL type A RS is always set for PDCCH and PDSCH, and QCL type D RS may be set additionally. Because it is difficult to estimate Doppler shift, delay, etc. from a single shot of DMRS reception, QCL type A RS is used to improve channel estimation accuracy. QCL type D RS is used for receiving beam determination when DMRS is received.

[0026] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is advertised as QCL type C / D RS by the PDSCH's TCI state. By advertising the TCI state, the UE can use information obtained from past periodic TRS1-1 reception / measurement results to receive / channel estimate the DMRS for the PDSCH. In this case, the PDSCH's QCL source is TRS1-1, and the QCL target is the DMRS for the PDSCH.

[0027] (Multi-TRP) In NR, it is being considered that one or more transmission / reception points (TRPs) (multi-TRPs (MTRPs)) will use one or more panels (multi-panels) to perform DL transmission to the UE. Furthermore, it is being considered that the UE will use one or more panels to perform UL transmission to one or more TRPs.

[0028] Multiple TRPs may correspond to the same cell identifier (Cell Identifier (ID)) or to different cell IDs. This cell ID may be a physical cell ID or a virtual cell ID.

[0029] Multiple TRPs (e.g., TRP #1, #2) may be connected by an ideal / non-ideal backhaul, and information, data, etc., may be exchanged. Each TRP in a multi-TRP may transmit a different code word (CW) and a different layer. Non-coherent joint transmission (NCJT) may be used as one form of multi-TRP transmission.

[0030] In NCJT, for example, TRP#1 modulates and layers a first codeword and transmits a first PDSCH using a first precode with a first number of layers (e.g., 2 layers). TRP#2 modulates and layers a second codeword and transmits a second PDSCH using a second precode with a second number of layers (e.g., 2 layers).

[0031] Furthermore, multiple PDSCHs (Multi-PDSCHs) that are NCJTed may be defined as partially or completely overlapping with respect to at least one of the time and frequency domains. In other words, 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] These first and second PDSCHs may be assumed not to be quasi-co-located. Reception of multiple PDSCHs may be reinterpreted as simultaneous reception of PDSCHs that are not of a certain QCL type (e.g., QCL type D).

[0033] Multiple PDSCHs from a multi-TRP (sometimes called multiple PDSCHs) may be scheduled using a single DCI (single DCI, single PDCCH) (single-master mode, single-DCI based multi-TRP). Multiple PDSCHs from a multi-TRP may each be scheduled using multiple DCIs (multi-DCI, multiple PDCCH) (multi-master mode, multi-DCI based multi-TRP).

[0034] In URLLC for multiple TRPs, support for PDSCH (Transport Block (TB) or Codeword (CW)) repetition spanning multiple TRPs is being considered. Support for repetition schemes (URLLC schemes, e.g., schemes 1, 2a, 2b, 3, 4) spanning multiple TRPs on the frequency domain, layer (spatial) domain, or time domain is being considered. In scheme 1, multiple PDSCHs from multiple TRPs are performed using space division multiplexing (SDM). In schemes 2a and 2b, PDSCHs from multiple TRPs are performed using frequency division multiplexing (FDM). In scheme 2a, the redundant version (RV) is the same for multiple TRPs. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCHs from multiple TRPs are performed using time division multiplexing (TDM). In Scheme 3, multi-PDSCH signals from multi-TRPs are transmitted within a single slot. In Scheme 4, multi-PDSCH signals from multi-TRPs are transmitted within different slots.

[0035] Such multi-TRP scenarios allow for more flexible transmission control using high-quality channels.

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

[0037] A UE may be determined to be a multi-TRP based on multi-DCI if at least one of the following conditions 1 and 2 is met. In this case, TRP may be interpreted as a CORESET pool index. [Condition 1] A CORESET pool index of 1 is set. [Condition 2] Two different values ​​(e.g., 0 and 1) are set for the CORESET pool index.

[0038] The UE may determine a single DCI-based multi-TRP if the following conditions are met. In this case, the two TRPs may be interpreted as two TCI states indicated by MAC CE / DCI. [conditions] The "Enhanced TCI States Activation / Deactivation for UE-specific PDSCH MAC CE" is used to specify one or two TCI states for a single code point in the TCI field within the DCI.

[0039] The DCI for common beam indication may be in 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 in a UE-group common DCI format.

[0040] (Unified / Common TCI Framework) According to the Unified TCI Framework, UL and DL channels can be controlled by a common framework. Rather than defining TCI states or spatial relationships for each channel as in Rel. 15, the Unified TCI Framework may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

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

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

[0043] The default beams for UL and DL may be aligned by beam management based on MAC CE (MAC CE level beam indication). Alternatively, the default TCI status of PDSCH may be updated to match the default UL beam (spatial relationship).

[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 MAC CE. UL / DL DCI may select one from the X active TCI states. The selected TCI state may be applied to both UL and DL channels / RS.

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

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

[0047] In this disclosure, when N=M=X (where X is any integer), it may mean that X TCI states (joint TCI states) common to ULs and DLs (corresponding to X TRPs) are notified / set / instructed to the UE.

[0048] Furthermore, when N=X (where X is any integer) and M=Y (where Y is any integer, and Y=X), it may mean that X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) are notified / set / instructed to the UE. These UL TCI states and DL TCI states may represent TCI states common to both UL and DL (i.e., joint TCI states) or separate TCI states for UL and DL (i.e., separate TCI states).

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

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

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

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

[0053] Furthermore, for example, if N=2 and M=1 are specified, it may mean that the UE is notified / set / instructed to have a common TCI state for two ULs and DLs. In this case, the UE may use the two TCI states that are set / instructed as the UL TCI state, and one of the two TCI states that are set / instructed as the DL TCI state.

[0054] Furthermore, for example, if N=2 and M=1 are specified, it may mean that the UE is notified / configured / instructed to have two UL TCI states and one DL TCI state as separate TCI states.

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

[0056] The case M>1 / N>1 may indicate at least one of the following: a TCI status indication for multiple TRPs, and multiple TCI status indications for interband CAs.

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

[0058] In the example in Figure 1A, one point may represent a single TCI state that applies to both UL and DL, or it may represent two TCI states that apply to UL and DL respectively.

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

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

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

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

[0063] Existing DCI formats 1_1 / 1_2 may be used to indicate common TCI states.

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

[0065] The DCI format indicating the TCI status (DCI format 1_1 / 1_2) may be a DCI format without DL assignment. In this disclosure, the DCI format without DL assignment, the DCI format without scheduling PDSCH (DCI format 1_1 / 1_2), the DCI format that does not include one or more specific fields (DCI format 1_1 / 1_2), the DCI format in which one or more specific fields are set to fixed values ​​(DCI format 1_1 / 1_2), and so on may be interpreted interchangeably.

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

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

[0068] All RV fields may be set to 1. All MCS fields may be set to 1. All NDI fields may be set to 0. All FDRA fields for type 0 may be set to 0. All FDRA fields for type 1 may be set to 1. All FDRA fields for dynamic switches (upper layer parameter dynamicSwitch) may be set to 0.

[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 activating / deactivating the TCI state of UE-specific PDSCHs (see Figure 2).

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

[0072] The MAC CE may be used in environments using a single TRP or a multi-TRP based on multi-DCI.

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

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

[0075] Furthermore, 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 UE-specific PDSCHs (see Figure 3).

[0076] The MAC CE in question is identified by the MAC PDU subheader containing the eLCID.

[0077] The MAC CE may be used in environments that utilize multi-TRP 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 (where i is an integer from 0 to N, and j is 1 or 2)), a field (Ci) indicating whether or not TCI state IDi,2 exists in the corresponding octet, and a reserved bit field (R, set to 0).

[0079] "i" may correspond to the index of the code point of the TCI field indicated by DCI. "TCI state IDi,j" may indicate the j-th TCI state of the code point 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 activating / deactivating the TCI state of UE-specific PDCCH / CORESET (see Figure 4).

[0081] The MAC CE in question is identified by a MAC subheader containing an LCID.

[0082] The MAC CE may include a Serving Cell ID field, a field indicating a CORESET (CORESET ID) that indicates a TCI state, and a field (TCI state ID) that indicates a TCI state applicable to the CORESET identified by the CORESET ID.

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

[0084] [Consideration 1] The first slot to apply the indicated TCI is considered to be at least Y symbols after the last symbol of the acknowledgment (ACK) for the joint or separate DL / UL beam indication. The first slot to apply the indicated TCI is considered to be at least Y symbols after the last symbol of the ACK / negative acknowledgement (NACK) for the joint or separate DL / UL beam indication. The Y symbols may be set by the base station based on the UE capability reported by the UE. That UE capability may be reported in units of symbols.

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

[0086] For DCI basebeam indications in Rel.17, it is being considered that at least one Y symbol should be set for each BWP / CC in the UE.

[0087] If the SCS differs among multiple CCs, the Y symbol values ​​will also differ, potentially resulting in different application times among the multiple CCs.

[0088] [Consideration 2] For CA cases, the application time of the beam indication may follow any of the following options 1 to 3. [Option 1] Both the first slot and the Y symbol are determined on the carrier with the minimum SCS among the one or more carriers to which the beam indication is applied. [Option 2] Both the first slot and the Y symbol are determined on the carrier with the minimum SCS, which is one or more carriers to which the beam indication is applied, and the UL carrier carrying its ACK. [Option 3] Both the first slot and the Y symbol are determined on the UL carrier that carries its ACK.

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

[0090] The application time (Y symbol) for beam indication to CA may be determined on the carrier with the minimum SCS among the carriers to which beam indication is applied. MAC CE base beam indication in Rel. 17 (when only a single TCI code point is activated) may follow the Rel. 16 application timeline for MAC CE activation.

[0091] Based on these considerations, it is being considered that the following actions should be defined in the specifications. [Operation] When a UE transmits the last symbol of a PUCCH with HARQ-ACK information corresponding to a DCI that conveys a TCI state indication, the indicated TCI state with the Rel.17TCI state may begin to be applied from the first slot that is at least Y symbols after the last symbol of that PUCCH, where Y may be a higher layer parameter (e.g., BeamAppTime_r17[symbol]). Both the first slot and the Y symbol may be determined on the carrier with the minimum SCS among the carriers to which the beam indication is applied. At some point in time, the UE may assume one indicated TCI state with the Rel17TCI state for DL ​​and UL, or one indicated TCI state (separate from DL) with the Rel17TCI state for UL.

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

[0093] Regarding application time, it is being considered that the UE should report at least one of the following UE capabilities 1 and 2. [UE ability 1] Minimum application time per SCS (the minimum number of Y symbols between the last symbol of the PUCCH carrying the ACK and the first slot to which the beam is applied). [UE ability 2] The minimum time gap between the last symbol of the beam indicator PDCCH(DCI) and the first slot to which the beam is applied. The gap between the last symbol of the beam indicator PDCCH(DCI) and the first slot to which the beam is applied may satisfy the UE capability (minimum time gap).

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

[0095] The relationship between the beam direction 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 communication) 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, regarding future wireless communication technologies, it is being considered to utilize beam quality predicted using AI / ML for future beam designation. AI / ML can make beam quality prediction possible.

[0098] The BAT from HARQ-ACK related to beam indication is being considered to be at least one value set / (pre-defined) for the TCI state as defined in Rel.17 and later.

[0099] In Rel.17, it is being considered that beam pattern indication (sequence of TCI states) 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) can be indicated to the UE using the TCI state field (TCI field, maximum 3 bits) contained in the DCI format (for example, DCI format 1_1 / 1_2 without / with DL assignment).

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

[0102] Figure 5B shows an example of a separate TCI state indication. As shown in Figure 5B, in a separate TCI state indication, one or two TCI states correspond to a code point in a single TCI field. Each of the two TCI states may be a DL (separate) TCI state and a UL (separate) TCI state. Based on the code point of the indicated TCI field, the UE determines which TCI states to apply to the DL channel / signal and which TCI states to apply to the UL channel / signal. If the UE is notified of a code point in a TCI field that corresponds to only one TCI state (for example, code point "000" in Figure 10B), the UE may continue / indicate the UL TCI state that was applied up to the time of the notification, even if it is not indicated (for example, the UL TCI state in the case of code point "000" in Figure 5B).

[0103] Furthermore, in Rel.17 and later, a timeline has been considered regarding the time from the instruction of a TCI state (which may also be called a "beam instruction") to the application of the instructed TCI state. The timing from the receipt of the beam instruction to the application of the TCI state (which may also be called the beam application timing (BAT)) may be a time from the transmission of a HARQ-ACK to the PDSCH scheduled by the DCI that instructs the TCI state until a certain time (e.g., after the K symbol) (see Figure 6). This timing may be the first slot after at least a certain time (e.g., the K symbol). In this disclosure, BAT, beam application start timing, K symbol, Y symbol, X [ms], time offset, and timing offset may be interpreted as mutually exclusive.

[0104] The K may be determined based on upper-layer signaling (RRC parameters) based on capability information reported by the UE (UE Capability Information, e.g., "timeDurationForQCL-rel18"). Furthermore, the BAT for a particular subcarrier interval may be set for multiple (e.g., all) CC / BWPs where a common TCI state ID is set for a common TCI state in carrier aggregation (CA).

[0105] Incidentally, there are cases where the application of unified TCI states has not been adequately considered. For example, the dynamic instruction of the timeline from beam (TCI state) instruction to application (e.g., the BAT mentioned above) has not been adequately considered. Also, for example, the instruction of beam patterns for unified TCI states has not been adequately considered. If such considerations are insufficient, it may lead to a decrease in communication quality, a decrease in throughput, etc.

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

[0107] In one embodiment of this disclosure, a terminal (User Equipment (UE)) / base station (BS) trains an ML model in training mode and runs the ML model in test mode (also called test mode or testing mode). In test mode, the accuracy of the trained ML model trained in training mode may be validated.

[0108] In this disclosure, the UE / BS may input channel status information, reference signal measurements, etc., to the ML model and output high-precision channel status information / measurements / beam selection / position, future channel status information / wireless link quality, etc.

[0109] In this disclosure, AI may be interpreted as an object (also called a subject, object, data, function, program, etc.) having (implementing) at least one of the following characteristics: • Estimation based on observed or collected information • Selection based on observed or collected information. • Predictions based on observed or collected information.

[0110] In this disclosure, the object may be, for example, a device such as a terminal or base station. The object may also be a program included in the device.

[0111] Furthermore, in this disclosure, the ML model may be replaced with an object having (implementing) at least one of the following features: • By providing information (feeding), estimates are generated. By providing information, predict the estimated value. By providing information, we can discover features. • By providing information, the user can select an action.

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

[0113] An ML model outputs at least one piece of information based on the input information, such as an estimate, a prediction, a chosen 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 for mapping inputs to outputs. Unsupervised learning may be used to learn data features. Reinforcement learning may be used to learn actions to maximize an objective (goal).

[0115] The embodiments described later will primarily be explained assuming the use of supervised learning in the ML model, but are not limited to this.

[0116] In this disclosure, terms such as implementation, operation, function, and execution may be interpreted interchangeably. Similarly, terms such as test, after-training, production use, and actual use may be interpreted interchangeably. The term "signal" may be interpreted interchangeably with "signal / channel."

[0117] In this disclosure, the training mode may correspond to the mode in which the UE / BS transmits / receives signals for the ML model (in other words, the mode of operation during the training period). In this disclosure, the test mode may correspond to the mode in which the UE / BS runs the ML model (for example, runs the trained ML model to predict the output) (in other words, the mode of operation during the test period).

[0118] In this disclosure, training mode may mean a mode in which a particular signal transmitted in test mode is transmitted in a manner that has high overhead (e.g., high resource usage).

[0119] In this disclosure, the training mode may mean a mode that refers to a first configuration (e.g., a first DMRS configuration, a first CSI-RS configuration). In this disclosure, the test mode may mean a mode that refers to a second configuration other than the first configuration (e.g., a second DMRS configuration, a second CSI-RS configuration). The first configuration may have at least one more time resource, frequency resource, code resource, or port (antenna port) for measurement than the second configuration.

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

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

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

[0123] In this disclosure, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable.

[0124] In this disclosure, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In this disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher-layer parameters, RRC information elements (IE), RRC messages, and settings may be interpreted as mutually exclusive.

[0125] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). In this disclosure, MAC CEs, update commands, and activation / deactivation commands may be interpreted as interchangeable.

[0126] Broadcast information may include, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI, SIB1), and Other System Information (OSI).

[0127] In this disclosure, 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 of QCL type D in TCI state / QCL assumption, RS of 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 interpreted as each other. In this disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, DL-RS source, SSB, CSI-RS, and SRS may be interpreted as each other.

[0128] In this disclosure, the terms used include: panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmit entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relationship, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), base station, antenna port for a signal (e.g., Demodulation Reference Signal (DMRS) port), DMRS, antenna port group for a signal (e.g., DMRS port group), group for multiplexing (e.g., Code Division Multiplexing (CDM) group, reference signal group, CORESET group), and Physical Uplink Control. The following terms may be interchangeable: Channel (PUCCH) group, PUCCH resource group, resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, 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 layers (multi-input multi-output (MIMO) layer, transmit layer, spatial layer).Furthermore, Panel Identifier (ID) and Panel may be interpreted as interchangeable. In this disclosure, TRP ID and TRP may be interpreted as interchangeable.

[0129] Furthermore, the panel identifier (ID) and the panel may be interchangeable. In other words, TRP ID and TRP, CORESET group ID and CORESET group, etc., may be interchangeable.

[0130] In this disclosure, TRP, transmit point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in the TCI field may be interpreted as one another.

[0131] Each embodiment of the present disclosure may be used for at least one of single DCI-based single TRP transmission / reception, single DCI-based multi-TRP transmission / reception, and multi-DCI-based multi-TRP transmission / reception.

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

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

[0134] In this disclosure, single TRP, single TRP system, single TRP transmission, and single PDSCH may be interpreted interchangeably. In this disclosure, multiple TRP, multi-TRP system, multi-TRP transmission, and multi-PDSCH may be interpreted interchangeably. In this disclosure, single DCI, single PDCCH, multi-TRP based on a single DCI, and activating two TCI states on at least one TCI code point may be interpreted interchangeably.

[0135] In this disclosure, the following can be interpreted interchangeably: single TRP, channel using single TRP, channel using one TCI state / spatial relationship, multi-TRP not being enabled by RRC / DCI, multiple TCI state / spatial relationships not being enabled by RRC / DCI, no CORESET pool index value of 1 being set for any CORESET, and no code point in a TCI field being mapped to two TCI states.

[0136] In this disclosure, multi-TRP, channels using multi-TRP, channels using multiple TCI state / spatial relationships, multi-TRP being enabled by RRC / DCI, multiple TCI state / spatial relationships being enabled by RRC / DCI, and at least one of a single-DCI-based multi-TRP and a multi-DCI-based multi-TRP may be interpreted as mutually exclusive. In this disclosure, multi-DCI-based multi-TRP and a CORESET pool index (CORESETPoolIndex) value of 1 is set for a CORESET may be interpreted as mutually exclusive. In this disclosure, single-DCI-based multi-TRP and at least one code point of a TCI field being mapped to two TCI states may be interpreted as mutually exclusive.

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

[0138] In this 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 code point may be interpreted as mutually exclusive.

[0139] In this disclosure, the terms "multi-DCI (mDCI)," "multi-PDCCH," "multi-TRP system based on multi-DCI," "mDCI-based MTRP," "two CORESET pool indices," or "CORESET pool index = 1 (or a value of 1 or more)" may be interpreted interchangeably.

[0140] The QCLs in this disclosure may be interpreted interchangeably with QCL Type D.

[0141] In this disclosure, phrases such as "TCI state A is the same QCL type D as TCI state B," "TCI state A is the same as TCI state B," and "TCI state A is TCI state B and QCL type D" may be interpreted interchangeably.

[0142] In this disclosure, the code points of the DCI field 'Transmission Configuration Indication', the TCI code points, the DCI code points, and the code points of the TCI field may be interpreted as interchangeable.

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

[0144] In this disclosure, a PDSCH / PDCCH utilizing a single TRP may be interpreted as a PDSCH / PDCCH based on a single TRP, or a single TRP PDSCH / PDCCH. Furthermore, in this disclosure, a PDSCH / PDCCH utilizing an SFN may be interpreted as a PDSCH / PDCCH utilizing an SFN in multiple configurations, an SFN-based PDSCH / PDCCH, or an SFN PDSCH / PDCCH.

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

[0146] In this disclosure, the terms HST-SFN scheme, SFN scheme Rel.17 and later, new SFN scheme, new HST-SFN scheme, HST-SFN scenario Rel.17 and later, 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 at least one of the Doppler pre-compensation schemes may be interpreted as one another.

[0147] In this 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 interpreted interchangeably. In this disclosure, the terms pre-compensation scheme, mitigation scheme, improvement scheme, and correction scheme may be interpreted interchangeably.

[0148] In this disclosure, a linkage-containing PDCCH / searchspace(SS) / CORESET, a linked PDCCH / SS / CORESET, and a pair of PDCCH / SS / CORESETs may be interpreted interchangeably. In this disclosure, a non-linkage-containing PDCCH / SS / CORESET, an unlinked PDCCH / SS / CORESET, and a single PDCCH / SS / CORESET may be interpreted interchangeably.

[0149] In this disclosure, two linked CORESETs for PDCCH iterations and two CORESETs associated with two linked SS sets may be interpreted as one another.

[0150] In this disclosure, SFN-PDCCH repetition, PDCCH repetition, two linked PDCCHs, and one DCI being received across the two linked search spaces (SS) / CORESETs may be interpreted as mutually exclusive.

[0151] In this disclosure, PDCCH repeats, SFN-PDCCH repeats, PDCCH repeats for higher reliability, PDCCH for higher reliability, PDCCH for reliability, and two linked PDCCHs may be interpreted as one another.

[0152] In this disclosure, the terms PDCCH receiving method, PDCCH repetition, SFN-PDCCH repetition, HST-SFN, and HST-SFN scheme may be interpreted interchangeably.

[0153] In this disclosure, the PDSCH receiving method, single DCI-based multi-TRP, and HST-SFN scheme may be interpreted as interchangeable.

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

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

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

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

[0158] In each embodiment of this disclosure, SFN PDSCH / PDCCH may be interpreted as equivalent to SFN PDSCH / PDCCH as defined in Rel. 17 and later.

[0159] In each embodiment of this disclosure, the use of multiple TRPs based on multi-DCI may mean that the CORESET pool index = 1 is set. Alternatively, the use of multiple TRPs based on multi-DCI may mean that the CORESET pool index has two different values ​​(e.g., 0 and 1).

[0160] In each embodiment of this disclosure, UL transmission using multiple panels may mean a UL transmission scheme using multiple panels of UE by DCI enhancement.

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

[0162] Each embodiment of the present disclosure described below may be applied to the transmission and reception of any channel / signal to which the Unified TCI State Framework defined above in Rel. 17 and later applies.

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

[0164] In this disclosure, the terms small, few, short, and low may be interpreted interchangeably. Similarly, in this disclosure, terms such as ignore and drop may be interpreted interchangeably.

[0165] In this disclosure, "highest" and "lowest" may be interpreted interchangeably. Also, in this disclosure, "highest" may be interpreted interchangeably with "nth (where n is any natural number) largest," "greater than," "higher than," etc. Also, in this disclosure, "lowest" may be interpreted interchangeably with "nth (where n is any natural number) smallest," "smaller than," "lower than," etc.

[0166] In this disclosure, repetition, repeated transmission, and repeated reception may be interpreted as mutually exclusive.

[0167] In this disclosure, channel, signal, and channel / signal may be interpreted as interchangeable. In this disclosure, DL channel, DL signal, DL signal / channel, DL signal / channel transmission / reception, DL reception, and DL transmission may be interpreted as interchangeable. In this disclosure, UL channel, UL signal, UL signal / channel, UL signal / channel transmission / reception, UL reception, and UL transmission may be interpreted as interchangeable.

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

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

[0170] In this disclosure, timing, time, duration, time instance, slot, subslot, symbol, subframe, etc., may be interpreted interchangeably.

[0171] (Wireless communication method) Each embodiment / appearance / option / option / modification of this disclosure may be used based on at least one of the following conditions: • Explicitly setting the corresponding higher-level layer parameters. • (Implicitly) setting of related higher-level layer parameters. • Instructions for MAC CE / DCI (and the fields included in it). • (Reported) UE Capability. • Defined within the specifications. • Specific conditions defined within the specifications. • Setting / instruction by at least one of the upper layer parameters, MAC CE, DCI, and (reported) UE capabilities.

[0172] Each embodiment / aspect / option / choice / modification / variation of this disclosure may be used individually or in combination.

[0173] <First Embodiment> The first embodiment relates to instructions for BAT.

[0174] The UE may refer to an RS whose TCI state is indicated as an RS with a specific QCL type (e.g., QCL type D) set for a particular signal (if applicable). The UE may apply such TCI state to the transmission and reception of one or more channels / signals.

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

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

[0177] The specific time resource in question may be at least one of the following options 1-0-1 through 1-0-3.

[0178] The specific time resource may be at least one of the first / last symbols of a PUCCH with a HARQ-ACK scheduled by a DCI (Beam Indicator DCI) that includes a TCI state indication, and the slot of that PUCCH (e.g., the first / last slot) (Option 1-0-1).

[0179] In this disclosure, a HARQ-ACK scheduled by a DCI may be interpreted as a HARQ-ACK associated with a DCI. Also in this disclosure, a beam-directing DCI may be in a DCI format with DL assignments or in a DCI format without DL assignments.

[0180] The specific time resource may be at least one of the first / last symbols of the PDCCH of the DCI (Beam Indicator DCI) that includes the TCI state indication, and the slots of the PDCCH (e.g., the first / last slots) (Option 1-0-2).

[0181] The specific time resource may be an indicated symbol / slot / subframe (option 1-0-3). The symbol / slot / subframe may be represented by at least one of the following: a symbol (index) in the slot, a slot index in the subframe, and a subframe index.

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

[0183] Figure 7 shows an example of the criteria for initiating BAT according to the first embodiment. In the example shown in Figure 7, the UE receives a beam instruction DCI. According to option 1-0-1 above, a specific period from the transmission of the HARQ-ACK associated with the DCI becomes the BAT. According to option 1-0-2 above, a specific period from the reception of the DCI becomes the BAT.

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

[0185] The following explains BAT.

[0186] The UE may decide to apply beam indication (and the TCI condition) 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 represented by a specific (e.g., X (where X is any integer)) symbol / slot / subframe, or by Y[ms] (where Y is any 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 predetermined in the specifications.

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

[0191] For example, the RRC parameter may be an RRC parameter that indicates whether the beam indication is enabled or disabled for multiple beam application times (BAT).

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

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

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

[0195] Figures 8A and 8B show an example of the application of TCI states related to option 1-1-1. As shown in Figure 8A, an association is established between the UE and the BAT (TCI state (joint DL / UL TCI state in the example in Figure 8A)).

[0196] The associations between TCI code points and TCI states described in each embodiment of this disclosure are merely examples, and the number of bits in the code point and the indicated TCI state are not limited to the examples shown. Furthermore, while the TCI states described within such associations are mainly explained using the joint DL / UL TCI state as an example, the TCI states included in such associations may also be separate DL / UL TCI states.

[0197] In the example shown in Figure 8B, if the TCI code point "000" is indicated to the UE using the beam indicator DCI, the UE determines that the BAT is BAT#1. Also, if the TCI code point "100" is indicated to the UE using the beam indicator DCI, the UE determines that the BAT is BAT#2.

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

[0199] The specific RRC parameter in question may be an RRC parameter that is not associated with (is independent of) a code point within DCI (e.g., a TCI code point).

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

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

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

[0203] Figures 9A and 9B show an example of the application of TCI states related to option 1-1-3. As shown in Figure 9A, an association is established between the UE and the BAT (TCI state (joint DL / UL TCI state in the example in Figure 9A)).

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

[0205] In this disclosure, the BAT instruction may be indicated by the BAT index (number) or by an index associated with the BAT. The association between the BAT-related index and the BAT value may be established by upper-layer signaling (RRC / MAC CE) or may be predefined in the specification.

[0206] The maximum number of code points in a TCI field (maxNrofcodepointsinTCI-StateField) may be a specific number. For example, if N is 1, the maximum number of code points 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 code points in the corresponding TCI field (maxNrofcodepointsinTCI-StateField) may be a second value (e.g., 4).

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

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

[0209] Figure 10 shows an example of the application of the TCI state related to option 1-1-4. In the example shown in Figure 10, the setting parameter for 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 represent one value from among several values ​​(in the example in Figure 10, n1, n2, n4, n8, or n16). Note that the multiple values ​​shown in the figure are merely examples and are not limited to these.

[0210] [Variation 1 of Option 1-1-4] For example, the specific RRC parameter mentioned above may be a parameter of QCL information ("QCL-Info") included in the TCI state setting parameter ("TCI-State"). 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 parameters of the QCL information ("QCL-Info") may be indicated by at least one of the parameters indicating a first QCL type ("qcl-Type1") and the parameters indicating a second QCL type ("qcl-Type2").

[0212] Figure 11 shows an example of the application of the TCI state according to Modification 1 of Option 1-1-4. In the example shown in Figure 11, the setting parameter of the TCI state ("TCI-State") includes the parameter of the QCL information ("QCL-Info"), and the parameter of the QCL information ("QCL-Info") 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 represent one value from among several values ​​(in the example in Figure 11, n1, n2, n4, n8, or n16). Note that the multiple values ​​shown in the figure are merely examples and are not limited to these.

[0213] This modification allows for the creation of independent (different) BATs that depend on different QCL types (e.g., QCL types A / B / C / D), providing greater flexibility in BAT configuration.

[0214] [Variation 2 of Option 1-1-4] In at least one of the above options 1-1-4 and the above modification 1, the UE may set / notify information regarding the correspondence (mapping) between the TCI status ID and the BAT ID.

[0215] The BAT ID may be a parameter used to identify the BAT value. The correspondence between the BAT ID and the BAT value may be defined in advance in the specifications, set / instructed to the UE using higher layer signaling (RRC / MAC CE) / DCI, or determined based on the reported UE capability information.

[0216] Information regarding the correspondence (mapping) between TCI status IDs and BAT IDs may also be information that associates TCI status IDs with BAT IDs. This information may be communicated to the UE using higher-layer signaling (RRC / MAC CE).

[0217] Figure 12 shows an example of TCI state application related to Modification 2 of Option 1-1-4. In the example shown in Figure 12, associations for N TCI state IDs and associations for M BATs are described. Information regarding each association and the correspondence (mapping) between TCI state IDs and BAT IDs is set for the UE. At this time, the UE determines the BAT for application of the TCI state based on these correspondences and the indicated TCI state (ID).

[0218] This modification eliminates the need to specify the BAT associated with each TCI state each time, and also reduces overhead by limiting the candidate values ​​for the BAT for each TCI state ID.

[0219] 《Option 1-1-5》 The specific period may be determined / set / indicated based on the parameters / fields specified in MAC CE.

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

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

[0222] The subheader of the MAC CE may include a new Logical Channel ID (LCID).

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

[0224] Figure 13 shows an example of the MAC CE configuration related to option 1-1-5-1. In the MAC CE shown in Figure 13, there is a field indicating the CORESET pool ID, a field indicating the serving cell ID, a field indicating the BWP ID, and a field indicating the activation / deactivation of TCI state i (T i (This is included in the description.)

[0225] The MAC CE shown in Figure 13 further includes a field indicating the BAT corresponding to each activated TCI code point. 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 in question may be an existing MAC CE (for example, one specified up to Rel. 15 / 16).

[0227] With respect to the MAC CE in question, the reserved bits included in existing MAC CEs (for example, those specified up to Rel. 15 / 16) may be used as fields indicating whether to interpret the MAC CE as having an activation field for a list of TCI states with a BAT (Time Offset).

[0228] The MAC CE in question may be a MAC CE in which new fields / octets are added to an existing MAC CE (for example, one specified up to Rel. 15 / 16).

[0229] Existing MAC CEs (e.g., those specified by Rel. 15 / 16) may be, for example, MAC CEs for UE-specific TCI states activation / deactivation for UE-specific PDSCH MAC CEs.

[0230] Figure 14 shows an example of the MAC CE configuration related to option 1-1-5-2. In the MAC CE shown in Figure 14, there is 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 (C) indicating whether or not TCI state IDi,2 exists in the corresponding octet. i ), and a reserved bit field (R, set to 0) may be included.

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

[0232] The MAC CE shown in Figure 14 also has a field (D) indicating the presence of an octet in the BAT corresponding to the i-th TCI state ID (i.e., TCI state IDi,1) i (as stated) and a field (E) indicating the existence of an octet in BAT corresponding to the second TCI state field corresponding to the i-th TCI state ID (i.e., TCI state IDi,2) i (as stated) and are included.

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

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

[0235] In the example shown in Figure 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 specific period may be determined / instructed based on specific fields included in the DCI.

[0237] With respect to the DCI, at least one of the following options 1-1-6-1 to 1-1-6-4 may be followed.

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

[0239] For the DCI in question, 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. This new DCI field may be a field that indicates BAT.

[0241] Furthermore, under certain conditions, existing fields in the DCI may be used / interpreted as fields to indicate the BAT.

[0242] The specific condition may be, for example, a condition in which at least one (all) of specific fields (e.g., at least one of FDRA field, TDRA field, MCS field, RV field, and NDI field) is 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 the DCI, the CRC of the DCI may be scrambled by a new RNTI defined after Rel.17.

[0245] For the DCI, a new DCI field may be included. The new DCI field may be a field indicating BAT.

[0246] Also, for the DCI, under specific conditions, an existing field may be used / interpreted as a field for indicating BAT.

[0247] The specific condition may be, for example, a condition in which at least one (all) of specific fields (e.g., at least one of FDRA field, TDRA field, MCS field, RV field, and NDI field) is 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 after Rel.17.

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

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

[0251] With respect to the DCI, the CRC attached to the DCI may be scrambled by a new RNTI as defined in Rel. 17 or later.

[0252] 《Option 1-1-7》 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 points in the TCI field do not map to the BAT, as shown in options 1-1-3 / 1-1-4 above, then options 1-1-1 / 1-1-2 above may be used.

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

[0255] Alternatively, for example, a BAT common to multiple (e.g., all) TCI code points and a differential BAT for some of those TCI code points may be set / instructed to the UE. The UE may determine the 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 the difference value (Difference BAT) associated with each specific number (e.g., N (where N is an integer greater than or equal to 1)) of TCI code points, and the Common BAT.

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

[0258] 《Option 1-2-2》 The UE may calculate / derive / determine the BAT based on the difference value associated with each TCI code point of a specific number (e.g., N (where N is an integer greater than or equal to 1)) and the BAT associated with a particular TCI code point.

[0259] For example, the UE may calculate / derive / determine BAT based on the BAT value associated with a particular TCI code point and the difference value associated with other TCI code points.

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

[0261] The particular TCI code point in question may, for example, be the TCI code point that corresponds to the index of the highest (or lowest) code point among the indices of lower (or higher) code points associated with different values.

[0262] The value of the differential BAT may be determined based on at least one method (optional) described in the first embodiment. Furthermore, the differential BAT may support both positive and negative values.

[0263] According to option 1-2-2, it is sufficient to set a difference value with a smaller bit width compared to option 1-2-1, thus reducing the overhead required for setting the BAT.

[0264] Figures 15A and 15B are diagrams showing an example of the application of the TCI state according to Option 1-2-1. In the example shown in Figures 15A and 15B, the UE receives beam indication DCI and applies the TCI state indicated by the DCI. <{

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

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

[0267] Figure 16 is a diagram showing an example of the application of the TCI state according to Option 1-2-2. In the example shown in Figure 16, the UE receives beam indication DCI and applies the TCI state indicated by the DCI. Note that in the example shown in Figure 16, in addition to Option 1-2-2, an example in which the above Option 1-2-1 is also applied is shown.

[0268] In the example shown in Figure 16, a common BAT is set / stipulated for the UE. Also, the correspondence relationship between the TCI code point, the TCI state, and the BAT is set for the UE.

[0269] In the example shown in Figure 16, if the UE is instructed to select the largest BAT (and its corresponding TCI code point) within the given correspondence, the UE determines that the BAT is the sum of the largest BAT (BAT#1 in the example in Figure 16) and the common BAT. If the UE is instructed to select a BAT other than the largest BAT (and its corresponding TCI code point), the UE determines that the BAT is the sum of the value of the largest BAT (BAT#1) and the other BAT (BAT#2 in the example in Figure 16).

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

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

[0272] The UE may determine the value of the time offset (BAT) based on the BAT (bit field) of 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 bitfield / BAT ID of a BAT and the value of the BAT may be set in the UE using upper-layer signaling (RRC signaling).

[0274] For example, the UE may set up multiple BAT values ​​(including associations) using RRC signaling. The UE may then determine one (or more) BAT values ​​from among these multiple BAT values.

[0275] If an association is established with a UE using RRC signaling that includes only one BAT value, the UE does not need to receive the quantized bits (bit field representing BAT) that indicate the BAT value.

[0276] Figure 17A shows an example of the association of BAT values ​​related to option 1-3-1. The UE may set up an association between a bit field (or BAT ID) and a BAT value as shown in Figure 17A and determine the BAT based on the indicated quantized bits (bit field indicating the BAT).

[0277] Note that the values ​​and field names within the correspondence shown in Figure 17A are merely examples and are not limited to them.

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

[0279] The specific rule / association may, for example, be defined in the specifications beforehand.

[0280] The UE may receive quantized bits (a bit field representing BAT) that indicate the BAT value based on the specific rule.

[0281] Figure 17B shows an example of the association of BAT values ​​related to option 1-3-2. The association between the bit field (or BAT ID) and the BAT value, as shown in Figure 17B, is predetermined / determined. The UE may determine the BAT based on this association and the indicated quantized bits (the bit field indicating the BAT).

[0282] Note that the values ​​and field names within the correspondence shown in Figure 17B are merely examples and are not limited to them.

[0283] According to options 1-3-1 and 1-3-2 above, BAT notifications can be properly delivered.

[0284] Modified form of the first embodiment For example, at least one option of this embodiment may be applied in the case where no BAT is associated with a code point in at least one TCI field. This modification is also applicable to the second embodiment described below.

[0285] For example, even when the UE performs operations that utilize multi-panel / multi-TRP / multi-cell, at least one option of this embodiment (e.g., option 1-2-1 / 1-2-2) may be applied to determine the BAT.

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

[0287] Additionally, the UE may be configured / instructed to set / create a differential BAT corresponding to information related to specific data.

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

[0289] According to the first embodiment described above, the determination, setting, and instruction of the BAT can be performed appropriately.

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

[0291] The UE may refer to multiple RSs indicated by the code points in the TCI field of the beam instruction in the first symbol / slot after a certain time resource has elapsed since the reception of the beam instruction DCI.

[0292] The UE may apply one or more TCI states indicated by the code point in the TCI field of the beam instruction in the first symbol / slot after a certain time resource has elapsed since the reception of the beam instruction DCI.

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

[0294] The specific time resource may be subject to at least one of the above options 1-0-1 to 1-0-3.

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

[0296] A single TCI state (common TCI state / joint (DL / UL) TCI state / separate (DL / UL) TCI state) may be mapped to a single BAT. In other words, if a single TCI code point indicates multiple TCI states, a BAT may be mapped to each of those TCI states.

[0297] This configuration allows a single DCI (TCI code point) to specify beam patterns (TCI states) and BATs across multiple time domains.

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

[0299] Furthermore, in this disclosure, beam pattern, TCI state pattern, sequence of TCI states, correspondence between multiple TCI states, and correspondence between multiple TCI states and BAT may be interpreted interchangeably. Also, in this disclosure, beam pattern may mean a correspondence for indicating multiple TCI states across multiple time domains using a single TCI code point.

[0300] Figures 18A and 18B show an example of the application of TCI states according to the second embodiment. In the example shown in Figure 18A, a correspondence relationship is set / defined for the UE between a TCI code point, a TCI state (first joint DL / UL TCI state and second joint DL / UL TCI state), and a BAT corresponding to the TCI state.

[0301] In the example shown in Figure 18B, the UE receives a TCI field indicating a code point of 000 using the beam indicator DCI. Based on this 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] Figure 19 shows another example of the application of TCI states according to the second embodiment. As shown in the example in Figure 19, the correspondence between TCI code points set in the UE, TCI states, and BATs corresponding to the TCI states may include at least one of joint DL / UL TCI states and separate DL / UL TCI states. Among the separate DL / UL TCI states, the DL TCI state and the UL TCI state may represent the same TCI state or different TCI states. In such examples as well, at least one method of the first embodiment described above may be applied.

[0303] The following section explains how to set up the correspondence between BAT and TCI status.

[0304] The UE may apply multiple TCI states (references to multiple RSs) indicated by a single TCI code point, in accordance with at least one of options 2-1-1 to 2-1-3 described below.

[0305] 《Option 2-1-1》 For the UE, a TCI state parameter ("TCI-State") containing multiple pieces of the same type of QCL information ("QCL-info") may be set using RRC.

[0306] Figure 20 shows an example of the TCI state parameters related to option 2-1-1. In the example shown in Figure 20, the RRC parameter ("TCI-State") includes the TCI state ID, multiple 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") and 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 that set the beam application time corresponding to the QCL information ("beamApptime", "SecondbeamApptime", and "ThirdbeamApptime"). "beamApptime" supports "qcl-Type1" and "qcl-Type2", "SecondbeamApptime" supports "Secondqcl-Type1" and "Secondqcl-Type2", and "ThirdbeamApptime" supports "Thirdqcl-Type1" and "Thirdqcl-Type2".

[0307] Note that while Figure 20 shows an example where each QCL information item has three entries, the number is not limited to this example and may be three or more. Also, the names of each parameter are merely examples and are not limited to this example.

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

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

[0310] Furthermore, the UE may determine the timing of application for a third TCI state among multiple TCI states indicated by a single TCI code point, 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 BAT based on these multiple beam application time parameters may follow at least one of the variations 2-1-1-1 to 2-1-1-4 described below.

[0312] [Variation 2-1-1-1] The UE may determine that the BAT set by the parameter ("beamApptime") which 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 the timing based on the common BAT.

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

[0314] Figure 21A shows an example of the application of the TCI state related to variation 2-1-1-1. In the example shown in Figure 21A, the UE determines that the BAT set by the parameter ("beamApptime") which 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] Furthermore, in the example shown in Figure 21A, the UE applies the second TCI state at the timing of the sum of the BAT (BAT#1 in Figure 21A) set by the parameter ("SecondbeamApptime") which 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 parameter that sets the beam application time corresponding to the mth (where m is a positive integer) type 1 / type 2 QCL information is the BAT for applying the mth TCI state.

[0317] Figure 21B shows an example of the application of the TCI state related to variation 2-1-1-2. In the example shown in Figure 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 (it may also be a common BAT), and applies the first TCI state.

[0318] Furthermore, in the example shown in Figure 21B, the UE determines that the BAT set by the parameter ("SecondbeamApptime") which 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 the parameter ("beamApptime") which 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 the 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 by a parameter that sets the beam application time corresponding to the nth (where n is an integer greater than or equal to 2) type 1 / type 2 QCL information, and a BAT set by a parameter that sets the beam application time corresponding to the (n-1)th 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 that set the beam application time corresponding to the nth type 1 / type 2 QCL information (e.g., "SecondbeamApptime" and "ThirdbeamApptime" mentioned above), but instead may include parameters that indicate the switching gap.

[0323] The parameter indicating the switching gap may also 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] Figure 22A shows an example of the application of the TCI state related to variation 2-1-1-3. In the example shown in Figure 22A, the UE determines that it is a common BAT set by the parameter ("beamApptime") which sets the beam application time corresponding to the first type 1 / type 2 QCL information, and applies the first TCI state.

[0325] Furthermore, in the example shown in Figure 22A, a parameter indicating the switching gap is set for the UE. Based on the timing indicated by the switching gap parameter (BAT#1 in Figure 22A), the UE determines the timing for applying the second TCI state and the third TCI state.

[0326] [Variation 2-1-1-4] The UE may determine that the BAT, set by a parameter that sets the beam application time corresponding to the first type 1 / type 2 QCL information (e.g., "beamApptime"), is a parameter that indicates the switching gap from the application timing of the (m-1)th 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 that set the beam application time corresponding to the mth type 1 / type 2 QCL information (e.g., "beamApptime", "SecondbeamApptime", "ThirdbeamApptime" above), but instead may include parameters that indicate the switching gap.

[0328] Figure 22B shows an example of the application of TCI states related to variation 2-1-1-4. In the example shown in Figure 22B, the UE determines the timing of application of the first / second / third TCI states based on the BAT (BAT#1 in Figure 22B), which is set by a parameter indicating the switching gap.

[0329] According to option 2-1-1-4, overhead can be reduced by consolidating the BAT for applying multiple TCI states into a single BAT.

[0330] 《Option 2-1-2》 QCL information ("QCL-info") containing information about multiple source RSs may be configured for the UE using RRC.

[0331] In option 2-1-2, the QCL information within the parameters of a single TCI state may include information about multiple source RSs. Therefore, the UE may receive an instruction for a single TCI code point (TCI state ID) and, based on the information about multiple source RSs contained in the indicated TCI state, determine which BAT to apply to multiple TCI states.

[0332] Information regarding multiple source RSs may include, 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 parameters indicating each reference signal may also indicate the index of the reference signal being referenced (e.g., CSI-RS / SSB).

[0334] Note that the number of pieces of information regarding the source RS is not limited to three, but can be any number. Also, the names of each parameter are merely examples and are not limited to these examples.

[0335] Figure 23 shows an example of the TCI state parameters related to option 2-1-2. In the example shown in Figure 23, the RRC parameter ("TCI-State") includes type 1 QCL information ("qcl-Type1"), type 2 QCL information ("qcl-Type2"), and a parameter for setting the beam application time ("beamApptime").

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

[0337] Note that Figure 23 shows an example where there are two parameters related to the reference signal in the QCL information, but the number is not limited to this example and may be three or more.

[0338] In the example shown in Figure 23, the UE determines the application of a first TCI state from among multiple TCI states indicated by a single TCI code point, based on information about the first source RS. The UE also determines the application of a second TCI state from among multiple TCI states indicated by a single TCI code point, based on information about the second source RS.

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

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

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

[0342] In option 2-1-2, the determination of BAT based on the parameter for setting the beam application time may be appropriately performed by applying 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 a MAC CE (Activation / Deactivation Command MAC CE) containing fields for multiple TCI states for multiple (different) BATs.

[0344] These multiple BATs may also be BATs corresponding to the application of each of the multiple TCI states associated with a single TCI code point.

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

[0346] [Option 2-1-3-1] The MAC CE may be a new MAC CE (specified after Rel.17).

[0347] In the sub-header of the MAC CE, a new Logical Channel ID (LCID) may be included.

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

[0349] The number of fields / octets included in the MAC CE may be set using RRC signaling or determined based on the reported UE capability information. The UE capability information may be defined, for example, by the maximum number of BATs related to one code point.

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

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

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

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

[0354] [Option 2-1-3-2] The MAC CE in question may be an existing MAC CE (for example, one specified up to Rel. 15 / 16).

[0355] With respect to the MAC CE in question, the reserved bits included in existing MAC CEs (for example, those specified up to Rel. 15 / 16) may be used as fields indicating whether to interpret the MAC CE as having an activation field for a list of TCI states with a BAT (Time Offset).

[0356] The MAC CE in question may be a MAC CE in which new fields / octets are added to an existing MAC CE (for example, one specified up to Rel. 15 / 16).

[0357] Existing MAC CEs (e.g., those specified by Rel. 15 / 16) may be, for example, MAC CEs for UE-specific TCI states activation / deactivation for UE-specific PDSCH MAC CEs.

[0358] Figure 25 shows an example of the MAC CE configuration related to option 2-1-3-2. In the MAC CE shown in Figure 25, there is a Serving Cell ID field, a BWP ID field, a field for indicating the TCI state identified by the 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) indicating whether or not TCI state IDi,2 exists in the corresponding octet. i ), and a reserved bit field (R, set to 0) may be included. Note that the field for indicating the TCI state corresponding to each BAT may mean the field for indicating the TCI state to be referenced after each BAT has elapsed.

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

[0360] The MAC CE shown in Figure 25 also has a field (D) indicating the existence of an octet corresponding to the first TCI state field of the i-th TCI state ID corresponding to BAT#Y (where Y is any integer) (i.e., TCI state IDi, 1). iY (as stated) and a field (E) indicating the existence of an octet corresponding to the second TCI state field of the i-th TCI state ID corresponding to BAT#Y (i.e., TCI state IDi,2). iY (as stated) and are included.

[0361] The above D iY When the field shows a first value (e.g., 0 (or 1)), the UE may determine that it contains a field for indicating the TCI state corresponding to IDi,1, which corresponds to BAT#Y. iY When the field indicates a second value (for example, 1 (or 0)), the UE may determine that there is no field to indicate the TCI state corresponding to IDi,1 corresponding to BAT#Y.

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

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

[0364] Note that while Figure 25 shows an example where there are two BATs, this number may be three or more. Furthermore, the MAC CE in Option 2-1-3-2 may include fields indicating each BAT corresponding to the TCI status ID (for example, BAT#1 / #2 in the example in Figure 25), as described in Option 1-1-5-2 of the first embodiment above.

[0365] According to options 2-1-1 to 2-1-3 above, even when multiple TCI states are associated with a single TCI code point, the TCI state / BAT settings can be configured appropriately.

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

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

[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, after a specific time resource determined based on at least one of the methods described in the first embodiment above, initiate a reference to the RS regarding the indicated TCI state based on the set / indicated BAT.

[0370] In other words, the UE may, after a specific time resource determined based on at least one of the methods described in the first embodiment above, initiate the application of a specified TCI state based on the set / specified BAT.

[0371] The BAT specified in the setting / instruction may indicate a period from that particular time resource.

[0372] Figures 26A and 26B show an example of the application of TCI states related to option 2-2-1. As shown in the example in Figure 26A, the UE establishes associations between a TCI code point, multiple TCI states (first TCI state / second TCI state), and a BAT corresponding to each TCI state.

[0373] In the example shown in Figure 26B, the UE receives a beam instruction DCI indicating the TCI code point "000". At this time, the UE determines that the application of the first TCI state (TCI#0) begins after BAT#1 has elapsed from 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) begins after BAT#2 has elapsed from the transmission of the HARQ-ACK associated with the beam instruction DCI.

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

[0375] In other words, the UE may, after a specific time resource determined based on at least one of the methods described in the first embodiment above, initiate the application of a specified TCI state based on the set / specified BAT.

[0376] The BAT specified in this setting / instruction may represent at least one of the period from the particular time resource and the period to be added (i.e., the differential BAT).

[0377] For example, the UE may determine that, among multiple TCI states and multiple BATs corresponding to a single TCI code point, the first TCI state will begin to be applied after the specified time resource and after the BAT corresponding to the first TCI state (the first BAT) has elapsed. In this case, the UE may also determine that the second TCI state will begin to be applied after the specified time resource, after the first BAT has elapsed, and further after the BAT corresponding to the second TCI state (the second BAT) has elapsed. Thus, the start of application for the nth TCI state may be determined based on the start timing of application for the (n-1)th TCI state and the indicated BAT.

[0378] Figures 27A and 27B show an example of the application of TCI states related to option 2-2-2. As shown in the example in Figure 27A, the UE establishes associations between a TCI code point, multiple TCI states (first TCI state / second TCI state), and a BAT corresponding to each TCI state.

[0379] In the example shown in Figure 27B, the UE receives a beam instruction DCI indicating the TCI code point "000". At this time, the UE determines that the application of the first TCI state (TCI#0) begins after BAT#1 has elapsed from 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) begins after BAT#2 has elapsed from the timing of the application of the first TCI state (after BAT#1 has elapsed from the transmission of the HARQ-ACK associated with the beam instruction DCI).

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

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

[0382] According to the second embodiment described above, even when multiple TCI states correspond to a single TCI code point, the application of the TCI state and the timing of such application can be appropriately determined.

[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 CE) corresponding to a specific number (e.g., up to X) combinations / pairs of TCI states.

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

[0386] In this disclosure, a combination of TCI states may correspond to a pair of TCI states indicated by a single TCI code point.

[0387] 《Aspect 3-2》 The UE may receive activation commands (MAC CE) corresponding to combinations of TCI states, which consist of a specific number (for example, up to X) of TCI states (pairs of TCI states) in total.

[0388] For example, the MAC CE may activate a total of up to eight TCI states (pairs of TCI states). By limiting the maximum number of 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 CE) corresponding to combinations / pairs of TCI states consisting of a certain number (e.g., up to X) of QCL information sources RS in total.

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

[0391] The value of 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] X may represent the maximum number of source RSs for a particular QCL type (e.g., QCL types A / B / C).

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

[0395] Note that while the example above shows X as 8, X may be a number greater than 8.

[0396] According to the third embodiment described above, the number of TCI states to activate for the UE can be appropriately determined.

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

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

[0399] Appearance 4-1 The UE does not need to expect or anticipate receiving instructions / activations / configurations that include a BAT value greater than the specified / determined maximum BAT value.

[0400] The UE may assume / expect not to receive instructions / activations / configurations that include 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 greater than the specified / determined maximum BAT, the UE may decide to use the specified / determined maximum BAT.

[0402] Appearance 4-2 The UE does not need to expect or anticipate receiving instructions / activations / configurations that include a BAT value smaller than the minimum BAT value specified / determined.

[0403] The UE may assume / expect not to receive instructions / activations / configurations that include a BAT value smaller than the minimum BAT value specified / determined.

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

[0405] According to the fourth embodiment described above, the maximum / minimum values ​​of the BAT and the operation of the UE related to the maximum / minimum values ​​can be appropriately performed.

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

[0407] 《Aspect 5-1》 After receiving a DCI / MAC CE indicating a TCI state, the UE does not need to expect or anticipate receiving a specific DCI / MAC CE.

[0408] The specific DCI / MAC CE may be a DCI / MAC CE that indicates a BAT (Beam Application Timing) at a timing earlier than the last BAT (Beam Application Timing) indicated using the received DCI / MAC CE.

[0409] Figure 28 shows an example of the application of the TCI state according to embodiment 5-1. In the example shown in Figure 28, the UE receives a beam instruction DCI#1 which instructs it to refer to RS#0 after BAT#0 has elapsed, and to refer to RS#1 after BAT#1 has elapsed.

[0410] In this disclosure, the referenced RS (referred RS) may be interpreted interchangeably with the source RS (reference RS) of the TCI state used at a given time.

[0411] Figure 28 shows beam indicator DCI#2, which indicates that RS#2 should be referenced after BAT#2 has elapsed. Beam indicator DCI#2 exists after the reception of beam indicator DCI#1, and BAT#2 indicates a timing prior to BAT#1 (i.e., the last BAT indicated by beam indicator DCI#1).

[0412] In such cases, the UE does not expect or anticipate receiving beam instruction DCI#2.

[0413] Figure 29 shows another example of the application of the TCI state according to embodiment 5-1. In the example shown in Figure 29, the UE receives beam instruction DCI#1 which instructs it to refer to RS#0 after BAT#0 has elapsed and to refer to RS#1 after BAT#1 has elapsed.

[0414] Figure 29 shows beam indicator DCI#2, which indicates that RS#2 should be referenced after BAT#2 has elapsed. Beam indicator DCI#2 exists after the reception of beam indicator DCI#1, and BAT#2 indicates a timing later than BAT#1 (i.e., the last BAT indicated by beam indicator DCI#1).

[0415] In such cases, the UE decides to follow the instructions of beam instruction DCI#2 and refer to RS#2.

[0416] 《Appearance 5-2》 After receiving a DCI / MAC CE indicating a TCI state, the UE may ignore some or all of the instructions from a particular DCI / MAC CE.

[0417] The specific DCI / MAC CE may be a DCI / MAC CE that indicates a BAT (Beam Application Timing) at a timing earlier than the last BAT (Beam Application Timing) indicated using the received DCI / MAC CE.

[0418] Regarding beam instruction DCI#2 as shown in Figure 28, the UE will ignore part or all of the instruction.

[0419] 《Aspect 5-3》 After receiving a DCI / MAC CE indicating a TCI state, the UE does not need to expect or anticipate receiving a specific DCI / MAC CE.

[0420] The particular DCI / MAC CE may indicate a different TCI state / RS than the one indicated for the TCI state / RS at a timing prior to the last BAT (Beam Application Timing) indicated using the received DCI / MAC CE.

[0421] Figure 30 shows an example of the application of the TCI state according to embodiment 5-3. In the example shown in Figure 30, the UE receives a beam instruction DCI#1 which instructs it to refer to RS#0 after BAT#0 has elapsed, and to refer to RS#1 after BAT#1 has elapsed.

[0422] Figure 30 shows beam instruction DCI#2, which indicates that RS#0 should be referenced during a specific period from after BAT#0 to before BAT#1, that RS#1 should be referenced during a specific period from after BAT#1 to after BAT#2, and that RS#2 should be referenced after BAT#2. The instructions for RS#0 and RS#1 provided by beam instruction DCI#2 include the same instructions as those provided by beam instruction DCI#1.

[0423] In such cases, the UE decides to follow the instructions of beam instruction DCI#2 and refer to RS#2 (and RS#0 / #1).

[0424] On the other hand, regarding beam indicator DCI#2 as shown in Figure 28 above, the UE does not expect or anticipate receiving this beam indicator DCI.

[0425] Appearance 5-4 After receiving a DCI / MAC CE indicating a TCI state, the UE may ignore some or all of the instructions from a particular DCI / MAC CE.

[0426] The particular DCI / MAC CE may indicate a different TCI state / RS than the one indicated for the TCI state / RS at a timing prior to the last BAT (Beam Application Timing) indicated using the received DCI / MAC CE.

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

[0428] 《Appearance 5-5》 Embodiment 5-5 describes the operation when a UE receives a specific DCI / MAC CE after receiving a DCI / MAC CE indicating a TCI state.

[0429] The DCI / MAC CE in question may be a DCI / MAC CE that indicates a different TCI state / RS than the one indicated for the TCI state / RS at a time prior to the last BAT (Beam Application (Start) Timing) indicated using the received DCI / MAC CE.

[0430] If a UE receives a DCI / MAC CE indicating a TCI state, and then receives a specific DCI / MAC CE, the UE may apply (or modify) the TCI state based on the instructions of the later-received DCI / MAC CE. In this case, the UE does not need to refer to the TCI state / source RS that will be applied at a specific time after the instructions 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] This specific timing may be a timing after a specific period (e.g., X symbol / slot / subframe / Y [ms]) has elapsed since the reception of the DCI / MAC CE (which will be received later).

[0433] Furthermore, this specific timing may also be the timing of the transmission of the HARQ-ACK related to the DCI / MAC CE (which will be received later).

[0434] Figure 31 shows an example of the application of the TCI state related to option 5-5-1. In the example shown in Figure 31, the UE receives beam instruction DCI#1 which instructs 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] Furthermore, in the example shown in Figure 31, the UE receives a beam instruction DCI#2 that instructs it to refer to RS#3 after BAT#3 has elapsed. BAT#3 is located between BAT#1 and BAT#2.

[0436] In the example shown in Figure 31, the UE does not follow the reference to RS by beam instruction DCI#1 (application of TCI state) after a certain timing (for example, after sending the HARQ-ACK associated with beam instruction DCI#2). In other words, the UE determines to refer to RS#0 (not to refer to RS#1) from after sending the HARQ-ACK associated with 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] That specific timing may also be the time resource (symbol) for the application / reference of the initial TCI state / RS, as indicated by the DCI / MAC CE (which will be received later).

[0438] Figure 32 shows an example of the application of the TCI state related to option 5-5-2. In the example shown in Figure 32, the UE receives beam instruction DCI#1 which instructs 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] Furthermore, in the example shown in Figure 32, the UE receives a beam instruction DCI#2 that instructs it to refer to RS#3 after BAT#3 has elapsed. BAT#3 is located between BAT#1 and BAT#2.

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

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

[0442] The specific period may be predetermined in the specifications, determined based on specific rules, determined based on upper layer signaling (RRC / MAC CE) / DCI, or determined based on reported UE capability information (e.g., capability information regarding the application time of QCL ("timedurationForQCL")). The specific period may be expressed in X symbol / slot / subframe / Y [ms].

[0443] According to the fifth embodiment described above, even when receiving multiple beam instructions, the application of the TCI state and the operation of referencing the source RS can be appropriately controlled.

[0444] <Other Embodiments> At least one of the embodiments described above may apply only to a UE that has reported or supports a particular UE capability.

[0445] The specific UE capability may represent (or be defined by) at least one of the following: • Capabilities regarding the operation / information related to each embodiment / appearance. • Capability regarding the operation / information related to each option / combination of options. • Ability to understand actions / information related to each option / combination of options. • The maximum number of TCI states associated with a single (supported) TCI code point. • The maximum number of source RSs with the same QCL type associated with one (supported) TCI code point. • The maximum number of TCI states that can be activated (and supported). • The maximum / minimum value of the supported BAT file.

[0446] The above UE capability may be defined, for example, by whether or not it supports at least one of the following: BAT determination (for AI-assisted beam prediction), BAT setting / instruction, beam pattern setting / activation / instruction (multiple TCI states), maximum number of TCI states (combinations / pairs) included in MAC CE, maximum / minimum BAT value, and behavior for receiving multiple beam instructions.

[0447] Furthermore, the above UE capability may be defined by the maximum supported N / M / n / m / X / Y value (as described in each embodiment).

[0448] The above 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 (SCS).

[0449] The above UE capabilities may be reported in common for both Time Division Duplex (TDD) and Frequency Division Duplex (FDD), or they may be reported independently.

[0450] Furthermore, at least one of the embodiments described above may apply when the UE is configured with specific information related to the embodiments described above through upper-layer signaling.

[0451] According to the other embodiments described above, 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 one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.

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

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

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

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

[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 the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may fall in a frequency band higher than FR2.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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, as DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc., may be transmitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0495] The transmitting / receiving unit 120 may transmit configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, and instructions for TCI states applied to the multiple types of channels. The control unit 110 may use information regarding the timing of the start of application of the TCI state included in the configuration information and the instructions to instruct the timing of the start of application of the TCI state (first embodiment).

[0496] The transmitting / receiving unit 120 may transmit configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, and an instruction for the TCI state. The code points of the TCI field included in the instruction may be associated with multiple TCI states. The control unit 110 may use information regarding the timing of the start of application of the TCI state included in the configuration information and the instruction to indicate the timing of the start of application of the TCI state (second embodiment).

[0497] The transmitting / receiving unit 120 may transmit at least one of the following: setting information including settings for transmission configuration indication (TCI) states applied to multiple types of channels; a first instruction regarding the TCI state; and a second instruction regarding the TCI state. The control unit 110 may use information regarding the timing of the start of application of the TCI state included in the setting information, the first instruction, and at least one of the second instruction to instruct the application of a first TCI state based on the first instruction and the application of a second TCI state based on the second instruction (fifth embodiment).

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

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

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

[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 transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0502] The transmitting / receiving unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

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

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

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

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

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

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

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

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

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

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

[0515] The transmitting / receiving unit 220 may receive configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, and instructions for TCI states applied to the multiple types of channels. The control unit 210 may determine the timing for the start of application of the TCI state based on information regarding the timing for the start of application of the TCI state included in the configuration information and the instructions (first embodiment).

[0516] The aforementioned configuration information may also be Radio Resource Control (RRC) parameters. The information regarding the timing of the application of the TCI state may be included in at least one of the configuration parameters for the physical downlink shared channel, the TCI state, and the pseudo-collocation configuration parameters (first embodiment).

[0517] The aforementioned configuration information may be a Medium Access Control element (MAC Control Element (CE)). The information regarding the timing of the application of the TCI state 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 transmitting / receiving unit 220 may receive configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, and an instruction for the TCI state. The code points of the TCI field included in the instruction may be associated with multiple TCI states. The control unit 210 may determine the timing for starting the application of the TCI state based on information regarding the timing for starting the application of the TCI state 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 aforementioned configuration information may be a Medium Access Control element (MAC Control Element (CE)). The MAC CE may activate TCI states included in up to a specific number of pairs or combinations of TCI states (third embodiment).

[0522] The control unit 210 does not need to anticipate the reception of at least one instruction for an application start timing greater than the maximum value for the application start timing, and an instruction for an application start timing less than the minimum value for the application start timing (fourth embodiment).

[0523] The transmitting / receiving unit 220 may receive at least one of the following: setting information including settings for transmission configuration indication (TCI) states applied to multiple types of channels; a first instruction regarding the TCI state; and a second instruction regarding the TCI state. The control unit 210 may determine, based on information regarding the timing of the start of application of the TCI state included in the setting information, and at least one of the first instruction and the second instruction, whether to apply a first TCI state based on the first instruction and whether to apply a second TCI state based on the second instruction (Fifth Embodiment).

[0524] The control unit 210 does not need to anticipate receiving the second instruction indicating an application start timing for the second TCI state that is earlier than a specific timing relating to the application start timing of the first TCI state, and it may ignore at least a portion of the second instruction indicating an application start timing for the second TCI state that is earlier than the specific timing (Fifth Embodiment).

[0525] The control unit 210 does not need to anticipate receiving the second instruction which instructs 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, nor does it need to ignore at least a portion of the second instruction which instructs the application of a TCI state other than the first TCI state during the period (Fifth Embodiment).

[0526] The control unit 210 may, after a certain period of time has elapsed since receiving the second instruction, decide 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 in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

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

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

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

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

[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 the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

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

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

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

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

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

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

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

[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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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 sends and receives data (information) via the communication port 63 to the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58 provided in the vehicle 40.

[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 external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10 or the user terminal 20 described above. Alternatively, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 (it may function as at least one of the base station 10 and the user terminal 20).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0604] The term "maximum transmit power" as used in this disclosure may mean the maximum value of the 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,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

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

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

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

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

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

Claims

1. A receiving unit that receives configuration information including settings for transmission configuration indication (TCI) states applied to multiple types of channels, a first instruction regarding the TCI state, and a second instruction regarding the TCI state, A terminal having a control unit that determines whether to apply a first TCI state based on the first instruction and an application of a second TCI state based on the second instruction, based on information regarding the timing of the start of application of the TCI state included in the setting information, and at least one of the first instruction and the second instruction, and predicts beam quality using AI based on the result of the determination.

2. The terminal according to claim 1, wherein the control unit does not anticipate receiving the second instruction indicating an application start timing for the second TCI state that is earlier than a specific timing relating to the application start timing of the first TCI state, or ignores at least a portion of the second instruction indicating an application start timing for the second TCI state that is earlier than the specific timing.

3. The terminal according to claim 1, wherein the control unit does not anticipate receiving a 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, or ignores at least a portion of the second instruction instructing the application of a TCI state other than the first TCI state during the period.

4. The terminal according to claim 1, wherein the control unit determines, 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.

5. A step of receiving configuration information including settings for transmission configuration indication (TCI) states applicable to multiple types of channels, a first instruction regarding the TCI state, and a second instruction regarding the TCI state, A step of determining whether to apply a first TCI state based on the first instruction and an application of a second TCI state based on the second instruction, based on information regarding the timing of the start of application of the TCI state included in the setting information, the first instruction and the second instruction, A wireless communication method for a terminal, comprising the step of predicting beam quality using AI based on the results of the aforementioned determination.

6. A transmission unit that transmits configuration information including settings for transmission configuration indication (TCI) states applicable to multiple types of channels, a first instruction regarding the TCI state, and a second instruction regarding the TCI state, A base station having a control unit that instructs the application of a first TCI state based on the first instruction and the application of a second TCI state based on the second instruction, using information regarding the timing of the start of application of the TCI state included in the setting information, and at least one of the first instruction and the second instruction.

Images