Terminal, wireless communication method, base station and system

Abstract

A terminal according to one aspect of the present disclosure comprises: a transmission unit that transmits a beam report based on an event related to at least one of a serving cell and an additional cell; and a control unit that determines whether to update a quasi-co-location (QCL) assumption on the basis of the beam report. According to one aspect of the present disclosure, it is possible to appropriately perform a beam report and application of a TCI state.

Description

Terminal, wireless communication method and base station

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

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

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

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

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

[0006] In addition, in Rel. 18 and later, the introduction of event-based beam reporting and reducing the latency required for switching / activating TCI states in the beam reporting are being considered.

[0007] However, there has been insufficient consideration of the beam reporting and methods for reducing the delay time, which may result in a decrease in communication quality and throughput.

[0008] Therefore, one of the objectives of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately perform beam reporting and apply TCI status.

[0009] A terminal according to one aspect of the present disclosure has a transmitting unit that transmits a beam report based on an event regarding at least one of a serving cell and an additional cell, and a control unit that determines an update of a Quasi-Co-Location (QCL) assumption based on the beam report.

[0010] According to one aspect of the present disclosure, beam reporting and TCI status application can be performed appropriately.

[0011] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of a DCI-based TCI state indication. Figure 3 is a diagram showing an example of a timeline for switching / activating TCI states defined up to Rel. 15 / 16. Figure 4 is a diagram showing an example of TCI states defined up to Rel. 16. Figure 5 is a flowchart showing an example of an event-triggered beam reporting process. Figure 6 is a diagram showing an example of a beam update according to embodiment 2-1. Figure 7 is a diagram showing an example of a beam update according to embodiment 2-2. Figures 8A and 8B are diagrams showing an example of a beam-known period according to a third embodiment. Figure 9 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 10 is a diagram showing an example of a base station configuration according to an embodiment. Figure 11 is a diagram showing an example of a user terminal configuration according to an embodiment. Figure 12 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. Figure 13 is a diagram showing an example of a vehicle according to an embodiment.

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

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

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

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

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

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

[0018] The QCL information as shown in the above QCL types A to D may be called a QCL property.

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

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

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

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

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

[0024] Furthermore, the RS that has a QCL relationship with the channel may be, for example, at least one of a synchronization signal block (SSB), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a tracking CSI-RS (also called a tracking reference signal (TRS)), and a QCL detection reference signal (also called a QRS).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0040] Support for N = M = 1 is being considered for Rel. 17. For example, it may be supported to indicate one common beam (e.g., a common beam) using RRC / MAC CE / DCI, and the common beam may be applied to multiple DL / UL channels / reference signals. Other cases may also be supported in Rel. 18 and later.

[0041] 1A and 1B illustrate an example of a unified TCI framework, where Fig. 1A illustrates an example of a joint DL / UL TCI state (e.g., Joint DL / UL TCI state), and Fig. 1B illustrates an example of a separate TCI state (e.g., Separate TCI (DL TCI state and UL TCI state)).

[0042] In the example of FIG. 1A , RRC parameters (information elements) configure multiple TCI states for both DL and UL. In this disclosure, the TCI states configured by the RRC parameters may be referred to as configured TCI states or configured TCI states (e.g., configured TCI states). The MAC CE may activate multiple TCI states from the configured TCI states. The DCI may indicate one of the activated TCI states. In this disclosure, the TCI state indicated by the DCI may be referred to as indicated TCI state or indicated TCI state (e.g., indicated TCI state).

[0043] The DCI may be a UL DCI (e.g., a DCI used to schedule a PUSCH) or a DL DCI (e.g., a DCI used to schedule a PDSCH). The indicated TCI state may apply to at least one (or all) of the UL / DL channels / RS. One DCI may indicate both a UL TCI and a DL TCI.

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

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

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

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

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

[0049] It is assumed that in Rel. 17 NR and later, the MAC CE / DCI supports beam activation / indication to a TCI state associated with a different physical cell identifier (PCI), and in Rel. 18 NR and later, the MAC CE / DCI supports indicating a serving cell change to a cell with a different PCI.

[0050] The method of setting / indicating the TCI state (e.g., joint DL / UL TCI state) in Fig. 1A and the method of setting / indicating the application of the TCI state (e.g., separate TCI state) in Fig. 1B may be switched between. Whether the joint DL / UL TCI state or the separate TCI state is applied may be configured by a base station to the UE by a higher layer parameter.

[0051] (TCI State Indication) The Rel. 17 unified TCI framework supports the following modes 1 to 3: [Mode 1] MAC CE based TCI state indication [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0052] A UE with a TCI state configured and activated with a Rel. 17 TCI State ID (e.g., tci-StateId_r17) receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for one CC, or receives DCI format 1_1 / 1_2 providing an indicated TCI state with the Rel. 17 TCI State ID for all CCs in the same CC list as the CC list configured by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). DCI format 1_1 / 1_2 may or may not be accompanied by a DL assignment if one is available.

[0053] If DCI format 1_1 / 1_2 does not carry a DL assignment, the UE can assume (verify) the following for that DCI: - the CS-RNTI is used to scramble the CRC for the DCI; - the values ​​of the following DCI fields (special fields) are set as follows: - the redundancy version (RV) field is all '1's; - the modulation and coding scheme (MCS) field is all '1's; - the new data indicator (NDI) field is 0; - the frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, or all '1's for FDRA type 1, or all '0's for Dynamic Switch (similar to PDCCH validation for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).

[0054] Note that the DCI in the above-mentioned mode 2 / mode 3 may be referred to as beam instruction DCI.

[0055] In Rel. 15 / 16, if a UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. A similar behavior is considered for the relationship between support for Rel. 17 TCI states and the interpretation of the TCI field. It is considered that if a UE is configured with Rel. 17 TCI states, the TCI field will always be present in DCI format 1_1 / 1_2, and if the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0056] In Rel. 15 / 16, whether or not a TCI field is present (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0057] The TCI field in DCI format 1_1 is 0-bit if the higher layer parameter tci-PresentInDCI is not enabled, and 3-bit otherwise. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following behavior: [Action] If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying that DCI format 1_1, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI is enabled for all CORESETs in the indicated BWP.

[0058] The TCI field in DCI format 1_2 is 0 bit if the higher layer parameter tci-PresentInDCI-1-2 is not set, otherwise it is 1, 2 or 3 bits determined by the higher layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates a BWP other than the active BWP, the UE shall follow the following actions. [Operation] If the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used for the PDCCH carrying that DCI format 1_2, the UE shall assume that tci-PresentInDCI is not enabled for all CORESETs in the indicated BWP; otherwise, the UE shall assume that tci-PresentInDCI-1-2 for all CORESETs in the indicated BWP is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used for the PDCCH carrying that DCI format 1_2.

[0059] 2A shows an example of a DCI-based joint DL / UL TCI status indication, in which a TCI status ID indicating the joint DL / UL TCI status is associated with a value of the TCI field for the joint DL / UL TCI status indication.

[0060] 2B shows an example of DCI-based separate DL / UL TCI status indication. At least one TCI status ID, indicating a DL-only TCI status or indicating a UL-only TCI status, is associated with a value of the TCI field for the separate DL / UL TCI status indication. In this example, TCI field values ​​000 to 001 are associated with only one TCI status ID for DL, TCI field values ​​010 to 011 are associated with only one TCI status ID for UL, and TCI field values ​​100 to 111 are associated with both one TCI status ID for DL ​​and one TCI status ID for UL.

[0061] (Indicated TCI State / Configured TCI State) For Rel. 17 TCI states, unified / common TCI state may mean the Rel. 17 TCI state indicated using (Rel. 17) DCI / MAC CE / RRC (indicated Rel. 17 TCI state).

[0062] In the present disclosure, the terms indicated Rel. 17 TCI state, indicated TCI state, unified / common TCI state, TCI state applicable to multiple types of signals (channels / RS), and TCI state for multiple types of signals (channels / RS) may be interpreted interchangeably.

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

[0064] Regarding the Rel. 17 TCI state, a TCI state other than the unified TCI state may refer to a Rel. 17 TCI state configured using (Rel. 17) MAC CE / RRC (configured Rel. 17 TCI state). In this disclosure, the terms configured Rel. 17 TCI state, configured TCI state, TCI state other than the unified TCI state, and TCI state applied to a specific type of signal (channel / RS) may be interpreted interchangeably.

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

[0066] (Channels / RSs to which the indicated TCI state applies) The indicated TCI state by the MAC CE / DCI may apply to the following channels / RSs:

[0067] [PDCCH] - If followUnifiedTCIState is configured for CORESET0, the indicated TCI state applies. Otherwise, the Rel. 15 specifications apply for that CORESET. That is, CORESET0 follows the TCI state activated by the MAC CE or is QCL'd with SSB. - For CORESETs with USS / CSS type 3 and index other than 0, the indicated TCI state always applies. - For CORESETs with index other than 0 and at least CSS type other than 3, if followUnifiedTCIState is configured, the indicated TCI state applies. Otherwise, the configured TCI state for that CORESET applies to that CORESET.

[0068] [PDSCH] - The indicated TCI state always applies to all UE-dedicated PDSCHs. - For non-UE-dedicated PDSCHs (PDSCHs scheduled by DCI in CSS), the indicated TCI state may apply if followUnifiedTCIState is set (for the CORESET of the PDCCH that schedules that PDSCH). Otherwise, the configured TCI state for that PDSCH applies to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state may depend on whether followUnifiedTCIState is set for the CORESET used to schedule that PDSCH.

[0069] [CSI-RS] For an A-CSI-RS for CSI acquisition or beam management, if followUnifiedTCIState is set (for CORESET of the PDCCH that triggers that A-CSI-RS), the indicated TCI state applies. For other CSI-RSs, the configured TCI state for that CSI-RS applies.

[0070] [PUCCH] - For all dedicated PUCCH resources, the indicated TCI state always applies.

[0071] [PUSCH] - For dynamic / configured grant PUSCH, the indication TCI state always applies.

[0072] [SRS] - When the SRS resource set for the A-SRS used for beam management and the A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow the unified TCI state, the indicated TCI state is applied. For other SRSs, the configured TCI state in the SRS resource set is applied.

[0073] TCI State Switching Rel. 15 / 16 specifies a delay time for switching the active TCI state for a UE configured with one or more TCI states in the serving cell.

[0074] Even if the UE measures / stores / holds the QCL characteristics, unless the UE makes an L1-RSRP report / beam report to the network (NW, for example, a base station), the NW cannot recognize whether the UE measures / stores / holds the QCL characteristics. For this reason, the UE measures and reports the beam / RS, and the UE and the NW need to have a common understanding of whether the TCI state is known or unknown.

[0075] In Rel. 16, a TCI state is known if the following conditions 0 to 5 are satisfied: (Condition 0): From the last transmission of RS resources used for reporting L1-RSRP measurements in the target TCI state until the switching of the active TCI state is completed, the RS resources for L1-RSRP measurements are RSs in the target TCI state or RSs that have a QCL relationship with the target TCI state. (Condition 1): A TCI state switch command is received within 1280 ms from the last transmission of RS resources for beam reporting or measurements. (Condition 2): The UE has transmitted at least one L1-RSRP report for the target TCI state before the TCI state switch command. (Condition 3): During the TCI state switching period, detection of the TCI state remains possible. (Condition 4): During the TCI state switching period, detection of the SSB associated with the TCI state remains possible. (Condition 5) The signal to noise ratio (SNR) in a TCI state is −3 dB or more.

[0076] The TCI state being unknown means that the TCI state is not known.

[0077] In addition, in the present disclosure, a known TCI state may be referred to as a "known TCI state," and an unknown TCI state may be referred to as an "unknown TCI state."

[0078] In the case where MAC CE is used for switching the TCI state (MAC-CE based TCI state switch), when the target TCI state (the TCI state to which switching is made) is a known TCI state, when the UE receives a physical downlink shared channel (PDSCH) including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot +TO k *(T first-SSB+T SSB-proc In the first slot after slot n+T, the UE receives the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot The PDCCH in the old (pre-switching) TCI state can be received until slot n+T. HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state that the UE applies is undefined (see Figure 3).

[0079] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. first-SSB T is the time from when the UE decodes the MAC CE command used to activate the TCI state until it transmits the first SSB. SSB-proc is 2 ms. k is 1 if the target TCI state is not included in the list of active TCI states for the PDSCH, otherwise it is 0. NR slot length indicates the length of the slot.

[0080] 4 is a diagram showing an example of the TCI state defined up to Rel. 16. As shown in FIG. 4, the TCI state of the PDCCH indicates the relationship between the QCL type A / D between the demodulation reference signal (DMRS) for the PDCCH and the TRS (or CSI-RS, TRS#1 in this case). Also, the TCI state of the TRS indicates the relationship between the QCL type C / D between the TRS and the SSB (SSB#1 in this case).

[0081] When MAC CE is used for TCI state switching and the target TCI state is unknown TCI state, if the UE receives a PDSCH containing a TCI state activation command in slot n, it will HARQ +3N subframe,μ slot +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ) / (NR slot length), the UE receives the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot Until then, the PDCCH in the old (pre-switching) TCI state can be received.

[0082] Here, TO uk is 1 for L1-RSRP measurements using CSI-RS or for switching of the TCI state in which a QCL type other than QCL type D is configured. uk is 0 for TCI state switching with at least QCL type D configured and for L1-RSRP measurements using SSB.

[0083] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.

[0084] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRPis 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.

[0085] Furthermore, in the case where downlink control information (DCI) is used for TCI state switching (DCI-based TCI state switch), if the target TCI state is a known TCI state, and if the higher layer parameter tci-PresentInDCI for CORESET scheduling PDSCH in slot n is set to enabled, the UE receives the PDSCH in the target TCI state of the serving cell where the TCI state switching occurred in the first slot after slot n+timeDurationForDCI, where timeDurationForDCI is the time required for receiving the PDCCH and applying spatial relationship / QCL information (spatial QCL information) to receiving the DCI for the PDSCH.

[0086] Furthermore, when RRC signaling is used for switching the TCI state (RRC based TCI state switch), if the target TCI state is a known TCI state, when the UE receives a PDSCH carrying an RRC activation command for the TCI state in slot n, the UE RRC_processing +TO k *(T first-SSB +T SSB-proc ))) / (NR slot length), the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred is received.

[0087] Here, T RRC_processing is the RRC processing delay. first-SSB is the time to the first SSB transmission after the UE RRC process. SSB-proc , T.O. kand (NR slot length) are the same as in the case of known TCI state in TCI state switching using MAC CE.

[0088] In addition, when RRC signaling is used for switching the TCI state (RRC based TCI state switch), if the target TCI state is an unknown TCI state, when the UE receives a PDSCH carrying an RRC activation command for the TCI state in slot n, the UE RRC_processing +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ))) / (NR slot length), the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred is received.

[0089] Here, T RRC_processing is the RRC processing delay. SSB-proc , T.O. uk and (NR slot length) are the same as in the case of unknown TCI state in TCI state switching using MAC CE.

[0090] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.

[0091] Rel. 17 defines a delay time for switching between unified TCI states.

[0092] For example, when an RRC parameter (DLorJoint-TCIState) related to the unified TCI state for the DL channel of the serving cell is configured for the UE, the specified delay time may be applied.

[0093] In MR-DC or standalone NR, this delay time also applies to all lists of multiple serving cells in simultaneous TCI update lists for multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).

[0094] If the target DL TCI state refers to an additional PCI that is different from the Physical Cell ID (PCI) of the serving cell for which this DL TCI state is configured, this delay may be applied provided that the following conditions are met: the active BWP of the serving cell and the cell of the additional PCI are the same, the center frequency, subcarrier spacing (SCS) and system frame number (SFN) offset of the cell of the additional PCI are the same as those of the serving cell, and the cell of the additional PCI is known to the UE.

[0095] Also, a cell of an additional PCI may be known if the following conditions are met: The UE has sent a valid L3 measurement report for the cell of the additional PCI in the last 5 seconds before the L1-RSRP measurement is configured. The timing offset between the serving cell and the cell of the additional PCI is within the CP of the corresponding SCS.

[0096] If this condition is not met, the cells of the additional PCI may be unknown.

[0097] A DL TCI state in a unified TCI state may be known if it satisfies the following conditions: - The RS resources for L1-RSRP measurements are the RSs of the target DL TCI state or the RSs that have a QCL relationship with the target DL TCI state from the last transmission of the RS resources used for reporting L1-RSRP measurements of the target DL TCI state until the switching of the active DL TCI state is completed. - A DL TCI state switch indication (downlink TCI state switch command) is received within 1280 ms from the last transmission of the RS resources for beam reporting or measurements. - The UE has sent at least one L1-RSRP report for the target DL TCI state before the DL TCI state switch indication. - Detection of the DL TCI state remains possible during the DL TCI state switching period. During the DL TCI state switching period, detection of the SSB associated with the DL TCI state remains possible. The Signal to Noise Ratio (SNR) in the DL TCI state is -3 dB or greater.

[0098] The SSB may be associated with the PCI of the serving cell or a PCI different from the serving cell PCI.

[0099] If the above conditions are not met, the DL TCI status may be unknown.

[0100] In the case of joint TCI state switching, if the target PL-RS is not maintained, the UE may not be expected to receive in the DL based on the target TCI state before completing the switch of DL and UL TCI states.

[0101] When MAC CE is used for switching the DL TCI state (MAC-CE based downlink TCI state switch), if the target TCI state (the TCI state to which switching is made) is a known TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc In the first slot after slot n+T, the UE receives the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot The UE can receive the UE-specific PDSCH / PDCCH using the old (pre-switching) TCI state until slot n+T. HARQ +3N subframe,μ slot From slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state that the UE applies is not specified.

[0102] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. first-SSB T is the time from when the UE decodes the MAC CE command used to activate the TCI state until it transmits the first SSB. SSB-proc is 2 ms. kis 1 if the target TCI state is not included in the list of active TCI states for the PDSCH, otherwise it is 0. NR slot length indicates the length of the slot.

[0103] When using MAC CE for DL ​​TCI state switching and the target TCI state is unknown TCI state, if the UE receives a PDSCH containing a TCI state activation command in slot n, it will HARQ +3N subframe,μ slot +T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ) / (NR slot length), the UE receives the PDCCH of the target TCI state of the serving cell where the TCI state switching occurred. HARQ +3N subframe,μ slot Until then, the UE can receive the UE-specific PDSCH / PDCCH using the old (pre-switching) TCI state.

[0104] Here, TO uk is 1 for L1-RSRP measurements using CSI-RS or for switching of the TCI state in which a QCL type other than QCL type D is configured. uk is 0 for TCI state switching with at least QCL type D configured and for L1-RSRP measurements using SSB.

[0105] Also, T first-SSB is the time from the L1-RSRP measurement to the first SSB transmission when switching the TCI state with at least QCL type D set. first-SSB is the time until the UE first transmits an SSB after decoding a MAC CE command used to activate a TCI state other than QCL type D.

[0106] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRP is 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.

[0107] Also, for example, when an RRC parameter related to the unified TCI state (DLorJoint-TCIState (when unifiedTCI-StateType indicates Joint) or UL-TCIState) is configured for the UE for the UL channel / signal of the serving cell, the specified delay time may be applied.

[0108] In MR-DC or standalone NR, this delay time also applies to all lists of multiple serving cells in simultaneous TCI update lists for multiple CCs / cells (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).

[0109] Regarding the UL TCI state (or the joint TCI state), the known / unknown status of the cell of the additional PCI and the known / unknown status of the UL TCI state are the same as those obtained by replacing the "DL TCI state" of the known / unknown status of the cell of the additional PCI and the TCI state for the above DL TCI state with "UL TCI state (or the joint TCI state)."

[0110] In the case of a joint TCI state switch, the UE may not be expected to transmit on the UL before the switch of DL and UL TCI states is complete.

[0111] When MAC CE is used for switching between separate UL TCI states and joint TCI states for UL channels / signals (MAC-CE based uplink TCI state switch), if the target TCI state (the TCI state to which the UE is switched) is a known TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot + NM * (T first-target-PL-RS +4*T target-PL-RS +2 ms) / (NR slot length), the UL signal in the target TCI state can be transmitted, where the UL channel / signal can be PUCCH, PUSCH, or semi-persistent / periodic / aperiodic SRS (when beamCorrespondenceWithoutUL-BeamSweeping is set to 1).

[0112] Also, when MAC CE is used for switching between separate UL TCI state and joint TCI state for UL channels / signals, and the target TCI state is unknown TCI state, when the UE receives a PDSCH including a TCI state activation command (TCI state indication) in slot n, the UE activates the TCI state in slot n+T. HARQ +3N subframe,μ slot + (T L1-RSRP +T first-target-PL-RS +4*T target-PL-RS +2 ms) / (NR slot length), a UL signal in the target TCI state can be transmitted.

[0113] Here, T HARQ indicates the timing from the transmission of a downlink data signal (for example, PDSCH) to the transmission of acknowledgement information (for example, HARQ-ACK information). subframe,μ slot represents the number of slots per subframe for the subcarrier setting μ. NR slot length indicates the length of the slot.

[0114] NM is 1 if the target PL-RS is maintained, and 0 otherwise.

[0115] T target-PL-RS is the time until the first path loss RS is transmitted after the L1-RSRP measurement when the target TCI state is unknown. target-PL-RS is the time to the first pathloss RS transmission after the MAC CE command is decoded by the UE when the target TCI state is known.

[0116] T target-PL-RS is the period of the target PL-RS, which is an SSB or NZP CSI-RS, if the PL-RS is associated with the serving cell. target-PL-RS is the period of the PL-RS that becomes the SSB when the PL-RS is associated with a PCI different from the serving cell.

[0117] Compared to when the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the TCI state switching L1-RSRP This requires additional time. L1-RSRP is the time associated with the received power measurement. L1-RSRP is 0 in frequency range (FR) 1 or in FR2 where QCL type D is not set. Otherwise, it is the time required to determine / refine the receive beam in FR2.

[0118] (Analysis) It is being considered that future wireless communication systems (Rel. 18 / 19 and later) will support event-based beam reporting, which may also be called event-triggered beam reporting, and may mean UE-initiated beam reporting.

[0119] However, there has been insufficient consideration given to the provisions for reporting such event-triggered beams.

[0120] Furthermore, if the beam report follows the delay time related to the application of the beam (TCI state) of the existing specifications described above (e.g., the delay time related to the beam report, the time required for beam instruction, and the time related to the known / unknown cell / TCI state), it is considered that the beam / TCI state cannot be quickly applied / updated.

[0121] In event-triggered beam reporting, beam reporting by the UE can reduce delay time, so there is a study being conducted to define the delay time differently from the existing specifications. However, this study is not sufficient.

[0122] If these considerations are not sufficient, it may not be possible to achieve communication with lower latency, which may result in suppression of improvements in communication quality / throughput.

[0123] Therefore, the present inventors came up with a method for solving these problems.

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

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

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

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

[0128] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., messages from the core network such as positioning protocol (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP)) messages), or a combination thereof.

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

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

[0131] In this disclosure, terms such as omit, drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

[0132] (Wireless communication method) In this disclosure, event-triggered beam reporting may simply be referred to as beam reporting / CSI reporting / L1 beam reporting.

[0133] Each embodiment of the present disclosure may be applied in at least one of the following Case 1 or Case 2: - [Case 1]: L1-RSRP / SINR beam report including serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam report including serving cell / additional PCI cells for Rel. 18 L1 / L2 mobility with L1 / L2 inter-cell mobility / intra-cell multi-TRP (M-TRP inter-cell) / cell switching). - [Case 2] L1-RSRP / SINR beam report including only serving cell PCI.

[0134] Event-triggered beam reporting may be supported, for example, for at least one of the following purposes: A: To reduce the overhead of L1 beam reporting. B: To reduce the activation delay of TCI states.

[0135] Regarding A, in order to avoid beam failure, in the current network (NW), the base station needs to frequently perform L1 beam reporting, which increases the overhead of UL resources. It is also considered that the PDCCH overhead for beam reporting increases. Therefore, it is considered that event-triggered beam reporting contributes to reducing the overhead of L1 beam reporting.

[0136] This B will be described in detail in the third embodiment below.

[0137] The UE may report measurement results (e.g., L1-RSRP / L1-SINR) to the NW (e.g., base station) when a specific event occurs (a specific condition is met / not met).

[0138] The particular event may be, for example, an event relating to at least one of the serving cell and the additional cell, or an event relating to a beam report including at least one of the PCI of the serving cell and the PCI of the additional cell.

[0139] <<Events for Case 1>> An example of an event for the above-mentioned Case 1 will be described. The event may mean, for example, an event related to a serving cell and an additional cell, or an event related to a beam report including the PCI of the serving cell and the PCI of the additional cell.

[0140] [Option 1] A beam report (e.g., an aperiodic CSI report) may be triggered by reusing one or more existing events of Radio Resource Management (RRM) (e.g., at least one of the following events A2 to A6 and I1). That is, when at least one of the following events A2 to A6 and I1 occurs (when the condition of the event is satisfied), both the RRM report and the CSI report may be triggered, and the UE may transmit both the RRM report and the CSI report.

[0141] In addition, in the present disclosure, the RRM report may be read interchangeably with the L3 measurement report.

[0142] 5 is a flowchart showing an example of a process for an event-triggered beam report. The UE determines whether an event (for example, at least one of the following events A2 to A6 and I1) has occurred (S1). If the result in S1 is YES, the UE transmits an aperiodic CSI report (and an RRM report) (S2). If the result is NO, the UE terminates the process for the first embodiment. The process in FIG. 5 may be repeatedly performed at predetermined intervals.

[0143] In the present disclosure, triggering an aperiodic CSI report and a UE transmitting an aperiodic CSI report may be interchangeable. A CSI report, an L1 beam report, and a beam report may be interchangeable.

[0144] In the following events A2 to A6, the measurement result may be at least one of RSRP (L1-RSRP / L3-RSRP), RSRQ, and SINR (RS-SINR). In the conditions of the following events A2 to A6, "bad" may mean "low" and "good" may mean "high". In the conditions of the following events A2 to A6, SpCell means a special cell and may mean at least one of a Primary Cell (PCell) and a Primary Secondary Cell (PSCell). In the following events A2 to A6 and I1, a parameter corresponding to hysteresis may be added / subtracted from the measurement result. Each threshold may be the same or different. A neighboring cell may be a non-serving cell.

[0145] Event A2: The measurement result of the serving cell is worse than the threshold. Event A3: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the measurement result of the SpCell (the measurement result plus an offset). Event A4: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the threshold. Event A5: The measurement result of the SpCell is worse than the first threshold, and the measurement result of the neighboring cell (the measurement result plus an offset) is better than the second threshold. Event A6: The measurement result of the neighboring cell (the measurement result plus an offset) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the measurement result plus an offset). Event I1: The interference measurement result is higher than the threshold.

[0146] Option 1 simplifies configuration because the trigger for RRM reporting can be reused as the trigger for beam reporting.

[0147] [Option 2] One or more new events (separate from the events for RRM reporting) may be defined to trigger aperiodic L1 beam reporting (CSI reporting). The events may be similar to the above-mentioned events A2 to A6 and I1 that also apply to triggering RRM reporting, but may differ from any of the events A2 to A6 and I1 (triggering RRM reporting) in at least one of the following options 2-1 to 2-4.

[0148] [Option 2-1] The thresholds may be different, i.e., events A2 to A6 and I1 may be used for L1 beam reporting (CSI reporting) using thresholds different from those for RRM reporting.

[0149] [Option 2-2] The event may be triggered based on the measurement result of the reference signal received power (L1-RSRP) at Layer 1. That is, the comparison may be based on L1-RSRP instead of L3-RSRP. Alternatively, a new filtered L1-RSRP may be applied, whose timescale (period of update / measurement) is between L1-RSRP and L3-RSRP (or the same as L1-RSRP or L3-RSRP). Alternatively, other metrics, such as L1-SINR, L3-RSRQ, etc., may be applied. For example, the following event A2' may be applied as a new event: Event A2': The L1-RSRP measurement result of the serving cell is worse than a threshold.

[0150] [Option 2-3] This may be based on a comparison of measurements at a single beam level, at multiple beam levels (combining independent measurements of multiple beams into a single value), or at a cell level. For example, the following events A4' or A4'' may apply: Event A4': Measurements of one beam from a neighboring cell are better than a threshold. Event A4'': A statistic (e.g., average, sum, etc.) of measurements of multiple beams (e.g., the best X beams) is better than a threshold. X may be fixed or configurable, e.g., by higher layer signaling.

[0151] [Option 2-4] The number of beams that satisfy a condition (e.g., any of events A2 to A6 and I1) may be considered. For example, if X beams satisfy event A4' (if the measurement results of X beams from neighbor cells are better than a threshold), the UE may report CSI.

[0152] Note that examples combining at least two of the above 2-1 to 2-4 may also be applied. For example, A4''' can be considered as an event combining 2-2 and 2-3. Also, A4'''' can be considered as an event combining 2-2, 2-3, and 2-4: Event A4''': The L1-RSRP measurement result of one beam from an adjacent cell is better than the threshold. Event A4''': The L1-RSRP of each of X beams from adjacent cells is better than the threshold.

[0153] According to option 2, CSI reporting can be performed at a higher speed than when using existing RRM reporting events using RRC.

[0154] [Option 3] Any combination of two or more events from Option 1 and Option 2 above may be used to trigger aperiodic L1 beam reporting (CSI reporting).

[0155] An existing event for RRM reporting may be combined with one or more events of option 2. For example, a CSI report may be triggered when both event A4 and new event A4''' occur.

[0156] Two or more events in option 2 may be combined. For example, a CSI report may be triggered if both event A2′ and new event A4′″ are met.

[0157] <<Event for Case 2>> A description will be given of an example of an event for the above-mentioned Case 2. The event may mean, for example, an event related to only the serving cell, or an event related to a beam report including only the PCI of the serving cell.

[0158] One or more new events (separate from the events for RRM reporting) may be defined to trigger aperiodic L1 beam reporting (CSI reporting). The event may be at least one of the following events B2 to B6 and K1: Event B2: The measurement result of the current beam is worse than a threshold. Event B3: The measurement result of another beam (the measurement result plus an offset) is better than the measurement result of the current beam (the measurement result plus an offset). Event B4: The measurement result of another beam (the measurement result plus an offset) is better than a threshold. Event B5: The measurement result of the current beam is worse than a first threshold, and the measurement result of another beam (the measurement result plus an offset) is better than a second threshold. Event B6: The measurement result of the current beam (the measurement result plus an offset) is worse than a threshold, and the measurement result of another beam (the measurement result plus an offset) is better than the measurement result of the current beam (the measurement result plus an offset). Event K1: The interference measurement is higher than the threshold.

[0159] Note that the names / codes of events in this disclosure (e.g., A2-A6, B2-B6, I1, K1, etc.) are merely examples and are not limited to these. For example, the name of an event for Case 2 may be the same as the name of the event (numbered) corresponding to Case 1.

[0160] For at least one of the events (events related to Case 1 / Case 2) in the present disclosure, a duration / counter during which the event (condition) is satisfied may be specified. The UE / NW may determine that the condition of each event is satisfied when at least one of the conditions of each of the above events satisfies a condition related to a specific duration / counter. For example, the UE may determine that the condition of the above event B3 is satisfied when the measurement result of another beam is better than the measurement result of the current beam in a 100 ms time window. Furthermore, for example, the UE may determine that the condition of the above event B3 is satisfied when the measurement result of another beam is better than the measurement result of the current beam 10 times per multiple samples.

[0161] The "current beam" may refer to, for example, an SSB / CSI-RS that is QCL-related (QCLed) with the PDCCH.

[0162] The PDCCH may be, for example, a PDCCH corresponding to a CORESET determined by a specific rule / higher layer parameter setting, for example, a CORESET of a specific (e.g., lowest / highest) CORESET ID.

[0163] The CSI-RS may be, for example, a periodic / semi-persistent / aperiodic CSI-RS, and the SSB / CSI-RS may be, for example, limited to a periodic CSI-RS / SSB.

[0164] Also, the "current beam" may be, for example, an indicated TCI state (joint / DL TCI state) in the current unified TCI state. Also, the "current beam" may be, for example, a QCL source RS related to the current indicated TCI state.

[0165] Furthermore, the "current beam" may be, for example, a beam / resource index (e.g., CRI / SSBRI) reported in a particular (e.g., latest) L1-RSRP / L1-SINR.

[0166] "Other beams" may be, for example, beams / SSB / CSI-RS / TCI states other than the "current beam."

[0167] A set of multiple beams (candidate beam set) may be configured for the UE, and the UE may select / decide on an "other beam" from the set.

[0168] "Worse / better" may mean lower / higher measurement results (e.g., RSRP / SINR / RSRQ).

[0169] The threshold may be predefined in the specification, configured / indicated / signaled using higher layer signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or a combination thereof. For example, the threshold may be reused from an existing threshold (e.g., a threshold used in RRM / Case 1).

[0170] The offset with respect to the threshold may be predefined in the specification, configured / indicated / signaled using higher layer signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or a combination thereof.

[0171] First Embodiment The first embodiment relates to event-triggered beam reporting.

[0172] The first embodiment is broadly divided into the following embodiments 1-1 to 1-5. The UE / NW may conform to any one of embodiments 1-1 to 1-5, or may conform to a combination of at least two of embodiments 1-1 to 1-5.

[0173] <<Embodiment 1-1>> An event-triggered beam report may be transmitted using specific information / signaling.

[0174] For example, the event-triggered beam report may be transmitted using a MAC CE.

[0175] At least one of a new (for Rel. 18 / 19 and later) LCID (Logical Channel ID) and a new (for Rel. 18 / 19 and later) MAC CE may be defined / specified for event-triggered beam reporting.

[0176] An existing (e.g., defined up to Rel. 17) MAC CE (e.g., a MAC CE for BFR) may be utilized as a MAC CE for event-triggered beam reporting.

[0177] In this case, a new field may be added to the existing MAC CE. The new field may indicate, for example, that the MAC CE is a MAC CE for event-triggered beam reporting. The new field may indicate, for example, that a beamforming report (BFR) has not occurred. The new field may have a specific number of bits (for example, 1 bit).

[0178] In this case, a specific field (e.g., a reserved bit field) included in the existing MAC CE may be reinterpreted and used. For example, the field may indicate that the MAC CE is a MAC CE for event-triggered beam reporting. For example, the field may indicate that a BFR has not occurred. The field may have a specific number of bits (e.g., 1 bit).

[0179] Specific UL resources may be configured for the UE for event-triggered beam reporting.

[0180] The UL resource may be, for example, a (dedicated) PUCCH resource for a scheduling request (SR) (PUCCH-SR resource (SR setting)).

[0181] The UL resource may be, for example, at least one of another / existing PUCCH-SR resource (SR configuration) and a PRACH. For example, the UE may use the UL resource to request an UL grant from the NW. For example, the UE may use the UL resource when the specific PUCCH-SR resource is not configured.

[0182] By using a unique PUCCH-SR resource, the network can recognize when a situation occurs in which a beam report is required in the UE, and can allocate PUCCH resources to that UE on a priority basis, enabling flexible communication.

[0183] In addition, using other / existing PUCCH-SR resources can simplify UE implementation.

[0184] <<Embodiment 1-2>> An event-triggered beam report may be transmitted using specific information / signaling.

[0185] For example, the event-triggered beam report may be transmitted using UCI.

[0186] The UE may be configured with event-triggered beam reporting in advance.

[0187] The UE may transmit a beam report (UCI including a beam report) on an UL channel (e.g., PUSCH / PUCCH) when an event occurs.

[0188] The UE may omit transmitting a beam report using UCI on an UL channel (e.g., PUSCH / PUCCH) if no event occurs.

[0189] In the first and second embodiments, in order to avoid blind detection of UCI bits of different sizes in the base station, the base station and the UE need to have the same understanding of the number of UCI bits. Therefore, the UE may transmit only the event-triggered beam report using the UCI (PUCCH / PUSCH). In other words, the UCI for the beam report may include only the beam report.

[0190] With this configuration, the base station only needs to determine whether or not PUCCH has been transmitted, and blind detection of UCI bits of different sizes can be avoided.

[0191] The UCI for event-triggered beam reporting may not be multiplexed with other UCI (e.g., HARQ-ACK / SR).

[0192] The UCI for the event-triggered beam report may be transmitted only on the PUCCH. For example, the UCI for the event-triggered beam report may not be transmitted on the PUSCH (it may not be piggybacked on the PUSCH).

[0193] If a UE is instructed to transmit other UCI / PUSCH in a certain time resource (e.g., slot / subslot / symbol), it may not expect / assume to transmit UCI for event-triggered beam reporting in that time resource.

[0194] Furthermore, when the UE multiplexes the UCI for the event triggered beam report with other UCI (when the UCI for the event triggered beam report and other UCI are transmitted in the same time resource), the UE may assume / determine that the number of bits of the UCI for the event triggered beam report is a predetermined number of bits. Note that the predetermined number of bits may be specified in a specification, configured by a higher layer, or reported in UE capability information.

[0195] Furthermore, when a UE is instructed to transmit a UCI for an event-triggered beam report and another UCI in the same slot / subslot (e.g., when instructed to multiplex both UCIs), the UE may transmit the UCI, assuming / determining that a predetermined number of bits of UCI for the event-triggered beam report will be multiplexed, regardless of whether or not there is a UCI for the event-triggered beam report. The predetermined number of bits may be specified in the specifications, configured by a higher layer, or reported in the UE capability information. This makes the number of UCI bits after UCI multiplexing constant regardless of whether or not there is a UCI for the event-triggered beam report, thereby avoiding blind detection of the number of UCI bits on the base station side. When there is no UCI for the event-triggered beam report, the predetermined length of bits multiplexed as the UCI for the event-triggered beam report may include predetermined bits (e.g., all 0s).

[0196] For example, the UE may perform padding to make the UCI for the event-triggered beam report have the specific number of bits. The UE may assume that the UCI for the event-triggered beam report has a larger number of bits than other UCIs.

[0197] According to embodiments 1-1 / 1-2, event-triggered beam reporting can be performed appropriately using specific information / signaling.

[0198] <<Embodiment 1-3>> In embodiments 1-3 to 1-5, information included in an event-triggered beam report will be described.

[0199] The event-triggered beam report may include information indicating at least one of the following: Serving cell index, BWP index, Beam / Reference signal (e.g., SSB / CSI-RS) index, Measurement results (e.g., L1-RSRP / L1-SINR).

[0200] <<Embodiment 1-4>> The number of reported beams / RSs included in the event-triggered beam report may be a specific number.

[0201] The specific number may be, for example, 1 or N (N is an integer equal to or greater than 1).

[0202] The specific number may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported as a UE capability.

[0203] When multiple beams / RSs are reported, multiple sets of beam / RS indices (e.g., CRI / SSBRI) and measurement results (e.g., L1-RSRP / L1-SINR) may be reported.

[0204] The values ​​of the measurement results (e.g., L1-RSRP / L1-SINR) included in the event-triggered beam report may be expressed as absolute values, for example, and may be represented by the first bit (e.g., 7 bits) for each beam / RS.

[0205] The values ​​of the measurement results (e.g., L1-RSRP / L1-SINR) included in the event-triggered beam report may be indicated, for example, in absolute and relative values.

[0206] In this case, for example, the measurement results corresponding to the best beam / RS may be expressed as absolute values, and the measurement results corresponding to the other beams / RS may be expressed as relative values.

[0207] The absolute value may be represented by a first number of bits (e.g., 7 bits). The relative value may be represented by, for example, a difference from the absolute value. The relative value may be represented by, for example, a second number of bits (e.g., 4 bits).

[0208] Embodiment 1-5 An event-triggered beam report may include information indicating at least one of the following: PCI (or re-indexed PCI); Panel ID (UE capability value set); Resource set indicator; Event indication; Parameters related to beam update.

[0209] For example, the information indicating the PCI may always be included in the event-triggered beam report. Also, the information indicating the PCI may be included in the event-triggered beam report when, for example, an L1 / L2 beam report including an additional PCI is configured.

[0210] Information indicating the resource set indicator may be included in the event-triggered beam report, for example, if group based beam reporting is configured / supported.

[0211] Information regarding the event indication may be included in the event-triggered beam report, for example, when multiple events are configured for the UE.

[0212] The parameter for beam update may be, for example, a parameter / indicator indicating whether the UE will (autonomously) update the beam / TCI state / QCL assumptions after reporting.

[0213] According to embodiments 1-3 / 1-4 / 1-5, the configuration of event-triggered beam reporting can be appropriately specified.

[0214] According to the first embodiment described above, event-triggered beam reporting can be appropriately defined.

[0215] Second Embodiment The second embodiment relates to operations after transmission of an event-triggered beam report.

[0216] After sending the event-triggered beam report, the UE may update / change / adapt the beam (QCL assumption / TCI state / spatial relationship) based on a specific method.

[0217] The second embodiment is roughly divided into the following embodiments 2-1 and 2-2. The UE / NW may follow either embodiment 2-1 or 2-2, or a combination of embodiments 2-1 and 2-2.

[0218] <<Embodiment 2-1>> Operations based on existing specifications (for example, Rel. 15-17) may be used to update / change / apply TCI state / QCL assumptions.

[0219] It may be up to the NW (base station) to instruct a new beam (beam update) based on the event-triggered beam report. For example, the NW (base station) may instruct a new beam based on the event-triggered beam report. The UE may update / change the instructed beam (QCL assumption / TCI state / spatial relationship) based on the instruction.

[0220] In this case, the UE may receive a response (e.g., an acknowledgement (ACK) or a negative acknowledgement (NACK)) to the beam report from the NW (base station). In this manner, the UE can distinguish between whether the NW (base station) fails to receive the beam report and whether the NW (base station) ignores a beam report that it has received successfully.

[0221] If the UE does not receive a positive response to the beam report within a first period after the beam report, or if the UE receives a negative response to the beam report in the first period, the UE may retransmit the beam report after the first period ends, or may transmit a new beam report different from the beam report that was transmitted. The retransmission of the beam report may be performed up to a certain number of times.

[0222] The first period and the specific number of times may be specified in advance in a specification, may be configured / instructed / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported by UE capability information.

[0223] A response to the beam report may be transmitted, for example, using a specific DL signal (e.g., DCI).

[0224] 6 is a diagram showing an example of beam updating according to embodiment 2-1. In the example shown in FIG. 6, the UE sends an event-triggered beam report to the NW (base station) (step S601). The NW determines whether or not a beam update is necessary (presence or absence) based on the beam report (step S602). Next, the NW instructs the UE to perform a beam update (new beam) (step S603). The UE performs a beam update based on the instruction (step S604).

[0225] According to embodiment 2-1, the implementation of the UE can be simplified and beam updating can be performed appropriately.

[0226] <<Embodiment 2-2>> The UE may update / change / apply the beam (QCL assumption / TCI state / spatial relationship) based on the event-triggered beam report.

[0227] This differs from embodiment 2-1 in that the updating / changing / applying does not require instructions from the NW (base station).

[0228] The UE may update / change / apply the beam (QCL assumption / TCI state / spatial relationship) after a certain period of time has elapsed after sending the event-triggered beam report, which may be the beam corresponding to the best beam / RS included in the beam report.

[0229] By performing autonomous beam updates by the UE, faster beam updates can be achieved.

[0230] 7 is a diagram showing an example of a beam update according to embodiment 2-2. In the example shown in FIG. 7, the UE sends an event-triggered beam report to the NW (base station) (step S701). Then, after a specific period has elapsed since the beam report, the UE (autonomously) performs a beam update based on the beam report (step S702).

[0231] The specific period may be defined in advance in a specification, may be configured / instructed / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported by the UE capability information.

[0232] The specific period may be indicated, for example, in a specific time unit (eg, X ms / symbol / slot / subslot).

[0233] The UE may receive a response (e.g., an acknowledgement (ACK) or a negative acknowledgement (NACK)) to the beam report from the NW (base station). In this way, mismatch of recognition between the UE and the base station can be avoided.

[0234] If the UE does not receive a positive response to the beam report within a first period after the beam report, or if the UE receives a negative response to the beam report in the first period, the UE may retransmit the beam report after the first period ends, or may transmit a new beam report different from the beam report that was transmitted. The retransmission of the beam report may be performed up to a certain number of times.

[0235] The first period and the specific number of times may be specified in advance in a specification, may be configured / instructed / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported by UE capability information.

[0236] A response to the beam report may be transmitted, for example, using DCI.

[0237] For example, when a beam report is made using a MAC CE, a response to the beam report may be transmitted using a DCI format having the same HARQ process number as the initial PUSH (transmitting the MAC CE) and having a toggled value for the New Data Indicator (NDI) field.

[0238] When a UE performs a beam report for multiple beams / RSs, a response to the beam report may indicate any of the multiple beams / RSs. This configuration allows for more flexible beam updating.

[0239] For example, if a UE reports measurement results for N beams / RSs, the response to the beam report may include N bits of information indicating any one of the multiple beams / RSs.

[0240] For example, when a UE reports measurement results for N beams / RSs, the UE may receive one bit of information indicating a response to the beam report. In this case, the UE may determine to update / change to the best beam among the N beams / RSs.

[0241] If the reported beam report includes parameters related to beam updating (parameters / indicators indicating whether to (autonomously) update the beam / TCI state / QCL assumptions), the UE may expect / assume to receive an ACK (or NACK) from the NW.

[0242] The UE may update / change / apply the beam (QCL assumption / TCI state / spatial relationship) after a certain period of time has elapsed after receiving the beam report (or after transmitting the beam report).

[0243] The specific period may be defined in advance in a specification, may be configured / instructed / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported by the UE capability information.

[0244] The specific period may be indicated, for example, in a specific time unit (eg, X ms / symbol / slot / subslot).

[0245] According to embodiment 2-2, more flexible, faster, and more accurate beam updating can be performed.

[0246] According to the second embodiment described above, beam updating can be performed appropriately.

[0247] Third Embodiment The third embodiment relates to the activation delay of the TCI state.

[0248] (Analysis) As mentioned above, when the activated TCI state is known, the time associated with the received power measurement or the time required for the determination / refinement of the receive beam (e.g., T L1-RSRP ) can be omitted / reduced.

[0249] Also, if the UE has already performed measurements on the root SSB (QCL source (SSB / CSI-RS) related to the QCL source (TRS / CSI-RS) in the TCI state), the time required to measure the SSB (for example, TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) can be omitted / reduced (TO k= 0).

[0250] When a UE reports L1-RSRP using event-triggered beam reporting, it means that the UE has already measured the beam / RS. Therefore, since at least the reported beam / RS is known, the time associated with the received power measurement or the time required for the determination / refinement of the received beam (e.g., T L1-RSRP ) can be omitted / reduced.

[0251] Furthermore, if the UE can measure the root SSB (e.g., SSB / CSI-RS) associated with the reported beam, the UE can estimate the time it takes to measure the SSB (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) can be omitted / reduced (TO k = 0).

[0252] The following describes UE / NW operations based on the above.

[0253] The third embodiment is roughly divided into the following embodiments 3-1 and 3-2. The UE / NW may follow either embodiment 3-1 or 3-2, or a combination of embodiments 3-1 and 3-2.

[0254] The time required to measure SSB (for example, TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) may be based on a period starting from the indication of TCI state activation (reception of MAC CE of TCI activation command). Specifically, the time required for SSB measurement may be a period for measuring SSB a predetermined number of times (e.g., twice) from the indication of TCI state activation (start / end symbols).

[0255] In addition, the time required to measure SSB (for example, TO k *(T first-SSB +T SSB-proc) / (NR slot length)) may be based on a period starting from a specific timing. Specifically, the time required for SSB measurement may be a period for measuring SSB a predetermined number of times (e.g., twice) starting from a specific timing.

[0256] The specific timing may be the transmission timing of an event-triggered beam report (e.g., start / end symbol) or the measurement timing of SSB / CSI-RS immediately before the beam report (e.g., start / end symbol). This allows the measurement of SSB to be started before the activation instruction of the TCI state, compared to the case where the SSB is measured after receiving the activation instruction of the TCI state later, so that the time required for the measurement of SSB (e.g., TO k *(T first-SSB +T SSB-proc The time from the event-triggered beam report to the completion of SSB measurement can be shortened without shortening (NR slot length).

[0257] <<Embodiment 3-1>> The UE may report L1-RSRP using an event-triggered beam report.

[0258] Based on the event-triggered beam report, the UE / NW (base station) may assume / determine that the reported beam (beam / RS corresponding to the reported L1-RSRP) is known.

[0259] After sending / receiving an event-triggered beam report, the UE / NW (base station) may assume / determine that the reported beam (beam / RS corresponding to the reported L1-RSRP) is known.

[0260] The UE / NW (base station) may assume / determine that the reported beam (beam / RS corresponding to the reported L1-RSRP) is known for a certain period of time after the reporting of the event-triggered beam report.

[0261] The specific period may start from a specific (e.g., first / last) symbol of the PUSCH / PUCCH of the beam report. Also, the specific period may start from a specific (e.g., first / last) symbol of the response (e.g., ACK / NACK) to the beam report.

[0262] The specific period may be defined in advance in a specification, may be configured / instructed / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported by the UE capability information.

[0263] A response to the beam report may be transmitted, for example, by DCI.

[0264] The DCI may include information regarding the length of the particular period.

[0265] For example, when a beam report is made using a MAC CE, a response to the beam report may be transmitted using a DCI format having the same HARQ process number as the initial PUSH (transmitting the MAC CE) and having a toggled value for the New Data Indicator (NDI) field.

[0266] 8A is a diagram showing an example of a period during which a beam is known according to the third embodiment. In the example shown in FIG. 8A, the UE assumes that the reported beam is known for a specific period from the end symbol of the event-triggered beam report.

[0267] 8B is a diagram showing another example of a period during which a beam is known according to the third embodiment. In the example shown in FIG. 8B, the UE assumes that the reported beam is known for a specific period from the end symbol of the response (ACK) to the event-triggered beam report.

[0268] According to embodiment 3-1, by performing beam reporting, the time related to the received power measurement or the time required for determining / refinement of the received beam (for example, T L1-RSRP ) can be omitted / reduced.

[0269] <<Embodiment 3-2>> The UE may report L1-RSRP using an event-triggered beam report.

[0270] The UE may measure a specific reference signal (SSB / CSI-RS) associated with the reported beam.

[0271] The particular SSB / CSI-RS may be, for example, a root SSB. In this disclosure, the root SSB may refer to a QCL source (e.g., SSB / CSI-RS) related to a QCL source (e.g., TRS / CSI-RS) in the TCI state.

[0272] The switching / activation delay of the TCI is the time it takes to measure the SSB (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slot length)).

[0273] When an active (activated) TCI state is reported in the beam report (when the active TCI state is the TCI state corresponding to the beam / RS reported in the beam report), the UE / NW (base station) measures the time required for SSB measurement (for example, TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) may be assumed to be 0 (TO k = 0. Otherwise, the UE / NW (base station) determines the time required to measure the SSB based on the existing method (defined up to Rel. 17) (for example, TO k ) may be assumed / determined to be determined.

[0274] For the serving cell or additional cell (cell of additional PCI), a formula (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) and at least one of the known / unknown based parameters for activation delay may be different.

[0275] Furthermore, for an additional cell (e.g., intra-CU or inter-CU), a parameter indicating an additional processing time may be added to the existing activation delay (defined up to Rel. 17). The additional processing time may be based on a cell-specific configuration (configured by RRC) or may be predefined in a specification.

[0276] Parameters related to the time required to measure SSB (e.g., TO k The value of TO may be determined / reported based on event-triggered beam reporting and / or UE capability reporting. k The value of 0 or 1 may be determined / reported based on at least one of an event-triggered beam report and a UE capability report. In this way, the operation can be made dependent on whether the UE can start measuring the root SSB.

[0277] Parameters related to the time required to measure SSB (e.g., TO k The value of TO may be reported using a specific number of bits (e.g., 1 bit) for multiple (e.g., all) reported beams. k Whether the value of may be 0 or 1 may be reported using a specific number of bits (e.g., 1 bit) for multiple (e.g., all) reported beams.

[0278] Parameters related to the time required to measure SSB (e.g., TO k The value of TO may be reported using a specific number of bits for each reported beam (e.g., N bits for N beams). k Whether the value of may be 0 or 1 may be reported using a specific number of bits for each reported beam (e.g., N bits for N beams).

[0279] According to embodiment 3-2, by measuring the root SSB, the time required for measuring the SSB can be omitted / reduced.

[0280] The above embodiment 3-1 may be supported by all UEs, whereas the above embodiment 3-2 may be supported only by specific UEs.

[0281] According to the above third embodiment, the activation delay of the TCI state related to the event-triggered beam report can be appropriately specified.

[0282] <Supplementary Information> [Notification of Information to UE] In the above-described embodiments, any information may be notified to the UE (from a network (NW) (e.g., a base station (BS))) (in other words, reception of any information from the BS by the UE) using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PDCCH, PDSCH, reference signal), or a combination thereof.

[0283] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new Logical Channel ID (LCID) in the MAC subheader, which is not defined in existing standards.

[0284] When the notification is made by DCI, the notification may be made by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0285] Furthermore, notification of any information to the UE in the above embodiments may be performed periodically, semi-persistently, or aperiodically.

[0286] [Notification of Information from UE] In the above-described embodiments, notification of any information from the UE (to the NW) (in other words, transmission / report of any information from the UE to the BS) may be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), a specific signal / channel (e.g., PUCCH, PUSCH, PRACH, reference signal), or a combination thereof.

[0287] When the notification is performed by a MAC CE, the MAC CE may be identified by including a new LCID, which is not defined in existing standards, in the MAC subheader.

[0288] If the notification is made by UCI, the notification may be transmitted using PUCCH or PUSCH.

[0289] Furthermore, any information in the above-described embodiments may be notified from the UE periodically, semi-persistently, or aperiodically.

[0290] [Application of Each Embodiment] At least one of the above-described embodiments may be applied when a specific condition is met. The specific condition may be defined in a standard or may be notified to a UE / BS using higher layer signaling / physical layer signaling.

[0291] At least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0292] The particular UE capability may indicate support for particular processing / operation / control / information for at least one of the above embodiments (e.g., at least one of event-triggered beam reporting, measurement of root SSB).

[0293] Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (e.g., one or a combination of a cell, a band, a band combination, a BWP, a component carrier, etc.), or may be a capability for each frequency range (e.g., Frequency Range 1 (FR1), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or may be a capability for each subcarrier spacing (SubCarrier Spacing (SCS)), or may be a capability for each Feature Set (FS) or Feature Set Per Component-carrier (FSPC).

[0294] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0295] Furthermore, at least one of the above-described embodiments may be applied when the UE configures / activates / triggers specific information related to the above-described embodiments (or performs the operations of the above-described embodiments) through higher layer signaling / physical layer signaling. For example, the specific information may be information indicating that event-triggered beam reporting is enabled, any RRC parameter for a specific release (e.g., Rel. 18 / 19), etc.

[0296] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may apply, for example, the behavior of Rel. 15 / 16 / 17.

[0297] Each embodiment of the present disclosure may be applied to any of the following: reporting only L1-RSRP, reporting only L1-SINR, and reporting both L1-RSRP and L1-SINR.

[0298] Each embodiment of the present disclosure may be applied to only the TCI state / spatial relationships defined in Rel. 15, only the unified TCI states defined in Rel. 17, or both the TCI state / spatial relationships defined in Rel. 15 and the unified TCI states defined in Rel. 17.

[0299] Each embodiment of the present disclosure may be applied to only group-based beam reporting, only non-group-based beam reporting, or both group-based beam reporting and non-group-based beam reporting.

[0300] Each embodiment of the present disclosure may be applied to either only L1 beam reporting of the serving cell, only L1 beam reporting of the additional cell, or both L1 beam reporting of the serving cell and L1 beam reporting of the additional cell.

[0301] (Supplementary Note A) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note A-1] A terminal having: a transmitter that transmits a beam report based on an event related to at least one of a serving cell and an additional cell; and a controller that determines, based on the beam report, to update a Quasi-Co-Location (QCL) assumption. [Supplementary Note A-2] The terminal according to Supplementary Note A-1, wherein the beam report is transmitted using a Medium Access Control control element or uplink control information. [Supplementary Note A-3] The terminal according to Supplementary Note A-1 or Supplementary Note A-2, wherein the controller updates the QCL assumption after a first period has elapsed since the transmission of the beam report. [Supplementary Note A-4] The terminal according to any one of Supplements A-1 to A-3, wherein the controller controls reception of downlink control information including a response to the beam report, and the controller updates the QCL assumption after a second period has elapsed since the reception of the downlink control information.

[0302] (Supplementary Note B) The following inventions are added to one embodiment of the present disclosure. [Supplementary Note B-1] A terminal having: a transmitter that transmits a beam report based on an event related to at least one of a serving cell and an additional cell; and a controller that, based on the beam report, assumes that a reported beam is known after transmission of the beam report. [Supplementary Note B-2] The terminal according to Supplementary Note B-1, wherein the controller assumes that the reported beam is known during a first period starting after transmission of the beam report. [Supplementary Note B-3] The terminal according to Supplementary Note B-1 or Supplementary Note B-2, wherein the controller controls reception of downlink control information including a response to the beam report, and the controller assumes that the reported beam is known during a second period starting from reception of the downlink control information. [Supplementary Note B-4] The terminal according to any of Supplements B-1 to B-3, wherein the controller performs measurements of a specific reference signal associated with a beam included in the beam report.

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

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

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

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

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

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

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

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

[0311] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

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

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

[0314] The core network 30 may include network functions (Network Functions (NF)) such as a User Plane Function (UPF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), a Unified Data Management (UDM), an Application Function (AF), a Data Network (DN), a Location Management Function (LMF), and Operation, Administration and Maintenance (Management) (OAM). A single network node may provide multiple functions. Communication with an external network (e.g., the Internet) may also be performed via the DN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0347] The transceiver 120 may receive an event-based beam report for at least one of the serving cell and the additional cell, and the controller 110 may determine an update of a quasi-co-location (QCL) assumption based on the beam report (first / second embodiment).

[0348] The transceiver 120 may receive an event-based beam report for at least one of the serving cell and the additional cell. The controller 110 may determine, based on the beam report, that the reported beam is known after transmitting the beam report (first / third embodiments).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0365] The measurement unit 223 may derive channel measurements for CSI calculation based on the channel measurement resources. The channel measurement resources may be, for example, non-zero power (NZP) CSI-RS resources. The measurement unit 223 may also derive interference measurements for CSI calculation based on the interference measurement resources. The interference measurement resources may be at least one of an NZP CSI-RS resource for interference measurement, a CSI-Interference Measurement (IM) resource, etc. Note that CSI-IM may be referred to as CSI-Interference Management (IM) or may be interchangeably read as Zero Power (ZP) CSI-RS. Note that in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeably read as interchangeable.

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

[0367] The transceiver 220 may transmit an event-based beam report for at least one of the serving cell and the additional cell. The controller 210 may determine an update of a Quasi-Co-Location (QCL) assumption based on the beam report (first / second embodiment).

[0368] The beam report may be transmitted using a Medium Access Control control element or uplink control information (first embodiment).

[0369] The control unit 210 may update the QCL assumption after a first period has elapsed since the transmission of the beam report (second embodiment).

[0370] The control unit 210 may control the reception of downlink control information including a response to the beam report, and may update the QCL assumption after a second period has elapsed since the reception of the downlink control information (second embodiment).

[0371] The transceiver 220 may transmit an event-based beam report for at least one of the serving cell and the additional cell. Based on the beam report, the controller 210 may assume that the reported beam is known after transmitting the beam report (first / third embodiments).

[0372] The control unit 210 may assume that the reported beam is known during a first period starting after the transmission of the beam report (third embodiment).

[0373] The control unit 210 may control the reception of downlink control information including a response to the beam report, and may assume that the reported beam is known during a second period starting from the reception of the downlink control information (third embodiment).

[0374] The control unit 210 may perform measurements of a specific reference signal (e.g., root SSB) associated with the beam included in the beam report (third embodiment).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0421] 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," "layer," "number of layers," "rank," "resource," "resource set," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," "UE panel," "transmitting entity," "receiving entity," etc. may be used interchangeably.

[0422] In the present disclosure, the term "antenna port" may be interchangeably read as an antenna port for any signal / channel (e.g., a demodulation reference signal (DMRS) port). In the present disclosure, the term "resource" may be interchangeably read as a resource for any signal / channel (e.g., a reference signal resource, an SRS resource, etc.). The resource may include time / frequency / code / space / power resources. Furthermore, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0423] The group may include, for example, at least one of a spatial relationship group, a Code Division Multiplexing (CDM) group, a Reference Signal (RS) group, a Control Resource Set (CORESET) group, a PUCCH group, an antenna port group (e.g., a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, and the like.

[0424] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. may be read as interchangeable terms.

[0425] In addition, in the present disclosure, the terms TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, joint TCI state, etc. may be read interchangeably.

[0426] Furthermore, in the present disclosure, terms such as "QCL," "QCL assumption," "QCL relationship," "QCL type information," "QCL property / properties," "specific QCL type (e.g., Type A, Type D) property," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

[0427] In the present disclosure, terms such as index, identifier (ID), indicator, indication, and resource ID may be interchangeable. In the present disclosure, terms such as sequence, list, set, group, cluster, and subset may be interchangeable.

[0428] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information (TCI state)" may be interchangeable with "set of spatial relationship information (TCI state)", "one or more pieces of spatial relationship information", etc. The TCI state and the TCI may be interchangeable. The spatial relationship information and the spatial relationship may be interchangeable.

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

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

[0431] In the present disclosure, a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control / operate based on the information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0458] Furthermore, "determination" may be considered to be "determining" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "determining" some kind of action. In the present disclosure, "determination" may be read interchangeably with the above-mentioned actions.

[0459] Furthermore, in this disclosure, "determine / determining" may be interchangeably read as "assume / assuming," "expect / expecting," "consider / considering," etc. Furthermore, in this disclosure, "does not expect to do..." may be interchangeably read as "assumes not to do...."

[0460] In the present disclosure, "expect" may be interchangeably read as "be expected." For example, "expect(s) ..." ("..." may be expressed, for example, as a that clause, a to-infinitive, etc.) may be interchangeably read as "be expected ...." "does not expect ..." may be interchangeably read as "be not expected ...." Furthermore, "An apparatus A is not expected ..." may be interchangeably read as "an apparatus B other than apparatus A does not expect ... from apparatus A" (e.g., if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

[0467] In the present disclosure, terms such as "less than or equal to," "less than," "greater than," "more than," "equal to," etc. may be interchangeable. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative. Furthermore, in the present disclosure, terms meaning "good," "bad," "big," "small," "high," "low," "fast," "slow," "wide," "narrow," etc. may be interchangeable, not limited to the positive, comparative, and superlative, as expressions with "i-th" (i is an arbitrary integer) attached (for example, "highest" may be interchangeable with "i-th highest").

[0468] In this disclosure, the terms "of," "for," "regarding," "related to," "associated with," etc. may be read interchangeably.

[0469] In the present disclosure, terms such as "when A, B," "if A, (then) B," "B upon A," "B in response to A," "B based on A," "B during / while A," "B before A," "B at (the same time as) / on A," "B after A," "B since A," and "B until A" may be interchangeable. Note that A, B, and the like herein may be replaced with appropriate expressions such as nouns, gerunds, and regular sentences, depending on the context. Note that the time difference between A and B may be approximately zero (immediately after or immediately before). A time offset may also be applied to the time at which A occurs. For example, "A" may be interchangeable with "before / after a time offset at which A occurs." The time offset (eg, one or more symbols / slots) may be predefined or may be specified by the UE based on signaled information.

[0470] In the present disclosure, timing, time, duration, time instance, any time unit (e.g., slot, subslot, symbol, subframe), period, occasion, resource, etc. may be read interchangeably.

[0471] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The description of the present disclosure is for illustrative purposes only and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A control unit that determines whether to transmit a channel state information (CSI) report based on an event based on whether a measurement result of a reference signal different from the reference signal related to an indication Transmission Configuration Indication (TCI) state is higher than a value obtained by adding a specific value to the measurement result of the reference signal, and based on a period and a counter related to the event; a transmitter that transmits the CSI report using an uplink (UL) channel when determining to transmit the CSI report.

2. The terminal according to claim 1 , wherein the control unit controls the CSI report to include a specific number of reference signal indexes and measurement results set by Radio Resource Control (RRC) signaling.

3. A terminal as described in claim 2, wherein, when the specific number is multiple, the control unit controls the CSI report to include multiple sets of the reference signal index and the measurement results.

4. A step of determining whether to transmit a channel state information (CSI) report based on an indication Transmission Configuration Indication (TCI) state based on whether a measurement result of a reference signal different from the reference signal is higher than a value obtained by adding a specific value to the measurement result of the reference signal, and based on a period and a counter related to the event; If it is determined to transmit the CSI report, transmitting the CSI report using an uplink (UL) channel.

5. A transmitter that transmits a setting for a channel state information (CSI) report based on an event, the setting being transmitted by a terminal based on whether a measurement result of a reference signal different from the reference signal for an indication Transmission Configuration Indication (TCI) state is higher than a value obtained by adding a specific value to the measurement result of the reference signal, and a period and a counter related to the event. a receiving unit for receiving the CSI report.

6. A system having a terminal and a base station, The terminal includes a control unit that determines whether to transmit a channel state information (CSI) report based on an event based on whether a measurement result of a reference signal different from the reference signal is higher than a value obtained by adding a specific value to the measurement result of the reference signal related to an indication Transmission Configuration Indication (TCI) state, and based on a period and a counter related to the event; a transmitter that transmits the CSI report using an uplink (UL) channel when determining to transmit the CSI report; The base station includes: a transmitter that transmits the CSI report configuration; a receiver for receiving the CSI report.