Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives a setting related to a trigger condition that supports a combination of a plurality of events for event-based beam reporting, and a control unit that controls the event-based beam reporting based on the setting, and applies a specific operation in a case where a condition for a time to trigger (TTT) until triggering is satisfied in addition to the trigger condition.

Description

Technical Field

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

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

[0003] The development of successor systems to LTE is also underway (e.g., also known as the 5th generation mobile communication system (5G), 5G+, the 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.).

[0004] Existing technical documents

[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] The problem that the invention aims to solve

[0008] In future wireless communication systems (e.g., NR), research is underway on using L1L2-triggered mobility (LTM) as specified in Rel.18 when terminals (user terminals, user equipment (UE)) move between cells.

[0009] In mobility scenarios after Rel.19, a wide variety of use cases can be envisioned. For example, in industrial communication systems, remote control of industrial equipment and factory automation could be examples. Furthermore, in real-time interactive services, AI-based / XR services could be cited.

[0010] Furthermore, research is underway into supporting event-based beam reporting in future wireless communication systems.

[0011] Triggered beam reporting is supported in MIMO / mobility versions after Rel.19. Furthermore, conditional handover (CHO) is also supported as a mobility mechanism.

[0012] That is, event-triggered beam reports can be used for measurement reporting / beam switching / cell switching.

[0013] On the other hand, it is envisioned that the types of beam reports supported for each use case are different.

[0014] For example, in event-triggered beam reporting for MIMO in Rel.19, Type 1 / Type 2-1 beam reporting is supported. In event-triggered beam reporting for mobility in Rel.19, Type 2-2 beam reporting is supported.

[0015] However, research on the specifications related to event-based beamforming reporting corresponding to the applied use cases is insufficient. This lack of research hinders the achievement of lower latency communication and raises concerns about inhibiting improvements in communication quality / throughput.

[0016] Therefore, one of the purposes of this disclosure is to provide terminals, wireless communication methods, and base stations that can improve communication quality / throughput.

[0017] Methods for solving problems

[0018] One aspect of this disclosure relates to a terminal comprising: a receiving unit that receives settings related to trigger conditions supporting a combination of multiple events for event-based beam reporting; and a control unit that, based on the settings, controls the event-based beam reporting, wherein, in addition to the trigger conditions, a condition for the time to trigger (Time to trigger: TTT) is also satisfied, and the control unit applies a specific operation.

[0019] Invention Effects

[0020] According to one method disclosed herein, it is possible to improve communication quality / throughput. Attached Figure Description

[0021] Figure 1A as well as Figure 1B This illustrates an example of a unified / public TCI framework.

[0022] Figure 2A as well as Figure 2B An example of a DCI-based TCI status indication is shown.

[0023] Figure 3 This is a diagram illustrating an example of the timeline for the switching / activation of the TCI state as specified up to Rel. 15 / 16.

[0024] Figure 4 This is a diagram illustrating an example of the TCI status specified up to Rel.16.

[0025] Figure 5A This is a diagram illustrating an example of UE movement in Rel.17. Figure 5B This is a diagram illustrating an example of UE movement in Rel.18.

[0026] Figure 6 This is a flowchart illustrating an example of event-based beam reporting processing.

[0027] Figure 7 This is a diagram illustrating an example of event-based beam reporting.

[0028] Figure 8 This is a diagram illustrating an example of an event involved in the first embodiment.

[0029] Figure 9 This is a diagram illustrating an example of the correspondence between the combination of events involved in Mode 2-1 and the time up to the trigger.

[0030] Figure 10 This is a diagram illustrating an example of the operation of event-based beam reporting according to the third embodiment.

[0031] Figure 11 This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment.

[0032] Figure 12 This is a diagram illustrating an example of the structure of a base station according to one embodiment.

[0033] Figure 13 This is a diagram illustrating an example of the structure of a user terminal according to one embodiment.

[0034] Figure 14 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment.

[0035] Figure 15 This is a diagram illustrating an example of a vehicle according to one embodiment. Detailed Implementation

[0036] (CSI Report)

[0037] In NR, the UE uses a specific reference signal (or the resources used by that reference signal) to measure the channel state and feeds back (reports) the Channel State Information (CSI) to the base station.

[0038] The UE can also use Channel State Information-Reference Signal (CSI-RS), Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, Synchronization Signal (SS), DeModulation Reference Signal (DMRS), etc., to measure channel state.

[0039] CSI-RS resources can also include at least one Non-Zero Power (NZP) CSI-RS and CSI Interference Management (IM). An SS / PBCH block is a block containing synchronization signals (e.g., Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS)) and PBCH (and the corresponding DMRS), and can also be referred to as an SS block (SSB), etc. An SSB index can also be assigned to the time position of the SSB within a half-frame.

[0040] Additionally, CSI can also include Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), Layer 1 (L1) Reference Signal Received Power (RSRP) (the power of the reference signal received in Layer 1), L1 Reference Signal Received Quality (RSRQ), L1 Signal to Interference plus Noise Ratio (SINR), and L1 Signal to Noise Ratio (SNR). At least one of the following: Ratio (SNR).

[0041] A CSI can also have multiple parts. The first part of the CSI (CSI Part 1) can also contain relatively few bits of information (e.g., RI). The second part of the CSI (CSI Part 2) can also contain relatively many bits of information, such as information determined based on CSI Part 1 (e.g., CQI).

[0042] As feedback methods for CSI, research is underway on (1) periodic CSI (P-CSI) reports, (2) aperiodic CSI (A(AP)-CSI) reports, and (3) semi-permanent CSI (SP-CSI) reports.

[0043] The UE may also be notified of information related to CSI reports (also known as CSI report configuration information) using higher-layer signaling, physical-layer signaling (e.g., downlink control information (DCI)) or a combination thereof. CSI report configuration information may also be configured, for example, using the RRC information element "CSI-ReportConfig".

[0044] CSI report configuration information may include information related to reporting period, offset, etc., which can be expressed in specific time units (slot units, subframe units, symbol units, etc.). CSI report configuration information may also include a configuration ID (CSI-ReportConfigId). This configuration ID can be used to determine parameters such as the type of CSI reporting method (whether it is SP-CSI, etc.) and the reporting period. CSI report configuration information may also include information indicating which signal (or resource used by which signal) was used to report the measured CSI (CSI-ResourceConfigId).

[0045] (TCI, Spatial Relations, QCL)

[0046] In NR, research is underway on controlling the reception processing (e.g., at least one of receiving, demapping, demodulation, and decoding) and transmission processing (e.g., at least one of transmitting, mapping, precoding, modulation, and encoding) of at least one of the signals and channels (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0047] TCI states can also represent the states of signals / channels applied to the downlink. States equivalent to the TCI states of signals / channels applied to the uplink can also be described as spatial relations.

[0048] The so-called TCI status refers to information related to the quasi-co-location (QCL) of a signal / channel, and can also be called spatial reception parameters, spatial relation information, etc. The TCI status can also be set to the UE on a per-channel or per-signal basis.

[0049] QCL is an indicator of the statistical properties of a signal / channel. For example, it can also mean that, given a QCL relationship between a signal / channel and other signals / channels, it can be assumed that at least one of the following is the same among these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter). (The QCL refers to at least one of these parameters.)

[0050] Additionally, the spatial reception parameters may also correspond to the UE's receive beam (e.g., receive analog beam), and the beam may also be determined based on the spatial QCL. The QCL (or at least one element of the QCL) in this disclosure may also be rewritten as sQCL (spatial QCL).

[0051] Regarding QCL, multiple types (QCL types) can also be specified. For example, four QCL types AD can be set, in which the parameters (or parameter sets) that can be assumed to be the same are different. These parameters (also referred to as QCL parameters) are represented as follows: • QCL Type A (QCL-A): Doppler shift, Doppler spread, average delay, and delay spread. • QCL Type B (QCL-B): Doppler shift and Doppler extension, • QCL Type C (QCL-C): Doppler shift and average delay, • QCL Type D (QCL-D): Spatial reception parameters.

[0052] The information of QCLs as shown in QCL types A to D above can also be referred to as QCL properties.

[0053] The situation in which a UE envisions a certain Control Resource Set (CORESET), channel, or reference signal in a specific QCL (e.g., QCL type D) relationship with other CORESETs, channels, or reference signals can also be referred to as a QCL assumption.

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

[0055] TCI status can also be, for example, information related to the QCL between the target channel (in other words, the reference signal (RS) used by the channel) and other signals (e.g., other RS). TCI status can also be set (indicated) by higher layer signaling, physical layer signaling, or a combination thereof.

[0056] Physical layer signaling can also be, for example, downlink control information (Downlink Control Information (DCI)).

[0057] The channel that is set (specified) to TCI state or spatial relationship can be, for example, at least one of the following: downlink shared channel (Physical Downlink Shared Channel (PDSCH))), downlink control channel (Physical Downlink Control Channel (PDCCH))), uplink shared channel (Physical Uplink Shared Channel (PUSCH))), and uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0058] Furthermore, the RS that is related to the channel as QCL can be at least one of the following: a Synchronization Signal Block (SSB), a Channel State Information Reference Signal (CSI-RS), a Measurement Reference Signal (Sounding Reference Signal (SRS)), a Tracking CSI-RS (also known as a Tracking Reference Signal (TRS)), or a QCL Detection Reference Signal (also known as a QRS).

[0059] An SSB is a block of signals that contains at least one Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and broadcast channel (Physical Broadcast Channel (PBCH)). An SSB can also be referred to as an SS / PBCH block.

[0060] The RS of QCL type X in TCI state can also refer to the RS that is in a relationship of QCL type X with a certain channel / signal (DMRS), and this RS can also be called the QCL source of QCL type X in TCI state.

[0061] (Unified / Common TCI Framework)

[0062] According to the unified TCI framework, multiple (UL / DL) channels / RS can be controlled through a common framework. Regarding the unified TCI framework, instead of specifying TCI states or spatial relationships for each channel as in Rel.15, it can both indicate a common beam (common TCI state) and apply it to all channels of UL and DL, or apply the common beam used by UL to all channels of UL and the common beam used by DL to all channels of DL.

[0063] We are researching a common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (overall, two common beams).

[0064] The UE can also envision 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 can also envision different TCI states for UL and DL respectively (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

[0065] UL and DL default beam alignment can also be achieved through MAC CE-based beam management (MAC CE-level beam indication). The default TCI state of the PDSCH can also be updated and matched with the default UL beam (spatial relationship).

[0066] Alternatively, a common beam / unified TCI state can be indicated from the same TCI pool (joint common TCI pool, joint TCI pool, set) used by both UL and DL through DCI-based beam management (DCI-level beam indication). X (>1) TCI states can also be activated via MAC CE. UL / DL DCI can also select one from X active TCI states. The selected TCI state can also be applied to the channels / RS of both UL and DL.

[0067] A TCI pool (set) can be either multiple TCI states set via RRC parameters, or multiple TCI states activated via MAC CE (activating a TCI state, activating a TCI pool, or a set) among multiple TCI states set via RRC parameters. Each TCI state can also be a QCL type A / D RS. As a QCL type A / D RS, it can also be set as SSB, CSI-RS, or SRS.

[0068] The number of TCI states corresponding to each of more than one TRP can also be specified. For example, the number of TCI states (UL TCI states) applied in the UL channel / RS (≥1) and the number of TCI states (DL TCI states) applied in the DL channel / RS (≥1) can also be specified. At least one of N and M can also be notified / set / indicated to the UE via higher-layer signaling / physical layer signaling.

[0069] In this disclosure, when N = M = X (where X is any integer), it can also mean that the UE is notified / set / indicated X TCI states (corresponding to X TRPs) common to UL and DL (joint TCI states). Furthermore, when N = X (where X is any integer) and M = Y (where Y is any integer, or Y = X), it can also mean that the UE is notified / set / indicated X UL TCI states (corresponding to X TRPs) and Y DL TCI states (corresponding to Y TRPs) separately (i.e., independent TCI states).

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

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

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

[0073] Furthermore, for example, when N=2 and M=2 are recorded, it may also mean that the UE is notified / set / instructed to have multiple (two) UL TCI states and multiple (two) DL TCI states (independent TCI states for multiple TRPs) for multiple (two) TRPs.

[0074] Furthermore, the above example illustrates the case where N and M have values ​​of 1 or 2, but the values ​​of N and M can also be 3 or higher, and N and M can also be different.

[0075] Support for N=M=1 in Rel.17 is under investigation. For example, it would also be possible to support indicating a common beam (e.g., common beam) via RRC / MAC CE / DCI, and having this common beam applied to the channels / reference signals of multiple DL / UL. Furthermore, other scenarios could be supported in Rel.18 and later.

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

[0077] exist Figure 1A In the example, the RRC parameter (information element) sets multiple TCI states for both DL and UL. In this disclosure, the TCI state set via the RRC parameter can also be referred to as a configured TCI state or a TCI state (e.g., configured TCI states). The MAC CE can also activate multiple TCI states among the configured TCI states. The DCI can also indicate one of the activated TCI states. In this disclosure, the TCI state indicated via the DCI can also be referred to as an indicated TCI state or an indicated TCI state (e.g., indicated TCI state).

[0078] A DCI can be a UL DCI (e.g., a DCI used for PUSCH scheduling) or a DL DCI (e.g., a DCI used for PDSCH scheduling). The indicated TCI state can also be applied to at least one (or all) of the UL / DL channels / RS. A DCI can also indicate both the UL TCI and the DL TCI.

[0079] In the example in the diagram, a point can be either a TCI state applied to both UL and DL, or two TCI states applied to UL and DL respectively.

[0080] At least one of the multiple TCI states set by RRC parameters and the multiple TCI states activated by MAC CE can also be referred to as a TCI pool (common TCI pool, joint TCI pool, TCI state pool). Multiple TCI states activated by MAC CE can also be referred to as an activated TCI pool (activated common TCI pool).

[0081] Furthermore, in this disclosure, the high-level parameters (RRC parameters) for setting multiple TCI states can also be referred to as setting information for setting multiple TCI states, or simply as "setting information". Additionally, in this disclosure, using a DCI to indicate one of the multiple TCI states can either involve receiving indication information contained in the DCI indicating one of the multiple TCI states, or it can involve only receiving the "indication information".

[0082] exist Figure 1B In the example, the RRC parameter sets multiple TCI states (joint common TCI pool) for both DL and UL. MAC CE can also activate multiple TCI states (activate TCI pools) among the set multiple TCI states. It can also be set / activated to activate separate, independent TCI pools for UL and DL respectively.

[0083] The DL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) DL channels / RS. The DL channel can also be PDCCH / PDSCH / CSI-RS. The UE can also use the Rel.16 TCI state operation (TCI framework) to determine the TCI state of each DL channel / RS. The UL DCI or new DCI format can also select (indicate) more than one (e.g., one) TCI state. The selected TCI state can also be applied to more than one (or all) UL channels / RS. The UL channel can also be PUSCH / SRS / PUCCH. Thus, different DCIs can separately indicate the UL TCI and the DL DCI.

[0084] From Rel.17 NR onwards, it is envisioned that support will be provided via MAC CE / DCI for beam activation / indication to TCI states associated with different physical cell identifiers (PCIs). Furthermore, from Rel.18 NR onwards, it is envisioned that support will be provided via MAC CE / DCI for indicating changes to serving cells with different PCIs.

[0085] Figure 1A The method for setting / indicating the TCI status (e.g., combined DL / UL TCI status), and Figure 1B The application of the TCI state (e.g., standalone TCI state) can also be switched. The choice between the joint DL / UL TCI state and the standalone TCI state can also be set by the base station for the UE via higher-layer parameters.

[0086] (TCI status indication)

[0087] The Rel.17 Unified TCI framework supports the following modes 1 through 3.

[0088] [Mode 1] TCI state indication based on MAC CE

[0089] [Mode 2] DCI-based TCI state indication with DL assignment (DCI based TCI state indication by DCI format 1_1 / 1_2 with DL assignment)

[0090] [Mode 3] DCI-based TCI state indication without DL assignment (DCI based TCI state indication by DCI format 1_1 / 1_2 without DL assignment)

[0091] A UE receiving a CC that is set 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 a given CC. Alternatively, it 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 set by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2). Regarding DCI format 1_1 / 1_2, it may or may not be accompanied by DL allocation if DL allocation is available.

[0092] In the absence of DL allocation for DCI format 1_1 / 1_2, the UE can envision (verify) the following for this DCI.

[0093] - CS-RNTI is used for scrambling CRC in DCI.

[0094] - The following DCI field (special field) values ​​are set as follows: - The redundant version (RV) field is all '1's.

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

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

[0097] - 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 DynamicSwitch (same as the validation of the released PDCCH for DL ​​semi-persistent scheduling (SPS) or UL license type 2 scheduling).

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

[0099] In Rel.15 / 16, the UE ignores the BWP indicator field if it does not support activation of BWP changes via DCI. The same approach is being investigated regarding the relationship between Rel.17 TCI state support and the interpretation of the TCI field. It is being investigated that, when the UE is configured with the Rel.17 TCI state, the TCI field is always present in DCI format 1_1 / 1_2, and the UE ignores the TCI field if it does not support TCI updates via DCI.

[0100] In Rel.15 / 16, the presence of the TCI field (TCI presence information within DCI, tci-PresentInDCI) is set per CORESET.

[0101] In DCI format 1_1, the TCI field is 0 bits if the higher-layer parameter tci-PresentInDCI is not set to valid, and 3 bits otherwise. When the BWP indicator field indicates that a BWP other than the active BWP is activated, the UE follows these steps.

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

[0103] In DCI format 1_2, the TCI field is 0 bits if the higher-layer parameter tci-PresentInDCI-1-2 is not set to valid; otherwise, it is 1, 2, or 3 bits, determined by the higher-layer parameter tci-PresentInDCI-1-2. If the BWP indicator field indicates that a BWP other than BWP is activated, the UE follows the procedure below.

[0104] [Operation] If the higher-layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH transmitting DCI format 1_2, the UE assumes that tci-PresentInDCI is not set to valid for all CORESETs within the indicated BWP. Otherwise, the UE assumes that tci-PresentInDCI-1-2 is set with the same value as tci-PresentInDCI-1-2 set for the CORESET used in the PDCCH transmitting DCI format 1_2.

[0105] Figure 2A This illustrates an example of a DCI-based joint DL / UL TCI status indication. The value of the TCI field used for the joint DL / UL TCI status indication is associated with a TCI status ID representing the joint DL / UL TCI status.

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

[0107] (Indicates TCI status / Sets TCI status)

[0108] For Rel.17 TCI states, the unified / common TCI state can also refer to the Rel.17 TCI state indicated by using (Rel.17) DCI / MAC CE / RRC (indicated Rel.17 TCI state).

[0109] In this disclosure, the Rel.17 TCI state, the indicated TCI state, the unified / common TCI state, the TCI state applied to multiple signals (channel / RS), and the TCI state used for multiple signals (channel / RS) can also be overwritten with each other.

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

[0111] For Rel.17 TCI states, TCI states other than the unified TCI state can also refer to Rel.17 TCI states configured using (Rel.17) MACCE / RRC (configured Rel.17 TCI state). In this disclosure, the configured Rel.17 TCI state, the configured TCI state, TCI states other than the unified TCI state, and TCI states applied to specific types of signals (channels / RS) can also be interchanged.

[0112] Setting the Rel.17TCI state may not be shared with at least one of the UE-specific receive, dynamically authorized (DCI) / configured authorized PUSCH, and multiple (e.g., all) dedicated PUCCH resources in the PDSCH / PDCCH (updated using Rel.17 DCI / MAC CE / RRC). Setting the Rel.17TCI state may also be structured such that it is set per CORESET / per resource / per resource set via RRC / MAC CE, and the setting of the Rel.17TCI state will not be updated even if the aforementioned indicated Rel.17TCI state (common TCI state) is updated.

[0113] (Channel / RS whose TCI status is indicated by the application)

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

[0115] [PDCCH]

[0116] • When CORESET0 is set to followUnifiedTCIState, the indicated TCI state is applied. Otherwise, the Rel.15 specification is applied for that CORESET. That is, CORESET0 follows the TCI state activated by MAC CE, or is QCL-enabled with SSB.

[0117] • For CORESETs with USS / CSS type 3 and index 0 or above, the TCI status is always applied.

[0118] • If a CORESET other than index 0 is configured to conform to a uniform TCI state for at least CSS type 3, then the indicated TCI state is applied. Otherwise, the configured TCI state is applied to that CORESET.

[0119] [PDSCH]

[0120] • The UE-dedicated PDSCH is always indicated by the application to indicate the TCI status.

[0121] • When a non-UE-dedicated PDSCH (a PDSCH scheduled via DCI within the CSS) has its followUnifiedTCIState set (for the CORESET of the PDCCH that schedules the PDSCH), the indicator TCI state can 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 indicator TCI state depends on whether followUnifiedTCIState is set for the CORESET used in scheduling that PDSCH.

[0122] [CSI-RS]

[0123] • When the CORESET of the PDCCH that triggers the A-CSI-RS for CSI acquisition or beam management is set to followUnifiedTCIState, the TCI state is applied. For other CSI-RS, the configured TCI state for that CSI-RS is applied.

[0124] [PUCCH]

[0125] • For all dedicated PUCCH resources, the application always indicates the TCI status.

[0126] [PUSCH]

[0127] • For dynamic / configured license PUSCH, the application is always indicated with TCI status.

[0128] [SRS]

[0129] • When the SRS resource sets for A-SRS used for beam management and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching are configured to follow a unified TCI state, an indication TCI state is applied. For other SRS, the TCI state set within this SRS resource set is applied.

[0130] (TCI state switching)

[0131] In Rel.15 / 16, the delay time for handover of the active TCI state for a UE that has been set to more than one TCI state in the serving cell is specified.

[0132] Even if the UE measures / saves / maintains QCL characteristics, the NW cannot identify whether the UE has measured / saves / maintained QCL characteristics unless the UE reports L1-RSRP / beam to the network (NW, e.g., base station). Therefore, for the UE to perform beam / RS measurements and reports, both the UE and the NW need to have a common understanding of whether the TCI state is known or unknown.

[0133] In Rel.16, a TCI state is known if the following conditions 0-5 are met: (Condition 0): During the period from the last transmission of the RS resource used in the report of L1-RSRP measurement from the target TCI state to the completion of the switch to activate the TCI state, the RS resource used for L1-RSRP measurement is the RS of the target TCI state or the RS that has a QCL relationship with the target TCI state.

[0134] (Condition 1): The TCI state switch command is received within 1280ms from the last transmission of the RS resource used for beam reporting or measurement.

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

[0136] (Condition 3): During the TCI state transition, the ability to detect the TCI state must be maintained.

[0137] (Condition 4): During the transition of TCI state, the detection of SSB associated with TCI state is maintained.

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

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

[0140] In addition, in this disclosure, a known TCI state may also be referred to as a "Known TCI State", and an unknown TCI state may also be referred to as an "Unknown TCI State".

[0141] In the case of using MAC CE for TCI state switching (MAC-CE based TCI state switch), and where the target TCI state (the TCI state at the switching destination) is a known TCI state, if the UE receives a Physical Downlink Shared Channel (PDSCH) containing an 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 The initial time slot reception after (NR slotlength) involves the Physical Downlink Control Channel (PDCCH) of the serving cell in the target TCI state of the TCI state switching. Additionally, the UE receives the PDCCH in time slot n+T. HARQ +3N subframe,μ slot Previously, it was able to receive the PDCCH in the old (pre-switching) TCI state. From time slot n+T HARQ +3N subframe,μ slot It serves as a time slot n+T HARQ +3N subframe,μ slot +TO k (T) first-SSB +T SSB-proc During the period up to (NR slot length), the TCI state applied by the UE is undefined (see reference). Figure 3 ).

[0142] Here, T HARQ This indicates the timing from the transmission of downlink data signals (e.g., PDSCH) to the delivery of acknowledgment information (e.g., HARQ-ACK information). N subframe,μ slotThis indicates the number of time slots per subframe for setting μ for a subcarrier. T first-SSB This is the time from after the UE decodes the MAC CE command used during the activation of the TCI state until the initial transmission of the SSB. SSB-proc It's 2ms. k The value is 1 if the target TCI state is not included in the list of active TCI states used by PDSCH, and 0 otherwise. NR slot length indicates the length of the slot.

[0143] Figure 4 This is a diagram illustrating an example of the TCI states specified up to Rel.16. (See diagram.) Figure 4 As shown, the TCI state of the PDCCH indicates the relationship between the decall reference signal (DMRS) used by the PDCCH and the QCL type A / D of the TRS (or, CSI-RS, here TRS#1). Furthermore, the TCI state of the TRS indicates the relationship between the TRS and the QCL type C / D of the SSB (here SSB#1).

[0144] When using MAC CE during TCI state transition, and if the target TCI state is unknown, if the UE receives a PDSCH containing an activation command for the TCI state in time slot n, then in time slot n+T... HARQ +3N subframe ,μ slot +T L1-RSRP +TO uk (T) first-SSB +T SSB-proc In the initial time slot following (NR slot length), the UE receives the PDCCH of the serving cell in the target TCI state where a TCI state handover has occurred. Furthermore, in time slot n+T... HARQ +3N subframe,μ slot Previously, it was able to receive the PDCCH in the old (pre-switch) TCI state.

[0145] Here, TO uk For L1-RSRP measurements using CSI-RS, or for TCI states set to a QCL type other than QCL type D, the switching is 1. On the other hand, TO uk For the switching of TCI states that are at least set to QCL type D and the L1-RSRP measurement using SSB is 0.

[0146] In addition, T first-SSBThis is the time from the start of the L1-RSRP measurement to the initial SSB transmission, assuming at least a TCI state switch of QCL type D is performed. Alternatively, T... first-SSB It is the time from after the UE decodes the MAC CE command used in the activation of the TCI state other than QCL type D until the initial transmission of the SSB.

[0147] Compared to 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. T L1-RSRP This is the time associated with the received power measurement. T L1-RSRP It is 0 in frequency range (FR) 1, or in FR2 when QCL type D is not set. In other cases, it is the time required for the determination / refinement of the received beam in FR2.

[0148] Furthermore, in cases where downlink control information (DCI) is used during TCI state switching (DCI-based TCI state switch), and the target TCI state is a known TCI state, for the UE, if the higher-layer parameter tci-PresentInDCI used for CORESET scheduling PDSCH in time slot n is enabled, then in the first time slot after time slot n + timeDurationForDCI, the PDSCH of the serving cell with the target TCI state from which the TCI state switching occurred will be received. Here, timeDurationForDCI is the time required for the reception of PDCCH and the application of spatial QCL-related information (spatial QCL information) to the reception of DCI used for PDSCH.

[0149] Furthermore, in the case of using RRC signaling during TCI state switching (RRC-based TCI state switch), and given that the target TCI state is a known TCI state, if the UE receives the PDSCH transmitting the 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 PDCCH of the serving cell in the target TCI state of the first time slot after (NR slot length) is received when the TCI state handover occurs.

[0150] Here, T RRC_processing This is the RRC processing delay. first-SSB This refers to the time from the start of the UE's RRC process to the initial transmission of the SSB. T SSB-proc TO k And (NR slot length) is the same as the case of a known TCI state during the switching of TCI states using MAC CE.

[0151] Furthermore, in cases where RRC signaling is used during TCI state switching (RRC-based TCI state switch), and the target TCI state is unknown, 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 PDCCH of the serving cell in the target TCI state of the first time slot after (NR slot length) is received when the TCI state handover occurs.

[0152] Here, T RRC_processing This is the RRC processing delay. SSB-proc TO uk And (NR slot length) is the same as the case of unknown TCI state during TCI state switching using MAC CE.

[0153] In addition, T first-SSB This is the time from the start of the L1-RSRP measurement to the initial SSB transmission, assuming at least a TCI state switch of QCL type D is performed. Alternatively, T... first-SSB It is the time from after the UE decodes the MAC CE command used in the activation of the TCI state other than QCL type D until the initial transmission of the SSB.

[0154] Rel.17 specifies the delay time for switching involved in the unified TCI state.

[0155] For example, this specified delay time can also be applied when the RRC parameter (DLorJoint-TCIState) related to the unified TCI state is set for the DL channel of the serving cell for the UE.

[0156] In MR-DC or standalone NR, this delay time can 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) of multiple CCs / cells.

[0157] When the target DL TCI state reference differs from the Physical Cell ID (PCI) of the serving cell that has set that DL TCI state, the delay time can also be applied if the following conditions are met: • The activation BWP is the same for serving cells and cells with additional PCI.

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

[0159] • The cell for which PCI is added is known to the UE.

[0160] In addition, the PCI cell can be added as known if the following conditions are met: • Within the last 5 seconds before the L1-RSRP measurement is set, the UE sends a valid L3 measurement report for the cell with the additional PCI.

[0161] • The timing offset between the serving cell and the cell with added PCI is within the corresponding SCS CP.

[0162] If this condition is not met, the cell for which PCI is added can also be unknown.

[0163] In the unified TCI state, the DL TCI state being known can also mean that the following conditions are met: • During the period from the last transmission of RS resources used in the L1-RSRP measurement report of the target DL TCI state to the completion of the switch to activate the DL TCI state, the RS resources used for L1-RSRP measurement are RS of the target DL TCI state or RS that are QCL related to the target DL TCI state.

[0164] • The DL TCI state switch command is received within 1280ms from the last transmission of the RS resource used for beam reporting or measurement.

[0165] • Before the DL TCI state switching indication, the UE sends at least one L1-RSRP report for the target DL TCI state.

[0166] • Maintain the ability to detect the DL TCI state during the transition between DL TCI states.

[0167] • During the transition of DL TCI state, maintain the ability to detect SSBs associated with the DL TCI state.

[0168] • The signal-to-noise ratio (SNR) in DL TCI mode is above -3dB.

[0169] The SSB can also be associated with the PCI of the serving cell or with a PCI that is different from the PCI of the serving cell.

[0170] If the above conditions are not met, the DL TCI state can also be unknown.

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

[0172] In the case of using MAC CE for DL ​​TCI state switching (MAC-CE based downlink TCI state switch), and if the target TCI state (the TCI state of the switching destination) is a known TCI state, if the UE receives a PDSCH containing an 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 The initial time slot reception after (NR slot length) involves the Physical Downlink Control Channel (PDCCH) of the serving cell in the target TCI state of the TCI state switching. Additionally, the UE receives the PDCCH in time slot n+T. HARQ +3N subframe,μ slot Previously, it was possible to use the old (pre-handover) TCI state to receive UE-specific PDSCH / PDCCH. From time slot n+T HARQ +3N subframe,μ slotIt serves as a time slot n+T HARQ +3N subframe,μ slot +TO k (T) first-SSB +T SSB-proc During the period up to (NR slot length), the TCI state applied by the UE is not specified.

[0173] Here, T HARQ This indicates the timing from the transmission of downlink data signals (e.g., PDSCH) to the delivery of acknowledgment information (e.g., HARQ-ACK information). N subframe,μ slot This indicates the number of time slots per subframe for setting μ for a subcarrier. T first-SSB This is the time from after the UE decodes the MAC CE command used during the activation of the TCI state until the initial transmission of the SSB. SSB-proc It's 2ms. k The value is 1 if the target TCI state is not included in the list of active TCI states used by PDSCH, and 0 otherwise. NR slot length indicates the length of the time slot.

[0174] When using MAC CE during DL TCI state handover, and if the target TCI state is unknown, if the UE receives a PDSCH containing an activation command for the TCI state in time slot n, then in time slot n+T... HARQ +3N subframe,μ slot +T L1-RSRP +TO uk (T) first-SSB +T SSB-proc In the initial time slot following (NR slot length), the UE receives the PDCCH of the serving cell in the target TCI state where a TCI state handover has occurred. Furthermore, in time slot n+T... HARQ +3N subframe,μ slot Previously, it was possible to use the old (pre-switching) TCI state to receive UE-specific PDSCH / PDCCH.

[0175] Here, TO uk For L1-RSRP measurements using CSI-RS, or for TCI states set to a QCL type other than QCL type D, the switching is 1. On the other hand, TO uk For the switching of TCI states that are at least set to QCL type D and the L1-RSRP measurement using SSB is 0.

[0176] In addition, T first-SSB This is the time from the start of the L1-RSRP measurement to the initial SSB transmission, assuming at least a TCI state switch of QCL type D is performed. Alternatively, T... first-SSB It is the time from after the UE decodes the MAC CE command used in the activation of the TCI state other than QCL type D until the initial transmission of the SSB.

[0177] Compared to 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. T L1-RSRP This is the time associated with the received power measurement. T L1-RSRP It is 0 in frequency range (FR) 1, or in FR2 when QCL type D is not set. In other cases, it is the time required for the determination / refinement of the received beam in FR2.

[0178] Furthermore, for example, when the RRC parameter (DLorJoint-TCIState (unifiedTCI-StateType indicating Joint) or UL-TCIState) related to the unified TCI state is set for the UE in order to serve the cell's UL channel / signal, the specified delay time can also be applied.

[0179] In MR-DC or standalone NR, this delay time can 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) of multiple CCs / cells.

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

[0181] In the case of joint TCI state switching, it is also possible to not expect transmission in UL before the UE completes the switching of DL and UL TCI states.

[0182] In the case of using MAC CE for the handover of independent UL TCI state / joint TCI state for UL channel / signal (MAC-CE based uplink TCI state switch), and if the target TCI state (the TCI state of the handover destination) is a known TCI state, if the UE receives a PDSCH containing an activation command (TCI state indication) for 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), capable of transmitting the UL signal of 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.

[0183] Furthermore, when using MAC CE in the handover of independent UL TCI state / joint TCI state for UL channel / signal, and when the target TCI state is an unknown TCI state, if the UE receives a PDSCH containing an 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 the UL signal of the target TCI state.

[0184] Here, T HARQ This indicates the timing from the transmission of downlink data signals (e.g., PDSCH) to the delivery of acknowledgment information (e.g., HARQ-ACK information). N subframe,μ slot This indicates the number of time slots per subframe for which μ is set for the subcarrier. NRslot length indicates the length of the time slot.

[0185] For NM, it is 1 if the target PL-RS is maintained, and 0 if not.

[0186] T target-PL-RSThis refers to the time from the L1-RSRP measurement to the initial path loss RS transmission when the target TCI state is unknown. Furthermore, T... 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, assuming the target TCI status is known.

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

[0188] Compared to 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. T L1-RSRP This is the time associated with the received power measurement. T L1-RSRP It is 0 in frequency range (FR) 1, or in FR2 when QCL type D is not set. In other cases, it is the time required for the determination / refinement of the received beam in FR2.

[0189] (L1 / L2 inter-cell mobility)

[0190] The study investigates UL transmission of a UE to one or more cells / TRPs. As a procedure in this case, consider scenario 1 or scenario 2 below. Additionally, in this disclosure, the serving cell can also be rewritten as the TRP within the serving cell. Layer 1 / Layer 2 (L1 / L2) and the DCI / Medium Access Control Control Element (MAC CE) can also be rewritten. In this disclosure, a PCI that differs from the Physical Cell Identity (PCI) of the current serving cell is sometimes simply referred to as "different PCI". Non-serving cells, cells with different PCIs, and additional cells can also be rewritten.

[0191] <Scenario 1>

[0192] Scenario 1 could be a scenario that corresponds to inter-cell mobility in multi-TRP, but it could also be a scenario that does not correspond to inter-cell mobility in multi-TRP.

[0193] (1) The UE receives from the serving cell the settings of the SSB for beam measurement of the TRP corresponding to a different PCI from the serving cell, as well as the settings required for using radio resources in data transmission and reception, which include resources of different PCIs.

[0194] (2) The UE performs beam measurement for the TRP corresponding to different PCIs and reports the beam measurement results to the serving cell.

[0195] (3) Based on the above report, the Transmission Configuration Indication (TCI) status associated with the TRP corresponding to different PCIs is activated by L1 / L2 signaling from the serving cell.

[0196] (4) The UE uses the dedicated channel on the TRP corresponding to different PCIs to transmit and receive.

[0197] (5) In cases involving multiple TRPs, the UE needs to always cover the serving cell. Similar to previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

[0198] In Scenario 1, when the UE transmits and receives signals with the additional cell / TRP (the TRP corresponding to the PCI of the additional cell), the serving cell (the assumption of the serving cell in the UE) is not changed. The UE is configured with higher-layer parameters associated with the PCI of the non-serving cell from the serving cell. Scenario 1 can also be applied, for example, in Rel. 17.

[0199] Figure 5A This diagram illustrates an example of UE movement in Rel.17. Imagine the UE moving from PCI#1 cell (serving cell) to PCI#3 cell (additional cell) (overlapping with the serving cell). In this case, L1 / L2-based handover of the serving cell is not supported in Rel.17.

[0200] An additional cell is a cell with an additional PCI that differs from the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. For the UE to receive UE-common channels (e.g., system information / paging / SMS), it needs to be within the coverage area of ​​the serving cell. If the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required.

[0201] <Scenario 2>

[0202] In Scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, serving cell changes can be performed using functions such as beam control without RRC resetting. In other words, transmission and reception with the additional cell can be performed without handover. Handover requires RRC reconnection, causing data communication interruptions. Therefore, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can continue even during serving cell changes. Scenario 2 can also be applied, for example, in Rel. 18. In Scenario 2, for example, the following process is performed.

[0203] (1) In order to change the beam measurement / serving cell, the UE receives the SSB settings of the cell (additional cell) with different PCI from the serving cell.

[0204] (2) The UE performs beam measurements for cells using different PCIs and reports the measurement results to the serving cell.

[0205] (3) The UE can also receive the settings (serving cell settings) of cells with different PCIs through higher-layer signaling (e.g., RRC). That is, it can also perform pre-configuration related to serving cell changes. This configuration can be performed together with the configuration in (1) or separately.

[0206] (4) Based on the above report, the TCI status of cells with different PCIs can also be activated via L1 / L2 signaling according to the change of the serving cell. The activation of the TCI status and the change of the serving cell can also be carried out separately.

[0207] (5) The UE changes its serving cell (the intended serving cell) and uses a pre-set UE-specific channel and TCI state to begin receiving / transmitting.

[0208] That is, in Scenario 2, the serving cell (the assumption of the serving cell in the UE) is updated via L1 / L2 signaling. Scenario 2 can also be applied in Rel.18.

[0209] Figure 5B This diagram illustrates an example of UE movement in Rel.18. In Rel.18, the serving cell is handed over via L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated / common channels between a new serving cell (or a target serving cell). The UE can also leave the coverage area of ​​its current serving cell (e.g., the current serving cell).

[0210] (Type of beam report)

[0211] <Intra-cell Beam Report for Rel. 15 / 16>

[0212] In Rel.15 / 16, intra-cell beam reporting is supported. For example, L1-RSRP / SINR reporting can be configured via higher-layer signaling (RRC).

[0213] For example, in the calculation of L1-RSRP, when resources are associated with QCL type C / type D, the UE can be configured with either CSI-RS resources or SS / PBCH block resources, or both.

[0214] Furthermore, the UE can be configured with a maximum of 16 CSI-RS resource sets, each containing a maximum of 64 resources. The total number of different CSI-RS resources across all resource sets is 128 or less.

[0215] In the L1-RSRP report, when the higher-level parameter nrofReportedRS (e.g., within CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140~-44] dBm with a step size of 1 dB.

[0216] Here, the largest measurement of L1-RSRP is quantized as a 7-bit value in the range of [-140~-44] dBm with a step size of 1 dB. In addition, the differential values ​​of L1-RSRP are quantized as 4-bit values.

[0217] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP report instance.

[0218] For example, in L1-SINR calculation and channel measurement, the UE can be configured with either NZP CSI-RS resources or SS / PBCH block resources, or both. Furthermore, for interference measurement, the UE can be configured with either NZP CSI-RS resources or CSI-IM resources.

[0219] For channel measurement, the UE can be configured with CSI resource settings associated with a maximum of 64 CSI resources or a maximum of 16 CSI-RS resource sets with SS / PBCH block resources.

[0220] In the L1-SINR report, with the high-level parameter nrofReportedRS set to 1, the reported L1-SINR value is defined as a 7-bit value in the range of [-23~40] dBm with a step size of 0.5 dB.

[0221] When the higher-layer parameter nrofReportedRS is set to a value greater than 1, or when the higher-layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the differential-based L1-SINR value in the report.

[0222] The difference value is calculated with a step size of 1 dB, referencing the largest measurement as part of the same L1-SINR reporting instance.

[0223] In this disclosure, the intra-cell beam report of Rel.15 / 16 (also referred to as intra-cell beam report) may also be referred to as a type 1 beam report (beam report type 1) or a beam report for intra-cell beam handover.

[0224] <Inter-cell Beam Report of Rel.17>

[0225] As mentioned above, Rel.17 supports L1 / L2 inter-cell mobility. For example, a UE can transmit and receive UL / DL channels / signals between cells with different PCIs than the serving cell. For example, if a non-serving cell has a larger RSRP than the serving cell, the UE can transmit and receive UL / DL channels / signals between non-serving cells without handover.

[0226] In the L1-RSRP report, the absolute / differential values ​​of L1-RSRP can be used in the same way as in Rel.15 / 16. In the inter-cell beamforming report of Rel.17 (the type 2-1 beamforming report described later), each L1-RSRP value is associated with the PCI ID (for the serving cell / additional cell / candidate cell). The association between L1-RSRP values ​​and PCI IDs can also be set / indicated via higher-layer signaling / physical-layer signaling.

[0227] Based on the higher-layer signaling settings, up to seven additional cells are supported. Additionally, ID=0 refers to the PCI of the serving cell.

[0228] In this disclosure, inter-cell beam reporting (in Rel. 17 / 18) may also be referred to as type 2 beam reporting (beam reporting type 2). Type 2 beam reporting can further be classified as type 2-1, 2-2, as described later.

[0229] In this disclosure, the beam report of Rel.17 may also be referred to as a type 2-1 beam report, or a beam report for inter-cell beam switching.

[0230] <Inter-cell Beam Report of Rel.18>

[0231] Furthermore, Rel.18 beam reporting only supports SSB-based L1-RSRP reporting (beam reporting). Here, the number of candidate cells L is any one of 1 to 4, and the number of beams M for each cell can also be any one of 1 to 4. For example, in beam reporting, the 7-bit absolute value (the largest L1-RSRP value among all cells) is reported to one cell, and all remaining L1-RSRP values ​​are reported as differential values.

[0232] Regarding beam selection in the L1-RSRP report based on SSB, and regarding the M and L mentioned above that can be set via RRC, M... The maximum value of L and the combination of M and L can also depend on the UE capabilities.

[0233] In the L1-RSRP report, the absolute value / difference value of L1-RSRP can also be used in the same way as in Rel.15 / 16 / 17.

[0234] In the L1-RSRP report, the reported L1-RSRP value is defined as a 7-bit value in the range of [-140~-44] dBm with a step size of 1 dB.

[0235] Here, the largest measurement of L1-RSRP is quantized as a 7-bit value in the range of [-140~-44] dBm with a step size of 1 dB. In addition, the differential values ​​of L1-RSRP are quantized as 4-bit values.

[0236] The difference value is calculated with a step size of 2 dB, referencing the largest measurement that is part of the same L1-RSRP report instance.

[0237] The L1-RSRP report includes the SSBRIs of the configured candidate cells. That is, the L1-RSRP report includes the L1-RSRP corresponding to the SSBRI of the configured candidate cells. The format can also be the same as existing specifications.

[0238] In this disclosure, the beam report of Rel.18 may also be referred to as a type 2-2 beam report or a beam report used for cell handover. Furthermore, the type 2-2 beam report does not contain PCI-related information (PCI ID). Instead, PCI-related information may be included in the SSBRI. For example, in the case of four cells with 64 SSBs, the SSBRI can be any one of {0, 1, ..., 255}.

[0239] (Event-based beam reporting)

[0240] In future wireless communication systems, research is underway to support event-based beam reporting. Event-based beam reporting can also be called event-triggered beam reporting, or UE-initiated beam reporting.

[0241] The events defined in the existing 5G NR can exemplify the following. Furthermore, events are not limited to those shown below; other new events can also be defined.

[0242] Event A1: The measurement result of the serving [cell] is better than the threshold.

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

[0244] Event A3: A situation where the measurement result of a neighboring [cell] (the value after adding an offset to the measurement result) is better than the measurement result of SpCell (the value after adding an offset to the measurement result).

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

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

[0247] Event A6: A situation where the measurement result of a neighboring cell (the value after adding an offset to the measurement result) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (the value after adding an offset to the measurement result).

[0248] Event B1: The measurement results of neighboring [cells] between RATs are better than the threshold.

[0249] Event B2: The PCell measurement result is worse than the first threshold, and the measurement result of the neighboring [cell] between RATs (the value after adding the offset to the measurement result) is better than the second threshold.

[0250] <Applicable Situations>

[0251] Event-based beam reporting can also be applied in at least one of the following scenarios: • [Scenario 1]: L1-RSRP / SINR beam reports containing serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam reports for serving cell / additional PCI cells containing L1 / L2 intra-cell mobility / intra-cell multi-TRP (M-TRP intra-cell) / Rel.18 L1 / L2 mobility accompanying cell handover).

[0252] • [Scenario 2]: L1-RSRP / SINR beam reports containing only the serving cell PCI.

[0253] The UE may also report measurement results (e.g., L1-RSRP / L1-SINR) of the NW (e.g., base station) when a specific event occurs (or, in this disclosure, a specific condition is met / not met).

[0254] Specific events may also be, for example, events related to at least one of the serving cell and the additional cell, and events related to beam reporting of at least one of the PCI of the serving cell and the PCI of the additional cell.

[0255] Regarding the incident in scenario 1

[0256] An example of an event related to scenario 1 above will be described. This event may also refer to events related to the serving cell and the additional cell, or events related to beam reporting of the PCI of the serving cell and the PCI of the additional cell.

[0257] [Option 1]

[0258] Alternatively, one or more existing events from Radio Resource Management (RRM) (such as at least one of events A2 to A6 and I1 below) can be reused to trigger beam reporting (e.g., aperiodic CSI reporting). That is, both RRM reporting and CSI reporting can be triggered when at least one of the following events A2 to A6 and I1 occurs (if the event conditions are met), and the UE sends both RRM reporting and CSI reporting.

[0259] In addition, in this disclosure, the RRM report can also be rewritten with the L3 measurement report.

[0260] Figure 6This is a flowchart illustrating an example of event-based beamforming reporting processing. The UE determines whether an event has occurred (e.g., at least one of events A2 to A6 and I1 below) (S1). If the UE is yes (YES) in S1, it sends a non-periodic CSI report (and RRM report) (S2); if no (NO), it terminates the processing related to event-based beamforming reporting. Figure 6 The process can also be repeated for each specific period.

[0261] In this disclosure, the triggered non-periodic CSI report and the non-periodic CSI report sent by the UE can be overwritten. CSI reports, L1 beam reports, and beam reports can also be overwritten.

[0262] In events A2 to A6 below, the measurement result can also be at least one of RSRP (L1-RSRP / L3-RSRP), RSRQ, and SINR (RS-SINR). In the conditions of events A2 to A6 below, "poor" can also mean "low," and "excellent" can also mean "high." In the conditions of events A2 to A6 below, SpCell can also mean a special cell, or at least one of a Primary Cell (PCell) and a Primary Secondary Cell (PSCell). In events A2 to A6 and I1 below, the parameter corresponding to hysteresis can also be added to / subtracted from the measurement result. The thresholds can be the same or different. Neighboring cells can also be non-serving cells.

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

[0264] Event A3: The measurement results of the neighboring cell (the value after adding an offset to the measurement results) are better than the measurement results of SpCell (the value after adding an offset to the measurement results).

[0265] Event A4: The measurement results of the neighboring cell (the value after adding the offset to the measurement results) are better than the threshold.

[0266] Event A5: The SpCell measurement result 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.

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

[0268] Event I1: The measured value of the interference is higher than the threshold.

[0269] Option 1 allows for the reuse of RRM report triggering in beam report triggering, making it easy to set up.

[0270] [Option 2]

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

[0272] [[Option 2-1]]

[0273] The thresholds can also be different. That is, different thresholds can be used than those used for RRM reporting, such as using events A2 to A6 and I1 in L1 beam reporting (CSI reporting).

[0274] [[Option 2-2]]

[0275] The event can also occur based on the measurement of the reference signal received power (L1-RSRP) in Layer 1. That is, a comparison can be made based on L1-RSRP instead of L3-RSRP. Alternatively, a new filtered L1-RSRP can be applied, with the timescale (update / measurement period) between L1-RSRP and L3-RSRP (or the same as L1-RSRP or L3-RSRP). Other metrics, such as L1-SINR, L3-RSRQ, etc., can also be applied. For example, the following event A2' can be applied as a new event: Event A2': The L1-RSRP measurement result of the serving cell is worse than the threshold.

[0276] [[Options 2-3]]

[0277] It can also be based on comparisons of measurements at the beam level, multiple beam levels (combining independent measurements from multiple beams into a single value), or cell level. For example, the following event A4' or event A4'' can also be applied: Event A4': The measurement result from a beam from a neighboring cell is better than the threshold.

[0278] Event A4'': The statistical values ​​(e.g., average, total, etc.) of the measurement results of multiple beams (e.g., the optimal X beams) are better than the threshold. X can be fixed or can be set via higher-layer signaling, etc.

[0279] [[Options 2-4]]

[0280] Alternatively, the number of beams that meet the conditions (such as any one of events A2 to A6 and I1) can be considered. For example, if X beams meet event A4' (where the measurements from X beams from neighboring cells are better than a threshold), the UE can also report a CSI.

[0281] Alternatively, examples that combine at least two of 2-1 to 2-4 above can also be applied. For example, consider A4''' as an event combining 2-2 and 2-3. Furthermore, consider A4'''' as an event combining 2-2, 2-3, and 2-4: Event A4''': L1-RSRP measurement results from a beam from a neighboring cell are better than the threshold.

[0282] Event A4'''': The L1-RSRP ratio of each beam from X neighboring cells is better than the threshold.

[0283] Option 2 enables faster CSI reporting compared to existing RRM reporting that utilizes RRC.

[0284] [Option 3]

[0285] Alternatively, any combination of two or more events from options 1 and 2 above can be used to trigger a non-periodic L1 beam report (CSI report).

[0286] You can also combine existing events used in RRM reporting with one or more events from option B. For example, you can also trigger a CSI report if both event A4 and a new event A4''' occur.

[0287] You can also combine two or more events from option 2. For example, you can trigger a CSI report if both event A2' and the new event A4''' are met.

[0288] Regarding the incident in scenario 2

[0289] An example of an event related to scenario 2 above will be described. This event may also refer to an event that is only related to the serving cell, or an event that is related to a beam report of a PCI that only includes the serving cell.

[0290] You can also define one or more new events (separate from those used in RRM reporting) to trigger aperiodic L1 beam reporting (CSI reporting). This event can also be at least one of the following events: B2 through B6 and K1. Event B2: The measurement result of the current beam is worse than the threshold.

[0291] Event B3: The measurement results of other beams (the value after adding an offset to the measurement results) are better than the measurement results of the current beam (the value after adding an offset to the measurement results).

[0292] Event B4: Measurements of other beams (the values ​​after adding an offset to the measurement) are better than the threshold.

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

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

[0295] Event K1: The measured value of the interference is higher than the threshold.

[0296] Furthermore, the names / symbols used in the events described in this disclosure (e.g., A2-A6, B2-B6, I1, K1, etc.) are merely examples and are not limited to this example. For instance, the name of the event for case 2 may be the same as the name of the event for case 1 corresponding to (number).

[0297] Alternatively, for at least one of the events in this disclosure (the events involved in scenario 1 / scenario 2), a period (duration) / counter for satisfying the event (condition) can be specified. The UE / NW can also determine that the conditions of each event are satisfied if at least one of the conditions of each event is satisfied with a condition related to a specific period / counter. For example, the UE can also determine that the condition of the event B3 above is satisfied if, within a 100ms time window, the measurement result of another beam is better than the measurement result of the current beam. Furthermore, for example, the UE can also determine that the condition of the event B3 above is satisfied if, for every plurality of samples, the measurement result of another beam is better than the measurement result of the current beam 10 times.

[0298] In this disclosure, "current beam" may also mean, for example, an SSB / CSI-RS that is QCL-relationed with the PDCCH (QCLed).

[0299] The PDCCH can also be, for example, the PDCCH corresponding to a CORESET determined by specific rules / higher-level parameter settings. The CORESET can also be, for example, a CORESET with a specific (e.g., lowest / highest) CORESET ID.

[0300] The CSI-RS can also be, for example, a periodic / semi-persistent / aperiodic CSI-RS. The SSB / CSI-RS can also be, for example, defined as a periodic CSI-RS / SSB.

[0301] Furthermore, in this disclosure, "current beam" can also be, for example, the indicated TCI state (joint / DL / UL TCI state) in the current unified TCI state. Additionally, "current beam" can also be, for example, the QCL source RS (QCL type D / A) associated with the current indicated TCI state.

[0302] Furthermore, in this disclosure, "current beam" may also be, for example, a beam / resource index (e.g., CRI / SSBRI) reported in a specific (e.g., latest) L1-RSRP / L1-SINR.

[0303] In this disclosure, "other beams" can also be, for example, beams other than the "current beam" / SSB / CSI-RS / TCI status.

[0304] Multiple beam sets (candidate beam sets) can also be configured for the UE. The UE can also select / determine "other beams" from this set.

[0305] In this disclosure, “(better than...)” can also mean, for example, a measurement result that is (lower than...) or higher (e.g., RSRP / SINR / RSRQ).

[0306] The aforementioned thresholds can be predefined in the specification, set / indicated / notified using higher-level signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or specified through a combination of these methods. For example, the threshold can also reuse an existing threshold (e.g., the threshold used in RRM / Scenario 1).

[0307] The aforementioned offset associated with this threshold can be predefined in the specification, set / indicated / notified using higher-level signaling (RRC / MAC CE) / DCI, reported by UE capabilities, or specified by a combination of these.

[0308] Furthermore, in this disclosure, UE-initiated beam reports, event-triggered beam reports, event-based beam reports, and event-based beam reports can be rewritten to each other.

[0309] In this disclosure, the reported beam, the reporting beam, and the UE reporting beam can also be rewritten to each other.

[0310] (Rel.18 cell handover command (MAC CE))

[0311] The cell handover command sent via MAC CE can also contain at least the following information.

[0312] Information used to identify target cells Information related to advance timing (TA), • A joint TCI status index for the target cell, or a set of DL / UL TCI status indices for the target cell. • Activated DL / UL BWP for the target cell.

[0313] Regarding the existence of beam indication in cell handover commands, the following content is supported for at least a certain scenario.

[0314] • The cell handover command always contains a field that represents a joint TCI status index for the target cell, or a set of DL / UL TCI status indexes for the target cell.

[0315] • UE operations related to the beam indication field of RACH-based handover scenarios following a cell handover command.

[0316] (Triggering conditions (events) for event-based beam reporting for Rel.19)

[0317] Event-triggered [L1] beam reports can also be triggered when a certain condition (event) is met. For example, the UE can apply different / the same conditions / events for the following beam report triggers.

[0318] • UE Feature #1: Event-triggered [L1] beam reporting for MIMO in Rel.19.

[0319] • UE Feature #2: Event-triggered [L1] beam reporting for mobility in Rel.19.

[0320] Different UE capabilities can also be imported / defined between UE features #1 and #2. Furthermore, different high-level parameters can be set to activate each UE feature. UE features and UE capabilities can also be modified to each other.

[0321] The UE does not expect to set UE features #1 and #2 simultaneously in a certain BWP / CC / band / frequency / band / frequency (or for each UE).

[0322] Alternatively, a UE can have UE features #1 and #2 set simultaneously within a certain BWP / CC / band / frequency (or for each UE). For example, if a UE is set, the priority of which event (which UE feature) is determined can be predefined or set / indicated through higher-layer signaling / physical layer signaling.

[0323] This disclosure can also be applied within the unified TCI framework (Rel. 15 / 16 / 17 / 18).

[0324] This disclosure may also be applied only if the corresponding UE capability is reported. Alternatively, this disclosure may also be applied only if the corresponding higher-level parameters (e.g., RRC) are notified / reported.

[0325] <Beaming Report for MIMO>

[0326] The following can also be applied to beam reports triggered by events for MIMO in Rel.19.

[0327] ·MAC CE in PUSCH.

[0328] • UCI in periodic / semi-persistent PUCCH, UCI in dynamic license (DG) / configurable license (CG) PUSCH.

[0329] The relationship between the MAC CE-based method and the UCI-based method described above. For example, it is also possible to set up two independent methods. Alternatively, it is also possible to apply the UCI-based method on top of the MAC CE-based method (or to apply a combination of the two methods (a 2-step method)).

[0330] The content of the report can be essentially the same as existing L1 beam measurement reports, and may include at least one of the following:

[0331] ·SSBRI / CRI.

[0332] • The number of beams reported, X.

[0333] • Method for selecting X beams.

[0334] • L1-RSRP / SINR (absolute value / difference value) for each SSBRI / CRI.

[0335] When using MAC CE, • An indicator that indicates whether the following octet is included.

[0336] When using MAC CE, or when using UCI, • Serving Cell ID, BWP ID (indicated by the activation of the TCI status requested in this report, or beam switching).

[0337] <Beam Report for Mobility>

[0338] Regarding event-triggered beam reporting for mobility in Rel.19, it needs to be clarified whether event-triggered beam reporting is used for cell handover reporting. For example, the following could also be applied.

[0339] MAC CE in semi-persistent / aperiodic PUSCH.

[0340] • UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUSCH.

[0341] The report may also include at least one of the following.

[0342] When using measurement reports in cell handover reports, based on MIMO-related information, • Indicators indicating whether cell handover has occurred, or TA-related information.

[0343] In cases where this is not the case (where the measurement report is not used in the cell handover report), • Content that is the same as MIMO-related information (or it may differ only in which cell / inter-cell it is).

[0344] The supported events are also the same as those for Conditional Hand-Over (CHO).

[0345] For example, since candidate cells are set based on L3 measurement reports, L1-RSRP / SINR can also be used as a threshold.

[0346] When reports are used for cell handover commands, specific domain filters (e.g., time / frequency / space) can be considered / applied to prevent frequent handovers.

[0347] You can also specify the flexibility of whether or not to trigger at a certain time (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds).

[0348] <Definitions of terms for specific events>

[0349] In the existing events described above, the definitions of Serving [cell] and Neighbor [cell] can also be rewritten / updated in the Rel.19 event-triggered beam report as follows.

[0350] For example, the serving [cell], SpCell, and PCell in existing L3 events can also be rewritten with the current beam (e.g., the RSID associated with the [Joint / DL] TCI state) in the beam report triggered by the event for MIMO in Rel.19.

[0351] In addition, the serving cell, SpCell, and PCell in existing L3 events can be rewritten with the current beam (e.g., the RSID associated with the indication of the [Joint / DL] TCI state) or the serving cell's beam (e.g., the RS ID associated with the TCI state of the serving cell's PCI) in the beam report triggered by the event for Rel.19 mobility.

[0352] In existing L3 events, neighboring [cells] in the event-triggered beam reports for Rel.19 MIMO (or mobility) events are rewritten with other beams (e.g., RS IDs not associated with the [Joint / DL] TCI status, but associated with the RS IDs for L1 beam measurements).

[0353] Furthermore, in existing L3 events, neighboring [cells] in the event-triggered beam reports for mobility in Rel.19 can also be rewritten with the beams of non-serving cells / target cells / candidate cells (e.g., RS IDs associated with the TCI status of the PCI for the target cell / candidate cell).

[0354] The measured values ​​of each reference signal (RS) can also be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or the average of multiple L1-RSRP / SINR values.

[0355] For example, L1-RSRP / SINR can change dynamically. Therefore, by averaging multiple (X) L1-RSRP / SINR values ​​(e.g., X=5), it is possible to avoid control oscillations (frequent switching of trigger states) in beam reporting triggering.

[0356] (ACK / NACK in event-based beamforming reports)

[0357] <Method 1>

[0358] The UE may also use specific methods to receive ACK / NACK for event-based beam reports (e.g., at least one of (UCI-based) event-based beam reports transmitted using UCI and (MAC CE-based) event-based beam reports transmitted using MAC CE).

[0359] For example, the UE can also use a specific DCI to receive ACK / NACK for event-based beam reports (e.g., event-based beam reports based on UCI / MAC CE).

[0360] The specific DCI can be, for example, a new DCI format (specified after Rel.19) or an existing DCI format that has been scrambled with CRC by a new RNTI (specified after Rel.19).

[0361] You can also specify / set timers associated with ACK / NACK for event-based beam reports.

[0362] For example, the timer can also start when the UCI used for event-based beam reporting is sent.

[0363] For example, if the UE receives a DCI in DCI format scrambled with a new RNTI before the timer expires, the UE can determine that the DCI is an ACK used for event-based beamforming. If this is not the case, the UE can determine that the event-based beamforming failed (a NACK was received).

[0364] If the UE determines that the event-based beam report has failed (received NACK), the UE can also retransmit the event-based beam report.

[0365] <Method 2>

[0366] The UE can also use specific methods to receive ACK / NACK for event-based beam reports (e.g., event-based beam reports based on UCI / MACCE).

[0367] At least one of the new bit fields, and existing bit fields in the existing DCI format (e.g., DCI format 0_0 / 0_1 / 1_0 / 1_1), can also be used / reused for ACK / NACK in UCI-based event-based beamforming.

[0368] Existing DCI formats can also be DCI formats that scramble CRC using existing RNTI (e.g., C- / TC- / CS- / SP-CSI- / MCS-C-RNTI).

[0369] For example, specific fields contained in the DCI format (DCI format 0_1) of the scheduling PUSCH, which is scrambled with a specific RNTI (e.g., CS-RNTI) by the CRC, can be reused for ACK / NACK in event-based beam reporting.

[0370] This specific field can also be a downlink feedback information (DFI) flag field.

[0371] In existing specifications, the DFI flag has only 1 bit in the unlicensed band domain / shared spectrum. Therefore, in Rel.19 and later, this 1-bit field is specified in the case of event-based beam reporting and can be reused for ACK / NACK in event-based beam reporting.

[0372] The UE may also choose not to simultaneously configure both the CGDFI for unlicensed band / shared spectrum as specified in Rel.16 and the CG DFI for event-based beam reporting.

[0373] Furthermore, when both the CG DFI for unlicensed band / shared spectrum as specified in Rel.16 and the CG DFI for event-based beam reporting are configured simultaneously, the UE can also perform a handover operation based on the HARQ process ID after receiving the DFI indication.

[0374] For example, the UE can also perform operations related to CG DFI for unlicensed band / shared spectrum as specified in Rel.16 for HARQ process IDs that are not associated with event-based beam reports (as specified in Rel.19 and later).

[0375] In this scenario, if the UE receives an ACK, it can also terminate the repeated transmission (repeated transmission) of the transport block associated with that HARQ process ID. Otherwise, the UE can continue to repeatedly transmit the transport block associated with that HARQ process ID.

[0376] In addition, for example, the UE can also perform operations related to CG DFI for event-based beam reporting for HARQ process ID associated with (as specified in Rel.19 and later).

[0377] In this scenario, if the UE receives an ACK, it can determine that it is switching the beam / TCI state applied in a specific DL reception / UL transmission. If not, the UE can determine that it is not switching the beam / TCI state applied in a specific DL reception / UL transmission.

[0378] Additionally, the use of pre-set UL resources can continue only if the UE receives a NACK, or if the UE receives both an ACK and a NACK, in order to perform beam reporting.

[0379] Furthermore, in the case where both the CG DFI for unlicensed band domain / shared spectrum as specified in Rel.16 and the CG DFI for event-based beam reporting are set simultaneously, an additional bit can be added to the DCI for use in event-based beam reporting.

[0380] Furthermore, for example, new fields included in the DCI format of scheduling PDSCH / PUSCH (e.g., DCI format 0_1 / 1_1) can also be used for ACK / NACK in event-based beam reporting.

[0381] This field can also be specified by x bits (e.g., x = 1).

[0382] This new field can also be included in the DCI if event-based beam reporting is configured.

[0383] For example, if the ACK / NACK field included in the DCI for event-based beamforming reports represents a first value (e.g., 0 (or 1)), the UE can also determine that an ACK has been received. Furthermore, if the ACK / NACK field included in the DCI for event-based beamforming reports represents a second value (e.g., 1 (or 2)), the UE can also determine that a NACK has been received.

[0384] In addition, special values ​​of existing fields contained in the existing DCI can also be reused for ACK / NACK in event-based beamforming reports based on UCI / MAC CE.

[0385] <Method 3>

[0386] The UE can also use specific methods to receive ACK / NACK for event-based beam reports (e.g., event-based beam reports based on UCI / MACCE).

[0387] The UE can also use a specific search space / CORESET to receive ACK / NACK for event-based beam reports (e.g., event-based beam reports based on UCI / MAC CE).

[0388] You can also specify / set timers associated with ACK / NACK for event-based beam reports.

[0389] For example, the timer can also start when the UCI used for event-based beam reporting is sent.

[0390] For example, if the UE receives a DCI in DCI format (e.g., DCI format 0_0 / 0_1 / 1_0 / 1_1) sent in that specific search space / CORESET before the timer expires, the UE can also determine that the DCI is an ACK for event-based beam reporting. If this is not the case, the UE can also determine that the event-based beam reporting failed (a NACK was received).

[0391] If the UE determines that the event-based beam report has failed (received NACK), the UE can also retransmit the event-based beam report.

[0392] <Method 4>

[0393] The UE can also use specific methods to receive ACK / NACK for event-based beam reports (e.g., event-based beam reports based on UCI / MACCE).

[0394] The indications involved in the TCI status can also be used for responses from NW (ACK / NACK involved in event-based beam reporting).

[0395] For example, the indication involved in this TCI status can also be an indication based on the TCI field contained in a specific DCI (e.g., DCI format 1_1 / 1-2).

[0396] Furthermore, for example, the indication involved in this TCI status can also be an indication of the (activated) TCI status based on MAC CE.

[0397] The UE can also interpret any indication related to a TCI state as an acknowledgment from the NW (ACK / NACK related to event-based beam reporting). In this case, the UE can also determine that it will not send an event-based beam report from the time the indication is received until a specific period has elapsed.

[0398] Furthermore, the UE can also interpret an indication related to a specific TCI state as a response from the NW (ACK / NACK related to event-based beamforming). In the case of an indication related to that specific TCI state, for example, where the indicated TCI state is associated with event-based beamforming, the UE can also determine that the event-based beamforming report has been (normally) received in the NW. In this case, the UE can also determine that no event-based beamforming report will be transmitted from the time the indication is received until a specific period has elapsed.

[0399] In addition, the triggering of a specific beam report (e.g., A beam report) can also be used for responses from NW (ACK / NACK involved in event-based beam reports).

[0400] The ACK / NACK methods 1-4 described above can also be referred to as ACK / NACK (from) the gNB. In particular, the gNB's ACK can also be used to trigger beam reporting, which will be discussed later.

[0401] (analyze)

[0402] The aforementioned event-triggered beam reporting can be supported in MIMO / mobility versions after Rel.19. Furthermore, conditional handover (CHO) can also be supported as a mobility mechanism.

[0403] That is, event-triggered beam reports can be used for measurement reporting / beam handover / cell handover.

[0404] Furthermore, it is conceivable that the type of beam reporting supported for each of the above use cases would be different.

[0405] For example, in event-triggered beam reporting for MIMO in Rel.19, Type 1 / Type 2-1 beam reporting is supported. In event-triggered beam reporting for mobility in Rel.19, Type 2-2 beam reporting is supported.

[0406] However, regarding events in existing L3 measurement reports, for example, consider situations where it is difficult to set absolute thresholds for neighboring cells of event A5. Therefore, events A2 or A3 are utilized in stages.

[0407] More specifically, if the condition for event A2 is met, and then the condition for event A3 is met, an L3 measurement report is triggered. In this case, the measurement report can be issued multiple times. For example, a report can be sent once for event A2, and other reports can be sent for event A3.

[0408] That is, a measurement report is sent every time an event is triggered, which can be a cause of increased overhead during reporting.

[0409] Therefore, in the case of extending to event-based beam reporting for MIMO / mobility beyond Rel.19, further reductions in reporting overhead / latency are required.

[0410] Thus, research on the specifications related to event-based beamforming reporting corresponding to the applied use cases is insufficient. This inadequacy hinders the achievement of lower latency communication and raises concerns about inhibiting improvements in communication quality / throughput.

[0411] In view of these, the inventors of this invention conceived of a new method for event-triggered beam reporting.

[0412] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The wireless communication methods involved in each embodiment can be applied individually or in combination.

[0413] (Various interpretations)

[0414] In this disclosure, terms enclosed in parentheses "()" may also indicate explanations of the preceding term (e.g., spelling instructions), in other words, specific examples, supplementary explanations, etc. Furthermore, in this disclosure, terms enclosed in square brackets "[]" may be included in the interpretation of the entire article, or may be excluded (ignored) while still interpreting the overall meaning of the article. Additionally, "()" and "[]" may also be used for purposes / meanings other than these.

[0415] In this disclosure, "A / B" and "at least one of A and B" may be rewritten as each other. In addition, in this disclosure, "A / B / C" may also mean "at least one of A, B and C".

[0416] In this disclosure, terms such as notification, activation, deactivation, indication (or indication), selection, configuration, update, and determination can be overridden. Similarly, terms such as support, control, ability to control, operation, and ability to operate can also be overridden.

[0417] In this disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher-level parameters, fields, Information Elements (IE), settings, etc., can also be modified interchangeably. In this disclosure, Medium Access Control (MAC) elements (MAC ControlElement (CE)), update commands, activation / deactivation commands, etc., can also be modified interchangeably.

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

[0419] In this disclosure, MAC signaling may also use, for example, a MAC Control Element (MACCE) or a MAC Protocol Data Unit (PDU). Broadcast information may also be, for example, a Master Information Block (MIB), a System Information Block (SIB), a Minimum System Information (Remaining Minimum System Information (RMSI)), or Other System Information (OSI).

[0420] In this disclosure, physical layer signaling may also be, for example, downlink control information (DCI), uplink control information (UCI), etc.

[0421] In this disclosure, functions such as discard, abort, delete, truncate, rate match, postpone (postpone), and do not send can be rewritten interchangeably.

[0422] In this disclosure, indexes, identifiers (IDs), indicators, resource IDs, etc., can also be overridden with each other. In this disclosure, time series, lists, sets, groups, clusters, subsets, etc., can also be overridden with each other.

[0423] In this disclosure, the following terms are used: panel, UE panel, panel group, beam, beam group, precoder, uplink (UL) transmitting entity, transmission / reception point (TRP)), base station, spatial relation information (SRI), spatial relation, SRS resource indicator (SRI), control resource set (CORESET), physical downlink shared channel (PDSCH), codeword (CW), transport block (TB), reference signal (RS), antenna port (e.g., demodulation reference signal (DMRS)) port, antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, code division multiplexing (CDM) group, reference signal group, CORESET group, physical uplink control channel (PDSCH)). The Uplink Control Channel (PUCCH) group, PUCCH resource group, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL) and QCL concept can also be rewritten.

[0424] In this disclosure, base stations, gNBs, and networks (NWs) can also be rewritten.

[0425] In this disclosure, cell groups, serving cell groups, primary cell groups (MCG), and secondary cell groups (SCG) can be interchanged. L1 / L2, L1 / L2 signaling, and DCI / MAC CE can also be interchanged. The serving cell can also be replaced with the cell that sends PDSCH. A candidate cell can also refer to a cell that becomes a candidate serving cell through L1 / L2 inter-cell mobility. L1L2-triggered mobility (LTM) and L1 / L2 inter-cell mobility can also be interchanged.

[0426] In this disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and band can be interchanged. In this disclosure, the terms cell, PCI, cell with added PCI, additional cell, other cell, non-serving cell, cell with different PCI, candidate cell, candidate serving cell, cell with a PCI different from the current serving cell, other serving cells, and target cell can also be interchanged. The target cell can also be a cell selected from multiple candidate cells. In this disclosure, handover, change, and update can also be interchanged. The serving cell can also be rewritten as the serving cell before handover or the serving cell after handover.

[0427] In this disclosure, event-based beamforming, event-triggered beamforming, UE-triggered beamforming, and UE-initiated beamforming can be overridden with each other.

[0428] In this disclosure, event-triggered beam reports may also be referred to simply as beam reports / CSI reports / L1-RSRP / SINR beam reports.

[0429] In this disclosure, type 1 beam reports and beam reports for intra-cell beam switching can also be rewritten.

[0430] In this disclosure, type 2 beam reports and inter-cell beam reports can also be rewritten to each other.

[0431] In this disclosure, the beam report of type 2-1 and the beam report for inter-cell beam switching can also be rewritten.

[0432] In this disclosure, the type 2-2 beam report and the beam report used for cell handover can also be rewritten to each other.

[0433] In this disclosure, tables, mappings, and associations can also be rewritten.

[0434] In this disclosure, lists and pools can also be overridden.

[0435] In this disclosure, the (new) MAC CE, UCI, cell handover command, beam handover command, MAC CE for beam reporting, and MAC CE for cell handover can also be rewritten to each other.

[0436] In this disclosure, event-based beamforming reports can also be reported in a PUSCH (e.g., a permissioned PUSCH, a permission-based PUSCH). That is, the reporting content in this disclosure can also be transmitted using at least one of MAC CE / UCI / PUCCH / PUSCH.

[0437] In this disclosure, CSI reports and reports may be adapted from each other.

[0438] In this disclosure, reports, resources used in reports, and resources can be adapted from each other. For example, the first resource and the first report can be adapted from each other, and the second resource and the second report can be adapted from each other.

[0439] In this disclosure, the number of beams and the number of resources can also be rewritten.

[0440] In this disclosure, ACK can also be referred to as an affirmative response, and NACK can also be referred to as a negative response.

[0441] In this disclosure, Serving can also be interchanged with Serving Beam / Serving Cell / SpCell.

[0442] In this disclosure, Neighbor can also be rewritten with beams / cells other than the serving beam / serving cell / SpCell / SCell.

[0443] (Wireless communication method)

[0444] The embodiments disclosed herein can be broadly categorized as follows.

[0445] • Zero Implementation: Various regulations for beam reporting.

[0446] • First implementation: New events for beam reporting.

[0447] • Second implementation method: New rules for beam reporting.

[0448] • Third implementation method: UE operation after beam report triggering.

[0449] The following describes each implementation method based on these principles.

[0450] The UE can also apply the various implementation methods described later to perform beam report control (transmission control). The NW / BS / gNB can also provide / transmit settings / instructions to the UE for the UE to implement this control. Furthermore, the NW / BS / gNB can also perform various controls required to receive the beam report from the UE.

[0451] The event-based beamforming disclosed herein can be applied to any scenario for MIMO / mobility oriented toward Rel.19 and beyond.

[0452] In this disclosure, each implementation method / option can be applied individually or in combination.

[0453] <Empirical Implementation>

[0454] The zeroth implementation involves various provisions for beam reporting.

[0455] <<Settings for events>>

[0456] Regarding the events mentioned above, for Rel.19 MIMO / mobility, either all events or only a portion of the limited events can be supported. For example, if the UE is configured to trigger beam reporting for Rel.19 MIMO / mobility events, the limited events can also be applied. An event set (event set) containing multiple events can also be defined.

[0457] In Rel.19 MIMO / mobility, the same or different events / event sets can also be supported. Which event / event set the UE applies can be defined in advance by the specification or set / indicated by higher-layer signaling / physical layer signaling.

[0458] In addition, priorities can be defined for each event / event set, and the UE can make a decision based on these priorities. For example, the UE can also prioritize events with higher priorities.

[0459] For each of the events described above, a high-level parameter (RRC) can also be set to represent at least one of the following values.

[0460] Event A1: Threshold.

[0461] Event A2: Threshold.

[0462] Event A3: Offset.

[0463] Event A4: Threshold.

[0464] Event A5: Multiple thresholds (e.g., threshold #1, threshold #2).

[0465] Event A6: Offset.

[0466] Event B1: Threshold.

[0467] Event B2: Multiple thresholds (e.g., threshold #1, threshold #2).

[0468] <<Event Inspection>>

[0469] Events can also be examined by averaging the L1-RSRP / SINR for each event / a portion of an event. Figure 7 This is a diagram illustrating an example of a beam report triggered by an event.

[0470] To inspect events, the number of samples S used for averaging L1-RSRP / SINR can be defined in advance or set / indicated by higher-layer signaling / physical layer signaling (e.g., S=5).

[0471] (Variation Example 1)

[0472] However, there may be situations where the number of incident checks and the number of reported L1-RSRP / SINR samples differ. In such cases, the complexity of processing on the UE side may increase. Therefore, the following steps can also be applied.

[0473] Step 1

[0474] No special processing is performed regarding the sample size. That is, the sample size S used for event inspection and the sample size M used for reporting can be different (e.g., S=5, M=3). Figure 7 For example, the UE can also use the average L1-RSRP / SINR based on S samples for event inspection and report the average L1-RSRP / SINR based on M samples.

[0475] Step 2

[0476] The number of samples M used for reporting follows the number of samples S used for event checking. For example, if the UE uses the average L1-RSRP / SINR based on S samples for event checking, the UE can also report the average L1-RSRP / SINR based on S samples. In this case, the UE does not need to store two values ​​(average L1-RSRP / SINR) for event checking and reporting, thus saving memory.

[0477] Step 3

[0478] The UE does not expect the value of S to be different from the value of M. That is, the UE can also expect the value of S to be the same as the value of M.

[0479] (Variation Example 2)

[0480] The UE may also choose not to use the average L1-RSRP / SINR based on S samples for event checking, but instead perform event checking every time S samples are acquired. That is, the UE may also choose not to perform event checking every time samples are acquired, but instead perform event checking once every S times.

[0481] In other words, the period for event checking can also be different from the period for obtaining the sample. For example, the period for event checking can also be longer than the period for obtaining the sample (e.g., 20 milliseconds) (e.g., 100 milliseconds).

[0482] In this case, the average value is not used, so the UE does not need to store the sample value every time, which saves memory.

[0483] <<The content of the beamforming report and the container used for the report>>

[0484] The following can also be supported as part of the report content.

[0485] • Measurements based on SSB / CSI-RS.

[0486] • Measured values ​​of L1-RSRP / L1-RSRP / SINR.

[0487] The number of beams reported can also be variable. In this case, the UE can also determine / decide the number of beams to be reported. This is because if multiple beams meet the conditions (in a valid case), it is preferable to report these multiple (all) beams.

[0488] In addition, it is also possible to configure whether to include the serving beam (the current beam) in the report. This is because it facilitates comparison of the current beam and adjacent beams on the NW side.

[0489] As a container for beam reports, MAC CE or UCI can also be used. That is, the UE can also use MAC CE or UCI to perform / control the transmission of the aforementioned beam reports.

[0490] For example, the UE can also determine the utilization of the reporting container (MAC CE / UCI) based on the report content. Alternatively, the UE can also determine whether the beam report is mobility-oriented or MIMO-oriented based on the report content.

[0491] More specifically, when configured / instructed to include either serving or non-serving beams in the report, the UE can also perform beam reporting using MAC CE (e.g., in the case of mobility). Alternatively, when configured / instructed to include only serving beams in the report (or when configured / instructed not to report non-serving beams), the UE can also perform beam reporting using UCI (e.g., in the case of MIMO).

[0492] Alternatively, if beam reporting for the purpose of cell switching is configured / instructed, the UE may also perform beam reporting using MAC CE (e.g., in mobility scenarios). Alternatively, if beam reporting for the purpose of cell switching is not configured / instructed, the UE may also perform beam reporting using UCI.

[0493] Alternatively, the UE can also switch between performing beam reporting using MAC CE (e.g., in mobility scenarios) and performing beam reporting using UCI via higher-layer instructions. Higher-layer parameters for setting beam reporting using MAC CE can also be parameters associated with mobility / cell switching. Higher-layer parameters for setting beam reporting using UCI can also be parameters not associated with mobility / cell switching.

[0494] Through these means, the UE can appropriately control the beam reporting corresponding to the reported content.

[0495] <First Implementation>

[0496] The first implementation relates to new events for beam reporting. Figure 8 This is a diagram illustrating an example of an event (e.g., event A7) involved in the first embodiment.

[0497] The UE can also receive / set settings from the NW for specific events related to event-based beam reporting. In addition to the events mentioned above, the following new events can be exemplified for specific events.

[0498] The existing events mentioned above can also be defined as new events through any combination. That is, a new event can also be defined based on at least two combinations of existing events.

[0499] For example, events A2 and A3 can be combined to define a new event A7 (see [reference]). Figure 8 The conditions for applying event A7 can also be as follows.

[0500] • The case where the measurement result of the serving cell is worse than the threshold, and the measurement result of the neighboring cell (the value after adding an offset to the measurement result) is better than the measurement result of the SpCell (serving cell) (the value after adding an offset to the measurement result).

[0501] <<Application Conditions>>

[0502] If we express the application conditions of event A7 by formula, then the following examples can be given.

[0503] (Example 1: Trigger / Input Conditions)

[0504] Ms + Hys1 < Threshold, and / or, Mn + Ofn + Ocn - Hys2 < Mp + Ofp + Ocp + Off

[0505] (Example 2: Cancel / Remove from conditions)

[0506] Ms-Hys1 > Threshold, and / or, Mn + Ofn + Ocn-Hys2 < Mp + Ofp + Ocp + Off

[0507] The parameters in the above formula are explained below.

[0508] Ms can also represent the measurement result of the serving cell without considering the offset. For Ms, it can also be expressed in dBm for RSRP and in dB for RSRQ / SINR.

[0509] Hys1 is a hysteresis parameter for this event, which can also be expressed in dB. Hys1 represents a value from 0 to 30 dB and is signaled (defined) within the high-level parameter reportConfigNR, which is related to report settings. Alternatively, the actual dB value can be obtained by multiplying the signaled value by 0.5.

[0510] Threshold is a parameter representing the threshold for this event (A7 / A2). This parameter can be instantiated as a2-Threshold as a value defined within reportConfigNR. Threshold can also be expressed in the same units as Ms (i.e., dBm / dB).

[0511] Mn can also represent the measurement results of neighboring cells without considering offset. Mn can also be expressed in dBm for RSRP and in dB for RSRQ / SINR.

[0512] Ofn can also represent a measurement object-specific offset corresponding to the reference signal (RS) of a neighboring cell. As Ofn, offsetMO can be exemplified in the higher-layer parameter measObjectNR associated with the measurement object corresponding to the neighboring cell.

[0513] Ocn can also represent a cell-specific offset corresponding to a neighboring cell. As an Ocn, it can be an instance of cellIndividualOffset defined within measObjectNR corresponding to the frequency of the neighboring cell. cellIndividualOffset is set to 0 if no neighboring cell is specified.

[0514] Hys2 is the hysteresis parameter for this event, which can also be expressed in dB. Hys2 can also be defined within reportConfigNR.

[0515] Mp can also represent the measurement result of the serving cell without considering the offset. Mp can also be expressed in dBm for RSRP and in dB for RSRQ / SINR.

[0516] Ofp can also represent a measurement object-specific offset corresponding to the serving cell. As Ofp, offsetMO can be defined in the higher-level parameter measObjectNR associated with the measurement object corresponding to the serving cell.

[0517] Ocp can also represent a cell-specific offset corresponding to the serving cell. Ocp can also be defined within measObjectNR.

[0518] Off is a parameter representing the offset of the event (A7 / A3). This parameter can be instantiated as a3-Offset as a value defined in reportConfigNR.

[0519] The third embodiment describes the UE operation when the above application conditions are met.

[0520] <<Measured Values>>

[0521] The measured values ​​for each reference signal can also be at least one of the following.

[0522] ·RSRP / SINR.

[0523] ·L3-RSRP / SINR.

[0524] ·L1-RSRP / SINR.

[0525] • The average / filtered value of multiple L1-RSRP / SINR values ​​for one or more identical / different beams in a cell.

[0526] The instantaneous L1-RSRP / SINR value (i.e., the instantaneous value) can change dynamically. Therefore, control oscillations (frequent switching of the beam reporting trigger state) in beam reporting triggering can be avoided by averaging multiple (X) L1-RSRP / SINR values ​​(e.g., X=5).

[0527] Alternatively, the L1-RSRP / SINR values ​​can be averaged across Z (e.g., Z=2) beams / RS within the same cell, thereby avoiding control oscillations during beam reporting triggering as described above. In this case, the UE needs to report one or more beams within the cell for the NW to determine the optimal beam.

[0528] When reporting a single beam, the UE can also select from multiple beams the one that represents the largest measurement value (RSRP / SINR value) in the cell.

[0529] When reporting more than one (other than two) beams, the UE can also select the beam to be reported in descending order of the measured values ​​in that cell / any cell.

[0530] <<Delay>>

[0531] Regarding hysteresis, at least one of the following can also be applied.

[0532] For this event, one or more (e.g., two) delays can also be set / indicated.

[0533] For example, if a hysteresis is set, the hysteresis can also be used to compare the serving cell with a threshold, or to compare the serving cell with neighboring cells.

[0534] The purpose for which this hysteresis is used can be set / indicated through higher-layer signaling (RRC / MAC CE) / physical layer signaling (DCI), or it can be defined in advance by specifications, or it can be determined according to the UE's capabilities.

[0535] For example, in the case of DCI / MAC CE, a 1-bit flag can also be used. In the case of RRC, new flags can also be introduced (e.g., parameters independent of each purpose).

[0536] Even with a single hysteresis, a hysteresis value common to multiple purposes can be utilized. That is, a single hysteresis can be used for multiple purposes.

[0537] When multiple (two) hysteresis are set, the multiple hysteresis can also be used separately for comparing the serving cell with a threshold, and for comparing the serving cell with neighboring "cells". The values ​​of each hysteresis can be the same or different.

[0538] The maximum number of hysteresis that can be set / indicated can be set / indicated through higher-layer signaling / physical layer signaling, or it can be defined in advance by specifications, or it can be determined by UE capabilities.

[0539] <<Parameters for the time until triggering (Time to trigger: TTT)>>

[0540] TTT can also apply at least one of the following Alt1~Alt3.

[0541] (Alt1)

[0542] Use the same parameters as the RRC parameters for other events.

[0543] (Alt2)

[0544] A new RRC parameter is introduced for this event.

[0545] (Alt3)

[0546] You can also define / utilize new timers and counters in the MAC layer.

[0547] <<Specific examples>>

[0548] like Figure 8 As shown, in event A7, which is defined by the combination of events A2 and A3, a timer for reporting starts when the trigger condition is met. A hysteresis can also be applied to the trigger condition for event A2.

[0549] Next, after the time to trigger (TTT) has elapsed, event-based beam reporting begins.

[0550] Reports can also be executed multiple times (e.g., reports #1 to #3, for example, periodically).

[0551] Furthermore, the report can also be cancelled / stopped at this time if certain cancellation conditions are met. An offset / hysteresis can also be applied to event A3 within the cancellation conditions.

[0552] According to this implementation, the UE can appropriately control beam reporting based on new events.

[0553] <Second Implementation>

[0554] The second implementation involves new rules for beam reporting.

[0555] Multiple events can also be set for an event-based beam report.

[0556] In this disclosure, multiple events can be configured and rewritten with any combination of events (new events) configured in the first embodiment.

[0557] <<Method 2-0>>

[0558] The UE may also send an event-based beam report by following at least one of the following conditions.

[0559] (Alt1)

[0560] The condition for one of the set [multiple] events is met (similar to existing L3 measurement reports). In this case, the UE can also include the event (event ID) corresponding to the met condition in the report content and send it.

[0561] (Alt2)

[0562] The condition that all the set events are met. In this case, the existing events can be utilized.

[0563] The conditions for applying Alt1 / Alt2 can be set / indicated either through higher-layer signaling (RRC / MAC CE) / physical layer signaling (DCI), or predefined by specifications, or determined by UE capabilities.

[0564] For example, in the case of DCI / MAC CE, a 1-bit flag can also be used. In the case of RRC, new flags can also be introduced (e.g., parameters independent of each purpose).

[0565] <<Method 2-1>>

[0566] When Alt2 is specified in mode 2-0 above, it is necessary to specify which event's TTT (Time To To TTT) should be used. For example, in existing specifications, TTT can be set for each event. Figure 9 This is a diagram illustrating an example of the correspondence between the combination of events involved in Mode 2-1 and the time up to the trigger.

[0567] In the case of a combination of multiple events (where all conditions of the events are met), the UE may also determine the application of TTT by following at least one of the following criteria.

[0568] (Alt1)

[0569] The UE can also apply TTT for a specific event among multiple events. The UE can also select / determine a specific event based on at least one of the following Alt1-1 to Alt1-2.

[0570] (Alt1-1)

[0571] Specific events can also be defined in advance through specifications.

[0572] [Example 1]

[0573] like Figure 9 As shown, the association between combinations of events and events corresponding to the applied TTT can also be specified. Figure 9 The table (association) can also be set via higher-level signaling.

[0574] Specifically, such as Figure 9 As shown, in the combination of events A2 and A3, TTT is associated with event A3 as a reference. Furthermore, in the combination of events A2 and A6, TTT is associated with event A6 as a reference.

[0575] When a combination of events A2 and A3 is set / indicated, the UE can also select / apply the TTT of event A3 (the TTT corresponding to the setting of event A3).

[0576] [Example 2]

[0577] Alternatively, the UE can also apply the TTT corresponding to the event that finally satisfies the conditions.

[0578] (Alt1-2)

[0579] Specific events can also be determined through RRC settings.

[0580] [Example 1]

[0581] New flags can also be introduced in the event settings. For example, the UE can determine that if the new flag is True, then the TTT corresponding to that specific event will be referenced; if the new flag is False, then it will not be referenced.

[0582] [Example 2]

[0583] The UE can also refer to the TTT parameters set in the event settings for a specific event. For example, the TTT can also be set (specified) for only one event setting (a specific event).

[0584] (Alt2)

[0585] The UE can also apply TTT for all events. That is, the UE can also send a beam report after the TTT for all set events has elapsed (provided the TTT conditions have been met). In other words, the UE can also send a beam report after the longest TTT of the set events has elapsed.

[0586] (Alt3)

[0587] The UE can also utilize new RRC parameters, or new timers and counters in the MAC layer. That is, the UE can also ignore the TTT set in the event settings and apply other [new] TTTs.

[0588] <Variation Example>

[0589] When a new event (a combination of multiple events) is defined, TTT can be set / specified in the settings of the new event, either together with or independently of other parameters. Parameters associated with the new event can also be applied within the new event.

[0590] Priorities can also be specified for the selection of TTTs for specific events. UEs can then follow these priorities to select / determine the TTT for a specific event.

[0591] Based on this structure, the UE can appropriately control the triggering / reporting timing of event-based beam reporting.

[0592] <Third Implementation Method>

[0593] The third implementation involves UE operations after beam report triggering.

[0594] Regardless of the type of event, if the triggering condition for an event-based beam report is met, and subsequently other conditions (such as the passage of TTT) are met (after these conditions are met), the UE may also perform the following operations 1 to 2.

[0595] <<Operation 1>>

[0596] The UE can also send UCI / MAC CEs in the PUCCH / PUSCH. These UCI / MAC CEs can also include event-based beam reports, scheduling requests (SRs), etc.

[0597] Regarding this sending, the following control (sending cancellation) can also be applied.

[0598] (Cancellation of sending)

[0599] If the UE performs a transmission [only] once, the cancellation condition may not be applied.

[0600] In cases where the UE performs multiple transmissions [periodically], specific cancellation conditions can be applied to cancel the transmission. Therefore, it is necessary to specify specific cancellation conditions and accompanying parameters.

[0601] As a parameter, the reporting / sending period (X slot / symbol / millisecond) can also be set, for example.

[0602] As a cancellation condition, Alt1 to Alt5 can also be specified. The UE can also cancel the triggered beam report based on at least one of Alt1 to Alt5.

[0603] (Alt1)

[0604] Apply the rules of the existing specifications for L3 measurement reports. For example, the following formula can also be applied as a condition: Ms-Hys > Threshold, and / or, Mn + Ofn + Ocn-Hys < Mp + Ofp + Ocp + Off

[0605] (Alt2)

[0606] In the MAC layer, timers are used. For example, the UE can cancel the report when the timer expires.

[0607] (Alt3)

[0608] In the MAC layer, counters are used. For example, the UE can also cancel the report if a set / predefined in the specification / determined by the UE's capabilities are reached.

[0609] (Alt4)

[0610] The actual reporting time (scheduled, periodic, etc.) / number of reports can also be defined in advance through specifications.

[0611] (Alt5)

[0612] A new DL signal for cancellation can be introduced, or an existing DL signal for cancellation can be utilized. For example, the report can be cancelled if the UE receives a specific DL signal (the DL signal that triggers cancellation).

[0613] If the cancellation conditions described above are met for a certain resource (cell / beam), the UE may also apply at least one of the following Opt1 to Opt2 operations.

[0614] <Opt1>

[0615] The UE can also use MAC CE / UCI to explicitly or implicitly report that the cancellation condition has been met. As an explicit method, a 1-bit flag can be specified, for example. Alternatively, as an implicit method, the gNB can determine the outcome based on the content's order / result information.

[0616] Regarding the MAC CE / UCI used for reporting, either the existing MAC CE / UCI can be used for event-based beam reporting, or a new MAC CE / UCI can be introduced specifically for event-based beam reporting.

[0617] <Opt2>

[0618] The UE can also stop sending reports.

[0619] Which Opt1 / Opt2 operation to apply can be set / indicated either through higher-layer signaling (RRC / MAC CE) / physical layer signaling (DCI), or it can be predefined by the specification, or it can be determined by the UE's capabilities.

[0620] <<Operation 2>>

[0621] The UE may also perform at least one of the following operations after a certain time has elapsed following the transmission of an event-based beam report. Figure 10 This is a diagram illustrating an example of the time sequence of operation of the event-based beam reporting according to the third embodiment.

[0622] Operation 2-1: Activation of TCI state.

[0623] Operation 2-2: UL synchronization (RACH based on PDCCH order, TA measurement based on UE, etc.).

[0624] Operation 2-3: TRS tracking.

[0625] • Operation 2-4: Handover to a neighboring cell / beam / RS that meets specific events.

[0626] • Operation 2-5: Reception of ACK (DCI) for event-based beam reporting.

[0627] The aforementioned UE operations can also be performed at all times (each time an event-based beam report is received). Furthermore, as... Figure 10 As shown, operations 2-1 to 2-5 can also be executed after a certain period of time following the transmission of the event-based beam report. Furthermore, operations 2-1 to 2-4 can also be executed after a certain period of time following the execution of operation 2-5.

[0628] A certain time (Y slot / symbol / millisecond) can be set / indicated by higher layer signaling (RRC / MAC CE) / physical layer signaling (DCI), or it can be defined in advance by the specification, or it can be determined according to the UE's capabilities.

[0629] Furthermore, this time can also vary depending on each UE operation / scenario (e.g., intra-frequency / inter-frequency / CU / DU / cell / beam).

[0630] According to this implementation, the UE can appropriately control the operation after beam reporting is triggered.

[0631] <Supplement>

[0632] <<Information Notification to UE>>

[0633] In the above embodiments, any information [notification from the network (NW) (e.g., base station (BS))] to the UE (in other words, the reception of any information from the BS in the UE) can also be delivered using physical layer signaling (e.g., DCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PDCCH, PDSCH, reference signals), or combinations thereof.

[0634] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new Logical Channel ID (LCID) that is not specified in the existing standard in the MAC subheader.

[0635] When the above notification is made through a DCI, the notification can also be made through specific fields of the DCI, the Radio Network Temporary Identifier (RNTI) used in the scrambling of the Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc.

[0636] Furthermore, the notification of any information to the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0637] <<Notification of Information from UE>>

[0638] The notification of arbitrary information from the UE to the NW (in other words, the transmission / reporting of arbitrary information from the UE to the BS) in the above embodiments can also be performed using physical layer signaling (e.g., UCI), higher layer signaling (e.g., RRC signaling, MAC CE), specific signals / channels (e.g., PUCCH, PUSCH, PRACH, reference signals), or combinations thereof.

[0639] In the case where the above notification is made via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC subheader that is not specified in the existing standard.

[0640] In cases where the above notification is sent via UCI, the above notification may also be sent using PUCCH or PUSCH.

[0641] Furthermore, the notification of any information from the UE in the above embodiments can also be carried out periodically, semi-persistently, or non-periodically.

[0642] <<Application of Each Implementation Method>>

[0643] In the UE / BS, a specific processing / operation / control / conception / information for at least one of the above-described implementations may also be applied (used) if any one or more of the following conditions are met: • High-level parameters are set to represent the specific processing / operation / control / concept / information mentioned above.

[0644] The specific processing / operation / control / concept / information mentioned above is determined based on associated high-level parameters.

[0645] The aforementioned specific processing / operation / control / concept / information is specified / activated / triggered via MAC CE / DCI / UCI / resource / channel / RS.

[0646] • The report or support indicates the specific UE capability (UE capability) of the aforementioned specific processing / operation / control / conception / information (or associated information).

[0647] The application of the aforementioned specific processing / operation / control / conception / information is judged based on specific conditions.

[0648] The specific UE capability mentioned above can also represent at least one of the following: • Supports specific processing / operation / control / information for at least one of the above-described embodiments.

[0649] • Supports event-triggered beam reporting.

[0650] • Supports beam reporting of type 1 / 2 / 2-1 / 2-2.

[0651] • Supports MIMO / mobility from Rel.19 onwards.

[0652] • Supports event-based beam reporting using MAC CE / UCI.

[0653] • Supports the combination of events.

[0654] • Supports parameters related to the trigger / cancellation conditions corresponding to the event combination.

[0655] • Supports various UE operations triggered by event-based beam reporting.

[0656] Furthermore, the aforementioned specific UE capabilities can be capabilities that apply across all frequencies (frequency-independent and common), capabilities that apply to each frequency (e.g., one or a combination of cells, bands, band combinations, BWPs, component carriers, etc.), capabilities that apply to each frequency range (e.g., Frequency Range 1 (FR1)), FR2, FR3, FR4, FR5, FR2-1, FR2-2), capabilities that apply to each subcarrier spacing (SCS) or capabilities that apply to each feature set (FS) or each feature set per component carrier (FSPC).

[0657] Furthermore, the aforementioned specific UE capabilities can be either capabilities that apply to all duplex modes (commonly regardless of the duplex mode) or capabilities that apply to each duplex mode (e.g., Time Division Duplex (TDD) and Frequency Division Duplex (FDD)).

[0658] UE / BS may also follow the operations specified in the existing 3GPP version if the above conditions are not met.

[0659] (Postscript)

[0660] Regarding one embodiment of this disclosure (MIMO for the first / second embodiment), the following invention is noted.

[0661] [Postscript 1]

[0662] A terminal having: The receiving unit receives settings related to the triggering conditions for event-based beam reporting; and The control unit, based on the aforementioned settings, controls the event-based beamforming. The settings support the combination of multiple events. The triggering condition is based on a comparison of the current or other beam measurement results with a threshold.

[0663] [Postscript 2]

[0664] As described in Appendix 1, the triggering condition includes a hysteresis parameter for a specific event or a parameter representing an offset.

[0665] [Postscript 3]

[0666] As described in Appendix 1 or Appendix 2, the terminal wherein the control unit performs control to include the ID corresponding to the event that has met the triggering condition in the beam report.

[0667] [Postscript 4]

[0668] The terminal as described in any one of Annexes 1 to 3, wherein the control unit determines, based on specific settings or instructions, whether to report one or more of a plurality of events that meet the triggering conditions.

[0669] (Postscript)

[0670] Regarding one embodiment of this disclosure (mobility in relation to the first / second embodiment), the following invention is noted.

[0671] [Postscript 1]

[0672] A terminal having: The receiving unit receives settings related to the triggering conditions for event-based beam reporting; and The control unit, based on the aforementioned settings, controls the event-based beamforming. The settings support the combination of multiple events. The triggering condition is based on a comparison of the measurement results of the serving cell or neighboring cells with a threshold.

[0673] [Postscript 2]

[0674] As described in Appendix 1, the terminal wherein the triggering condition includes at least one of a hysteresis parameter for a specific event and a parameter representing a specific offset of the serving cell or a neighboring cell.

[0675] [Postscript 3]

[0676] The terminal as described in Appendix 1 or Appendix 2, wherein, The settings include conditions for canceling beam reporting. The control unit cancels the beam report based on the cancellation condition.

[0677] [Postscript 4]

[0678] The terminal as described in any one of Annexes 1 to 3, wherein, The settings include a parameter for the time to trigger (TTT). The control unit determines the applicable TTT based on the parameters for that TTT.

[0679] (Postscript)

[0680] Regarding one embodiment (third embodiment) of this disclosure, the invention is described below.

[0681] [Postscript 1]

[0682] A terminal having: The receiving unit receives settings related to trigger conditions that support a combination of multiple events for event-based beam reporting; and The control unit, based on the aforementioned settings, controls the event-based beamforming. If, in addition to the aforementioned triggering conditions, a condition regarding the time to trigger (TTT) is also met, the control unit applies a specific operation.

[0683] [Postscript 2]

[0684] As described in Appendix 1, the control unit controls the cancellation of the beam report based on the cancellation conditions included in the settings.

[0685] [Postscript 3]

[0686] As described in Appendix 1 or Appendix 2, the control unit, after the TTT, performs at least one of the following: activation of the Transmission Setting Indication (TCI) state, uplink (UL) synchronization, tracking of the Tracking Reference Signal (TRS), and cell or beam switching.

[0687] [Postscript 4]

[0688] As in any one of Annexes 1 to 3, the control unit controls the reception of the positive response (ACK) to the event-based beam report after the TTT.

[0689] (Wireless communication system)

[0690] The structure of a wireless communication system according to one embodiment of this disclosure will now be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of this disclosure.

[0691] Figure 11This is a diagram illustrating an example of the schematic structure of a wireless communication system according to one embodiment. The wireless communication system 1 (also referred to simply as System 1) may also be a system that uses Long Term Evolution (LTE) or 5th generation mobile communication system New Radio (5G NR) as standardized by the Third Generation Partnership Project (3GPP) to achieve communication.

[0692] Furthermore, the wireless communication system 1 can also support dual connectivity between multiple radio access technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC can 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)), etc.

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

[0694] Wireless communication system 1 can also support dual connectivity between multiple base stations within the same RAT (e.g., MN and SN are dual connectivity between NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0695] The wireless communication system 1 may also include a base station 11 forming a macro cell C1 with a relatively wide coverage area, and a base station 12 (12a-12c) configured within the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located within at least one cell. The configuration, number, shape, size, etc., of each cell and the user terminal 20 are not limited to the manner shown in the figure. Hereinafter, without distinguishing between base stations 11 and 12, they will be collectively referred to as base station 10.

[0696] Alternatively, the wireless communication system 1 can also utilize Multiple Input Multiple Output (MIMO). For example, a cell can be formed by one antenna / base station 10 or by multiple antennas / base stations 10. A [virtual] cell (e.g., also called a super cell) can also be composed of multiple [virtual] cells (e.g., also called sub-cells). A super cell can also be equivalent to a cell with a fixed physical range, and a sub-cell can also be equivalent to a cell with a semi-static / dynamically varying physical range. In this case, the wireless communication system 1 can also be called a cell-free system.

[0697] User terminal 20 may also connect to at least one of multiple base stations 10. User terminal 20 may also utilize at least one of carrier aggregation (CA) using multiple component carriers (CC) and dual connectivity (DC).

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

[0699] In addition, user terminal 20 can also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) to communicate in each CC.

[0700] Multiple base stations 10 can also be connected via wired (e.g., fiber optic cable based on the Common Public Radio Interface (CPRI), X2 / Xn 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 is equivalent to a host station, can also be referred to as an Integrated Access Backhaul (IAB) donor, and base station 12, which is equivalent to a relay station, can also be referred to as an IAB node.

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

[0702] The core network 30 may also include, for example, user plane functions (UPF), access and mobility management functions (AMF), session management functions (SMF), unified data management (UDM), application functions (AF), data network (DN), location management functions (LMF), and network functions (NF) such as operation, administration and maintenance (OAM). Alternatively, multiple functions can be provided through a single network node. Furthermore, communication with external networks (e.g., the Internet) can also be achieved via the DN.

[0703] User terminal 20 can also be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0704] In wireless communication system 1, wireless access methods based on Orthogonal Frequency Division Multiplexing (OFDM) can also be used. For example, in at least one of the downlink (DL) and uplink (UL) links, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA) can also be used.

[0705] The wireless access method can also be referred to as a waveform. In addition, in the wireless communication system 1, other wireless access methods (e.g., other single-carrier transmission methods, other multi-carrier transmission methods) can also be used in the wireless access methods of UL and DL.

[0706] In the wireless communication system 1, the downlink channel can also be a shared downlink channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), or a downlink control channel (Physical Downlink Control Channel (PDCCH)) shared by each user terminal 20.

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

[0708] User data, high-level control information, and System Information Blocks (SIBs) are transmitted via the PDSCH. User data and high-level control information can also be transmitted via the PUSCH. In addition, Master Information Blocks (MIBs) can also be transmitted via the PBCH.

[0709] Lower-layer control information can also be transmitted via PDCCH. This lower-layer control information may include, for example, downlink control information (DCI), which includes scheduling information for at least one of PDSCH and PUSCH.

[0710] Additionally, the DCI that schedules PDSCH can also be called DL allocation, DL DCI, etc., and the DCI that schedules PUSCH can also be called UL authorization, UL DCI, etc. Furthermore, PDSCH can be rewritten as DL data, and PUSCH can be rewritten as UL data.

[0711] In PDCCH detection, a Control Resource Set (CORESET) and a search space can also be utilized. A CORESET corresponds to the resources used to search for DCIs. The search space corresponds to the search area and search method for PDCCH candidates. A CORESET can also be associated with one or more search spaces. The UE can also monitor CORESETs associated with a specific search space based on search space settings.

[0712] A search space can also correspond to one or more PDCCH candidates equivalent to one or more aggregation levels. One or more search spaces can also be referred to as a search space set. In addition, the terms "search space", "search space set", "search space setting", "search space set setting", "CORESET", and "CORESET setting" in this disclosure can be rewritten interchangeably.

[0713] The PUCCH can also transmit uplink control information (uplink control information (UCI)) that includes at least one of the following: Channel State Information (CSI), delivery confirmation information (e.g., also known as Hybrid Automatic Repeat Request ACK Knowledge (HARQ-ACK), ACK / NACK, etc.), and Scheduling Request (SR). The PRACH can also transmit random access preambles used for establishing connections with the cell.

[0714] In addition, in this disclosure, downlink, uplink, etc., may be described without the word "link". Furthermore, various channels may be described without the word "physical".

[0715] In wireless communication system 1, synchronization signals (SS) and downlink reference signals (DL-RS) can also be transmitted. In wireless communication system 1, DL-RS can also transmit cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), positioning reference signals (PRS), and phase tracking reference signals (PTRS).

[0716] Synchronization signals can be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block containing SS (PSS, SSS) and PBCH (and DMRS for PBCH) can also be called an SS / PBCH block, SS block (SSB), etc. In addition, SS, SSB, etc. can also be called reference signals.

[0717] Furthermore, in wireless communication system 1, the uplink reference signal (UL-RS) can also transmit measurement reference signals (sounding reference signals (SRS)) and demodulation reference signals (DMRS). Additionally, DMRS can also be referred to as user terminal-specific reference signals (UE-specific reference signals).

[0718] (Base station)

[0719] Figure 12 This diagram illustrates an example of the structure of a base station according to one embodiment. The base station 10 includes a control unit 110, a transmit / receive unit 120, a transmit / receive antenna 130, and a transmission path interface (transmission line interface) 140. Alternatively, the control unit 110, the transmit / receive unit 120, the transmit / receive antenna 130, and the transmission path interface 140 may each be provided in more than one manner.

[0720] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the base station 10 may also possess other functional blocks required for wireless communication. A portion of the processing of each unit described below may also be omitted.

[0721] The control unit 110 performs overall control of the base station 10. The control unit 110 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the art to which this disclosure pertains.

[0722] The control unit 110 can also control signal generation and scheduling (e.g., resource allocation, mapping). The control unit 110 can also control transmission, reception, and measurement using the transmit / receive unit 120, transmit / receive antenna 130, and transmission path interface 140. The control unit 110 can also generate data, control information, sequences, etc., to be transmitted as signals and forward them to the transmit / receive unit 120. The control unit 110 can also perform call processing (setting, releasing, etc.) of the communication channel, status management of the base station 10, and management of wireless resources.

[0723] The transmitting / receiving unit 120 may also include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmitting processing unit 1211 and a receiving processing unit 1212. The transmitting / receiving unit 120 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0724] The transmitting and receiving unit 120 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 1211 and an RF unit 122. The receiving unit can also be composed of a receiving processing unit 1212, an RF unit 122, and a measurement unit 123.

[0725] The transmitting and receiving antenna 130 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

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

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

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

[0729] The transmitting and receiving unit 120 (transmitting processing unit 1211) can 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, and digital-to-analog conversion on the bit string to be transmitted, and output the baseband signal.

[0730] The transmitting and receiving unit 120 (RF unit 122) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 130.

[0731] On the other hand, the transmitting and receiving unit 120 (RF unit 122) can also amplify, filter, and demodulate the signals of the wireless frequency band received through the transmitting and receiving antenna 130 into the baseband signal.

[0732] The transmitting and receiving unit 120 (receiving and processing unit 1212) can also perform receiving and processing on the acquired baseband signal, including analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (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 acquire user data, etc.

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

[0734] The transmission path interface 140 can also transmit and receive signals (backhaul signaling) between the device included in the core network 30 (e.g., the network node providing the NF), other base stations 10, etc., and can also acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

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

[0736] Additionally, base station 10 can be separated into three elements: Radio Unit (RU), Distributed Unit (DU), and Central Unit (CU). For example, the RU can implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level physical layer functions (precoding, IFFT, FFT, etc.). The DU can implement higher-level physical layer functions (from coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU can also implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0737] In this disclosure, base station 10 may include a device that implements all the functions of RU, DU, and CU, or it may include multiple devices that implement a portion of the functions of RU, DU, and CU respectively and are interconnected. In this disclosure, base station 10 may also be rewritten in relation to RU / DU / CU.

[0738] Additionally, the transmit / receive unit 120 can also transmit settings related to trigger conditions for event-based beam reports. The control unit 110 can also control the reception of the event-based beam reports transmitted from the terminal based on these settings. Multiple events can also be combined in these settings. The trigger conditions can also be based on a comparison of current or other beam measurement results with a threshold.

[0739] The triggering condition can also be based on a comparison of the measurement results of the serving cell or neighboring cells with a threshold.

[0740] The transmitting / receiving unit 120 can also transmit settings related to trigger conditions that support a combination of multiple events for event-based beam reporting. The control unit 110 can also, based on these settings, control the reception of the event-based beam report transmitted from the terminal by applying specific operations when conditions for the time to trigger (TTT) are met, in addition to the trigger conditions.

[0741] (User terminal)

[0742] Figure 13 This diagram illustrates an example of the structure 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. Alternatively, more than one of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be included.

[0743] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it is also conceivable that the user terminal 20 may also have other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

[0744] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., which are described based on common knowledge in the technical field to which this disclosure pertains.

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

[0746] The transmitting / receiving 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 transmitting processing unit 2211 and a receiving processing unit 2212. The transmitting / receiving unit 220 may be composed of transmitters / receivers, RF circuits, baseband circuits, filters, phase shifters, measurement circuits, transmitting / receiving circuits, etc., as described based on common knowledge in the art to which this disclosure pertains.

[0747] The transmitting and receiving unit 220 can be configured as a single integrated transmitting and receiving unit, or it can be composed of a transmitting unit and a receiving unit. The transmitting unit can also be composed of a transmitting processing unit 2211 and an RF unit 222. The receiving unit can also be composed of a receiving processing unit 2212, an RF unit 222, and a measurement unit 223.

[0748] The transmitting and receiving antenna 230 can be constructed from an antenna, such as an array antenna, as described based on common knowledge in the art to which this disclosure pertains.

[0749] The transmitting / receiving unit 220 can also receive the downlink channel, synchronization signal, downlink reference signal, etc., mentioned above. The transmitting / receiving unit 220 can also transmit the uplink channel, uplink reference signal, etc., mentioned above.

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

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

[0752] The transmitting and receiving unit 220 (transmitting processing unit 2211) can also perform channel coding (which may 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 the baseband signal.

[0753] Furthermore, whether or not to apply DFT processing can be based on the transform precoding settings. For a certain channel (e.g., PUSCH), if transform precoding is enabled, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above for transmitting the channel using the DFT-s-OFDM waveform; otherwise, the transmit / receive unit 220 (transmit processing unit 2211) can perform DFT processing as described above for transmitting the channel without performing DFT processing.

[0754] The transmitting and receiving unit 220 (RF unit 222) can also perform modulation, filtering, amplification, etc. on the baseband signal to the wireless frequency band, and transmit the wireless frequency band signal through the transmitting and receiving antenna 230.

[0755] On the other hand, the transmitting and receiving unit 220 (RF unit 222) can also amplify, filter, demodulate, etc., the signals of the wireless frequency band received by the transmitting and receiving antenna 230.

[0756] The transmitting and receiving unit 220 (receiving and processing unit 2212) can also perform receiving and processing on the acquired baseband signal, 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 obtain user data.

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

[0758] Additionally, the measurement unit 223 can also derive channel measurements for CSI calculation based on channel measurement resources. Channel measurement resources can be, for example, non-zero power (NZP) CSI-RS resources. Furthermore, the measurement unit 223 can also derive interference measurements for CSI calculation based on interference measurement resources. Interference measurement resources can be at least one of NZP CSI-RS resources for interference measurement, CSI-Interference Measurement (IM) resources, etc. Additionally, CSI-IM can also be referred to as CSI-Interference Management (IM), and can be interchanged with zero power (ZP) CSI-RS. Furthermore, in this disclosure, CSI-RS, NZP CSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

[0759] Alternatively, the transmitting and receiving units of the user terminal 20 in this disclosure may also be composed of at least one transmitting / receiving unit 220 and transmitting / receiving antenna 230.

[0760] Additionally, the transmit / receive unit 220 can also receive settings related to trigger conditions for event-based beam reporting. The control unit 210 can also control the event-based beam reporting based on these settings. The settings can also support combinations of multiple events. The trigger conditions can also be based on a comparison of current or other beam measurements with a threshold. The trigger conditions can also include hysteresis parameters for specific events or parameters representing offsets. The control unit 210 can also control the inclusion of the ID corresponding to an event that satisfies the trigger conditions in the beam report. The control unit 210 can also determine whether to report one or more events that satisfy the trigger conditions based on specific settings or indications.

[0761] The triggering condition may also be based on a comparison of the measurement results of the serving cell or neighboring cells with a threshold. The triggering condition may also include at least one parameter representing a hysteresis parameter for a specific event and a parameter representing a specific offset of the serving cell or neighboring cell. The setting may also include a cancellation condition for beam reporting. The control unit 210 may also cancel the beam reporting based on this cancellation condition. The setting may also include a parameter for the time to trigger (Time to trigger: TTT). The control unit 210 may also determine the applied TTT based on the parameter for this TTT.

[0762] The transmit / receive unit 220 can also receive settings related to trigger conditions that support a combination of multiple events for event-based beam reporting. The control unit 210 can also control the event-based beam reporting based on these settings. The control unit 210 can also apply specific operations if, in addition to the trigger conditions, conditions for the time to trigger (TTT) are met. The control unit 210 can also control the cancellation of the beam reporting based on cancellation conditions included in the settings. The control unit 210 can also, after the TTT has elapsed, perform at least one of the following: activation of the Transmit Setting Indication (TCI) state, uplink (UL) synchronization, tracking of the Tracking Reference Signal (TRS), and cell or beam handover. The control unit 210 can also, after the TTT has elapsed, control the reception of positive acknowledgments (ACKs) for the event-based beam reporting.

[0763] (Hardware structure)

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

[0765] Here, the functions include judgment, decision, determination, calculation, calculation, processing, export, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, regard as, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that implements the sending function can also be called a transmitting unit, transmitter, etc. As described above, the implementation method of any of them is not particularly limited.

[0766] For example, in one embodiment of this disclosure, the base station, user terminal, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 14 This is a diagram illustrating an example of the hardware structure of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 described above can also be physically configured as a computer device including a processor 1001, a memory 1002, a storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0767] Furthermore, in this disclosure, terms such as apparatus, circuit, device, section, and unit can be interchanged. The hardware structure of base station 10 and user terminal 20 can be configured to include one or more of the apparatuses shown in the figures, or it can be configured not to include any of the apparatuses.

[0768] For example, only one processor 1001 is shown, but there can be multiple processors. Furthermore, processing can be performed by one processor, or simultaneously, sequentially, or by two or more processors using other methods. Additionally, processor 1001 can be implemented using more than one chip.

[0769] The functions of the base station 10 and the user terminal 20 are implemented, for example, by reading specific software (programs) 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 device 1003.

[0770] The processor 1001, for example, enables the operating system to operate and control the computer as a whole. The processor 1001 may also be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic devices, registers, etc. For example, at least a portion of the control unit 110 (210), the transmit / receive unit 120 (220), etc., described above may also be implemented by the processor 1001.

[0771] 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 performs various processes accordingly. As a program, a program that causes the computer to perform 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 operated in the processor 1001; similar implementations can be made for other functional blocks.

[0772] The memory 1002 may also be a computer-readable recording medium, such as being composed of at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage media. The memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. The memory 1002 is capable of storing executable programs (program code), software modules, etc., for implementing the wireless communication method according to an embodiment of this disclosure.

[0773] Storage device 1003 may also be a computer-readable recording medium, such as a flexible disc, floppy disk, optical disk (e.g., compact disc ROM, CD-ROM), digital multifunction disk, Blu-ray disc, removable disk, hard disk, smart card, flash memory device (e.g., card, stick, key drive), stripe, database, server, or at least one other suitable storage medium. Storage device 1003 may also be referred to as an auxiliary storage device.

[0774] The communication device 1004 is hardware (transmitting and receiving device) used for communication between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network interface card (NIC), communication module, etc. To implement at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD), the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. For example, the aforementioned transmit / receive unit 120 (220) and transmit / receive antenna 130 (230) may also be implemented by the communication device 1004. The transmit / receive unit 120 (220) may also be implemented by physically or logically separating the transmit unit 120a (220a) and the receive unit 120b (220b).

[0775] Input device 1005 is an input device that receives input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, light-emitting diode (LED) lamp, etc.). Alternatively, input device 1005 and output device 1006 can also be an integrated structure (e.g., a touch panel).

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

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

[0778] In addition, the devices included in the core network 30 (e.g., network nodes that provide NF) can also be implemented through the functional block / hardware structure described above.

[0779] (Variation example)

[0780] Furthermore, the terms described in this disclosure, as well as those necessary for understanding this disclosure, may be replaced with terms that have the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be interchanged. Additionally, a signal may also be a message. A reference signal can also be abbreviated as RS, and may be referred to as pilot, pilot signal, etc., depending on the applied standard. Furthermore, a component carrier (CC) may also be referred to as cell, frequency carrier, carrier frequency, etc.

[0781] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute 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 (e.g., 1 ms) independent of the parameter set (numerology).

[0782] Here, the parameter set can also be communication parameters applied in at least one of the transmission and reception of a signal or channel. For example, the parameter set can also represent at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame 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.

[0783] In the time domain, a time 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.). In addition, a time slot can also be a time unit based on a set of parameters.

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

[0785] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also use their respective other names. Furthermore, the time units such as frames, subframes, time slots, mini-time slots, and symbols in this disclosure can be interchanged.

[0786] For example, a subframe can also be called a TTI, multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe in existing LTE (1ms), a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but rather a time slot, mini-time slot, etc.

[0787] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules radio resources (frequency bandwidth, transmit power, etc., available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0788] TTI can also be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., and can also be a unit of processing such as scheduling and link adaptation. In addition, when a TTI is given, the actual time interval (e.g., the number of symbols) mapped to transmission blocks, code blocks, codewords, etc. can be shorter than the TTI.

[0789] Additionally, where a time slot or a mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can also be the minimum time unit for scheduling. Furthermore, the number of time slots (mini-time slots) constituting the minimum time unit of the schedule can also be controlled.

[0790] A TTI with a duration of 1 ms can 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 can 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 mini time slot, a sub-time slot, a time slot, etc.

[0791] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) can also be rewritten as a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can also be rewritten as a TTI with a duration of less than a long TTI but more than 1 ms.

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

[0793] Furthermore, an RB can contain one or more symbols in the time domain, and can also be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can also be composed of one or more resource blocks.

[0794] In addition, one or more RBs can also be referred to as Physical Resource Blocks (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0795] Furthermore, a resource block can also consist of one or more resource elements (REs). For example, an RE can also be a radio resource area consisting of a subcarrier and a symbol.

[0796] The Bandwidth Part (BWP) (also referred to as partial bandwidth, etc.) can also represent a subset of consecutive common resource blocks (RBs) used for a certain parameter set in a carrier. Here, common RBs can also be determined by the index of RBs based on the common reference point of the carrier. PRBs can also be defined in a BWP and appended with numbers within that BWP.

[0797] A BWP can also include a UL BWP (the BWP used by UL) and a DL BWP (the BWP used by DL). For a UE, one or more BWPs can also be set within a single carrier.

[0798] At least one of the configured BWPs can be active, and the UE may not intend to transmit or receive specific signals / channels outside of the active BWPs. Furthermore, the terms "cell," "carrier," etc., in this disclosure can be rewritten as "BWP."

[0799] Furthermore, the structures described above, such as radio frames, subframes, time slots, mini-time slots, and symbols, are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0800] Furthermore, the information, parameters, etc., described in this disclosure can be represented by absolute values, relative values ​​with respect to a specific value, or other corresponding information. For example, wireless resources can also be indicated by a specific index.

[0801] In this disclosure, the names used for parameters, etc., are not limiting names in any respect. Furthermore, the mathematical expressions, etc., using these parameters may differ from those explicitly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name; therefore, the various names assigned to these various channels and information elements are not limiting names in any respect.

[0802] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be mentioned throughout the above description, can also be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

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

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

[0805] Regarding any information (e.g., variables, constants, parameters) recorded in this disclosure, even if not specifically explicitly stated in the above embodiments, information representing / determining the value of such arbitrary information (or information associated with such arbitrary information) can be notified from any first device (e.g., UE / base station) to any second device (e.g., base station / UE).

[0806] The notification of information is not limited to the methods / implementations described in this disclosure, and may also be carried out by other methods. For example, the notification of information in this disclosure may also be implemented by physical layer signaling (e.g., downlink control information (DCI), uplink control information (UCI), etc.), 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 combinations thereof.

[0807] In addition, physical layer signaling can also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. Furthermore, RRC signaling can also be referred to as RRC messages, such as RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. Additionally, MAC signaling can also be notified using, for example, a MAC Control Element (CE).

[0808] Furthermore, notification of specific information (e.g., a notification of “is X”) is not limited to explicit notification, but can also be implicit (e.g., by not providing that specific information, or by providing other information).

[0809] The determination can be made by a value represented by a single bit (0 or 1), by a true or false value (boolean), or by a numerical comparison (e.g., a comparison with a specific value).

[0810] Whether software is called software, firmware, middleware, microcode, hardware description language, or any other name, it should be broadly interpreted to refer to instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

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

[0812] The terms “system” and “network” as used in this disclosure are interchangeable. “Network” may also mean devices included in a network (e.g., base stations).

[0813] In this disclosure, the terms “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”, “beamwidth”, “beam angle”, “antenna”, “antenna element”, “panel”, “UE panel”, “transmitting entity”, and “receiving entity” are used interchangeably.

[0814] Furthermore, in this disclosure, the antenna port can also be rewritten with an antenna port used for any signal / channel (e.g., a DeModulation Reference Signal (DMRS) port). In this disclosure, resources can also be rewritten with resources used for any signal / channel (e.g., reference signal resources, SRS resources, etc.). Additionally, resources can also include time / frequency / code / spatial / power resources. Moreover, the spatial domain transmission filter can also include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0815] The aforementioned groups may include, for example, at least one of the following: spatial relation group, code division multiplexing (CDM) group, reference signal (RS) group, control resource set (CORESET) group, PUCCH group, antenna port group (e.g., DMRS port group), layer group, resource group, beam group, antenna group, panel group, etc.

[0816] Furthermore, in this disclosure, beam, SRS Resource Indicator (SRI), CORESET, CORESET pool, PDSCH, PUSCH, Codeword (CW), Transport Block (TB), RS, etc., can also be rewritten to each other.

[0817] Furthermore, in this disclosure, the TCI state, downlink TCI state (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, and joint TCI state can also be rewritten to each other.

[0818] Furthermore, in this disclosure, terms such as "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", and "specific QCL type (e.g., type A, type D)" can be rewritten interchangeably.

[0819] In this disclosure, indexes, identifiers (IDs), indicators, indications, resource IDs, etc., can also be interchanged. In this disclosure, sequences, lists, sets, groups, clusters, subsets, etc., can also be interchanged.

[0820] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) can be interchanged. "Spatial relationship information (TCI state)" can also be interchanged with "a set of spatial relationship information (TCI states)," "one or more spatial relationship information," etc. TCI state and TCI can also be interchanged. Spatial relationship information and spatial relationship can also be interchanged.

[0821] In this disclosure, the terms "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. There are also instances where the terms macro cell, small cell, femtocell, and picocell are used to refer to a base station.

[0822] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

[0823] In this disclosure, the information sent by the base station to the terminal can also be rewritten with the control / operation instructed by the base station to the terminal based on that information.

[0824] In this disclosure, the terms “Mobile Station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” are used interchangeably.

[0825] There are also instances where mobile stations are referred to as subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or several other appropriate terms.

[0826] At least one of the base station and the mobile station can also be referred to as a transmitting device, a receiving device, a wireless communication device, etc. Additionally, at least one of the base station and the mobile station can also be a device mounted on a moving object, the moving object itself, etc.

[0827] The term "mobile body" refers to a movable object whose speed is arbitrary, including situations where the body is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, loading shovels, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, trolleys, rickshaws, ships (including vessels and other watercraft), airplanes, rockets, satellites, drones, multi-rotor aircraft, quadcopters, balloons, and objects carried on them, but are not limited to these. Furthermore, the mobile body can also be a mobile body that moves autonomously based on operational commands.

[0828] The mobile entity can be a means of transportation (e.g., a vehicle, an airplane, etc.), a mobile entity moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, 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 also be an Internet of Things (IoT) device such as a sensor.

[0829] Figure 15This figure illustrates an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a gear 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 speed sensor 51, a pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a gear shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0830] The drive unit 41 is comprised of 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 called a handlebar) and to perform directional control on at least one of the front wheel 46 and the rear wheel 47 based on the operation of the steering wheel by the user.

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

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

[0833] The information service unit 59 comprises various devices such as a vehicle navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices. The information service unit 59 uses information obtained from external devices via the communication module 60, etc., to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

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

[0835] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents and reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning devices (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyroscope systems (e.g., Inertial Measurement Unit (IMU)), Inertial Navigation System (INS)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via a communication module 60 and implements driver assistance or autonomous driving functions.

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

[0837] 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, it can transmit and receive various types of information between external devices via wireless communication. The communication module 60 can be located either inside or outside the electronic control unit 49. The external device can be, for example, the aforementioned base station 10, user terminal 20, etc. Furthermore, the communication module 60 can be, for example, at least one of the aforementioned base station 10 and user terminal 20 (or it can function as at least one of the base station 10 and user terminal 20).

[0838] The communication module 60 can also wirelessly transmit at least one of the following to an external device: signals from the various sensors 50-58 described above that are input to the electronic control unit 49, information obtained based on these signals, and information based on input from an external source (user) obtained via the information service unit 59. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc., can also be referred to as input units that receive input. For example, the PUSCH transmitted via the communication module 60 can also contain information based on the aforementioned input.

[0839] The communication module 60 receives various information (traffic information, traffic light information, vehicle-to-vehicle information, etc.) sent from external devices and displays it to the information service unit 59 provided by the vehicle. The information service unit 59 can also be referred to as an output unit that outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH received through the communication module 60 (or data / information decoded from the PDSCH).

[0840] 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, gear shift lever 45, left and right front wheels 46, left and right rear wheels 47, axle 48, and various sensors 50-58 of the vehicle 40 based on the information stored in the memory 62.

[0841] Furthermore, the base station in this disclosure can also be rewritten as a user terminal. For example, various methods / implementations of this disclosure can be applied to structures where communication between the base station and the user terminal is replaced by communication between multiple user terminals (e.g., also referred to as device-to-device (D2D) or vehicle-to-everything (V2X)). In this case, it can also be configured such that the user terminal 20 has the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be rewritten as terms corresponding to inter-terminal communication (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can also be rewritten as sidelink channel.

[0842] Similarly, the user terminal in this disclosure can also be rewritten as a base station. In this case, it can also be configured such that the base station 10 has the functions of the user terminal 20 described above.

[0843] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. Clearly, in a network containing one or more network nodes having a base station, various operations for communication with a terminal can be performed by the base station, one or more network nodes other than the base station (e.g., considering a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc., but not limited to these), or combinations thereof.

[0844] The various methods / implementations described in this disclosure can be used individually or in combination, and can be switched as needed during execution. Furthermore, the processing procedures, timing sequences, flowcharts, etc., of the various methods / implementations described in this disclosure can be rearranged as long as they do not contradict each other. For example, for the method described in this disclosure, the illustrated order is used to indicate various steps, but the order in which they are indicated is not limited.

[0845] The various methods / implementations described in this disclosure can 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), Futuregeneration radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE This includes 802.11 (Wi-Fi, a registered trademark), IEEE 802.16 (WiMAX, a registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, systems utilizing other suitable wireless communication methods, and next-generation systems derived from enhancements, modifications, creations, or specifications based on them. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0846] As used in this disclosure, the term "based on" does not mean "based on only" unless otherwise specified. In other words, the term "based on" means both "based on only" and "based on at least".

[0847] Any reference to an element using the designations "first," "second," etc., as used in this disclosure does not comprehensively limit 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 the first and second elements does not imply that only two elements may be used, or that the first element must take precedence over the second element in some form.

[0848] The term "determining" as used in this disclosure can encompass a wide variety of operations. For example, "determining" can also refer to judging, calculating, computing, processing, deriving, investigating, looking up (search, inquiry) (e.g., searching in a table, database or other data structure), and ascertaining.

[0849] In addition, "judgment (decision)" can also refer to receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, accessing (e.g., accessing data in memory), etc., as situations where "judgment (decision)" is performed.

[0850] Furthermore, "judgment (decision)" can also refer to situations where resolving, selecting, choosing, establishing, or comparing are considered as making a "judgment (decision)". That is, "judgment (decision)" can also refer to certain operations as making a "judgment (decision)". In this disclosure, "judgment (decision)" can also be rewritten in relation to the operations described above.

[0851] Furthermore, in this disclosure, "determine / determining" can also be interchanged with "assume / assuming," "expect / expecting," "consider / considering," etc. Additionally, in this disclosure, "not assuming..." can also be interchanged with "assuming not...".

[0852] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s)..." (where "..." can also be expressed as a that clause, an infinitive to, etc.) can also be interchanged with "be expected..." or "perform..." (in the case of "..." being an infinitive to "to," the verb with "to" removed). "Does not expect..." can also be interchanged with "be not expected..." or "does not perform..." (in the case of "..." being an infinitive to "to," the verb with "to" removed). Furthermore, "An apparatus A is not expected..." can also be interchanged with "Apparatus B other than apparatus A does not expect apparatus A to perform..." (for example, if apparatus A is a UE, apparatus B can also be a base station).

[0853] The term "maximum transmit power" as used in this 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).

[0854] As used in this disclosure, the terms “connected,” “coupled,” or all variations thereof, refer to all direct or indirect connections or combinations between two or more elements, and can include cases where there is one or more intermediate elements between two mutually “connected” or “coupled” elements. The connections or combinations between elements can be physical, logical, or a combination thereof. For example, “connection” can also be rewritten as “access.”

[0855] In this disclosure, when two elements are connected, it is possible to consider using more than one wire, cable, printed electrical connection, etc. to be "connected" or "combined" with each other, and as several non-limiting and non-exclusive examples, to use electromagnetic energy with wavelengths having wireless frequency domain, microwave region, light (both visible and invisible) region to be "connected" or "combined" with each other.

[0856] In this disclosure, the term "A is different from B" can also mean "A and B are different from each other." Additionally, the term can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0857] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," mean inclusive. Furthermore, the term "or" as used in this disclosure does not mean XOR.

[0858] In this disclosure, for example, in cases where articles are added through translation, such as a, an, and the in English, the disclosure may also include cases where the noun following these articles is in a plural form.

[0859] In this disclosure, terms such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, statements meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow" can be interchanged, not limited to the positive, comparative, and superlative degrees. Additionally, in this disclosure, statements meaning "good," "bad," "large," "small," "high," "low," "early," "late," "wide," and "narrow" can also be interchanged as expressions accompanied by "i" (where i is any integer), not limited to the positive, comparative, and superlative degrees (e.g., "highest" can also be interchanged with "i-th highest").

[0860] In this disclosure, "of", "for", "regarding", "related to", "associated with", etc., can also be rewritten interchangeably.

[0861] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "B based on A", "B during / while A", "B before A", "B at (the same time as) / on A", "B after A", "B since A", and "B until A" can be rewritten interchangeably. Furthermore, A and B can be appropriately replaced with nouns, gerunds, or other suitable expressions depending on the context. Additionally, the time difference between A and B can be approximately 0 (immediately following or immediately preceding). Moreover, a time offset can be applied to the time A occurs. For example, "A" can also be rewritten interchangeably with "before / after the time offset of A". This time offset (e.g., more than one symbol / slot) can be predetermined or determined by the UE based on the information it is notified of.

[0862] In this disclosure, timing, moment, time, time instance, arbitrary time unit (e.g., time slot, sub-time slot, symbol, subframe), period, opportunity, resource, etc., can also be overridden.

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

Claims

1. A terminal, comprising: The receiving unit receives settings related to trigger conditions that support a combination of multiple events for event-based beam reporting; and The control unit, based on the aforementioned settings, controls the event-based beamforming. If, in addition to the aforementioned triggering conditions, a condition for the time to trigger (TTT) is also met, the control unit applies a specific operation.

2. The terminal as described in claim 1, wherein, The control unit performs control to cancel the beam report based on the beam report cancellation conditions included in the settings.

3. The terminal as described in claim 1, wherein, After passing through the TTT, the control unit performs at least one of the following: activation of the transmission setting indication state (TCI state), uplink synchronization (UL synchronization), tracking of the tracking reference signal (TRS), and cell or beam switching.

4. The terminal as described in claim 1, wherein, After the TTT, the control unit controls the reception of the positive acknowledgment (ACK) for the event-based beam report.

5. A wireless communication method for a terminal, comprising: Steps for receiving and supporting the setting of trigger conditions related to the combination of multiple events for event-based beam reporting; Based on the aforementioned settings, control the steps of the event-based beam reporting; as well as In addition to the aforementioned triggering conditions, if the conditions for the time to trigger (TTT) are also met, then specific operation steps are applied.

6. A base station, comprising: The transmitting unit transmits settings related to trigger conditions that support combinations of multiple events for event-based beam reporting; and The control unit, based on the aforementioned settings, controls the reception of the event-based beam report, wherein... The event-based beam report is sent from the terminal by applying a specific operation when, in addition to the triggering condition, a condition for the time to trigger (TTT) is also met.

Images