Terminal, wireless communication method, and base station

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives a configuration of a (UE-initiated) beam report (UEIBR) initiated by UE; and a control unit that, on the basis of the configuration, controls the UEIBR for an event with respect to a specific use case. The control unit quantifies a current beam or a new beam in two stages.

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), it is being considered to use L1L2-triggered mobility (LTM) defined in Rel. 18 when a terminal (user terminal, User Equipment (UE)) moves between cells.

[0006] Various use cases are expected for mobility after Rel. 19. For example, in industrial communication systems, cases such as remote control of industrial equipment and factory automation can be mentioned. In addition, in real-time interactive services, AI-based / XR services can be mentioned.

[0007] Additionally, it is being considered that future wireless communication systems will support event-based beam reporting.

[0008] Event-triggered beam reporting () can be supported for MIMO / mobility in Rel. 19 and later. Conditional handover (CHO) can also be supported as a mobility aspect.

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

[0010] Event-triggered beam reporting may also be referred to as UE-initiated beam reporting (UEIBR).

[0011] On the other hand, it is expected that different use cases will support different types of beam reporting.

[0012] However, there are cases where the rules for event-based beam reporting according to the applicable use cases are not sufficiently considered. If these considerations are insufficient, it may not be possible to achieve lower latency communications, which may result in suppression of improvements in communication quality and throughput.

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

[0014] A terminal according to one aspect of the present disclosure has a receiving unit that receives a setting for a UE-initiated beam report (UEIBR), and a control unit that controls the UEIBR for an event for a specific use case based on the setting, and the control unit quantifies a current beam or a new beam in two stages.

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

[0016] Figures 1A and 1B show an example of a unified / common TCI framework. Figures 2A and 2B show an example of a CC-common TCI state pool and a CC-specific TCI state pool. Figures 3A and 3B show an example of a DCI-based TCI state indication. Figure 4 shows an example of a timeline for TCI state switching / activation defined up to Rel. 15 / 16. Figure 5 shows an example of TCI states defined up to Rel. 16. Figure 6A shows an example of UE mobility in Rel. 17. Figure 6B shows an example of UE mobility in Rel. 18. Figure 7 is a flowchart showing an example of an event-based beam reporting process. Figure 8 shows an example of a beam reporting timeline. Figure 9 shows an example of UE IBR using UCI / MAC CE. Figure 10 shows an example of a schematic configuration of a wireless communication system according to an embodiment. Figure 11 shows an example of a base station configuration according to an embodiment. Figure 12 shows an example of a user terminal configuration according to an embodiment. Fig. 13 is a diagram illustrating an example of a hardware configuration of a base station and a user terminal according to an embodiment. Fig. 14 is a diagram illustrating an example of a vehicle according to an embodiment.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] (Unified TCI Framework in Carrier Aggregation (CA)) In NR Rel. 17 and later, a unified TCI state framework in CA has been introduced. The common TCI state indicated to the UE may be common between CCs (cells) (QCL type D at least between CCs).

[0065] Also, in the unified TCI framework, common TCI state ID update / activation has been introduced to provide common QCL information / common UL transmit spatial filter across a set of configured CCs.

[0066] The TCI status pool for a CA may be either option 1 or 2 below.

[0067] <Option 1> A single TCI state pool configured by the RRC for a set of configured multiple CCs (cells) / BWPs may be shared (configured). For example, a cell group TCI state may be defined, or the TCI state pool for PDSCH in the reference cell may be reused. In the TCI state, there may be no CC (cell) ID for the QCL type A RS, and the CC (cell) ID for the QCL type A RS may be determined according to the target CC (cell) of the TCI state.

[0068] In Option 1, a common TCI state pool is configured for each of multiple CCs / BWPs, so that when one unified TCI state is indicated in the MAC CE / DCI, the indicated unified TCI state may be applied to all CCs / BWPs (all CCs / BWPs included in the pre-configured CC / BWP list).

[0069] 2A shows an example of a CC common TCI status pool. In this example, a common TCI status list is set for BWP / CC#1 and BWP / CC#2 (in the example shown in the figure, the list is set in BWP / CC#1, and the list is not set (absent) in BWP / CC#2). Then, when a TCI status indication (TCI status #4 in the example shown in the figure) is given for BWP / CC#1, which is the reference BWP / CC, the TCI status of BWP / CC#2, which is the target BWP / CC, is also updated accordingly.

[0070] In addition, in option 1, a common TCI state pool is configured (shared) by RRC for multiple CCs, the TCI states in the common TCI state pool are indicated by a common TCI state ID, and one RS determined based on the TCI state may be used to indicate QCL type D across the set of multiple configured CCs / BWPs.

[0071] <Option 2> A TCI state pool may be configured by the RRC for each individual CC.

[0072] In Option 2, similar to Rel. 16, a list of CCs / BWPs to which simultaneous beam updates are applied is pre-configured by the RRC, and if a beam update is performed in the MAC CE / DCI for any CC / BWP included in the CC / BWP list, the update may be applied to all CCs / BWPs.

[0073] 2B shows an example of a CC-specific TCI status pool. In this example, a unique TCI status list is configured for each of BWP / CC #1 and BWP / CC #2. Then, when a TCI status indication (TCI status #4 in the example shown) is issued for BWP / CC #1, the TCI status of BWP / CC #2 is updated accordingly.

[0074] In addition, in option 2, a separate common TCI state pool may be configured by RRC for each CC, the TCI states in the unified TCI state pool may be indicated by a unified TCI state ID, and one RS determined based on the TCI state may be used to indicate QCL type D across a set of multiple configured CCs / BWPs.

[0075] Furthermore, in Rel. 17, up to four CC lists (for example, upper layer parameter simultaneousTCI-UpdateList1-r17) may be configured for each cell group.

[0076] When the TCI status in the list is indicated using MAC CE / DCI, the TCI status of the same ID may be applied to all BWPs / CCs in the CC list.

[0077] (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

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

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

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

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

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

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

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

[0085] 3A 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.

[0086] 3B shows an example of DCI-based separate DL / UL TCI status indication. At least one TCI state ID, indicating a DL-only TCI state or indicating a UL-only TCI state, 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 state ID for DL, TCI field values ​​010 to 011 are associated with only one TCI state ID for UL, and TCI field values ​​100 to 111 are associated with both one TCI state ID for DL ​​and one TCI state ID for UL.

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

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

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

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

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

[0092] (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:

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

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

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

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

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

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

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

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

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

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

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

[0104] 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 applied by the UE is undefined (see Figure 4).

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

[0106] 5 is a diagram showing an example of the TCI state defined up to Rel. 16. As shown in FIG. 5, 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). In addition, 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0129] 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, the UE 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0148] Figure 6A 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.

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

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

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

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

[0153] Figure 6B 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0179] (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, and may mean UE-initiated beam reporting.

[0180] Examples of events defined in existing 5G NR include the following. Note that the events are not limited to those shown below, and other new events may be defined. Event A1: A case in which the measurement result of the serving [cell] is better than a threshold. Event A2: A case in which the measurement result of the serving [cell] is worse than a threshold. Event A3: A case in which the measurement result of the neighboring [cell] (a value obtained by adding an offset to the measurement result) is better than the measurement result of the SpCell (a value obtained by adding an offset to the measurement result). Event A4: A case in which the measurement result of the neighboring [cell] (a value obtained by adding an offset to the measurement result) is better than a threshold. Event A5: A case in which the measurement result of the SpCell is worse than a first threshold, and the measurement result of the neighboring [cell] (a value obtained by adding an offset to the measurement result) is better than a second threshold. Event A6: A case where the measurement result of the neighboring [cell] (a value obtained by adding an offset to the measurement result) is better than the measurement result of the serving cell (Secondary Cell (SCell)) (a value obtained by adding an offset to the measurement result). Event B1: A case where the measurement result of the inter-RAT neighboring [cell] is better than a threshold. Event B2: A case where the measurement result of the PCell is worse than a first threshold, and the measurement result of the inter-RAT neighboring [cell] (a value obtained by adding an offset to the measurement result) is better than a second threshold.

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

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

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

[0184] <<Events for Case 1>> A description will be given of an example of an event for the above-mentioned Case 1. 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.

[0185] <<<Option 1>>> A beam report (e.g., 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.

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

[0187] 7 is a flowchart showing an example of an event-based beam reporting process. The UE determines whether an event (for example, 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. 7 may be repeatedly performed at predetermined intervals.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0220] (Triggering Conditions (Events) for Event-Based Beam Reporting for Rel. 19) An event-triggered [L1] beam report may be triggered when certain conditions (events) are met. For example, the UE may apply different / same conditions / events to trigger the following beam reports:

[0221] UE Feature #1: Event-triggered [L1] beam reporting for MIMO in Rel. 19. UE Feature #2: Event-triggered [L1] beam reporting for mobility in Rel. 19.

[0222] Different UE capabilities may be introduced / defined between UE features #1 and #2. Also, different upper layer parameters may be set to enable each UE feature. UE features and UE capabilities may be interchangeable.

[0223] The UE does not expect UE features #1 and #2 to be configured simultaneously in a given BWP / CC / band / frequency band / frequency (or for each UE).

[0224] Alternatively, the UE may be configured with UE features #1 and #2 simultaneously in a certain BWP / CC / band / frequency band / frequency band (or for each UE). For example, if configured, the UE may predefine which event (which UE feature) to prioritize, and this may be configured / instructed by higher layer signaling / physical layer signaling.

[0225] The present disclosure may be applied in the unified TCI framework (of Rel. 15 / 16 / 17 / 18).

[0226] The present disclosure may apply only if the corresponding UE capabilities are reported, or alternatively, the present disclosure may apply only if the corresponding higher layer parameters (e.g., RRC) are signaled / reported.

[0227] <Beam Reporting for MIMO> Regarding event-triggered beam reporting for MIMO in Rel. 19, the following may apply.

[0228] MAC CE in PUSCH. UCI in periodic / semi-persistent PUCCH, UCI in dynamic grant (DG) / configuration grant (CG) PUSCH. Relationship between the MAC CE-based method and the UCI-based method described above. For example, two independent methods may be configurable. Alternatively, a UCI-based method may be applicable in addition to a MAC CE-based method (a combination of the two methods (2-step method) may be applied).

[0229] The report content may be basically the same as the existing L1 beam measurement report, and may include, for example, at least one of the following: - SSBRI / CRI. - Number of beams to be reported X. - Selection method for the X beams. - L1-RSRP / SINR (absolute value / differential value) for each SSBRI / CRI. - If MAC CE is used, an indicator showing whether the following octets are included: - If MAC CE is used or UCI is used, serving cell ID, BWP ID (if the report requests activation of TCI state or beam switching).

[0230] <Beam Reporting for Mobility> Regarding event-triggered beam reporting for mobility in Rel. 19, it is necessary to clarify whether event-triggered beam reporting is utilized for reporting cell switches. For example, the following may apply:

[0231] MAC CE in semi-persistent / aperiodic PUSCH. UCI in periodic / semi-persistent PUCCH, UCI in semi-persistent / aperiodic PUSCH.

[0232] The report content may include, for example, at least one of the following: If the measurement report is used for cell switch reporting, in addition to the MIMO-related information: An indicator indicating whether a cell switch has occurred or not, or TA-related information; Otherwise (if the measurement report is not used for cell switch reporting), The same content as the MIMO-related information (which may only differ in whether it is intra-cell / inter-cell).

[0233] The supported events may be similar to Conditional Hand-Over (CHO).

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

[0235] If reporting is used for cell switch commands, specific domain filters (eg time / frequency / space) may be considered / applied to prevent frequent switches.

[0236] It may also be specified whether flexibility in triggering time (eg, 5 ms, 10 ms, 20 ms) is required.

[0237] <Definition of Wording for Specific Events> In the existing events described above, the definitions of serving (cell) and neighbor (cell) may be rephrased / updated as follows in event-triggered beam reporting for Rel. 19:

[0238] For example, the serving cell, SpCell, and PCell in existing L3 events may be interchangeably referred to as the current beam (e.g., the RS ID associated with the indicated [joint / DL] TCI state) in event-triggered beam reporting for Rel. 19 MIMO.

[0239] Furthermore, the serving [cell], SpCell, and PCell in existing L3 events may be interchangeably read as the current beam (e.g., RS ID associated with the indicated [joint / DL] TCI state) or the beam of the serving cell (e.g., RS ID associated with the TCI state for the PCI of the serving cell) in event-triggered beam reporting for Rel. 19 mobility.

[0240] Neighbors in existing L3 events may be interchanged with other beams (e.g., RS IDs not associated with the indicated [joint / DL] TCI state but associated with RS IDs for L1 beam measurements) in event-triggered beam reporting for Rel. 19 MIMO (which may be mobility).

[0241] Additionally, the neighbor [cell] in the existing L3 event may be interchangeably read as the beam of a non-serving cell / target cell / candidate cell (e.g., RS ID associated with the TCI state for the PCI of the target cell / candidate cell) in event-triggered beam reporting for Rel. 19 mobility.

[0242] The measurement value for each reference signal (RS) may be RSRP / SINR, L3-RSRP / SINR, L1-RSRP / SINR, or an average value of multiple L1-RSRP / SINRs.

[0243] For example, L1-RSRP / SINR may change dynamically, so by averaging multiple (X) L1-RSRP / SINR values ​​(e.g., X=5), control hunting (frequent switching of trigger states) in beam reporting triggering can be avoided.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0270] <Aspect 3> 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.

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

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

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

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

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

[0276] <Aspect 4> 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.

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

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

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

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

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

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

[0283] The ACK / NACK of the above-described aspects 1 to 4 may be referred to as an ACK / NACK of (from) the gNB. In particular, the ACK of the gNB may be used to trigger the beam report described below.

[0284] (Transmission of Beam Report Using MAC CE / UCI) The event-triggered beam report described above can be supported in MIMO / mobility in Rel. 19 and later. Conditional handover (CHO) can also be supported as a mobility aspect.

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

[0286] It is also expected that different types of beam reports will be supported for each of the above use cases.

[0287] For example, event-triggered beam reporting for MIMO in Rel. 19 supports Type 1 / Type 2-1 beam reporting, and event-triggered beam reporting for mobility in Rel. 19 supports Type 2-2 beam reporting.

[0288] In addition, it is necessary to consider what container (e.g., MAC CE or UCI) should be used to transmit these beam reports. Regardless of whether MAC CE or UCI is used, various rules associated with them must be clarified for the beam reports.

[0289] <Container for Beam Report> As mentioned above, a UE-initiated beam report is triggered when a specific event set by the NW is met, because if no event is set by the NW, the NW cannot know the reason for sending the beam report (the purpose of the beam report is unknown).

[0290] For example, the above-mentioned events A3 / A5 can use existing parameters (threshold, offset, etc.), but these parameters need to be further expanded to achieve high-speed beam reporting.

[0291] 8 is a diagram showing an example of a time sequence of beam reporting. UE-initiated beam reporting (UEIBR), event-driven beam reporting, event-based beam reporting, etc. may be read as interchangeable terms.

[0292] The upper half of Figure 8 shows an example of event-based beam reporting. The UE evaluates events set in the network based on the trigger conditions for beam reporting. If the predetermined conditions are met, the UE initiates beam reporting.

[0293] Specifically, the UE may send a scheduling request (SR) and may send DCI for (including) an UL grant, after which the UE may send a beam report.

[0294] The bottom half of Figure 8 is an example of non-event-based (non-UE initiated) beam reporting. The UE may trigger and perform beam reporting according to terminal implementation (terminal specific timing).

[0295] Specifically, the UE may send a scheduling request (SR) and may send DCI for (including) an UL grant, after which the UE may send a beam report.

[0296] In event-independent beam reporting, beam reporting may be triggered at terminal-specific timing. In this case, the NW (gNB) may frequently report that the UE has started beam reporting. As a result, UL resources may be wasted, which may affect UE control.

[0297] Regarding event-based beam reporting, the following items are being considered:

[0298] (Report Content) The following report contents may be supported: SSB / CSI-RS based measurements. L1-RSRP / L1-RSRP / SINR measurements.

[0299] The number of beams reported may be variable, in which case the UE may determine / decide how many beams to report, since if multiple beams are eligible (valid), it is preferable to report on multiple (all) of these beams.

[0300] In addition, whether or not to include the serving beam (current beam) in the report may be configurable, since this is convenient for the network side to compare the current beam with adjacent beams.

[0301] For example, the UE may determine the use of a reporting container (MAC CE / UCI) based on the report content, or may determine whether the beam report is for mobility or MIMO based on the report content.

[0302] More specifically, if the UE is configured / instructed to include either the serving beam or the non-serving beam in the report, the UE may perform beam reporting using the MAC CE (e.g., in the case of mobility), or if the UE is configured / instructed to include only the serving beam in the report (and not to report non-serving beams), the UE may perform beam reporting using the UCI (e.g., in the case of MIMO).

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

[0304] Alternatively, the UE may switch between performing beam reporting using MAC CE (e.g., in the case of mobility) and performing beam reporting using UCI according to a higher layer instruction. The higher layer parameter for configuring beam reporting using MAC CE may be a parameter related to mobility / cell switching. The higher layer parameter for configuring beam reporting using UCI may be a parameter not related to mobility / cell switching.

[0305] This allows the UE to appropriately control beam reporting according to the report content.

[0306] (Report Container) MAC CE or UCI may be used as a container for the beam report. That is, the UE may use MAC CE or UCI to perform / control the transmission of the beam report described above. Specific examples thereof will be described below with reference to aspects 1-1 and 1-2.

[0307] <<Aspect 1-1>> Aspect 1-1 relates to beam reporting using MAC CE.

[0308] The beam report using MAC CE may be applied, for example, in a mobility scenario (such as a Type 2-2 L1 beam report). However, the beam report is not limited to this and can be applied to any scenario (such as MIMO).

[0309] At least one of the following methods can be applied to request an UL grant for the MAC CE.

[0310] (Alt1) Use existing SR (PUCCH-SR resource).

[0311] (Alt2) Configure a dedicated SR (PUCCH-SR resource) for event-based beam reporting.

[0312] The dedicated SR may be used to request an UL grant for the MAC CE in question when sufficient resources are not available on the UL shared channel (e.g., PUSCH).

[0313] MAC CE allows transmitting (including) more information depending on the number of beams without reserving resources in advance, and is therefore more useful when the number of beams reported is variable.

[0314] Furthermore, MAC CE can reduce the impact on existing specifications.

[0315] <<Aspect 1-2>> Aspect 1-2 relates to beam reporting using UCI.

[0316] The beam report using UCI may be applied, for example, in a MIMO scenario (such as L1 beam report of type 1 / 2-2). However, the beam report is not limited to this and can be applied to any scenario (for example, mobility).

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

[0318] (Alt1) UL resources for transmitting (carrying) beam reports may be dynamically scheduled by DCI. For example, the UE may send dedicated signaling (e.g., SR-like signaling) to the NW to declare an event. Then, existing aperiodic / semi-persistent beam reporting may be triggered / activated by DCI.

[0319] (Alt2) The UL resources for transmitting (carrying) the beam report may be pre-configured by [dedicated] higher layer signaling, e.g., a configuration for a configured grant PUSCH or a configuration for a dedicated PUSCH similar to MsgA-PUSCH may be used (and provided to the UE).

[0320] Note that the ACK for the PUSCH in Alt2 may have a toggled NDI field value at the last symbol of a PDCCH reception containing a DCI format that schedules a PUSCH transmission with the same HARQ process number as the initial PUSCH transmission. The transmission of the ACK for the PUSCH may start after the last symbol of the MAC CE for the PUSCH (see, for example, FIG. 8).

[0321] <<Comparison Between UCI and MAC CE>> An example comparing UCI-based beam reporting and MAC CE-based beam reporting will be described with reference to Fig. 9. Fig. 9 is a diagram illustrating an example of UEIBR using UCI / MAC CE.

[0322] As shown in Figure 9, UCI allows a UE to report with a relatively short delay after a specific event occurs. That is, UCI allows the reporting delay to be reduced. In this case, it is expected that the impact on specifications will be large. Also, more UL (PUCCH / PUSCH) resources will need to be reserved.

[0323] On the other hand, in the case of MAC CE, after a specific event occurs, the UE needs to receive DCI for the UL grant, transmit MAC CE via PUSCH, receive ACK for the PUSCH, etc. Therefore, a large delay may occur until the report is executed (completed). MAC CE not only allows more information to be transmitted, but also reduces the impact on existing specifications.

[0324] (UEIBR Procedure) As a UEIBR procedure, the UE may apply one of the following options depending on the type of container (UCI / MAC CE) used.

[0325] <<Option 1: MAC CE>> Step 1: The UE sends an SR requesting an UL shared channel resource (e.g., a PUSCH resource) when a trigger event occurs (a specific event is met). Step 2: The UE detects the DCI format for the UL grant. Step 3: The UE sends a beam report using a MAC CE included in a new PUSCH transmission (the MAC CE carries the beam report).

[0326] Steps 1 and 2 may be skipped if PUSCH resources are available for new transmissions.

[0327] The MAC CE may be transmitted on dynamically scheduled resources or on semi-statically configured resources.

[0328] <<Option 2+3: UCI>> Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is an UL channel that notifies / requests a second UL channel (e.g., PUCCH) for transmitting a beam report in advance, and may consist of one or more bits. Step 2: The UE detects a DCI format indicating a second UL channel resource. This DCI format may be assumed to be a response from the NW to step 1. Note that step 2 may be enabled by RRC configuration from the NW. Step 3: The UE transmits a beam report using resources (UCI) on the second UL channel.

[0329] If step 2 is enabled by RRC configuration from the NW, the resource for reporting (second UL channel resource) may be determined from pre-configured UL resources or may be scheduled by the DCI format.

[0330] Regardless of whether step 2 is enabled, the resource for reporting (second UL channel resource) may be determined from the pre-configured UL resource.

[0331] A UE capability to enable step 2 may be introduced.

[0332] The notification of step 1 may be included in a separate reporting instance from the beam report of step 3.

[0333] Option 2+3 may be referred to as Mode A, which will be described below.

[0334] <<Option 4: UCI (Pre-configured Resources Not Dedicated to UEIBR)>> Step 1: When a trigger event occurs (a specific event is met), the UE sends a beam report using pre-configured resources. The pre-configuration (notification) may be realized by a part of the beam report. For example, like a two-part UCI, Part 1 may indicate information of Part 2, and Part 2 may be used to send the beam report.

[0335] The two-part UCI may be transmitted on the same PUCCH / PUSCH.

[0336] In each of the above options, the UE may or may not receive an ACK from the NW for each step.

[0337] In this way, the UE can control the transmission of the UEIBR depending on the type of container.

[0338] (UCI-based UEIBR) In the UCI-based UEIBR procedure, the following modes may be supported.

[0339] Mode A relates to dynamic scheduling of UCI by the NW (gNB). That is, in Mode A, resources for UCI are scheduled by the gNB. Mode A may be a basic function of the UE (a UE that supports UE IBR may naturally support this function).

[0340] Step 1: The UE transmits a first UL channel (e.g., PUCCH), which may consist of one or more bits, that notifies / requests a second UL channel (e.g., PUCCH) for transmitting a beam report.

[0341] Step 2: The UE detects the DCI format indicating the second UL channel resource.

[0342] Step 3: The UE transmits a beam report using resources (UCI) on the second UL channel.

[0343] Mode B Mode B relates to UCI within pre-configured resources for the second UL channel.

[0344] Step 1: The UE transmits a first UL channel (e.g., PUCCH). The first UL channel is an UL channel that indicates a second UL channel for transmitting a beam report and may be configured with one or more bits. The first UL channel may be configured with one or more bits.

[0345] Step 2: The UE transmits a beam report in the second UL channel (e.g., using specific resources (UCI) within the channel).

[0346] Note that the notification in step 1 may be included in a separate reporting instance from the beam report in step 2.

[0347] In either of the above-mentioned modes A / B, cross-CC (component carrier) beam reporting may be supported.

[0348] (Event Detection (Event Trigger Use Case #1)) In UEIBR, it is considered that specific events (e.g., at least Event 2) will be supported for trigger event detection of beam reporting.

[0349] For example, for a particular event (eg, event 2), it may be supported that at least L1-RSRP is used as a quality indicator.

[0350] Event 2 may be, for example, the quality (eg, L1-RSRP) of at least one new beam becoming better than a certain threshold compared to the quality of the current beam.

[0351] That is, at least L1-RSRP may be supported as the quality metrics used in event 2.

[0352] Here, it is considered how the L1-RSRP is used to determine the trigger event (e.g., timer, counter, filter coefficient, etc.) It also needs to be considered whether the NW controls how the L1-RSRP is used to determine the trigger event.

[0353] Also, in a particular event (e.g., event 2), the "current beam" may be a beam corresponding to the indicated TCI state. More specifically, the "current beam" may be determined / derived based on the QCL RS (e.g., QCL source RS) of the indicated TCI state. In this case, the QCL RS of the indicated TCI state may support at least one of SSB and CSI-RS.

[0354] For example, for the "current beam" in a particular event (e.g., event 2), at least one of the following beam options 2a and 2c may be supported: Beam option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS of the indicated TCI state. Beam option 2c: The RS corresponding to the current beam is explicitly configured / indicated using RRC signaling / MAC CE.

[0355] For example, for a "new beam" in event 2, at least one of the following beam options 3a to 3c may be supported: Beam option 3a: The RS corresponding to the new beam is configured [explicitly] using RRC signaling (e.g., reconfiguration of existing RS measurements or configuration parameters of the TCI state (e.g., TCI-State)) / MAC CE. Beam option 3b: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of the activated TCI state (active TCI state). Beam option 3c: The RS corresponding to the new beam is [implicitly] derived / determined based on the QCL RS of one or more configured TCI states (configured TCI states).

[0356] In the implicit method described above, if there are multiple (two) QCL RSs in the TCI state, the measurement RS may be derived / determined from the QCL type D RS.

[0357] Furthermore, the quality index is not limited to L1-RSRP, but may be L1-SINR.

[0358] Note that the beam option names in this disclosure are merely examples and are not limited to the examples in this disclosure.

[0359] In this disclosure, UEIBR based on Event 2 is UEIBR Use Case #1 (which may simply be referred to as Use Case #1). In Event 2, the "current beam" is one beam and corresponds to the indicated TCI state as described above.

[0360] According to use case #1, it is possible to help the gNB update the indicated TCI state [by DCI], i.e., use case #1 may be [by the gNB] updating the indicated TCI state indicated [by DCI].

[0361] In the event for Use Case #1 (i.e., Event 2), it is sufficient for the beam report to include "new beam" and the measurement values ​​(L1-RSRP / SINR) of the new beam. In other words, the beam report does not necessarily include the measurement values ​​(L1-RSRP / SINR) of the current beam.

[0362] (Event Variations (Event Trigger Use Case #2)) In addition to Event 2 described above, the following trigger events are considered: Event 1: The quality of the current beam becomes worse than a certain threshold. Event 3: The quality of a new beam becomes better than a certain threshold. Event 4: The quality of the current beam becomes worse than a first threshold and the quality of at least one new beam becomes better than a second threshold. Event 5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam becomes smaller than a certain threshold. Event 6: The current beam is no longer included in the best K (greater than 1: K>1) beams (among the beams configured for measurement / reporting). Event 7a: The quality (e.g., L1-RSRP) of at least one new beam becomes a threshold better than the RS derived from the activated (active) TCI state with the worst quality. Event 7b: The quality (e.g. L1-RSRP) of at least one new beam reaches a threshold better than the RS derived from the best quality activated (active) TCI state. Event 8: The quality (e.g. L1-RSRP) of M (more than 1: M>1) new beams reaches a threshold better than the current beam. Event 9: The quality (e.g. L1-RSRP) of at least one new beam reaches a threshold better than the configured reference RS (which may be SSB / CSI-RS).

[0363] At least one of these events may apply to another use case of UEIBR, which may be called use case #2, which may be updating the TCI state activated (by MAC CE).

[0364] In Use Case #2, it is preferable to treat the RS derived / determined from the currently activated (active) TCI state as the current beam.

[0365] The "current beam" may be one of the following options Opt1 to Opt2: (Opt1) One RS / beam selected from the activated (active) TCI state with the worst / best quality. Alternatively, one RS / beam with the worst / best quality selected from the activated (active) TCI state. (Opt2) Multiple (e.g., X) RSs / beams selected from the activated (active) TCI state. The value of X may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities.

[0366] In the above-mentioned use case #1, it was sufficient to include [information (measurements, etc.)] about the new beam in the beam report, but in use case #2, it is assumed that including the new beam alone is not sufficient. For example, in event 1, information about the new beam will not be included in the beam report (because only the current beam is of interest).

[0367] That is, the beam report about the event for use case #2 needs to be different than for use case #1.

[0368] Thus, it is necessary to clarify the provisions regarding beam reporting according to the use case of UEIBR.

[0369] (Analysis) If the regulations regarding beam reporting according to the above-mentioned UEIBR use cases are not clear, it may not be possible to achieve communication with lower latency, which may result in suppression of improvement in communication quality / throughput.

[0370] Therefore, the present inventors have conceived a new method for UEIBR.

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

[0372] (Various Reinterpretations) In the present disclosure, a word enclosed in "( )" in a sentence may indicate an explanation of the word immediately preceding it (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Furthermore, in the present disclosure, a word enclosed in "[ ]" in a sentence may be interpreted including the word in the meaning of the entire sentence, or may be interpreted excluding (ignoring) the word in the meaning of the entire sentence. Note that "( )" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

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

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

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

[0379] In the present disclosure, the terms drop, abort, cancel, puncture, rate match, postpone, do not transmit, etc. may be read interchangeably.

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

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

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

[0383] 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) and L1 / L2 inter-cell mobility may be interchangeable.

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

[0385] In the present disclosure, event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, and UE-initiated beam reporting (UEIBR) may be read interchangeably.

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

[0387] In the present disclosure, Type 1 beam report and beam report for intra-cell beam switching may be read interchangeably.

[0388] In the present disclosure, Type 2 beam report and inter-cell beam report may be read interchangeably.

[0389] In the present disclosure, Type 2-1 beam report and beam report for inter-cell beam switching may be read interchangeably.

[0390] In the present disclosure, Type 2-2 beam report and beam report for cell switching may be read interchangeably.

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

[0392] In the present disclosure, the terms list and pool may be read interchangeably.

[0393] In the present disclosure, the (new) MAC CE, UCI, cell switch command, beam switch command, beam report MAC CE, and cell switch MAC CE may be read as interchangeable terms.

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

[0395] In the present disclosure, CSI report, beam report, and report may be read interchangeably.

[0396] In the present disclosure, the terms report, resource for report, and resource may be interchangeable. For example, a first resource and a first report may be interchangeable, and a second resource and a second report may be interchangeable.

[0397] In the present disclosure, the number of beams and the number of resources may be read interchangeably.

[0398] In the present disclosure, the RS to be measured may be a QCL source RS in an active / indicated TCI state.

[0399] In the present disclosure, the terms serving cell, cell, CC, BWP, and frequency may be interchangeable.

[0400] In the present disclosure, the terms activated TCI state, active TCI state, and active TCI state list may be read interchangeably.

[0401] In this disclosure, updating a TCI state may refer to updating an active TCI state list.

[0402] In the present disclosure, the occurrence of an event and the satisfaction of the conditions for the event may be read interchangeably.

[0403] In the present disclosure, the terms beam, RS, and [L1 / L3] measurement result may be interpreted interchangeably.

[0404] In the present disclosure, NW / BS / gNB may be interpreted interchangeably.

[0405] In the present disclosure, CSI reports and beam reports may be read interchangeably.

[0406] In the present disclosure, the terms event-based beam reporting (for Rel. 19), event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), and beam reporting may be interchangeable.

[0407] In the present disclosure, QCL Type A and QCL Type D may be read interchangeably.

[0408] In the present disclosure, the active TCI state list, the TCI state, and the active TCI state may be read interchangeably.

[0409] In the present disclosure, the terms TCI state, RS (source RS), beam, and L1-RSRP / SINR may be interchangeable.

[0410] (Wireless communication method) The embodiments of the present disclosure can be broadly categorized as follows: First embodiment: UEIBR when there is one current beam. Second embodiment: UEIBR when there are multiple current beams. Third embodiment: Quantization of measurement values ​​in UEIBR. Fourth embodiment: UEIBR when event 1 is set. Each embodiment will be described below based on these.

[0411] The UE may perform beam measurement / reporting (e.g., UE IBR) by applying the present disclosure. The NW / BS / gNB may provide / send to the UE settings / instructions, etc. for the UE to realize the control. Furthermore, the NW / BS / gNB may perform various controls necessary to receive the beam report / CSI report from the UE.

[0412] The event-based beam reporting of the present disclosure can be applied to any MIMO / mobility scenario in Rel. 19 and later. For example, in the mobility case, the UE may determine the cell to switch to based on the determined current beam.

[0413] The present disclosure is applicable to each of the MIMO / mobility use cases.

[0414] In the present disclosure, each embodiment / option may be applied alone or in combination with other embodiments / options.

[0415] As described above, in the present disclosure, the "current beam" may be any of the following Opt1 to Opt2: (Opt1) One RS / beam selected from the activated (active) TCI state with the worst / best quality. Alternatively, one RS / beam with the worst / best quality selected from the activated (active) TCI state. (Opt2) Multiple (e.g., X) RSs / beams selected from the activated (active) TCI state. The value of X may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities.

[0416] The following embodiments mainly illustrate use case #2 (a case in which an event other than event 2 is triggered), but are not limited to this. The following embodiments can also be applied to use case #1.

[0417] First Embodiment The first embodiment relates to the case where there is one current beam.

[0418] <<Beams to be reported>> If the current beam corresponds to Opt1 described above, the beam report for use case #2 may have the same design / content as the beam report for use case #1. For example, in use case #2, if there is one current beam, the beam report may include [only] information about the new beam. In other words, the beam report may not include information about the current beam. Alternatively, the beam report may include information about the current beam.

[0419] In Use Case #2, at least one of the above-described Events 3 to 9 may be set. That is, a new beam may be set / measured. Events 3 to 9 may be referred to as events related to a new beam.

[0420] In a beam report for an event for use case #2 (beam report for use case #2), the gNB sets the number of beams to be reported (which may also be referred to as the number of beams to be reported, the number of beam reports, etc.) N. Here, N is the total number of beams to be reported, and can be set for each reporting configuration (CSI-ReportConfig) / BWP / CC / serving cell.

[0421] For beam reporting for use case #2, at least one of the following options (including variations) may be applied:

[0422] (Opt1-A) N indicates the number of new beams to be reported. In this case, the current beam may not be included in the beam report (the current beam may not be reported).

[0423] (Opt1-B) N indicates the total number of beams to be reported (including new beams and current beams), i.e., the current beam may be reported.

[0424] (Opt1-B-1) A beam report may be predefined to always include the current beam. For example, a beam report may include (N-1) new beams and one current beam.

[0425] (Opt1-B-2) The gNB may configure whether the current beam is included in the beam report.

[0426] (Opt1-B-3) The UE may determine / judge whether the current beam is included in the beam report. In this case, the UE may notify the gNB whether the current beam is reported or whether the reported beam is the current beam.

[0427] (Variation 1) N may indicate the number of new beams to be reported. The number of current beams (e.g., 1) may be set / indicated by higher layer signaling / physical layer signaling or may be predefined by a specification. In this case, the total number of beams to be reported may be N+1.

[0428] (Variation 2) At least one of the new beams to be reported must satisfy the event condition. That is, the new beams to be reported may include beams that do not satisfy the condition. Alternatively, if no suitable new beam is found (if no beam satisfies the condition), zeros may be padded.

[0429] (Variation 3) N may be determined by the UE based on the maximum number of reports N_max. N_max indicates the maximum number of beams to be reported and may be set / instructed by the gNB or may be predefined by specifications. The UE may instruct the gNB of N through the PUCCH in step 1. Alternatively, N may be predefined by specifications.

[0430] (Modification 4) The settings for use case #1 may be applied to use case #2.

[0431] (Note) Depending on the number of current beams, the following options may be selected: (Option 1) If there is one current beam, the UE may include the current beam in the beam report even if the current beam has worse measurement results than the new beam. (Option 2) If there are multiple current beams, a specific current beam (e.g., the beam with the worst / best quality) may be reported in preference to the new beam. Other current beams may not be included in the beam report.

[0432] <<Method of Indicating New Beam / Current Beam>> The method of indicating the current beam may differ for each use case (use case #1 / #2).

[0433] For example, in use case #1, the current beam is known by the gNB and the UE, so there is no need to report the current beam index in use case #1.

[0434] On the other hand, for use case #2, the gNB cannot know the current beam without a report from the UE, because the current beam is selected from multiple activated TCI states.

[0435] As a method for indicating a new beam / current beam in a beam report, at least one of the following Alt1 to Alt2 may be applied.

[0436] (Alt1) The multiple new beams (e.g., M beams) configured may be re-indexed (e.g., from 0 to M-1). The multiple new beams may be indicated by the re-indexed indices.

[0437] (Alt1-1) The RS / beam corresponding to the activated TCI state may be re-indexed (e.g., from 0 to a maximum of 7 / a maximum of 3 bits), and the current beam may be indicated by the re-indexed index (e.g., the worst / best quality beam).

[0438] Furthermore, in the beam report, a distinction may be made between a new beam and a current beam. As a distinction method, any of the following OptA to OptC may be applied.

[0439] ((OptA)) The order of beam reports in UCI may be as follows: For example, the current beam [and current beam quality] may be placed at the front / end of the beam report.

[0440] ((OptB)) In the UCI, an explicit novelty indicator may be added to indicate the new beam / current beam. For example, a novelty indicator may be given for each beam [index].

[0441] ((OptC)) The beam with the worst quality may be considered the current beam. In this case, only new beams with better quality than the current beam can be reported. For this reason, zero padding can be used for beam reporting.

[0442] (Alt2) The configured new beams (e.g., M) and the RSs / beams (e.g., Q: Q=8 or up to 8) corresponding to the activated TCI states may be jointly re-indexed (e.g., from 0 to M+Q-1), i.e., each reported beam index may indicate (mean) the new beam / current beam.

[0443] (Note) The measurement values ​​(L1-RSRP / SINR) may be placed after the beam index [indication]. The order thereafter can be changed as appropriate, as shown in the following examples: - Multiple beam indices (e.g., in ascending order of index), then multiple measurement values ​​(e.g., in ascending order of index). - Beam index #1, measurement value #1, beam index #2, measurement value #2, ... - Index for the current beam, measurement value for the current beam, indexes for multiple new beams (e.g., in ascending order of index), then multiple measurement values ​​for the new beams (e.g., in ascending order of index).

[0444] According to this embodiment, it is possible to appropriately control the UEIBR when there is one current beam.

[0445] Second Embodiment The second embodiment relates to the case where there are multiple current beams.

[0446] <<Beams to be reported>> If the current beam corresponds to Opt2 described above, the beam report for use case #2 may be different from the beam report for use case #1. For example, in use case #2, if there are multiple current beams (e.g., X), the beam report may include [only] information about the new beam. In other words, the beam report may not include information about the current beam. Alternatively, the beam report may include information about the current beam. That is, the beam report may include the current beam in addition to the new beam.

[0447] As mentioned above, the value of X may be set / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities.

[0448] In Use Case #2, at least one of the above-described Events 3 to 9 may be set. That is, a new beam may be set / measured. Events 3 to 9 may be referred to as events related to a new beam.

[0449] In a beam report for an event for use case #2 (beam report for use case #2), the gNB sets the number of beams to be reported (which may also be referred to as the number of beams to be reported, the number of beam reports, etc.) N. Here, N is the total number of beams to be reported, and can be set for each reporting configuration (CSI-ReportConfig) / BWP / CC / serving cell.

[0450] For beam reporting for use case #2, at least one of the following options (including variations) may be applied:

[0451] (Opt2-A) N indicates the number of new beams to be reported. In this case, the current beam may not be included in the beam report (the current beam may not be reported).

[0452] (Opt2-B) N indicates the total number of beams to be reported (including new beams and current beams), i.e., the current beam may be reported.

[0453] (Opt2-B-1) A beam report may be predefined to always include the current beam. For example, a beam report may include (N-X) new beams and X current beams.

[0454] (Opt2-B-2) The gNB may configure whether the beam report includes X current beams.

[0455] (Opt2-B-3) Whether Y current beams among X current beams are included in the beam report (i.e., the values ​​of X and Y) may be set / indicated by the gNB via higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities. In this case, the beam report may include (N-Y) new beams and Y current beams.

[0456] (Opt2-B-4) The UE may determine / judge whether the beam report includes X current beams. In this case, the gNB can recognize the current beam / new beam based on the beam report transmitted from the UE.

[0457] (Variation 1) N may indicate the number of new beams to be reported. The number of current beams (e.g., Y) may be separately set / indicated by higher layer signaling / physical layer signaling or may be predefined by a specification. In this case, the total number of beams to be reported may be N+Y.

[0458] (Variation 2) At least one of the new beams to be reported must satisfy the event condition. That is, the new beams to be reported may include beams that do not satisfy the condition. Alternatively, if no suitable new beam is found (if no beam satisfies the condition), zeros may be padded.

[0459] (Variation 3) N may be determined by the UE based on the maximum number of reports N_max. N_max indicates the maximum number of beams to be reported and may be set / instructed by the gNB or may be predefined by specifications. The UE may instruct the gNB of N through the PUCCH in step 1. Alternatively, N may be predefined by specifications.

[0460] (Modification 4) The settings for use case #1 may be applied to use case #2.

[0461] <<Method of indicating new beam / current beam>> At least one of the following Alt1 to Alt2 may be applied as a method of indicating a new beam / current beam in a beam report.

[0462] (Alt1) The multiple new beams (e.g., M beams) configured may be re-indexed (e.g., from 0 to M-1). The multiple new beams may be indicated by the re-indexed indices.

[0463] (Alt1-1) The RS / beam corresponding to the activated TCI state may be re-indexed (e.g., 0 to Q bits / up to 7 / up to 3 bits), and the current beam may be indicated by the re-indexed index (e.g., the worst / best beam).

[0464] Furthermore, in the beam report, a distinction may be made between a new beam and a current beam. As a distinction method, any of the following OptA to OptC may be applied.

[0465] ((OptA)) The order of beam reports in UCI may be as follows: For example, the current beam [and current beam quality] may be placed at the front / end of the beam report.

[0466] In this case, the gNB needs to know in advance the number of current beams to be reported, e.g., the number of current beams to be reported may be set / instructed by the gNB or may be predefined by a specification.

[0467] Alternatively, the number of current beams to be reported may be additionally indicated by the PUCCH in step 1. Alternatively, the number of current beams to be reported may be additionally indicated in the UCI before the beam report.

[0468] ((OptB)) In the UCI, an explicit novelty indicator may be added to indicate the new beam / current beam. For example, a novelty indicator may be given for each beam [index].

[0469] (Alt1-2) A Q bit or a bitmap of up to 8 bits may be reported in the UCI before the beam report to indicate the RS / beam corresponding to the activated TCI states to be reported, where one bit corresponds to the current beam of one of the activated TCI states, and may follow a predefined order.

[0470] For example, a bit value of "00110100" indicates three current beams (associated with the third, fifth, and sixth activated TCI states from the least significant digit) to be reported, and then the measurements (L1-RSRP / L1-SINR) corresponding to these three current beams can be reported in the beam report.

[0471] (Alt2) The configured new beams (e.g., M) and the RSs / beams (e.g., Q: Q=8 or up to 8) corresponding to the activated TCI states may be jointly re-indexed (e.g., from 0 to M+Q-1), i.e., each reported beam index may indicate (mean) the new beam / current beam.

[0472] (Note) The measurement value (L1-RSRP / SINR) may be placed after the beam index [indication]. The order thereafter can be changed as appropriate.

[0473] According to this embodiment, it is possible to appropriately control the UEIBR when there are multiple current beams.

[0474] Third Embodiment The third embodiment relates to quantization of measurement values ​​(L1 values, for example, L1-RSRP / L1-SINR) in UEIBR. Quantization may be one aspect of quantization.

[0475] <Aspect 3-1> In the first and second embodiments described above, when an event is triggered, the highest L1 value should (and preferably is) derived from the new beam, not the current beam.

[0476] Therefore, we propose that multiple new beams / current beams for UEIBR be quantified in two stages (first / second quantification, described below).

[0477] Specifically, the measurement values ​​for the best new beam among the multiple new beams may be quantized with a relatively high granularity (e.g., 7 bits) (which may be referred to as first quantization (quantization)), while for the other (remaining) new beams, the difference values ​​for the best new beam may be quantized with a relatively low granularity (e.g., 4 bits) (which may be referred to as second quantization (quantization)).

[0478] The current beam quantification method will be exemplified below for each of the first and second embodiments described above.

[0479] <<Quantification for the First Embodiment (One Current Beam)>> One current beam may be quantized with: (Opt1): 7 bits. (Opt2): It may be represented by a 4-bit difference value relative to the best new beam.

[0480] <<Quantification in the case of the second embodiment (multiple current beams)>> (Opt3): Each current beam may be quantized with 7 bits. (Opt4): For each current beam, the difference value from the best new beam may be quantized with 4 bits. (Opt5): The best current beam of all reported current beams may be quantized with 7 bits (this may be called first quantization (quantization)). For the other (remaining) current beams, the difference value from the best current beam may be quantized with 4 bits (this may be called second quantization (quantization)).

[0481] <Aspect 3-2> When filtering is applied to a certain event, there may be cases where the quality of the current beam is better than the new beam, depending on how the measurements (L1-RSRP / L1-SINR) are selected for reporting.

[0482] Therefore, we propose multiple new beam / current beam quantification methods for UEIBR.

[0483] (OptA) As in Opt1 / 3 / 5 of aspect 3-1, the current beam and the new beam may be quantized separately.

[0484] (OptB) A new field (e.g., 1 bit) may be additionally reported in the UCI, which may indicate that the beam with the best value by 7-bit quantization is the first current beam / first new beam in the beam report.

[0485] This allows reporting the best beam quantized on 7 bits, and for the remaining beams, the difference values ​​quantized on 4 bits.

[0486] According to this embodiment, it is possible to appropriately control the quantification of the measurements in the UEIBR.

[0487] Fourth Embodiment The fourth embodiment relates to a case where event 1 is set.

[0488] If event 1 (the quality of the current beam becomes worse than a certain threshold) is set, in the beam report for use case #2, the beam report may include [only] information about the current beam.

[0489] In the beam report for event 1 for use case #2 (beam report for use case #2), the gNB sets the number of beams to be reported (which may also be referred to as the number of beams to be reported, the number of beam reports, etc.) N. Here, N is the total number / total number of beams to be reported, and may only include the current beam.

[0490] N may be configured for each reporting configuration (CSI-ReportConfig) / BWP / CC / serving cell. The value of N may be configured / indicated by higher layer signaling / physical layer signaling, may be predefined by a specification, or may be determined according to UE capabilities. At least one of Alt1 to Alt2 below may be applied as a method for indicating the current beam in the beam report.

[0491] (Alt1) The RS / beam corresponding to the activated TCI state may be re-indexed (e.g., 0 to Q bits / up to 7 / up to 3 bits), and the current beam may be indicated by the re-indexed index (e.g., the worst / best beam).

[0492] (Alt2) A Q bit or a bitmap of up to 8 bits may be reported in the UCI to indicate the RS / beam corresponding to the activated TCI states to be reported, where one bit corresponds to the current beam of one of the activated TCI states, and may follow a predefined order.

[0493] (Note) The measurement value (L1-RSRP / SINR) may be placed after the beam index [indication]. The order thereafter can be changed as appropriate.

[0494] According to this embodiment, it is possible to appropriately control the UEIBR when there are multiple current beams.

[0495] <Modification> The embodiments of the present disclosure may be applied to each cell / CC or between cells / CCs.

[0496] Each serving cell / CC / frequency may have RRC information elements / parameters for UE IBR. In other words, RRC information elements / parameters for UE IBR may be configured for each serving cell / CC / frequency.

[0497] For example, the RRC information elements / parameters for UE IBR may be configured in / under the serving cell configuration (e.g., the RRC parameter ServingCellConfig).

[0498] In other words, the RRC information elements / parameters for UE IBR may be configured individually for each serving cell.

[0499] In the present disclosure, the RRC information elements / parameters for UE IBR may include at least one of candidate reference signal (RS) configuration, (maximum) number of RSs to be reported, reporting amount, events, event thresholds, timers / counters for filtering L1 results, whether serving beam results are included in the report, and first / second step resources.

[0500] For example, existing parameters (e.g., CSI reporting configuration (RRC parameter CSI-ReportConfig)) may be reused / utilized for UEIBR. In this case, the parameters in each serving cell may be configured as RRC information elements / parameters for UEIBR of each serving cell.

[0501] Also, for example, a new parameter (e.g., CSI configuration reporting for UEIBR (RRC parameter UEI-CSI-ReportConfig-r19)) may be introduced / configured in / under the serving cell configuration. In this case, the parameter in each serving cell may be configured as an RRC information element / parameter for UEIBR of each serving cell.

[0502] <Supplementary Information> <<Notification of Information to UE>> In the above-described embodiments, notification of any information 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) may be performed 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.

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

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

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

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

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

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

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

[0510] <<Application of Each Embodiment>> In a UE / BS, specific (one or more) processes / operations / controls / assumptions / information for at least one of the above-described embodiments may be applied (used) when one or more of the following conditions are met: - A higher layer parameter indicating the specific processes / operations / controls / assumptions / information is configured. - The specific processes / operations / controls / assumptions / information is determined based on related higher layer parameters. - The specific processes / operations / controls / assumptions / information is specified / activated / triggered by a MAC CE / DCI / UCI / resource / channel / RS. - A specific UE capability indicating (or related to) the specific processes / operations / controls / assumptions / information is reported or supported. - The application of the specific processes / operations / controls / assumptions / information is determined based on specific conditions.

[0511] 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 (configuring) UE IBR in multiple serving cells / frequencies. Maximum number of serving cells / frequencies according to UE IBR configuration. Maximum number of beams per serving cell / frequency. Maximum number of beams across multiple (all configured) serving cells / frequencies. Supporting common / separate resources for different serving cells / frequencies in the first / second step of UCI-based reporting. Supporting common / separate resources for different serving cells / frequencies in the first / second step of MAC CE-based reporting. Supporting multiple resource configurations in the first / second step of UCI-based reporting for UE selection / reporting and / or base station / network indication. Supporting beam reporting for multiple serving cells / frequencies using one UCI / MAC CE. Support beam reporting for multiple serving cells / frequencies using multiple (separate) UCI / MAC CEs. Support event-based beam reporting using MAC CE / UCI.

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

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

[0514] If the above conditions are not met, the UE / BS may follow the behavior specified in existing 3GPP releases.

[0515] (Supplementary Notes) The following inventions are supplementary notes regarding one embodiment (first / second embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives a configuration of a UE-initiated beam report (UEIBR); and a controller that controls the UEIBR for an event for a specific use case based on the configuration, wherein the controller includes information on at least one of a current beam and a new beam in the UEIBR. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the event is an event related to the new beam. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the current beam is one or more beams selected from an activated transmission configuration indication (TCI) state. [Supplementary Note 4] The terminal according to any one of Supplements 1 to 3, wherein indexes are reassigned to multiple configured new beams or multiple beams corresponding to an activated transmission configuration indication (TCI) state.

[0516] (Supplementary Notes) The following inventions are supplementary notes regarding an embodiment (third / fourth embodiment) of the present disclosure. [Supplementary Note 1] A terminal comprising: a receiver that receives a configuration of a UE-initiated beam report (UEIBR); and a controller that controls the UEIBR for an event for a specific use case based on the configuration, wherein the controller quantizes a current beam or a new beam in two stages. [Supplementary Note 2] The terminal according to Supplementary Note 1, wherein the current beam or the new beam is quantized using 7 bits, and then the remaining beam is represented by a 4-bit difference value. [Supplementary Note 3] The terminal according to Supplementary Note 1 or Supplementary Note 2, wherein the current beam and the new beam are quantized separately. [Supplementary Note 4] The terminal according to any one of Supplements 1 to 3, wherein the controller includes one or more current beams in the UEIBR when a specific event related to the current beam is configured.

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

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

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

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

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

[0522] 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 location, number, shape, size, etc. of each cell and user terminal 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 the base station 10.

[0523] The wireless communication system 1 may utilize multi-input multi-output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a supercell) may be composed of multiple [virtual] cells (which may be called, for example, subcells). A supercell may correspond to a cell with a fixed physical range, and a subcell may correspond to a cell with a quasi-static / dynamically variable physical range. In this case, the wireless communication system 1 may be called a cell-free system.

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

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

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

[0527] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 / Xn 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0562] The base station 10 may be separated into three elements: a radio unit (RU), a distributed unit (DU), and a central unit (CU). For example, the RU may implement RF processing (digital beamforming, digital-to-analog conversion, analog beamforming, etc.) and lower-level functions of the physical layer (precoding, IFFT, FFT, etc.). The DU may implement higher-level functions of the physical layer (coding to resource element mapping, etc.), MAC layer functions, and RLC layer functions. The CU may implement the functions of the PDCP layer, Service Data Adaptation Protocol (SDAP) layer, and RRC layer.

[0563] In the present disclosure, the base station 10 may include a single device that realizes all of the functions of the RU, DU, and CU, or may include multiple devices that each realize some of the functions of the RU, DU, and CU and are connected to each other. In the present disclosure, the base station 10 may be interchangeably read as RU / DU / CU.

[0564] The transceiver 120 may transmit a configuration of a UE-initiated beam report (UEIBR). The controller 110 may control reception of the UEIBR for an event for a specific use case transmitted from the terminal based on the configuration. The UEIBR may include information on at least one of a current beam and a new beam.

[0565] The current beam or new beam included in the UEIBR is quantified in two stages.

[0566] (User Terminal) Fig. 12 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0583] Note that the transmitting section and receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220 and the transmitting / receiving antenna 230.

[0584] The transceiver unit 220 may perform at least one of the processes of the transmitter / receiver unit in any of the above appendices.

[0585] The control unit 210 may execute at least one of the processes of any of the control units described above.

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

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

[0588] For example, a base station, a user terminal, or the like 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. 13 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, and the like.

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

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

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

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

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

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

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

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

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

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

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

[0600] In addition, the devices included in the core network 30 (for example, network nodes that provide NF) may also be realized by the above-mentioned functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0626] With respect to any information (e.g., variables, constants, parameters) described in the present disclosure, even if not specifically stated in the above embodiments, any first device (e.g., UE / base station) may notify any second device (e.g., base station / UE) of information indicating / specifying (or relating to) the value of the any information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0673] 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 ..." or "do ... (if the above "..." is a to-infinitive, a verb with "to")," etc. "does not expect ..." may be interchangeably read as "be not expected ..." or "does not ... (if the above "..." is a to-infinitive, a verb with "to")," etc. 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" (for example, if apparatus A is a UE, apparatus B may be a base station).

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

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

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

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

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

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

[0680] 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 any integer) attached (for example, "highest" may be interchangeable with "i-th highest").

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

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

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

[0684] 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 having a receiving unit that receives a setting for a UE-initiated beam report (UEIBR); and a control unit that controls the UEIBR for an event for a specific use case based on the setting, wherein the control unit quantifies a current beam or a new beam in two stages.

2. The terminal of claim 1, wherein the current beam or the new beam is quantized with 7 bits and then represented by a 4-bit difference value for the remaining beams.

3. The terminal of claim 1, wherein the current beam and the new beam are each quantized separately.

4. The terminal of claim 1, wherein the control unit includes one or more current beams in the UEIBR if a specific event related to the current beam is set.

5. A wireless communication method for a terminal, comprising: a step of receiving a configuration of a UE-initiated beam report (UEIBR); a step of controlling the UEIBR for an event for a specific use case based on the configuration; and a step of quantifying a current beam or a new beam in two stages.

6. A base station comprising: a transmitting unit that transmits a setting for a UE-initiated beam report (UEIBR); and a control unit that controls reception of the UEIBR for an event for a specific use case transmitted from a terminal based on the setting, wherein the current beam or new beam included in the UEIBR is quantified in two stages.

Images