Terminal, wireless communication method, and base station

Abstract

A terminal according to one embodiment of the present disclosure includes a reception unit that receives a setting of a channel state information (CSI) report scheduled by a base station and a setting of a UE-initiated beam report (UEIBR) initiated by a UE, and a control unit that, in a case where both the CSI report and the UEIBR are supported, controls transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied.

Description

Technical Field

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

[0002] In Universal Mobile Telecommunications System (UMTS) networks, Long Term Evolution (LTE) was standardized with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Furthermore, LTE-Advanced (3GPP Rel. 10-14) was standardized with the aim of further increasing capacity and improving 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), it is being investigated how terminals (user terminals, user equipment (UE)) can use L1L2-triggered mobility (LTM) as specified in Rel.18 when making inter-cell movements.

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

[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 handover. Event-triggered beam reports can also be referred to as UE-initiated beam reports (UEIBR).

[0013] Assume the UE supports both existing CSI reporting and UEIBR. In this case, it's necessary to clarify the regulations concerning the relationship between the two. If these regulations are unclear, lower latency communication cannot be achieved, raising concerns about hindering improvements in communication quality / throughput.

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

[0015] Methods for solving problems

[0016] One aspect of this disclosure relates to a terminal comprising: a receiving unit that receives settings for channel state information (CSI) reports scheduled by a base station and settings for UE-initiated beam reports (UEIBRs); and a control unit that, in supporting both the CSI reports and the UEIBRs, controls the transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied.

[0017] Invention Effects

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

[0019] Figure 1A as well as Figure 1B This represents an example of a unified / common TCI framework.

[0020] Figure 2A as well as Figure 2B This represents an example of a TCI status indication based on DCI.

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

[0022] Figure 4 This is a diagram representing an example of the TCI status as specified in Rel.16.

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

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

[0025] Figure 7 This is a diagram illustrating an example of overlap between existing CSI reports and Event-Based Beam Reporting (UEIBR).

[0026] Figure 8 This is a diagram illustrating an example of beam reporting according to the first embodiment (corresponding to case 1).

[0027] Figure 9 This is a diagram illustrating an example of beam reporting in the first embodiment (corresponding to case 2).

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

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

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

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

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

[0033] (CSI Report)

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

[0035] 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) and other signals to measure channel state.

[0036] CSI-RS resources can also include at least one of Non-Zero Power (NZP) CSI-RS and CSI Interference Management (IM). An SS / PBCH block is a block that includes 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.

[0037] Additionally, CSI may include at least one of the following: 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).

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

[0039] 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 (semi-persistent CSI: SP-CSI) reports.

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

[0041] CSI report configuration information may include, for example, 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 also be used to determine parameters such as the type of CSI reporting method (whether it is SP-CSI, etc.) and reporting period. CSI report configuration information may also include information indicating which signal (or resource used by which signal) was used to measure the CSI (CSI-ResourceConfigId).

[0042] (TCI, Spatial Relations, QCL)

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

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

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

[0046] QCL is an indicator that represents the statistical properties of a signal / channel. For example, if a signal / channel has a QCL relationship with other signals / channels, it can also mean that among these different 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0062] (Unified / Common TCI Framework)

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

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

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

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

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

[0068] A TCI pool (set) can be either multiple TCI states set via RRC parameters, or multiple TCI states activated via MAC CE (activating TCI states, activating TCI pools, or sets) among multiple TCI states set via RRC parameters. 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.

[0069] The number of TCI states corresponding to each of more than one TRP can also be specified. For example, the number of TCI states (UL TCI states) applied to the UL channel / RS can be specified as N (≥1), and the number of TCI states (DL TCI states) applied to the DL channel / RS can be specified as 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.

[0070] In this disclosure, when N=M=X (X is any integer), it is also intended to notify / set / indicate to the UE the common TCI state (joint TCI state) in X ULs (corresponding to X TRPs) and DLs. Furthermore, when N=X (X is any integer) and M=Y (Y is any integer, or Y=X), it is also intended to notify / set / indicate to the UE X UL TCI states (corresponding to X TRPs) and Y DLTCI states (corresponding to Y TRPs) (i.e., independent TCI states).

[0071] For example, when recorded as N=M=1, it can also mean: a notification / setting / indication to the UE of a TCI state common in a UL and DL for a single TRP (a joint TCI state for a single TRP).

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

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

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

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

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

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

[0078] 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 states set via the RRC parameter can also be referred to as set TCI states or configured TCI states (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 via the DCI can also be referred to as indicated TCI state or indicated TCI state (e.g., indicated TCI state).

[0079] 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 a UL TCI and a DL TCI.

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

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

[0082] Furthermore, in this disclosure, the high-level parameters (RRC parameters) for setting multiple TCI states can also be referred to as setting information for multiple TCI states, or simply "setting information". Additionally, in this disclosure, using DCI to indicate one of 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".

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

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

[0085] From Rel.17 NR onwards, it is envisioned that support will be provided for the activation / indication of beams with TCI states associated with different physical cell identifiers (PCIs) via MAC CE / DCI. 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.

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

[0087] (TCI status indication)

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

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

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

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

[0092] 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 with the Rel.17 TCI state ID; or, for all CCs in the same CC list that is 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 with the Rel.17 TCI state ID. If DL allocation is available, DCI format 1_1 / 1_2 may or may not be accompanied by DL allocation.

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

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

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

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

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

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

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

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

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

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

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

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

[0105] 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 procedure below.

[0106] [Operation] If the higher-layer parameter tci-PresentInDCI-1-2 is not set for the CORESET used in the PDCCH that transmits 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 all CORESETs within the indicated BWP.

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

[0108] Figure 2B This example illustrates an independent DL / UL TCI status indication based on DCI. At least one of the TCI status IDs—one indicating the TCI status for DL ​​only and one indicating the TCI status for UL only—is associated with the value of the TCI field used for the independent DL / UL TCI status indication. 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.

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

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

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

[0112] The Rel.17 TCI state can also be shared with at least one of the following: UE-specific receive, dynamically authorized (DCI) / configured authorized 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.

[0113] For the Rel.17 TCI state, a TCI state other than the unified TCI state can also refer to the Rel.17 TCI state configured using the (Rel.17) MAC CE / 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.

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

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

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

[0117] [PDCCH]

[0118] • If followUnifiedTCIState is set for CORESET0, the application indicates the TCI state. Otherwise, the Rel.15 specification applies to this CORESET. That is, CORESET0 follows the TCI state activated via MAC CE, or is in QCL with SSB.

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

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

[0121] [PDSCH]

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

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

[0124] [CSI-RS]

[0125] • When the A-CSI-RS used for CSI acquisition or beam management is set to followUnifiedTCIState (for the CORESET of the PDCCH that triggers the A-CSI-RS), the application indicates the TCI state. For other CSI-RS, the application applies the configured TCI state for that CSI-RS.

[0126] [PUCCH]

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

[0128] [PUSCH]

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

[0130] [SRS]

[0131] • When the SRS resource set used for beam management and for codebook (CB) / non-codebook (NCB) / antenna switching is configured to follow a unified TCI state, the indicated TCI state is applied. For other SRS, the TCI state set within that SRS resource set is applied.

[0132] (TCI state switching)

[0133] Rel.15 / 16 specifies the delay time for switching the activated TCI state for a UE that has been set to more than one TCI state in the serving cell.

[0134] 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, such as the base station). Therefore, the UE needs to measure and report beam / RS, and both the UE and the NW need to have a common understanding of whether the TCI state is known or unknown.

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

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

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

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

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

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

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

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

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

[0144] 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) including 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 (n+T) / (NR time slot length), the UE receives the Physical Downlink Control Channel (PDCCH) for the serving cell where the TCI state handover has occurred, indicating the target TCI state. Additionally, in time slot n+T... HARQ +3N subframe,μ slot Previously, it was able to receive the PDCCH in the old (pre-switching) TCI state. From time slot n+T HARQ +3N subframe,μ slot 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 not defined (see reference). Figure 3 ).

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

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

[0147] When MAC CE is used 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 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 (n / (NR time slot length)), the UE receives the PDCCH of the serving cell in the target TCI state from the cell where the TCI state handover occurred. Additionally, the UE can receive the PDCCH of the old (pre-handover) TCI state until time slot n+T. HARQ +3N subframe,μ slot .

[0148] 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 SSB, TO uk It is 0.

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

[0150] 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 received power measurement. In frequency range (FR) 1, or in FR2 when QCL type D is not set, T... L1-RSRPIt is 0. Otherwise, it is the time required for the determination / refinement of the receive beam in FR2.

[0151] 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 used for scheduling PDSCH CORESET in time slot n is enabled, then in the first time slot after time slot n + timeDurationForDCI, the PDSCH of the serving cell with the target TCI state of the TCI state switch has been received. Here, timeDurationForDCI is the time required for the reception of PDCCH and spatial relationship / QCL-related information (spatial QCL information) to be sent to the application for receiving DCI used for PSDCH.

[0152] 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 first time slot after (NR time slot length), receive the PDCCH of the serving cell whose TCI state has been switched.

[0153] Here, T RRC_processing This refers to the delay associated with the RRC process (RRC processing delay). 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 The (NR slot length) is the same as the case of a known TCI state during the switching of TCI states using MAC CE.

[0154] 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 first time slot after (NR time slot length), receive the PDCCH of the serving cell whose TCI state has been switched.

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

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

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

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

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

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

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

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

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

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

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

[0166] • The timing offset between the serving cell and the cell that adds PCI is within the CP of the corresponding SCS.

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

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

[0169] • From the last transmission of the RS resource used for the L1-RSRP measurement report of the target DL TCI state until the completion of the switch to activate the DL TCI state, the RS resource used for L1-RSRP measurement is the RS of the target DL TCI state or the RS that is in a QCL relationship with the target DL TCI state.

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

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

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

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

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

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

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

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

[0178] In the handover of DL TCI state, MAC CE (MAC-CE-based downlink TCI state switch) is used, and if the target TCI state (the TCI state of the handover destination) is a known TCI state, and the UE receives an activation command (TCI state indication) PDSCH including the TCI state 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 (n+T) / (NR time slot length), the UE receives the Physical Downlink Control Channel (PDCCH) for the serving cell where the TCI state handover has occurred, indicating the target TCI state. Additionally, in time slot n+T... HARQ +3N subframe,μ slot Previously, the old (pre-handover) TCI state could be used 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 timeslot length), the TCI state applied by the UE is not specified.

[0179] Here, THARQ 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). N subframe,μ 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 The time is 2ms. If the target TCI state is not included in the list of active TCI states for PDSCH, TO k If it is 1, otherwise TO k It is 0. NR slot length indicates the length of the slot.

[0180] 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 (n / (NR time 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, the old (pre-switching) TCI state could be used to receive UE-specific PDSCH / PDCCH.

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

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

[0183] 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 received power measurement. In frequency range (FR) 1, or in FR2 when QCL type D is not set, T... L1-RSRP It is 0. Otherwise, it becomes the time required for the determination / refinement of the receive beam in FR2.

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

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

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

[0187] In the case of joint TCI state switching, the UE may not be expected to transmit in UL before completing the switching of DL and UL TCI states.

[0188] In the case of using MAC-CE (MAC-CE based uplink TCI state switch) for the handover of separate UL TCI states / joint TCI states for UL channels / signals, and the target TCI state (the TCI state of the handover destination) is a known TCI state, if the UE receives a PDSCH including an activation command (TCI state indication) in time slot n, it can be enabled 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), the UL signal of the target TCI state is transmitted. Here, the UL channel / signal can also be PUCCH, PUSCH, or a semi-persistent / periodic / aperiodic SRS when beamCorrespondenceWithoutUL-BeamSweeping is set to 1.

[0189] 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 including 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 time slot length), the UL signal of the target TCI state is transmitted.

[0190] 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). N subframe,μ slot This indicates the number of time slots per subframe for which μ is set for a subcarrier. NR slot length indicates the length of the time slot.

[0191] If the target PL-RS is maintained, NM is 1; otherwise, NM is 0.

[0192] When the target TCI state is unknown, T target-PL-RS This is the time from the L1-RSRP measurement until the initial path loss RS is transmitted. 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.

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

[0194] 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 is required during 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. Otherwise, it becomes the time required for the determination / refinement of the receive beam in FR2.

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

[0196] The UE is studying UL transmission 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.

[0197] <Scenario 1>

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

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

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

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

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

[0203] (5) Even in the case of multiple TRPs, the UE must always be covered by the serving cell. As with previous systems, the UE needs to use common channels from the serving cell (Broadcast Control Channel (BCCH), Paging Channel (PCH)), etc.

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

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

[0206] 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. To receive UE-common channels (e.g., system information / paging / SMS), the UE needs to be within the coverage area of ​​the serving cell. If the UE moves outside the coverage area of ​​the serving cell, a handover (also known as L3 mobility) is required.

[0207] <Scenario 2>

[0208] 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 arise where data communication is impossible 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.

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

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

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

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

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

[0214] In other words, in Scenario 2, the serving cell (the intended serving cell in the UE) is updated via L1 / L2 signaling. Scenario 2 can also be applied in Rel.18.

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

[0216] (Type of beam report)

[0217] <Intra-cell beam reporting in Rel. 15 / 16>

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

[0219] For example, in the calculation of L1-RSRP, when a resource is associated with QCL Type C / Type D, a UE may be configured with either or both of CSI-RS resources and SS / PBCH block resources.

[0220] Furthermore, a UE may be configured with a maximum of 16 CSI-RS resource sets, each set having a maximum of 64 resources. Across all resource sets, the total number of distinct CSI-RS resources is 128 or less.

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

[0222] Herein, the maximum measurement value of L1-RSRP is quantized to a 7-bit value within the range of [-140~-44]dBm with a step size of 1dB. Furthermore, the differential value of L1-RSRP is quantized to a 4-bit value.

[0223] The differential value is calculated with a step size of 2dB by referring to the maximum measurement value that is part of the same L1-RSRP reporting instance.

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

[0225] For channel measurement, a UE may be configured with a CSI resource configuration (setting) associated with a maximum of 16 CSI-RS resource sets, where the CSI-RS resource sets have a maximum of 64 CSI resources or SS / PBCH block resources.

[0226] In L1-SINR reporting, when the higher-layer parameter nrofReportedRS is configured to 1, the reported L1-SINR value is defined as a 7-bit value within the range of [-23~40]dBm with a step size of 0.5dB.

[0227] 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 shall use the L1-SINR values based on differential values for reporting.

[0228] The differential value is calculated with a step size of 1 dB by referring to the maximum measurement value that is part of the same L1-SINR reporting instance.

[0229] In the present disclosure, the intra-cell beam reporting in Rel. 15 / 16 (which may also be referred to as intra-cell beam reporting for short) may also be referred to as type 1 beam reporting (beam reporting type 1) or beam reporting for intra-cell beam switching.

[0230] <Inter-cell Beam Reporting in Rel. 17>

[0231] As mentioned above, in Rel. 17, L1 / L2 inter-cell mobility is supported. For example, a UE can transmit and receive UL / DL channels / signals with a cell having a PCI different from that of the serving cell. For example, if a non-serving cell has an RSRP greater than that of the serving cell, the UE can transmit and receive UL / DL channels / signals with the non-serving cell without performing handover.

[0232] In L1-RSRP reporting, the absolute / differential values of L1-RSRP can be used in the same manner as in Rel. 15 / 16. In inter-cell beam reporting in Rel. 17 (type 2-1 beam reporting described later), each L1-RSRP value is associated with a PCI ID (for serving cell / added cell / candidate cell). The association between L1-RSRP values and PCI IDs can be configured / indicated via higher-layer signaling / physical layer signaling.

[0233] Configuration based on higher-layer signaling supports a maximum of 7 additional cells. In addition, ID=0 indicates the PCI of the serving cell.

[0234] In the present disclosure, inter-cell beam reporting (in Rel. 17 / 18) may also be referred to as type 2 beam reporting (beam reporting type 2). Type 2 beam reporting can be further classified into type 2-1 and type 2-2, which will be described later.

[0235] In the present disclosure, the beam reporting in Rel. 17 may also be referred to as type 2-1 beam reporting or beam reporting for inter-cell beam switching.

[0236] <Inter-cell Beam Reporting in Rel. 18>

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

[0238] Regarding beam selection in the L1-RSRP report based on SSB, for M and L mentioned above, 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.

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

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

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

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

[0243] 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 SSBRIs of the configured candidate cells. The format can be the same as existing specifications.

[0244] 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 include PCI-related information (PCI ID). Instead, the SSBRI may include PCI-related information. For example, in the case of 4 cells with 64 SSBs, the SSBRI becomes any one of {0, 1, ..., 255}.

[0245] (Event-based beam reporting)

[0246] Research is underway to support event-based beamreporting in future wireless communication systems. Event-based beamreporting can also be called event-triggered beamreporting, or it can refer to beamreporting initiated by the UE.

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

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

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

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

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

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

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

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

[0255] Event B2: The PCell measurement result is worse than the first threshold, while 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.

[0256] <Applicable Scenarios>

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

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

[0259] • [Scenario 2]: Only L1-RSRP / SINR beam reports for the serving cell PCI are included.

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

[0261] Specific events may also be at least one of the following: 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.

[0262] Regarding the incident in scenario 1

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

[0264] [Option 1]

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

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

[0267] Figure 6This is a flowchart illustrating an example of event-based beam 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 S1 is yes (YES), the UE sends a non-periodic CSI report (and RRM report) (S2); if no (NO), the UE terminates the processing related to event-based beam reporting. Figure 6 The process can also be repeated at specific intervals.

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

[0269] In events A2 through 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 through A6 below, "poor" can also mean "low," and "good" can also mean "high." In the conditions of events A2 through 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 through A6 and I1 below, the parameter corresponding to hysteresis can also be added to / subtracted from the measurement result. The thresholds can be the same or different. Neighboring cells can also be non-serving cells.

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

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

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

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

[0274] Event A6: 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 the serving cell (Secondary Cell (SCell)) (the value obtained by adding an offset to the measurement results).

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

[0276] Option 1 allows the RRM report triggering to be reused in the beam report triggering, making setup easier.

[0277] [Option 2]

[0278] One or more new (separate) events, distinct from those used in RRM reporting, can also be defined to trigger aperiodic L1 beam reporting (CSI reporting). These events are similar to those described above, 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 (RRM reporting triggers) in at least one of the following options 2-1 through 2-4.

[0279] [[Option 2-1]]

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

[0281] [[Option 2-2]]

[0282] The event can also occur based on the measurement of the reference signal received power (L1-RSRP) in Layer 1. That is, a comparison can be made based on L1-RSRP instead of L3-RSRP. Alternatively, a 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. Alternatively, other metrics such as L1-SINR, L3-RSRQ, etc., can be applied. For example, the following event A2' can also be applied as a new event:

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

[0284] [[Options 2-3]]

[0285] 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 a cell level. For example, the following event A4' or event A4'' can also be applied:

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

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

[0288] [[Options 2-4]]

[0289] 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, the UE can also report a CSI if X beams meet event A4' (if the measurement results of X beams from neighboring cells are better than a threshold).

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

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

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

[0293] Option 2 allows for faster CSI reporting compared to using existing RRM reporting methods that leverage RRC.

[0294] [Option 3]

[0295] You can also use any combination of two or more events from Options 1 and 2 above to trigger a non-periodic L1 beam report (CSI report).

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

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

[0298] Regarding the incident in scenario 2

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

[0300] One or more new (independent) events, different from those used in RRM reporting, can also be defined to trigger non-periodic L1 beam reporting (CSI reporting). This event can also be at least one of the following events: B2 through B6 and K1:

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

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

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

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

[0305] 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 value obtained by adding an offset to the measurement result).

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

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

[0308] Furthermore, for at least one of the events in this disclosure (the events involved in Situation 1 / Situation 2), a duration / counter for the event (condition) to be met can also be specified. If at least one of the conditions for each of the above events satisfies a condition associated with a specific duration / counter, the UE / NW can also determine that the condition for each event is met. For example, if, within a 100ms time window, the measurement results of other beams are better than the measurement results of the current beam, the UE can also determine that the condition for event B3 above is met. Furthermore, 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 can also determine that the condition for event B3 above is met.

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

[0310] The PDCCH can also be, for example, the PDCCH corresponding to a CORESET that is 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.

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

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

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

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

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

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

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

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

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

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

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

[0322] The cell handover command sent via MAC CE may include at least the following information.

[0323] Information used to identify target cells

[0324] Information related to advance timing (TA),

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

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

[0327] Regarding the existence of beam indication in cell handover commands, at least for a certain scenario, the following can be supported.

[0328] • In cell handover commands, there is always a field that represents a joint TCI status index for the target cell or a set of DL / UL TCI status indices for the target cell.

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

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

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

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

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

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

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

[0336] 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 UE can either be predefined to prioritize a particular event (which UE feature), or it can be set / indicated to prioritize a particular event (which UE feature) via higher-layer signaling / physical layer signaling.

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

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

[0339] <Beaming Report for MIMO>

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

[0341] · MAC CE in PUSCH.

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

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

[0344] 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, for example.

[0345] • SSBRI / CRI.

[0346] • Number of beams reported X.

[0347] • Selection method for X beams.

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

[0349] When MAC CE is used

[0350] • An indicator that indicates whether to include the next octet.

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

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

[0353] <Beaming Report for Mobility>

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

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

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

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

[0358] When measurement reports are used in cell handover reports, in addition to including MIMO-related information,

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

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

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

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

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

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

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

[0366] <Definitions of terms for specific events>

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

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

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

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

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

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

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

[0374] (analyze)

[0375] Following Rel.19, research is underway to support event-based beam reporting (UE-initiated beam reporting, hereinafter referred to as UEIBR). UEIBR can be used for measurement reporting, beam handover, cell handover, etc.

[0376] For example, when the UE moves at a non-linear speed, the NW has difficulty accurately predicting the UE's movement (position change). In addition, scenarios where potential beam switching occurs frequently are also envisioned.

[0377] In such a scenario, when utilizing existing CSI reports (CSI reports scheduled by the NW), consider whether the NW sets the CSI reporting cycle to be shorter or longer.

[0378] For example, in cases of frequent beam switching (where the UE moves quickly or the beam quality varies greatly), the NW can set periodic CSI reports with a relatively short periodicity.

[0379] On the other hand, if beam switching does not occur frequently (rarely) (the UE moves slowly / the beam quality varies little), the NW can set periodic CSI reports with a relatively long periodicity.

[0380] However, existing CSI reports alone cannot adequately address all scenarios. For example, in non-periodic situations, from an efficiency standpoint, handover based on RRC reporting settings is not ideal, as mentioned above, and it is currently considered difficult for NW to predict [sharp] speed changes of UEs.

[0381] Therefore, we are investigating scenarios where the UE supports both the existing CSI report and UEIBR (Alt1 / Alt2), or where the UE only supports UEIBR (Alt3). The contents of Alt1 to Alt3 can be used to illustrate the following.

[0382] (Alt1)

[0383] The UE can support both the existing CSI reports and UEIBR with a short periodicity. In this case, real-time reporting (beam reports applicable to the aforementioned scenarios of frequent beam switching (where the UE moves quickly / beam quality varies greatly)) can be achieved through the existing CSI reports.

[0384] (Alt2)

[0385] The UE can support both existing CSI reports and UEIBR for longer periods. In this case, real-time reporting (as described above) can be achieved through UEIBR. Furthermore, occasional beam switching can be achieved through existing CSI reports.

[0386] In addition, UEIBR can be sent periodically multiple times during periods when certain conditions are met.

[0387] (Alt3)

[0388] The UE may only support UEIBR. For example, in UEIBR, there are multiple event types that can be satisfied in low-speed / high-speed scenarios. In this case, it is envisioned that the UE operation will differ after each event (condition) is satisfied. That is, the subsequent UE operation can vary depending on the type of event satisfied. For example, during the period when a certain condition is satisfied, the UE may send a beam report once or periodically multiple times.

[0389] According to UEIBR, real-time reporting can be achieved for specific use cases.

[0390] In this way, it is considered preferable to make flexible use of UEIBR in addition to the existing CSI report, thereby realizing beam reporting to cope with more use cases.

[0391] However, even if the UE simply combines the existing CSI report and UEIBR and supports both, such as Figure 7 As shown, there may also be instances where existing CSI reports overlap with event-based beamforming reports (UEIBR).

[0392] More specifically, in Figure 7 The example illustrates a scenario where the UE sends multiple CSI reports at a certain period based on existing CSI report settings.

[0393] like Figure 7 As shown, if an event is met at a certain time (the condition (trigger condition) of UEIBR is met), the UE can send UEIBR once or multiple times during the period when the event (condition) is met.

[0394] Here, we assume that the period (timing) of the existing CSI report overlaps with the period during which the event (condition) is met. In this case, the UE sends not only the UEIBR but also the existing CSI report, which could become a cause of communication overhead. That is, we assume that the existing CSI report is not needed during the period when the event is met.

[0395] In cases like this, if the regulations supporting existing CSI reports and UEIBR are unclear, lower latency communication cannot be achieved, raising concerns that this could inhibit improvements in communication quality / throughput.

[0396] In other words, in order to effectively enjoy the advantages of existing CSI reports and UEIBR, it is necessary to explicitly support the provisions for both (e.g., the simultaneous setting of existing CSI reports and UEIBR).

[0397] Therefore, in order to provide balanced support for existing CSI reporting and UEIBR, the inventors of this invention have devised a new wireless communication method as shown below.

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

[0399] (Various rewrites)

[0400] In this disclosure, terms enclosed in parentheses "()" may 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 "[]" may or may not be included in the interpretation of the entire article. Additionally, "()" and "[]" may also be used for purposes / meanings other than those listed above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0429] In this disclosure, the RS index and the L1-RSRP / SINR pair may be referred to as an L1 measurement report. That is, an L1 measurement report may include the RS index and the L1-RSRP / SINR pair.

[0430] The content of this disclosure can also be applied to existing CSI reports.

[0431] In this disclosure, reporting criteria, criteria, time / space domain filters, domain filters, etc., can be rewritten in different ways.

[0432] In this disclosure, candidate communities, target communities, neighboring communities, communities, etc., can be interchanged.

[0433] In this disclosure, the occurrence of an event and the fulfillment of the conditions for the event can be rewritten.

[0434] In this disclosure, beam, RS, and [L1 / L3] measurement results can be rewritten from one another.

[0435] In this disclosure, the RS being measured can be an active TCI state / QCL source RS indicating the TCI state.

[0436] In this disclosure, spatial domain filters, time domain filters, and domain filters can be rewritten in relation to each other.

[0437] In this disclosure, filtering at the cell level (each cell) can also refer to a spatial domain filter. Filtering at the beam level (each beam) can also refer to a time / spatial domain filter.

[0438] In this disclosure, NW / BS / gNB can be interchanged.

[0439] (Wireless communication method)

[0440] The embodiments disclosed herein can be broadly categorized as follows, in cases that support both existing CSI reports and UEIBR.

[0441] • Zero Implementation: Number of reports (number of reports) from UEIBR.

[0442] • First implementation: Conditions (timing requirements) for CSI reporting / beam reporting.

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

[0444] The UE can apply the various implementation methods described later to perform beam report / CSI 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 necessary controls in order to receive the beam report / CSI report from the UE.

[0445] The event-based beam reporting disclosed herein can be applied in any scenario for MIMO / mobility oriented toward Rel.19 and beyond.

[0446] In this disclosure, CSI reports and beam reports can be rewritten from each other.

[0447] In this disclosure, [for Rel.19] event-based beam reports, event-triggered beam reports, UE-triggered beam reports, UE-initiated beam reports (UEIBR), and beam reports can be overridden with each other.

[0448] In this disclosure, "existing CSI report" may refer to a CSI report (beam report) other than the aforementioned event-based beam report.

[0449] In this disclosure, existing CSI reports and CSI reports (beam reports) scheduled by NW can be rewritten to each other.

[0450] Furthermore, in this disclosure, the existing CSI report (beam report) may also be referred to as the first CSI report / beam report. In contrast, event-based beam reports (UEIBR, etc.) for Rel.19 and later may also be referred to as the second CSI report / beam report, or the new CSI report / beam report.

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

[0452] <Implementation Method Zero>

[0453] In the zeroth embodiment, the number of UEIBR reports (report counts) is explained when both existing CSI reports and UEIBR are supported.

[0454] As described above, in this disclosure, the UE can support both existing CSI reporting and UEIBR. That is, the UE can be configured with both existing CSI reporting and UEIBR simultaneously.

[0455] The UE can report / send one (single) or multiple (multiple) beam reports according to any of the scenarios 1 to 2 shown below. The number of beam reports can be set / indicated by higher-layer signaling / physical layer signaling, defined in advance by specifications, or determined by the UE's capabilities.

[0456] In this disclosure, a single beam report and a single beam report can be overwritten with each other. Furthermore, multiple beam reports and multiple beam reports can be overwritten with each other.

[0457] <<Scenario 1>>

[0458] After the event / condition for UEIBR is met, the UE can report / send a beam report (UEIBR). In other words, after the event / condition for UEIBR is met, the UE can report / send a beam report (UEIBR) only once.

[0459] <<Scenario 2>>

[0460] After the event / condition for UEIBR is met, the UE can report / send multiple beam reports (UEIBR) [at different times / timings]. In other words, after the event / condition for UEIBR is met, the UE reports / sends beam reports (UEIBR) multiple times.

[0461] Some parameters of beam reporting (such as period, offset, etc.) can be set via higher-level signaling.

[0462] (Conditions for beam)

[0463] For beam reports (UEIBR) that are reported / transmitted multiple times at specific times (timing), the beam of the reporting / transmission object at each time can follow at least one of Opt1 to Opt2 below.

[0464] <opt1>

[0465] One or more beams may be included in each beam report (beam reports reported at various times / each beam report). The quality of each beam (e.g., L1-RSRP / SINR) may be different.

[0466] According to option 1, the NW can continuously monitor (continue to monitor) changes in the quality of a specific beam (one or more identical beams) for an event that has been met. That is, the NW can determine the appropriate cell / beam for mobility / beam management.

[0467] <opt2>

[0468] The beams included in each beam report (beam report reported at each time / each beam report) may be different. The quality of each beam (e.g., L1-RSRP / SINR) may be different.

[0469] According to option 2, NW is able to continuously monitor (continue to monitor) changes (variations) of beams (one or more) that meet the event.

[0470] For example, if a new beam satisfies an event, the UE sends an additional UL channel / signal (beam report) to the NW. By receiving this additional UL channel / signal (beam report), the NW can identify whether the beam of the monitored object is a stable beam or a new beam.

[0471] In this scenario, NW can envision that a beam report is sent from the UE after the event is satisfied.

[0472] (Method for distinguishing between single-beam reports and multiple-beam reports)

[0473] As a method for distinguishing between one-beam reports and multiple-beam reports for UEIBR, at least one of the following Opt1 to Opt2 can be applied.

[0474] <opt1>

[0475] For UEIBR, NW can decide whether to apply / support one beam report or multiple beam reports.

[0476] Whether to apply / support one or more beam reports can be set / indicated by higher-layer signaling / physical layer signaling, defined in advance by specifications, or determined by UE capabilities.

[0477] < <opt1-1>>

[0478] For example, any of the aforementioned signaling (DL signals) could include a 1-bit flag (bit field) indicating the number (times) of beam reports. For instance, a bit value of "0" could indicate one (single) beam report, while a bit value of "1" could indicate multiple (multiple) beam reports. Alternatively, the correspondence between bit values ​​and the number of reports (times) could be reversed.

[0479] The number of beam reports can be set / indicated by higher-layer signaling / physical layer signaling, defined in advance by specifications, or determined by UE capabilities.

[0480] < <opt1-2>>

[0481] For example, any of the above signaling (DL signals) may include the number of beam reports [related information]. For example, "1" may mean one (single) beam report, and "3" may mean three (three) beam reports.

[0482] Additionally, if the cancellation conditions are met before the set number of reports is reached, the UE can suspend beam reporting.

[0483] In Opt1, the specific time (e.g., X symbol / time slot / millisecond) at which a UE can send multiple beam reports can be set / indicated by higher-layer signaling / physical layer signaling, defined in advance by the specification, or determined by the UE's capabilities.

[0484] In Opt1, the maximum number of beam reports that a UE can send can be set / indicated by higher-layer signaling / physical layer signaling, defined in advance by the specification, or determined by the UE's capabilities.

[0485] <opt2>

[0486] For UEIBR, the UE can decide whether to apply / support one beam report or multiple beam reports.

[0487] For example, the UE may include a 1-bit flag (bit field) representing the number (number) of beam reports, or the number (number) of beam reports, in any DL signal (e.g., beam reports).

[0488] Furthermore, whether to apply / support one or multiple beam reports can be determined based on the UE implementation.

[0489] <<Variation Example 1>>

[0490] Whether to apply either scenario 1 or scenario 2 above, i.e., whether to prioritize one or more UEIBRs, can be determined by the UE based on the frequency of beam switching, etc.

[0491] For example, if beam switching does not occur frequently (rarely) (the UE moves slowly / the beam quality varies little), the UE can apply the operation in case 1 and send one (once) UEIBR when the UEIBR event is satisfied.

[0492] Alternatively, if frequent beam switching occurs (the UE moves quickly / the beam quality varies greatly), the UE can apply the operation in scenario 2 to send multiple (multiple) UEIBRs when the UEIBR event is satisfied.

[0493] Therefore, the UE can appropriately control the number (number) of UEIBRs according to the frequency of beam switching.

[0494] <<Variation Example 2>>

[0495] This disclosure describes the scenario where a UE transmits multiple UEIBRs at different times, but it is not limited to this. For example, a UE can also perform FDM on multiple UEIBRs and transmit them in a timed set.

[0496] According to this implementation, the UE can support both existing CSI reports and UEIBR, and appropriately control the number of UEIBR reports.

[0497] <First Implementation Method>

[0498] In the first embodiment, the conditions (period requirements) for CSI reporting / beam reporting in the case of supporting both existing CSI reporting and UEIBR will be described. Each of the above cases (case 1 / case 2) will be described below.

[0499] The UE can control beam reporting by following the conditions shown below.

[0500] <<Scenario 1>>

[0501] Figure 8 This is a diagram illustrating an example of beam reporting according to the first embodiment (corresponding to case 1).

[0502] In Case 1 (for UEIBR, the case that supports one (single) beam report), at least one of Opt1 to Opt3 below can be applied.

[0503] (Opt1)

[0504] The UE will not send existing CSI reports within a certain time after sending the UEIBR (see reference). Figure 8 (The dashed part). That is, in Opt1, UEIBR can be prioritized. A specific time can be, for example, X symbol / slot / millisecond.

[0505] A window / time / timer representing a specific time can start at at least one of the following timings.

[0506] • After the specific event (triggering condition) for UEIBR is met (see reference) Figure 8 ).

[0507] • After receiving the ACK [from NW] for UEIBR.

[0508] • After a specific time following the execution of a specific operation / UL transmission / DL reception.

[0509] The control of this window / time / timer can be performed by the UE.

[0510] Opt1 can also be referred to as the non-sendable condition for existing CSI reports, or the condition prioritizing UEIBR.

[0511] (Opt2)

[0512] The UE will not send a UEIBR within a specific time period after sending an existing CSI report, even if a specific event (triggering condition) for the UEIBR is met (see reference). Figure 8 (The dashed section). That is, in Opt2, existing CSI reports can be prioritized. A specific time can be, for example, X symbol / slot / millisecond.

[0513] A window / time / timer representing a specific time can start at at least one of the following timings.

[0514] • After the existing CSI report is sent.

[0515] • After a specific time following the execution of a specific operation / UL transmission / DL reception.

[0516] The control of this window / time / timer can be performed by the UE.

[0517] Opt2 can also be referred to as the non-transmission condition for UEIBR, or the condition that prioritizes existing CSI reports.

[0518] (Opt3)

[0519] Within a specific timeframe (a specific window) from the time an existing CSI report is sent until the time of the next existing CSI report, the UE is able to send a UEIBR (refer to...). Figure 8 (The solid line portion).

[0520] This window can be set / indicated via higher-layer signaling / physical layer signaling. It can consist of time, offset, length, etc.

[0521] This window can be set in relation to the period / offset of existing CSI reports. For example, the window can be set between two existing CSI reports, excluding specific times before and after each existing CSI report. That is, the window can be set in a time period that does not overlap with the timing of two consecutive existing CSI reports.

[0522] Opt3 can also be referred to as the transmittable condition for UEIBR.

[0523] (Note)

[0524] The "specific time" in Opt1~Opt3 can be maintained by a timer in the MAC, set by higher-level parameters, predefined by the specification, or determined by the UE's capabilities.

[0525] Specific time periods can be set for each CC / BWP / UE / cell / report.

[0526] Updates can be made at specific times via higher-level signaling / physical-level signaling.

[0527] A specific time can be set to a variety of (different) values.

[0528] (Modified example)

[0529] Whether to apply either Opt1 or Opt2, i.e., whether to prioritize either UEIBR or existing CSI reports, can be determined by the UE based on whether there are any existing CSI reports recently.

[0530] For example, if a specific event for the UEIBR is met, and an existing CSI report was sent within the most recent specific time period before the specific event was met, the UE can apply Opt1.

[0531] Alternatively, if a specific event for the UEIBR is met, and no existing CSI report has been sent within the most recent specific time period prior to the meeting of that specific event (or if no existing CSI report has been sent for a while within the most recent specific time period), then the UE may apply Opt2.

[0532] Therefore, the UE can perform beam reporting separately at appropriate timings, provided that the existing CSI report and UEIBR do not overlap.

[0533] In addition, the aforementioned "recent specific time" can be, for example, Y symbol / time slot / millisecond, which can be set / indicated by higher layer signaling / physical layer signaling, defined in advance by specifications, or determined by UE capabilities.

[0534] <<Scenario 2>>

[0535] Figure 9 This is a diagram illustrating an example of beam reporting in the first embodiment (corresponding to case 2).

[0536] In Case 2 (for UEIBR, the case that supports multiple (multiple) beam reports), at least one of Opt1 to Opt4 below can be applied.

[0537] (Opt1)

[0538] Within a certain time after sending the UEIBR, the UE will not send the existing CSI report (see reference). Figure 9 (The dashed part). That is, in Opt1, UEIBR can be prioritized. A specific time can be, for example, X symbol / slot / millisecond.

[0539] A window / time / timer representing a specific time can start at at least one of the following timings.

[0540] • After the specific event (triggering condition) for UEIBR is met (see reference) Figure 9 ).

[0541] • After receiving the ACK [from NW] for UEIBR.

[0542] • After a specific time following the execution of a specific operation / UL transmission / DL reception.

[0543] The control of this window / time / timer can be performed by the UE.

[0544] Opt1 can also be referred to as the non-sendable condition for existing CSI reports, or the condition prioritizing UEIBR.

[0545] (Opt2)

[0546] After the UEIBR is sent, and before the cancellation conditions are met (during the period until the cancellation conditions are met), the UE does not send existing CSI reports (refer to...). Figure 9 (The dashed part). That is, in Opt2, UEIBR can be given priority.

[0547] The start timing for the window / time / timer that does not send existing CSI reports can be the same as Opt1 above.

[0548] • After the specific event (triggering condition) for UEIBR is met (see reference) Figure 9 ).

[0549] • After receiving the ACK [from NW] for UEIBR.

[0550] • After a specific time following the execution of a specific operation / UL transmission / DL reception.

[0551] The end timing of not sending an existing CSI report window / time / timer can be at least one of the following.

[0552] • After the cancellation conditions of UEIBR are met (refer to...) Figure 9 ).

[0553] • From the last transmission (UEIBR / existing CSI report), before a specific time has elapsed.

[0554] • After the final transmission (UEIBR / existing CSI report).

[0555] (Opt3)

[0556] Within a specific timeframe following the sending of an existing CSI report, the UE will not send a UEIBR even if a specific event (triggering condition) for the UEIBR is met (see reference). Figure 9 (The dashed section). That is, in Opt3, existing CSI reports can be prioritized. A specific time can be, for example, X symbol / slot / millisecond.

[0557] A window / time / timer representing a specific time can start at at least one of the following timings.

[0558] • After the existing CSI report is sent.

[0559] • After a specific time following the execution of a specific operation / UL transmission / DL reception.

[0560] The control of this window / time / timer can be performed by the UE.

[0561] Opt3 can also be referred to as the untransmittable condition for UEIBR, or the condition that prioritizes existing CSI reports.

[0562] (Opt4)

[0563] Within a specific timeframe (a specific window) from the time an existing CSI report is sent until the time of the next existing CSI report, the UE is able to send a UEIBR (refer to...). Figure 9 (The solid line portion).

[0564] This window can be set / indicated via higher-layer signaling / physical layer signaling. It can consist of time, offset, length, etc.

[0565] This window can be set in relation to the period / offset of existing CSI reports. For example, the window can be set between two existing CSI reports, excluding specific times before and after each existing CSI report. That is, the window can be set in a time period that does not overlap with the timing of two consecutive existing CSI reports.

[0566] Opt4 can also be referred to as the transmittable condition for UEIBR.

[0567] (Note)

[0568] The "specific time" in Opt1~Opt4 can be maintained by a timer in the MAC, set by higher-level parameters, predefined by the specification, or determined by the UE's capabilities.

[0569] Specific time periods can be set for each CC / BWP / UE / cell / report.

[0570] Updates can be made at specific times via higher-level signaling / physical-level signaling.

[0571] A specific time can be set to a variety of (different) values.

[0572] In this disclosure, existing CSI reports can be periodic / non-periodic / semi-persistent CSI reports for beam management / LMT.

[0573] This implementation can be applied to each CC / BWP, taking into account the case of carrier aggregation (CA).

[0574] (Modified example)

[0575] Whether to apply any of Opt1 to Opt3 above, that is, whether to prioritize any of the UEIBR / existing CSI reports, can be determined by the UE based on whether there is an existing CSI report recently.

[0576] For example, if a specific event for the UEIBR is met, and an existing CSI report was sent within the most recent specific time period before the specific event was met, the UE can apply Opt1 / Opt2.

[0577] Alternatively, if a specific event for the UEIBR is met, and no existing CSI report has been sent within the most recent specific time period prior to the meeting of that specific event (or if no existing CSI report has been sent for a while within the most recent specific time period), then the UE may apply Opt3.

[0578] Therefore, the UE can perform beam reporting separately at appropriate timings, provided that the existing CSI report and UEIBR do not overlap.

[0579] In addition, the aforementioned "recent specific time" can be, for example, Y symbol / time slot / millisecond, which can be set / indicated by higher layer signaling / physical layer signaling, defined in advance by specifications, or determined by UE capabilities.

[0580] According to this implementation, the UE can support both existing CSI reports and UEIBR, and control the reporting at appropriate timings when the two do not overlap.

[0581] <Supplement>

[0582] <<Information Notification to UE>>

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

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

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

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

[0587] <<Notifications from UE>>

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

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

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

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

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

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

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

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

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

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

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

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

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

[0601] • Supports event-triggered beam reporting.

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

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

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

[0605] • Supports combinations of events.

[0606] • Supports parameters related to the trigger / cancellation conditions corresponding to the combination of events.

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

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

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

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

[0611] (Postscript)

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

[0613] [Postscript 1]

[0614] A terminal having:

[0615] The receiving unit receives the settings for Channel State Information (CSI) reports scheduled by the base station, and the settings for UE-initiated Beam Reports (UEIBRs); and

[0616] The control unit, in supporting both the CSI report and the UEIBR, controls the transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied.

[0617] [Postscript 2]

[0618] As described in Appendix 1, in the case of the control unit sending the plurality of UEIBRs, each beam report includes one or more beams that may be the same or different.

[0619] [Postscript 3]

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

[0621] The receiving unit receives information related to the number of reports from the UEIBR.

[0622] The control unit determines the number of reports from the UEIBR based on the information.

[0623] [Postscript 4]

[0624] The terminal as described in any one of Annexes 1 to 3, wherein the control unit controls the number of reports of the UEIBR based on the frequency of beam switching.

[0625] (Postscript)

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

[0627] [Postscript 1]

[0628] A terminal includes: a receiving unit that receives settings for Channel State Information (CSI) reports scheduled by a base station and settings for UE-initiated Beam Reports (UEIBRs); and

[0629] The control unit, supporting both the CSI report and the UEIBR, controls the transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied.

[0630] The control unit controls the timing of sending the CSI report and the UEIBR based on specific conditions.

[0631] [Postscript 2]

[0632] As described in Appendix 1, the terminal control unit controls itself to not send the CSI report for a specific period of time after sending the UEIBR.

[0633] [Postscript 3]

[0634] As described in Appendix 1 or Appendix 2, the terminal control unit controls itself to not send the UEIBR within a specific time period after sending the CSI report.

[0635] [Postscript 4]

[0636] The terminal as described in any one of Annexes 1 to 3, wherein the control unit controls the transmission of the UEIBR within a specific time period from the transmission of the CSI report to the transmission of the next CSI report.

[0637] (Wireless communication system)

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

[0639] Figure 10 This 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0660] 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", "CORESET setting" etc. disclosed herein can be rewritten interchangeably.

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

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

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

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

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

[0666] (Base station)

[0667] Figure 11 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.

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

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

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

[0671] 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 a transmitter / receiver, RF circuitry, baseband circuitry, filters, phase shifters, measurement circuitry, transmitting / receiving circuitry, etc., as described based on common knowledge in the art to which this disclosure pertains.

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

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

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

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

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

[0677] The transmitting and receiving unit 120 (transmitting processing unit 1211) can also perform transmission processing such as channel coding (including 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.

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

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

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

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

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

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

[0684] Additionally, base station 10 can be divided 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 implement PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer functions.

[0685] 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 and are interconnected. In this disclosure, base station 10 may also be rewritten in relation to RU / DU / CU.

[0686] Additionally, the transmit / receive unit 120 can transmit settings for Channel State Information (CSI) reports and settings for UE-initiated Beam Reports (UEIBRs). The control unit 110 can, in support of both the CSI reports and the UEIBRs, control the reception of one or more UEIBRs transmitted from the terminal after a specific event for the UEIBR is satisfied.

[0687] The control unit 110 can control the transmission of specific conditions, which are used to control the transmission timing of the CSI report and the UEIBR.

[0688] (User terminal)

[0689] Figure 12 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.

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

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

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

[0693] 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 a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common knowledge in the art to which this disclosure pertains.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0707] Additionally, the transmit / receive unit 220 can receive settings for Channel State Information (CSI) reports scheduled by the base station and settings for UE-initiated beam reports (UEIBRs). The control unit 210 can control the transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied, provided that both the CSI reports and the UEIBRs are supported. When transmitting multiple UEIBRs, the control unit 210 can include one or more beams in each beam report, which may be the same or different. The transmit / receive unit 220 can receive information related to the number of UEIBR reports. The control unit 210 can determine the number of UEIBR reports based on this information. The control unit 210 can control the number of UEIBR reports based on the beam switching frequency.

[0708] Control unit 210 can control the timing of sending the CSI report and the UEIBR based on specific conditions. Control unit 210 can control the transmission of the CSI report to not be sent within a specific time period after the UEIBR is sent. Control unit 210 can control the transmission of the UEIBR to not be sent within a specific time period after the CSI report is sent. Control unit 210 can control the transmission of the UEIBR to be sent within a specific time period from the time the CSI report is sent until the next CSI report is sent.

[0709] (Hardware structure)

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

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

[0712] 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 13 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, etc.

[0713] 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 to exclude some of the apparatuses.

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

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

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

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

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

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

[0720] 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 transmitting and receiving unit 120 (220) and transmitting and receiving antenna 130 (230) may also be implemented by the communication device 1004. The transmitting and receiving unit 120 (220) may also be implemented by physically or logically separating the transmitting unit 120a (220a) and the receiving unit 120b (220b).

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

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

[0723] Furthermore, the base station 10 and the user terminal 20 can also be configured with hardware including a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), a field-programmable gate array (FPGA), etc., 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.

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

[0725] (Modified example)

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

[0727] A radio frame can also be composed of one or more periods (frames) in the time domain. Each of these periods (frames) that constitute a radio frame can also be called a subframe. Furthermore, a subframe can also be composed of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

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

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

[0730] A time slot can also comprise 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.

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

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

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

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

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

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

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

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

[0739] Furthermore, an RB can also include one or more symbols in the time domain, or it can 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.

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

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

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

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

[0744] 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. In addition, "cell", "carrier", etc. in this disclosure may be rewritten as "BWP".

[0745] 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 included in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots included in a time slot, the number of symbols and RBs included in a time slot or mini-time slot, the number of subcarriers included in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

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

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

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

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

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

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

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

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

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

[0755] 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 comparison of values ​​(e.g., by comparison with a specific value).

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

[0757] 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 transmission medium.

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

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

[0760] 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 may also include time / frequency / code / space / power resources. Moreover, the spatial domain transmission filter may include at least one of a spatial domain transmission filter and a spatial domain reception filter.

[0761] The aforementioned groups may also 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.

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

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

[0764] Furthermore, in this disclosure, "QCL", "QCL concept", "QCL relationship", "QCL type information", "QCL property (QCLproperty / properties)", "specific QCL type (e.g., type A, type D) property", "specific QCL type (e.g., type A, type D)" can also be rewritten in different ways.

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

[0766] 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)" or "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.

[0767] 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 macrocell, small cell, femtocell, and picocell are used to refer to a base station.

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

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

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

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

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

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

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

[0775] Figure 14 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.

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

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

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

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

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

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

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

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

[0784] 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 include information based on the aforementioned inputs.

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

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

[0787] 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 that replace communication between the base station and the user terminal with 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 also 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.

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

[0789] 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 comprising 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.

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

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

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

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

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

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

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

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

[0798] In this disclosure, "expect" can also be interchanged with "be expected." For example, "expect(s) ..." (which can also be expressed using a that clause, a to infinitive, etc.) can be interchanged with "be expected ..." and "... (in the case of the above "..." being a to infinitive, the verb after removing to)." Similarly, "does not expect ..." can be interchanged with "be not expected ..." and "not ... (in the case of the above "..." being 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 can also be a base station).

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

[0800] As used in this disclosure, the terms "connected," "coupled," or any 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, "connected" can also be rewritten as "access."

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

[0802] 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 different from C respectively". Terms such as "separate" and "combined" can also be interpreted in the same way as "different".

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

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

[0805] In this disclosure, words such as "below," "less than," "above," "more," and "equal to" can be interchanged. Furthermore, in this disclosure, words meaning "good," "bad," "large," "small," "high," "low," "early," "slow," "wide," and "narrow" 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" are used as expressions with "i" appended (i being any integer), and 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").

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

[0807] 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 zero (immediately following or immediately preceding). Moreover, a time offset can be applied to the time when A occurs. For example, "A" can also be interchanged 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.

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

[0809] 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 the settings for the Channel State Information (CSI) report scheduled by the base station and the settings for the UE-initiated Beam Report (UEIBR); and The control unit, in supporting both the CSI report and the UEIBR, controls the transmission of one or more UEIBRs after a specific event for the UEIBR is satisfied.

2. The terminal as described in claim 1, wherein, When the control unit sends the plurality of UEIBRs, each beam report includes one or more beams that may be the same or different.

3. The terminal as described in claim 1, wherein, The receiving unit receives information related to the number of reports from the UEIBR. The control unit determines the number of reports from the UEIBR based on the information.

4. The terminal as described in claim 1, wherein, The control unit controls the number of reports from the UEIBR based on the frequency of beam switching.

5. A wireless communication method for a terminal, comprising: The steps for receiving Channel State Information (CSI) reports scheduled by the base station and setting up the UE-initiated Beam Report (UEIBR); and In the case of supporting both the CSI report and the UEIBR, the steps of controlling the transmission of one or more UEIBRs after satisfying a specific event for the UEIBR.

6. A base station, comprising: The transmission unit is responsible for setting the Channel State Information (CSI) report and the UE-initiated Beam Report (UEIBR); and... The control unit, in supporting both the CSI report and the UEIBR, controls the reception of one or more UEIBRs sent from the terminal after a specific event for the UEIBR is satisfied.

Images