Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a control unit that determines a trigger for an event-based beam report for multi-input multi-output (MIMO) operation; and a transmission unit that transmits beam report information relating to the event-based beam report in a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH). The one aspect of the present disclosure makes it possible to improve communication quality / throughput.

Description

Terminal, wireless communication method and base station

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

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

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

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

[0005] In future wireless communication systems (e.g., NR), the introduction of UE-initiated / event-driven beam management initiated by the terminal (user terminal, User Equipment (UE)) is being considered from the perspective of reducing overhead / delay.

[0006] However, detailed consideration of such beam management has not been sufficiently carried out, which may result in a lack of realization of lower latency communications, and may lead to a suppression of improvements in communication quality / throughput.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput.

[0008] A terminal according to one aspect of the present disclosure has a control unit that determines a trigger for an event-based beam report for multi-input multi-output (MIMO) operation, and a transmission unit that transmits beam report information regarding the event-based beam report on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH).

[0009] According to one aspect of the present disclosure, communication quality / throughput can be improved.

[0010] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of a DCI-based TCI state indication. Figure 3 shows an example of a timeline for switching / activating TCI states defined up to Rel. 15 / 16. Figure 4 shows an example of TCI states defined up to Rel. 16. Figure 5A shows an example of UE movement in Rel. 17. Figure 5B shows an example of UE movement in Rel. 18. Figure 6 is a flowchart showing an example of event-based beam reporting processing. Figure 7 shows an example of a beam report according to the first embodiment. Figure 8 shows an example of starting a timer related to retransmission of a beam report according to the first embodiment. Figure 9 shows an example of stopping a timer related to retransmission of a beam report according to the first embodiment. Figure 10 shows another example of stopping a timer related to retransmission of a beam report according to the first embodiment. Figure 11 shows a first example of a MAC CE used for CSI reporting. FIG. 12 is a diagram showing a second example of a MAC CE used for CSI reporting. FIG. 13 is a diagram showing a third example of a MAC CE used for CSI reporting. FIG. 14 is a diagram showing a fourth example of a MAC CE used for CSI reporting. FIG. 15 is a diagram showing a fifth example of a MAC CE used for CSI reporting. FIG. 16 is a diagram showing a sixth example of a MAC CE used for CSI reporting. FIG. 17 is a diagram showing a seventh example of a MAC CE used for CSI reporting. FIG. 18 is a diagram showing an eighth example of a MAC CE used for CSI reporting. FIG. 19 is a diagram showing an example of a CG PUSCH according to Option 3-A. FIG. 20 is a diagram showing an example of a CG PUSCH according to Option 3-B. FIG. 21 is a diagram showing an example of transmission of beam report information according to Option 4-5. FIG. 22 is a diagram showing an example of transmission of beam report information according to Option 4-6. FIG. 23 is a diagram showing an example of transmission of beam report information according to Option 4-7. Fig. 24 is a diagram showing an example of transmission of beam report information according to options 4-8. Fig. 25A and Fig. 25B are diagrams showing SR selection and association of SR with SSB according to a variation of the fourth embodiment. Fig. 26 is a diagram showing an example of starting a timer for retransmission of a beam report according to the sixth embodiment.Fig. 27 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. Fig. 28 is a diagram showing an example of a configuration of a base station according to an embodiment. Fig. 29 is a diagram showing an example of a configuration of a user terminal according to an embodiment. Fig. 30 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 31 is a diagram showing an example of a vehicle according to an embodiment.

[0011] (CSI Reporting) In NR, a UE measures the channel state using a predetermined reference signal (or a resource for the reference signal) and feeds back (reports) channel state information (CSI) to the base station.

[0012] The UE may measure the channel state using a Channel State Information-Reference Signal (CSI-RS), a Synchronization Signal / Physical Broadcast Channel (SS / PBCH) block, a Synchronization Signal (SS), a Demodulation Reference Signal (DMRS), etc.

[0013] The CSI-RS resource may include at least one of a non-zero power (NZP) CSI-RS and a CSI-Interference Management (IM). An SS / PBCH block is a block including a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)) and a PBCH (and corresponding DMRS), and may be referred to as an SS block (SSB). An SSB index may be assigned to the time position of the SSB within a half-frame.

[0014] The CSI may include at least one of a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS Resource Indicator (CRI), a SS / PBCH Block Resource Indicator (SS / PBCH Block Indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), a Layer 1 (L1)-Reference Signal Received Power (RSRP), a L1-Reference Signal Received Quality (RSRQ), a L1-Signal to Interference plus Noise Ratio (SINR), a L1-Signal to Noise Ratio (SNR), and the like.

[0015] The CSI may have multiple parts. A first part of the CSI (CSI Part 1) may include information with a relatively small number of bits (e.g., RI). A second part of the CSI (CSI Part 2) may include information with a relatively large number of bits (e.g., CQI), such as information determined based on CSI Part 1.

[0016] As CSI feedback methods, (1) periodic CSI (P-CSI) reporting, (2) aperiodic CSI (A(AP)-CSI) reporting, and (3) semi-persistent (semi-persistent, semi-persistent) CSI reporting (Semi-Persistent CSI: SP-CSI) reporting are being considered.

[0017] The UE may be notified of information related to CSI reporting (which may be referred to as CSI reporting configuration information) using higher layer signaling, physical layer signaling (e.g., Downlink Control Information (DCI)), or a combination thereof. The CSI reporting configuration information may be configured, for example, using the RRC information element "CSI-ReportConfig."

[0018] The CSI reporting configuration information may include, for example, information regarding a reporting period, an offset, etc., which may be expressed in a predetermined time unit (slot unit, subframe unit, symbol unit, etc.). The CSI reporting configuration information may include a configuration ID (CSI-ReportConfigId). The configuration ID may identify parameters such as the type of CSI reporting method (whether it is SP-CSI, etc.), the reporting period, etc. The CSI reporting configuration information may include information (CSI-ResourceConfigId) indicating which signal (or which signal resource) is used to report the measured CSI.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0125] (L1 / L2 Inter-Cell Mobility) It is being considered that a UE performs UL transmission to one or more cells / TRPs. The following scenario 1 or scenario 2 can be considered as a procedure in this case. In the present disclosure, the term "serving cell" may be replaced with the TRP in the serving cell. The terms "layer 1 / layer 2" (L1 / L2) and "DCI / Medium Access Control Element (MAC CE)" may be interchangeable. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." The terms "non-serving cell," "cell with a different PCI," and "additional cell" may be interchangeable.

[0126] <Scenario 1> Scenario 1 corresponds to, for example, multi-TRP inter-cell mobility, but may be a scenario that does not correspond to multi-TRP inter-cell mobility.

[0127] (1) The UE receives from the serving cell the configuration necessary for using radio resources for data transmission and reception, including the SSB configuration for beam measurement of the TRP corresponding to a PCI different from that of the serving cell and the resources of the different PCI. (2) The UE performs beam measurement of the TRP corresponding to the different PCI and reports the beam measurement results to the serving cell. (3) Based on the above report, the Transmission Configuration Indication (TCI) state associated with the TRP corresponding to the different PCI is activated by L1 / L2 signaling from the serving cell. (4) The UE transmits and receives using UE-dedicated channels on the TRP corresponding to the different PCI. (5) The UE must always cover the serving cell, including in the case of multiple TRPs. As in conventional systems, the UE must use common channels from the serving cell, such as the Broadcast Control Channel (BCCH) and the Paging Channel (PCH).

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

[0129] Figure 5A shows an example of UE movement in Rel. 17. Assume that the UE moves from a cell (serving cell) with PCI #1 to a cell (additional cell) with PCI #3 (which overlaps with the serving cell). In this case, Rel. 17 does not support switching of the serving cell via L1 / L2.

[0130] An additional cell is a cell with an additional PCI that is different from the PCI of the serving cell. The UE can receive / transmit UE-dedicated channels from the additional cell. The UE needs to be within the coverage of the serving cell to receive UE common channels (e.g., system information / paging / short messages). When the UE moves out of the coverage of the serving cell, a cell change is required, such as by handover (also called L3 mobility).

[0131] <Scenario 2> In scenario 2, L1 / L2 inter-cell mobility is applied. With L1 / L2 inter-cell mobility, the serving cell can be changed using functions such as beam control without RRC reconfiguration. In other words, transmission and reception with an additional cell is possible without handover. Since handover requires RRC reconnection, which results in a period when data communication is unavailable, by applying L1 / L2 inter-cell mobility that does not require handover, data communication can be continued even when the serving cell is changed. Scenario 2 may be applied, for example, in Rel. 18. In scenario 2, for example, the following procedure is performed.

[0132] (1) The UE receives SSB configuration for a cell with a different PCI (additional cell) from the serving cell for beam measurement / serving cell change. (2) The UE performs beam measurement for the cell using the different PCI and reports the measurement results to the serving cell. (3) The UE may receive the configuration for the cell with a different PCI (serving cell configuration) via higher layer signaling (e.g., RRC). That is, pre-configuration for the serving cell change may be performed. This configuration may be performed together with or separately from the configuration in (1). (4) Based on the above report, the TCI state of the cell with a different PCI may be activated via L1 / L2 signaling in accordance with the serving cell change. The activation of the TCI state and the serving cell change may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts reception / transmission using the pre-configured UE-dedicated channel and TCI state.

[0133] That is, in Scenario 2, the serving cell (the serving cell assumed by the UE) is updated by L1 / L2 signaling. Scenario 2 may be applied in Rel. 18.

[0134] Figure 5B shows an example of UE mobility in Rel. 18. In Rel. 18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated channels / common channels to / from the new serving cell (or target serving cell). The UE may move out of the coverage of the current serving cell (e.g., current serving cell).

[0135] (Beam Report Types) <Intra-cell beam reporting in Rel. 15 / 16> In Rel. 15 / 16, intra-cell beam reporting is supported. For example, L1-RSRP / SINR reporting can be configured by higher layer signaling (RRC).

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

[0137] A UE may also be configured with up to 16 CSI-RS resource sets, with a maximum of 64 resources in each set, and the total number of different CSI-RS resources across all resource sets may not exceed 128.

[0138] For L1-RSRP reporting, if the higher layer parameter nrofReportedRS (e.g., in CSI-ReportConfig) is set to 1, the reported L1-RSRP value is defined as a 7-bit value in the range [-140 to -44] dBm with a step size of 1 dB.

[0139] Here, the maximum measured value of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm in 1 dB steps, and the differential value of L1-RSRP is quantized to a 4-bit value.

[0140] The difference value is calculated with a step size of 2 dB with reference to the largest measurement that is part of the same L1-RSRP reporting instance.

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

[0142] For channel measurement, the UE may be configured with a CSI resource setting for up to 64 CSI resources or up to 16 CSI-RS resource sets with SS / PBCH block resources.

[0143] For L1-SINR reporting, if the upper layer parameter nrofReportedRS is set to 1, the reported L1-SINR value is defined as a 7-bit value in the range [-23 to 40] dBm with a step size of 0.5 dB.

[0144] If the higher layer parameter nrofReportedRS is set to be greater than 1, or if the higher layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the differential value-based L1-SINR value for reporting.

[0145] The difference value is calculated with a step size of 1 dB with reference to the largest measurement that is part of the same L1-SINR reporting instance.

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

[0147] <Inter-cell beam reporting in Rel. 17> As mentioned above, Rel. 17 supports L1 / L2 inter-cell mobility. For example, a UE can transmit and receive UL / DL channels / signals to and from a PCI of a cell that is different from the PCI of the serving cell. For example, if a non-serving cell has a higher RSRP than the serving cell, the UE can transmit and receive UL / DL channels / signals to and from the non-serving cell without performing a handover.

[0148] In L1-RSRP reporting, absolute / differential values ​​of L1-RSRP may be used, as in Rel. 15 / 16. In inter-cell beam reporting (type 2-1 beam reporting, described later) in Rel. 17, each L1-RSRP value is associated with a PCI ID (for the serving cell / additional cell / candidate cell). The association between the L1-RSRP value and the PCI ID may be set / indicated by higher layer signaling / physical layer signaling.

[0149] Configuration by higher layer signaling supports up to seven additional cells, where ID=0 means the PCI of the serving cell.

[0150] In this disclosure, inter-cell beam reporting (in Rel. 17 / 18) may be referred to as Type 2 beam reporting (Beam Report Type 2). Type 2 beam reporting can be further classified into Types 2-1 and 2-2, which will be described later.

[0151] In this disclosure, Rel. 17 beam reporting may be referred to as Type 2-1 beam reporting or beam reporting for inter-cell beam switching.

[0152] <Inter-cell beam reporting in Rel. 18> In addition, Rel. 18 supports only SSB-based L1-RSRP reporting (beam reporting). Here, the number of candidate cells L may be any value between 1 and 4, and the number of beams M per cell may be any value between 1 and 4. For example, in beam reporting, a 7-bit absolute value (the largest L1-RSRP value among all cells) is reported for one cell, and all remaining L1-RSRP values ​​are reported as differential values.

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

[0154] In the L1-RSRP report, the absolute value / differential value of the L1-RSRP may be used, as in Rel. 15 / 16 / 17.

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

[0156] Here, the maximum measured value of L1-RSRP is quantized to a 7-bit value in the range of [-140 to -44] dBm in 1 dB steps, and the differential value of L1-RSRP is quantized to a 4-bit value.

[0157] The difference value is calculated with a step size of 2 dB with reference to the largest measurement that is part of the same L1-RSRP reporting instance.

[0158] The L1-RSRP report includes the SSBRIs between the configured candidate cells. That is, the L1-RSRP report includes the SSBRIs of the configured candidate cells and the corresponding L1-RSRPs. The format may be the same as that of the existing specifications.

[0159] In this disclosure, the beam report of Rel. 18 may be referred to as a Type 2-2 beam report or a beam report for cell switching. Note that the Type 2-2 beam report does not include information about the PCI (PCI ID). Instead, the SSBRI may include information about the PCI. For example, if four cells have 64 SSBs, the SSBRI may be any of {0, 1, ..., 255}.

[0160] (Event-Based Beam Reporting) It is being considered that future wireless communication systems will support event-based beam reporting. Event-based beam reporting may also be called event-triggered beam reporting or event-driven beam reporting, and may refer to UE-initiated beam reporting.

[0161] <Applicable Cases> Event-based beam reporting may be applied, for example, in at least one of the following Case 1 or Case 2: - [Case 1]: L1-RSRP / SINR beam reporting including serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam reporting including serving cell / additional PCI cells for Rel. 18 L1 / L2 mobility with L1 / L2 inter-cell mobility / intra-cell multi-TRP (M-TRP inter-cell) / cell switching). - [Case 2]: L1-RSRP / SINR beam reporting including only serving cell PCI.

[0162] When a specific event occurs (which in the present disclosure may be interpreted as a specific condition being met / not being met), the UE may report measurement results (e.g., L1-RSRP / L1-SINR) to the NW (e.g., base station).

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

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

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

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

[0167] 6 is a flowchart showing an example of an event-based beam reporting process. The UE determines whether an event (e.g., at least one of the following events A2 to A6 and I1) has occurred (S1). If the result of S1 is YES, the UE transmits an aperiodic CSI report (and an RRM report) (S2). If the result of S1 is NO, the UE terminates the process related to the event-based beam reporting. The process of FIG. 6 may be repeatedly performed at predetermined intervals.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0189] In the present disclosure, the "current beam" may be, for example, an indicated TCI state (joint / DL / UL TCI state) in the current unified TCI state. Also, the "current beam" may be, for example, a QCL source RS (QCL type D / A) related to the current indicated TCI state.

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

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

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

[0193] In this disclosure, "worse / better" may mean, for example, lower / higher measurement results (e.g., RSRP / SINR / RSRQ).

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

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

[0196] In addition, in the present disclosure, UE-initiated beam reporting, event-triggered beam reporting, event-driven beam reporting, event-based beam reporting, and event-based beam reporting may be read interchangeably.

[0197] In the present disclosure, the reported beam, the reporting beam, and the UE reporting beam may be read interchangeably.

[0198] (Cell Switch Command (MAC CE) in Rel. 18) The cell switch command sent by the MAC CE may include at least the following information: Information to identify the target cell, Information about the Timing Advance (TA), One joint TCI state index for the target cell or a set of DL / UL TCI state indices for the target cell, Active DL / UL BWPs of the target cell.

[0199] Regarding the presence of beam indication in the cell switch command, the following may be supported for at least some scenarios: There is always a field in the cell switch command indicating one joint TCI state index for the target cell or a set of DL / UL TCI state indices for the target cell. UE behavior with respect to the beam indication field for RACH-based handover scenarios after a cell switch command.

[0200] (Analysis) As mentioned above, in future wireless communication systems (e.g., Rel. 19 and later), from the viewpoint of reducing overhead / delay, a unified TCI framework is assumed, and the introduction of UE-initiated / event-driven beam management is being considered while utilizing the existing CSI measurement / reporting configuration framework as much as possible.

[0201] The beam management may, for example, target frequency range 2 (FR2) and a single TRP with intra-cell / inter-cell beam management.

[0202] Specifically, consideration has been given to the content of UL signaling for UE-initiated / event-driven beam reporting to facilitate fast beam switching, and the medium / container of UL signals that take into account the nature of UE-initiated / event-driven beam management of UL transmissions, but these considerations have not been sufficient.

[0203] In addition, there has been insufficient consideration of how the UE recognizes whether or not the network (NW, e.g., base station) has received a UE-initiated / event-driven beam report, and the UE's behavior when it recognizes that the beam report has failed.

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

[0205] Based on this, the inventors have conceived a new method for beam reporting regarding mobility.

[0206] (Various Replacements, etc.) Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

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

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

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

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

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

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

[0213] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0214] In the present disclosure, the terms 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 (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0215] In the present disclosure, base station, gNB, and network (NW) may be read interchangeably.

[0216] In the present disclosure, a cell group, a serving cell group, a master cell group (MCG), and a secondary cell group (SCG) may be interchangeable. L1 / L2, L1 / L2 signaling, and DCI / MAC CE may be interchangeable. A serving cell may be replaced with a cell that transmits a PDSCH. A candidate cell may refer to a cell that is a candidate to become a serving cell through L1 / L2 inter-cell mobility. L1L2-triggered mobility (LTM), L1 / L2 inter-cell mobility, and mobility may be interchangeable.

[0217] In the present disclosure, the terms cell, PCI, serving cell, source serving cell, source cell, CC, BWP, BWP within a CC, and band may be interchangeable. In the present disclosure, the terms cell, PCI, cell with an additional PCI, additional cell, other cell, non-serving cell, cell with a different PCI, candidate cell, candidate serving cell, cell with a PCI different from the PCI of the current serving cell, another serving cell, and target cell may be interchangeable. The target cell may be a cell selected from multiple candidate cells. In the present disclosure, the terms switch, change, and update may be interchangeable. The serving cell may be interchangeable with the serving cell before the switch or the serving cell after the switch.

[0218] In the present disclosure, event-based beam reporting, event-based beam reporting, event-triggered beam reporting, event-driven beam reporting, UE-triggered beam reporting, and UE-initiated beam reporting may be read interchangeably.

[0219] In this disclosure, event-based beam reporting may simply be referred to as beam reporting / CSI reporting / L1-RSRP / SINR beam reporting.

[0220] In the present disclosure, the terms table, mapping, and association may be read interchangeably.

[0221] In the present disclosure, (new) MAC CE, (new) UCI, CG-UCI, UTO-UCI, cell switch command, beam switch command, beam report MAC CE, cell switch MAC CE, and beam switch MAC CE may be read interchangeably.

[0222] In the present disclosure, the event-based beam report may be reported in a PUSCH (e.g., a configured grant PUSCH, a grant-based PUSCH) / PUCCH. In addition, the report content in the present disclosure may be transmitted using at least one of a MAC CE / UCI / PUCCH / PUSCH.

[0223] (Wireless Communication Method) The configuration of a particular UL channel may be configured / activated / instructed for event-based beam reporting.

[0224] The configuration / activation / indication may be performed using higher layer signaling (e.g., RRC signaling / MAC CE) / DCI.

[0225] When an event-based beam report is triggered, the UE may transmit beam report information / CSI report using the specific UL channel.

[0226] Each embodiment of the present disclosure may be applied to at least one of event-based beam reporting for MIMO (Multi-Input Multi-Output) operation and event-based beam reporting for mobility / LTM operation.

[0227] First Embodiment The first embodiment relates to operations related to event-based beam reporting.

[0228] The particular UL channel transmitting the beam report information / CSI report may be, for example, a (dedicated) configured grant (CG) PUSCH.

[0229] Event-based beam reporting may be triggered based on a particular triggering event / condition, which may be, for example, at least one of the events described above.

[0230] The UE may transmit the beam report information using a specific MAC CE. An example of the specific MAC CE is described below. The specific MAC CE may be, for example, a MAC CE newly defined (for Rel. 19 or later).

[0231] According to the first embodiment, compared with a PUSCH (a dynamic grant PUSCH (DG PUSCH)) requested by an SR / PRACH for a MAC CE having beam report information, the use of a CG PUSCH can shorten the delay for beam reporting. Furthermore, since resources for the CG PUSCH can be shared among multiple UEs, resource utilization efficiency can be improved.

[0232] In addition, the CG PUSCH configuration in this embodiment does not have to be a CG PUSCH configuration dedicated to event-based beam reporting. In other words, the UE may use any CG PUSCH configuration for event-based beam reporting.

[0233] When an event-based beam report is triggered, the UE may transmit beam report information at the first valid CG PUSCH transmission opportunity after the trigger.

[0234] Furthermore, the CG PUSCH configuration in this embodiment may be a CG PUSCH configuration dedicated to event-based beam reporting. In this case, if the CG PUSCH is not configured for the UE, the UE may transmit an SR and schedule PUSCH transmission for the event-based beam reporting. The SR configuration / resource may be a configuration / resource dedicated to event-based beam reporting, or may not be a configuration / resource dedicated to event-based beam reporting (may be any configuration / resource).

[0235] 7 is a diagram showing an example of a beam report according to the first embodiment. In the example shown in FIG. 7, a CG PUSCH for beam reporting (which may also be referred to as a CG PUSCH transmission opportunity or a CG PUSCH opportunity, etc.) is configured in advance for the UE. When an event-based beam report is triggered (or the UE determines to perform an event-based beam report based on its implementation), the UE transmits a MAC CE including beam information at the first valid CG PUSCH transmission opportunity thereafter.

[0236] A timer for retransmission of the beam report (e.g., cg-BeamReport-RetransmissionTimer) may be defined / configured, and the UE may control the retransmission of the beam report information based on the timer.

[0237] The timer for retransmission of the beam report (e.g., cg-BeamReport-RetransmissionTimer) may correspond to the period after transmission / retransmission for the configured grant for the HARQ process of the initial transmission of the MAC CE for the event-based beam report, for example, when the UE does not autonomously initiate retransmission in the HARQ process.

[0238] The UE may decide autonomously not to retransmit the CG by the MAC CE for the beam report while the timer for retransmission of the beam report is running / starting.

[0239] A timer for retransmission of a beam report (e.g., cg-BeamReport-RetransmissionTimer) may be started / restarted for at least one of the CG PUSH for the initial transmission of a MAC CE for an event-based beam report and the retransmission of the initial transmission of the MAC CE.

[0240] If a timer for retransmission of a beam report (e.g., cg-BeamReport-RetransmissionTimer) is started by a PUSH transmission, the timer may be started at a specific timing (e.g., at the start of the first symbol of the PUSH transmission).

[0241] 8 is a diagram showing an example of starting a timer for retransmission of a beam report according to the first embodiment. In the example shown in FIG. 8, the UE transmits a MAC CE for an event-based beam report using a CG PUSCH.

[0242] In the example shown in Figure 8, if the HARQ process of the CG PUSH corresponds to HARQ process number (HPN) #3, a timer for retransmitting the beam report corresponding to the HARQ process of HPN #3 is started at a specific timing (in the example shown in Figure 8, the start symbol of the CG PUSH transmitting the MAC CE).

[0243] The timer for retransmission of a beam report (e.g., cg-BeamReport-RetransmissionTimer) may be stopped in certain cases while the corresponding HARQ process is running.

[0244] The specific case may be at least one of the following: - When an UL grant of the PDCCH is received for a specific RNTI of the MAC entity (e.g., Cell (C-) RNTI / Temporary Cell (TC-) RNTI); - When an UL grant is received in a Random Access Response (RAR) (when an UL grant of the PDCCH is received for a specific RNTI of the MAC entity (e.g., Random Access (RA-) RNTI)); - When an UL grant of the PDCCH is received for a specific RNTI of the MAC entity (e.g., Configured Scheduling (CS-) RNTI) and the New Data Indicator (NDI) corresponding to the received HARQ information indicates a specific value (e.g., a toggled value (e.g., 1)); - When a timer related to the configured grant (e.g., configuredGrantTimer) expires.

[0245] If the same HARQ process ID is indicated by at least one of an UL grant / DCI whose CRC is scrambled by a specific RNTI (e.g., C- / TC-RNTI), an UL grant / DCI corresponding to an RAR, and an UL grant / DCI whose CRC is scrambled by a specific RNTI (e.g., CS-RNTI) and has an NDI with a specific value, the UE may determine that the previous transmission for the same HARQ process ID was successful and stop the corresponding timer.

[0246] 9 is a diagram showing an example of stopping a timer for retransmission of a beam report according to the first embodiment. In the example shown in FIG. 9, the UE transmits a MAC CE for an event-based beam report using a CG PUSCH.

[0247] In the example shown in Figure 9, a timer for retransmission of the beam report corresponding to the HARQ process of HPN #3 is started, as shown in Figure 8 above.

[0248] At a certain timing, the UE receives DCI with NDI=1 for HPN #3 (DCI in PDCCH whose CRC is scrambled by C- / TC- / RA- / CS-RNTI). At that timing, the UE stops the timer for retransmitting the beam report.

[0249] In addition, if the timer related to the configured grant for the HARQ process (e.g., configuredGrantTimer) expires, the UE may stop the timer related to the retransmission of the beam report (e.g., cg-BeamReport-RetransmissionTimer) if the HARQ process is running.

[0250] 10 is a diagram showing another example of stopping the timer for retransmission of a beam report according to the first embodiment. In the example shown in FIG. 10, the UE transmits a MAC CE for an event-based beam report using a CG PUSCH.

[0251] In the example shown in Figure 10, a timer for retransmission of the beam report corresponding to the HARQ process of HPN #3 is started, as shown in Figure 8 above.

[0252] 10, the timer (configuredGrantTimer) related to the configured grant for HPN #3 expires at a certain timing, and the UE stops the timer related to the retransmission of the beam report at that timing.

[0253] For the CG PUSCH, if a timer for retransmission of the beam report (e.g., cg-BeamReport-RetransmissionTimer) is configured and the corresponding HARQ entity is not running, and if the CG PUSCH is for a MAC CE for beam report (Case A), the UE may determine that the NDI bit is toggled. In this case, the UE may deliver a UL grant (configured UL grant) for the CG PUSCH and related HARQ information to the HARQ entity.

[0254] In cases other than case A, if the previous UL grant for the same HARQ process is for the initial transmission / retransmission of the MAC CE for beam reporting and a PDCCH addressed to a specific RNTI (e.g., C-RNTI) has not been received in the same HARQ process used for the retransmission of the MAC CE for beam reporting, the UE may determine that the NDI bit is not toggled, and in this case, the UE may deliver a UL grant for the CG PUSCH (configured UL grant) and related HARQ information to the HARQ entity.

[0255] By specifying it in this way, the NDI bit can be interpreted appropriately for the first transmission of the CG PUSCH carrying the MAC CE for the beam report before the timer for retransmission of the beam report starts.

[0256] According to the first embodiment described above, event-based beam reporting can be performed appropriately by utilizing CG PUSCH.

[0257] <<Example of Specific MAC CE>> An example of the specific MAC CE will be described below.

[0258] In the diagram showing an example of MAC CE in the present disclosure, an example in which the measurement results are indicated by L1-RSRP is described, but this is merely an example, and the indicator of the measurement results is not limited to this.

[0259] A new MAC CE including a Logical Channel ID (LCID) may be defined and used for the CSI report triggered by the above event. In the following description, "report" may refer to, for example, an SSB index, a re-indexing index of a cell, or a set of L1-RSRP / L3-RSRP. The SSB index in each figure may be replaced with a CSI-RS index. Each figure may include, for example, a report for one serving cell and a report for one or more non-serving cells. RSRP may be replaced with SINR.

[0260] Figure 11 shows a first example of a MAC CE used for CSI reporting. In the example of Figure 11, a new ID (Re-indexing index of cell) and L1-RSRP corresponding to each SSB index are reported. The first report (SSB index, Re-indexing index of cell, and L1-RSRP) may relate to the serving cell, and the second and third reports may relate to non-serving cells. One of the SSB indices in Figure 11 may be the SSB index of the best beam of the non-serving cell.

[0261] Figure 12 shows a second example of a MAC CE used for CSI reporting. "T" in Figure 12 is a flag indicating whether a report of the next octet (8 bits) exists for a non-serving cell. Other points are the same as in Figure 11.

[0262] Fig. 13 is a diagram showing a third example of MAC CE used for CSI reporting. In the example of Fig. 13, the report includes L1-RSRP and L3-RSRP. The number of reports is two, but may be three as in Figs. 11 and 12. Other points are the same as Fig. 11.

[0263] Figure 14 is a diagram showing a fourth example of MAC CE used for CSI reporting. In the example of Figure 14, L1-RSRP (absolute) is an absolute value (maximum value). L1-RSRP (differential) is the difference between the L1-RSRP of the second SSB index (beam) and the first L1-RSRP (absolute). L3-RSRP (absolute, cell-level) is the absolute value (maximum value) of the L3-RSRP at the cell level (per cell).

[0264] Fig. 15 is a diagram showing a fifth example of a MAC CE used for CSI reporting. In the example of Fig. 15, the contents except for L3-RSRP from the example of Fig. 14 are arranged for every three cells.

[0265] 16 is a diagram showing a sixth example of a MAC CE used for CSI reporting. In FIG. 16, the report for the first cell (e.g., serving cell) is the same as that in FIG. 15, but for the second and third cells (e.g., non-serving cells), L1-RSRP (differential) is included instead of L1-RSRP (absolute). For example, L1-RSRP (differential) is a measurement result for each beam, and may be the difference from the L1-RSRP (absolute) of the first cell.

[0266] Fig. 17 is a diagram illustrating a seventh example of a MAC CE used for CSI reporting. Fig. 18 is a diagram illustrating an eighth example of a MAC CE used for CSI reporting.

[0267] The MAC CE shown in FIG. 17 includes a field indicating the second to fourth measurement results and the presence of an RS ("C i" field (i = 2, 3, 4)), a field indicating the RS IDs corresponding to the top four beams ("RS ID i" field (i = 2, 3, 4)), a field indicating the measurement results ("L1-RSRP i" field (i = 2, 3, 4)), and a reserved field ("R" field).

[0268] The field indicating the RS ID may consist of 6 bits in the case of SSBRI only, or 7 bits in the case of SSBRI / CRI.

[0269] In the MAC CE, the field corresponding to the measurement result of the best (first highest) beam may be defined by the first number of bits (e.g., 7 bits), in which case the field may indicate the absolute value of the measurement result.

[0270] In the MAC CE, a field corresponding to the measurement results of beams other than the best beam (e.g., the measurement results of the second to fourth beams) may be defined with a second number of bits (e.g., 4 bits), in which case the field may indicate a relative / differential value with respect to the measurement result of the best beam.

[0271] In the MAC CE, a field corresponding to the measurement results of beams other than the best beam (e.g., the measurement results of the second to fourth beams) may be defined by the first number of bits (e.g., 7 bits). In this case, the field may indicate the absolute value of the measurement results.

[0272] In the MAC CE, "C i The "C" field may be represented by 1 bit. i If the "C" field indicates a first value (e.g., 0), it may indicate that the corresponding beam is not reported. i If the " field indicates a second value (e.g., 1), it may indicate that reporting of the corresponding beam is performed.

[0273] For example, if the "C2", "C3", and "C4" fields each indicate 1, the measurement results and RS ID of the second beam, the measurement results and RS ID of the third beam, and the measurement results and RS ID of the fourth beam may be reported in the MAC CE. In other words, only when the "C2", "C3", and "C4" fields indicate 1, the fields (RSRP / PCI) corresponding to the second to fourth beams may be present.

[0274] In FIG. 17, the fields in octets 3 to 7 may be optional.

[0275] The MAC CE shown in FIG. 18 may have 16 bits added corresponding to octets 8 and 9 compared to the MAC CE shown in FIG.

[0276] The additional fields may include a field indicating the PCI of the serving cell / additional cell / candidate cell ("PCI i" field (e.g., i = 1, 2, 3, 4)) and a reserved field ("R" field). The field indicating the PCI may be configured with, for example, 3 bits.

[0277] The additional fields (also utilizing the reserved fields) can indicate the PCI of up to seven additional cells in addition to the PCI of one serving cell. The size of each field can be changed as needed. The size of each field can be configured by the RRC, predefined by a specification, or determined by the UE capabilities.

[0278] For example, the size of a field indicating an RS ID (RS ID field) may be increased or decreased depending on whether a field indicating a PCI (PCI field) is included. For example, if a field indicating a PCI is not included (e.g., Type 2-1), the RS ID field may be increased / extended (e.g., 2 bits). That is, the size of the PCI field may be variable depending on the type of beam report.

[0279] Second Embodiment The second embodiment relates to event-based beam reporting.

[0280] The particular UL channel transmitting beam report information / CSI report may be, for example, a PUSCH.

[0281] The PUSCH may carry, for example, a unique semi-persistent (SP-) / aperiodic (A-) CSI report with a CSI reporting configuration ID (eg, CSI-ReportConfigId).

[0282] When event-based beam reporting is triggered, the UE may transmit beam report information in a PUSCH for SP- / A-CSI reporting.

[0283] If event-based beam reporting is not triggered, the UE does not need to transmit beam report information in the PUSCH for SP- / A-CSI reporting.

[0284] Event-based beam reporting may be triggered based on a particular triggering event / condition, which may be, for example, at least one of the events described above.

[0285] The UE may transmit the beam report information using a specific MAC CE. An example of the specific MAC CE may be at least one of the MAC CEs described above. The specific MAC CE may be, for example, a MAC CE newly defined (for Rel. 19 or later).

[0286] Regarding retransmission of SP- / A-CSI reports (beam report information) in PUSH, the UE may perform the retransmission based on scheduling by an UL grant for PUSH with the same HARQ process ID.

[0287] According to the second embodiment described above, appropriate event-based beam reporting can be performed by utilizing the PUSCH that transmits SP- / A-CSI.

[0288] <Third Embodiment> The third embodiment relates to a UCI that transmits beam report information.

[0289] At least one of the new UCI, the existing CG-UCI (with extension), and the unused transmission occasion(s) indicated by UCI (UTO-UCI) in the CG-PUSCH may be configured / defined to indicate beam report information for event-based beam reporting.

[0290] At least one of the new UCI, the existing CG-UCI, and the UTO-UCI may transmit a beam report.

[0291] In this disclosure, a new UCI may refer to a new type of UCI. In this disclosure, a new UCI may simply be referred to as a "UCI."

[0292] Settings for reporting new UCI may follow Option 3-1 / 3-2 below.

[0293] <<Option 3-1>> Reporting of new UCI may be configured for each CG setting.

[0294] For example, only one CG setting may be configured for reporting new UCI.

[0295] Also, for example, one or more CG settings may be configured for (reporting of) new UCI.

[0296] <<Option 3-2>> Reporting of new UCI may be set commonly for multiple (e.g., all) CG settings.

[0297] At each CG PUSCH transmission opportunity for CG configuration in which a new UCI is configured, at least one of the following options 3-A to 3-D may be applied regarding whether or not there is a new UCI (which may also be referred to as a new UCI container) that can transmit a beam report.

[0298] <<Option 3-A>> Each transmitted CG PUSCH transmission opportunity may include a new UCI container.

[0299] 19 is a diagram showing an example of a CG PUSCH according to Option 3-A. In the example shown in FIG. 19, four CG PUSCH transmission opportunities are shown, each of which includes a new UCI container.

[0300] In the example shown in Figure 19, an event beam report is triggered at a certain timing, and the UE transmits beam report information using new UCI in the first subsequent PUSCH transmission opportunity.

[0301] <<Option 3-B>> The CG PUSCH transmission opportunity having the new UCI container may be predefined, may be set / indicated based on the CG configuration, or may be determined based on specific conditions.

[0302] For example, the CG PUSCH transmission opportunity may be set based on at least one of information about the period in the CG configuration and information about the start offset.

[0303] Fig. 20 is a diagram showing an example of a CG PUSCH according to Option 3-B. In the example shown in Fig. 20, four CG PUSCH transmission opportunities are shown, and it is pre-defined / pre-configured that two of the transmission opportunities include a new UCI container.

[0304] In the example shown in Figure 20, an event beam report is triggered at a certain timing, and the UE transmits beam report information at the first subsequent PUSCH transmission opportunity that includes a new UCI container.

[0305] <<Option 3-C>> If certain conditions are met, a new UCI container may be included in a CG PUSCH transmission opportunity.

[0306] The specific condition may be, for example, that the CG PUSCH transmission opportunity is the first PUSCH transmission in a CG period. Also, the specific condition may be, for example, that the CG PUSCH transmission opportunity is the first PUSCH transmission after an SR for event-based beam reporting is transmitted.

[0307] The transmission of SRs for event-based beam reporting will be described in detail in the fourth embodiment below.

[0308] <<Option 3-D>> Whether a new UCI container is included in a CG PUSCH transmission opportunity may be indicated using a field / bit of CG-UCI / UTO-UCI.

[0309] In this case, it may be supported that the CG PUSCH includes both CG-UCI / UTO-UCI and new UCI.

[0310] For example, a CG-UCI / UTO-UCI may indicate whether a new UCI container is present in the current CG PUSCH transmission opportunity (of that CG-UCI / UTO-UCI).

[0311] Also, for example, the CG-UCI / UTO-UCI may indicate whether a new UCI container is present at the next CG PUSCH transmission opportunity.

[0312] Also, for example, the CG-UCI / UTO-UCI may indicate whether a new UCI container is present in one or more CG PUSCH transmission opportunities, for example, in a predefined / specified pattern or in a bitmap format.

[0313] In addition, when the presence of a new UCI container is indicated in the above options 3-A to 3-D, the UE may determine that a new UCI container exists in the corresponding CG PUSCH transmission opportunity. In this case, the new UCI container does not necessarily have to include beam report information.

[0314] Furthermore, if the presence of a new UCI container is indicated in Options 3-A to 3-D, the UE may determine that a new UCI container exists in the corresponding CG PUSCH transmission opportunity, and the new UCI container may necessarily include beam report information.

[0315] The new UCI in CG-PUSCH may be coded / multiplexed using the same coding / multiplexing method as that used for CG-UCI / UTO-UCI.

[0316] The new UCI may have a specific priority (physical priority), for example, the new UCI may have the same priority as the CG PUSCH.

[0317] For example, when a HARQ-ACK with the same priority as a CG PUSCH is mapped / multiplexed to a CG PUSCH, the new UCI may be coded together with the HARQ-ACK.

[0318] Also, for example, HARQ-ACK bits may be jointly coded following the UTO-UCI bits.

[0319] The content of the beam report information included in the new UCI may be specific information, for example, information corresponding to a field included in the above-mentioned MAC CE.

[0320] For example, the UE may transmit some information (additional fields) included in the above-mentioned MAC CE by using specific CSI (e.g., CSI Part 2). The UE may transmit information for determining the size X of CSI Part 2 (some indication fields of CSI Part 2) to the NW as separate UCI of CSI Part 1.

[0321] In other words, CSI Part 1 may include information regarding the UCI size of CSI Part 2. CSI Part 1 and CSI Part 2 may be reported by one PUCCH resource.

[0322] CSI Part 1 and CSI Part 2 may be transmitted over different PUCCH resources / UCI.

[0323] If the CG-UCI / UTP-UCI is validated for event-based beam reporting, the content of the beam reporting information may be added to the content of the existing CG-UCI / UTP-UCI.

[0324] According to the third embodiment described above, beam report information can be appropriately transmitted using various UCIs.

[0325] <Fourth embodiment> The fourth embodiment relates to SR related to beam report information.

[0326] The (specific) SR (PUCCH-SR) setting may be configured for event-based beam reporting.

[0327] The configuration may be based on RRC signaling using new RRC parameters.

[0328] When an event-based beam report is triggered by a particular event / condition, an associated SR may be sent from the UE to the NW.

[0329] After a specific period of time (eg, period X) has elapsed since the transmission of the SR, at least one of the sub-options 4-1 to 4-8 may be applied.

[0330] Note that X may be predefined, may be notified / configured / instructed to the UE using higher layer signaling (RRC / MAC CE) / DCI, may be determined based on UE capability information, or may be determined by a combination of these.

[0331] <<Option 4-1>> The UE does not need to take any additional action.

[0332] The UE may receive semi-persistent / non-periodic beam reporting configuration / instruction from the NW to report beam reporting information for a specific CSI reporting configuration (e.g., CSI-ReportConfig).

[0333] The UE may wait to receive semi-persistent / non-periodic beam reporting configuration / instruction from the NW to report beam reporting information for a particular CSI reporting configuration (e.g., CSI-ReportConfig).

[0334] A specific CSI reporting configuration (e.g., CSI-ReportConfig) may be extended from an existing CSI reporting configuration to report beam information for event-based beam reporting.

[0335] <<Option 4-2>> The UE may generate a MAC CE including beam report information.

[0336] The UE may also receive / wait for a DCI with an UL grant to schedule a PUSCH and transmit the corresponding MAC CE.

[0337] In this option, the UE may transmit the existing SR and may not transmit an SR for event-based beam reporting.

[0338] <<Option 4-3>> The UE may generate a MAC CE including beam report information.

[0339] The UE may transmit the MAC CE at a specific (e.g., first) CG PUSCH transmission opportunity after transmitting an SR for event-based beam reporting.

[0340] The transmission period of the CG PUSCH may be based on any CG PUSCH configuration, or may be based on the CG PUSCH configuration described in the first embodiment.

[0341] <Option 4-4> The UE may generate new UCI (and at least one of CG-UCI / UTO-UCI) including beam report information.

[0342] The UE may transmit a new UCI container / new UCI at a specific (e.g., first) CG PUSCH transmission opportunity after an SR transmission for event-based beam reporting.

[0343] The transmission period of the CG PUSCH may be based on any CG PUSCH configuration, or may be based on the CG PUSCH configuration described in the first embodiment.

[0344] In this option, the presence of the new UCI container may be set / indicated according to at least one of the methods described in the third embodiment above, in which case the actual transmission of the new UCI may be indicated by the SR.

[0345] <Option 4-5> The SR for event-based beam reporting may be considered as an indication of new UCI with beam reporting information at the next CG PUSH transmission opportunity (which may be based on any CG PUSH configuration or on the CG PUSH configuration described in the first embodiment above).

[0346] That is, the UE may generate new UCI / CG-UCI / UTO-UCI with beam report information.

[0347] The UE may then transmit the new UCI container / new UCI at a specific (e.g., first) CG PUSCH transmission opportunity after the SR transmission for the event-based beam report.

[0348] In this option, the new UCI container may not be present in the CG PUSCH before the transmission of the SR. The UE may assume / determine that the new UCI container is not present in the CG PUSCH before the transmission of the SR.

[0349] At least one of the presence of the new UCI container / new UCI and the actual transmission of the new UCI may be indicated by the SR.

[0350] Furthermore, until the transmission of the new UCI is successful, the transmission of the new UCI may be specified as one-shot / multi-shot new UCI transmission. In other words, the UE may transmit the new UCI as one-shot (single transmission) or as multi-shot (multiple transmissions). The number of multi-shots may be specified in advance in a specification, may be notified to the UE by RRC / MAC CE / DCI, or may be determined based on the capability information of the UE.

[0351] 21 is a diagram showing an example of transmission of beam report information according to Option 4-5. In the example shown in FIG. 21, four CG PUSCH transmission opportunities are shown. In the example shown in FIG. 21, by default, no new UCI container is present in each CG PUSCH transmission opportunity.

[0352] In the example shown in Figure 21, an event beam report is triggered at a certain timing. The UE transmits beam report information using new UCI at the first PUSH transmission opportunity after a specific period (X) has elapsed since the trigger. In the example shown in Figure 21, an instruction to transmit one-shot new UCI / beam report information is given.

[0353] <Option 4-6> The SR for event-based beam reporting may be considered as an indication of activation of a predefined / configured CG PUSCH setting.

[0354] The SR may also be configured in association with CG PUSCH configuration.

[0355] The UE may transmit the MAC CE / new UCI at a particular (eg, first) CG PUSCH transmission opportunity in the newly activated CG PUSCH configuration.

[0356] Conditions for deactivating the CG PUSCH configuration may be specified.

[0357] For example, a timer for CG PUSCH configuration may be predefined / configured, and when the timer expires, the UE may deactivate the CG PUSCH configuration.

[0358] Also, for example, the UE may deactivate the CG PUSCH configuration at a specific timing after the MAC CE / new UCI is (successfully) transmitted in a specific (for example, first) CG PUSCH transmission opportunity.

[0359] Figure 22 is a diagram showing an example of transmission of beam report information related to options 4-6. In the example shown in Figure 22, an event beam report is triggered at a certain timing. At this time, the UE determines that the CG setting has been activated, and transmits beam report information using a MAC CE / new UCI at the first CG PUSCH transmission opportunity after a specific period (X) has elapsed since the trigger. Note that in the example shown in Figure 22, an instruction to transmit one-shot new UCI / MAC CE / beam report information is issued.

[0360] <Option 4-7> The SR for event-based beam reporting may be considered as an indication of event-based beam reporting in the next first PUCCH resource (normal PUCCH resource).

[0361] The UE may transmit beam report information using UCI in a specific (e.g., first) PUCCH resource (normal PUCCH resource) after transmitting the SR.

[0362] In this case, the UE may transmit beam report information in the PUCCH resource regardless of whether there is other UCI content.

[0363] The UE may also transmit beam report information along with the UCI content in a specific (e.g., first) PUCCH resource (a PUCCH resource with other UCI content) after transmitting the SR.

[0364] In this case, if the UCI includes periodic / semi-persistent beam reporting information, the beam reporting information relating to the event-based beam reporting may be replaced with the periodic / semi-persistent beam reporting information.

[0365] Figure 23 is a diagram showing an example of transmission of beam report information related to options 4-7. In the example shown in Figure 23, an event beam report is triggered at a certain timing. At this time, the UE determines that the CG setting has been activated, and transmits beam report information using new UCI in the first (normal) PUCCH resource after a specific period (X) has elapsed since the trigger. In the example shown in Figure 23, an instruction to transmit one-shot new UCI / beam report information is issued.

[0366] <Option 4-8> The SR for event-based beam reporting may be considered as an indication of activation of pre-configured SP- / A-CSI reporting in PUSH.

[0367] The SR may also be associated with the SP- / A-CSI report in the PUSH.

[0368] The UE may transmit beam report information for event-based beam reporting based on the SP- / A-CSI report in the PUSH.

[0369] Conditions for deactivation of the SP- / A-CSI report may be specified / set.

[0370] For example, a timer for SP- / A-CSI reporting may be predefined / configured, and when the timer expires, the UE may deactivate SP- / A-CSI reporting on the PUSCH.

[0371] Also, for example, the UE may deactivate SP- / A-CSI reporting at a specific timing after beam report information related to event-based beam reporting has been (successfully) transmitted.

[0372] In addition, the SP- / A-CSI report may be transmitted using PUSCH / PUCCH.

[0373] Figure 24 is a diagram showing an example of transmission of beam report information related to options 4-8. In the example shown in Figure 24, an event beam report is triggered at a certain timing. At this time, the UE determines that the SP- / A-CSI report has been activated, and transmits beam report information using the SP- / A-CSI at the first PUSH transmission opportunity after a specific period (X) has elapsed since the trigger. In the example shown in Figure 24, an instruction to transmit one-shot CSI / beam report information is issued.

[0374] <<Variation of the Fourth Embodiment>> Multiple (unique) SRs (PUCCH-SR resources) may be configured for event-based beam reporting via RRC signaling.

[0375] Each SR setting may be associated with a particular beam (e.g., CSI-RS / SSB) from a particular cell.

[0376] The particular cell may be the serving cell for intra-cell cases, or a cell with an additional physical cell ID (PCI) for inter-cell cases.

[0377] If the event-based beam reporting is triggered by a specific event / condition, the SR resource used for transmission may be the specific SR resource.

[0378] For example, the UE may select / determine as the specific SR resource an SR resource corresponding to a beam (recommended beam) with good channel quality (e.g., RSRP / RSRQ / SINR).

[0379] 25A and 25B are diagrams illustrating SR selection and association of SR with SSB according to a variation of the fourth embodiment. In Fig. 25A, the correspondence between SR (SR setting) and associated beam (here, SSB (e.g., CSI-RS, SRS, TCI state, physical cell ID (PCI) etc.)) is described.

[0380] In the example shown in Figure 25B, SR#1 to SR#6 are listed as multiple SR settings. The UE selects SR#5 based on the recommended beam (here, SSB#5).

[0381] According to the above fourth embodiment, it is possible to appropriately specify operations related to event-based beam reporting using SR and SR settings.

[0382] <Modifications of the First to Fourth Embodiments> The above different embodiments / options may be applied to different purposes / scenarios.

[0383] For example, the different purposes / scenario may be event-based beam reporting for MIMO and event-based beam reporting for mobility / LTM.

[0384] For example, in the case of MIMO (e.g., when the target is not a cell switch but beam management), UCI-based beam reporting (e.g., the second, third, or fourth embodiment) may be applied. Since beam instruction can be performed in a relatively short time (e.g., several ms), it is preferable to use UCI to prevent delays in beam reporting.

[0385] For example, in the case of mobility / LTM (e.g., when a cell switch is the target), MAC CE-based beam reporting (e.g., the first embodiment described above) may be applied. Since a cell switch requires a delay of several tens of ms and the delay of the beam reporting is unlikely to be a problem, it is preferable to use MAC CE.

[0386] <Fifth embodiment> The fifth embodiment relates to responses (e.g., ACK / NACK) related to event-based beam reporting.

[0387] The following embodiments may be applied, for example, assuming at least one of the following options 5-1 to 5-8: Option 5-1: A MAC CE with beam report information for an event-based beam report is transmitted in a PUSCH (DG PUSCH) scheduled by a dynamic grant (DCI). Option 5-2: A MAC CE with beam report information for an event-based beam report is transmitted in a CG PUSCH. Option 5-3: Beam report information for an event-based beam report is transmitted by SP-CSI in a PUSCH. Option 5-4: Beam report information for an event-based beam report is transmitted by A-CSI in a PUSCH. Option 5-5: Beam report information for an event-based beam report is transmitted by new UCI / (extended) CG-UCI / (extended) UTO-UCI in a CG-PUSCH. Option 5-6: Beam report information is transmitted by SR transmission (e.g., beam report information relating to the best beam is implicitly transmitted by SR). Option 5-7: SR transmission is performed, followed by the above options 5-1 / 5-2 / 5-3 / 5-4 / 5-5 / 5-6. Option 5-8: Beam report information for event-based beam reporting is transmitted using normal (existing) UCI / PUCCH.

[0388] For DG / CG PUSH in options 5-1 / 5-2 / 5-3 / 5-4 / 5-5 / 5-7, the UE may determine that the reception of a UL grant (and the NDI field of the DCI) of a PDCCH whose CRC is scrambled by a specific RNTI (e.g., C- / TC- / CS-RNTI) of the same HARQ process ID (HARQ process number (HPN)) as the PUSH transmission is an ACK / NACK for the event-based beam report.

[0389] For example, the UE may determine that an UL grant for the same HPN (and a predefined first NDI value (e.g., 0) or a toggled NDI value) is an ACK for an event-based beam report.

[0390] For example, the UE may determine that an UL grant for the same HPN (and a predefined second NDI value (e.g., 1) or an NDI value that is not toggled) is a NACK for an event-based beam report.

[0391] In this case, the CRC associated with the UL grant may be addressed / scrambled by a specific RNTI (eg, CS-RNTI).

[0392] A specific timer may be defined / configured to control the effective ACK / NACK feedback period.

[0393] For example, the timer may be started when a MAC CE / UCI for an event-based beam report is transmitted.

[0394] For example, if the timer expires and the UE does not receive an UL grant, the UE may determine that the event-based beam reporting has failed (a NACK has been received).

[0395] According to the above fifth embodiment, the response related to the event-based beam report can be appropriately defined.

[0396] Sixth Embodiment The sixth embodiment is a partial modification of the first embodiment.

[0397] For event-based beam reporting after a specific timer, UE autonomous CG PUSCH retransmission for a specific HPN may be supported.

[0398] The specific timer may be, for example, a timer for retransmission of a beam report. For one HARQ process, a timer for retransmission of a beam report (e.g., cg-BeamReport-RetransmissionTimer) may be defined / configured. The UE may control retransmission of beam report information based on the timer.

[0399] The timer for retransmission of the beam report (e.g., cg-BeamReport-RetransmissionTimer) may correspond to the period after transmission / retransmission for the configured grant for the HARQ process of the first transmission of the MAC CE / new UCI for the event-based beam report, for example, when the UE does not autonomously initiate retransmission in the HARQ process.

[0400] The UE may decide autonomously not to retransmit the CG with the MAC CE / new UCI for the beam report while the timer for retransmission of the beam report is running / starting.

[0401] A timer for retransmission of a beam report (e.g., cg-BeamReport-RetransmissionTimer) may be started / restarted for at least one of the CG PUSCH for the initial transmission of a MAC CE / new UCI for an event-based beam report and the retransmission of the initial transmission of the MAC CE.

[0402] This embodiment may be applied in combination with the fifth embodiment.

[0403] 26 is a diagram illustrating an example of starting a timer for retransmission of a beam report according to the sixth embodiment. In the example shown in FIG. 26, the UE transmits a MAC CE / new UCI for an event-based beam report using a CG PUSCH.

[0404] In the example shown in FIG. 26 , if the HARQ process of the CG PUSCH corresponds to HARQ process number (HPN) #3, a timer for retransmitting the beam report corresponding to the HARQ process of HPN #3 is started at a specific timing (in the example shown in FIG. 26 , the start symbol of the CG PUSCH transmitting the MAC CE / new UCI).

[0405] According to the sixth embodiment described above, even when MAC CE / new UCI is used for event-based beam reporting, it is possible to appropriately retransmit autonomous beam reports.

[0406] <Seventh embodiment> The seventh embodiment relates to ACK / NACK related to event-based beam reporting.

[0407] The UE may receive an ACK / NACK for an event-based beam report (e.g., at least one of an event-based beam report transmitted using a UCI (UCI-based) and an event-based beam report transmitted using a MAC CE (MAC CE-based)) using a specific method.

[0408] For example, the UE may receive an ACK / NACK for an event-based beam report (e.g., a UCI-based / MAC CE-based event-based beam report) using a specific DCI.

[0409] The particular DCI may be, for example, a DCI of a new DCI format (specified in Rel. 19 or later), or a DCI of an existing DCI format in which the CRC is scrambled with a new RNTI (specified in Rel. 19 or later).

[0410] This embodiment may be applied to, for example, at least one of the above options 5-3 to 5-8.

[0411] A timer for ACK / NACK of event-based beam reports may be defined / set.

[0412] For example, the timer may start when UCI for event-based beam reporting is transmitted.

[0413] For example, if the UE receives a DCI in a DCI format in which the CRC is scrambled by a new RNTI before the timer expires, the UE may determine that the DCI is an ACK for the event-based beam report. Otherwise, the UE may determine that the event-based beam report has failed (a NACK has been received).

[0414] If the UE determines that the event-based beam report has failed (received a NACK), the UE may retransmit the event-based beam report.

[0415] According to the seventh embodiment described above, UE behavior regarding ACK / NACK related to event-based beam reporting can be appropriately specified.

[0416] <Eighth embodiment> The eighth embodiment relates to ACK / NACK related to event-based beam reporting.

[0417] The UE may receive ACK / NACK for an event-based beam report (e.g., a UCI-based / MAC CE-based event-based beam report) using a specific method.

[0418] At least one of the new bit fields and existing bit fields in existing DCI formats (e.g., DCI formats 0_0 / 0_1 / 1_0 / 1_1) may be utilized / reused for ACK / NACK for UCI-based event-based beam reporting.

[0419] The existing DCI format may be, for example, a DCI format in which the CRC is scrambled by an existing RNTI (e.g., C- / TC- / CS- / SP-CSI- / MCS-C-RNTI).

[0420] For example, a specific field included in a DCI format (DCI format 0_1) that schedules a PUSH, in which the CRC is scrambled by a specific RNTI (e.g., CS-RNTI), may be reused for ACK / NACK for event-based beam reporting.

[0421] The particular field may be a downlink feedback information (DFI) flag field.

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

[0423] The UE does not need to assume that both the CG DFI for unlicensed bands / shared spectrum as defined in Rel. 16 and the CG DFI for event-based beam reporting are configured at the same time.

[0424] Furthermore, when both the CG DFI for unlicensed bands / shared spectrum specified in Rel. 16 and the CG DFI for event-based beam reporting are configured simultaneously, the UE may switch operations based on the HARQ process ID after receiving the DFI indication.

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

[0426] In this case, if the UE receives an ACK, it may terminate the repeated transmission of the transport block associated with that HARQ process ID, otherwise it may continue the repeated transmission of the transport block associated with that HARQ process ID.

[0427] Also, for example, the UE may perform operations related to the CG DFI for event-based beam reporting for HARQ process IDs associated with event-based beam reporting (defined in Rel. 19 and later).

[0428] In this case, if the UE receives an ACK, the UE may decide to switch the beam / TCI state applied to the specific DL reception / UL transmission. Otherwise, the UE may decide not to switch the beam / TCI state applied to the specific DL reception / UL transmission.

[0429] In addition, the UE may continue to use the pre-configured UL resources to perform beam reporting only when it receives a NACK, or when it receives an ACK and also when it receives a NACK.

[0430] Furthermore, when both the CG DFI for unlicensed bands / shared spectrum specified in Rel. 16 and the CG DFI for event-based beam reporting are configured simultaneously, one new bit may be added to the DCI for the DFI used for event-based beam reporting.

[0431] Also, for example, a new field included in a DCI format (e.g., DCI format 0_1 / 1_1) that schedules PDSCH / PUSCH may be used for ACK / NACK for event-based beam reporting.

[0432] The field may be defined, for example, as x bits (for example, x=1).

[0433] If event-based beam reporting is configured, the new field may be included in the DCI.

[0434] For example, if a field used for ACK / NACK for an event-based beam report included in the DCI indicates a first value (e.g., 0 (or 1)), the UE may determine that it has received an ACK. Also, if a field used for ACK / NACK for an event-based beam report included in the DCI indicates a second value (e.g., 1 (or 2)), the UE may determine that it has received a NACK.

[0435] In addition, special values ​​of existing fields included in the existing DCI may be reused for ACK / NACK for UCI-based / MAC CE-based event-based beam reporting.

[0436] According to the eighth embodiment described above, ACK / NACK related to event-based beam reporting can be appropriately defined using DCI.

[0437] Ninth Embodiment The ninth embodiment relates to a (unique) search space / CORESET for event-based beam reporting.

[0438] The UE may receive ACK / NACK for an event-based beam report (e.g., a UCI-based / MAC CE-based event-based beam report) using a specific method.

[0439] The UE may receive ACK / NACK for an event-based beam report (e.g., a UCI-based / MAC CE-based event-based beam report) using a specific search space / CORESET.

[0440] A timer for ACK / NACK of event-based beam reports may be defined / set.

[0441] For example, the timer may start when UCI for event-based beam reporting is transmitted.

[0442] For example, if the UE receives a DCI of a DCI format (e.g., DCI format 0_0 / 0_1 / 1_0 / 1_1) transmitted in the specific search space / CORESET before the timer expires, the UE may determine that the DCI is an ACK for the event-based beam report. Otherwise, the UE may determine that the event-based beam report failed (a NACK was received).

[0443] If the UE determines that the event-based beam report has failed (received a NACK), the UE may retransmit the event-based beam report.

[0444] According to the above ninth embodiment, UE behavior regarding ACK / NACK related to event-based beam reporting can be appropriately specified.

[0445] <Tenth embodiment> The tenth embodiment relates to ACK / NACK related to event-based beam reporting.

[0446] The UE may receive ACK / NACK for an event-based beam report (e.g., a UCI-based / MAC CE-based event-based beam report) using a specific method.

[0447] An indication of the TCI status may be used in a response from the network (ACK / NACK for event-based beam reporting).

[0448] For example, the indication regarding the TCI status may be an indication by a TCI field included in a specific DCI (for example, DCI format 1_1 / 1-2).

[0449] Also, for example, the indication regarding the TCI state may be an indication of an (active) TCI state by a MAC CE.

[0450] The UE may determine that an instruction regarding any TCI state is a response from the NW (ACK / NACK regarding the event-based beam report). In this case, the UE may determine not to transmit the event-based beam report until a specific period has elapsed since receiving the instruction.

[0451] Furthermore, the UE may determine that an indication regarding a specific TCI state is a response from the NW (ACK / NACK related to an event-based beam report). For example, if the indication regarding the specific TCI state is related to an event-based beam report, the UE may determine that the event-based beam report has been (successfully) received in the NW. In this case, the UE may determine not to transmit an event-based beam report until a specific period has elapsed since receiving the indication.

[0452] In addition, triggering a specific beam report (e.g., A beam report) may be used for a response from the NW (ACK / NACK related to event-based beam reporting).

[0453] According to the above tenth embodiment, ACK / NACK related to event-based beam reporting can be appropriately defined.

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

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

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

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

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

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

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

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

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

[0463] At least one of the above-described embodiments may be applied only to UEs that have reported or support a specific UE capability. Note that "supporting" and "whether to support" may be interpreted as interchangeable.

[0464] The specific UE capability may indicate at least one of the following: - Supporting specific processing / operation / control / information for at least one of the above embodiments. - Supporting event-based beam reporting. - Supporting (specific) CG PUSCH configuration for event-based beam reporting. - Supporting configuration of SP-CSI reporting in PUSCH for event-based beam reporting. - Supporting configuration of A-CSI reporting in PUSCH for event-based beam reporting. - Supporting new UCI / (extended) CG-UCI / (extended) UTO-CSI in CG PUSCH configured for event-based beam reporting. - Supporting configuration of (specific) SR / PUCCH-SR for event-based beam reporting. - Supporting UE autonomous retransmission of event-based beam reporting. - Supporting UE autonomous retransmission of CG PUSCH for event-based beam reporting. - Supporting new RNTI for event-based beam reporting. Supporting a new timer for DCI detection for new RNTI for event-based beam reporting. Supporting the use / reuse of new / existing DCI fields for event-based beam reporting. Supporting (unique) search spaces / CORESETs for event-based beam reporting. Supporting a new timer for DCI detection in (unique) search spaces / CORESETs for event-based beam reporting.

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

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

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

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

[0469] (Supplementary Notes) The following inventions are supplemented with respect to one embodiment of the present disclosure. [Supplementary Note 1-1] A terminal having a control unit that determines a trigger for an event-based beam report for Multi-Input Multi-Output (MIMO) operation, and a transmission unit that transmits beam report information related to the event-based beam report on a Configured Grant Physical Uplink Shared Channel (CG PUSCH) or a Physical Uplink Control Channel (PUCCH). [Supplementary Note 1-2] The terminal according to Supplementary Note 1-1, wherein the beam report information is transmitted using a Medium Access Control (MAC) control element or uplink control information. [Supplementary Note 1-3] The terminal according to Supplementary Note 1-1 or Supplementary Note 1-2, wherein the transmission unit transmits a scheduling request related to the event-based beam report. [Supplementary Note 1-4] The terminal according to any one of Supplements 1-1 to 1-3, wherein the control unit controls retransmission of the beam report information based on a timer related to retransmission of the event-based beam report. [Supplementary Note 2-1] A terminal having a control unit that determines a trigger for an event-based beam report for mobility operation, and a transmission unit that transmits beam report information related to the event-based beam report on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH). [Supplementary Note 2-2] The terminal according to Supplementary Note 2-1, wherein the beam report information is transmitted using a Medium Access Control (MAC) control element or uplink control information. [Supplementary Note 2-3] The terminal according to Supplementary Note 2-1 or Supplementary Note 2-2, wherein the transmission unit transmits a scheduling request related to the event-based beam report. [Supplementary Note 2-4] The terminal according to any of Supplements 2-1 to 2-3, wherein the control unit controls retransmission of the beam report information based on a timer for retransmission of the event-based beam report. [Supplementary Note 3-1] A terminal having a transmission unit that transmits beam report information related to an event-based beam report, and a control unit that controls reception of a response to the beam report information using a specific method.[Supplementary Note 3-2] The terminal according to Supplementary Note 3-1, wherein the control unit controls retransmission of the beam report information based on a timer for retransmission of an event-based beam report. [Supplementary Note 3-3] The terminal according to Supplementary Note 3-1 or Supplementary Note 3-2, wherein the response is transmitted using at least one of specific downlink control information (DCI), a specific DCI field, a specific search space, and a specific control resource set. [Supplementary Note 3-4] The terminal according to any of Supplements 3-1 to 3-3, wherein the response is transmitted using an indication of a Transmission Configuration Indication (TCI) state.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0514] The control unit 110 may control transmission of settings related to triggering of event-based beam reporting for multi-input multi-output (MIMO) operation. The transceiver unit 120 may receive beam report information related to the event-based beam reporting on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH).

[0515] The control unit 110 may transmit a setting related to triggering an event-based beam report for mobility operation. The transceiver unit 120 may receive beam report information related to the event-based beam report on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH).

[0516] The transceiver 120 may receive beam report information related to event-based beam reporting, and the controller 110 may control transmission of a response to the beam report information using a specific method.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0535] The control unit 210 may determine a trigger for an event-based beam report for multi-input multi-output (MIMO) operation. The transceiver unit 220 may transmit beam report information regarding the event-based beam report on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH).

[0536] The beam report information may be transmitted using a Medium Access Control (MAC) control element or uplink control information (new UCI / CG-UCI / UTO-UCI).

[0537] The transceiver unit 220 may transmit a scheduling request associated with the event-based beam report.

[0538] The control unit 210 may control the retransmission of the beam report information based on a timer for retransmission of the event-based beam report.

[0539] The control unit 210 may determine a trigger for an event-based beam report for mobility operation. The transceiver unit 220 may transmit beam report information regarding the event-based beam report on a configured grant physical uplink shared channel (CG PUSCH) or a physical uplink control channel (PUCCH).

[0540] The beam report information may be transmitted using a Medium Access Control (MAC) control element or uplink control information (new UCI / CG-UCI / UTO-UCI).

[0541] The transceiver unit 220 may transmit a scheduling request associated with the event-based beam report.

[0542] The control unit 210 may control the retransmission of the beam report information based on a timer for retransmission of the event-based beam report.

[0543] The transceiver 220 may transmit beam report information related to event-based beam reporting, and the controller 210 may control reception of a response to the beam report information using a specific method.

[0544] The control unit 210 may control the retransmission of the beam report information based on a timer for retransmission of the event-based beam report.

[0545] The response may be transmitted using at least one of specific downlink control information (DCI), a specific DCI field, a specific search space, and a specific control resource set.

[0546] The response may be sent using a Transmission Configuration Indication (TCI) state indication.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal comprising: a control unit that determines a trigger for event-based beam reporting for Multi-Input Multi-Output (MIMO) operation; and a transmission unit that transmits beam reporting information regarding the event-based beam reporting on a Configured Grant Physical Uplink Shared Channel (CG PUSCH) or a Physical Uplink Control Channel (PUCCH).

2. The terminal according to claim 1, wherein the beam reporting information is transmitted using a Medium Access Control (MAC) control element or uplink control information.

3. The terminal according to claim 1, wherein the transmission unit transmits a scheduling request related to the event-based beam reporting.

4. The terminal according to claim 1, wherein the control unit controls retransmission of the beam reporting information based on a timer related to retransmission of event-based beam reporting.

5. A wireless communication method for a terminal, comprising: determining a trigger for event-based beam reporting for Multi-Input Multi-Output (MIMO) operation; and transmitting beam reporting information regarding the event-based beam reporting on a Configured Grant Physical Uplink Shared Channel (CG PUSCH) or a Physical Uplink Control Channel (PUCCH).

6. A base station comprising: a control unit that controls transmission of settings related to a trigger for event-based beam reporting for Multi-Input Multi-Output (MIMO) operation; and a reception unit that receives beam reporting information regarding the event-based beam reporting on a Configured Grant Physical Uplink Shared Channel (CG PUSCH) or a Physical Uplink Control Channel (PUCCH).

Images