Terminals, wireless communication methods, base stations and systems

By implementing a terminal with a reception unit for TCI state threshold settings and CSI reporting control, the challenges of unclear beam reporting conditions are addressed, improving communication throughput and reducing overhead in wireless systems.

JP7876532B2Active Publication Date: 2026-06-19NTT DOCOMO INC

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
NTT DOCOMO INC
Filing Date
2021-07-30
Publication Date
2026-06-19

AI Technical Summary

Technical Problem

The conditions and methods for beam reporting in future wireless communication systems are not clear, leading to potential decreases in communication throughput and increases in overhead.

Method used

A terminal equipped with a reception unit to receive higher layer parameters for threshold settings in Transmission Configuration Indication (TCI) states and a control unit to trigger Channel State Information (CSI) reporting based on these thresholds, ensuring appropriate beam reporting for both uplink and downlink channels.

Benefits of technology

This approach enables appropriate beam reporting, enhancing communication efficiency and reducing overhead in wireless systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007876532000003
    Figure 0007876532000003
  • Figure 0007876532000004
    Figure 0007876532000004
  • Figure 0007876532000005
    Figure 0007876532000005
Patent Text Reader

Abstract

A terminal according to one aspect of the present disclosure has: a control unit which, on the basis of an event pertaining to at least one of a plurality of beams, controls at least one of first beam reporting not based on the event and second beam reporting based on the event; and a transmission unit which, when performing the second beam reporting, transmits at least one element from among a random access channel related to first information pertaining to a novel candidate beam, and a medium access control (MAC) control element containing second information pertaining to the novel candidate beam. According to one aspect of the present disclosure, it is possible to appropriately perform beam reporting based on an event.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] This disclosure relates to terminals and wireless communication methods in next-generation mobile communication systems. 、 base station and system Regarding. [Background technology]

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

[0003] Successor systems to LTE (for example, 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also being considered. [Prior art documents] [Non-patent literature]

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

Problems to be Solved by the Invention

[0005] In future wireless communication systems, it is considered that a terminal performs beam reporting based on an event.

[0006] However, the conditions of the event and the method of beam reporting based on the event are not clear. If the conditions of the event and the method of beam reporting based on the event are not clarified, there is a risk of causing a decrease in communication throughput / an increase in overhead.

[0007] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method 、 base station and system that appropriately performs beam reporting based on an event.

Means for Solving the Problems

[0008] A terminal according to one aspect of the present disclosure , multiple a reception unit that receives a higher layer parameter indicating a threshold corresponding to each of a plurality of transmission configuration indication (TCI) states of reference signal reception power (RSRP) Of these, the largest RSRP with respect to an event, and a control unit that controls channel state information (CSI) reporting triggered by the event. , the above Furthermore, the TCI state is an activated TCI state for both the uplink and the downlink, and the TCI state is applied to multiple channels including both the uplink and the downlink, and the CSI report is made when the largest RSRP among the RSRPs corresponding to each of the multiple activated TCI states satisfies the threshold condition.

Effects of the Invention

[0009] According to one aspect of the present disclosure, beam reporting based on an event can be appropriately performed.

Brief Description of the Drawings

[0010] [Figure 1] FIG. 1 is a diagram showing an example of the number of RLM-RSs. [Figure 2] FIG. 2 is a diagram showing an example of a beam recovery procedure. [Figure 3] FIGS. 3A and 3B are diagrams showing an example of beam reporting by a plurality of UEs.​​ [Figure 4] Figure 4 shows an example of a serving beam and an adjacent beam. [Figure 5] Figures 5A and 5B show an example of a beam comparison according to Embodiment 1-2. [Figure 6] Figure 6 shows an example of a beam report according to Embodiment 1-3. [Figure 7] Figure 7 shows an example of the configuration of MAC CE according to Embodiment 2-2. [Figure 8] Figure 8 shows another example of the MAC CE configuration according to Embodiment 2-2. [Figure 9] Figures 9A and 9B show an example of an event occurrence timeline according to the fourth embodiment. [Figure 10] Figures 10A and 10B show other examples of the event occurrence timeline according to the fourth embodiment. [Figure 11] Figure 11 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 12] Figure 12 shows an example of the configuration of a base station according to one embodiment. [Figure 13] Figure 13 shows an example of the configuration of a user terminal according to one embodiment. [Figure 14] Figure 14 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Modes for carrying out the invention]

[0011] (CSI report) In Rel.15 / 16 NR, the UE measures the channel state using a predetermined reference signal (or a resource for that reference signal) and feeds back (reports) the Channel State Information (CSI) to the base station.

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

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

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

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

[0016] Methods for providing feedback on CSIs include (1) periodic CSI (P-CSI) reporting, (2) aperiodic CSI (A(AP)-CSI) reporting, and (3) semi-persistent CSI (SP-CSI) reporting.

[0017] The UE may notify CSI reporting information (which may also be called CSI reporting configuration information) using upper-layer signaling, physical layer signaling (e.g., Downlink Control Information (DCI)), or a combination thereof. CSI reporting configuration information may be configured, for example, using the RRC information element "CSI-ReportConfig".

[0018] Here, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0019] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (MAC PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0020] CSI reporting configuration information may include, for example, information regarding the reporting cycle, offset, etc., which may be expressed in a predetermined time unit (slot unit, subframe unit, symbol unit, etc.). CSI reporting configuration information may also include a configuration ID (CSI-ReportConfigId). This configuration ID may specify parameters such as the type of CSI reporting method (whether or not it is SP-CSI) and the reporting cycle. CSI reporting configuration information may also include information (CSI-ResourceConfigId) indicating which signal (or resource for which signal) was used to measure the CSI and report it.

[0021] (Beam management) Up until now, beam management (BM) methods have been considered in Rel.15 NR. In this beam management, beam selection is being considered based on the L1-RSRP reported by the UE. Changing (switching) the beam for a particular signal / channel may be equivalent to changing the transmission configuration indication state (TCI state) of that signal / channel.

[0022] The beam selected by beam selection may be either the transmit beam (Tx beam) or the receive beam (Rx beam). Furthermore, the beam selected by beam selection may be either the UE beam or the base station beam.

[0023] The UE may report (transmit) measurement results for beam management using PUCCH or PUSCH. These measurement results may include CSIs that include at least one of the following: L1-RSRP, L1-RSRQ, L1-SINR, L1-SNR, etc. These measurement results may also be called beam measurement, beam measurement results, beam report, beam measurement report, etc.

[0024] CSI measurements for beam reporting may include interference measurements. The UE may use resources for CSI measurements to measure channel quality, interference, etc., and derive the beam report. Resources for CSI measurements may be at least one of the following: for example, SS / PBCH block resources, CSI-RS resources, or other reference signal resources. CSI measurement report configuration information may be set in the UE using upper-layer signaling.

[0025] The beam report may include the results of at least one of channel quality measurements and interferometry measurements. The channel quality measurement results may include, for example, L1-RSRP. The interferometry measurement results may include L1-SINR, L1-SNR, L1-RSRQ, and other interference metrics (e.g., any metric other than L1-RSRP).

[0026] Resources for CSI measurements for beam management may also be called beam measurement resources. Furthermore, the signal / channel being measured for CSI may be called a beam measurement signal. Additionally, CSI measurement / reporting may be interpreted as at least one of the following: measurement / reporting for beam management, beam measurement / reporting, or wireless link quality measurement / reporting.

[0027] The CSI reporting settings information, which takes into account the current NR beam management, is included in the RRC information element "CSI-ReportConfig". This section explains the information within the RRC information element "CSI-ReportConfig".

[0028] The CSI reporting configuration information (CSI-ReportConfig) may include reporting quantity information ("reporting quantity," which may be represented by the RRC parameter "reportQuantity"), which is information about the parameters to be reported. The reporting quantity information is defined as an ASN.1 object of type "choice." Therefore, one of the parameters specified as reporting quantity information (such as cri-RSRP and ssb-Index-RSRP) is set.

[0029] A UE with a higher-level parameter included in the CSI reporting settings information (e.g., RRC parameter "groupBasedBeamReporting") enabled may include multiple beam measurement resource IDs (e.g., SSBRI, CRI) and their corresponding measurement results (e.g., L1-RSRP) in the beam report for each reporting setting.

[0030] A UE that has set the number of reportable RS resources to one or more by a higher-layer parameter included in the CSI reporting configuration information (for example, the RRC parameter "nrofReportedRS") may include in the beam report one or more beam measurement resource IDs and one or more corresponding measurement results (e.g., L1-RSRP) for each reporting configuration.

[0031] (TCI, spatial relations, QCL) In NR, it is being considered to control the receive processing (e.g., at least one of receive, demapping, demodulation, and decoding) and transmit processing (e.g., transmit, mapping, precoding, modulation, and encoding) of at least one of the signal and channel (referred to as signal / channel) at the UE based on the Transmission Configuration Indication state (TCI state).

[0032] The TCI state may represent the one applied to the downlink signal / channel. The equivalent of the TCI state applied to the uplink signal / channel may be expressed as a spatial relation.

[0033] TCI status refers to information about signal / channel quasi-co-location (QCL), and may also be called spatial reception parameters or spatial relation information. TCI status may be set for each channel or signal in the UE.

[0034] QCL is an index that indicates the statistical properties of a signal / channel. For example, if two signals / channels have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0035] The spatial reception parameters may correspond to the UE's received beam (e.g., the received analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0036] QCL may have multiple types (QCL types). For example, there may be four QCL types A and D that differ in the parameters (or parameter sets) that can be assumed to be the same, and these parameters (which may also be called QCL parameters) are shown below: • 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.

[0037] The assumption by the UE that one control resource set (CORESET), channel, or reference signal is in a specific QCL (e.g., QCL type D) relationship with another CORESET, channel, or reference signal may be called a QCL assumption.

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

[0039] The TCI state may, for example, be information regarding the QCL between the target channel (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 upper-layer signaling, physical layer signaling, or a combination thereof.

[0040] Physical layer signaling may include, for example, Downlink Control Information (DCI).

[0041] The channel on which the TCI state or spatial relationship is set (specified) may be, for example, at least one of the following: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), or Physical Uplink Control Channel (PUCCH).

[0042] Furthermore, the RS that has a QCL relationship with the channel may be at least one of the following: 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)), or a QCL detection reference signal (also called a QRS).

[0043] An SSB is a signal block that includes 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 called an SS / PBCH block.

[0044] The RS of a QCL type X in a TCI state may also mean the RS in the relationship between a channel / signal (or its DMRS) and a QCL type X, and this RS may also be called the QCL source of the QCL type X in that TCI state.

[0045] QCL type A RS is always set for PDCCH and PDSCH, and QCL type D RS may be set additionally. Because it is difficult to estimate Doppler shift, delay, etc. from a single shot of DMRS reception, QCL type A RS is used to improve channel estimation accuracy. QCL type D RS is used for receiving beam determination when DMRS is received.

[0046] For example, TRS1-1, 1-2, 1-3, and 1-4 are transmitted, and TRS1-1 is advertised as QCL type C / D RS by the PDSCH's TCI state. By advertising the TCI state, the UE can use information obtained from past periodic TRS1-1 reception / measurement results to receive / channel estimate the DMRS for the PDSCH. In this case, the PDSCH's QCL source is TRS1-1, and the QCL target is the DMRS for the PDSCH.

[0047] (Unified / Common TCI Framework) According to the Unified TCI Framework, UL and DL channels can be controlled by a common framework. Rather than defining TCI states or spatial relationships for each channel as in Rel. 15, the Unified TCI Framework may specify a common beam (common TCI state) and apply it to all UL and DL channels, or a common beam for UL may be applied to all UL channels, and a common beam for DL ​​may be applied to all DL channels.

[0048] One common beam for both DL and UL, or a common beam for DL ​​and a common beam for UL (two common beams in total) are being considered.

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

[0050] The default beams for UL and DL may be aligned by beam management based on MAC CE (MAC CE level beam indication). Alternatively, the default TCI status of PDSCH may be updated to match the default UL beam (spatial relationship).

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

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

[0053] (Radio Link Monitoring (RLM)) In NR (New Radio), Radio Link Monitoring (RLM) is used.

[0054] In NR, the network (NW, e.g., base station) may configure a Radio Link Monitoring Reference Signal (RLM-RS) for each BWP (Band Point Wand) for the UE using higher-layer signaling. The UE may receive configuration information for the RLM (e.g., the "RadioLinkMonitoringConfig" information element of the RRC).

[0055] The configuration information for the RLM may include fault detection resource configuration information (for example, the higher-layer parameter "failureDetectionResourcesToAddModList"). The fault detection resource configuration information may also include parameters related to RLM-RS (for example, the higher-layer parameter "RadioLinkMonitoringRS").

[0056] Parameters related to RLM-RS may include information indicating the purpose of the RLM, and an index corresponding to the RLM-RS resource (for example, an index included in the higher-layer parameter "failureDetectionResources" (RadioLinkMonitoringRS in failureDetectionResourcesToAddModList)). This index may be, for example, an index for the CSI-RS resource setting (e.g., a non-zero power CSI-RS resource ID) or an SS / PBCH block index (SSB index). The information of purpose may indicate beam failure, (cell-level) Radio Link Failure (RLF), or both.

[0057] The UE may identify RLM-RS resources based on an index corresponding to the RLM-RS resources and perform RLM using those RLM-RS resources.

[0058] In the RLM procedure of Rel.16, the UE follows the following implicit RLM-RS decision procedure.

[0059] [Implicit RLM-RS determination procedure] If the UE does not provide RLM-RS (RadioLinkMonitoringRS) and the UE provides a TCI state that includes one or more CSI-RS for PDCCH reception, the UE shall follow steps 1 through 4 below.

[0060] [[Step 1]] If the active TCI state for PDCCH reception contains only one RS, the UE uses that RS provided for the active TCI state for PDCCH reception for RLM. [[Step 2]] If the active TCI state for PDCCH reception includes two RSs, the UE assumes that one RS has QCL type D, and uses that RS with QCL type D for RLM. The UE does not assume that both RSs have QCL type D. [[Step 3]] UE does not require the use of aperiodic or semi-persistent RS in RLM. [[Step 4]] L max For =4, the UE provides N for the active TCI state for PDCCH reception within multiple CORESETs associated with multiple search space sets, in order from the smallest monitoring period (periodicity). RLM Select the number of RSs. If more than one CORESET is associated with multiple search space sets with the same monitoring period, the UE determines the order of the CORESETs from the best CORESET index.

[0061] Here, L max This is the maximum number of SS / PBCH block indices within a cell. The maximum number of SS / PBCH blocks transmitted within a half-frame is L max That is the case.

[0062] Thus, if the UE does not provide RLM-RS, the UE makes an implicit RLM-RS determination and uses the active TCI state for PDCCH reception for RLM. max If = 4, the UE is first sorted in ascending order of the monitoring period of the search space set, then in descending order of the CORESET index, N RLM Select this RS. Select CORESET.

[0063] The UE can be configured with up to N RLM-RSs for link recovery procedures and RLM. LR-RLM Out of the N RLM-RSs, up to N LR-RLM RLM-RSs are used for RLM depending on L max . In Rel.16, as shown in Figure 1, when L RLM = 4, N max = 2, and when L RLM = 8, N max = 4, and when L RLM = 64, N max = 8. RLM

[0064] (Beam Failure Detection (BFD) / Beam Failure Recovery (BFR)) In NR, communication is performed using beamforming. For example, the UE and the base station (e.g., gNB (gNodeB)) may use a beam used for signal transmission (also referred to as a transmission beam, Tx beam, etc.) and a beam used for signal reception (also referred to as a reception beam, Rx beam, etc.).

[0065] When using beamforming, since it is vulnerable to the influence of interference by obstacles, it is assumed that the radio link quality deteriorates. Due to the deterioration of the radio link quality, there is a risk that radio link failures (RLFs) occur frequently. When an RLF occurs, reconnection to the cell is required, so frequent occurrence of RLFs leads to degradation of the system throughput.

[0066] In NR, in order to suppress the occurrence of RLF, when the quality of a specific beam deteriorates, a procedure for switching to another beam (which may be referred to as beam recovery (BR), beam failure recovery (BFR), L1 / L2 (Layer 1 / Layer 2) beam recovery, etc.) is performed. Note that the BFR procedure may simply be referred to as BFR.

[0067] In this disclosure, beam failure (BF) may also be referred to as link failure.

[0068] Figure 2 shows an example of the beam recovery procedure in Rel.15 NR. The number of beams and other details are examples only and are not limited to this. In the initial state (step S101), the UE performs measurements based on the Reference Signal (RS) resource transmitted using two beams.

[0069] The RS may be at least one of a Synchronization Signal Block (SSB) and a Channel State Information RS (CSI-RS). The SSB may also be called an SS / PBCH (Physical Broadcast Channel) block, etc.

[0070] RS may be at least one of the following: Primary SS (PSS), Secondary SS (SSS), Mobility Reference Signal (MRS), signals included in SSB, SSB, CSI-RS, Demodulation Reference Signal (DMRS), beam-specific signals, or signals that are extended or modified from these. The RS measured in step S101 may also be called the RS for beam failure detection (Beam Failure Detection RS (BFD-RS)), or the RS for use in the beam recovery procedure (BFR-RS).

[0071] In step S102, the UE is unable to detect the BFD-RS (or the quality of the RS reception is degraded) due to interference with the radio waves from the base station. Such interference can occur, for example, due to obstacles, fading, or interference between the UE and the base station.

[0072] The UE detects a beam fault when certain conditions are met. For example, the UE may detect a beam fault if the BLER (Block Error Rate) is below a threshold for all configured BFD-RS (BFD-RS resource settings). When a beam fault is detected, the lower layer of the UE (physical (PHY) layer) may notify (instruct) the upper layer (MAC layer) of the beam fault instance.

[0073] Furthermore, the criteria for judgment are not limited to BLER, but may also be the Layer 1 Reference Signal Received Power (L1-RSRP). In addition, beam fault detection may be performed based on the Physical Downlink Control Channel (PDCCH) or the like, instead of or in addition to RS measurement. BFD-RS may be expected to be in quasi-co-location (QCL) with the DMRS of the PDCCH monitored by the UE.

[0074] Here, QCL is an index that indicates the statistical properties of a channel. For example, if one signal / channel and another signal / channel have a QCL relationship, it may mean that we can assume that at least one of the following is identical between these different signals / channels: Doppler shift, Doppler spread, average delay, delay spread, and spatial parameter (e.g., spatial Rx parameter).

[0075] The spatial reception parameters may correspond to the UE's received beam (e.g., the received analog beam), and the beam may be identified based on the spatial QCL. In this disclosure, QCL (or at least one element of QCL) may be interpreted as sQCL (spatial QCL).

[0076] Information regarding BFD-RS (e.g., RS index, resources, number, number of ports, precoding, etc.) and information regarding beam fault detection (BFD) (e.g., the thresholds mentioned above) may be set (notified) to the UE using higher-layer signaling or the like. Information regarding BFD-RS may also be called information regarding resources for BFR.

[0077] The upper layers of the UE (e.g., the MAC layer) may start a predetermined timer (which may be called a beam failure detection timer) when it receives a beam failure instance notification from the UE's PHY layer. If the UE's MAC layer receives a certain number of beam failure instance notifications (e.g., beamFailureInstanceMaxCount set in RRC) or more before the timer expires, it may trigger a BFR (e.g., start one of the random access procedures described below).

[0078] The base station may determine that the UE has detected a beam fault if it does not receive notification from the UE, or if it receives a predetermined signal from the UE (a beam recovery request in step S104).

[0079] In step S103, the UE starts searching for a new candidate beam to be used for communication in order to recover the beam. The UE may select a new candidate beam corresponding to a predetermined RS by measuring that RS. The RS measured in step S103 may be called new candidate RS, RS for new candidate beam identification, NCBI-RS (New Candidate Beam Identification RS), RS for new beam identification, RS for new beam identification, NBI-RS (New Beam Identification RS), CBI-RS (Candidate Beam Identification RS), CB-RS (Candidate Beam RS), etc. NBI-RS may be the same as or different from BFD-RS. The new candidate beam may also be simply called a candidate beam or candidate RS.

[0080] The UE may determine a beam corresponding to an RS that meets predetermined conditions as a new candidate beam. For example, the UE may determine a new candidate beam based on an RS among the set NBI-RSs where the L1-RSRP exceeds a threshold. Note that the criteria for judgment are not limited to the L1-RSRP. The L1-RSRP for SSB may be called SS-RSRP. The L1-RSRP for CSI-RS may be called CSI-RSRP.

[0081] Information regarding NBI-RS (e.g., RS resources, number, number of ports, precoding, etc.) and information regarding new beam identification (NBI) (e.g., the thresholds mentioned above) may be set (notified) to the UE using higher-layer signaling or the like. Information regarding new candidate RS (or NBI-RS) may be obtained based on information regarding BFD-RS. Information regarding NBI-RS may also be called information regarding NBI resources.

[0082] Note that BFD-RS, NBI-RS, etc., may be interpreted interchangeably with the Radio Link Monitoring RS (RLM-RS).

[0083] In step S104, the UE that identified the new candidate beam sends a Beam Failure Recovery reQuest (BFRQ). The Beam Failure Recovery reQuest may also be called a Beam Failure Recovery request signal or a Beam Failure Recovery request signal.

[0084] BFRQ may be transmitted using, for example, at least one of the following: Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH), Physical Uplink Shared Channel (PUSCH), or configured grant (CG) PUSCH.

[0085] The BFRQ may include information on new candidate beams / new candidate RSs identified in step S103. Resources for the BFRQ may be associated with the new candidate beam. Beam information may be communicated using a beam index (BI), a port index of a given reference signal, an RS index, a resource index (e.g., a CSI-RS resource indicator (CRI), an SSB resource indicator (SSBRI)), etc.

[0086] Rel.15 NR considers CB-BFR (Contention-Based BFR), which is based on the Contention-Based Random Access (CBRA) procedure, and CF-BFR (Contention-Free BFR), which is based on the Contention-Free Random Access (CFRA) procedure. In CB-BFR and CF-BFR, the UE may use a PRACH resource to send a preamble (also called an RA preamble, random access channel (Physical Random Access Channel (PRACH)), RACH preamble, etc.) as a BFRQ.

[0087] In CB-BFR, a UE may transmit a preamble randomly selected from one or more preambles. In contrast, in CF-BFR, a UE may transmit a preamble specifically assigned to the UE by the base station. In CB-BFR, a base station may assign the same preamble to multiple UEs. In CF-BFR, a base station may assign preambles individually to each UE.

[0088] Furthermore, CB-BFR and CF-BFR may also be called CB PRACH-based BFR (contention-based PRACH-based BFR (CBRA-BFR)) and CF PRACH-based BFR (contention-free PRACH-based BFR (CFRA-BFR)), respectively. CBRA-BFR may also be called CBRA for BFR. CFRA-BFR may also be called CFRA for BFR.

[0089] Whether it is CB-BFR or CF-BFR, information regarding PRACH resources (RA preamble) may be communicated, for example, by upper-layer signaling (such as RRC signaling). For example, this information may include information showing the correspondence between the detected DL-RS (beam) and the PRACH resource, and different PRACH resources may be associated with each DL-RS.

[0090] In step S105, the base station that detected the BFRQ transmits a response signal (which may be called a gNB response, etc.) to the BFRQ from the UE. This response signal may include reconstruction information for one or more beams (e.g., configuration information for DL-RS resources).

[0091] The response signal may be transmitted, for example, in the UE common search space of the PDCCH. The response signal may be communicated using the PDCCH (DCI) scrambled with a Cyclic Redundancy Check (CRC) by the UE's identifier (e.g., Cell-Radio RNTI (C-RNTI)). The UE may determine, based on beam reconstruction information, at least one of the transmit beam and receive beam to use.

[0092] The UE may monitor the response signal based on at least one of the Control Resource Set (CORESET) for BFR and the Search Space Set for BFR.

[0093] Regarding CB-BFR, contention resolution may be considered successful if the UE receives a PDCCH corresponding to its own C-RNTI.

[0094] Regarding the processing in step S105, a period may be set for the UE to monitor the response from the base station (e.g., gNB) to the BFRQ. This period may be called, for example, the gNB response window, the gNB window, or the beam recovery request response window. If no gNB response is detected within the window period, the UE may retransmit the BFRQ.

[0095] In step S106, the UE may send a message to the base station indicating that beam reconstruction is complete. This message may be sent, for example, by PUCCH or by PUSCH.

[0096] A successful beam recovery (BR success) may indicate, for example, that the process reaches step S106. On the other hand, a failed beam recovery (BR failure) may correspond to, for example, that the number of BFRQ transmissions reaches a predetermined number, or that the beam-failure-recovery-Timer expires.

[0097] Rel.15 supports beam recovery procedures (e.g., BFRQ notification) for beam faults detected by SpCell (PCell / PSCell) using random access procedures. On the other hand, Rel.16 supports beam recovery procedures (e.g., BFRQ notification) for beam faults detected by SCell using at least one of the following: sending a PUCCH for BFR (e.g., scheduling request (SR)) or sending a MAC CE for BFR (e.g., UL-SCH).

[0098] For example, a UE may transmit beam fault information using a MAC CE-based two-step process. This beam fault information may include information about the cell that detected the fault and information about a new candidate beam (or new candidate RS index).

[0099] [Step 1] If a beam fault is detected, the UE may send a PUCCH-BFR (scheduling request (SR)) to the PCell / PSCell. The PCell / PSCell may then send a UL grant (DCI) to the UE for step 2 below. If a MAC CE (or UL-SCH) exists for sending information about a new candidate beam when a beam fault is detected, step 1 (e.g., PUCCH transmission) may be omitted and step 2 (e.g., MAC CE transmission) may be performed.

[0100] [Step 2] Next, the UE may transmit information about the cell where a beam fault was detected (failed) (e.g., cell index) and information about a new candidate beam to the base station (PCell / PSCell) via the uplink channel (e.g., PUSCH) using MAC CE. Subsequently, after a BFR procedure and a predetermined period (e.g., 28 symbols) after receiving a response signal from the base station, the QCL of PDCCH / PUCCH / PDSCH / PUSCH may be updated with the new beam.

[0101] Note that the numbers in these steps are for illustrative purposes only, and multiple steps may be grouped together, or their order may be changed. Also, whether or not to perform BFR may be set in the UE using higher-layer signaling.

[0102] (Transmit power control for PUCCH) In NR, the PUCCH's transmit power is controlled based on the TPC command (also called value, increment / decrement value, correction value, instruction value, etc.) indicated by the value of a specific field in DCI (also called the TPC command field, first field, etc.).

[0103] The TPC command field may be included in a specific DCI (e.g., DCI format 1_0 / 1_1 / 1_2 / 2_2). In Rel. 16 NR, the TPC command field may have a bit length of 2 bits. Additionally, a specific DCI (e.g., DCI format 2_2) may include a field that instructs closed-loop power control (e.g., a closed-loop indicator field).

[0104] For example, using the power control adjustment state index l, the PUCCH transmission power (P) during the PUCCH transmission occasion (also called the transmission period, etc.) i for the active UL BWP b of the carrier f of serving cell c can be calculated. PUCCH、b,f,c (i,q u ,q d ,l)) may also be expressed by the following formula (1).

[0105] The power control adjustment state may also be called the PUCCH power control adjustment state, the first or second state, etc.

[0106] Furthermore, the PUCCH transmission opportunity i is a predetermined period during which PUCCH is transmitted, and may consist of, for example, one or more symbols, one or more slots, etc.

[0107]

number

[0108] In equation (1), P CMAX,f,c (i) is, for example, the transmit power of the user terminal set for the carrier f of serving cell c in transmission opportunity i (also called maximum transmit power, UE maximum output power, etc.). O_PUCCH,b,f,c (q u) is, for example, a parameter relating to the target received power set for the active UL BWP b of the carrier f of serving cell c in a transmission opportunity i (also known as a parameter relating to the transmit power offset, transmit power offset P0, or target received power parameter, etc.).

[0109] M PUCCH RB,b,f,c (i) is the number of resource blocks (bandwidth) allocated to PUCCH for transmission opportunities i in the active UL BWP b of a serving cell c and carrier f with subcarrier spacing μ. b,f,c (q d ) is, for example, the index q of the reference signal for the downlink BWP (path loss reference RS, path loss measurement DL RS, PUCCH-PathlossReferenceRS) associated with the active UL BWP b of the carrier f of serving cell c. d This is the path loss calculated on the user terminal using [a specific method / tool].

[0110] Δ F_PUCCH (F) is a higher-level parameter given for each PUCCH format. Δ TF,b,f,c (i) is the transmission power adjustment component (offset) for the UL BWP b of the carrier f of serving cell c.

[0111] g b,f,c (i,l) is a value based on the TPC command of the above power control adjustment state index l of the active UL BWP of the carrier f of serving cell c and transmission opportunity i (e.g., power control adjustment state, cumulative value of TPC commands, closed-loop value, PUCCH power adjustment state). For example, g b,f,c (i,l) may also be expressed by equation (2). l may be called a closed-loop index.

[0112]

number

[0113] In equation (2), δ PUCCH,b,f,c (m,l) is the TPC command value at the PUCCH transmission opportunity m. Σ C(C_i)-1 m=0 δ PUCCH,b,f,c (m,l) is the K before the transmission opportunity i-i0 of PUCCH. PUCCH (i-i0)-1 symbol and the K before the transmission opportunity i of PUCCH PUCCH (i) The group C(C) between the symbol and i The sum of the TPC command values ​​in the set of TPC command values, where i0 is an integer greater than or equal to 1. The TPC command value in a PUCCH transmission opportunity may be the TPC command indicated by the TPC command field value in a DCI (e.g., DCI format 1_0 or 1_1) detected by the active UL BWP b of the carrier f of serving cell c, or it may be the TPC command indicated by the TPC command field value in a DCI (CRC scrambled) (e.g., DCI format 2_2) that has a CRC parity bit scrambled with a specific Radio Network Temporary Identifier (RNTI) (e.g., TPC-PUCCH-RNTI).

[0114] If the UE is provided with information indicating the use of two PUCCH power control adjustment states (twoPUCCH-PC-AdjustmentStates) and PUCCH spatial relationship information (PUCCH-SpatialRelationInfo), then l may be {0,1}. If the UE is not provided with information indicating the use of two PUCCH power control adjustment states or PUCCH spatial relationship information, then l may be 0.

[0115] When the UE obtains a TPC command value from DCI format 1_0 or 1_1, and when the UE is provided with PUCCH spatial relation information, the UE may obtain a mapping (association, relationship) between the PUCCH spatial relation information ID (pucch-SpatialRelationInfoId) value and the closed-loop index (closedLoopIndex, power adjustment state index l) by index provided by the PUCCH P0 ID (p0-PUCCH-Id in p0-Set in PUCCH-Config-PowerControl). When the UE receives an activation command containing the value of the PUCCH spatial relation information ID, the UE may determine the value of the closed-loop index that provides the value of l through a link to the corresponding PUCCH P0 ID.

[0116] UE for the active UL BWP b of carrier f of serving cell c, and for the corresponding PUCCH power adjustment state l O_PUCCH,b,f,c (q u ) If the setting of the value is provided by the upper layer, g b,f,c (k,l)=0, k=0,1,...,i. If the UE is provided with PUCCH spatial relation information, the UE will be q u Based on the PUCCH P0 ID corresponding to l, the closed-loop index value corresponding to l, and the PUCCH spatial relation information associated with q u You can also determine the value of l from the value of .

[0117] q u This may also be a P0 ID (p0-PUCCH-Id) indicating a P0 for PUCCH (P0-PUCCH) within a P0 set (p0-Set) for PUCCH.

[0118] Note that equations (1) and (2) are merely illustrative and not limiting. The user terminal only needs to control the PUCCH's transmit power based on at least one of the parameters exemplified in equations (1) and (2), and additional parameters may be included, or some parameters may be omitted. Also, in equations (1) and (2) above, the PUCCH's transmit power is controlled for each active UL BWP of a carrier in a serving cell, but this is not limited to that. At least some of the serving cell, carrier, BWP, and power control adjustment state may be omitted.

[0119] (Initialization of beam renewal and PUCCH power control) In Rel.15 / 16, for PCell or PSCell, the UE transmits a PUCCH on the same cell as the PRACH transmit until 28 symbols after the last symbol of the first PDCCH receive in the search space set provided by the RRC information element "recoverySearchSpaceId" in which the UE detects the DCI format scrambled by C-RNTI or MCS-C-RNTI, and until the UE receives an activation command for "PUCCH-SpatialRelationInfo" or is provided with "PUCCH-SpatialRelationInfo" for the PUCCH resource.

[0120] In transmitting the PUCCH, the UE uses the same spatial filter as the previous (last) PRACCH transmission, and in equation 1 above, q u =0, q d =q new The power is determined by setting l=0.

[0121] For PCell or PSCell, within the search space set provided by the RRC information element "recoverySearchSpaceId" where the UE detected the CRC-scrambled DCI format by C-RNTI or MCS-C-RNTI, 28 symbols after the last symbol of the first PDCCH reception, the UE uses index q for PDCCH monitoring in the CORESET at index 0. new Assume the same antenna port pseudo-collocation parameters as those associated with it.

[0122] For PCell or PSCell, if a BFR MAC CE is sent using message 3 or message A of the CBRA procedure and a PUCCH resource is provided using "PUCCH-SpatialRelationInfo", then 28 symbols after the last symbol of the PDCCH reception that determines the completion of the CBRA procedure, the UE sends a PUCCH in the same cell as the PRACH transmission.

[0123] In the PUCCH transmission, the UE uses the same spatial filter as the previous PRACH transmission, and in equation 1 above, q u =0, q d =q new The power is determined by setting l=0. Here, q new This is the SS / PBCH block index selected for the most recent PRACH transmission.

[0124] The UE can provide a configuration for sending a PUCCH with a Link Recovery Request (LRR) using "schedulingRequestID-BFR-SCell-r16".

[0125] 28 symbols after the last symbol of the PDCCH received with DCI format, which has the same HARQ process number as the initial PUSCH transmission and has a toggled New Data Indicator (NDI) field, the UE will execute the corresponding index (index / indexes) q newIf present, monitor the PDCCH of all CORESETs in the SCell(s) indicated by MAC CE using the same antenna port pseudo-collocation parameters as those associated with it / them.

[0126] Furthermore, 28 symbols after the last symbol of the reception of a PDCCH with a DCI format that schedules the transmission of a PUSCH having the same HARQ process number as the initial PUSCH transmission and having a toggled NDI field, if "PUCCH-SpatialRelationInfo" is provided for PUCCH and no PUCCH with LRR has been transmitted, or has been transmitted in a PCell or PSCell, and the PUCCH-SCell is included in a SCell indicated by MAC CE, then in formula 1 above, q u =0, q d =q new Using the power determined with l=0, q for receiving periodic CSI-RS or SS / PBCH blocks new PUCCH is transmitted in PUCCH-SCell using the same spatial domain filter as the corresponding spatial domain filter.

[0127] Here, the setting of the 28-symbol subcarrier spacing (SCS) is the minimum SCS setting among the active DL BWP for PDCCH reception and the SCS setting of at least one SCell's active DL BWP(s).

[0128] (analysis) BFRs involve significant resource overhead and latency. From a network perspective, it is preferable to avoid UEs experiencing beam failure and to maintain beam connectivity as much as possible.

[0129] One possible solution is to frequently trigger beam reporting so that the base station directs a new beam before the UE enters a beam-fault condition. However, this method incurs significant resource overhead.

[0130] For example, one or more UEs may perform periodic (P) / semi-persistent (SP) beam reporting (see Figure 3A). In Figure 3A, UE#0 to UE#2 are performing periodic beam reporting. Beam reporting may also be transmitted using PUCCH / PUSCH. This beam reporting generates significant resource overhead. For most UEs, such frequent beam reporting is not necessary.

[0131] Furthermore, for example, one or more UEs may perform aperiodic (A) beam reporting (see Figure 3B). In Figure 3B, UE#0 to UE#2 are performing aperiodic beam reporting triggered by DCI. Aperiodic beam reporting allows the base station to frequently trigger beam reporting only for the UEs that require it. However, frequent beam reporting triggering is difficult considering the capacity / blockage of the PDCCH. Due to PDCCH blocking, the maximum number of DCIs that a base station can transmit per slot is usually limited.

[0132] Therefore, in Rel.17 and beyond, the introduction of event-triggered beam reporting is being considered. The UE will perform beam reporting when a specific event occurs.

[0133] However, the conditions for the event and the method of beam reporting based on the event are unclear. Failure to clarify the conditions for the event and the method of beam reporting based on the event may lead to a decrease in communication throughput and an increase in overhead.

[0134] Therefore, the inventors conceived of the conditions for the event and a method for beam reporting based on the event.

[0135] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0136] In this disclosure, “A / B / C” and “at least one of A, B, and C” may be interpreted as mutually exclusive.

[0137] In this disclosure, cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be interpreted interchangeably. In this disclosure, index, ID, indicator, and resource ID may be interpreted interchangeably. In this disclosure, support, control, controllable, operate, and operable may be interpreted interchangeably.

[0138] In this disclosure, configure, activate, update, indicate, enable, specify, and select may be interpreted as interchangeable.

[0139] In this disclosure, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof. In this disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher-layer parameters, RRC information elements (IE), and RRC messages may be interpreted as one another.

[0140] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0141] In this disclosure, MAC CE and activation / deactivation commands may be interpreted as interchangeable.

[0142] In this disclosure, pool, set, group, list, and candidate may be interpreted as interchangeable.

[0143] In this disclosure, DMRS, DMRS port, and antenna port may be interpreted as interchangeable.

[0144] In this disclosure, the terms special cell, SpCell, PCell, and PSCell may be interpreted as interchangeable.

[0145] In this disclosure, beam, spatial domain filter, spatial setting, TCI state, UL TCI state, unified TCI state, unified beam, common TCI state, common beam, TCI assumption, QCL assumption, QCL parameter, spatial domain receive filter, UE spatial domain receive filter, UE receive beam, DL beam, DL receive beam, DL precoding, DL precoder, DL-RS, RS of QCL type D in TCI state / QCL assumption, RS of QCL type A in TCI state / QCL assumption, spatial relationship, spatial domain transmit filter, UE spatial domain transmit filter, UE transmit beam, UL beam, UL transmit beam, UL precoding, UL precoder, and PL-RS may be interpreted as each other. In this disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS having QCL type X, DL-RS source, SSB, CSI-RS, and SRS may be interpreted as each other.

[0146] In this disclosure, CSI-RS, NZP-CSI-RS, periodic(P)-CSI-RS, P-TRS, semi-persistent(SP)-CSI-RS, aperiodic(A)-CSI-RS, TRS, CSI-RS for tracking, CSI-RS having TRS information (upper layer parameter trs-Info), NZP CSI-RS resource in an NZP CSI-RS resource set having TRS information, NZP-CSI-RS resource in an NZP-CSI-RS resource set consisting of multiple NZP-CSI-RS resources for the same antenna port, and TRS resource may be interpreted as one another. In this disclosure, CSI-RS resource, CSI-RS resource set, CSI-RS resource group, and information element (IE) may be interpreted as one another.

[0147] In this disclosure, the terms panel, Uplink (UL) transmit entity, TRP, spatial relationship, control resource set (CORESET), PDSCH, codeword, base station, antenna port for a signal (e.g., demodulation reference signal (DMRS) port), group of antenna ports for a signal (e.g., DMRS port group), group for multiplexing (e.g., code division multiplexing (CDM) group, reference signal group, CORESET group), CORESET pool, CORESET subset, CW, redundancy version (RV)), and layer (MIMO layer, transmit layer, spatial layer) may be interpreted as one another. Also, the terms panel identifier (ID) and panel may be interpreted as one another. In this disclosure, TRP ID, TRP-related ID, CORESET pool index, the position of one of two TCI states corresponding to a code point in a field within DCI (ordinal number, first TCI state or second TCI state), and TRP may be interpreted as other terms.

[0148] In this disclosure, TRP, transmit point, panel, DMRS port group, CORESET pool, and one of two TCI states associated with one code point in the TCI field may be interpreted as one another.

[0149] In this disclosure, CORESET0, CORESET having index 0, and common CORESET may be interpreted as interchangeable.

[0150] In this disclosure, the Radio Resource Management (RRM) report may be interpreted interchangeably with the Layer 3 (L3) measurement report.

[0151] In this disclosure, DL TCI, DL only TCI, separate DL only TCI, DL common TCI, DL unified TCI, common TCI, and unified TCI may be interpreted interchangeably. In this disclosure, UL TCI, UL only TCI, separate UL only TCI, UL common TCI, UL unified TCI, common TCI, and unified TCI may be interpreted interchangeably.

[0152] In this disclosure, the terms "setting / instructing / updating a separate TCI state," "setting / instructing a TCI state for DL ​​only," "setting / instructing / updating a TCI state for UL only," and "setting / instructing / updating a TCI state for DL ​​and UL" may be interpreted as mutually interchangeable.

[0153] In this disclosure, "joint TCI pool" and "when a joint TCI pool is established" may be interpreted interchangeably. In this disclosure, "separate TCI pool" and "when a separate TCI pool is established" may be interpreted interchangeably.

[0154] In this disclosure, event-based beam reporting, beam reporting based on the occurrence of an event, event-triggered beam reporting, and event-triggered beam reporting may be interpreted interchangeably.

[0155] (Wireless communication method) <First Embodiment> In the first embodiment, the conditions for events related to beam reporting are described.

[0156] Embodiment 1-1 One or more events may be defined that trigger a beam report to the UE.

[0157] The event in question may be at least one of the events listed below: • Event (1): The serving beam deteriorates below a certain threshold (for example, this may be called Event A2). • Event (2): The neighbor beam performs better than the serving beam plus an offset (for example, this may be called Event A3). • Event (3): The adjacent beam improves beyond a certain threshold (for example, this may be called Event A4). • Event (4): The serving beam deteriorates below the first threshold, and the adjacent beam improves above the second threshold (for example, this may be called Event A5). • Event (5): The neighbor beam performs better than the serving beam plus an offset (for example, this may be called Event A6). • Event (6): The interference value exceeds a certain threshold (for example, this may be called Event I1).

[0158] Please note that the symbols used to refer to events in this disclosure are merely examples, and the letters and numbers used are not limited to these.

[0159] The UE may trigger a beam report based on at least one of the above events. The beam report may be a non-periodic Layer 1 (L1) beam report.

[0160] In this disclosure, a serving beam may be a specific beam different from the adjacent beams described below (see Figure 4). In this disclosure, a serving beam may mean the current TCI state / spatial relationship that is indicated / activated for a specific channel / signal within the existing (Rel. 15 / 16) TCI state framework. A serving beam may also mean the current joint TCI state / separate TCI state that is indicated / activated within the common / unified TCI state framework defined in Rel. 17 and later. A serving beam may also mean the beam that has been recently reported as an L1 RSRP / SINR beam report.

[0161] In this disclosure, adjacent beams may mean TCI states / spatial relationships / joint TCI states / separate TCI states that are set / activated and are different from serving beams.

[0162] At least one of the above events may correspond to an event in an existing RRM report (as defined in Rel. 15 / 16).

[0163] For example, the above event (1) may have an entering condition where the sum of the serving beam measurement result and a specific hysteresis parameter falls below a specific threshold. Alternatively, the above event (1) may have a leaving condition where the difference between the serving beam measurement result and a specific hysteresis parameter exceeds a specific threshold.

[0164] For example, the input condition for event (2) above may be that the value obtained by subtracting a specific hysteresis parameter from the sum of the measurement result of the adjacent beam, the offset specific to the measurement object of the adjacent beam, and the offset specific to the adjacent beam exceeds the sum of the measurement result of the specific beam, the offset specific to the measurement object of the specific beam, the offset specific to the specific beam, and the offset related to the event. Alternatively, the exit condition for event (2) above may be that the sum of the measurement result of the adjacent beam, the offset specific to the measurement object of the adjacent beam, the offset specific to the adjacent beam, and the specific hysteresis parameter falls below the sum of the measurement result of the specific beam, the offset specific to the measurement object of the specific beam, the offset specific to the specific beam, and the offset related to the event.

[0165] For example, event (3) above may have an input condition that the value obtained by subtracting a specific hysteresis parameter from the sum of the measurement result of the adjacent beam, the offset specific to the measurement object of the adjacent beam, and the offset specific to the adjacent beam exceeds a specific threshold. Alternatively, event (3) above may have a release condition that the sum of the measurement result of the adjacent beam, the offset specific to the measurement object of the adjacent beam, the offset specific to the adjacent beam, and the specific hysteresis parameter falls below a specific threshold.

[0166] For example, the above event (4) may have a first input condition that the sum of the serving beam measurement result and a specific hysteresis parameter falls below a first threshold, and a second input condition that the value obtained by subtracting a specific hysteresis parameter from the sum of the adjacent beam measurement result, the measurement object-specific offset of the adjacent beam, and the adjacent beam's specific offset exceeds a second threshold.

[0167] Furthermore, the above event (4) may have a first exit condition where the difference between the measurement result of the serving beam and a specific hysteresis parameter exceeds a first threshold, and a second exit condition where the sum of the measurement result of the adjacent beam, the measurement object-specific offset of the adjacent beam, the specific offset of the adjacent beam, and the specific hysteresis parameter falls below a second threshold.

[0168] For example, the input condition for event (5) above may be that the value obtained by subtracting a specific hysteresis parameter from the sum of the measurement results of the adjacent beam and the intrinsic offset of the adjacent beam exceeds the sum of the measurement results of the serving beam, the intrinsic offset of the serving beam, and the offset related to the event. Alternatively, the exit condition for event (5) above may be that the sum of the measurement results of the adjacent beam, the intrinsic offset of the adjacent beam, and the specific hysteresis parameter is less than the sum of the measurement results of the serving beam, the intrinsic offset of the serving beam, and the offset related to the event.

[0169] For example, event (6) above may have an input condition that the interference value to the serving beam exceeds a specific threshold. Alternatively, event (6) above may have a departure condition that the interference value to the serving beam falls below a specific threshold.

[0170] In this disclosure, at least one of the thresholds (specific / first / second thresholds), measurement results, offsets, and hysteresis parameters may be calculated (or presented) in specific units (e.g., at least one of dB and dBm).

[0171] In this disclosure, at least one of the thresholds (specific / first / second thresholds), offsets, and hysteresis parameters may be set in the UE using upper-layer signaling. Furthermore, the offsets in this disclosure may be predefined in the specification.

[0172] In the first embodiment, the "measurement result" may be at least one of the following, for example, L1-RSRP, L1-RSRQ, L1-SINR, L1-SNR, or the corresponding L3 measurement result (for example, L3-RSRP). Hereafter, "L1-", "L3-", etc. may be omitted.

[0173] Embodiment 1-2 One or more serving beams may be configured / directed to the UE.

[0174] A single serving beam may be configured / instructed to the UE (Embodiment 1-2-1).

[0175] The serving beam in question may be a beam (TCI state) corresponding to a specific CORESET. This specific CORESET may, for example, be the CORESET having the smallest (or largest) CORESET ID.

[0176] Furthermore, when a common TCI state is configured for a UE, that single serving beam may have a single instructed / activated joint TCI state / DL separate TCI state.

[0177] The UE may determine the occurrence of at least one of the above events by comparing the received power / received quality of the one serving beam with the received power / received quality of other beams (adjacent beams).

[0178] Figure 5A shows an example of beam comparison according to Embodiment 1-2. As shown in the example in Figure 5A, one serving beam and other adjacent beams are set for the UE. The UE compares the one serving beam with the other adjacent beams to determine if an event has occurred. RSRP is used as the received power of the beam in the example in Figure 5A.

[0179] Furthermore, a specific offset may be used when comparing the serving beam with the adjacent beam. For example, the measurement result of the serving beam plus a specific offset may be compared with the measurement result of the adjacent beam. By using an offset in this way, it is possible to suppress the occurrence of excessive beam switching.

[0180] The specific offset may be set / notified to the UE using higher-layer signaling, or it may be specified in advance.

[0181] Multiple serving beams may be configured / instructed to the UE (Embodiment 1-2-2).

[0182] The multiple serving beams may correspond to a specific CORESET (TCI state). This specific CORESET may correspond to a specific number of CORESET IDs, or to all CORESETs configured in the UE. Furthermore, the multiple serving beams may be active TCI states for multiple or all PDSCHs.

[0183] Furthermore, when a common TCI state is configured for a UE, the multiple serving beams may be in a joint TCI state or a separate TCI state of DL, configured / notified using higher-layer signaling (e.g., RRC signaling / MAC CE).

[0184] The UE may determine the occurrence of at least one of the above events by comparing the received power / received quality of at least one of the multiple serving beams with the received power / received quality of the other beams (adjacent beams).

[0185] For example, the beam with the lowest (or highest) received power / received quality among the multiple serving beams may be compared with the adjacent beam. Alternatively, for example, the average received power / received quality of the multiple serving beams may be calculated, and this calculated value may be compared with the received power / received quality of the adjacent beam.

[0186] Figure 5B shows another example of beam comparison according to Embodiment 1-2. As shown in the example in Figure 5B, three serving beams and other adjacent beams are set up for the UE. The UE compares the three serving beams with the other adjacent beams to determine if an event has occurred. RSRP is used as the received power of the beams in the example in Figure 5B.

[0187] Furthermore, a specific offset may be used when comparing the serving beam with the adjacent beam. For example, the measurement result of the serving beam with a specific offset added may be compared with the measurement result of the adjacent beam. By using an offset in this way, it is possible to suppress the occurrence of excessive beam switching.

[0188] The specific offset may be set / notified to the UE using higher-layer signaling, or it may be specified in advance.

[0189] The UE may also determine one or more serving beams (Embodiment 1-2-3).

[0190] For example, the UE may determine the top X beams (where X is an integer greater than or equal to 1) from among the measured beams based on received power / received quality as serving beams.

[0191] X may be set by upper-layer signaling, predefined in the specifications, or determined based on UE capability information reports.

[0192] According to the above embodiments 1-1 / 1-2, the NW can suppress the increase in the frequency of beam reporting by the UE.

[0193] Since UEs (Unified Elementals) only report beams when specific events occur, high-frequency beam reporting can be limited to only the necessary UEs, thereby suppressing increased resource overhead.

[0194] Embodiments 1-3 A base station may configure periodic / semi-persistent / aperiodic beam reports (first beam reports) for multiple UEs. In addition, a base station may configure periodic / semi-persistent beam reports (second beam reports) with a shorter period (or higher frequency) than the first beam reports for UEs where events occur at a frequency above a certain threshold.

[0195] In this disclosure, the first beam report may be an event-independent beam report. Also, in this disclosure, the second beam report may be the event-triggered beam report described in the first embodiment.

[0196] An event occurring at a frequency above a certain threshold may mean that an event occurs more than a certain number of times within a specific number of time units (e.g., slots / symbols) (an integer greater than or equal to 1).

[0197] Information regarding at least one of the reporting cycle, duration, and frequency of beam reports may be set / notified / instructed to the UE using upper-layer signaling / physical layer signaling. Information regarding the first beam report and information regarding the second beam report may be set / notified / instructed separately.

[0198] According to this, base stations can determine which terminals require high-frequency beam reporting based on the frequency of events.

[0199] Figure 6 shows an example of beam reporting according to Embodiment 1-3. In Figure 6, the first beam report and the second beam report are set for UE#0 to UE#2. As shown in Figure 6, for UE#0, where the second beam report event occurs frequently (above a certain threshold), the base station may set the first beam report / second beam report with a shorter period.

[0200] Furthermore, based on the frequency of events related to the second beam report, the base station may change the period of the second beam report (for example, by setting it to a longer period). For example, if events related to the second beam report occur infrequently (below a certain threshold) in the UE, the base station may set the second beam report to have a longer period in that UE. This makes it possible to reduce the burden on the UE to check for the occurrence of events.

[0201] Based on the frequency of events, the UE may send information / requests to the NW to change the cycle of the first beam report / second beam report. Such information / requests may be sent using RRC signaling / MAC CE / UCI.

[0202] According to the first embodiment described above, events for which beam reporting is performed can be appropriately defined.

[0203] <Second Embodiment> In the second embodiment, the operation of the UE / base station after the event occurs will be described.

[0204] Embodiment 2-1 The UE may send a PRACH when a specific event occurs (when the input conditions for a specific event, as described in Embodiment 1-1, are met). In other words, in Embodiment 2-1, an event-triggered beam report may correspond to a PRACH.

[0205] The PRACH occasion / resource transmitted may be associated with information about the beam being modified (new beam). The UE may use PRACH to transmit information about the new beam to the NW.

[0206] Multiple PRACH opportunities / resources may be configured for a UE. The UE may select a PRACH opportunity / resource from among these multiple opportunities / resources and send / report information about new beams.

[0207] PRACH opportunities / resources for beam reporting and PRACH opportunities / resources for other uses (e.g., BFR) may be configured separately. This is preferably available in CFRA. This allows the network to determine that it has received an event-based beam report based on the PRACH opportunities / resources.

[0208] Furthermore, PRACH opportunities / resources for beam reporting and PRACH opportunities / resources for other applications (e.g., BFR) may be common. This is preferably available in CBRA.

[0209] According to this, the network cannot determine that it has received an event-based beam report based on PRACH opportunities / resources. Therefore, the UE may send message 3 / message A containing specific information. The network may then determine that it has received an event-based beam report based on that specific information.

[0210] The specific information may be included in the MAC CE. The MAC CE may be called the Event Trigger Beam Reporting MAC CE. The MAC CE may be the MAC CE described in Embodiment 2-2 below, or it may be another MAC CE (for example, a MAC CE specified in Rel. 17 or later).

[0211] Embodiment 2-2 In Embodiment 2-2, the event-triggered beam report may correspond to a MAC CE. A MAC CE containing specific information for notifying an event-based beam report (hereinafter referred to as the MAC CE for event-triggered beam reporting, the first MAC CE, etc.) may be an existing MAC CE (as defined in Rel. 15 / 16).

[0212] In Embodiment 2-2, the first MAC CE may have the same configuration as the MAC CE for BFR. The MAC CE for BFR may include at least one of a BFR MAC CE and a Truncated BFR MAC CE.

[0213] The first MAC CE may include multiple fields. These fields may include a field indicating beam fault detection for the SpCell (SP field, denoted as "SP"), and a field indicating beam fault detection for the SCell of serving cell index (ID) i (C i Field, "C i The field may include at least two of the following: a field indicating the presence of a candidate RS ID field within the same octet (the AC field, labeled "AC"), the candidate RS ID field, the reserved bit field (the R field, labeled "R"), and a field indicating the value of the received power / received quality (e.g., RSRP).

[0214] The UE may use specific fields (e.g., at least one of the R field and the SP field) to indicate whether the first MAC CE is a MAC CE for BFR or a MAC CE for event-triggered beam reporting.

[0215] The UE may be configured using higher-layer signaling (e.g., RRC signaling) to indicate whether the first MAC CE is a MAC CE for BFR or a MAC CE for event-triggered beam reporting.

[0216] The UE may indicate that a MAC CE is a MAC CE for BFR by setting the value of a specific (e.g., first) specific field contained in the first MAC CE to a first value (e.g., 0 (or 1)).

[0217] Furthermore, the UE may indicate that a MAC CE is an event-triggered beam reporting MAC CE by setting the value of a specific (e.g., first) specific field contained in the first MAC CE to a second value (e.g., 1 (or 0)).

[0218] The UE may use multiple MAC CEs in at least one of the following cases: when reporting multiple candidate RS IDs for a single cell, and when reporting multiple received power / received quality (e.g., RSRP) values ​​for a single cell.

[0219] The UE may receive a UL Grant (DCI) for the first MAC CE. If the UE does not receive a UL Grant for the first MAC CE, it may send an SR to the NW requesting a UL Grant. If no resources are set up for the SR, the UE may send a PRACH as specified in Rel. 15 / 16.

[0220] The first MAC CE may contain information from multiple cells. In this case, C i An octet containing a field may be set.

[0221] Furthermore, the first MAC CE may contain information for only one cell (for example, the cell that sends the MAC CE). In this case, C i An octet containing a field does not need to be set (it may be omitted).

[0222] The MAC CE for event-triggered beam reporting may have at least one candidate RS ID field. In this case, the first AC field may be changed to an R bit, or the value of the AC field may be ignored.

[0223] For BFR MAC CEs, the candidate RS ID field does not need to be present.

[0224] Figure 7 shows an example of the MAC CE configuration according to Embodiment 2-2. In Figure 7, the UE uses the MAC CE to transmit event trigger beam reports to the NW.

[0225] The MAC CE shown in Figure 7 has the same configuration as the MAC CE for BFR. Specifically, the MAC CE has an SP field, C i The field includes (i is an integer from 1 to 7), candidate RS ID field, AC field, and R field.

[0226] In Figure 7, the UE may use the SP field contained in the MAC CE to indicate that the MAC CE is an event-triggered beam reporting MAC CE. Alternatively, the UE may use the first R field contained in the MAC CE to indicate that the MAC CE is an event-triggered beam reporting MAC CE.

[0227] The MAC CE for event-triggered beam reporting may include fields that report multiple candidate RS IDs (and their corresponding received power / received quality (e.g., RSRP) values).

[0228] The maximum number of candidate RS IDs reported by the UE may be set using higher-layer signaling. The UE may also determine a number of candidate RS IDs less than the set maximum.

[0229] Figure 8 shows another example of the MAC CE configuration according to Embodiment 2-2. As shown in Figure 8, the first MAC CE is supplemented with fields (first-fourth candidate RS ID fields) that report four candidate RS IDs (and corresponding received power / received quality (e.g., RSRP) values). The UE may report up to four candidate RS IDs (and RSRP values) whose received power / received quality exceeds (is greater than) a certain threshold.

[0230] The R field shown in Figure 8 may indicate whether or not the following octet exists. This can reduce the signaling overhead of MAC CE.

[0231] A MAC CE containing the fields shown in Figure 8 may contain information from multiple cells. In this case, C i An octet containing a field may be set.

[0232] Furthermore, a MAC CE containing the fields shown in Figure 8 may contain information for only one cell (for example, the cell that sends the MAC CE). In this case, C i An octet containing a field does not need to be set (it may be omitted).

[0233] A MAC CE containing the fields shown in Figure 8 may have at least one candidate RS ID field. In this case, the first AC field may be changed to an R bit, or the value of the AC field may be ignored.

[0234] Note that event-triggered beam reports may also be CSI reports.

[0235] According to the second embodiment described above, beam reporting based on the occurrence of an event allows for appropriate control of the operation of the UE / base station after the event occurs.

[0236] <Third Embodiment> In a third embodiment, the updating / modification of the beam state in beam reporting based on the occurrence of an event is described.

[0237] In the following, the first timing may be defined as at least one of the following cases: after the completion of the CFRA / CBRA procedure and after the completion of the first MAC CE transmission.

[0238] Furthermore, in the following, the second timing may be at least one of the following cases: receiving a signal equivalent to a BFR response, receiving a DCI in a dedicated search space, receiving message 4 (or a signal equivalent to message 4), and receiving a DCI equivalent to an ACK (acknowledgment) to a PUSCH in a random access procedure.

[0239] After the first timing condition is met and a specific period of time has elapsed, the UE / base station may update the beam state (which may also be called beam state / beam assumption).

[0240] Furthermore, after the first timing condition is met and a specific period has elapsed, the UE / base station may reset / update parameters / states related to the transmit power control of the UL channel / signal (e.g., PUSCH / PUCCH / SRS).

[0241] Furthermore, after the first and second timing conditions are met and a specific period of time has elapsed, the UE / base station may update the beam state.

[0242] Furthermore, after the first and second timing conditions are met and a specific period has elapsed, the UE / base station may reset / update parameters / states related to the transmit power control of the UL channel / signal (e.g., PUSCH / PUCCH / SRS).

[0243] The update of the beam state may be performed for the beams of a specific channel / signal (e.g., PDCCH / PUCCH). Also, the update of the beam state may be performed for the beams of a plurality of channels / signals (e.g., all channels / signals). Further, the update of the beam state may be performed for the beams of a plurality of channels / signals (e.g., all channels / signals except CSI-RS / SRS).

[0244] After satisfying the first timing and after a specific period has elapsed, the base station may not update the state of the beam. Also, after satisfying the first timing and the second timing and after a specific period has elapsed, the base station may not update the state of the beam.

[0245] For example, the update of the beam state at the base station may be performed when making an (explicit) response to an event-triggered beam report. When the UE receives an (explicit) response to an event-triggered beam report, it may assume that the beam state is updated. The occurrence of the second timing may mean the completion of reception of an event-triggered beam report by the base station. The "response" in the third embodiment may correspond to at least one of the signals / information received at the second timing.

[0246] The completion of reception of an event-triggered beam report by the base station may mean permission / approval of a change to the beam reported using the event-triggered beam report.

[0247] After the completion of reception of an event-triggered beam report by the base station, two states may be defined: a state (the first state) where permission / approval of a change to the beam reported using the event-triggered beam report has not been given, and a state (the second state) where permission / approval of a change to the beam reported using the event-triggered beam report has been given.

[0248] The UE may receive a response (the channel / signal on which the response is transmitted) corresponding to each of the two states. Based on the received response, the UE may decide whether or not to update / modify the beam state of a particular channel / signal after the response.

[0249] For example, if a response indicating a first state is received, the UE may decide not to update / change the beam state of a particular channel / signal (e.g., all channels / signals) after receiving that response.

[0250] Furthermore, for example, if a response indicating a second state is received, the UE may decide to update / change the beam state of a specific channel / signal (e.g., all channels / signals) after receiving the response.

[0251] The UE may receive responses corresponding to each of the two states using different CORESET / search spaces. Alternatively, the UE may receive responses corresponding to each of the two states using the same (or common) CORESET / search space but using different DCIs. These different DCIs may mean at least one of the following: a DCI with at least one field that is different, a DCI in a different DCI format, or a DCI that is CRC scrambled using a different RNTI.

[0252] Furthermore, this embodiment may be limited to cases where the UE notifies / instructs, using message 3 / message A, that the MAC CE to be transmitted is an event trigger beam reporting MAC CE. In this case, the NW can determine for what purpose the CBRA procedure was used.

[0253] According to the third embodiment described above, it is possible to appropriately control the updating / modification of the beam state in beam reporting based on the occurrence of an event.

[0254] <Fourth Embodiment> In a fourth embodiment, the operation of an existing beam report (which may be called a first beam report) (as defined up to Rel. 15 / 16) and an event-based beam report (which may be called a second beam report) will be described.

[0255] The UE may control the implementation of the first and second beam reports based on at least one of the embodiments 4-1 to 4-5 described below.

[0256] Figures 9A and 9B show an example of an event occurrence timeline according to the fourth embodiment. In Figures 9A and 9B, it is set that a first beam report will be made. In Figure 9A, the first beam report is not made within a specific period from the occurrence of the event. On the other hand, in Figure 9B, the first beam report is made within a specific period from the occurrence of the event.

[0257] Figures 10A and 10B show other examples of event occurrence timelines according to the fourth embodiment. In Figures 10A and 10B, a first beam report is set to be made. In Figure 10A, no events occur within a specific period prior to the first beam report. On the other hand, in Figure 10B, an event occurs within a specific period prior to the first beam report.

[0258] The following embodiments 4-1 to 4-5 describe cases in which the first beam report is made within a specific period following the occurrence of an event, as shown in Figure 9B. However, they may also be appropriately applied to cases in which the event occurs within a specific period prior to the first beam report, as shown in Figure 10B.

[0259] When it is configured / instructed to perform a first beam report during a specific period following the occurrence of an event, the UE may perform the first beam report instead of the second beam report (Embodiment 4-1).

[0260] When it is configured / instructed to perform a first beam report within a specific period following the occurrence of an event, the UE may perform a second beam report instead of the first beam report (Embodiment 4-2).

[0261] When it is configured / instructed to perform a first beam report within a specific period following the occurrence of an event, the UE may perform both the first and second beam reports (Embodiment 4-3).

[0262] When it is set / instructed to make a first beam report within a specific period of time from the occurrence of an event, the UE may make at least one of the first beam report and the second beam report based on certain conditions (Embodiment 4-4).

[0263] In Embodiment 4-4, the specific condition may be a condition based on information reported using the second beam report. For example, if a new candidate beam reported using the second beam report is included in (or identical to) the first beam report, the UE may perform the first beam report but not the second beam report. Otherwise, the UE may perform the second beam report, or both the first and second beam reports.

[0264] When it is configured / instructed to perform a first beam report within a specific period following the occurrence of an event, the UE may perform at least one of the first and second beam reports based on the upper layer signaling configuration (Embodiment 4-5).

[0265] In Embodiments 4-5, for example, when configured using upper-layer signaling, the UE may perform a second beam report, or both a first and a second beam report. Otherwise, the UE may perform a first beam report but not a second beam report.

[0266] According to Embodiment 4-5, by performing the second beam report using MAC CE, more information can be transmitted to the NW.

[0267] Note that the specific period in this embodiment may be defined in advance in the specification, or may be set / notified to the UE using upper layer signaling.

[0268] According to the above Fourth Embodiment, it is possible to appropriately control the implementation of the existing beam report (defined up to Rel.15 / 16) and the beam report based on the occurrence of an event.

[0269] <Fifth Embodiment> Upper layer parameters (RRC IE) / UE capabilities corresponding to the functions (features) in at least one of the above embodiments may be defined. The UE capabilities may indicate that it supports this function.

[0270] A UE in which an upper layer parameter corresponding to the function (enabling the function) is set may perform the function. It may be defined that "a UE in which an upper layer parameter corresponding to the function is not set does not perform the function (for example, in accordance with Rel.15 / 16)".

[0271] A UE that has reported UE capabilities indicating that it supports the function may perform the function. It may be defined that "a UE that has not reported UE capabilities indicating that it supports the function does not perform the function (for example, in accordance with Rel.15 / 16)".

[0272] When a UE reports UE capabilities indicating that it supports the function and an upper layer parameter corresponding to the function is set, the UE may perform the function. It may be defined that "when a UE does not report UE capabilities indicating that it supports the function or an upper layer parameter corresponding to the function is not set, the UE does not perform the function (for example, in accordance with Rel.15 / 16)".

[0273] UE capability may indicate whether the UE supports this feature or not.

[0274] UE capability may be defined by whether or not it supports event-triggered beam reporting.

[0275] UE capability may be defined by whether or not it supports PRACH based on event-triggered beam reporting.

[0276] UE capability may be defined by whether or not it supports MAC CE based on event-triggered beam reporting (MAC CE transmitted by PUSCH).

[0277] UE capability may be defined by whether or not it supports new MAC CEs (MAC CEs transmitted by PUSCH) based on event-triggered beam reporting (as defined in Rel. 17 and later). If a UE does not support such UE capability, and the UE supports at least one of SCell's BFR and CBRA's BFR using BFR MAC CEs in Rel. 16, then BFR MAC CEs may be used for event-triggered beam reporting.

[0278] UE capability may be defined by the number of new candidate beam (RS) IDs per CC / MAC CE that the UE can report.

[0279] UE capability may be defined by whether or not it supports reporting of received power / received quality (e.g., RSRP) values ​​within MAC CE.

[0280] According to the fifth embodiment described above, the UE can achieve the above functions while maintaining compatibility with existing specifications.

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

[0282] Figure 11 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0283] Furthermore, the wireless communication system 1 may 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)), and so on.

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

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

[0286] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0287] 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 (CC) and Dual Connectivity (DC).

[0288] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a 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 above 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 fall in a frequency band higher than FR2.

[0289] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0290] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

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

[0292] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0293] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. 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), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0294] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

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

[0296] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0297] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

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

[0299] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0300] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0301] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0302] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0303] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

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

[0305] 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 SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0306] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0307] (base station) Figure 12 shows an example of the configuration of a base station according to one 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 one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0308] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0309] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

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

[0311] The transmitting / receiving 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 transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0312] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0313] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

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

[0315] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0317] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0318] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

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

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

[0321] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to 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 also measure received power (e.g., Reference Signal Received Power (RSRP)), reception 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.

[0322] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0323] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0324] The control unit 110 may control the reception of at least one of a first beam report not based on an event and a second beam report based on an event relating to at least one of a plurality of beams at the terminal. When the second beam report is made, the transmitting / receiving unit 120 may receive at least one of a random access channel associated with first information relating to a new candidate beam and a Medium Access Control (MAC) control element containing second information relating to a new candidate beam (first and second embodiments).

[0325] (User terminal) Figure 13 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0326] In this example, the functional blocks of the characteristic parts of this 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 part described below may be omitted.

[0327] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

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

[0329] The transmitting / receiving 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 transmitting / receiving unit 220 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0330] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0331] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0332] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0333] The transmitting / receiving unit 220 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0334] The transmitting / receiving 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 and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0335] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, 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, and output a baseband signal.

[0336] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0337] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

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

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

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

[0341] In this disclosure, the transmitting and receiving units of the user terminal 20 may consist of at least one of a transmitting / receiving unit 220, a transmitting / receiving antenna 230, and a transmission path interface 240.

[0342] The control unit 210 may control at least one of a first beam report not based on an event relating to at least one of a plurality of beams, and a second beam report based on the event. When the transmitting unit 220 performs the second beam report, it may transmit at least one of a random access channel associated with first information relating to a new candidate beam and a Medium Access Control (MAC) control element containing second information relating to a new candidate beam (first and second embodiments).

[0343] The MAC control element may have the same configuration as the MAC control element for beam fault detection (second embodiment).

[0344] The control unit 210 may, after the transmission of the MAC control element and after a specific period of time has elapsed, control at least one of the following: updating the beam state of at least one of a specific channel and signal, and resetting the transmit power control parameter of at least one of the uplink channel and uplink signal (third embodiment).

[0345] The control unit 210 may control the system to perform at least one of the first beam report and the second beam report based on the timing of the event occurrence and the timing of the first beam report after the event occurrence (fourth embodiment).

[0346] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0347] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

[0349] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0350] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

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

[0352] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0353] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly.

[0354] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0355] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

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

[0357] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0359] 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), and a field programmable gate array (FPGA), and some or all of each functional block may be implemented using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0360] (modified version) In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be used interchangeably. Also, a signal may be a message. A reference signal may be abbreviated as RS and may be called a pilot, pilot signal, etc., depending on the applicable standard. Also, a component carrier (CC) may be called a cell, frequency carrier, carrier frequency, etc.

[0361] A wireless frame may consist of one or more periods (frames) in the time domain. Each of these periods (frames) constituting a wireless frame may be called a subframe. Furthermore, a subframe may consist 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.

[0362] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0363] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

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

[0365] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0366] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0367] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0368] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0369] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0370] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0371] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0372] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0373] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0374] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0375] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0376] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0377] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0378] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0379] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0381] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

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

[0383] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0384] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0385] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0386] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0387] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not providing notification of the specified information or by providing notification of other information).

[0388] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0389] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0390] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0391] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0392] 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," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0393] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0394] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services 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 ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0395] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0396] A mobile station may also be called 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 appropriate term.

[0397] 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. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. 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.

[0398] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this 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), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, uplink channel and downlink channel may be interpreted as sidelink channel.

[0399] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0400] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0401] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0402] Each aspect / embodiment described in this disclosure includes 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) (xG (where x is, for example, an integer or decimal)), 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®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may be applied to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that extend these. It may also be applied in combination with multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0403] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0404] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0405] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0406] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0407] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0408] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0409] The term "maximum transmit power" as used in this disclosure may mean the maximum transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0410] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0411] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0412] In this 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 "combine" may be interpreted similarly to "different."

[0413] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0414] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0415] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. A receiving unit that receives a higher layer parameter indicating a threshold corresponding to the event related to the largest RSRP among the reference signal received power (RSRP) corresponding to each of a plurality of transmission setting instruction (TCI) states, The system includes a control unit that controls the reporting of channel status information (CSI) triggered by the aforementioned event, The TCI state is an activated TCI state for both the uplink and the downlink, and the TCI state is applied to multiple channels including both the uplink and the downlink. A terminal that performs the CSI report when the largest RSRP among the RSRPs corresponding to each of the multiple activated TCI states satisfies the threshold condition.

2. A step of receiving a higher layer parameter that indicates a threshold corresponding to the event relating to the largest RSRP among the reference signal received power (RSRP) corresponding to each of a plurality of transmit setting instruction (TCI) states, The process includes a step of controlling the reporting of channel status information (CSI) triggered by the aforementioned event, The TCI state is an activated TCI state for both the uplink and the downlink, and the TCI state is applied to multiple channels including both the uplink and the downlink. A wireless communication method for a terminal in which a CSI report is performed when the largest RSRP among the RSRPs corresponding to each of the multiple activated TCI states satisfies the conditions relating to the threshold.

3. A transmission unit that transmits a higher layer parameter indicating a threshold corresponding to the event related to the largest RSRP among the reference signal received power (RSRP) corresponding to each of a plurality of transmission setting instruction (TCI) states, The system includes a receiving unit that receives a channel status information (CSI) report triggered by the aforementioned event, The TCI state is an activated TCI state for both the uplink and the downlink, and the TCI state is applied to multiple channels including both the uplink and the downlink. A base station that performs the CSI report when the largest RSRP among the RSRPs corresponding to each of the multiple activated TCI states satisfies the threshold condition.

4. A system including terminals and base stations, The aforementioned terminal is A receiving unit that receives a higher-layer parameter indicating a threshold corresponding to the event related to the largest Reference Signal Received Power (RSRP) among the Reference Signal Received Powers (RSRP) corresponding to each of multiple Transmit Configuration Instruction (TCI) states, The system includes a control unit that controls the reporting of channel status information (CSI) triggered by the aforementioned event, The TCI state is an activated TCI state for both the uplink and the downlink, and the TCI state is applied to multiple channels including both the uplink and the downlink. If the largest RSRP among the RSRPs corresponding to each of the multiple activated TCI states satisfies the threshold condition, the CSI report is made. The aforementioned base station is A system having a transmission unit that transmits the aforementioned higher-layer parameters.