Terminal, wireless communication method, and base station

By sending beam reports in the terminal and assuming known beams for TCI state application, the problem of insufficient beam report research is solved, the communication quality and throughput are improved, the TCI state switching delay is reduced, and the performance of the wireless communication system is optimized.

CN120677656APending Publication Date: 2025-09-19NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380094615.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-02-24
Publication Date
2025-09-19

AI Technical Summary

Technical Problem

In future wireless communication systems, insufficient research on beam reporting will lead to reduced communication quality and throughput, and existing technologies cannot effectively reduce the delay time of TCI state switching.

Method used

Provided are a terminal and a wireless communication method for optimizing the switching process of beam reporting and TCI state by sending beam reports and applying TCI state based on the reported beam assumption as a known beam.

Benefits of technology

Appropriate beam reporting and TCI status application are implemented, which improves communication quality and throughput and reduces the delay time of TCI state switching.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120677656A_ABST
    Figure CN120677656A_ABST
Patent Text Reader

Abstract

A terminal according to one embodiment of the present disclosure is provided with: a transmission unit that transmits a beam report on the basis of an event relating to at least one of a serving cell and an additional cell; and a control unit that, on the basis of the beam report, assumes that the beam to be reported is known after the transmission of the beam report. According to one embodiment of the present disclosure, beam reporting and TCI state application can be appropriately performed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been standardized to achieve even higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Releases 10-14) has been standardized to further enhance the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP (registered trademark)) Releases 8 and 9).

[0003] Research is also underway on successor systems to LTE (e.g., also referred to as the fifth-generation mobile communication system (5G), 5G+ (plus), the sixth-generation mobile communication system (6G), New Radio (NR), and 3GPP Rel. 15 and later).

[0004] Prior art literature

[0005] Non-patent literature

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

[0007] Problems to be solved by the invention

[0008] In future wireless communication systems (e.g., NR), research is underway to control transmission and reception processing in user terminals (UEs) based on information related to Quasi-Co-Location (QCL) (QCL assumptions, Transmission Configuration Indication (TCI) status, and spatial relationships).

[0009] In addition, after Rel.18, the introduction of event-based beam reporting and the reduction of the delay time required for switching / activating the TCI status in the beam reporting are being studied.

[0010] However, research on beam reporting and methods for reducing delay time are insufficient, and if this research is insufficient, there is a risk of degradation in communication quality and throughput.

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

[0012] Means for solving problems

[0013] A terminal involved in one embodiment of the present disclosure comprises: a sending unit that sends 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, based on the beam report, assumes that the reported beam is known after the beam report is sent.

[0014] Effects of the Invention

[0015] According to one embodiment of the present disclosure, beam reporting and TCI status can be appropriately applied. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1A as well as Figure 1B An example of a unified / common TCI framework is shown.

[0017] Figure 2A as well as Figure 2B An example of TCI status indication based on DCI is shown.

[0018] Figure 3 This is a diagram showing an example of a timeline for switching / activation of TCI states specified up to Rel.15 / 16.

[0019] Figure 4 This is a diagram showing an example of TCI states specified up to Rel. 16.

[0020] Figure 5 This is a flowchart showing an example of the processing of event-triggered beam reporting.

[0021] Figure 6 This is a diagram showing an example of beam updating according to embodiment 2-1.

[0022] Figure 7 This is a diagram showing an example of beam updating according to embodiment 2-2.

[0023] Figure 8A as well as Figure 8B This is a diagram showing an example of a known period of a beam according to the third embodiment.

[0024] Figure 9 This is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.

[0025] Figure 10 This is a diagram showing an example of the configuration of a base station according to one embodiment.

[0026] Figure 11 This is a diagram showing an example of the configuration of a user terminal according to an embodiment.

[0027] Figure 12 This is a diagram showing an example of the hardware configuration of a base station and a user terminal according to one embodiment.

[0028] Figure 13 This is a diagram showing an example of a vehicle according to an embodiment. DETAILED DESCRIPTION

[0029] (TCI, spatial relation, QCL)

[0030] In NR, research is underway 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 coding) of at least one of a signal and a channel (expressed as signal / channel) in the UE based on the transmission configuration indication state (TCI state).

[0031] The TCI state may also indicate the state of a signal / channel applied to a downlink. A state equivalent to the TCI state applied to a signal / channel applied to an uplink may also be expressed as a spatial relation.

[0032] The TCI status refers to information related to Quasi-Co-Location (QCL) of signals / channels and can also be referred to as spatial reception parameters or spatial relation information. The TCI status can also be set for the UE on a per-channel or per-signal basis.

[0033] QCL is an indicator of the statistical properties of a signal / channel. For example, it can mean that when a signal / channel is in a QCL relationship with other signals / channels, it can be assumed that at least one of the Doppler shift, Doppler spread, average delay, delay spread, and spatial parameters (e.g., spatial Rx parameters) is the same among these different signals / channels (at least one of these is QCL).

[0034] In addition, the spatial reception parameter may also correspond to the UE's receive beam (eg, receive analog beam), and the beam may also be determined based on spatial QCL. The QCL (or at least one element of QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0035] Multiple QCL types (QCL types) may be specified. For example, four QCL types AD may be provided. These four QCL types AD may have different parameters (or parameter sets) that can be assumed to be the same. These parameters (also referred to as QCL parameters) are expressed as follows:

[0036] QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread,

[0037] QCL type B (QCL-B): Doppler shift and Doppler spread,

[0038] QCL Type C (QCL-C): Doppler shift and average delay,

[0039] QCL type D (QCL-D): spatial reception parameters.

[0040] The information about the QCL types A to D described above may also be referred to as QCL properties.

[0041] The situation where the UE assumes that a certain Control Resource Set (CORESET), channel or reference signal is in a specific QCL relationship (for example, QCL type D) with other CORESETs, channels or reference signals may also be called QCL assumption.

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

[0043] The TCI status may also include, for example, information related to the quality of contact (QCL) between the target channel (in other words, the reference signal (RS) used for that channel) and other signals (for example, other RSs). The TCI status may also be set (indicated) via higher-layer signaling, physical-layer signaling, or a combination thereof.

[0044] The physical layer signaling may be, for example, downlink control information (Downlink Control Information (DCI))).

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

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

[0047] The SSB is a signal block that includes at least one of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a broadcast channel (physical broadcast channel (PBCH)). The SSB may also be referred to as an SS / PBCH block.

[0048] The RS of QCL type X in the TCI state may also mean an RS that is in a QCL type X relationship with a certain channel / signal (DMRS), and the RS may also be called a QCL source of QCL type X in the TCI state.

[0049] (Unified / common TCI framework)

[0050] The unified TCI framework enables control of multiple (UL / DL) channels and RSs using a common framework. Unlike Rel. 15, which specifies TCI states and spatial relationships for each channel, the unified TCI framework allows for the designation of a common beam (common TCI state) and its application to all UL and DL channels, or for the application of a common beam for UL to all UL channels and a common beam for DL ​​to all DL channels.

[0051] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams overall) are under study.

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

[0053] MAC CE-based beam management (MAC CE-level beam indication) can also be used to align the default UL and DL beams. The default PDSCH TCI state can also be updated to match the default UL beam (spatial relationship).

[0054] DCI-based beam management (DCI-level beam indication) can also indicate a common beam / unified TCI state from the same TCI pool (joint common TCI pool, joint TCI pool, or set) for both UL and DL. X (>1) TCI states can also be activated via a MAC CE. The UL / DL DCI can also select one of the X activated TCI states. The selected TCI state can also be applied to both UL and DL channels / RSs.

[0055] A TCI pool (set) can be multiple TCI states configured via RRC parameters, or multiple TCI states (activated TCI state, activated TCI pool, set) activated via MAC CE within the multiple TCI states configured via RRC parameters. Each TCI state can also be a QCL-type A / D RS. SSB, CSI-RS, or SRS can also be configured as a QCL-type A / D RS.

[0056] The number of TCI states corresponding to each of one or more TRPs may also 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 also be specified. At least one of N and M may be notified, configured, or indicated to the UE via higher layer signaling or physical layer signaling.

[0057] In this disclosure, the expression N=M=X (where X is an arbitrary integer) may also mean that a UE is notified / configured / indicated of X (corresponding to X TRPs) common UL and DL TCI states (joint TCI state). Furthermore, the expression N=X (where X is an arbitrary integer) and M=Y (where Y is an arbitrary integer, and may also be Y=X) may also mean that a UE is notified / configured / indicated of X (corresponding to X TRPs) UL TCI states and Y (corresponding to Y TRPs) DL TCI states (i.e., independent TCI states).

[0058] For example, when N=M=1 is recorded, it may also mean that a TCI state common to UL and DL for a single TRP (joint TCI state for a single TRP) is notified / set / indicated to the UE.

[0059] Furthermore, for example, when N=1 and M=1 is described, it may also mean that one UL TCI state and one DL TCI state for a single TRP are separately notified / set / indicated to the UE (independent TCI states for a single TRP).

[0060] In addition, for example, when N=M=2 is recorded, it may also mean that the UE is notified / set / indicated of the TCI state common to multiple (two) ULs and DLs for multiple (two) TRPs (joint TCI state for multiple TRPs).

[0061] In addition, for example, when N=2, M=2 is recorded, it may also mean that the UE is notified / set / indicated of multiple (two) UL TCI states and multiple (two) DL TCI states (independent TCI states for multiple TRPs) for multiple (two) TRPs.

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

[0063] Support for N=M=1 in Rel.17 is under study. For example, RRC / MAC CE / DCI may be used to indicate a common beam (e.g., a common beam) that is applied to multiple DL / UL channels / reference signals. Other scenarios may also be supported in Rel.18 and beyond.

[0064] Figure 1A as well as Figure 1B An example of a unified TCI framework is shown. Figure 1AAn example of a joint DL / UL TCI state (eg, a Joint DL / UL TCI state) is shown. Figure 1B An example of a separate TCI state (eg, separate TCI (DL TCI state and UL TCI state)) is shown.

[0065] exist Figure 1A In the example, RRC parameters (information elements) configure multiple TCI states for both DL and UL. In the present disclosure, the TCI state configured by the RRC parameters may also be referred to as a configured TCI state or a configured TCI state (e.g., configured TCI states). The MAC CE may also activate multiple TCI states among the configured multiple TCI states. The DCI may also indicate one of the multiple activated TCI states. In the present disclosure, the TCI state indicated by the DCI may also be referred to as an indicated TCI state or an indicated TCI state (e.g., an indicated TCI state).

[0066] The DCI may be UL DCI (e.g., DCI used for PUSCH scheduling) or DL ​​DCI (e.g., DCI used for PDSCH scheduling). The indicated TCI state may also apply to at least one (or all) UL / DL channels / RSs. A single DCI may also indicate both UL TCI and DL TCI.

[0067] In the example of this figure, one point may be one TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0068] At least one of the multiple TCI states configured via RRC parameters and the multiple TCI states activated via MAC CE can also be referred to as a TCI pool (common TCI pool, joint TCI pool, or TCI state pool). The multiple TCI states activated via MAC CE can also be referred to as an activated TCI pool (activated common TCI pool).

[0069] In this disclosure, higher-layer parameters (RRC parameters) that configure multiple TCI states may also be referred to as configuration information for configuring multiple TCI states, or simply as "configuration information." Furthermore, in this disclosure, using DCI to indicate one of multiple TCI states may involve either receiving indication information indicating one of the multiple TCI states included in the DCI or simply receiving the "indication information."

[0070] exist Figure 1B In this example, RRC parameters configure multiple TCI states for both DL and UL (joint common TCI pool). A MAC CE can also activate multiple TCI states (activated TCI pools) within the configured multiple TCI states. Separate (separate) activated TCI pools for UL and DL can also be configured / activated.

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

[0072] From Rel.17 NR onwards, it is envisaged that support for activating / indicating beams in TCI states associated with different physical cell identifiers (PCIs) will be supported via MAC CE / DCI. Furthermore, from Rel.18 NR onwards, support for indicating a serving cell change to a cell with a different PCI will be supported via MAC CE / DCI.

[0073] Figure 1A TCI state (eg, combined DL / UL TCI state) setting / indication method, and Figure 1B The method for setting / indicating the application of the TCI state (e.g., independent TCI state) can also be switched. Whether to apply the joint DL / UL TCI state or the independent TCI state can also be configured by the base station to the UE through higher layer parameters.

[0074] (TCI status indication)

[0075] The Rel.17 unified TCI framework supports the following modes 1 to 3.

[0076] [Mode 1] MAC CE based TCI state indication

[0077] [Mode 2] DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment

[0078] [Mode 3] DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment

[0079] 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 indicating the TCI state with the Rel.17 TCI state ID for one CC, or receives DCI format 1_1 / 1_2 indicating the TCI state with the Rel.17 TCI state ID for all CCs in the same CC list configured with 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 included if it can be used for DL ​​allocation.

[0080] When DCI format 1_1 / 1_2 is not accompanied by DL allocation, the UE can assume (verify) the following for the DCI.

[0081] - CS-RNTI is used to scramble the CRC for DCI.

[0082] - The values ​​of the following DCI fields (special fields) are set as follows:

[0083] - The redundancy version (RV) field is all '1's.

[0084] - The modulation and coding scheme (MCS) field is all '1's.

[0085] - The new data indicator (NDI) field is 0.

[0086] - The frequency domain resource assignment (FDRA) field is all '0's for FDRA type 0, all '1's for FDRA type 1, or all '0's for Dynamic Switch (same as the validation of the PDCCH for release of DL semi-persistent scheduling (SPS) or UL grant type 2 scheduling).

[0087] In addition, the DCI in the above-mentioned mode 2 / mode 3 can also be called beam indication DCI.

[0088] In Rel.15 / 16, if the UE does not support active BWP changes via DCI, the UE ignores the BWP indicator field. Similar operations are under study regarding support for Rel.17 TCI states and their relationship to the interpretation of the TCI field. Studies are underway to ensure that the TCI field is always present in DCI formats 1_1 / 1_2 when the UE is configured with the Rel.17 TCI state. If the UE does not support TCI updates via DCI, the UE will ignore the TCI field.

[0089] In Rel.15 / 16, whether the TCI field exists (TCI presence information in DCI, tci-PresentInDCI) is set for each CORESET.

[0090] The TCI field in DCI format 1_1 is 0 bits when the higher layer parameter tci-PresentInDCI is not valid, and is 3 bits otherwise. When the BWP indicator field indicates a BWP other than the activated BWP, the UE follows the following operation.

[0091] [Operation] When the higher layer parameter tci-PresentInDCI is not set to valid for the CORESET used in the PDCCH conveying the DCI format 1_1, the UE assumes that tci-PresentInDCI is not valid for all CORESETs within the indicated BWP. Otherwise, the UE assumes that tci-PresentInDCI is valid for all CORESETs within the indicated BWP.

[0092] The TCI field in DCI format 1_2 is 0 bits when the higher-layer parameter tci-PresentInDCI-1-2 is not valid. Otherwise, it is 1, 2, or 3 bits determined by the higher-layer parameter tci-PresentInDCI-1-2. When the BWP indicator field indicates a BWP other than the activated BWP, the UE follows the following operation.

[0093] [Operation] In the case where the higher layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH conveying the DCI format 1_2, the UE assumes that tci-PresentInDCI is not valid for all CORESETs within the indicated BWP. In the case where this is not the case, the UE assumes that tci-PresentInDCI-1-2 is set for all CORESETs within the indicated BWP with the same value as tci-PresentInDCI-1-2 set for the CORESET used in the PDCCH conveying the DCI format 1_2.

[0094] Figure 2A An example of a joint DL / UL TCI state indication based on DCI is shown. A TCI state ID indicating the joint DL / UL TCI state is associated with the value of the TCI field for joint DL / UL TCI state indication.

[0095] Figure 2BAn example of independent DL / UL TCI state indication based on DCI is shown. The TCI field value used for independent DL / UL TCI state indication is associated with at least one TCI state ID, indicating a DL-only TCI state and a UL-only TCI state. In this example, TCI field values ​​000 to 001 are associated with only one DL TCI state ID, TCI field values ​​010 to 011 are associated with only one UL TCI state ID, and TCI field values ​​100 to 111 are associated with both one DL TCI state ID and one UL TCI state ID.

[0096] (Indicates TCI status / sets TCI status)

[0097] For the Rel.17 TCI state, the unified / common TCI state may also mean a Rel.17 TCI state indicated using DCI / MAC CE / RRC (of Rel.17) (indicated Rel.17 TCI state).

[0098] In the present disclosure, the indicated Rel.17 TCI state, the indicated TCI state, the unified / common TCI state, the TCI state applied to multiple signals (channels / RSs), and the TCI state used for multiple signals (channels / RSs) may also be overwritten with each other.

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

[0100] Regarding the Rel.17 TCI state, a TCI state other than the unified TCI state may also refer to a Rel.17 TCI state configured using (Rel.17) MACCE / 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 override each other.

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

[0102] (Channel / RS to which TCI status is applied)

[0103] The "indicated TCI state" based on MAC CE / DCI can also be applied to the following channels / RSs.

[0104] [PDCCH]

[0105] If followUnifiedTCIState is set for CORESET0, the indicated TCI state is applied. Otherwise, the Rel.15 specification applies to this CORESET. In other words, CORESET0 follows the TCI state activated by the MAC CE or is QCLed with the SSB.

[0106] For CORESETs with USS / CSS type 3 and indexes other than 0, the TCI status is always applied.

[0107] If the unified TCI state is set for a CORESET with at least a CSS other than CSS type 3 and indexes other than 0, the indicated TCI state is applied. Otherwise, the configured TCI state for that CORESET is applied to that CORESET.

[0108] [PDSCH]

[0109] For all UE-dedicated PDSCHs, the TCI status is always applied.

[0110] When followUnifiedTCIState is set for a non-UE-dedicated PDSCH (a PDSCH scheduled using DCI within the CSS), the indicated TCI state may also be applied. Otherwise, the set TCI state for that PDSCH is applied to that PDSCH. If followUnifiedTCIState is not set for a PDSCH, whether a non-UE-dedicated PDSCH follows the indicated TCI state is determined by whether followUnifiedTCIState is set for the CORESET used for scheduling that PDSCH.

[0111] [CSI-RS]

[0112] When followUnifiedTCIState is set for the A-CSI-RS used for CSI acquisition or beam management (for the CORESET of the PDCCH that triggers the A-CSI-RS), the indicated TCI state is applied. The configured TCI state for that CSI-RS ("configured TCIstate") is applied to other CSI-RS.

[0113] [PUCCH]

[0114] For all dedicated PUCCH resources, the TCI status is always applied.

[0115] [PUSCH]

[0116] For dynamic / configured granted PUSCH, the TCI status is always applied.

[0117] [SRS]

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

[0119] (TCI status switching)

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

[0121] Even if a UE measures, stores, or maintains QCL characteristics, the network (e.g., base station) cannot identify whether the UE has measured, stored, or maintained these characteristics unless it reports L1-RSRP or beam reporting to the network (e.g., base station). Therefore, for the UE to measure and report beam / RS, both the UE and the network must share knowledge of whether the TCI status is known or unknown.

[0122] In Rel. 16, the TCI status is known if the following conditions 0 to 5 are met:

[0123] (Condition 0): During the period from the last transmission of the RS resources used in the L1-RSRP measurement report of the target TCI state to the completion of the switching to the activated TCI state, the RS resources used for L1-RSRP measurement are the RS of the target TCI state or the RS in a QCL relationship with the target TCI state.

[0124] (Condition 1): A TCI state switch command is received within 1280 ms from the last transmission of a beam report or RS resource for measurement.

[0125] (Condition 2): The UE sends at least one L1-RSRP report for the target TCI state before the TCI state switching indication.

[0126] (Condition 3): During the switching of the TCI state, the detection of the TCI state remains possible.

[0127] (Condition 4): During the switching of the TCI state, detection of the SSB associated with the TCI state remains possible.

[0128] (Condition 5) The signal-to-noise ratio (SNR) in the TCI state is -3dB or higher.

[0129] A TCI status of unknown means that the TCI status is not known.

[0130] In addition, in the present disclosure, a known TCI state may also be referred to as a “known TCI state (Known TCI State)”, and an unknown TCI state may also be referred to as an “unknown TCI state (Unknown TCI State)”.

[0131] When MAC CE is used in TCI state switching (MAC-CE-based TCI state switch), and the target TCI state (switching destination TCI state) is a known TCI state, if the UE receives a physical downlink shared channel (PDSCH) containing a TCI state activation command (TCI state indication) in time slot n, then in time slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slotlength) in the first time slot after receiving the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred. In addition, the UE receives the physical downlink control channel (PDCCH) of the target TCI state of the serving cell in the time slot n+T HARQ +3N subframe,μ slot Before, the PDCCH of the old (before switching) TCI state can be received. HARQ +3N subframe,μ slot Up to time slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state applied by the UE is undefined (refer to Figure 3 ).

[0132] Here, T HARQ Indicates the timing from the transmission of a downlink data signal (e.g., PDSCH) to the delivery confirmation information (e.g., HARQ-ACK information). N subframe,μ slot T represents the number of time slots per subframe for subcarrier setting μ.first-SSB It is the time from when the UE decodes the MAC CE command used in the activation of the TCI state to when the SSB is first transmitted. SSB-proc is 2ms. k If the target TCI state is not included in the list of activated TCI states for PDSCH, it is 1. Otherwise, it is 0. NR slot length indicates the length of a time slot.

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

[0134] When MAC CE is used in switching TCI state, and the target TCI state is an unknown TCI state, if the UE receives a PDSCH containing an activation command of the TCI state in time slot n, then the UE will switch to the unknown TCI state in time slot n+T. 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. In addition, the UE receives the PDCCH of the target TCI state of the serving cell in the first time slot after time slot n+T HARQ +3N subframe,μ slot Previously, it was possible to receive PDCCH in the old (before switching) TCI state.

[0135] Here, TO uk For L1-RSRP measurement using CSI-RS or switching of the TCI state to a QCL type other than QCL type D, the value is 1. uk For switching of the TCI state with at least QCL type D set and using SSB, the L1-RSRP measurement is 0.

[0136] In addition, T first-SSB It is the time from the L1-RSRP measurement to the first transmission of SSB when switching to the TCI state with at least QCL type D is performed. Or, T first-SSBIt is the time from when the UE decodes the MAC CE command used in the activation of the TCI state other than the set QCL type D to when the SSB is initially sent.

[0137] Compared with the case where the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the switching of the TCI state requires an additional T L1-RSRP Time. L1-RSRP is the time associated with the received power measurement. L1-RSRP In frequency range (FR) 1, or in FR2 where QCL type D is not set, it is 0. Otherwise, it is the time required for decision and refinement of the reception beam in FR2.

[0138] Furthermore, when downlink control information (DCI) is used in a TCI state switch (DCI-based TCI state switch), and when the target TCI state is a known TCI state, the UE shall receive the PDSCH of the target TCI state of the serving cell in which the TCI state switch occurred in the first slot after slot n + timeDurationForDCI, provided that the higher layer parameter tci-PresentInDCI for the CORESET scheduling the PDSCH in slot n is enabled. Here, timeDurationForDCI is the time required for receiving the PDCCH and applying information related to spatial relations / QCL (spatial QCL information) to the reception of the DCI for the PDSCH.

[0139] Furthermore, when RRC signaling is used to switch the TCI state (RRC-based TCI state switch), and when the target TCI state is a known TCI state, if the UE receives a PDSCH transmitting an RRC activation command for the TCI state in time slot n, then in time slot n+(T RRC_processing +TO k *(T first-SSB +T SSB-proc The first time slot after )) / (NR slot length) receives the PDCCH of the target TCI state of the serving cell where the TCI state switching occurs.

[0140] Here, T RRC_processing It is the delay associated with the RRC process (RRC processing delay). first-SSBIt is the time from the UE's RRC process to the initial transmission of SSB. SSB-proc 、TO k And (NR slot length) is the same as the case of known TCI state in TCI state switching using MAC CE.

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

[0142] Here, T RRC_processing It is the delay associated with the RRC process (RRC processing delay). SSB-proc 、TO uk And (NR slot length) is the same as the case of unknown TCI state in TCI state switching using MAC CE.

[0143] In addition, T first-SSB It is the time from the L1-RSRP measurement to the first transmission of SSB when switching to the TCI state with at least QCL type D is performed. Or, T first-SSB It is the time from when the UE decodes the MAC CE command used in the activation of the TCI state other than the set QCL type D to when the SSB is initially sent.

[0144] Rel. 17 specifies a delay time for switching related to a unified TCI state.

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

[0146] In MR-DC or standalone NR, this delay time may also be applied to the entire list of multiple serving cells in the simultaneous TCI update lists (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4) in multiple CCs / cells.

[0147] When the target DL TCI state refers to an additional physical cell ID (PCI) different from the serving cell's physical cell ID (PCI) for which the DL TCI state is set, the delay time may be applied if the following conditions are met:

[0148] The activation BWP of the serving cell and the cell to which the PCI is added are the same.

[0149] The center frequency, subcarrier spacing (SCS), and system frame number (SFN) offset of the cell to which the PCI is added are the same as those of the serving cell.

[0150] The cell to which the PCI is added is known to the UE.

[0151] In addition, the cell to which the PCI is added may be known if the following conditions are met:

[0152] Within the last 5 seconds immediately before the L1-RSRP measurement is set, the UE sends a valid L3 measurement report to the cell to which the PCI is added.

[0153] The timing offset between the serving cell and the cell to which the PCI is added is within the CP of the corresponding SCS.

[0154] If this condition is not met, the cell to which the PCI is added may also be unknown.

[0155] The DL TCI state in the unified TCI state is known and may also mean that the following conditions are met:

[0156] From the last transmission of RS resources used for L1-RSRP measurement reporting in the target DL TCI state until the completion of switching to the active DL TCI state, the RS resources for L1-RSRP measurement are RSs in the target DL TCI state or RSs in a QCL relationship with the target DL TCI state.

[0157] The DL TCI state switch command (downlink TCI state switch command) is received within 1280 ms from the last transmission of the beam report or RS resource for measurement.

[0158] • The UE sends at least one L1-RSRP report for the target DL TCI state before the DL TCI state switch indication.

[0159] During the switching of DL TCI states, detection of the DL TCI state remains possible.

[0160] • During the switching of DL TCI states, detection of SSBs associated with the DL TCI state remains possible.

[0161] The signal-to-noise ratio (SNR) in the DL TCI state is -3dB or higher.

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

[0163] When the above conditions are not met, the DL TCI state may also be unknown.

[0164] In the case of joint TCI state switching, if the target PL-RS is not maintained, the UE may not expect DL reception based on the target TCI state before completing the switching of the DL and UL TCI states.

[0165] When MAC CE is used in the switching of DL TCI state (MAC-CE based downlink TCI state switch), and the target TCI state (switching destination TCI state) is a known TCI state, if the UE receives a PDSCH containing a TCI state activation command (TCI state indication) in time slot n, then in time slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slotlength) in the first time slot after receiving the physical downlink control channel (PDCCH) of the target TCI state of the serving cell where the TCI state switching occurred. In addition, the UE receives the physical downlink control channel (PDCCH) of the target TCI state of the serving cell in the time slot n+T HARQ +3N subframe,μ slotPreviously, the old (before switching) TCI state could be used to receive UE-specific PDSCH / PDCCH. HARQ +3N subframe,μ slot Up to time slot n+T HARQ +3N subframe,μ slot +TO k *(T first-SSB +T SSB-proc ) / (NR slot length), the TCI state applied by the UE is not specified.

[0166] Here, T HARQ Indicates the timing from the transmission of a downlink data signal (e.g., PDSCH) to the delivery confirmation information (e.g., HARQ-ACK information). N subframe,μ slot T represents the number of time slots per subframe for subcarrier setting μ. first-SSB It is the time from when the UE decodes the MAC CE command used in the activation of the TCI state to when the SSB is first transmitted. SSB-proc is 2ms. k If the target TCI state is not included in the list of activated TCI states for PDSCH, it is 1; otherwise, it is 0. NR slot length indicates the length of a time slot.

[0167] When MAC CE is used for switching of DL TCI state, and the target TCI state is an unknown TCI state, if the UE receives a PDSCH including an activation command of the TCI state in time slot n, then the UE shall switch to the unknown TCI state in time slot n+T. 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. In addition, the UE receives the PDCCH of the target TCI state of the serving cell in the first time slot after time slot n+T HARQ +3N subframe,μ slot Previously, it was possible to receive UE-specific PDSCH / PDCCH using the old (pre-handover) TCI state.

[0168] Here, TO uk For L1-RSRP measurement using CSI-RS or switching of the TCI state to a QCL type other than QCL type D, the value is 1.uk For switching of the TCI state with at least QCL type D set and using SSB, the L1-RSRP measurement is 0.

[0169] In addition, T first-SSB It is the time from the L1-RSRP measurement to the first transmission of SSB when switching to the TCI state with at least QCL type D is performed. Or, T first-SSB It is the time from when the UE decodes the MAC CE command used in the activation of the TCI state other than the set QCL type D to when the SSB is initially sent.

[0170] Compared with the case where the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the switching of the TCI state requires an additional T L1-RSRP Time. L1-RSRP is the time associated with the received power measurement. L1-RSRP In frequency range (FR) 1, or in FR2 where QCL type D is not set, it is 0. Otherwise, it is the time required for decision and refinement of the reception beam in FR2.

[0171] In addition, for example, when RRC parameters related to the unified TCI state (DLorJoint-TCIState (when unifiedTCI-StateType indicates Joint) or UL-TCIState) are set for the UE for the UL channel / signal of the serving cell, the specified delay time can also be applied.

[0172] In MR-DC or standalone NR, this delay time may also be applied to the entire list of multiple serving cells in the simultaneous TCI update lists (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4) in multiple CCs / cells.

[0173] For the UL TCI state (or, combined TCI state), the known / unknown of the cell with the additional PCI and the known / unknown of the UL TCI state are the same as the case where the "DLTCI state" of the cell with the additional PCI and the known / unknown TCI state for the above-mentioned DL TCI state is rewritten as "UL TCI state (or, combined TCI state)".

[0174] In the case of joint TCI state switching, the UE may not expect transmission in the UL before completing the switching of the DL and UL TCI states.

[0175] In the case where MAC CE is used in switching between independent UL TCI state / joint TCI state for UL channel / signal (MAC-CE based uplink TCI state switch), and when the target TCI state (switching destination TCI state) is a known TCI state, if the UE receives a PDSCH containing an activation command (TCI state indication) of the TCI state in time slot n, then in time slot n+T HARQ +3N subframe,μ slot +NM*(T first-target-PL-RS +4*T target-PL-RS +2ms) / (NR slot length) can transmit UL signals in the target TCI state. Here, the UL channel / signal can also be PUCCH, PUSCH, or (when beamCorrespondenceWithoutUL-BeamSweeping is set to 1) semi-persistent / periodic / aperiodic SRS.

[0176] In addition, when MAC CE is used for switching between independent UL TCI state / joint TCI state for UL channel / signal, and when the target TCI state is unknown TCI state, if the UE receives a PDSCH including a TCI state activation command (TCI state indication) in time slot n, then in time slot n+T HARQ +3N subframe,μ slot +(T L1-RSRP +T first-target-PL-RS +4*T target-PL-RS +2ms) / (NR slot length) can send UL signal of target TCI state.

[0177] Here, T HARQ Indicates the timing from the transmission of a downlink data signal (e.g., PDSCH) to the delivery confirmation information (e.g., HARQ-ACK information). N subframe,μ slot Indicates the number of slots per subframe for subcarrier setting μ. NR slot length indicates the length of the slot.

[0178] Regarding NM, it is 1 when the target PL-RS is maintained, and it is 0 when it is not maintained.

[0179] Ttarget-PL-RS When the target TCI state is unknown, it is the time from the L1-RSRP measurement to the initial transmission of the path loss RS. target-PL-RS It is the time from when the MAC CE command is decoded by the UE to when the initial path loss RS is sent when the target TCI state is known.

[0180] In the case where PL-RS is associated with the serving cell, T target-PL-RS is the period of the target PL-RS as SSB or NZP CSI-RS. In case the PL-RS is associated with a PCI different from that of the serving cell, T target-PL-RS It is the period of PL-RS that becomes SSB.

[0181] Compared with the case where the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, the switching of the TCI state requires an additional T L1-RSRP Time. L1-RSRP is the time associated with the received power measurement. L1-RSRP In frequency range (FR) 1, or in FR2 where QCL type D is not set, it is 0. Otherwise, it is the time required for decision and refinement of the reception beam in FR2.

[0182] (analyze)

[0183] In future wireless communication systems (Rel. 18 / 19 and later), support for event-based beam reporting is under study. Event-based beam reporting can also be referred to as event-triggered beam reporting or UE-initiated beam reporting.

[0184] However, the provisions for triggering beam reporting for this event are not well studied.

[0185] In addition, it is believed that in this beam report, the beam / TCI status cannot be applied / updated quickly while following the above-mentioned existing specifications and the delay time involved in the application of the beam (TCI status) (for example, the delay time involved in the beam report, the time required for the beam indication, the time involved in the known / unknown cell / TCI status).

[0186] In event-triggered beam reporting, since UE-based beam reporting can reduce delay time, research is underway to define this delay time differently from existing specifications. However, this research is not yet sufficient.

[0187] If these studies are insufficient, communication with lower latency cannot be achieved, which may lead to a suppression of improvements in communication quality and throughput.

[0188] Therefore, the inventors of the present invention have conceived a method for solving these problems.

[0189] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods according to the respective embodiments may be applied individually or in combination.

[0190] In the present disclosure, "A / B" and "at least one of A and B" may be replaced with each other. In addition, in the present disclosure, "A / B / C" may also mean "at least one of A, B, and C."

[0191] In the present disclosure, the words “notify,” “activate,” “deactivate,” “indicate,” “select,” “configure,” “update,” and “determine” may be used interchangeably. In the present disclosure, the words “support,” “control,” “controllable,” “operate,” and “operable” may also be used interchangeably.

[0192] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-layer parameters, fields, Information Elements (IEs), and settings may also be overwritten. In this disclosure, Medium Access Control (MAC) Control Elements (CEs), update commands, and activation / deactivation commands may also be overwritten.

[0193] In the present disclosure, high-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (for example, positioning protocols (for example, NR Positioning Protocol A (NRPPa)) / LTE Positioning Protocol (LTE Positioning Protocol (LPP))) messages, etc., messages from the core network), or any one of them, or a combination thereof.

[0194] In the present disclosure, MAC signaling may include, for example, a MAC Control Element (MACCE) and a MAC Protocol Data Unit (PDU). Broadcast information may include, for example, a Master Information Block (MIB), a System Information Block (SIB), minimum system information (Remaining Minimum System Information (RMSI)), and other system information (Other System Information (OSI)).

[0195] In the present disclosure, the physical layer signaling may also be, for example, downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI)), etc.

[0196] In the present disclosure, omit, discard, suspend, delete, truncate, rate match, postpone, not send, etc. may also be replaced with each other.

[0197] (Wireless Communication Method)

[0198] In the present disclosure, event-triggered beam reporting may also be referred to as beam reporting / CSI reporting / L1 beam reporting.

[0199] The embodiments of the present disclosure may also be applied in at least one of the following scenarios 1 or 2:

[0200] [Case 1]: L1-RSRP / SINR beam reporting including serving cell PCI / supplementary PCI (e.g., L1-RSRP / SINR beam reporting including serving cell / supplementary PCI for Rel.18 L1 / L2 mobility with L1 / L2 intra-cell (inter-cell) mobility / intra-cell multi-TRP (inter-cell M-TRP) / cell handover).

[0201] [Case 2] L1-RSRP / SINR beam report including only the serving cell PCI.

[0202] Event-triggered beam reporting may also be supported, for example, for at least one of the following purposes:

[0203] A: Reduce the overhead of L1 beam reporting.

[0204] B: Reduced TCI status activation delay.

[0205] Regarding A, to avoid beam failure, base stations must frequently perform L1 beam reporting in the current network (NW), increasing UL resource overhead. Furthermore, it is believed that PDCCH overhead for beam reporting also increases. Therefore, it is believed that event-triggered beam reporting can help reduce L1 beam reporting overhead.

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

[0207] The UE may also report measurement results (eg, L1-RSRP / L1-SINR) to the NW (eg, base station) when a specific event occurs (specific conditions are met / not met).

[0208] For example, a specific event may be an event related to at least one of the serving cell and the additional cell, or an event related to a beam report including the PCI of the serving cell and the PCI of the additional cell.

[0209] Incidents Regarding Scenario 1

[0210] An example of an event for the above-mentioned scenario 1 will be described. This event may refer to, for example, an event related to the serving cell and the additional cell, or an event related to a beam report including the PCI of the serving cell and the PCI of the additional cell.

[0211] [Option 1]

[0212] One or more existing Radio Resource Management (RRM) events (e.g., at least one of the following events A2 to A6 and I1) can also be reused to trigger beam reporting (e.g., aperiodic CSI reporting). Specifically, when at least one of the following events A2 to A6 and I1 occurs (if the event conditions are met), both an RRM report and a CSI report can be triggered, and the UE can send both an RRM report and a CSI report.

[0213] In addition, in the present disclosure, RRM reports and L3 measurement reports may also be overwritten with each other.

[0214] Figure 5This flowchart illustrates an example of event-triggered beam reporting processing. The UE determines whether an event (e.g., at least one of events A2 to A6 and I1) has occurred (S1). If the answer in S1 is YES, the UE transmits an aperiodic CSI report (and RRM report) (S2). If not, the processing related to the first embodiment ends. Figure 5 The processing may also be repeated at specific intervals.

[0215] In the present disclosure, triggering of aperiodic CSI reporting and sending of aperiodic CSI reporting by the UE may also overwrite each other. CSI reporting, L1 beam reporting, and beam reporting may also overwrite each other.

[0216] In the following events A2 to A6, the measurement result may also be the measurement result of at least one of RSRP (L1-RSRP / L3-RSRP), RSRQ, and SINR (RS-SINR). In the conditions of the following events A2 to A6, "poor" may also mean "low", and "excellent" may also mean "high". In the conditions of the following events A2 to A6, SpCell may also mean a special cell, or 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 also be added / subtracted from the measurement result. The thresholds may be the same or different. A neighboring cell may also be a non-serving cell.

[0217] Event A2: The measurement result of the serving cell is worse than the threshold.

[0218] Event A3: The measurement result of the neighboring cell (the value after adding the offset to the measurement result) is better than the measurement result of the SpCell (the value after adding the offset to the measurement result).

[0219] Event A4: The measurement result of the neighboring cell (the value after adding the offset to the measurement result) is better than the threshold.

[0220] Event A5: The measurement result of the SpCell is worse than the first threshold, and the measurement result of the neighboring cell (the value after adding the offset to the measurement result) is better than the second threshold.

[0221] Event A6: The measurement result of the neighboring cell (the value after adding the offset to the measurement result) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the value after adding the offset to the measurement result).

[0222] Event I1: The interference measurement result is higher than the threshold.

[0223] According to Option 1, since the trigger of the RRM report can be reused in the trigger of the beam report, it is easy to set up.

[0224] [Option 2]

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

[0226] [[Option 2-1]]

[0227] The thresholds may also be different. That is, different thresholds from those used for RRM reporting may be used, and events A2 to A6 and I1 may be used for L1 beam reporting (CSI reporting).

[0228] [[Option 2-2]]

[0229] An event may also occur based on the measurement results of the reference signal received power (L1-RSRP) in layer 1. That is, the comparison may be based on L1-RSRP rather than L3-RSRP. Alternatively, a newly filtered L1-RSRP with a time scale (update / measurement period) between L1-RSRP and L3-RSRP (or the same as L1-RSRP or L3-RSRP) may be used. Alternatively, other metrics such as L1-SINR and L3-RSRQ may be used. For example, the following event A2' may be applied as a new event:

[0230] Event A2': the L1-RSRP measurement result of the serving cell is worse than the threshold.

[0231] [[Option 2-3]]

[0232] The comparison may also be based on a beam level, multiple beam levels (combining the independent measurement results of multiple beams into one value), or cell level measurement results. For example, the following event A4' or event A4'' may also be applied:

[0233] Event A4': The measurement result of one beam from a neighboring cell is better than the threshold.

[0234] Event A4'': The statistical value (e.g., average value, total value, etc.) of the measurement results of multiple beams (e.g., the best X beams) exceeds a threshold. X can be fixed or set through higher layer signaling.

[0235] [[Options 2-4]]

[0236] The number of beams that meet the conditions (e.g., any of events A2 to A6 and I1) may also be considered. For example, if X beams meet event A4' (the measurement results of X beams from neighboring cells are better than the threshold), the UE may also perform CSI reporting.

[0237] In addition, an example of combining at least two of the above 2-1 to 2-4 can also be applied. For example, consider A4''' as an event that combines 2-2 and 2-3. In addition, consider A4'''' as an event that combines 2-2, 2-3, and 2-4:

[0238] Event A4''': The L1-RSRP measurement result of one beam from the neighboring cell is better than the threshold.

[0239] Event A4'''': L1-RSRP of each of the X beams from the neighboring cell is better than the threshold.

[0240] According to Option 2, CSI reporting can be performed at a higher speed than when using an event for conventional RRM reporting using RRC.

[0241] [Option 3]

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

[0243] It is also possible to combine existing events for RRM reporting with one or more events of Option 2. For example, CSI reporting may be triggered when both event A4 and new event A4''' occur.

[0244] It is also possible to combine two or more events of Option 2. For example, a CSI report may be triggered when both event A2' and a new event A4''' are satisfied.

[0245] Incidents Regarding Scenario 2

[0246] An example of an event for the above-mentioned scenario 2 will be described. This event may refer to, for example, an event related only to the serving cell or an event related to a beam report including only the PCI of the serving cell.

[0247] One or more new events (separate from the events used for RRM reporting) may also be defined to trigger aperiodic L1 beam reporting (CSI reporting). The event may also be at least one of the following events B2 to B6 and K1:

[0248] Event B2: The measurement result of the current beam is worse than the threshold.

[0249] Event B3: The measurement result of another beam (the value after adding the offset to the measurement result) is better than the measurement result of the current beam (the value after adding the offset to the measurement result).

[0250] Event B4: The measurement results of other beams (the value after adding the offset to the measurement result) are better than the threshold.

[0251] Event B5: The measurement result of the current beam is worse than the first threshold, and the measurement results of other beams (the value after adding the offset to the measurement result) are better than the second threshold.

[0252] Event B6: The measurement result of the current beam (the value after adding the offset to the measurement result) is worse than the threshold, and the measurement results of other beams (the value after adding the offset to the measurement result) are better than the measurement result of the current beam (the value after adding the offset to the measurement result).

[0253] Event K1: The interference measurement result is higher than the threshold.

[0254] Furthermore, the names and symbols associated with the events in this disclosure (e.g., A2-A6, B2-B6, I1, K1, etc.) are merely examples and are not intended to be limiting. For example, the name of the event for scenario 2 may be the same as the name of the event for the corresponding scenario 1.

[0255] In addition, for at least one of the events in the present disclosure (events involved in Case 1 / Case 2), a period (duration) / counter that satisfies the event (condition) may also be specified. The UE / NW may also determine that the condition of each event is satisfied when at least one of the conditions of the above-mentioned events satisfies the condition related to a specific period / counter. For example, the UE may also determine that the condition of the above-mentioned event B3 is satisfied when the measurement results of other beams are better than the measurement results of the current beam in a time window of 100ms. In addition, for example, the UE may also determine that the condition of the above-mentioned event B3 is satisfied when the measurement results of other beams are better than the measurement results of the current beam 10 times out of every plurality of samples.

[0256] The so-called “current beam” may refer to, for example, an SSB / CSI-RS that is in a QCL relationship (QCLed) with the PDCCH.

[0257] The PDCCH may be, for example, a PDCCH corresponding to a CORESET determined by a specific rule or a higher-layer parameter setting. The CORESET may be, for example, a CORESET with a specific (eg, lowest / highest) CORESET ID.

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

[0259] Furthermore, the so-called "current beam" may be, for example, an indicated TCI state (joint / DL TCI state) in the current unified TCI state. Furthermore, the so-called "current beam" may be, for example, a QCL source RS associated with the current indicated TCI state.

[0260] Furthermore, the so-called “current beam” may be, for example, a beam / resource index (eg, CRI / SSBRI) reported in a specific (eg, latest) L1-RSRP / L1-SINR.

[0261] The so-called "other beams" may be, for example, beams / SSBs / CSI-RS / TCI states other than the "current beam".

[0262] A set of multiple beams (a candidate beam set) may be configured for the UE, and the UE may select or determine "other beams" from the set.

[0263] “(Worse) / Better” may also mean a (lower) / higher measurement result (eg, RSRP / SINR / RSRQ).

[0264] The above thresholds may be predefined in the specification, set / indicated / notified using higher-layer signaling (RRC / MAC CE) / DCI, reported via UE capabilities, or specified by a combination thereof. For example, the thresholds may be reused from existing thresholds (e.g., the thresholds used in RRM / Case 1).

[0265] The above-mentioned offset related to the threshold may be pre-defined in the specification, may be set / indicated / notified using higher layer signaling (RRC / MAC CE) / DCI, may be reported through UE capabilities, or may be specified through a combination of these.

[0266] <First embodiment>

[0267] The first embodiment involves event triggered beam reporting.

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

[0269] Implementation Method 1-1

[0270] Event triggered beam reports may also be sent using specific information / signaling.

[0271] For example, event-triggered beam reports may also be sent using MAC CE.

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

[0273] Existing MAC CEs (for example, those specified up to Rel. 17) (for example, MAC CEs for BFR) can also be used as MAC CEs for event-triggered beam reporting.

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

[0275] Furthermore, in this case, a specific field (e.g., a reserved bit field) included in the existing MAC CE can be used instead. This field can, for example, indicate that the MAC CE is an event-triggered beam reporting MAC CE. This field can also indicate that BFR has not occurred. This field can also have a specific number of bits (e.g., 1 bit).

[0276] For event-triggered beam reporting, specific UL resources can also be set for the UE.

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

[0278] Furthermore, the UL resource may also be, for example, at least one of another / existing PUCCH-SR resource (SR configuration) and PRACH. For example, the UE may use this UL resource to request a UL grant from the network. For example, the UE may use this UL resource even if the aforementioned specific PUCCH-SR resource is not configured.

[0279] By using specific PUCCH-SR resources, the NW can identify when a situation requiring beam reporting has occurred in the UE and prioritize the allocation of PUCCH resources to the UE, thereby enabling flexible communication.

[0280] In addition, by using other / existing PUCCH-SR resources, the UE implementation can be simplified.

[0281] Implementation Method 1-2

[0282] Event triggered beam reports may also be sent using specific information / signaling.

[0283] For example, event-triggered beam reports may also be sent using UCI.

[0284] The UE can also be pre-set with event-triggered beam reporting.

[0285] The UE may also send a beam report (including the UCI of the beam report) in an UL channel (e.g., PUSCH / PUCCH) when an event occurs.

[0286] The UE may also omit the transmission of beam reporting using UCI in the UL channel (eg, PUSCH / PUCCH) when no event occurs.

[0287] In implementations 1-2, to avoid blind detection of UCI bits of varying sizes in the base station, the base station and the UE must have the same understanding of the number of UCI bits. Therefore, the UE can use UCI (PUCCH / PUSCH) to transmit only event-triggered beam reports. In other words, the UCI used for beam reporting can also contain only beam reports.

[0288] With this configuration, the base station only needs to determine / judge whether the PUCCH is transmitted, thereby avoiding blind detection of UCI bits of different sizes.

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

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

[0291] When the UE is instructed to transmit other UCI / PUSCH in a certain time resource (e.g., time slot / sub-time slot / code symbol), it is not necessary to expect / assume the transmission of UCI for event-triggered beam reporting in this time resource.

[0292] Furthermore, when the UE multiplexes the UCI for event-triggered beam reporting with other UCI (when the UCI for event-triggered beam reporting and other UCI are transmitted in the same time resource), the UE may assume or determine that the number of bits of the UCI for event-triggered beam reporting is a specific number of bits. Furthermore, the specific number of bits may be specified in the specification, set by higher layers, or reported through UE capability information.

[0293] In addition, when the UE is instructed to send UCI for event-triggered beam reporting and other UCI in the same time slot / sub-time slot (for example, when the UE is instructed to multiplex the UCI of the two), regardless of whether there is UCI for event-triggered beam reporting, the UE can assume / judge that a specific number of bits of UCI for event-triggered beam reporting are multiplexed and send UCI. In addition, the specific number of bits can also be specified in the specification, or set by the upper layer, or reported by the UE capability information. Thus, the number of UCI bits after UCI multiplexing is fixed, regardless of whether there is UCI for event-triggered beam reporting, so that blind detection of the number of UCI bits can be avoided on the base station side. In addition, the bits of a specific length multiplexed as UCI for event-triggered beam reporting when UCI for event-triggered beam reporting does not exist can also include specific bits (for example, a value of all 0s).

[0294] For example, the UE may perform padding to set the UCI for event-triggered beam reporting to the specific number of bits. The UE may also assume that the UCI for event-triggered beam reporting has a larger number of bits than other UCIs.

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

[0296] Implementation Methods 1-3

[0297] In embodiments 1-3 to 1-5, the information included in the event-triggered beam report is described.

[0298] The event-triggered beam report may also include information indicating at least one of the following:

[0299] Serving cell index.

[0300] BWP index.

[0301] • Beam / reference signal (e.g., SSB / CSI-RS) index.

[0302] Measurement results (e.g., L1-RSRP / L1-SINR).

[0303] Implementation Methods 1-4

[0304] The number of reported beams / RSs included in the event-triggered beam report may also be a specific number.

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

[0306] This 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.

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

[0308] The measurement results (e.g., L1-RSRP / L1-SINR) included in the event-triggered beam report can also be expressed as absolute values. In this case, the measurement results can also be expressed by the first bit (e.g., 7 bits) for each beam / RS.

[0309] The values ​​of the measurement results (eg, L1-RSRP / L1-SINR) included in the event-triggered beam report may also be represented by absolute values ​​and relative values.

[0310] 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 other beams / RS may be expressed as relative values.

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

[0312] Implementation Methods 1-5

[0313] The event-triggered beam report may also include information indicating at least one of the following:

[0314] PCI (or re-indexed PCI).

[0315] Panel ID (UE capability value set).

[0316] Resource set indicator.

[0317] Event indication.

[0318] Parameters related to beam updating.

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

[0320] The information indicating the resource set indicator may also be included in the event-triggered beam report, for example, when group-based beam reporting is configured / supported.

[0321] Information related to event indication may also be included in the event triggered beam report, for example, when multiple events are set for the UE.

[0322] Parameters related to beam updating may also be parameters / indicators indicating whether the UE (autonomously) updates the beam / TCI status / QCL assumption after reporting, for example.

[0323] According to embodiments 1-3 / 1-4 / 1-5, the structure of the event-triggered beam report can be appropriately specified.

[0324] According to the above first embodiment, event-triggered beam reporting can be appropriately specified.

[0325] <Second embodiment>

[0326] The second embodiment relates to operations after the transmission of an event-triggered beam report.

[0327] After the event triggers the sending of the beam report, the UE can also update / change / apply the beam (QCL assumption / TCI status / spatial relationship) based on a specific method.

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

[0329] Implementation Method 2-1

[0330] Regarding updates / changes / applications of TCI status / QCL concepts, operations based on existing specifications (e.g., Rel. 15-17) can also be utilized.

[0331] Whether to indicate a new beam (or update a beam) based on an event-triggered beam report may also depend on the NW (base station). For example, the NW (base station) may indicate a new beam based on an event-triggered beam report. Based on this indication, the UE may update or change the indicated beam (QCL assumption, TCI status, or spatial relationship).

[0332] In this case, the UE may also receive a response (e.g., a positive acknowledgement (ACK) or negative acknowledgement (NACK)) to the beam report from the NW (base station). This method allows the UE to distinguish whether the NW (base station) failed to receive the beam report or whether the NW (base station) ignored a properly received beam report.

[0333] After the beam report, if the UE does not receive a positive response to the beam report during the first period, or if it receives a negative response to the beam report during the first period, it can retransmit the beam report after the end of the first period, or send a new beam report different from the sent beam report. The beam report can also be retransmitted a maximum of a specific number of times.

[0334] The first period and the specific number of times may be pre-defined in the specification, or may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported through UE capability information.

[0335] The response to the beam report may also be sent using a specific DL signal (eg, DCI), for example.

[0336] Figure 6 This is a diagram showing an example of beam updating according to Embodiment 2-1. Figure 6 In the example shown, the UE sends an event-triggered beam report to the NW (base station) (step S601). Based on this beam report, the NW determines whether a beam update is necessary (or not) (step S602). The NW then instructs the UE to update its beam (to a new beam) (step S603). Based on this instruction, the UE performs a beam update (step S604).

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

[0338] Implementation Method 2-2

[0339] The UE can also update / change / apply the beam (QCL assumption / TCI status / spatial relationship) based on event-triggered beam reporting.

[0340] This update / change / application is different from the embodiment 2-1 in that no instruction from the NW (base station) is required.

[0341] The UE may also update / change / apply the beam (QCL assumption / TCI state / spatial relationship) after a specific period following the sending of an event-triggered beam report. This beam may also correspond to the optimal beam / RS included in the beam report.

[0342] By performing autonomous beam updates based on the UE, faster beam updates can be performed.

[0343] Figure 7 This is a diagram showing an example of beam updating according to embodiment 2-2. Figure 7 In the example shown, the UE makes an event-triggered beam report to the NW (base station) (step S701). Then, after a specific period of time has passed since the beam report, the UE (autonomously) performs a beam update based on the beam report (step S702).

[0344] The specific period may be pre-defined in the specification, may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported through UE capability information.

[0345] This specific period is represented by, for example, a specific time unit (eg, Xms / symbol / time slot / sub-time slot).

[0346] The UE may also receive a response (eg, a positive acknowledgement (ACK) or a negative acknowledgement (NACK)) to the beam report from the NW (base station). This method can avoid mismatching of identification between the UE and the base station.

[0347] After the beam report, if the UE does not receive a positive response to the beam report during the first period, or if it receives a negative response to the beam report during the first period, it can retransmit the beam report after the end of the first period, or send a new beam report different from the sent beam report. The beam report can also be retransmitted a maximum of a specific number of times.

[0348] The first period and the specific number of times may be pre-defined in the specification, or may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported through UE capability information.

[0349] The response to the beam report may also be sent using DCI, for example.

[0350] For example, when MAC CE is used for beam reporting, a response to the beam report can also be sent using a DCI format with the same HARQ process number as the original PUSCH (transmitting the MAC CE) and a toggled New Data Indicator (NDI) field value.

[0351] When the UE performs beam reporting for multiple beams / RSs, the response to the beam reporting may also indicate any one of the multiple beams / RSs. This configuration enables more flexible beam updating.

[0352] For example, when the UE reports measurement results for N beams / RSs, the response to the beam report may also include N bits of information representing any one of the multiple beams / RSs.

[0353] Furthermore, for example, when the UE reports measurement results for N beams / RSs, the UE may receive 1 bit of information as 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.

[0354] In the case where the reported beam report contains parameters related to beam updating (parameters / indicators indicating whether the beam / TCI status / QCL assumption is updated (autonomously)), the UE may also expect / assume receiving an ACK (or NACK) from the NW.

[0355] The UE may also update / change / apply the beam (QCL assumption / TCI status / spatial relationship) after a specific period has passed since the beam report was received (or, since the beam report was sent).

[0356] The specific period may be pre-defined in the specification, may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported through UE capability information.

[0357] This specific period is represented by, for example, a specific time unit (eg, Xms / symbol / time slot / sub-time slot).

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

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

[0360] <Third embodiment>

[0361] The third embodiment relates to activation delay of the TCI state.

[0362] (analyze)

[0363] As described above, when the activated TCI state is known, the time associated with receiving power measurement or the time required for receiving beam determination / refinement (for example, T L1-RSRP ).

[0364] In addition, if the UE has already measured the root SSB (QCL source (SSB / CSI-RS) involved in the QCL source (TRS / CSI-RS) in the TCI state), the time required for SSB measurement can be omitted / reduced (for example, TO k *(T first-SSB +T SSB-proc ) / (NR slot length))(becomes TO k =0).

[0365] When the UE reports L1-RSRP using event-triggered beam reporting, it means that the UE has already measured the beam / RS. Therefore, at least the reported beam / RS is known, and thus the time associated with receiving power measurement or the time required for receiving beam decision / refinement (e.g., T L1-RSRP ).

[0366] Furthermore, if the UE can measure the root SSB (e.g., SSB / CSI-RS) associated with the reported beam, the time required for SSB measurement (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slot length))(becomes TO k =0).

[0367] The following describes the UE / NW operations described above.

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

[0369] In addition, the time required for SSB measurement (for example, TO k *(T first-SSB +T SSB-proc) / (NR slotlength)) may also be based on the period starting from the indication of activation of the TCI state (receipt of the MAC CE of the TCI activation command). Specifically, the time required for SSB measurement may be the period during which the SSB is measured a specific number of times (for example, twice) from the indication of activation of the TCI state (the start / end codeword).

[0370] In addition, the time required for SSB measurement (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slotlength)) may be based on a period starting from a specific timing. Specifically, the time required for SSB measurement may be a period during which SSB is measured a specific number of times (for example, twice) starting from a specific timing.

[0371] The specific timing may also be the transmission timing of the event-triggered beam report (e.g., the start / end symbol), or the measurement timing of the SSB / CSI-RS immediately before the beam report (e.g., the start / end symbol). As a result, compared to the case where the SSB is measured after the activation instruction of the TCI state is received later, the SSB measurement can be started before the activation instruction of the TCI state, thereby not shortening the time required for the SSB measurement (e.g., the time required for the TCI state activation). k *(T first-SSB +T SSB-proc ) / (NR slotlength)), which can shorten the time from event-triggered beam reporting to the completion of SSB measurement.

[0372] Implementation Method 3-1

[0373] The UE may also use event-triggered beam reporting to report L1-RSRP.

[0374] The UE / NW (base station) may also trigger beam reporting based on an event, assuming / determining that the reported beam (the beam / RS corresponding to the reported L1-RSRP) is known.

[0375] The UE / NW (base station) may also assume / determine that the reported beam (the beam / RS corresponding to the reported L1-RSRP) is known after the transmission / reception of the event-triggered beam report.

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

[0377] The specific period may also start from a specific (e.g., first / last) codeword of the PUSCH / PUCCH of the beam report, for example. In addition, the specific period may also start from a specific (e.g., first / last) codeword of the response (e.g., ACK / NACK) to the beam report, for example.

[0378] The specific period may be pre-defined in the specification, may be configured / indicated / notified to the UE using higher layer signaling (RRC / MAC CE) / DCI, or may be reported through UE capability information.

[0379] The response to the beam report may also be sent via DCI, for example.

[0380] The DCI may also include information related to the length of the specific period.

[0381] For example, when MAC CE is used for beam reporting, a response to the beam report can also be sent using a DCI format with the same HARQ process number as the original PUSCH (transmitting the MAC CE) and a toggled New Data Indicator (NDI) field value.

[0382] Figure 8A : is a diagram showing an example of a known period of a beam according to the third embodiment. Figure 8A In the example shown, the UE assumes that the reported beam is known during a specific period starting from the end codeword of the event-triggered beam report.

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

[0384] According to Embodiment 3-1, by performing beam reporting, it is possible to omit or reduce the time associated with receiving power measurement or the time required for determining or refining the receiving beam (for example, T L1-RSRP ).

[0385] Implementation Method 3-2

[0386] The UE may also use event-triggered beam reporting to report L1-RSRP.

[0387] The UE may also measure specific reference signals (SSB / CSI-RS) associated with the reported beam.

[0388] This specific SSB / CSI-RS may also be, for example, a root SSB. In the present disclosure, a root SSB may also refer to a QCL source (eg, SSB / CSI-RS) to which a QCL source (eg, TRS / CSI-RS) in a TCI state relates.

[0389] The switching / activation delay of the TCI may also include the time required for the measurement of the SSB (e.g., TO k *(T first-SSB +T SSB-proc ) / (NR slot length)).

[0390] When the UE / NW (base station) reports the activated (activated) TCI state in the beam report (when the activated TCI state is the TCI state corresponding to the beam / RS reported in the beam report), it can also be assumed that the time required for SSB measurement (for example, TO k *(T first-SSB +T SSB-proc ) / (NR slot length)) is 0 (it can also be imagined as TO k = 0). In other cases, the UE / NW (base station) may also assume / judge that it is the time required for SSB measurement (for example, TO k ) is determined based on the existing method (specified up to Rel.17).

[0391] Regarding the serving cell or the additional cell (cell to which PCI is added), the formula (for example, TO k *(T first-SSB +T SSB-proc Each parameter included in (NR slot length) / (NR slot length)) and at least one of the known / unknown parameters related to the activation delay may be different.

[0392] Furthermore, for additional cells (e.g., intra-CU or inter-CU), a parameter indicating the additional processing time may be added to the existing activation delay (specified up to Rel. 17). This additional processing time may be based on a configuration for each cell (based on RRC configuration) or may be pre-defined in the specification.

[0393] Parameters related to the time required for SSB measurement (e.g., TO k The value of ) may also be determined / reported based on at least one of event-triggered beam reporting and UE capability reporting. kThe value of is 0 or 1, and can also be determined / reported based on at least one of an event-triggered beam report and a UE capability report. By configuring in this way, the UE can perform operations that depend on whether or not measurements of the root SSB can be started.

[0394] Regarding parameters related to the time required for SSB measurement (e.g., TO k ), it is also possible to report the value of TO using a specific number of bits (e.g., 1 bit) for multiple (e.g., all) beams being reported. k The value of may be 0 or 1, and may also be reported using a specific number of bits (eg, 1 bit) for multiple (eg, all) beams being reported.

[0395] Regarding parameters related to the time required for SSB measurement (e.g., TO k ), it may also be reported using a specific number of bits for each beam being reported (e.g., N bits for N beams). k The value of may be 0 or 1, and may also be reported using a specific number of bits for each beam being reported (eg, N bits for N beams).

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

[0397] In addition, the above-mentioned embodiment 3-1 may also be supported by all UEs, and the above-mentioned embodiment 3-2 may also be supported only by specific UEs.

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

[0399] Supplementary information

[0400] [Notification of Information to UE]

[0401] The notification of arbitrary information (from the network (NW)) (e.g., base station (BS))) to the UE (in other words, the reception of arbitrary information from the BS in the UE) in the above-mentioned embodiment can also be performed using physical layer signaling (e.g., DCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or a combination thereof.

[0402] When the notification is performed through a MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) not specified in existing standards in a MAC subheader.

[0403] In the case where the above-mentioned notification is performed through DCI, the above-mentioned notification may also be performed through a specific field of the DCI, a radio network temporary identifier (Radio Network Temporary Identifier (RNTI)) used in scrambling of a cyclic redundancy check (CRC) bit assigned in the DCI, the format of the DCI, and the like.

[0404] Furthermore, notification of arbitrary information to the UE in the above-mentioned embodiments may be performed periodically, semi-continuously, or aperiodically.

[0405] [Notification of information from UE]

[0406] The notification of arbitrary information from the UE (to the NW) in the above-mentioned embodiment (in other words, the sending / reporting of arbitrary information from the UE to the BS) can also be carried out using physical layer signaling (e.g., UCI), high-layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or a combination thereof.

[0407] When the above notification is performed through MAC CE, the MAC CE can also be identified by including a new LCID that is not specified in the existing standards in the MAC subheader.

[0408] When the notification is performed through UCI, the notification may be sent using PUCCH or PUSCH.

[0409] Furthermore, the notification of arbitrary information from the UE in the above-mentioned embodiments may be performed periodically, semi-continuously, or aperiodically.

[0410] [Regarding the application of each embodiment]

[0411] At least one of the above embodiments may also be applied when a specific condition is met, which may be specified in a standard or notified to the UE / BS using higher layer signaling / physical layer signaling.

[0412] At least one of the above-mentioned embodiments may also be applied only to UEs that report a specific UE capability or support the specific UE capability.

[0413] The specific UE capability may also indicate support for specific processing / operation / control / information for at least one of the above-mentioned embodiments (for example, at least one of event-triggered beam reporting and root SSB measurement).

[0414] In addition, the above-mentioned specific UE capabilities can be capabilities that are applied throughout all frequencies (commonly regardless of frequency), or capabilities for each frequency (for example, one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), or capabilities for each frequency range (for example, Frequency Range 1 (FR1)), FR2, FR3, FR4, FR5, FR2-1, FR2-2), or capabilities for each subcarrier spacing (SubCarrier Spacing (SCS)), or capabilities for each feature set (FS) or feature set per component carrier (FSPC)).

[0415] Furthermore, the specific UE capability may be a capability that applies to all duplex modes (commonly regardless of the duplex mode) or a capability that applies to each duplex mode (eg, time division duplex (TDD) or frequency division duplex (FDD)).

[0416] Furthermore, at least one of the aforementioned embodiments may also be applied when specific information associated with the aforementioned embodiment is configured / activated / triggered by the UE through higher layer signaling / physical layer signaling (or operations of the aforementioned embodiment are performed). For example, the specific information may be information indicating that an activation event triggers a beam report, or any RRC parameter for a specific release (e.g., Rel. 18 / 19).

[0417] The UE may also apply the operations of Rel.15 / 16 / 17, for example, when it does not support at least one of the above-mentioned specific UE capabilities or is not set with the above-mentioned specific information.

[0418] Each embodiment of the present disclosure may also be applied to any of reporting of only L1-RSRP, reporting of only L1-SINR, or reporting of both L1-RSRP and L1-SINR.

[0419] The various embodiments of the present disclosure can also be applied to any one of the TCI state / spatial relationship specified only in Rel.15, the unified TCI state specified only in Rel.17, or the TCI state / spatial relationship specified in Rel.15 and the unified TCI state specified in Rel.17.

[0420] The various embodiments of the present disclosure may also be applied to any one of group-based beam reporting only, non-group-based beam reporting only, or both group-based beam reporting and non-group-based beam reporting.

[0421] Each embodiment of the present disclosure may also be applied to any one of L1 beam reporting of only the serving cell, L1 beam reporting of only the additional cell, and L1 beam reporting of both the serving cell and the additional cell.

[0422] (Supplementary Note A)

[0423] The following inventions are added to one embodiment of the present disclosure.

[0424] [Supplementary Note A-1]

[0425] A terminal having:

[0426] a transmitting unit configured to transmit a beam report based on an event related to at least one of the serving cell and the additional cell; and

[0427] The control unit determines, based on the beam report, an update of a Quasi-Co-Location (QCL) concept.

[0428] [Supplementary Note A-2]

[0429] The terminal as described in Supplement A-1, wherein

[0430] The beam report is sent using a Medium Access Control (MAC) control element or uplink control information.

[0431] [Supplementary Note A-3]

[0432] The terminal as described in Supplement A-1 or Supplement A-2, wherein:

[0433] The control unit updates the QCL assumption after a first period has elapsed since the transmission of the beam report.

[0434] [Supplementary Note A-4]

[0435] A terminal as described in any one of Supplement A-1 to Supplement A-3, wherein:

[0436] The control unit controls reception of downlink control information including a response to the beam report,

[0437] The control unit updates the QCL assumption after a second period has elapsed since the downlink control information was received.

[0438] (Supplementary Note B)

[0439] The following inventions are added to one embodiment of the present disclosure.

[0440] [Supplementary Note B-1]

[0441] A terminal having:

[0442] a transmitting unit configured to transmit a beam report based on an event related to at least one of the serving cell and the additional cell; and

[0443] The control unit, based on the beam report, assumes that the reported beam is known after sending the beam report.

[0444] [Supplementary Note B-2]

[0445] The terminal as described in Supplement B-1, wherein

[0446] The control unit assumes that the reported beam is known during a first period starting after the transmission of the beam report.

[0447] [Supplementary Note B-3]

[0448] The terminal as described in Supplement B-1 or Supplement B-2, wherein:

[0449] The control unit controls reception of downlink control information including a response to the beam report,

[0450] The control unit assumes that the reported beam is known during a second period starting from the reception of the downlink control information.

[0451] [Supplementary Note B-4]

[0452] A terminal as described in any one of Supplement B-1 to Supplement B-3, wherein:

[0453] The control unit performs measurement of a specific reference signal associated with the beam included in the beam report.

[0454] (Wireless Communication System)

[0455] The following describes a configuration of a wireless communication system according to an embodiment of the present disclosure. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.

[0456] Figure 9 This figure shows an example of a schematic configuration of a wireless communication system according to one embodiment. Wireless communication system 1 (also referred to simply as system 1) may be a system that implements communication using Long Term Evolution (LTE) standardized by the Third Generation Partnership Project (3GPP), the fifth-generation mobile communication system New Radio (5GNR), or the like.

[0457] In addition, the wireless communication system 1 may also support dual connectivity between multiple radio access technologies (Radio Access Technologies (RATs)) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may also include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

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

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

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

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

[0462] Each CC may also be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). Macrocell C1 may also be included in FR1, and small cell C2 may also be included in FR2. For example, FR1 may be a frequency band below 6 GHz (below 6 GHz (sub-6 GHz)), and FR2 may be a frequency band higher than 24 GHz (above 24 GHz (above-24 GHz)). In addition, the frequency bands and definitions of FR1 and FR2 are not limited to these. For example, FR1 may also correspond to a frequency band higher than FR2.

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

[0464] Multiple base stations 10 may be connected via wired (e.g., optical fiber based on the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which functions as a host station, may be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which functions as a relay station (relay), may be referred to as an IAB node.

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

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

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

[0468] In the wireless communication system 1 , a radio access scheme based on orthogonal frequency division multiplexing (OFDM) may be used. For example, in at least one of the downlink (DL) and uplink (UL), cyclic prefix OFDM (CP-OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), orthogonal frequency division multiple access (OFDMA), or single carrier frequency division multiple access (SC-FDMA) may be used.

[0469] The radio access scheme may also be referred to as a waveform. In addition, in the wireless communication system 1 , other radio access schemes (eg, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

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

[0472] The PDSCH transmits user data, higher-layer control information, and the System Information Block (SIB). The PUSCH also transmits user data and higher-layer control information. The PBCH also transmits the Master Information Block (MIB).

[0473] The PDCCH may also transmit lower layer control information, which may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information for at least one of the PDSCH and the PUSCH.

[0474] In addition, the DCI that schedules the PDSCH may also be referred to as DL allocation, DL DCI, etc., and the DCI that schedules the PUSCH may also be referred to as UL grant, UL DCI, etc. In addition, the PDSCH may also be rewritten as DL data, and the PUSCH may also be rewritten as UL data.

[0475] PDCCH detection also utilizes control resource sets (CORESETs) and search spaces. A CORESET corresponds to the resources used to search for DCI. A search space corresponds to the search area and search method for PDCCH candidates. A CORESET can be associated with one or more search spaces. The UE can also monitor the CORESETs associated with a search space based on the search space configuration.

[0476] A search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may also be referred to as a search space set. Furthermore, the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" in this disclosure may be interchangeable.

[0477] The PUCCH can also transmit uplink control information (uplink control information (UCI)) including at least one of channel state information (CSI), delivery confirmation information (e.g., also known as hybrid automatic repeat request ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH can also transmit the random access preamble used to establish a connection with a cell.

[0478] In the present disclosure, terms such as downlink and uplink may be expressed without the word “link.” In addition, various channels may be expressed without the word “physical” at the beginning.

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

[0480] For example, a synchronization signal may be at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SSs (PSS, SSS) and PBCHs (and DMRS for the PBCH) may also be referred to as an SS / PBCH block or an SS block (SSB). Furthermore, SSs and SSBs may also be referred to as reference signals.

[0481] In addition, wireless communication system 1 may also transmit a sounding reference signal (SRS) or a demodulation reference signal (DMRS) as an uplink reference signal (UL-RS). DMRS is also called a user terminal-specific reference signal (UE-specific Reference Signal).

[0482] (Base Station)

[0483] Figure 10 This figure illustrates an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission path interface (transmission line interface) 140. Furthermore, one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140 may be provided.

[0484] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also assumed that the base station 10 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0485] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

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

[0487] Transmitter / receiver unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. Baseband unit 121 may also include a transmit processing unit 1211 and a receive processing unit 1212. Transmitter / receiver unit 120 may include a transmitter / receiver, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmit / receive circuits, and the like, as described based on common knowledge in the technical fields involved in this disclosure.

[0488] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit or may be configured as a transmitting unit and a receiving unit. The transmitting unit may also be configured as a transmitting processing unit 1211 and an RF unit 122. The receiving unit may also be configured as a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.

[0489] The transmitting and receiving antenna 130 can be formed of an antenna described based on common knowledge in the technical field to which this disclosure relates, such as an array antenna.

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

[0491] The transmitting and receiving unit 120 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

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

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

[0494] The transmitting and receiving unit 120 (RF unit 122 ) may also perform modulation, filter processing, amplification, etc. on the baseband signal to a radio frequency band, and transmit the signal in the radio frequency band via the transmitting and receiving antenna 130 .

[0495] On the other hand, the transmitting and receiving unit 120 (RF unit 122 ) may also perform amplification, filtering, and demodulation into baseband signals on the radio frequency band signals received via the transmitting and receiving antenna 130 .

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

[0497] The transmitting / receiving unit 120 (measuring unit 123) may also perform measurements related to received signals. For example, the measuring unit 123 may perform radio resource management (RRM) measurements and channel state information (CSI) measurements based on the received signals. The measuring unit 123 may also 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)), and propagation path information (e.g., CSI). The measurement results may also be output to the control unit 110.

[0498] The transmission path interface 140 can also send and receive signals (return signaling) between the devices included in the core network 30 (for example, the network node providing NF), other base stations 10, etc., and can also obtain and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0499] In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 120 , the transmitting and receiving antenna 130 , and the transmission path interface 140 .

[0500] The transmitting and receiving unit 120 may also receive a beam report based on an event related to at least one of the serving cell and the additional cell. The control unit 110 may also determine an update of the Quasi-Co-Location (QCL) assumption based on the beam report (first and second embodiments).

[0501] The transmitting and receiving unit 120 may also receive a beam report based on an event related to at least one of the serving cell and the additional cell. The control unit 110 may also determine, based on the beam report, that the reported beam is known after the beam report is sent (first / third embodiments).

[0502] (User Terminal)

[0503] Figure 11 This figure shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Furthermore, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0504] In addition, in this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it is also assumed that the user terminal 20 also has other functional blocks required for wireless communication. Part of the processing of each unit described below may also be omitted.

[0505] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, a control circuit, and the like that are described based on common knowledge in the technical field to which this disclosure relates.

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

[0507] The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may also include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may include a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, and the like, which are described based on common knowledge in the technical fields involved in this disclosure.

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

[0509] The transmitting and receiving antenna 230 can be formed of an antenna described based on common knowledge in the technical field involved in the present disclosure, such as an array antenna.

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

[0511] The transmitting and receiving unit 220 may also use digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), etc. to form at least one of a transmitting beam and a receiving beam.

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

[0513] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may also include error correction coding), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion and other transmission processing on the bit string to be transmitted, and output a baseband signal.

[0514] Furthermore, whether or not to apply DFT processing may also be determined based on the transform precoding configuration. For a particular channel (e.g., PUSCH), if transform precoding is enabled, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmission process in order to transmit the channel using a DFT-s-OFDM waveform. Otherwise, the transceiver unit 220 (transmit processing unit 2211) may perform DFT processing as part of the aforementioned transmission process.

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

[0516] On the other hand, the transmitting and receiving unit 220 (RF unit 222 ) may also perform amplification, filter processing, and demodulation into a baseband signal on the radio frequency band signal received by the transmitting and receiving antenna 230 .

[0517] The transmitting and receiving unit 220 (receiving processing unit 2212) may also apply receiving processing such as analog-to-digital conversion, FFT processing, IDFT processing (as needed), filter processing, demapping, demodulation, decoding (which may also include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the obtained baseband signal to obtain user data, etc.

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

[0519] In addition, the measurement unit 223 may also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources may also be, for example, non-zero power (NZP) CSI-RS resources. In addition, the measurement unit 223 may also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources may also be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, and the like. In addition, CSI-IM may also be referred to as CSI-Interference Management (IM) and may be interchangeable with Zero Power (ZP) CSI-RS. In addition, in the present disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc. may be interchangeable.

[0520] In addition, the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may also be composed of at least one of the transmitting and receiving unit 220 and the transmitting and receiving antenna 230 .

[0521] The transmitting and receiving unit 220 may also transmit a beam report based on an event related to at least one of the serving cell and the additional cell. The control unit 210 may also determine an update of the Quasi-Co-Location (QCL) assumption based on the beam report (first / second embodiments).

[0522] The beam report may also be sent using a Medium Access Control (MAC) control element or uplink control information (first embodiment).

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

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

[0525] The transmitting and receiving unit 220 may also transmit a beam report based on an event related to at least one of the serving cell and the additional cell. The control unit 210 may also assume, based on the beam report, that the reported beam is known after the beam report is transmitted (first / third embodiments).

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

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

[0528] The control unit 210 may also measure a specific reference signal (eg, a root SSB) associated with the beam included in the beam report (third embodiment).

[0529] (Hardware structure)

[0530] Furthermore, the block diagrams used in the description of the above embodiments illustrate blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. Furthermore, the implementation method of each functional block is not particularly limited. Specifically, each functional block can be implemented using a single device that is physically or logically combined, or by connecting two or more physically or logically separate devices directly or indirectly (e.g., by wired or wireless connections) to implement these multiple devices. A functional block can also be implemented by combining one or more of these devices with software.

[0531] Functions include, but are not limited to, judging, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that implements a transmitting function may also be referred to as a transmitting unit, a transmitter, or the like. Any of these terms are as described above, and the implementation method is not particularly limited.

[0532] For example, a base station, a user terminal, etc. in one embodiment of the present disclosure may also function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 12 This figure shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and user terminal 20 described above can also 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.

[0533] In this disclosure, the terms "device," "circuit," "equipment," "section," and "unit" are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figures, or may exclude some of the devices.

[0534] For example, although only one processor 1001 is shown, multiple processors may be provided. Furthermore, processing may be performed by a single processor, or by two or more processors simultaneously, sequentially, or using other methods. Furthermore, processor 1001 may be implemented using more than one chip.

[0535] The functions of the base station 10 and the user terminal 20 are realized, for example, by reading specific software (program) into hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0536] Processor 1001 controls the entire computer by, for example, operating an operating system. Processor 1001 may also be comprised of a central processing unit (CPU) including interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, at least a portion of the aforementioned control unit 110 (210) and transceiver unit 120 (220) may also be implemented by processor 1001.

[0537] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes based on these programs. As a program, a program that causes a computer to execute at least a portion of the operations described in the above embodiments can be used. For example, the control unit 110 (210) can also be implemented by a control program stored in the memory 1002 and executed by the processor 1001, and the other functional blocks can also be implemented similarly.

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

[0539] Storage 1003 may also be a computer-readable recording medium, such as at least one of a flexible disk, a floppy disk, an optical disk (such as a compact disk (Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (such as a card, a stick, or 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.

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

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

[0542] Furthermore, the processor 1001, memory 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured as a single bus or may be configured as different buses between the devices.

[0543] Furthermore, the base station 10 and user terminal 20 may also 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 may use this hardware to implement part or all of each functional block. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0544] (Variation)

[0545] In addition, the terms described in this disclosure and the terms required for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be replaced with each other. In addition, a signal may also be a message. Reference Signal (RS) may also be referred to as RS, and may also be referred to as Pilot, Pilot Signal, etc. depending on the applied standard. In addition, Component Carrier (CC) may also be referred to as Cell, Frequency Carrier, Carrier Frequency, etc.

[0546] A radio frame can also be composed of one or more time periods (frames) in the time domain. Each of these one or more time periods (frames) that make up a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (for example, 1ms) that is independent of the numerology.

[0547] Here, a parameter set may also refer to communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, the parameter set may also represent at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), the number of symbols per TTI, radio frame structure, specific filtering processing performed by the transmitter and receiver in the frequency domain, and specific windowing processing performed by the transmitter and receiver in the time domain.

[0548] In the time domain, a slot can also be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) Furthermore, a slot can also be a time unit based on a parameter set.

[0549] A time slot may also contain multiple mini-slots. Each mini-slot may also consist of one or more symbols in the time domain. Furthermore, a mini-slot may also be referred to as a sub-slot. A mini-slot may also consist of fewer symbols than a time slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may also be referred to as PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-slots may also be referred to as PDSCH (PUSCH) mapping type B.

[0550] Radio frames, subframes, time slots, mini-slots, and symbols all represent time units used for signal transmission. Radio frames, subframes, time slots, mini-slots, and symbols may also be referred to by their respective equivalents. Furthermore, the time units of frame, subframe, time slot, mini-slot, and symbol in this disclosure may be interchangeable.

[0551] For example, a subframe can be called a TTI, multiple consecutive subframes can be called a TTI, and a slot or a mini-slot can be called a TTI. That is, at least one of a subframe and a TTI can 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. Furthermore, the unit representing a TTI can be called a slot, a mini-slot, or the like, rather than a subframe.

[0552] Here, TTI refers to, for example, the minimum time unit used for scheduling in wireless communications. For example, in the LTE system, a base station schedules each user terminal by allocating radio resources (such as the frequency bandwidth and transmit power available to each user terminal) in TTI units. The definition of TTI is not limited to this.

[0553] A TTI can also be a unit of time for transmitting channel-coded data packets (transport blocks), code blocks, code words, etc., and can also be a unit of processing for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, code block, code word, etc. is actually mapped can be shorter than the TTI.

[0554] Furthermore, while a time slot or mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more time slots or one or more mini-slots) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-slots) that constitute this minimum time unit for scheduling can also be controlled.

[0555] A TTI with a time length of 1 ms may also be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a time slot, etc. A TTI shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a time slot, etc.

[0556] In addition, a long TTI (e.g., normal TTI, subframe, etc.) can also be rewritten as a TTI with a time length exceeding 1ms, and a short TTI (e.g., shortened TTI, etc.) can also be rewritten as a TTI with a TTI length shorter than the long TTI and longer than 1ms.

[0557] A resource block (RB) is a unit of resource allocation in the time and frequency domains. In the frequency domain, it may also include one or more consecutive subcarriers (subcarriers). The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0558] In addition, an RB may also include one or more symbols in the time domain, and may also be the length of a slot, a mini-slot, a subframe, or a TTI. A TTI, a subframe, etc. may also be composed of one or more resource blocks.

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

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

[0561] A Bandwidth Part (BWP) (also referred to as a fractional bandwidth) can also represent a subset of contiguous common resource blocks (RBs) used for a particular parameter set within a carrier. Common RBs can also be identified by their index relative to the common reference point for that carrier. PRBs can also be defined within a BWP and numbered within that BWP.

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

[0563] At least one of the configured BWPs may be activated, and the UE may not assume that it will transmit or receive specific signals / channels outside of the activated BWP. In addition, the terms "cell," "carrier," and the like in this disclosure may also be rewritten as "BWP."

[0564] The above-mentioned structures of radio frames, subframes, slots, mini-slots, and symbols are merely examples. For example, the number of subframes in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots within a slot, the number of symbols and RBs within a slot or mini-slot, the number of subcarriers within an RB, the number of symbols within a TTI, the symbol length, and the cyclic prefix (CP) length can be varied in various ways.

[0565] Furthermore, the information and parameters described in this disclosure may be expressed as absolute values, relative values ​​relative to a specific value, or other corresponding information. For example, wireless resources may be indicated by specific indexes.

[0566] The names used for parameters, etc. in this disclosure are not intended to be limiting in any respect. Furthermore, the mathematical formulas used for these parameters may differ from those explicitly disclosed in this disclosure. Various channels (such as PUCCH and PDCCH) and information elements can 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 respect.

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

[0568] Furthermore, information, signals, etc. can be output in at least one of the following directions: from a higher layer (upper layer) to a lower layer (lower layer), and from a lower layer to a higher layer. Information, signals, etc. can also be input and output via multiple network nodes.

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

[0570] The notification of information is not limited to the methods / implementations described in this disclosure and may also be performed using other methods. For example, the notification of information in this disclosure may also be implemented through physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI)), uplink control information (Uplink Control Information (UCI))), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB)), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof.

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

[0572] Furthermore, notification of specific information (eg, notification of “it is X”) is not limited to explicit notification, but may be performed implicitly (eg, by not notifying the specific information or by notifying other information).

[0573] The determination can be made using a value represented by a bit (0 or 1), a true or false value (Boolean value) represented by true or false, or a numerical comparison (eg, comparison with a specific value).

[0574] The term “software” or “firmware” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, sub-programs, software modules, applications, software applications, software packages, routines, sub-routines, objects, executable files, execution threads, procedures, functions, etc.

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

[0576] The terms "system" and "network" used in this disclosure are interchangeable. "Network" may also refer to devices included in the network (eg, base stations).

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

[0578] Furthermore, in the present disclosure, antenna ports can be interchanged with antenna ports used for any signal / channel (e.g., Demodulation Reference Signal (DMRS) ports). In the present disclosure, resources can be interchanged with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Furthermore, resources can include time / frequency / code / space / power resources. Furthermore, spatial domain transmit filters can include at least one of spatial domain transmission filters and spatial domain reception filters.

[0579] The above-mentioned group may also 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 (for example, a DMRS port group), a layer group, a resource group, a beam group, an antenna group, a panel group, etc.

[0580] In addition, in the present disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, codeword (CW), transport block (TB), RS, etc. can also be rewritten.

[0581] In addition, in the present disclosure, TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state (unified TCI state), common TCI state (common TCI state), joint TCI state, etc. can also be rewritten with each other.

[0582] In addition, in the present disclosure, "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL characteristics (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) characteristics", "specific QCL type (e.g., type A, type D)", etc. can also be rewritten with each other.

[0583] In the present disclosure, index, identifier (ID), indicator, indication, resource ID, etc. can also be overwritten with each other. In the present disclosure, sequence, list, set, group, cluster, subset, etc. can also be overwritten with each other.

[0584] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and spatial relationship information (TCI state) can also be overwritten. "Spatial relationship information (TCI state)" can also be overwritten with "a collection of spatial relationship information (TCI state)," "one or more spatial relationship information," and so on. TCI states and TCIs can also be overwritten. Spatial relationship information and spatial relationships can also be overwritten.

[0585] In this disclosure, terms such as "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP))", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" are used interchangeably. In some cases, a base station may be referred to as a macrocell, small cell, femtocell, or picocell.

[0586] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the base station's overall coverage area can be divided into multiple smaller areas, each of which can be provided with communications services by a base station subsystem (for example, a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or the entire coverage area of ​​at least one of a base station and a base station subsystem providing communications services within that coverage area.

[0587] In the present disclosure, the base station sending information to the terminal and the base station instructing the terminal to perform control / operation based on the information may be mutually rewritten.

[0588] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user device (UE)”, and “terminal” can be used interchangeably.

[0589] 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, hand set, user agent, mobile client, client, or several other appropriate terms.

[0590] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. In addition, at least one of the base station and the mobile station may also be a device mounted on a moving object, a moving object body, etc.

[0591] The mobile body refers to a movable object, and the moving speed is arbitrary, including the case where the mobile body stops. The mobile body includes, for example, vehicles, transport vehicles, cars, automatic two-wheeled vehicles (motorcycles), bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (ships and other watercrafts), airplanes, rockets, artificial satellites, drones, multi-rotor aircraft, quadcopters, balloons, and objects carried by them, but is not limited to these. In addition, the mobile body can also be a mobile body that moves autonomously based on operation instructions.

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

[0593] Figure 13This figure shows an example of a vehicle according to one embodiment. Vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a rotation speed 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.

[0594] The drive unit 41 is composed of, for example, at least one of an engine, a motor, or a combination of an engine and a motor. The steering unit 42 is configured to include at least a steering wheel (also referred to as a handlebar), and steers at least one of the front wheels 46 and the rear wheels 47 based on user manipulation of the steering wheel.

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

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

[0597] Information service unit 59 is comprised of various devices, such as a vehicle navigation system, audio system, speakers, display, television, and radio, for providing (outputting) various information, including driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. Information service unit 59 uses information obtained from external devices via communication module 60 and the like to provide various information and services (e.g., multimedia information and multimedia services) to vehicle 40 occupants.

[0598] The information service unit 59 may include an input device for accepting input from the outside (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.), or an output device for outputting to the outside (e.g., a display, a speaker, an LED light, a touch panel, etc.).

[0599] The driving assistance system unit 64 is composed of various devices for providing functions for preventing accidents or reducing the driver's driving load, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning sensors (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., high-precision (High Definition (HD)) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., inertial measurement units (IMUs)), inertial navigation systems (INSs), etc.), artificial intelligence (AI) chips, AI processors, and one or more ECUs that control these devices. Furthermore, the driving assistance system unit 64 transmits and receives various information via the communication module 60 to implement driving assistance functions or autonomous driving functions.

[0600] 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 between the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, the microprocessor 61 in the electronic control unit 49, the memory (ROM, RAM) 62, and the various sensors 50-58 included in the vehicle 40.

[0601] The communication module 60 is controlled by the microprocessor 61 of the electronic control unit 49 and is a communication device capable of communicating with external devices. For example, various information can be transmitted and received between external devices via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. Examples of external devices include the aforementioned base station 10 and user terminal 20. Furthermore, the communication module 60 can also be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or can function as at least one of the base station 10 and user terminal 20).

[0602] The communication module 60 may also transmit at least one of the following: signals input to the electronic control unit 49 from the various sensors 50-58, information obtained based on these signals, and information based on external (user) input received 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, and the like may also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 may also include information based on these inputs.

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

[0604] Furthermore, the communication module 60 stores various information received from external devices in a memory 62 that can be used by the microprocessor 61. The microprocessor 61 can also 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, included in the vehicle 40, based on the information stored in the memory 62.

[0605] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, the various methods / implementations of this disclosure can also be applied to a structure in which communication between a base station and a user terminal is replaced by communication between multiple user terminals (e.g., device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, the user terminal 20 can also have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" can also be rewritten with terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channels, downlink channels, etc. can also be rewritten as sidelink channels.

[0606] Likewise, the user terminal in the present disclosure may be rewritten as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.

[0607] In this disclosure, operations are described as being performed by a base station, and sometimes by its upper node, depending on circumstances. Obviously, in a network including one or more network nodes including 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 (for example, but not limited to, a Mobility Management Entity (MME) and a Serving-Gateway (S-GW)), or a combination thereof.

[0608] The various methods / implementations described in this disclosure may be used individually or in combination, and may be switched between them during execution. Furthermore, the processing procedures, sequences, flow charts, and the like of the various methods / implementations described in this disclosure may be reversed as long as they do not conflict. For example, the methods described in this disclosure use an illustrative order to present elements of various steps, but are not limited to the specific order presented.

[0609] The various modes and embodiments described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), systems utilizing other appropriate wireless communication methods, and next-generation systems based on enhancements, modifications, developments, or regulations of these systems. Furthermore, multiple systems may be combined for application (for example, LTE or LTE-A combined with 5G).

[0610] The phrase “based on” used in this disclosure does not mean “based only on” unless otherwise specified. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0611] Any reference to an element using the designations "first," "second," etc., as used in this disclosure, does not necessarily define the quantity or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to a first and a second element does not imply that only two elements may be used or that the first element must in some way take precedence over the second element.

[0612] The term "determining" as used in this disclosure may encompass a variety of operations. For example, "determining" may also include judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching a table, database, or other data structure), ascertaining, and the like as performing a "determination."

[0613] In addition, “judgment (decision)” may also refer to situations where receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc. are regarded as “judgment (decision)”.

[0614] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, and comparing are considered "judgment (decision)." In other words, "judgment (decision)" can also refer to situations where certain operations are considered "judgment (decision)." In this disclosure, "judgment (decision)" can be interchanged with the aforementioned operations.

[0615] In this disclosure, "determine / determining" can be interchanged with "assume / assuming," "expect / expecting," "consider / considering," and the like. Furthermore, in this disclosure, "do not assume..." can be interchanged with "do not assume...".

[0616] In the present disclosure, "expect" can be replaced with "be expected". For example, "expect(s)..." ("..." can also be expressed, for example, using a that clause, a to-infinitive, etc.) can be replaced with "be expected...". "Does not expect..." can also be replaced with "Does not expect...". In addition, "An apparatus A is not expected..." can also be replaced with "An apparatus B other than apparatus A does not expect apparatus A..." (for example, when apparatus A is a UE, apparatus B can also be a base station).

[0617] The “maximum transmit power” described in the present disclosure may refer to the maximum value of the transmit power, the nominal maximum transmit power (the nominal UE maximum transmit power), or the rated maximum transmit power (the rated UE maximum transmit power).

[0618] As used in this disclosure, the terms "connected," "coupled," and all variations 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 the two elements being "connected" or "coupled." The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" can also be rephrased as "accessed."

[0619] In the present disclosure, when two elements are connected, it is possible to consider them to be "connected" or "combined" to each other using one or more wires, cables, printed electrical connections, etc., and as several non-limiting and non-inclusive examples, they are "connected" or "combined" to each other using electromagnetic energy having a wavelength in the wireless frequency domain, microwave region, light (both visible and invisible) region, etc.

[0620] In the present disclosure, the term "A is different from B" may also mean "A and B are different from each other." Alternatively, the term may also mean "A and B are each different from C." Terms such as "separate" and "bound" may also be interpreted in the same manner as "different."

[0621] When used in this disclosure, "include," "including," and variations thereof have the same inclusive meaning as the term "comprising." Furthermore, the term "or" used in this disclosure does not mean an exclusive OR.

[0622] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure may also include a case where the noun following the article is in a plural form.

[0623] In the present disclosure, “below,” “less than,” “above,” “more than,” “equal to,” and the like may be replaced with each other. Furthermore, in the present disclosure, sentences meaning “good (excellent),” “poor,” “big,” “small,” “high,” “low,” “early,” “late,” “wide,” “narrow,” and the like may be replaced with each other without being limited to the positive, comparative, and superlative forms. Furthermore, in the present disclosure, sentences meaning “good (excellent),” “poor,” “big,” “small,” “high,” “low,” “early,” “late,” “wide,” “narrow,” and the like may be replaced with each other as expressions appended with “ith” (i is an arbitrary integer) without being limited to the positive, comparative, and superlative forms (for example, “highest” may be replaced with “ith highest”).

[0624] In the present disclosure, “of,” “for,” “regarding,” “related to,” “associated with,” etc. may also be replaced with each other.

[0625] In this disclosure, expressions 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 / on A," "B after A," "B since A," and "B until A" can be interchanged. Furthermore, A, B, and the like can be replaced with nouns, gerunds, or other appropriate expressions depending on the context. The time difference between A and B can be approximately zero (immediately after or immediately before). Furthermore, a time offset can be applied to the time when A occurs. For example, "A" can be interchanged with "before / after the time offset when A occurs." The time offset (eg, one or more symbols / time slots) may be predetermined or determined by the UE based on notified information.

[0626] In the present disclosure, timing, moment, time, time instance, arbitrary time unit (eg, time slot, sub-time slot, symbol, sub-frame), period, opportunity (occasion), resource, etc. may also be interchangeably written.

[0627] While the inventions disclosed herein have been described in detail above, it will be apparent to those skilled in the art that the inventions disclosed herein are not limited to the embodiments described herein. The disclosure herein is provided for illustrative purposes only and is not intended to limit the inventions disclosed herein.

Claims

1. A terminal comprising: a transmitting unit configured to transmit a beam report based on an event related to at least one of the serving cell and the additional cell; and The control unit, based on the beam report, assumes that the reported beam is known after sending the beam report.

2. The terminal according to claim 1, wherein: The control unit assumes that the reported beam is known during a first period starting after the transmission of the beam report.

3. The terminal according to claim 1, wherein: The control unit controls reception of downlink control information including a response to the beam report, The control unit assumes that the reported beam is known during a second period starting from the reception of the downlink control information. The terminal according to claim 1 , wherein: The control unit performs measurement of a specific reference signal associated with the beam included in the beam report.

5. A wireless communication method for a terminal, comprising: The step of transmitting a beam report based on an event related to at least one of the serving cell and the additional cell; and Based on the beam report, it is assumed that the reported beam is a known step after the sending of the beam report.

6. A base station comprising: a receiving unit configured to receive a beam report based on an event related to at least one of the serving cell and the additional cell; and The control unit determines, based on the beam report, that the reported beam is known after the beam report is sent.