Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives downlink control information (DCI) that triggers an event-based beam report, and a control unit that controls, based on the DCI, reporting of the event-based beam report using uplink control information (UCI), the control unit controlling execution of the event-based beam report in two steps using a first report and a second report, a number of bits of the UCI being fixed.

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 further increasing data rates and reducing latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving the height of 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+ (plus), 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 to use L1L2-triggered mobility (LTM) as specified in Rel.18 when terminals (user terminals, user equipment (UE)) move between cells.

[0009] In mobility scenarios beyond Rel.19, various use cases can be envisioned. For example, in industrial communication systems, examples include remote control of industrial equipment and factory automation. Furthermore, in real-time, two-way (interactive) services, examples include AI / XR-based services.

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

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

[0012] In other words, event-triggered beam reports can be used for measurement reporting / beam switching / cell switching.

[0013] On the other hand, it is envisioned that the type of beam reporting supported will differ depending on each use case.

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

[0015] However, research on regulations related to event-based beam reporting, appropriate for the specific use cases, is insufficient. This lack of research prevents the achievement of lower latency communication, potentially hindering 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 for receiving downlink control information (DCI) that triggers an event-based beam report; and a control unit for controlling, based on the DCI, to report the event-based beam report using uplink control information (UCI), the control unit controlling the execution of the event-based beam report in a two-step manner using a first report and a second report, wherein the number of bits in the UCI is fixed.

[0019] Invention Effects

[0020] According to one method disclosed herein, communication quality / throughput can be improved. Attached Figure Description

[0021] Figure 1A as well as Figure 1B This illustrates an example of a unified / common 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 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 a time series of UE-initiated / event-driven beam reports according to the first embodiment.

[0028] Figure 8 This is a diagram illustrating an example of event-based beam reporting according to the first embodiment.

[0029] Figure 9 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-1.

[0030] Figure 10 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0031] Figure 11 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0032] Figure 12 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0033] Figure 13 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0034] Figure 14 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0035] Figure 15 This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3.

[0036] Figure 16A as well as Figure 16B This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3.

[0037] Figure 17A as well as Figure 17B This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3.

[0038] Figure 18 This is a diagram illustrating an example of the encoding / decoding correspondence between the channel between the UE and gNB.

[0039] Figure 19 This is a diagram illustrating an example of event-based beam reporting according to the fourth embodiment.

[0040] Figure 20 This is a diagram illustrating an example of event-based beam reporting according to the fourth embodiment.

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

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

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

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

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

[0046] (CSI Report)

[0047] 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) Channel State Information (CSI) to the base station.

[0048] 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 the channel state.

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

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

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

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

[0053] 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".

[0054] CSI report configuration information may include information related to reporting period, offset, etc., which can be represented by 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 the type of CSI reporting method (whether it is SP-CSI, etc.), reporting period, and other parameters. CSI report configuration information may also include information indicating which signal (or resource used by which signal) was used for the CSI measurement (CSI-ResourceConfigId).

[0055] (TCI, Spatial Relations, QCL)

[0056] In NR, research is being conducted on 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 control signals and channels (referred to as signal / channel) in the UE based on the Transmission Configuration Indication state (TCI state).

[0057] TCI states can also represent elements of signals / channels applied to the downlink. The equivalent of TCI states applied to signals / channels in the uplink can also be described as spatial relations.

[0058] The so-called TCI status refers to information related to 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 for the UE on a per-channel or per-signal basis.

[0059] QCL is an indicator that represents 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 (QCL): Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

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

[0061] A QCL can also be defined with multiple types (QCL types). For example, four QCL types, or types AD, can be set, where the parameters (or parameter sets) that can be assumed to be the same are different. These parameters (also called QCL parameters) are represented as follows:

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

[0063] • QCL Type B (QCL-B): Doppler shift and Doppler extension,

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

[0065] • QCL Type D (QCL-D): Space reception parameters.

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

[0067] The assumption that a UE envisions a relationship between a Control Resource Set (CORESET), channel, or reference signal and other CORESETs, channels, or reference signals in a specific QCL (e.g., QCL type D) is called a QCL assumption.

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

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

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

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

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

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

[0074] 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 the RS can also be called the QCL source of QCL type X in TCI state.

[0075] (Unified / Common TCI Framework)

[0076] According to the unified TCI framework, multiple types of channels / RS (UL / DL) can be controlled through a common framework. Unlike Rel.15, which specifies TCI states or spatial relationships for each channel, the unified TCI framework can both indicate a common beam (common TCI state) and apply it to all channels of UL and DL, and can also apply the common beam used for UL to all channels of UL, and the common beam used for DL ​​to all channels of DL.

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

[0078] 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 each of UL and DL (separate TCI state, separate TCI pool, UL separate TCI pool and DL separate TCI pool, separate common TCI pool, UL common TCI pool and DL common TCI pool).

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

[0080] The common beam / unified TCI state can also 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 of the X active TCI states. The selected TCI state can also be applied to the channels / RS of both UL and DL.

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

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

[0083] In this disclosure, when N=M=X (X is any integer), it can also mean: notifying / setting / indicating to the UE the common TCI state (joint TCI state) in X ULs and DLs (corresponding to X TRPs). Furthermore, when N=X (X is any integer) and M=Y (Y is any integer, or Y=X), it can also mean: notifying / setting / indicating to the UE X UL TCI states (corresponding to X TRPs) and Y DLTCI states (corresponding to Y TRPs) separately (i.e., independent TCI states).

[0084] For example, when recorded as N=M=1, it can also mean: a TCI state that is common in a UL and DL for a single TRP, which is notified / set / indicated to the UE.

[0085] In addition, for example, when N=1 and M=1 are recorded, it can also mean: separately notifying / setting / indicating to the UE a UL TCI state and a DL TCI state (an independent TCI state for a single TRP).

[0086] In addition, for example, when N=M=2 is recorded, it can also mean: a TCI state common in multiple (2) ULs and DLs for multiple TRPs, which is notified / set / indicated to the UE.

[0087] In addition, for example, when N=2 and M=2 are recorded, it can also mean: notification / setting / instruction for the UE for multiple (2) TRPs, multiple (2) UL TCI states and multiple (2) DL TCI states (independent TCI states for multiple TRPs).

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

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

[0090] Figure 1A as well as Figure 1B This represents an example of the unified TCI framework. Figure 1A An example representing a joint DL / UL TCI state (e.g., Joint DL / UL TCI state). Figure 1B An example representing an independent TCI state (e.g., a separate TCI state (DLTCI state and UL TCI state)).

[0091] 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 by the RRC parameter can also be referred to as the set TCI state or the configured TCI state (e.g., configured TCI states). The MAC CE can also activate multiple TCI states among the set TCI states. The DCI can also indicate one of the activated TCI states. In this disclosure, the TCI state indicated by the DCI can also be referred to as the indicated TCI state or the indicated TCI state (e.g., indicated TCI state).

[0092] A DCI can be either 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.

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

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

[0095] 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 "setting information". Additionally, in this disclosure, the act of using a DCI to indicate one of the multiple TCI states can be either receiving indication information indicating one of the multiple TCI states included in the DCI, or simply receiving "indication information".

[0096] 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 among the set multiple TCI states (activate TCI pool). Separate activation TCI pools for UL and DL can also be set / activated.

[0097] DL DCI or new DCI formats can also select (indicate) more than one (e.g., one) TCI states. The selected TCI state can also be applied to more than one (or all) DL channels / RS. DL channels 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. UL DCI or new DCI formats can also select (indicate) more than one (e.g., one) TCI states. The selected TCI state can also be applied to more than one (or all) UL channels / RS. UL channels can also be PUSCH / SRS / PUCCH. In this way, different DCIs can also separately indicate UL TCI and DL DCI.

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

[0099] Figure 1A The method for setting / indicating the TCI status (e.g., combined DL / UL TCI status), and Figure 1B The application of TCI status (e.g., standalone TCI status) setting / indication method can also be switched. Whether to apply the combined DL / UL TCI status or the standalone TCI status can also be set by the base station to the UE via higher-layer parameters.

[0100] (TCI status indication)

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

[0102] [Mode 1] MAC CE based TCI state indication;

[0103] [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)

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

[0105] For a UE with a TCI state that is set and activated with a Rel.17 TCI state ID (e.g., tci-StateId_r17), for a CC, the UE receives DCI format 1_1 / 1_2 that provides the indicated TCI state along with the Rel.17 TCI state ID; or, for all CCs in the same CC list as those set by simultaneous TCI update list 1 or simultaneous TCI update list 2 (e.g., simultaneousTCI-UpdateList1 or simultaneousTCI-UpdateList2), the UE receives DCI format 1_1 / 1_2 that provides the indicated TCI state along with the Rel.17 TCI state ID. DCI format 1_1 / 1_2 may or may not be accompanied by DL allocation if DL allocation is available.

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

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

[0108] The values ​​for the following DCI fields (special fields) are set as follows:

[0109] - The redundant version (RV) field is all '1's.

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

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

[0112] - 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 PDCCH for release of DL semi-persistent scheduling (SPS) or UL licensed type 2 scheduling).

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

[0114] 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. The investigation is underway to determine whether the TCI field is always present in DCI format 1_1 / 1_2 when the UE is set with the Rel.17 TCI state, and whether the UE ignores the TCI field if it does not support TCI updates via DCI.

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

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

[0117] [Operation] If the higher-layer parameter tci-PresentInDCI is not set to valid for the CORESET used to transmit the DCI format 1_1 PDCCH, 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.

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

[0119] [Operation] If the higher-layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used to transmit the PDCCH of 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 to transmit the PDCCH of DCI format 1_2 for all CORESETs within the indicated BWP.

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

[0121] Figure 2B This example illustrates an independent DL / UL TCI status indication based on DCI. For the TCI field used in the independent DL / UL TCI status indication, the value is associated with at least one of the TCI status IDs representing the TCI status of DL only and the 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 used by DL, TCI field values ​​010 to 011 are associated with only one TCI status ID used by UL, and TCI field values ​​100 to 111 are associated with both one TCI status ID used by DL and one TCI status ID used by UL.

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

[0123] 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 / MACCE / RRC (indicated Rel.17 TCI state).

[0124] In this disclosure, the Rel.17 TCI state, the indicated TCI state, the unified / common TCI state, the TCI state applied to multiple types of signals (channels / RS), and the TCI state applied to multiple types of signals (channels / RS) can also be overwritten with each other.

[0125] The Rel.17 TCI state can also be shared with at least one of the following: the UE-specific receive, dynamic authorization (DCI) / configured authorization 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 via DCI / MAC CE / RRC can also be referred to as the indicated TCI state or the unified TCI state.

[0126] For Rel.17 TCI states, TCI states other than the unified TCI state can also refer to the Rel.17 TCI state configured using (Rel.17) MACCE / RRC (configured Rel.17 TCI state). In this disclosure, the configured Rel.17 TCI state, the configured TCI state, the TCI state other than the unified TCI state, and the TCI state applied to a specific type of signal (channel / RS) can also be interchanged.

[0127] The Rel.17 TCI state can also be set without sharing with at least one of the following: UE-specific receive, Dynamic Accreditation (DCI) / Configured Accreditation (PUSCH) in the PDSCH / PDCCH (which has been updated using Rel.17 DCI / MAC CE / RRC), and multiple (e.g., all) dedicated PUCCH resources. The Rel.17 TCI state can also be set via RRC / MAC CE per CORESET / per resource / per resource set, and the Rel.17 TCI state is not updated even if the aforementioned Rel.17 TCI state (common TCI state) is updated.

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

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

[0130] [PDCCH]

[0131] • If `followUnifiedTCIState` is set for CORESET0, the indicated TCI state is applied. Otherwise, for that CORESET, the Rel.15 specification is applied. That is, CORESET0 follows the TCI state activated via MACCE, or performs QCL with the SSB.

[0132] • For CORESETs with USS / CSS type 3 and index 0 or other, always apply the indicator TCI status.

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

[0134] [PDSCH]

[0135] • Always apply the TCI status indicator to all UE-dedicated PDSCHs.

[0136] • For non-UE-dedicated PDSCHs (PDSCHs scheduled via DCI within CSS), the indicator TCI state can also be applied if `followUnifiedTCIState` (for the CORESET of the PDCCH that schedules the PDSCH) is set. Otherwise, the set TCI state for the PDSCH is applied to that PDSCH. For PDSCHs, whether a non-UE-dedicated PDSCH follows the indicator TCI state when `followUnifiedTCIState` is not set can also be determined based on whether `followUnifiedTCIState` is set for the CORESET used to schedule the PDSCH.

[0137] [CSI-RS]

[0138] • For A-CSI-RS used for CSI acquisition or beam management, if followUnifiedTCIState (for the CORESET of the PDCCH that triggers the A-CSI-RS) is set, apply the indicated TCI state. For other CSI-RS, apply the configured TCI state for that CSI-RS.

[0139] [PUCCH]

[0140] • Always apply the indicator TCI status to all dedicated PUCCH resources.

[0141] [PUSCH]

[0142] • For dynamic / configured license PUSCH, always apply an indication of TCI status.

[0143] [SRS]

[0144] • For A-SRS used for beam management purposes and A / SP / P-SRS used for codebook (CB) / non-codebook (NCB) / antenna switching purposes, the SRS resource set applies an indicator TCI state when it is set to follow a unified TCI state. For other SRS, the TCI state settings within this SRS resource set are applied.

[0145] (TCI state switching)

[0146] In Rel.15 / 16, a delay time is specified for switching the activated TCI state for a UE that has set more than one TCI state in the serving cell.

[0147] 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, the UE needs beam / RS measurement and reporting, and both the UE and NW need to have a shared understanding regarding whether the TCI state is known or unknown.

[0148] In Rel.16, a known TCI state means that the following conditions 0-5 are met:

[0149] (Condition 0): From the last transmission of the RS resource used for the L1-RSRP measurement report for the target TCI state until the completion of the switch to activate the TCI state, the RS resource used for the L1-RSRP measurement is the RS of the target TCI state or the RS that is in a QCL relationship with the target TCI state.

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

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

[0152] (Condition 3): TCI state detection can still be performed during the TCI state transition.

[0153] (Condition 4): During the TCI state transition, the detection of SSBs associated with the TCI state can still be performed.

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

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

[0156] 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".

[0157] In the case of TCI state handover using MAC CE (MAC-CE based TCIstate switch) and the target TCI state (the TCI state of the handover destination) being 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 +3 Nsubframe,μ slot +TO k (T first-SSB +T SSB-procIn the initial time slot following (NR slot length), the UE receives the Physical Downlink Control Channel (PDCCH) of the serving cell where the TCI state handover has occurred, indicating the target TCI state. Furthermore, in time slot n+T... HARQ +3N subframe,μ slot Up to this point, it can receive the PDCCH in the old (pre-switching) TCI state. From time slot n+T HARQ +3N subframe,μ slot From 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 ).

[0158] Here, T HARQ This indicates the timing from the start of downlink data signal transmission (e.g., PDSCH) to the delivery of acknowledgment information (e.g., HARQ-ACK information). N subframe,μ slot This represents the number of time slots in each subframe for which μ is set for a subcarrier. T first-SSB This refers to the time from after the UE decodes the MAC CA command used for TCI state activation until the initial SSB is sent. 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 for PDSCH, and 0 otherwise. NR slot length indicates the length of the slot.

[0159] Figure 4 This is a diagram illustrating an example of the TCI status 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).

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

[0161] Here, for L1-RSRP measurements using CSI-RS, or for switching of TCI states for QCL types other than QCL type D, TO uk The value is 1. On the other hand, for the switching of TCI states that are at least set to QCL type D, and measured using the L1-RSRP of the SSB, TO uk It is 0.

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

[0163] Compared to the case where the target TCI state is a known TCI state, when the target TCI state is an unknown TCI state, an additional T needs to be added to the TCI state transition. L1-RSRP Time. T L1-RSRP This is the time associated with received power measurement. In frequency range (FR) 1, or in FR2 when QCL type D is not set, T... L1-RSRP It is 0. In cases where that is not the case, it is the time required for the determination / refinement of the receive beam in FR2.

[0164] Furthermore, when 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, if for the UE, the higher-layer parameter tci-PresentInDCI of CORESET used for PDSCH scheduling is enabled in time slot n, then in the initial time slot after time slot n + timeDurationForDCI, the PDSCH of the serving cell with the target TCI state of the TCI state switch will be received. Here, timeDurationForDCI is the time required for the reception of PDCCH and the application of spatial relationship / QCL-related information (spatial QCL information) to the reception of DCI for PSDCH.

[0165] Furthermore, if RRC signaling is used during TCI state switching (RRC-based TCI state switch), and the target TCI state is a known TCI state, if the UE receives a PDSCH transmitting an RRC activation command for the TCI state in time slot n, then in time slot n+(T RRC_processing +TO k (T first-SSB +T SSB-proc In the initial time slot following )) / (NR slot length), receive the PDCCH of the target TCI state of the serving cell where the TCI state handover has occurred.

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

[0167] 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 In the initial time slot following )) / (NR slot length), receive the PDCCH of the target TCI state of the serving cell where the TCI state handover has occurred.

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

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

[0170] In Rel.17, the delay time for the handover involved in the unified TCI state is specified.

[0171] For example, this specified delay time can also be applied when the UE is configured with RRC parameters (DLorJoint-TCIState) related to the unified TCI state for use in the DL channel of the serving cell.

[0172] In MR-DC or stand-alone NR, this delay time can also be applied to all lists of multiple serving cells in multiple CC / cell simultaneous TCI update lists (e.g., simultaneousU-TCI-UpdateList1, simultaneousU-TCI-UpdateList2, simultaneousU-TCI-UpdateList3, simultaneousU-TCI-UpdateList4).

[0173] If the target DL TCI state references an appended PCI that is different from the Physical Cell ID (PCI) of the serving cell that has the DL TCI state set, this delay time may also be applied if the following conditions are met:

[0174] • The activation BWP for the serving cell is the same as that for the cell with added PCI.

[0175] • 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.

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

[0177] Furthermore, the cell for which additional PCI is added can also be known if the following conditions are met:

[0178] • 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.

[0179] • The timing offset between the serving cell and the cell adding PCI is within the CP of the corresponding SCS.

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

[0181] The DL TCI state in the unified TCI state can be known if it also satisfies the following conditions:

[0182] • From the last transmission of RS resources for L1-RSRP measurements of the target DL TCI state until the completion of the switch to activate the DL TCI state, the RS resources used for L1-RSRP measurements are RS resources of the target DL TCI state or RS resources that are in a QCL relationship with the target DL TCI state.

[0183] • The DL TCI stateswitch indication (downlink TCI stateswitch command) is received within 1280ms of the last transmission of the RS resource used for beam reporting or measurement.

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

[0185] • Maintain the ability to detect the DL TCI state during the transition period of DL TCI state.

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

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

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

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

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

[0191] In the case of using MAC CE for DL ​​TCI state switching (MAC-CE based downlink TCI state switch), if the target TCI state (the TCI state of the switching destination) is a known TCI state, and 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 In the initial time slot following (NR slotlength), the UE receives the Physical Downlink Control Channel (PDCCH) for the serving cell where the TCI state handover has occurred, representing the target TCI state. Additionally, 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. In time slot n+T HARQ +3N subframe,μ slot To 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.

[0192] Here, T HARQ This indicates the timing from the start of downlink data signal transmission (e.g., PDSCH) to the delivery of acknowledgment information (e.g., HARQ-ACK information). Nsubframe,μ slot This represents the number of time slots in each subframe for which μ is set for a subcarrier. T first-SSB This is the time from when the UE decodes the MAC CE command for TCI state activation until the initial SSB is sent. SSB-proc It takes 2ms. k The value is 1 if the target TCI state is not included in the list of active TCI states for PDSCH, and 0 if it is not. NR slot length indicates the length of the time slot.

[0193] When MAC CE is used during DL TCI state switching and 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 where a TCI state handover has occurred, representing the target TCI state. Additionally, 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.

[0194] Here, for L1-RSRP measurements using CSI-RS or for switching of TCI states set to QCL types other than QCL type D, TO uk The value is 1. On the other hand, for the switching of TCI states that are at least set to QCL type D and measured using L1-RSRP of SSB, TO uk It is 0.

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

[0196] 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 additionally requires T... L1-RSRP Time. TL1-RSRP This is the time associated with the received power measurement. In frequency range (FR) 1, or in FR2 when QCL type D is not set, T... L1-RSRP It is 0. In cases where that is not the case, it is the time required for the determination / refinement of the receive beam in FR2.

[0197] Furthermore, for example, this specified delay time can also be applied when the UE is configured with RRC parameters related to the unified TCI state (DLorJoint-TCIState (unifiedTCI-StateType indicates Joint), or UL-TCIState) for the UL channel / signal of the serving cell.

[0198] In MR-DC or standalone NR, this delay time is also applied to all lists 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.

[0199] For the UL TCI state (or, combined TCI state), the known / unknown information of the cell with the added PCI and the known / unknown information of the UL TCI state are the same as the information obtained by rewriting the "DLTCI state" which is the cell with the added PCI and the known / unknown information of the TCI state with the above DL TCI state as "UL TCI state (or, combined TCI state)".

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

[0201] In the case of using MACCE in the handover of separate UL TCI states / joint TCI states for UL channels / signals (MAC-CE based uplink TCI stateswitch), if the target TCI state (the TCI state at the handover destination) is a known TCI state, and 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 +NM*(T) first-target-PL-RS+4*T target-PL-RS Within (+2ms) / (NR slot length), a UL signal representing the target TCI state can be transmitted. Here, the UL channel / signal can also be PUCCH, PUSCH, or (when beamCorrespondenceWithoutUL-BeamSweeping is set to 1) a semi-persistent / periodic / aperiodic SRS.

[0202] Furthermore, when using MAC CE for switching between independent UL TCI states / joint TCI states for UL channels / signals, and 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, it can be used in time slot n+T. HARQ +3N subframe,μ slot +(T) L1-RSRP +T first-target-PL-RS +4*T target-PL-RS Within (+2ms) / (NR slot length), send the UL signal of the target TCI state.

[0203] Here, T HARQ This indicates the timing from the start of downlink data signal transmission (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 each subcarrier. NR slot length indicates the length of the time slot.

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

[0205] When the target TCI state is unknown, T target-PL-RS This is the time from the L1-RSRP measurement to the transmission of the initial path loss RS. Furthermore, when the target TCI state is known, T... target-PL-RS It is the time from when the UE decodes the MAC CE command until the initial path loss RS is transmitted.

[0206] When PL-RS is 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 as SSB.

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

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

[0209] 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 abbreviated as "different PCI". Non-serving cells, cells with different PCIs, and additional cells can also be rewritten.

[0210] <Scenario 1>

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

[0212] (1) UE receives from the serving cell: the setting of the SSB for beam measurement of the TRP corresponding to a different PCI from the serving cell, and the settings required for using radio resources for data transmission and reception, including resources of different PCIs.

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

[0214] (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.

[0215] (4) The UE uses the dedicated channel on the TRP corresponding to different PCIs for transmission and reception.

[0216] (5) The UE needs to always cover the serving cell, including in the case of multiple TRPs. Similar to previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

[0217] 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 can also have higher-layer parameters associated with the PCI of a non-serving cell set from the serving cell. Scenario 1 can also be applied in Rel. 17, for example.

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

[0219] 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. When the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required.

[0220] <Scenario 2>

[0221] 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. Since periods of data communication disruption occur due to the need for RRC reconnection for handover, data communication can continue even during serving cell changes by applying L1 / L2 inter-cell mobility that does not require handover. Scenario 2 can also be applied, for example, in Rel. 18. In Scenario 2, for example, the following process is performed.

[0222] (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.

[0223] (2) The UE performs beam measurements on cells with different PCIs and reports the measurement results to the serving cell.

[0224] (3) The UE can also receive settings of cells with different PCIs (serving cell settings) through higher layer signaling (e.g., RRC). That is, prior settings related to serving cell change can also be performed. This setting can be performed together with the setting in (1) or separately.

[0225] (4) Based on the above report, the TCI states of cells with different PCIs can also be activated through L1 / L2 signaling according to the change of the serving cell. The activation of the TCI state and the change of the serving cell can also be performed separately.

[0226] (5) The UE changes the serving cell (the assumption of the serving cell) and starts receiving / sending using the UE-specific channels and TCI states that are pre-set.

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

[0228] Figure 5B It is a diagram showing an example of the movement of the UE in Rel.18. In Rel.18, the serving cell is switched through L1 / L2 (e.g., DCI / MAC CE). The UE can receive / send UE-specific channels / common channels between the UE and the new serving cell (or, the target serving cell). The UE can also move out of the coverage area of the current serving cell (e.g., the current serving cell).

[0229] (Type of beam report)

[0230] <Intra-cell beam report in Rel.15 / 16>

[0231] In Rel.15 / 16, intra-cell beam report is supported. For example, L1-RSRP / SINR reports can be set by higher layer signaling (RRC).

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

[0233] In addition, the UE can be set with a maximum of 16 CSI-RS resource sets with a maximum of 64 resources in each set. The total number of different CSI-RS resources in all resource sets is 128 or less.

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

[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 in steps of 2 dB, referencing the largest measurement that is part of the same L1-RSRP reporting instance.

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

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

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

[0240] 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 will use the L1-SINR value based on the differential value for reporting.

[0241] The difference value is calculated in 1 dB steps, referencing the largest measurement that is part of the same L1-SINR reporting instance.

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

[0243] <Inter-cell beam reporting in Rel.17>

[0244] As described above, in Rel.17, L1 / L2 inter-cell mobility is supported. For example, the UE can transmit and receive UL / DL channels / signals between the PCIs of cells different from the PCI of the serving cell. For example, when the RSRP of a non-serving cell is greater than that of the serving cell, the UE can transmit and receive UL / DL channels / signals between non-serving cells without performing a handover.

[0245] Similar to Rel.15 / 16, the absolute value / difference value of L1-RSRP can be utilized in the L1-RSRP report. In the inter-cell beam reporting in Rel.17 (beam reporting of type 2-1 described later), each L1-RSRP value is associated with a PCI ID (for the serving cell / additional cells / candidate cells). The association between the L1-RSRP value and the PCI ID can be set / indicated by higher layer signaling / physical layer signaling.

[0246] The setting based on higher layer signaling supports a maximum of 7 additional cells. Additionally, ID = 0 means the PCI of the serving cell.

[0247] In this disclosure, the inter-cell beam reporting (in Rel.17 / 18) can also be referred to as beam reporting of type 2 (beam reporting type 2). The beam reporting of type 2 can be further divided into type 2-1 and type 2-2 described later.

[0248] [[ID=E15]]In this disclosure, the beam reporting in Rel.17 can also be referred to as beam reporting of type 2-1 or beam reporting for inter-cell beam switching.

[0249] <Inter-cell beam reporting in Rel.18>

[0250] Furthermore, the beam reporting in Rel.18 only supports L1-RSRP reporting (beam reporting) based on SSB. Here, the number of candidate cells L can be any one of 1 to 4, and the number of beams M for each cell can be any one of 1 to 4. For example, in the beam reporting, 7 bits of the absolute value (the maximum L1-RSRP value in the whole cell) are reported for one cell, and the remaining all L1-RSRP values are reported as difference values.

[0251] ]Regarding the beam selection in the L1-RSRP reporting based on SSB, for the above M and L, the maximum value of M*L that can be set by RRC and the combination of M and L can depend on the UE capability.

[0252] Similar to Rel.15 / 16 / 17, the absolute value / difference value of L1-RSRP can be utilized in the L1-RSRP report.

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

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

[0255] The difference value is calculated in 2 dB steps, referencing the largest measurement that is part of the same L1-RSRP reporting instance.

[0256] 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 be the same as existing specifications.

[0257] 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 for cell handover. Furthermore, the type 2-2 beam report does not contain PCI-related information (PCI ID). Instead, the SSBRI may contain PCI-related information. For example, in the case of 4 cells with 64 SSBs, the SSBRI becomes any one of {0, 1, ..., 255}.

[0258] (Event-based beam reporting)

[0259] 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 it can refer to beam reporting initiated by the UE.

[0260] The events defined in the existing 5G NR can be exemplified as follows. Furthermore, events are not limited to those shown below; other new events can also be defined.

[0261] Event A1: The measurement results of the serving [cell] are better than the threshold.

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

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

[0264] Event A4: The measurement result of a neighboring [cell] (the value obtained by adding an offset to the measurement result) is better than the threshold.

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

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

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

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

[0269] <Applicable Scenarios>

[0270] Event-based beam reporting can also be applied in at least one of the following scenarios:

[0271] • [Scenario 1]: L1-RSRP / SINR beam reports containing serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam reports containing serving cell / additional PCI cells for Rel.18 L1 / L2 mobility accompanying L1 / L2 inter-cell mobility / inter-cell multi-TRP (M-TRP inter-cell) / cell handover).

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

[0273] In the event of a specific event (which may also be rewritten in this disclosure as meeting / not meeting specific conditions), the UE may also report measurement results (e.g., L1-RSRP / L1-SINR) of the NW (e.g., base station).

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

[0275] Regarding the incident in scenario 1

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

[0277] [Option 1]

[0278] 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 reports (e.g., aperiodic CSI reports). That is, if at least one of events A2 to A6 and I1 occurs (subject to the conditions of the event), both RRM reports and CSI reports are triggered, and the UE can also send both RRM reports and CSI reports.

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

[0280] Figure 6 This 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 at specific intervals.

[0281] In this disclosure, the triggering of non-periodic CSI reports and the transmission of non-periodic CSI reports by the UE can be mutually overridden. CSI reports, L1 beam reports, and beam reports can also be mutually overridden.

[0282] 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 at least one of a special cell, 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 / subtracted from the measurement result. The thresholds can be the same or different. Neighboring cells can also be non-serving cells.

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

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

[0285] Event A4: The measurement result of the neighboring cell (the value obtained by adding an offset to the measurement result) is better than the threshold.

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

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

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

[0289] Option 1 allows the RRM report trigger to be reused in the beam report trigger, making setup easy.

[0290] [Option 2]

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

[0292] [[Option 2-1]]

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

[0294] [[Option 2-2]]

[0295] Events can also occur based on measurements of the reference signal received power (L1-RSRP) in Layer 1. That is, comparisons can be made based on L1-RSRP instead of L3-RSRP. Alternatively, a newly filtered L1-RSRP with a time scale (update / measurement period) between L1-RSRP and L3-RSRP (or the same as L1-RSRP or L3-RSRP) can be applied. Other metrics, such as L1-SINR, L3-RSRQ, etc., can also be applied. For example, event A2' can be applied as a new event:

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

[0297] [[Options 2-3]]

[0298] It can also be based on a comparison of measurements at a beam level, multiple beam levels (integrating 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:

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

[0300] 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 a threshold. X can be fixed or set by higher-layer signaling, etc.

[0301] [[Options 2-4]]

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

[0303] Alternatively, examples combining 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:

[0304] Event A4''': L1-RSRP measurement from a beam in a neighboring cell is better than the threshold.

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

[0306] Option 2 enables faster CSI reporting compared to existing RRM reporting using RRC.

[0307] [Option 3]

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

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

[0310] You can also combine two or more events from option 2. For example, a CSI report can be triggered if both event A2' and the new event A4''' are satisfied.

[0311] Regarding the incident in scenario 2

[0312] An example of an event in scenario 2 above will be described. This event could 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.

[0313] You can also define one or more new (independent) events (different 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.

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

[0315] Event B3: The measurement results of other beams (the values ​​obtained by adding an offset to the measurement results) are better than the measurement results of the current beam (the values ​​obtained by adding an offset to the measurement results).

[0316] Event B4: Measurements of other beams (values ​​obtained by adding an offset to these measurements) are better than the threshold.

[0317] Event B5: The measurement result of the current beam is worse than the first threshold, while the measurement results of other beams (the value obtained by adding an offset to the measurement result) are better than the second threshold.

[0318] Event B6: The measurement result of the current beam (the value obtained by adding an offset to the measurement result) is worse than the threshold, while the measurement results of other beams (the values ​​obtained by adding an offset to the measurement result) are better than the measurement result of the current beam (the values ​​obtained by adding an offset to the measurement result).

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

[0320] 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 relating to case 2 and the name of the event relating to the corresponding case 1 (number) may also be the same.

[0321] Furthermore, for at least one of the events in this disclosure (the events involved in Situation 1 / Situation 2), a duration / counter may also be specified for the event (condition) to be satisfied. The UE / NW may also determine that the conditions for each event are satisfied if at least one of the conditions for each of the above events satisfies a condition related to a specific duration / counter. For example, within a 100ms time window, if the measurement results of other beams are better than the measurement results of the current beam, the UE may also determine that the condition for event B3 above is satisfied. Moreover, for example, if, for every plurality of samples, the measurement results of other beams are better than the measurement results of the current beam 10 times, the UE may also determine that the condition for event B3 above is satisfied.

[0322] In this disclosure, the term "current beam" may also refer, for example, to an SSB / CSI-RS that has a QCL relationship with the PDCCH (QCLed).

[0323] The PDCCH can also be, for example, a 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.

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

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

[0326] Furthermore, in this disclosure, the term "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.

[0327] In this disclosure, "other beams" may, for example, be beams / SSB / CSI-RS / TCI states other than the "current beam".

[0328] For the UE, multiple sets of beams (candidate beam sets) can also be set. The UE can also select / determine "other beams" from this set.

[0329] In this disclosure, “(worse) worse / better” may also mean, for example, a (worse) lower / higher measurement result (e.g., RSRP / SINR / RSRQ).

[0330] 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 by a combination of these. For example, the threshold can also reuse an existing threshold (e.g., the threshold used in RRM / Scenario 1).

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

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

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

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

[0335] The cell handover command sent by the MAC CE may contain at least the following information.

[0336] • Information used to identify target cells

[0337] • Information related to advance timing (TA)

[0338] • A joint TCI status index for the target cell or a set of DL / UL TCI status indices for the target cell.

[0339] • Activated DL / UL BWP for the target cell.

[0340] The presence of beam indication within a cell handover command can support the following at least in a certain scenario.

[0341] • 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.

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

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

[0344] Event-triggered [L1] beam reports can 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.

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

[0346] • UE Feature #2: Rel.19 Mobility-Triggered [L1] Beam Reporting.

[0347] Between UE features #1 and #2, different UE capabilities can be imported / defined. Furthermore, different higher-level parameters can be set to activate each UE feature. UE features and UE capabilities can be mutually modified.

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

[0349] Alternatively, UE features #1 and #2 can be set simultaneously within a specific BWP / CC / band / frequency band / frequency (or per UE). For example, when set, the priority of which event (which UE feature) the UE prioritizes can be predefined or set / indicated via higher-layer signaling / physical layer signaling.

[0350] This disclosure can be applied to the Unified TCI framework (Rel. 15 / 16 / 17 / 18).

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

[0352] <Beaming Report for MIMO>

[0353] The following can be applied to the event-triggered beam report for MIMO in Rel.19.

[0354] · MAC CE in PUSCH.

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

[0356] • The relationship between the MAC CE-based method and the UCI-based method described above. For example, two independent methods can be set up. Alternatively, in addition to MAC CE, a UCI-based method can also be applied (or a combination of the two methods can be applied (a two-step method)).

[0357] 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:

[0358] • SSBRI / CRI.

[0359] • Number of beams reported X.

[0360] • Method for selecting X beams.

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

[0362] When MAC CE is used

[0363] • An indicator indicating whether the next octet is included.

[0364] When MAC CE is used, or when UCI is used,

[0365] • Serving Cell ID, BWP ID (in cases where TCI status activation or beam switching is requested through this report).

[0366] <Beaming Report for Mobility>

[0367] Regarding Rel.19's event-triggered beam reporting for mobility, it needs to be clarified whether event-triggered beam reporting is used for cell handover reporting. For example, the following can be applied.

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

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

[0370] The report may contain at least one of the following:

[0371] When a measurement report is used in a cell handover report, in addition to including MIMO-related information,

[0372] • Indicates whether there is a cell handover indicator or TA-related information.

[0373] In cases where that is not the case (where the measurement report is not used for cell handover reporting),...

[0374] • Content identical to MIMO-related information (or differing only in which cell / inter-cell it is).

[0375] Supported events can be the same as conditional hand-over (CHO).

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

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

[0378] You can also specify whether the trigger time needs to be flexible (e.g., 5 milliseconds, 10 milliseconds, 20 milliseconds).

[0379] <Definitions of terms for specific events>

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

[0381] For example, the serving [cell], SpCell, and PCell in existing L3 events can also be rewritten with the current beam (e.g., the RS ID associated with the [joint / DL] TCI state) in the MIMO event-triggered beam report in Rel.19.

[0382] Furthermore, the serving cell, SpCell, and PCell in existing L3 events can also be overwritten in the event-triggered beam report for mobility in Rel.19 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 for the serving cell's PCI).

[0383] Neighboring [cells] in existing L3 events can also be rewritten in the Rel.19 event-triggered beam report for MIMO (or mobility) 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).

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

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

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

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

[0388] <Method 1>

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

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

[0391] The specific DCI can be either a new DCI format (specified after Rel.19) or an existing DCI format that has been scrambled by CRC through a new RNTI (specified after Rel.19).

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

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

[0394] For example, if the UE receives a DCI in DCI format scrambled with a new RNTI before the timer expires, the UE can also determine that the DCI is an ACK for event-based beam reporting. If not, the UE can also determine that the event-based beam reporting failed (received a NACK).

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

[0396] <Method 2>

[0397] 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 / MAC CE).

[0398] 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), may also be utilized / reused for ACK / NACK in UCI-based event-based beamforming.

[0399] Existing DCI formats can also be, for example, DCI formats in which CRC is scrambled by existing RNTI (e.g., C- / TC- / CS- / SP-CSI- / MCS-C-RNTI).

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

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

[0402] In existing specifications, the DFI flag has only one bit in the unlicensed band / shared spectrum. Therefore, in Rel.19 and later, when event-based beamforming is configured, this one-bit field can be specified and reused for ACK / NACK in event-based beamforming.

[0403] The UE may also disregard both the CGDFI for unlicensed bands / shared spectrum specified in Rel.16 and the CG DFI for event-based beam reporting.

[0404] Furthermore, when both the CG DFI for unlicensed bands / 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 instruction.

[0405] For example, for HARQ process IDs that are not related to event-based beam reporting (as specified in Rel.19), the UE can also perform operations related to CG DFI for unlicensed bands / shared spectrum as specified in Rel.16.

[0406] In this scenario, if the UE receives an ACK, the UE can also terminate the repeated transmission of transport blocks associated with that HARQ process ID. Otherwise, the UE can continue the repeated transmission of transport blocks associated with that HARQ process ID.

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

[0408] In this scenario, if the UE receives an ACK, the UE can determine that it should switch the beam / TCI state applied to a specific DL reception / UL transmission. If not, the UE can determine that it should not switch the beam / TCI state applied to a specific DL reception / UL transmission.

[0409] Additionally, the pre-set UL resources can continue to be used for beam reporting only if the UE receives a NACK, or if the UE receives both an ACK and a NACK.

[0410] Furthermore, when both the CG DFI for unlicensed bands / shared spectrum as specified in Rel.16 and the CG DFI for event-based beam reporting are set simultaneously, an additional bit may be added to the DCI for the DFI used for event-based beam reporting.

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

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

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

[0414] For example, if the ACK / NACK field included in the DCI for event-based beamforming is represented by 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 is represented by a second value (e.g., 1 (or 2)), the UE can also determine that a NACK has been received.

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

[0416] <Method 3>

[0417] 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 / MAC CE).

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

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

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

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

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

[0423] <Method 4>

[0424] 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 / MAC CE).

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

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

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

[0428] The UE can also determine that any indication related to any TCI state is a response from NW (ACK / NACK related to event-based beam reporting). In this case, the UE can also determine that it will not send event-based beam reporting during the period from receiving the indication until a specific period has elapsed.

[0429] 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). For example, if the indication related to that specific TCI state is associated with an event-based beamforming, the UE can also determine that the event-based beamforming has been successfully received in the NW. In this case, the UE can also determine that it will not transmit event-based beamforming during the period from receiving the indication until a specific period has elapsed.

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

[0431] The ACK / NACK methods 1-4 described above can also be referred to as gNB (from gNB) ACK / NACK. In particular, gNB ACK can be used to trigger beam reporting as described later.

[0432] (Priorities related to CSI reports)

[0433] In Rel.15 / 16 NR, CSI reports (also known as CSI feedback, CSI reports, etc.) can also be associated with a priority value. For example, this priority value can also be obtained using the function Pri. iCSI It is defined by (y, k, c, s). This priority can also be interchanged with CSI report priority, CSI priority, etc.

[0434] For example, Pri iCSI (y, k, c, s) can also be obtained from the following equation (1).

[0435] (Formula 1) Pri iCSI (y, k, c, s) = 2·N cells ·M s ·y+N cells ·M s ·k+M s ·c+s

[0436] Here, y can also be based on the type of CSI report (whether it is an A-CSI report, an SP-CSI report, or a P-CSI report) and the channel through which the CSI report is sent (uplink shared channel (Physical Uplink Shared Channel (PUSCH))) or uplink control channel (Physical Uplink Control Channel (PUCCH))).

[0437] For example, if it is an A-CSI report transmitted in PUSCH, then y=0; if it is an SP-CSI report transmitted in PUSCH, then y=1; if it is an SP-CSI report transmitted in PUCCH, then y=2; and if it is a P-CSI report transmitted in PUCCH, then y=3.

[0438] k can also be based on whether the CSI report contains the L1-RSRP / SINR value (e.g., k=0 if the CSI report contains L1-RSRP / SINR, and k=1 if it does not). c can also be the serving cell index. s can also be the report configuration ID (reportConfigID). Furthermore, L1-RSRP / L1-SINR can be assigned to different CSI reports.

[0439] In addition, N cells It can also be the maximum number of serving cells set (higher-layer parameter maxNrofServingCells), M s It can also be the maximum number of CSI reports set (high-level parameter maxNrofCSI-ReportConfigurations).

[0440] In Pri, which is associated with the first CSI report iCSI The value of (y, k, c, s) is less than the Pri associated with the second CSI report. iCSI In the case of values ​​(y, k, c, s), it can also mean that the first CSI report has a higher priority than the second CSI report.

[0441] According to Equation 1, for the same number of reports in the same serving cell, priority is given in the following order: A-CSI on PUSCH > SP-CSI on PUSCH > SP-CSI on PUCCH > P-CSI on PUCCH.

[0442] If the time occupancy of two physical channels scheduled to transmit two CSI reports overlaps in at least one OFDM symbol and is transmitted on the same carrier, it can also be referred to as a collision between the two CSI reports.

[0443] Furthermore, in Rel.15 / 16 NR, when a UE is configured to send two conflicting CSI reports of different types (in other words, the values ​​of y in these CSI reports are different), it is not necessary to send a report with a higher Pri value, except in cases where both CSI reports are CSI on PUCCH. iCSI CSI reports for (y, k, c, s) are sent, while those with lower Pri are sent. iCSI CSI report for (y, k, c, s).

[0444] In Rel.15 / 16 NR, when a UE is configured to send two conflicting CSI reports of the same type, or when the CSI reports are different but both are CSI on PUCCH, the CSI reports from both parties can be reused, or, based on Pri... iCSI (y, k, c, s) and drop the CSI report of the party that is discarded.

[0445] (analyze)

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

[0447] In other words, event-triggered beam reports can be used for measurement reporting / beam switching / cell switching.

[0448] Furthermore, it is envisioned that the type of beam reporting supported for each of the above use cases will differ.

[0449] For example, in Rel.19's event-triggered beam reporting for MIMO, type 1 / type 2-1 beam reporting is supported. In Rel.19's event-triggered beam reporting for mobility, type 2-2 beam reporting is supported.

[0450] Furthermore, regarding these beam reports, it is necessary to investigate which container (e.g., MAC CE or UCI) should be used to perform the transmission. Even if either MAC CE or UCI is used, the various specifications accompanying them need to be clearly defined for the purpose of beam reporting.

[0451] As such, research on regulations related to event-based beamforming reporting, tailored to the specific use cases, is insufficient. This lack of research prevents the achievement of lower latency communication, potentially hindering improvements in communication quality / throughput.

[0452] Based on these, the inventors of this invention conceived of a new method for event-triggered beam reporting.

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

[0454] (Various rewrites)

[0455] In this disclosure, terms enclosed in parentheses "()" can also indicate explanations of the preceding term (e.g., spelling notes), rewrites, specific examples, supplementary explanations, etc. Furthermore, in this disclosure, terms enclosed in square brackets "[]" can be interpreted either by including them (or ignoring) them. Additionally, "()" and "[]" can also be used for purposes / meanings other than those listed above.

[0456] 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".

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

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

[0459] In this disclosure, higher-layer signaling may also be any one or a combination of the following: Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, other messages (e.g., positioning protocol messages (e.g., NR Positioning Protocol A (NRPPa) / LTE Positioning Protocol (LPP) messages, etc. from the core network)).

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

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

[0462] In this disclosure, the terms drop, stop, cancel, puncture, rate match, postpone, and do not send can be interchanged.

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

[0464] 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). Channel (PUCCH) groups, PUCCH resource groups, resources (e.g., reference signal resources, SRS resources), resource sets (e.g., reference signal resource sets), CORESET pools, downlink transmission configuration indication states (TCI states) (DL TCI states), uplink TCI states (UL TCI states), unified TCI states, common TCI states, quasi-co-location (QCL) and QCL concepts can also be rewritten.

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

[0466] 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 interchanged as 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.

[0467] In this disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within CC, and frequency band can also 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.

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

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

[0470] In this disclosure, type 1 beam reports and beam reports for intra-cell beam switching can be rewritten to each other.

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

[0472] In this disclosure, the type 2-1 beam report and the beam report for inter-cell beam switching can be rewritten to each other.

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

[0474] In this disclosure, tables, mappings, and associations can be overridden.

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

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

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

[0478] In this disclosure, CSI reports and reports can be rewritten from one another.

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

[0480] In this disclosure, the number of beams and the number of resources can be interchanged.

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

[0482] (Wireless communication method)

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

[0484] • First implementation: A container for beam reporting.

[0485] • Second implementation method: Reserved PUSCH / PUCCH resources for UCI.

[0486] • Third implementation method: extension of CSI priority.

[0487] • Fourth implementation method: A method for avoiding blind detection of UCI bits performed by gNB.

[0488] The following describes each implementation method based on this information.

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

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

[0491] <First Implementation Method>

[0492] The first embodiment relates to a container used for beam reporting.

[0493] As mentioned above, UE-initiated beamreporting is triggered when a specific event set by the NW is met. This is because, without an event set by the NW, the NW cannot identify the reason for sending the beamreport (the purpose of the beamreport is unclear).

[0494] For example, events A3 / A5 can use existing parameters (thresholds, offsets, etc.), but these parameters need to be further extended in order to achieve high-speed beam reporting.

[0495] Figure 7 This is a diagram illustrating an example of a time series of UE-initiated / event-driven beam reports according to the first embodiment. UE-initiated beam reports, event-driven beam reports, and event-based beam reports can be rewritten from one another.

[0496] Figure 7 The upper part is an example of event-based beam reporting. The UE performs an event evaluation set by the NW based on the beam reporting trigger conditions. Then, the UE starts beam reporting when specific conditions are met.

[0497] Specifically, the UE can send a scheduling request (SR) and a DCI (including UL license) regarding UL authorization. Afterward, the UE can send a beam report.

[0498] Figure 7 The lower part is an example of non-event-based (not UE-initiated) beam reporting. The UE can trigger and execute beam reporting based on the terminal implementation (at a terminal-specific timing).

[0499] Specifically, the UE can send a scheduling request (SR) and a DCI (including UL license) regarding UL authorization. Afterward, the UE can send a beam report.

[0500] In non-event-based beam reporting, beam reporting may be triggered at terminal-specific timings. In this case, the NW (gNB) may frequently report that the UE has started beam reporting. As a result, UL resources are wasted, and there are concerns about the impact on UE control.

[0501] In addition, the following is being studied regarding event-based beam reporting.

[0502] (Report Content)

[0503] The following content can be used as report content.

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

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

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

[0507] Furthermore, whether to include the serving beam (the current beam) in the report is configurable. This is because it facilitates comparison of the current beam and adjacent beams on the NW side.

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

[0509] More specifically, when configured / instructed to include serving or non-serving beams in the report, the UE can 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 configured / instructed not to report non-serving beams), the UE can perform beam reporting using UCI (e.g., in the case of MIMO).

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

[0511] Alternatively, the UE can also specify via higher layers whether the handover should utilize beam reporting with MAC CE (e.g., in mobility scenarios) or with UCI. Higher-layer parameters for beam reporting with MAC CE can be associated with mobility / cell handover. Higher-layer parameters for beam reporting with UCI can be unrelated to mobility / cell handover.

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

[0513] (Container for the report)

[0514] As a container for beam reports, MAC CE or UCI can be used. That is, the UE can use MAC CE or UCI to execute / control the transmission of the aforementioned beam reports. Hereinafter, specific examples will be described with reference to methods 1-1 to 1-2.

[0515] <<Method 1-1>>

[0516] Method 1-1 involves beam reporting using MAC CE.

[0517] Beam reporting utilizing MAC CE can be applied to mobility scenarios (e.g., L1 beam reporting of type 2-2). It is not limited to this; the beam reporting can be applied to any scenario (e.g., MIMO).

[0518] The method for requesting UL authorization for this MAC CE can be at least one of the following.

[0519] (Alt1)

[0520] Utilize existing SR (PUCCH-SR resources).

[0521] (Alt2)

[0522] A dedicated SR (PUCCH-SR resource) is set up for event-based beam reporting.

[0523] A dedicated SR can be used to request UL permission for that MAC CE when resources for a UL shared channel (such as PUSCH) cannot be adequately secured.

[0524] According to MAC CE, more information can be transmitted (included) based on the number of beams without prior resource assurance. Therefore, MAC CE is more useful when the reported number of beams is variable.

[0525] In addition, according to the MAC CE, the impact on the existing specifications can be reduced.

[0526] <<Method 1-2>>

[0527] Method 1-2 involves beam reporting that utilizes UCI.

[0528] The beam reporting that utilizes UCI can be applied, for example, to scenarios of MIMO (such as L1 beam reporting of Type 1 / 2-2, etc.). Without limitation, this beam reporting can be applied to any scenario (such as mobility).

[0529] When using this UCI for beam reporting, it is preferable to apply the existing CSI measurement / reporting settings as much as possible. Therefore, for the beam reporting that utilizes UCI, at least one of the following can be applied.

[0530] (Alt1)

[0531] The UL resources for transmitting (carrying) the beam report can be dynamically scheduled by DCI. For example, the UE can send dedicated signaling (such as signaling like SR) to the NW for declaring an event. Then, the existing aperiodic / semi-persistent beam reports can be triggered / activated by DCI.

[0532] (Alt2)

[0533] The UL resources for transmitting (carrying) the beam report can be pre-set by [dedicated] higher-layer signaling. For example, the settings regarding the configured grant PUSCH or the settings regarding a dedicated PUSCH similar to MsgA-PUSCH (which can also be provided to the UE) can be utilized.

[0534] In addition, the ACK of the PUSCH in Alt2 can also have a switched NDI field value in the last symbol of the PDCCH reception, and this PDCCH reception includes the DCI format that schedules the PUSCH transmission with the same HARQ process number as the initial PUSCH transmission. The transmission of the ACK for this PUSCH can also start after the last symbol of the MAC CE based on the PUSCH (for example, refer to Figure 8 ).

[0535] <<Comparison between UCI and MAC CE>>

[0536] Refer to Figure 8 for an example of comparing the beam report based on UCI with the beam report based on MAC CE. Figure 8 is a diagram showing an example of the event-based beam report that utilizes UCI / MAC CE according to the first embodiment.

[0537] As Figure 8 shown, according to UCI, after a specific event occurs, the UE can perform reporting with relatively small latency. That is, according to UCI, the reporting latency can be reduced. In this case, it is envisioned that the impact on the specification becomes larger. In addition, more UL (PUCCH / PUSCH) resources need to be ensured.

[0538] On the other hand, in the case of MAC CE, after a specific event occurs, the UE needs to perform reception of DCI for UL grant, transmission of MAC CE based on PUSCH, reception of ACK for that PUSCH, etc. Therefore, a larger latency may occur until the execution (completion) of the reporting. According to MAC CE, in addition to being able to send more information, the impact on the existing specification can also be reduced.

[0539] According to this embodiment, the UE can appropriately control beam reporting using MAC CE / UCI.

[0540] <<Further research items in the application of UCI>>

[0541] As described above, in the case of using UCI, since the impact on the specification becomes larger, the following research items are envisioned, for example.

[0542] 1: Whether to introduce a new type of UCI or use an existing UCI. [[ID=2L]]

[0543] 2: Rules for CSI priority.

[0544] For example, in the existing specification, it is stipulated that: when a certain UCI is multiplexed with other UCIs on PUSCH / PUCCH, the UCI with a lower priority is discarded.

[0545] 3: Support either PUSCH or PUCCH, or support both. [[ID=JO]]

[0546] In the case of PUSCH, support either configured grant (CG) PUSCH / dynamic grant (DG) PUSCH, or support both.

[0547] In the case of PUCCH, support which one of periodic / aperiodic / semi-persistent PUCCH.

[0548] 4: The number of beam reports (whether the beam report is one time or sent in more than two times).

[0549] 5: Method for reducing PUSCH / PUCCH resources.

[0550] It should be noted that there seems to be a typo in the original text where "2L" is likely a misspelling and should be "21". This has been corrected in the translation for better readability.6: How to avoid blind detection based on gNB-based UCI size when supporting variable beam number.

[0551] The details of these contents will be explained in the second to fourth embodiments described later.

[0552] <Second Implementation Method>

[0553] The second implementation involves reserved PUSCH / PUCCH resources for UCI.

[0554] In this disclosure, “reserved” resources refer to resources scheduled (utilized / allocated) for a specific UE (dedicated to a specific UE), and may not include resources for other UEs. That is, reservation may mean resources that are not scheduled (utilized / allocated) for other UEs.

[0555] In this disclosure, the terms "reserved", "scheduled", "set / instructed", "utilized" / "allocated" can be overridden.

[0556] In this disclosure, the resource used for event-based beam reporting (UL resource) may refer to either the PUSCH / PUCCH resource or the SR resource.

[0557] In this disclosure, resources, first resources, second resources, PUSCH / PUCCH resources, SR resources, reporting resources, etc., can be interchanged.

[0558] When the UE is configured to perform event-based (UE-initiated) beam reporting, the UE may be configured to perform at least one of the following.

[0559] • PUCCH-SR (Dedicated PUCCH-oriented SR for event-based beam reporting).

[0560] Only one SR resource can be configured. Alternatively, multiple SR resources can be configured. In the latter case, the UE can select one SR resource from multiple SR resources based on reporting information (such as SR resource #X, SSBRI / CRI#X, etc.). For example, each SR resource is associated with the reported beam number (#X). The NW can identify the beam number and payload size of the next beam report based on the selected SR resource.

[0561] • PUCCH resources (in addition to the SR resources mentioned above).

[0562] The PUCCH resource can be reserved periodically or semi-persistently. The PUCCH resource can be less than two bits (in the case of PUCCH format (PF) 0 / 1) or more than two bits (in the case of PF2 / 3 / 4).

[0563] • PUSCH Resources (UL Licensed).

[0564] The PUSCH that becomes an object can be either a set license (CG) or a dynamic license (DG). The PUSCH resource can be reserved periodically or semi-persistently.

[0565] <<Method 2-1>>

[0566] This method involves one-step reporting of event-based beam reporting in PUCCH / PUSCH. Figure 9 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-1.

[0567] The UE may be configured with a first reporting resource (also referred to as the first resource) for notifying beam reports. The first resource may or may not contain information related to the number of beams of the reporting object (e.g., the value of the beam number X).

[0568] (Alt1)

[0569] The value of X can be set / indicated either through higher-layer signaling / physical layer signaling or predefined by specifications. This allows for the sharing of the reported payload size between the UE and gNB (with a common understanding).

[0570] (Alt2)

[0571] The value of X can also be determined based on the UE implementation. In this case, CSI Part 1 / 2 needs to be extended for UCI. For example, the number of beams can also be reported through Part 1, and the beam index / measurement can also be reported through Part 2. The gNB can first decode Part 1 and then use Part 1 to obtain / determine the payload size of Part 2.

[0572] After the first resource is transmitted, the UE is able to transmit all information for the event-based beam report (first SSBRI / CRI, first L1-RSRP, second SSBRI / CRI, etc.).

[0573] The first resource can be a PUCCH / PUSCH resource capable of carrying multiple bits.

[0574] <Specific example>

[0575] like Figure 9 As shown, when an event occurs at a certain time interval, the UE can send the next first resource. Alternatively, the next first resource can also be the first resource after Y milliseconds / Y symbols. The value of Y can be set / indicated by higher-layer / physical-layer signaling, or it can be predefined by the specification.

[0576] The first resource may or may not be reserved (depending on the gNB implementation). If the first resource is reserved, it will not conflict with resources for other UEs.

[0577] On the other hand, if the first resource is not reserved, it may conflict with a lower priority resource that is intended for other UEs (e.g., when events occur simultaneously for UEs of both parties).

[0578] According to this method, the UE can appropriately control the one-step reporting.

[0579] <<Method 2-2>>

[0580] This method involves two-step reporting of event-based beam reporting in PUCCH / PUSCH. Figures 10 to 14 This is a diagram illustrating an example of event-based beam reporting as described in Mode 2-2.

[0581] The UE may be configured with a first reporting resource (also referred to as the first resource) and a second reporting resource (also referred to as the second resource) for notifying the second beam report. The first resource may consist of N bits. The second resource may consist of M bits. As described below, M > N.

[0582] After all resources (first resource and second resource) are transmitted, the UE is able to transmit all information for event-based beam reports (first SSBRI / CRI, first L1-RSRP, second SSBRI / CRI, etc.).

[0583] Additionally, to avoid conflicts between multiple UEs, the first resource can be reserved. The second resource can be reserved or not. Generally, containers with smaller payload sizes can be reused with greater capacity. For example, PF0 / 1 has fewer bits than PF2 / 3 / 4, so it can be reused more (with greater capacity). Therefore, the preferred number of bits for the first / second resources is M > N.

[0584] The primary resource can be a PUCCH-SR resource. The secondary resource can be a PUCCH / PUSCH resource. The primary and secondary resources are not limited to these and can also be other resources.

[0585] like Figure 10 As shown, when an event occurs at a certain time interval, the UE can send the next first resource. Furthermore, the UE can send the next second resource. Alternatively, the next first / second resource can be the first / second resource after Y milliseconds / Y symbols. The value of Y can be set / indicated by higher-layer / physical-layer signaling, or it can be predefined by specifications.

[0586] The second resource may or may not be reserved (depending on the gNB implementation). If the second resource is reserved, the first resource will not conflict with resources for other UEs.

[0587] On the other hand, if the second resource is not reserved, it may conflict with a lower priority resource that is intended for other UEs (e.g., both UEs send the same first resource associated with the same second resource).

[0588] The association between the first and second resources can be set / indicated through higher-level signaling / physical-level signaling, or it can be predefined through specifications. For example, the following Alt1~Alt3 can be exemplified ( Figures 10-12 ).

[0589] (Alt1)

[0590] like Figure 10 As shown, the first resource and the second resource can be associated (mapped) one-to-one.

[0591] (Alt2)

[0592] like Figure 11 As shown, a second resource can be associated with multiple (two) first resources. That is, two different first resources can be associated with the same second resource. Additionally, the offset Z can be set / indicated from the transmission of the second resource to the transmission of the next second resource.

[0593] (Alt3)

[0594] like Figure 12 As shown, a first resource can be associated with multiple (two) second resources. That is, a first resource can be associated with two different second resources.

[0595] In this case, as a method for selecting a second resource from two different second resources, at least one of the following can be applied.

[0596] • Based on predefined rules.

[0597] • Based on a predefined hopping rule (e.g., the second resource can be determined based on at least one of the time slot, the first resource (based on TDM / FDM / CDM), RNTI, and UE ID). In this case, the possibility of conflicts involving the second resource between UEs can be reduced.

[0598] • Based on NW (gNB) indications (e.g., ACK for the first reported gNB).

[0599] • Based on UE judgment (e.g., the reported beam index (SSBRI / CRI)). In this case, the UCI bits of the second resource can be reduced. The gNB can also detect which resource the UE has transmitted.

[0600] <Variation Example>

[0601] In addition, for the second resource, the conditions / restrictions shown in Options 1 to 3 (Opt1 to Opt3) can also be applied.

[0602] (Option 1)

[0603] For a first resource, a second resource can be set / indicated either through higher-level signaling / physical-level signaling or by being predefined through specifications.

[0604] (Option 2)

[0605] For a first resource, multiple (e.g., two) second resources can be set / indicated either through higher-layer signaling / physical layer signaling or by pre-definition through specifications. The selection of a second resource from multiple second resources can be determined either based on the first report information (content) or indicated by the DCI sent from the gNB after the first report is received.

[0606] (Option 3 (Opt3))

[0607] The second resource can be set / indicated without higher-layer / physical-layer signaling, or it can be defined in advance without specifications. For example, the second resource can also be dynamically indicated by the DCI (gNB ACK, as described later) sent from the gNB after the first report is received, using existing methods.

[0608] <Other variations>

[0609] As mentioned above, the second resource may not be reserved (this may also depend on the gNB implementation). Figure 13 This shows an example where the first / second resource is reserved. Figure 14 This illustrates an example where the first resource is reserved, the second resource is not reserved, and the two resources are shared among multiple UEs.

[0610] like Figure 13 As shown, the first resource can be separately configured / indicated (reserved) as a first resource for UE#1 and a first resource for UE#2. The second resource can be separately configured / indicated (reserved) as a second resource for UE#1 and a second resource for UE#2.

[0611] The UE may send a second resource to UE#1 after sending a first resource to UE#1. Furthermore, the UE may send a second resource to UE#2 after sending a first resource to UE#2.

[0612] like Figure 14 As shown, the first resource can be separately set / designated (reserved) as a first resource for UE#1 and a first resource for UE#2. The second resource can be commonly set / designated as a second resource for UE#1 and a second resource for UE#2. That is, the same second resource can be set / designated for both UE#1 and UE#2.

[0613] The UE can send a second resource to UE#1 / UE#2 after sending the first resource to UE#1. For example... Figure 14 As shown, since the second resource for UE#1 / UE#2 is duplicated, a conflict will occur if UE#1 and UE#2 send the second resource at the same time, and the base station will not be able to receive the second resource correctly. However, the probability of this situation is low (because it only occurs when the first resource for UE#1 and the first resource for UE#2 corresponding to the same second resource are sent at the same time).

[0614] According to this method, the UE can appropriately control the two-step reporting.

[0615] <<Method 2-3>>

[0616] This approach involves event-based beam reporting that takes into account gNB ACKs. Figure 15 This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3.

[0617] To avoid conflicts between UEs in the second resource, the ACK of the gNB after the first report can be imported.

[0618] When the UE reports / transmits the first resource, the UE can perform monitoring in order to receive an ACK (from the gNB). Upon receiving the ACK, the UE can report / transmit the second resource. That is, the UE can trigger the reporting / transmission of the second resource with the gNB's ACK for the first resource as a trigger.

[0619] The gNB's ACK can appropriately apply methods 1 to 4 in the above (ACK / NACK in event-based beam reports).

[0620] To avoid conflicts with the second resource, the gNB can send an ACK associated with the same second resource to only one UE.

[0621] The second resource can be configured, for example, via UE-specific higher-layer signaling. In this case, the second resource may not be reserved. For example, even if the gNB configures the same second resource for two UEs, the gNB can still indicate the specific second resource to only one UE via DCI to avoid conflicts.

[0622] <Specific example>

[0623] like Figure 15 As shown, the UE can send a first resource to the gNB. The gNB can send an ACK for the first resource to the UE. The UE can receive the ACK from the gNB and use the gNB's ACK as a trigger to send a second resource.

[0624] <Variation Example>

[0625] The gNB's ACK can also indicate the physical resource of a second resource. For example, a UE may be configured with multiple PUCCH / PUSCH resources via higher-layer signaling. In this case, the gNB's ACK can indicate one of those multiple PUCCH / PUSCH resources.

[0626] Since the gNB can specify different secondary resources for different UEs, it can avoid conflicts of secondary resources between multiple UEs.

[0627] The method of indicating the second resource (resource indicator) in the gNB ACK can be exemplified as follows.

[0628] • Explicit indications of new / existing DCI fields are utilized.

[0629] • Implicit indication of gNB-based ACK resources (e.g., control channel element (CCE) index, aggregation level (AGL), search space (SS) / CORESET, etc.).

[0630] Figure 16A and Figure 16B This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3. Figure 16A The time series is shown. Figure 16B This shows an example of RRC settings for the second resource.

[0631] like Figure 16AAs shown, the UE can send a first resource to the gNB. The gNB can send an ACK for the first resource to the UE. The UE can receive the ACK from the gNB. The gNB's ACK may contain code points indicating a specific second resource.

[0632] like Figure 16B As shown, the RRC settings for the second resource demonstrate the association between specific code points and specific second resources. For example, code point = {00} is associated with the second resource (resource #1), code point = {01} is associated with the second resource (resource #2), and code point = {11} is associated with the second resource (resource #4).

[0633] like Figure 16A As shown, when the code point = {01} is shown in the ACK of the gNB, the UE can be based on Figure 16B The association shown determines / selects a second resource (resource #2) from multiple second resources.

[0634] Then, the UE is able to send the determined / selected second resource (resource #2).

[0635] In this way, the UE can determine / select a specific second resource from multiple second resources based on the information contained in the gNB's ACK, and then perform transmission.

[0636] Multiple secondary resources can be configured, for example, via UE-specific higher-layer signaling. In this case, all secondary resources may not be reserved. For instance, even if the gNB configures the same set of secondary resources (multiple secondary resources) for all UEs, the gNB can still instruct each UE to use different secondary resources via DCI. This avoids conflicts between multiple UEs.

[0637] <Second Variation>

[0638] The gNB's ACK can utilize existing DCI fields to indicate PUCCH / PUSCH resources. This allows for control of beam reporting using the gNB's ACK while suppressing its impact on specifications. The indication method for PUCCH / PUSCH resources (secondary resources) can apply any of the following options A to B (OptA to OptB).

[0639] (Option A (OptA))

[0640] When the gNB's ACK is in DCI format 1_0 / 1_1 / 1_2 (e.g., the DCI for scheduling PUCCH), the PUCCH resource indicator (PRI) can be used to indicate a second resource.

[0641] That is, the second resource can be a PUCCH resource. The RRC setting for the PUCCH resource set can utilize an existing PUCCH resource set. Alternatively, a PUCCH resource set dedicated to the second resource (i.e., dedicated to beam reporting) can also be set.

[0642] (Option B (OptB))

[0643] When the gNB's ACK is in DCI format 0_0 / 0_1 / 0_2, the DCI field of the scheduling PUSCH can be used to indicate a second resource.

[0644] That is, the second resource can be a PUSCH resource. The RRC settings for PUSCH resources can utilize existing PUSCH resources. Alternatively, a PUSCH resource can be set up specifically for the second resource (i.e., dedicated to beam reporting).

[0645] Based on the above options A to B (OptA to OptB), the first resource can be set as a dedicated PUCCH-SR resource, which can suppress the impact on the specification.

[0646] Figure 17A and Figure 17B This is a diagram illustrating an example of event-based beam reporting involved in methods 2-3. Figure 17A The time series is shown. Figure 17B An example of RRC configuration for the second resource is shown. As described above, the first resource can be a dedicated PUCCH-SR resource, and the second resource can be a PUSCH / PUCCH resource scheduled via DCI for gNB ACK.

[0647] like Figure 17A As shown, the UE can send a first resource to the gNB. The gNB can send an ACK for the first resource to the UE. The UE can receive the ACK from the gNB. The gNB's ACK (DCI) may contain a code point (PRI) indicating a specific second resource.

[0648] like Figure 17B As shown, the RRC settings for the second resource illustrate the association between a specific code point (PRI) and a specific second resource. For example, code point = {000} is associated with PUCCH resource #1, code point = {001} is associated with PUCCH resource #2, and code point = {111} is associated with PUCCH resource #8.

[0649] like Figure 17A As shown, when the PRI code point = {001} is shown in the gNB's ACK, the UE can base on Figure 17B The association shown indicates that PUCCH resource #2 will be determined / selected as the second resource.

[0650] Then, the UE is able to send the determined / selected second resource (resource #2).

[0651] In this way, the UE can determine / select a specific second resource based on the information contained in the gNB's ACK and perform transmission.

[0652] In the second variation shown in Figure 17, an example is illustrated where the SR (first resource) triggers the DCI, and this DCI triggers the PUCCH (second resource). In this case, the scheduling of the PDSCH may not be required in this DCI. That is, the DCI used for the gNB's ACK may not be the DCI that schedules the PDSCH.

[0653] <Third Variation>

[0654] As shown in the second variation, when using existing DCI fields to control event-based beam reporting, it is necessary to clarify how to distinguish the purpose of the event-based beam reporting from the purpose of existing UCI reporting.

[0655] Therefore, a method is proposed to identify / distinguish the purpose of beam reports.

[0656] (Alt1)

[0657] To indicate an ACK for an event-based beamforming report, a single bit can be appended to the DCI field. This allows the UE and gNB to mutually recognize that an event-based beamforming report is being sent via the PUCCH indicated by the PRI.

[0658] In the event of a conflict with other UCI types within the PUCCH, discard / reuse rules can be defined in advance to ensure that the UE and gNB have a common understanding regarding the presence of other UCI content within the PUCCH, the accurate payload size of the UCI, and the mapping order.

[0659] (Alt2)

[0660] Other methods to distinguish DCI include importing new DCI formats, new RNTI, and dedicated SS / CORESET.

[0661] Existing DCIs (which may include PDSCH scheduling) can be used to indicate existing PUCCH resources. New DCIs used to indicate ACKs for the aforementioned gNBs can be used to indicate secondary resources (for secondary reporting).

[0662] That is, the UE can determine the purpose of beam reporting based on existing / new DCI.

[0663] <Note>

[0664] The Alt1 to Alt2 (association between the first and second resources) in method 2-2 above can also be applied in method 2-3. That is, the first and second resources can also be associated one-to-one. Alternatively, one second resource can be associated with multiple (two) first resources. That is, two different first resources can be associated with the same second resource.

[0665] According to this method, the UE can appropriately control the beam reporting of ACKs that utilize the gNB.

[0666] According to the second embodiment, the UE is able to appropriately control beam reporting that utilizes UCI.

[0667] <Third Implementation Method>

[0668] The third implementation involves an extension of CSI priority.

[0669] As mentioned above, the priority of existing CSI reports (also known as CSI priority, or simply priority) is represented by equation (1). Here, this priority needs to be extended to beneficiary-based event-based beam reporting.

[0670] Event-based beamforming is a type of beamforming report initiated by the UE and is envisioned as a report that is significantly more important than regular CSI reports and is required in emergency situations. Therefore, it is possible to consider controlling the priority based on the presence or absence of event-based beamforming reports.

[0671] Therefore, a new dimension / parameter (z) is proposed to be added for CSI prioritization of event-based beam reporting.

[0672] Here, z can represent a value indicating whether the CSI report of the object is an event-based beam report. More specifically, it could be z=1 in the case of an event-based beam report and z=0 in the case of a non-event-based beam report.

[0673] Based on these, CSI prioritization for event-based beam reporting is implemented. iCSI (z, y, k, c, s) can also be obtained by the following equation (2).

[0674] (Formula 2) Pri iCSI (y, k, c, s) = 4·2·N cells ·Ms·z+2·N cells ·Ms·y+N cells ·M s ·k+M s ·c+s

[0675] In the first term of the above equation (the term containing z), weighting for event-based beam reporting is considered by multiplying by several parameters. The result is the ability to calculate a higher priority compared to other types of reports.

[0676] Specifically, in Equation 2, when event-based beam reporting is triggered, for example by setting z=1, y=0, k=0, beam reporting can be controlled with a higher priority than existing UCI (e.g., L1-RSRP).

[0677] According to this implementation, the UE can apply CSI priority to appropriately control event-based beam reporting.

[0678] <Fourth Implementation Method>

[0679] The fourth implementation relates to a method for avoiding blind detection of UCI bits based on gNB.

[0680] Figure 18 This is a diagram illustrating an example of the encoding / decoding correspondence between the channel between the UE and gNB. Figure 19 and Figure 20 This is a diagram illustrating an example of event-based beam reporting according to the fourth embodiment.

[0681] As mentioned above, it is assumed that the number of beams to be reported is variable. This is because, in the case of multiple beams being detected, the UE needs to report them. Therefore, the UE needs to determine / decide the number of beams to report.

[0682] However, in existing specifications (such as LTE / NR), gNBs are not required to perform blind detection of UCI bits. This is because, for gNBs, blind detection would complicate implementation and potentially increase the gNB's workload.

[0683] Therefore, in event-based beam reporting, it can also be considered that in order to suppress the load on the gNB, the number (size) of UCI bits needs to be notified to the gNB in ​​advance.

[0684] like Figure 18 As shown, consider a scenario where a 4-bit UCI is encoded into a 20-bit PUCCH by the UE and sent to the gNB. In this case, the gNB pre-identifies that the UCI consists of 4 bits. Therefore, the gNB can take this bit count into account when decoding the received 20-bit PUCCH.

[0685] To avoid blind detection by gNB, the following options 1 to 3 (Opt1 to Opt3) are proposed.

[0686] (Option 1)

[0687] The UCI size can be fixed through gNB settings / instructions. The UE can append "0" (also known as a size adjustment field) to make the UCI size consistent.

[0688] (Option 2)

[0689] The size of the second report can be reported / notified through the first report. That is, information related to the size of the second report can be included in the first report.

[0690] Specifically, the first report needs a field indicating the size of the UCI in the second report. For example, at least one of the following can be included in the first report.

[0691] • The number of beams X of the reporting object.

[0692] • SSBRI / CRI for the Xth maximum / optimal beam.

[0693] • L1-RSRP / SINR for the Xth largest / optimal beam.

[0694] <Variation Example>

[0695] The UE may be configured with multiple PUCCH / PUSCH resources for the first report (as the first resource). The UE sends different first resources depending on the value of X.

[0696] For example, such as Figure 19 As shown, the UE may be configured with two resources as the first resource (X=1, 2).

[0697] Here, with X=1, the first resource #1 is sent. This first resource #1 can be a PUCCH-SR resource (PF0 / 1).

[0698] When X=2 (X>1), the first resource #2 is sent. The second resource #1 can be a resource of PF0 / 1 / 2 / 3 / 4.

[0699] (Option 3 (Opt3))

[0700] The second report can be divided into two parts.

[0701] For example, similar to existing specifications, CSI Part 1 can represent the number of non-zero coefficients (NZCs) in extended type 2 of Rel.16. That is, the number of non-zero coefficients can correspond to the size of CSI Part 2.

[0702] The concept of CSI Part 1 / 2 can be applied to the second report of this disclosure. The second report can be divided into a first part (corresponding to CSI Part 1) and a second part (corresponding to CSI Part 2). The first part / second part can each contain the following information.

[0703] (Part 1)

[0704] • Number of SSBRI / CRI (number of beams reported / reported objects).

[0705] (Part Two)

[0706] • SSBRI / CRI for the Xth maximum / optimal beam.

[0707] • L1-RSRP / SINR for the Xth largest / optimal beam.

[0708] Additionally, the first SSBRI / CRI and the first L1-RSRP / SINR are always reported. Therefore, the first SSBRI / CRI and the first L1-RSRP / SINR may also be included in the first part. In this case, the first part may also indicate whether the first and subsequent SSBRI / CRIs, or the first and subsequent L1-RSRP / SINRs, are included in the second part.

[0709] Information related to Part One / Part Two can be encoded separately. Furthermore, as... Figure 20 As shown, the first part / second part can also be mapped to different resource elements (REs).

[0710] For example, the first part can be mapped earlier than the second part. Thus, the gNB is able to begin decoding the signal / channel at an early stage.

[0711] In addition, such as Figure 20 As shown, the UCI payload size of the second part can be the same as or larger than that of the first part. Furthermore, when multiple (e.g., two) first resources are configured, the UCI payload size of the second part corresponding to X=2 can be larger than that of the second part corresponding to X=1.

[0712] According to this implementation, beam reporting can be appropriately controlled while avoiding blind detection of gNB-based UCI bits.

[0713] <Supplement>

[0714] <<Information Notification to UE>>

[0715] The notification of any information from the Network (NW) (e.g., Base Station (BS)) to the UE in the above embodiments (in other words, the reception of any information from the BS in the UE) can also be performed 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.

[0716] 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) in the MAC subheader that is not specified in the existing standard.

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

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

[0719] <<Notifications from UE>>

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

[0721] In the case where the above notification is delivered via MAC CE, the MAC CE can also be identified by including a new LCID in the MAC sub-header that is not specified in the existing standard.

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

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

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

[0725] In the UE / BS, a specific processing / operation / control / conception / information regarding at least one of the above embodiments may also be applied (used) if any one or more of the following conditions are met:

[0726] • This indicates that the specific high-level parameters for the aforementioned processing / operation / control / conception / information have been set;

[0727] The specific processing / operation / control / concept / information mentioned above is determined based on relevant high-level parameters;

[0728] • The aforementioned specific processing / operation / control / conception / information is specified / activated / triggered via MAC CE / DCI / UCI / resource / channel / RS;

[0729] • The report or support indicates the specific UE capability (or related) to the aforementioned specific processing / operation / control / conception / information;

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

[0731] The aforementioned specific UE capabilities can also represent at least one of the following:

[0732] • Supports specific processing / operation / control / information regarding at least one of the above embodiments.

[0733] • Supports event-triggered beam reporting.

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

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

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

[0737] • Supports CSI prioritization for event-based beam reporting.

[0738] • Supports CSI Part 1 / 2 for event-based beam reporting.

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

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

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

[0742] (Postscript)

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

[0744] [Postscript 1]

[0745] A terminal having:

[0746] The receiving unit receives downlink control information (DCI) that triggers event-based beam reporting; and

[0747] The control unit controls the event-based beam reporting based on the DCI.

[0748] The control unit performs control to enable the event-based beam reporting to be reported using MAC control elements (CE) or uplink control information (UCI).

[0749] [Postscript 2]

[0750] The terminal as described in Appendix 1, wherein,

[0751] The control unit determines the utilization of the MAC CE or the UCI in relation to the event-based beamforming report based on the report content.

[0752] [Postscript 3]

[0753] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0754] The resources used for event-based beam reporting are any one of the following: scheduling request resources for the uplink control channel (PUCCH), PUCCH resources, and uplink shared channel (PUSCH) resources.

[0755] [Postscript 4]

[0756] The terminal as described in any one of Annexes 1 to 3, wherein,

[0757] The number of beams for the reported object is variable.

[0758] (Postscript)

[0759] Regarding one embodiment (second / third embodiment) of this disclosure, the following invention is noted.

[0760] [Postscript 1]

[0761] A terminal having:

[0762] The receiving unit receives downlink control information (DCI) that triggers event-based beam reporting; and

[0763] The control unit performs control based on the DCI to report the event-based beamforming using uplink control information (UCI).

[0764] The control unit controls the event-based beam reporting in one or two steps.

[0765] [Postscript 2]

[0766] The terminal as described in Appendix 1, wherein,

[0767] When the control unit controls the event-based beam reporting in a one-step manner, it controls the event-based beam reporting based on the number of beams of the reporting object set in the first reporting resource of the event-based beam reporting.

[0768] [Postscript 3]

[0769] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0770] When the control unit controls the event-based beam reporting in a two-step manner, a first reporting resource and a second reporting resource are set, wherein the number of bits in the second reporting resource is greater than that in the first reporting resource.

[0771] [Postscript 4]

[0772] The terminal as described in any one of Annexes 1 to 3, wherein,

[0773] The first report of this event-based beamforming uses reserved resources that are not used by other terminals.

[0774] (Postscript)

[0775] Regarding one embodiment (second / third embodiment) of this disclosure, the following invention is noted.

[0776] [Postscript 1]

[0777] A terminal having:

[0778] The receiving unit receives downlink control information (DCI) that triggers event-based beam reporting; and

[0779] The control unit performs control based on the DCI to report the event-based beamforming using uplink control information (UCI).

[0780] The control unit controls the execution of the event-based beam reporting, which utilizes a first reporting resource and a second reporting resource set by the base station, based on an ACK response from the base station.

[0781] [Postscript 2]

[0782] The terminal as described in Appendix 1, wherein,

[0783] The receiving unit receives the ACK for the first resource.

[0784] The control unit controls the transmission of the second resource based on the ACK.

[0785] [Postscript 3]

[0786] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0787] The ACK uses a specific DCI field to indicate the second resource.

[0788] [Postscript 4]

[0789] The terminal as described in any one of Annexes 1 to 3, wherein,

[0790] The control unit applies a priority corresponding to the presence or absence of the event-based beam reporting to control the event-based beam reporting.

[0791] (Postscript)

[0792] Regarding one embodiment (fourth embodiment) of this disclosure, the following invention is noted.

[0793] [Postscript 1]

[0794] A terminal having:

[0795] The receiving unit receives downlink control information (DCI) that triggers event-based beam reporting; and

[0796] The control unit performs control based on the DCI to report the event-based beamforming using uplink control information (UCI).

[0797] The control unit controls the execution of the event-based beam reporting, which utilizes a two-step process involving a first report and a second report.

[0798] The number of bits in the UCI is fixed.

[0799] [Postscript 2]

[0800] The terminal as described in Appendix 1, wherein,

[0801] The control unit determines the size of the second report based on the information contained in the first report.

[0802] [Postscript 3]

[0803] The terminal as described in Appendix 1 or Appendix 2, wherein,

[0804] The second report is divided into a first part and a second part.

[0805] [Postscript 4]

[0806] The terminal as described in any one of Annexes 1 to 3, wherein,

[0807] The first report contains information related to the number of beams of the reported object, as well as at least one of the fields for size adjustment.

[0808] (Wireless communication system)

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

[0810] Figure 21This 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 (5GNR) as standardized by the Third Generation Partnership Project (3GPP).

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

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

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

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

[0815] Alternatively, the wireless communication system 1 can also utilize MIMO (Multiple Input Multiple Output). 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 supercell) can also be composed of multiple [virtual] cells (e.g., also called subcells). A supercell can also be equivalent to a cell with a fixed physical range, and a subcell 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 cellless system.

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

[0817] 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 correspond to a frequency band higher than FR2.

[0818] In addition, in each CC, the user terminal 20 may also use at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) for communication.

[0819] Multiple base stations 10 can also be connected via wired (e.g., fiber optic based on the Common Public Radio Interface (CPRI), X2 / Xn interface, etc.) or wireless (e.g., NR communication). For example, when NR communication between base stations 11 and 12 is used as a backhaul, 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.

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

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

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

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

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

[0825] As a downlink channel, the wireless communication system 1 can also use downlink shared channels (Physical Downlink Shared Channel (PDSCH)), broadcast channels (Physical Broadcast Channel (PBCH)), downlink control channels (Physical Downlink Control Channel (PDCCH)) and so on, which are shared among the user terminals 20.

[0826] In addition, as uplink channels, the wireless communication system 1 may also use uplink shared channels (Physical Uplink Shared Channel (PUSCH)), uplink control channels (Physical Uplink Control Channel (PUCCH)), random access channels (Physical Random Access Channel (PRACH)) and so on, which are shared by each user terminal 20.

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

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

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

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

[0831] A search space can also correspond to a PDCCH candidate corresponding 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.

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

[0833] 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".

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

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

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

[0837] (Base station)

[0838] Figure 22 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.

[0839] Furthermore, while this example primarily illustrates the functional blocks of the characteristic portions of this embodiment, it can also be envisioned that the base station 10 also possesses other functional blocks required for wireless communication. Some of the processing of each unit described below may also be omitted.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0855] Furthermore, base station 10 can also 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.

[0856] In this disclosure, base station 10 may include a single 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.

[0857] Additionally, the transmit / receive unit 120 can transmit downlink control information (DCI) that triggers an event-based beam report. The control unit 110 can control the reception of the event-based beam report, which is transmitted from the terminal based on the DCI and using a MAC control element (CE) or uplink control information (UCI).

[0858] The control unit 110 can be controlled to receive the event-based beam report, which is transmitted from the terminal based on the DCI and using uplink control information (UCI) in a one-step or two-step manner.

[0859] Control unit 110 can control the reception of the event-based beam report, which is transmitted from the terminal based on the DCI and using uplink control information (UCI). Transmit / receive unit 120 can transmit an affirmative acknowledgment (ACK) for controlling the execution of the two-step event-based beam report using first and second reporting resources.

[0860] Control unit 110 can perform control to enable control to utilize a two-step event-based beamforming report, consisting of a first report and a second report, which is transmitted from the terminal based on the DCI and using uplink control information (UCI). The number of bits in the UCI can be fixed.

[0861] (User terminal)

[0862] Figure 23 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, the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may each be provided as one or more.

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

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

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

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

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

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

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

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

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

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

[0873] Furthermore, whether or not to apply DFT processing can be based on the settings of transform precoding. 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 in order to transmit the channel using the DFT-s-OFDM waveform. If not, the transmit / receive unit 220 (transmit processing unit 2211) can perform the above transmission processing without performing DFT processing.

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

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

[0876] 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 acquire user data.

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

[0878] 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, NZPCSI-RS, ZP CSI-RS, CSI-IM, CSI-SSB, etc., can also be interchanged.

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

[0880] Additionally, the transmit / receive unit 220 can receive downlink control information (DCI) that triggers event-based beamforming. The control unit 210 can control the event-based beamforming based on the DCI. The control unit 210 can control the reporting of the event-based beamforming using either a MAC control element (CE) or uplink control information (UCI). The control unit 210 can determine the utilization of the MAC CE or the UCI for the event-based beamforming based on the report content. The resources used for the event-based beamforming can be any one of the following: scheduling request resources for the uplink control channel (PUCCH), PUCCH resources, and uplink shared channel (PUSCH) resources. The number of beams to be reported can be variable.

[0881] Control unit 210 can perform control based on the DCI to report the event-based beamforming using uplink control information (UCI). Control unit 210 can control the event-based beamforming in one-step or two-step manner. When controlling the event-based beamforming in one-step manner, control unit 210 can control the event-based beamforming based on the number of beams of the reporting object set in the first reporting resource of the event-based beamforming. When control unit 210 controls the event-based beamforming in two-step manner, a first reporting resource and a second reporting resource are set, and the number of bits in the second reporting resource is greater than that in the first reporting resource. The first reporting resource of the event-based beamforming can be a reserved resource not used by other terminals.

[0882] Control unit 210 can perform control based on the DCI to report the event-based beamforming using uplink control information (UCI). Control unit 210 can control the execution of the two-step event-based beamforming using a first reporting resource and a second reporting resource set by the base station, based on a positive acknowledgment (ACK) from the base station. Transmit / receive unit 220 can receive the ACK for the first resource. Control unit 210 can control the transmission of the second resource based on the ACK. The ACK can indicate the second resource using a specific DCI field. Control unit 210 can apply a priority corresponding to the presence or absence of the event-based beamforming to control the event-based beamforming.

[0883] Control unit 210 can perform control based on the DCI to report the event-based beamforming using uplink control information (UCI). Control unit 210 can control the execution of the two-step event-based beamforming using a first report and a second report. The number of bits in the UCI can be fixed. Control unit 210 can determine the size of the second report based on information contained in the first report. The second report can be divided into a first part and a second part. The first report may contain at least one of the following: information related to the number of beams of the reporting object and a field for size adjustment.

[0884] (Hardware structure)

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

[0886] 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. Each of these, as described above, is not particularly limited in its implementation method.

[0887] 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 24 This diagram illustrates 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, and a bus 1007.

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

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

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

[0891] The processor 1001 enables the operating system to operate and control the computer as a whole. The processor 1001 may also be 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.

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

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

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

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

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

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

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

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

[0900] (Variation example)

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

[0902] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitutes 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).

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

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

[0905] 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. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-time slot can also be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using mini-time slots can also be called PDSCH (PUSCH) mapping type B.

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

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

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

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

[0910] 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 serve as 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.

[0911] A TTI with a duration of 1ms can also be referred to as a normal TTI (TTI in 3GPPRel.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.

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

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

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

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

[0916] In addition, 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.

[0917] 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 certain 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.

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

[0919] 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. Additionally, terms such as "cell" and "carrier" in this disclosure may be replaced with "BWP".

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

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

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

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

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

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

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

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

[0928] 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, the MAC control element (CE).

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

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

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

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

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

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

[0935] 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 / space / 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.

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

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

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

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

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

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

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

[0943] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its overall coverage area can be divided into several 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.

[0944] In this disclosure, the act of a base station sending information to a terminal can also be rewritten in relation to the act of the base station instructing the terminal to perform control / operation based on that information.

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

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

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

[0948] The term "mobile body" refers to a movable object whose speed is arbitrary, including when the object is stationary. Examples of such mobile bodies include vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ships and other watercraft), airplanes, rockets, artificial satellites, drones, multicopters, quadcopters, hot air 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.

[0949] 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 also includes a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station can also be an Internet of Things (IoT) device such as a sensor.

[0950] Figure 25 This is a diagram illustrating an example of a vehicle according to one embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (including a current sensor 50, a 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 shift lever sensor 57, and an object detection sensor 58), an information service unit 59, and a communication module 60.

[0951] 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 steering handle) that steers at least one of the front wheels 46 and the rear wheels 47 based on operation of the steering wheel by the user.

[0952] 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 to the electronic control unit 49. The electronic control unit 49 can also be referred to as an electronic control unit (ECU).

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

[0954] The information service unit 59 comprises various devices such as a navigation system, audio system, speakers, display, television, and radio, used to provide (output) various information such as driving information, traffic information, and entertainment information, and 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.

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

[0956] The driver assistance system unit 64 comprises various devices used to provide functions for preventing accidents or reducing the driver's workload, such as millimeter-wave radar, light detection and ranging (LiDAR), cameras, positioning detectors (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, and one or more ECUs that control these devices. Furthermore, the driver assistance system unit 64 sends and receives various information via communication module 60 to realize driver assistance functions or autonomous driving functions.

[0957] 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) with 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, axles 48, microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49 of the vehicle 40, and various sensors 50-58 via the communication port 63.

[0958] The communication module 60 can be 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 with external devices via wireless communication. The communication module 60 can be located both inside and 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).

[0959] The communication module 60 can also wirelessly transmit at least one of the signals input to the electronic control unit 49 from the various sensors 50-58 described above, the information obtained based on these signals, and the information based on input from an external (user) source obtained via the information service unit 59 to an external device. 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 inputs.

[0960] The communication module 60 receives various information (traffic information, signal information, workshop information, etc.) sent from external devices and displays it on the vehicle's information service unit 59. 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 by the communication module 60 (or the data / information decoded from the PDSCH).

[0961] Furthermore, the communication module 60 stores various types of information received from external devices into a memory 62 that can be utilized by the microprocessor 61. Based on the information stored in the memory 62, 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, axles 48, and various sensors 50-58, etc., of the vehicle 40.

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

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

[0964] In this disclosure, operations are assumed to be performed by the base station, and sometimes, depending on the circumstances, by its upper node. In a network containing one or more network nodes having a base station, the various operations performed for communication with a terminal can obviously 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.

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

[0966] 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, where 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 (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB)), Bluetooth (registered trademark), systems utilizing other suitable wireless communication methods, and next-generation systems derived from, modified, generated, or specified based on these methods. Furthermore, multiple systems can be combined (e.g., LTE or LTE-A, combinations with 5G, etc.) for application.

[0967] 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".

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

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

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

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

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

[0973] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (where "..." can also be expressed using a that clause, a to infinitive, etc.) can also be interchanged with "be expected ..." or "... (where "..." is a to infinitive, the verb after removing "to")." Similarly, "does not expect ..." can also be interchanged with "be not expected ..." or "not ... (where "..." is a to infinitive, the verb after removing "to")." Furthermore, "An apparatus A is not expected ..." can also be interchanged with "Apparatus B other than apparatus A does not expect ..." (for example, if apparatus A is a UE, apparatus B could also be a base station).

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

[0975] 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.”

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

[0977] 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."

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

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

[0980] In this disclosure, words such as "below," "less than," "above," "more than," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., are not limited to the positive, comparative, and superlative degrees, and can be interchanged. Additionally, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow," etc., as expressions with "i" appended (i being any integer), are not limited to the positive, comparative, and superlative degrees, and can be interchanged (for example, "highest" can also be interchanged with "i-th highest").

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

[0982] In this disclosure, phrases such as "when A, B", "if A, then B", "B upon A", "B in response to A", "based on A", "B during / while A", "before A", "at the same time as / on A", "after A", "since A", and "until A" can be rewritten interchangeably. Furthermore, A and B can be replaced with nouns, gerunds, or ordinary sentences, 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 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.

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

[0984] 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 downlink control information (DCI) that triggers event-based beamforming reports; and The control unit performs control based on the DCI to report the event-based beam report using uplink control information, i.e., UCI. The control unit controls the execution of the event-based beam reporting, which utilizes a two-step process involving a first report and a second report. The number of bits in the UCI is fixed.

2. The terminal as described in claim 1, wherein, The control unit determines the size of the second report based on the information contained in the first report.

3. The terminal as described in claim 1, wherein, The second report is divided into a first part and a second part.

4. The terminal as described in claim 1, wherein, The first report contains information related to the number of beams of the reported object, as well as at least one of the fields for size adjustment.

5. A wireless communication method for a terminal, comprising: The steps of receiving downlink control information (DCI) that triggers event-based beam reporting; Control is performed based on the DCI to enable the use of uplink control information, i.e., UCI, to report the event-based beam reporting step. as well as The steps for controlling the execution of the event-based beam reporting, which utilizes a two-step process involving both a first report and a second report, are as follows. The number of bits in the UCI is fixed.

6. A base station, comprising: The transmitting unit transmits downlink control information (DCI) that triggers event-based beamforming reports; and The control unit performs control by utilizing a two-step event-based beamforming report, consisting of a first report and a second report, which is transmitted from the terminal based on the DCI and using uplink control information, i.e., UCI. The number of bits in the UCI is fixed.

Images