Terminal, radio communication method, and base station

Abstract

To improve communication quality / throughput.SOLUTION: A terminal according to an aspect of the present disclosure has: a receiving section that receives a reference signal; and a control section that, when a first event based on the reference signal occurs in a first time window, determines whether to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window. When the PUCCH resource overlaps the specific time after transmission of a specific signal, or the transmission of the specific signal overlaps the first time window, the control section cancels the transmission of the first PUCCH.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

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

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) 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 Summary of the Invention [Problem to be solved by the invention]

[0005] It is being considered that future wireless communication systems (e.g., NR, Rel. 19 and later) will support event-based beam reporting initiated by a terminal (user terminal, User Equipment (UE)) (also referred to as event-triggered beam reporting / UE-initiated Beam Report (UEIBR)).

[0006] Such beam reporting is being considered for support in MIMO / mobility from Rel. 19 onwards.

[0007] However, there are cases where such beam reporting is not sufficiently considered. If this consideration is insufficient, it may not be possible to achieve lower latency communications, which may result in suppression of improvements in communication quality / throughput.

[0008] Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can improve communication quality / throughput. [Means for solving the problem]

[0009] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives a reference signal, and a control unit that, when a first event based on the reference signal occurs within a first time window, determines whether to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window, and when the PUCCH resource overlaps with a specific period after transmission of a specific signal, or when the transmission of the specific signal overlaps with the first time window, the control unit cancels the transmission of the first PUCCH. [Effects of the Invention]

[0010] According to one aspect of the present disclosure, communication quality / throughput can be improved. [Brief explanation of the drawings]

[0011] [Figure 1] Fig. 1A is a diagram showing an example of UE movement in Rel. 17. Fig. 1B is a diagram showing an example of UE movement in Rel. 18. [Figure 2] FIG. 2 is a diagram showing an example of a time window related to option 0-2. [Figure 3] 3A to 3C are diagrams showing an example of association between an event / setting and a first UL channel according to embodiment 1-1. [Figure 4] FIG. 4 is a diagram illustrating an example of the operation of the prohibit timer according to option 1.1A. [Figure 5] FIG. 5 is a diagram showing an example of the operation of a time window according to option 1.1A. [Figure 6] FIG. 6 is a diagram showing an example of the operation of the prohibition timer according to options 1.2A / 1.3A. [Figure 7] FIG. 7 is a diagram showing an example of the operation of the time window according to option 1.2A / 1.3A. [Figure 8] 8A to 8C are diagrams illustrating an example of association between CCs and first UL channels according to embodiment 1-2. [Figure 9] 9A to 9D are diagrams showing examples of associations between events / settings, CCs, and first UL channels according to the first to third embodiments. [Figure 10] FIG. 10 shows an example of cancellation of the first PUCCH according to option 1-2 of embodiment B2. [Figure 11] FIG. 11 shows an example of a measurement window according to embodiment C1. [Figure 12] FIG. 12 shows an example of the relationship between the event evaluation period, the first PUCCH resource period, and the measurement window length according to embodiment C2-1. [Figure 13]FIG. 13 shows another example of the relationship between the event evaluation period, the first PUCCH resource period, and the measurement window length according to embodiment C2-1. [Figure 14] FIG. 14 shows an example of the relationship between the event evaluation period, the first PUCCH resource period, and the measurement window length according to embodiment C2-2. [Figure 15] FIG. 15 shows an example of the relationship between the event evaluation period, the first PUCCH resource period, and the measurement window length according to embodiments C2-3. [Figure 16] FIG. 16 shows an example of overlapping of multiple measurement windows according to embodiment C3. [Figure 17] FIG. 17 shows an example of the operation of the counter according to embodiment C4. [Figure 18] FIG. 18 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of a vehicle according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (L1 / L2 inter-cell mobility) The UE may perform UL transmission to one or more cells / TRPs. The following scenario 1 or scenario 2 may be considered as a procedure in this case. In the present disclosure, the serving cell may be replaced with the TRP in the serving cell. Layer 1 / layer 2 (L1 / L2) and DCI / Medium Access Control Control Element (MAC CE) may be replaced with each other. In the present disclosure, a physical cell identity (PCI) different from the physical cell identity (PCI) of the current serving cell may be simply referred to as a "different PCI." A non-serving cell, a cell having a different PCI, and an additional cell may be replaced with each other.

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

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

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

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

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

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

[0019] (1) The UE receives from the serving cell the SSB configuration of a cell (additional cell) with a different PCI for beam measurement / serving cell change. (2) The UE performs beam measurements of cells using different PCIs and reports the measurement results to the serving cell. (3) The UE may receive a configuration of a cell with a different PCI (serving cell configuration) through higher layer signaling (e.g., RRC). That is, a pre-configuration regarding a serving cell change may be performed. This configuration may be performed together with the configuration in (1) or separately. (4) Based on the above report, the TCI states of cells with different PCIs may be activated by L1 / L2 signaling according to the change of serving cell. The activation of the TCI states and the change of serving cell may be performed separately. (5) The UE changes the serving cell (assumed serving cell) and starts receiving / transmitting using the pre-configured UE-specific channel and TCI state.

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

[0021] Figure 1B is a diagram showing an example of the movement of a UE in Rel.18. In Rel.18, the serving cell is switched by L1 / L2 (e.g., DCI / MAC CE). The UE can receive / transmit UE-dedicated channels / common channels with the new serving cell (or the target serving cell). The UE may go out of the coverage of the current serving cell (e.g., Current serving cell).

[0022] (Type of beam report) <Intra-cell beam report in Rel.15 / 16> In Rel.15 / 16, intra-cell beam reporting is supported. For example, the L1-RSRP / SINR report can be set by higher layer signaling (RRC).

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

[0024] Also, the UE can be set with up to 16 CSI-RS resource sets each having up to 64 resources within each set. In all resource sets, the total number of different CSI-RS resources is 128 or less.

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

[0026] Here, the maximum measured value of L1-RSRP is quantized to a 7-bit value in the range of [-140~-44]dBm with a step size of 1dB. Also, the differential value of L1-RSRP is quantized to a 4-bit value.

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

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

[0029] For channel measurement, the UE may be configured with CSI resource settings for a maximum of 64 CSI resources or a maximum of 16 CSI-RS resource sets with SS / PBCH block resources.

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

[0031] When the upper layer parameter nrofReportedRS is set greater than 1, or when the upper layer parameter groupBasedBeamReporting is set to "enabled", the UE uses the difference value-based L1-SINR value for reporting.

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

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

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

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

[0036] The setting by upper layer signaling supports up to seven additional cells. Note that ID = 0 means the PCI of the serving cell.

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

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

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

[0040] Regarding beam selection in SSB-based L1-RSRP reporting, the maximum value of M*L configurable by RRC for the above-mentioned M and L, and the combination of M and L may vary depending on the UE capabilities.

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

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

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

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

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

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

[0047] The additional PCIs to be configured are re-indexed by IDs. The RRC IE configures up to seven additional PCIs. The value 0 of the ID corresponding to the PCI means the serving cell.

[0048] M×L beams are reported in a single reporting instance: the UE reports M beams for each of the L cells from the configured plurality of cells.

[0049] (Event-triggered Beam Report / UE-initiated Beam Report (UEIBR)) It is being considered that future wireless communication systems (e.g., Rel. 19 and later) will support event-based beam reporting, which may also be called event-triggered beam reporting or UE-initiated beam reporting (UEIBR).

[0050] UEIBR / UE Initiated Beam Management (UEIBM) can be used for measurement reporting / beam switching / cell switching etc.

[0051] <Applicable cases> The UEIBR may be applied, for example, in at least one of the following cases 1 and 2: · Case 1: L1-RSRP / SINR beam report including serving cell PCI / additional PCI (e.g., L1-RSRP / SINR beam report including serving cell / additional PCI cell for Rel.18 L1 / L2 mobility with inter-cell mobility / intra-cell multi-TRP (M-TRP inter-cell) / cell switching within the L1 / L2 cell). · Case 2: L1-RSRP / SINR beam report including only serving cell PCI.

[0052] When a specific event occurs (in this disclosure, it may be read as, for example, a specific condition is satisfied / not satisfied, corresponding to a specific event, etc.), the UE may report measurement results (e.g., at least L1-RSRP / L1-SINR and corresponding resource indicator / RS index) to the NW.

[0053] The specific event may be, for example, at least one of an event related to at least one of the serving cell and the additional cell, and an event related to a beam report including at least one of the PCI of the serving cell and the PCI of the additional cell.

[0054] <Trigger conditions / events for UEIBR for Rel.19> UEIBR may be triggered when a certain condition (event) is satisfied. For example, the UE may apply different / same conditions / events for the triggering of the following beam reports.

[0055] · UE feature #1: UEIBR for Rel.19 MIMO. · UE feature #2: UEIBR for Rel.19 mobility.

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

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

[0058] The UE may set UE features #1 and #2 simultaneously in a certain BWP / CC / band / frequency band / frequency (or for each UE). For example, if set, the UE may pre-define which event (which UE feature) to prioritize, and it may be set / instructed by upper layer signaling / physical layer signaling.

[0059] This disclosure may be applied in the unified TCI framework.

[0060] This disclosure may be applied only when the corresponding UE capabilities are reported. Alternatively, this disclosure may be applied only when the corresponding upper layer parameters (e.g., RRC) are notified / reported.

[0061] <UE IBR for MIMO> Regarding the UE IBR for MIMO in Rel.19, the following may apply.

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

[0063] The content of the report may basically be the same as the existing L1 beam measurement report, and may include, for example, at least one of the following. · SSBRI / CRI. · The number of beams X reported. · The selection method of X beams. L1-RSRP / SINR (absolute value / differential value) for each SSBRI / CRI. If MAC CE is used, An indicator of whether the next octet is included. If MAC CE / UCI is used, Serving cell ID, BWP ID (if the report requires activation of TCI state or beam switching).

[0064] Events related to UEIBR for MIMO may be broadly categorized into the following event types: Event 1: The quality of the current beam becomes worse than a certain threshold. Event 2: The quality of at least one new beam (e.g., L1-RSRP) becomes better than a certain threshold compared to the quality of the current beam. Event 3: The quality of the new beam is better than a certain threshold. Event 4: The quality of the current beam becomes worse than a first threshold and the quality of at least one new beam becomes better than a second threshold. Event 5: The absolute value of the difference between the quality of the current beam and the quality of at least one new beam falls below a certain threshold. Event 6: The current beam is no longer among the best K (more than 1: K>1) beams (among the beams configured for measurement / reporting). Event 7: The quality of at least one new beam (e.g. L1-RSRP) becomes better than the quality of the Qth (Q may be M, Q or M may be greater than or equal to 1, Q or M may be configured by RRC (based on UE capability reporting)) RS derived from the activated (active) TCI state by more than a threshold. Event 8: The quality (e.g., L1-RSRP) of M (more than 1: M>1) new beams becomes better than the current beam by more than a threshold. Event 9: The quality of at least one new beam (e.g. L1-RSRP) becomes better than the configured reference RS (which may be SSB / CSI-RS) by more than a threshold.

[0065] It should be noted that the events exemplified in this manner do not exclude other events.

[0066] Priorities may be defined for events 1 to 9. For example, among events 1 to 9, a specific event (e.g., event 2) may have the highest priority (e.g., event 2 may be determined to take precedence).

[0067] For example, in event 2, the current beam may be determined / derived based on the QCL RS (e.g., QCL source RS) in the indicated TCI state.

[0068] For example, for the current beam in event 2, at least one of the following beam options 2a to 2c may be supported: Beam Option 2a: The RS corresponding to the current beam is implicitly derived / determined based on the QCL RS of the indicated TCI state. Beam Option 2b: The RS corresponding to the current beam is the QCL RS in the indicated TCI state and the QCL SSB. · Beam Option 2c: The RS corresponding to the current beam is [explicitly] configured / indicated using RRC signaling / MAC CE.

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

[0070] For example, for the reference signal measurement (RS measurement) of the current beam for Event 2 (and Beam Option 2a), several schemes may be supported: Scheme 1: The RS of the current beam is the QCL RS in the indicated TCI state. Scheme 2: The RS of the current beam is the QCL RS in the indicated TCI state and the QCLed SSB.

[0071] If there are two QCL RSs in the indicated TCI state, the QCL RSs may be QCL type D.

[0072] At least one of CSI-RS and SSB may be supported as the QCL RS configured / applied to the indicated TCI state. When CSI-RS is configured / applied as the QCL RS, at least one of a tracking CSI-RS (TRS) and a measurement CSI-RS may be supported. The measurement CSI-RS may be the CSI-RS used for L1-RSRP / L1-SINR or the CSI-RS used for beam management (BM).

[0073] In scheme 1, only a TRS (for example, one tracking CSI-RS) may be configured as a QCL-RS (for example, type A / D) in the indication TCI state.

[0074] When only a TRS is set as the QCL-RS for the indicated TCI state, a reference signal different from the TRS (e.g., an RS corresponding to the TRS) may be selected for measuring / reporting the RS of the current beam.

[0075] For RS measurements on the current beam in Event 2 / Option 2a, [in addition to Schemes 1 and 2], when only one TRS is set to the indicated TCI state, at least one of the following processing options 1 to 4 may be applied:

[0076] Processing option 1: An additional scheme is introduced. The RS for the current beam can be the CSI-RS for beam management derived from the QCL RS in the indicated TCI state. Processing Option 2: TRS is additionally supported as the measured RS of the current beam to determine the L1-RSRP. Processing option 3: An additional scheme is introduced: the RS for the current beam is explicitly configured / indicated by the RRC or MAC CE. Processing option 4: No further expansion is performed.

[0077] The explicit RS configuration for measurement of the new beam in event 2 may be configured in one RS resource set associated with the CSI reporting configuration.

[0078] In this case, if the existing UE capability cannot be reused, a UE capability indicating the maximum number of RSs configured in the RS resource set may be defined / introduced.

[0079] The RSs in the one RS resource set may be updated by the MAC CE.

[0080] The UE IBR for MIMO may be transmitted using UCI.

[0081] In a UCI-based UEIBR procedure, the following modes may be supported:

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

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

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

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

[0086] For mode A, at least a one-bit indication in the first UL channel (PUCCH) may be supported to request resources in the second UL channel for transmitting a beam report.

[0087] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

[0088] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit indication (for setting the one-bit indication) may be defined, and the RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0089] Also, an RRC parameter for periodic PUCCH resource configuration (e.g., firstPUCCHResourceConfig-ModeA-UEIBR) corresponding to the one-bit indication may be defined. The RRC parameter may not be associated with an SR ID (e.g., SchedulingRequestId).

[0090] The RRC parameters may include, for example, a periodicity and offset setting parameter (periodicityAndOffset) and a PUCCH resource ID (for example, PUCCH-ResourceID).

[0091] These RRC parameter specifications may be applied to the case where at least one CC (single CC) is used.

[0092] The DCI format in step 2 may be, for example, an UL grant DCI (for example, DCI format 0_1 / 0_2 / 0_3), and the second UL channel in step 3 may utilize at least a PUSCH.

[0093] Furthermore, the DCI format in step 2 may be, for example, DL grant DCI (for example, DCI format 1_1 / 1_2), and the second UL channel in step 3 may be PUCCH.

[0094] A 1-bit field may be newly defined in the DL grant DCI to instruct transmission of the UEIBR.

[0095] The PUCCH resources intended for HARQ-ACK transmission may be (re)used to transmit both HARQ-ACK and UEIBR.

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

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

[0098] Step 2: The UE transmits a beam report in the second UL channel (eg, using a specific resource (UCI) within the channel).

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

[0100] For Mode B, at least a one-bit indication in the first UL channel (PUCCH) may be supported to indicate that the second UL channel is used to transmit a beam report.

[0101] In this case, periodic PUCCH resources (PUCCH format 0 / 1) may be configured by dedicated higher layer signaling.

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

[0103] An RRC parameter (e.g., reportResourceRequest-UEIBR) corresponding to the one-bit indication (for setting the one-bit indication) may be defined, and the RRC parameter may be identified using a specific ID (e.g., a dedicated SchedulingRequestId).

[0104] Also, an RRC parameter for periodic PUCCH resource configuration (e.g., firstPUCCHResourceConfig-ModeB-UEIBR) corresponding to the one-bit indication may be defined. The RRC parameter may not be associated with an SR ID (e.g., SchedulingRequestId).

[0105] The RRC parameters may include, for example, a periodicity and offset setting parameter (periodicityAndOffset) and a PUCCH resource ID (for example, PUCCH-ResourceID).

[0106] These RRC parameter specifications may be applied to the case where at least one CC (single CC) is used.

[0107] The second UL channel in step 2 may be, for example, a Type 1 Configured Grant (CG) PUSCH or a PUCCH.

[0108] <UEIBR for mobility> With respect to UEIBR for Rel. 19 mobility (e.g., LTM), the following may apply:

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

[0110] The contents of the report may include, for example, at least one of the following: If the measurement report is used for cell switching reporting, in addition to MIMO related information: -Indicator of cell switching or TA related information. Otherwise (measurement reports are not used for cell switch reporting), · The same content as MIMO-related information (only difference is whether it is intra-cell or inter-cell).

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

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

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

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

[0115] In the case of L1 measurements by UEIBR, at least the results of beam level measurements may be used for event evaluation.

[0116] Events related to UEIBR for Mobility may be broadly categorized into the following event types: Event LTM2: The beam quality of the serving cell becomes worse than the (absolute) threshold. · Event LTM3: The beam quality of the candidate cell becomes better than the beam quality of the serving cell by more than a certain offset amount. · Event LTM4: The beam quality of the candidate cell becomes worse than the (absolute) threshold. Event LTM5: The beam quality of the serving cell becomes worse than a first (absolute) threshold and the beam quality of the candidate cell becomes better than a second (absolute) threshold.

[0117] Note that the events exemplified in this way do not exclude other events. Also, the above-mentioned MIMO events may be appropriately used (in this case, the "current beam" may be read as the "beam of the serving cell," and the "new beam" may be read as the "beam of the candidate cell," respectively). The events that are used / replaced may be called mobility / LTM events corresponding to the MIMO events.

[0118] In the L1 measurement resource configuration in the LTM configuration, both SSB and CSI-RS beam configurations may be supported.

[0119] In events LTM3 and LTM5, the same type of RS (eg, CSI-RS / SSB) may be used in both the serving cell and the candidate cell (neighbor cell).

[0120] Mobility event evaluation may apply at least one of the following: time to trigger (TimeToTrigger (TTT)), hysteresis for entering / leaving, and beam-specific / cell-specific offsets.

[0121] A mobility-oriented UE IBR may be transmitted using the MAC CE.

[0122] <Definition of terms for specific events> In the above-mentioned existing events, the definitions of serving (cell) and neighbor (cell) may be rephrased / updated as follows in the UEIBR for Rel.19:

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

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

[0125] Neighbors [cells] in existing L3 events may be interchangeably referred to as other beams (e.g., RS IDs that are not associated with the indicated [joint / DL] TCI state but are associated with the RS ID for L1 beam measurements) in event-triggered beam reporting for Rel.19 MIMO (which may be mobility).

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

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

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

[0129] <Multi-CC / Cross-CC Case UEIBR> A UE IBR that uses multiple CCs may be configured for the UE.

[0130] Also, UEIBR may be set for multiple CCs.

[0131] A UEIBR that utilizes multiple CCs may be referred to as a multi-CC case UEIBR.

[0132] The multi-CC case may include a cross-CC case.

[0133] With regard to cross-CC operations in UEIBR, the CC on which the event occurs / is satisfied may be, for example, the CC on which the reporting configuration including the triggered event is set.

[0134] The reporting configuration may be, for example, an existing (defined up to Rel. 18) reporting configuration (to be extended).

[0135] For example, the reporting configuration may be a CSI reporting configuration for LTM (e.g., LTM-CSI-ReportConfig-r18) [specified in Rel. 18].

[0136] The CSI reporting configuration for the LTM may be applied / used, for example, in a specific scenario (e.g., mobility / LTM case).

[0137] Also, for example, the reporting configuration may be a CSI reporting configuration (e.g., CSI-ReportConfig) [specified in Rel. 15].

[0138] The CSI reporting configuration may be applied / used in a specific scenario (eg, MIMO case), for example.

[0139] Also, for example, the reporting configuration may be a CSI reporting configuration for UEIBR (e.g., UEIBR-CSI-ReportConfig-r19) [newly defined in Rel. 19 and later].

[0140] The CSI reporting configuration may be applied / used in a specific scenario (eg, mobility / LMT / MIMO case), for example.

[0141] The CC to which the reporting configuration including the triggered event is set and the CC to which the RS set as the measurement target in the triggered event belongs (corresponding) may be the same.

[0142] Furthermore, a CC to which a reporting configuration including a triggered event is configured and a CC to which an RS configured as a measurement target for the triggered event belongs (corresponding) may be determined separately. For example, a CC to which a reporting configuration including a triggered event is configured and a CC to which an RS configured as a measurement target for the triggered event belongs (corresponding) may be different.

[0143] Furthermore, with regard to cross-CC operation in the UEIBR, the CC in which an event occurs / is satisfied may be, for example, the CC to which (corresponding to) the RS set as a measurement target in the triggered event belongs.

[0144] Also, with regard to cross-CC operation in the UEIBR, the CC on which the event occurs / is satisfied may be, for example, a CC configured / instructed by higher layer signaling (RRC signaling / MAC CE).

[0145] The primary / secondary UL channel may include the CC / cell ID of the CC where the event occurs / is satisfied.

[0146] Hereinafter, among the multiple CCs, CC#1 may correspond to a special cell (SpCell, for example, PCell / PSCell) / PUCCH SCell, and CC#2 to #N may correspond to SCells.

[0147] For each CC of the multiple CCs, one or more separate (different) reporting settings may be configured.

[0148] Cross-CC operation in UEIBR may mean operation when at least two of the following are different: the CC to which the reporting configuration is set, the (corresponding) CC to which the RS set as the measurement target in the reporting configuration belongs, the CC to which the first UL channel is transmitted, and the CC to which the second UL channel is transmitted.

[0149] For example, cross-CC operations in the UEIBR may include at least one of the following: Action 1: A report is triggered in CC#1 due to the reporting setting (measurement in CC#1), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in CC#1. Action 2: A report is triggered in CC#1 according to the reporting setting (measurement in CC#1), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in at least one of CC#2 to #N. Action 3: A report is triggered in CC#1 according to the reporting setting (measurement in CC#1), the first UL channel is transmitted in at least one of CC#2 to #N, and the second UL channel is transmitted in CC#1. Action 4: A report is triggered in CC#1 based on the reporting setting (measurement in CC#1), a first UL channel is transmitted in at least one of CC#2 to #N, and a second UL channel is transmitted in at least one of CC#2 to #N. Action 5: A report is triggered in CC#1 with a reporting configuration (measurement in at least one of CC#2 to #N), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in CC#1. Action 6: A report is triggered in CC#1 based on the reporting configuration (measurement in at least one of CC#2 to #N), a first UL channel is transmitted in CC#1, and a second UL channel is transmitted in at least one of CC#2 to #N. Action 7: A report is triggered in CC#1 based on the reporting configuration (measurement in at least one of CC#2 to #N), the first UL channel is transmitted in at least one of CC#2 to #N, and the second UL channel is transmitted in CC#1. Action 8: A report is triggered in CC#1 based on the reporting configuration (measurement in at least one of CC#2 to #N), a first UL channel is transmitted in at least one of CC#2 to #N, and a second UL channel is transmitted in at least one of CC#2 to #N. Action 9: A report is triggered in at least one of CC#2 to #N according to the reporting configuration (measurement in CC#1), the first UL channel is transmitted in CC#1, and the second UL channel is transmitted in CC#1. Action 10: A report is triggered in at least one of CCs #2 to #N according to the reporting configuration (measurement in CC #1), a first UL channel is transmitted in CC #1, and a second UL channel is transmitted in at least one of CCs #2 to #N. Action 11: A report is triggered in at least one of CCs #2 to #N according to the reporting setting (measurement in CC #1), a first UL channel is transmitted in at least one of CCs #2 to #N, and a second UL channel is transmitted in CC #1. Action 12: A report is triggered in at least one of CCs #2 to #N according to the reporting setting (measurement in CC #1), a first UL channel is transmitted in at least one of CCs #2 to #N, and a second UL channel is transmitted in at least one of CCs #2 to #N. Action 13: A report is triggered in at least one of CCs #2 to #N according to the reporting configuration (measurement in at least one of CCs #2 to #N), a first UL channel is transmitted in CC #1, and a second UL channel is transmitted in CC #1. Action 14: A report is triggered in at least one of CCs #2 to #N according to the reporting configuration (measurement in at least one of CCs #2 to #N), a first UL channel is transmitted in CC #1, and a second UL channel is transmitted in at least one of CCs #2 to #N. Action 15: A report is triggered in at least one of CCs #2 to #N according to the reporting configuration (measurement in at least one of CCs #2 to #N), a first UL channel is transmitted in at least one of CCs #2 to #N, and a second UL channel is transmitted in CC #1. Action 16: A report is triggered in at least one of CCs #2 to #N according to the reporting configuration (measurement in at least one of CCs #2 to #N), a first UL channel is transmitted in at least one of CCs #2 to #N, and a second UL channel is transmitted in at least one of CCs #2 to #N.

[0150] Cross-CC operation in UEIBR may mean, for example, a case where the CC to which the reporting configuration is configured and the CC to which the RS configured as the measurement target in the reporting configuration belongs (corresponds to) are different.

[0151] For example, the cross-CC operations in the UEIBR may be operations 5 / 6 / 9 / 10. For example, the cross-CC operations in the UEIBR may be limited to operations 5 / 6 / 9 / 10.

[0152] Also, for example, cross-CC operations in the UEIBR may include operations other than operations 5 / 6 / 9 / 10.

[0153] In the present disclosure, a case in which a second UL channel is transmitted in a CC of a serving cell for which a reporting configuration (eg, a CSI reporting configuration) is configured may be referred to as cross-CC case A.

[0154] In the present disclosure, a case in which a second UL channel is transmitted in a CC corresponding to a measurement target (RS) configured in a reporting configuration (e.g., a CSI reporting configuration) may be referred to as cross-CC case B.

[0155] Which of cross-CC cases A and B to apply may be predefined in the specifications, may be configured using higher layer signaling (RRC signaling / MAC CE), may be determined based on a report of UE capabilities, or may be determined based on a combination of at least two of these.

[0156] <Considerations regarding event-triggered beam reporting> In Rel.19 MIMO and mobility, UEIBR L1 beam reporting is considered. In Rel.19 mobility, conditional LTM (CLTM) is considered. UEIBR reporting may be used for at least one of measurement reporting, beam switching, and cell switching.

[0157] A common framework or different frameworks may be supported between Rel.19 MIMO and Rel.19 mobility. Event-triggered beam reporting for Rel.19 MIMO may support L1 beam reporting types 1 and 2-1, and event-triggered beam reporting for Rel.19 mobility may support L1 beam reporting type 2-2.

[0158] In Rel.19 MIMO, extensions are being considered to facilitate UE-initiated / event-driven beam management for overhead and / or latency reduction, assuming a unified TCI, leveraging the traditional CSI measurement and reporting configuration framework [where possible], and targeting FR2 and sTRP with intra-cell and inter-cell beam management. The extensions include: ◆a.UL signaling content [and procedures, if necessary] for UE-initiated / event-driven beam reporting to facilitate fast beam switching. ◆b. A medium / container for UL signaling designed primarily for beam reporting purposes and taking into account the UE-initiated / event-driven nature of UL transmissions.

[0159] Measurement-related extensions are being considered to support LTM. Measurement-related extensions are applicable to LTM for MCG / SCG within a CU. Components required to support event-triggered L1 measurement reporting are being considered.

[0160] To support conditional LTM, the following has been considered: ◆ The conditions evaluated by the UE to trigger LTM. ◆Aiming to support conditional LTM, including subsequent LTM. ◆ Prioritize LTM within the CU.

[0161] (Intra-cell beam report) L1-RSRP reporting or L1-SINR reporting can be configured by RRC.

[0162] If the UE is configured with SSB-MTC-AdditionalPCI, the CSI-SSB-ResourceSet configured for L1-RSRP reporting includes one or more sets of SSB indices, and multiple PCI indices are associated with multiple sets of SSB indices, respectively.

[0163] ServingCellConfig can include MIMOParam-r17. MIMOParam-r17 can include a list of one or more SSB-MTC-AdditionalPCI-r17 (additionalPCI-ToAddModList-r17). SSB-MTC-AdditionalPCI-r17 can include additionalPCIIndex-r17 and additionalPCI-r17(PhysCellId). additionalPCI is the PCI of the additional SSB, which is different from the serving cell PCI.

[0164] The CSI-SSB-ResourceSet can include a list of one or more SSB-Indexes (csi-SSB-ResourceList) and a list of ServingAdditionalPCIIndex-r17s (servingAdditionalPCIList-r17).

[0165] (Analysis A) Due to the triggering of the UEIBR, the event instances are evaluated / determined / counted.

[0166] For example, among the above events, it is being considered that for event 2, the event instance will be counted for each new beam.

[0167] In addition, the evaluation period for the event instance of Event 2 above is being considered.

[0168] For example, the period of the RS of the current beam may be the same as the period of the RS of the new beam.

[0169] In this case, the evaluation period of the event instance may be the same as the period of the RS of the current beam and the RS of the new beam.

[0170] Also, for example, the period of the RS of the current beam and the period of the RS of the new beam may be different (this may be supported).

[0171] In this case, the evaluation period of the event instance may be at least one of the following periods 1 to 5: The evaluation period of the event instance is the same as the RS period of the current beam. The evaluation period of the event instance is the same as the period of the RS of the new beam. The evaluation period of the event instance is the same as the shortest period of the RS of the current beam and the RS of the new beam. The evaluation period of the event instance is the larger (maximum value) of the shortest period among the periods of the RS of the current beam and the RS of the new beam, and X ms. The evaluation period of the event instance is the same as the largest period of the RS of the current beam and the RS of the new beam.

[0172] The RS period (or evaluation period) for multiple new beams may be the same.

[0173] Also, the introduction of a new UCI type (for example, a UCI type other than the UCI types defined up to Rel. 18) for the first UL channel in Mode A / Mode B is under consideration.

[0174] In particular, the introduction of a prohibition timer and / or a maximum number of transmissions / retransmissions for the first UL channel related to the new UCI type is being considered. While the prohibition timer is running, transmission of the first UL channel is not performed even if the event condition is met. By introducing the prohibition timer and / or a maximum number of transmissions / retransmissions, it is possible to reduce transmission waiting time / delay by suppressing frequent retransmissions.

[0175] However, the details of this implementation have not been thoroughly considered, which could result in increased transmission latency / delay due to the first UL channel (Issue 1).

[0176] (Analysis B) Regarding the determination of the triggering event for Event 2, several options are considered for the measurement window to start the UE-initiated / event-driven beam reporting procedure: ◆ Option 1: The measurement window is from T_PUCCH-T_proc-T_window to T_PUCCH-T_proc. T_PUCCH is the first PUCCH transmission occasion. T_proc is configured by RRC. ◆ Option 2: The measurement window is from T_Instance-T_window to T_Instance. T_Instance is configured by RRC. T_Instance is the evaluation occasion of the event instance. The UBER in the second PUSCH is based on the most recent measurements for the RS of the new / current beam. ◆ Option 3: The length, slot offset and period of the measurement window are configured by the NW for each CSI reporting configuration. ◆ Option 4: If an Event 2 instance for a new beam is obtained at time t, the UE starts (restarts) a timer for the new beam, the expiration time of which is equal to the length set by the NW of the time window (T_window).

[0177] T_window is the time window parameter for the measurement. Other options are not excluded. Option 4 is a BFR-like implementation, where multiple windows for a given new beam do not overlap in the time domain.

[0178] In this way, the time window for event evaluation (measurement window for initiating UE-initiated / event-driven beam reporting procedure) has been considered. However, the specific operation of transmitting the first PUCCH has not been sufficiently considered. If such consideration is insufficient, it may lead to a suppression of improvement in communication quality / throughput.

[0179] Therefore, the present inventors came up with a method for solving these problems.

[0180] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0181] (Various reading changes) In this disclosure, words enclosed in "()" in a sentence may indicate an explanation of the immediately preceding wording (for example, an explanation of spelling), a paraphrase, a specific example, a supplementary explanation, etc. Also, in this disclosure, words enclosed in "[ ]" in a sentence may be interpreted including the meaning of the entire sentence, or may be interpreted excluding the meaning of the entire sentence (ignoring the meaning of the entire sentence). Note that "()" and "[ ]" may also be used for purposes / meanings other than those mentioned above.

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

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

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

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

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

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

[0188] In this disclosure, A b , A_b, Ab, and A with b added to the bottom right may be read interchangeably. c , A^c, and the notation of A with c added to the upper right may be read interchangeably. b c , A_b^c, and the notation in which b is added to the bottom right of A and c is added to the top right of A may be read interchangeably. ~ may be expressed by adding 〜 to the x, or may be referred to as x tilde. - may be represented by placing a - on top of the x, or may be referred to as an x-bar. ^ may be represented by placing a ^ above the x, or may be called an x-hat.

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

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

[0191] In the present disclosure, base station, gNB, and network (NW) may be interpreted as interchangeable.

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

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

[0194] In the present disclosure, transmission and reception may be read interchangeably.

[0195] In this disclosure, terms such as table, mapping, association, list, format, content, report, etc. may be read interchangeably.

[0196] In the present disclosure, MAC CE, UCI, cell switch command, beam switch command, beam report MAC CE, and cell switch MAC CE may be read interchangeably.

[0197] In the present disclosure, the UEIBR may be reported on a PUSCH (e.g., a CG PUSCH / DG PUSCH). That is, the report content in the present disclosure may be transmitted using at least one of a MAC CE / UCI / PUCCH / PUSCH.

[0198] In the present disclosure, serving may be interchangeably read as serving beam / serving cell / SpCell.

[0199] In the present disclosure, neighbor may be interchangeably read as a beam / cell other than the serving beam / serving cell / SpCell / SCell.

[0200] In the present disclosure, candidate cells, target cells, neighboring cells, cells, etc. may be read interchangeably.

[0201] In the present disclosure, beam, RS, RS index (CRI / SSBRI), and [L1 / L3] measurement results may be interpreted interchangeably.

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

[0203] In the present disclosure, [for Rel. 19] event-based beam reporting, event-triggered beam reporting, UE-triggered beam reporting, UE-initiated beam reporting (UEIBR), UE-initiated beam management (UEIBM), beam reporting, etc. may be read interchangeably.

[0204] In the present disclosure, the terms indicated TCI state, active TCI state, activated TCI state, configured TCI state, and RS configured in RRC may be read interchangeably.

[0205] Each embodiment of the present disclosure can be applied to any event.

[0206] In the present disclosure, the terms rule, case, factor, condition, threshold, etc. may be read interchangeably.

[0207] In this disclosure, the CSI / UCI for the UEIBR may be referred to as UEIBR-CSI / UCI. In this disclosure, [other] UCI (or simply "UCI") may mean UCI other than the CSI / UCI for the UEIBR.

[0208] In the present disclosure, beam report, CSI report, UEIBR, CSI related to UEIBR, UEIBR-CSI, UEIBR-UCI, report, etc. may be read interchangeably.

[0209] In the present disclosure, Mode A and Mode B may be interpreted as interchangeable.

[0210] In the present disclosure, multiplexing (multiplexing / being multiplexed) and mapping (mapping / being mapped) may be read interchangeably.

[0211] In the present disclosure, the UL channel that transmits UEIBR-CSI, CG PUSCH, Type 1 CG PUSCH, Type 2 CG PUSCH, DG PUSCH, and PUSCH may be interchangeable.

[0212] In the present disclosure, other UL channels (carrying other UCI), PUCCH, and PUSCH may be read as interchangeable.

[0213] In the present disclosure, terms such as switch, activate, deactivate, instruct, change, update, etc. relating to the TCI state may be read interchangeably.

[0214] In the present disclosure, beam instruction (DCI / MAC CE), TCI state instruction (DCI / MAC CE), TCI state switching command (DCI / MAC CE), cell switch command (DCI / MAC CE), DCI, MAC CE, etc. may be read as interchangeable.

[0215] In the present disclosure, report content, content, field, ID, measurement result, and report amount may be read interchangeably.

[0216] In the present disclosure, beam report, report, MAC CE, beam report MAC CE, UCI, and PUSCH may be read interchangeably.

[0217] In the present disclosure, beam, beam ID, beam identifier, RS index, SSBRI, and CRI may be read interchangeably.

[0218] In the present disclosure, the current beam, the beam / RS corresponding to the current active TCI state, the beam / RS corresponding to the active TCI state, the beam / RS derived from the [current] active TCI state, etc. may be read interchangeably.

[0219] In the present disclosure, beam and beam ID, RS and RS ID, TCI state and TCI state ID may be read interchangeably.

[0220] In the present disclosure, the terms counter, timer, measurement window, time window, evaluation window, backward sliding window, sliding window, and window may be read interchangeably.

[0221] In the present disclosure, the first UL channel and the first UL channel resource may be interpreted as interchangeable.

[0222] In the present disclosure, the first UL channel resource may refer to a resource for the first UL channel that is configured / allocated regardless of whether the first UL channel is actually transmitted or not.

[0223] In the present disclosure, Mode A may be read as the first mode in which DCI is transmitted to schedule / trigger a UEIBR / beam report (second UL channel).

[0224] In the present disclosure, Mode B may be read as a second mode in which DCI that schedules / triggers UEIBR / beam report (second UL channel) is not transmitted.

[0225] In the present disclosure, the first UL channel and the first PUCCH may be interchangeable. In the present disclosure, the second UL channel and the second PUSCH may be interchangeable. In the present disclosure, the second PUSCH of Mode A and the dynamic grant (DG)-PUSCH may be interchangeable. In the present disclosure, the second PUSCH of Mode B and the configured grant (CG)-PUSCH may be interchangeable.

[0226] (Wireless communication method) The UE may apply each embodiment of the present disclosure when performing beam measurement / reporting (e.g., UE IBR). The NW / BS / gNB may provide / send to the UE settings / instructions, etc., for the UE to perform the operations / controls described in each embodiment of the present disclosure. Furthermore, the NW / BS / gNB may perform various operations / controls required to receive an event-triggered beam report / UE IBR from the UE.

[0227] One or more embodiments / options are applicable to MIMO / mobility use cases, which may be any use case such as LTM, conditional LTM (CLTM), conditional handover (CHO), etc.

[0228] One or more of the embodiments / options may be applied alone or in combination.

[0229] One or more embodiments / options may be applied in at least one of Case 1 and Case 2 above.

[0230] One or more embodiments / options may be applied in at least one of Mode A and Mode B described above.

[0231] In the present disclosure, the terms "specific period," "prohibition," "timer [operation period / operation]," "measurement window," and "time window" may be read interchangeably.

[0232] In the present disclosure, the terms [first / second] time window, [first / second] period, measurement window, and dedicated window may be read interchangeably.

[0233] In the present disclosure, [event] evaluation occasion and resource / opportunity for transmission / measurement of new / current RS may be read interchangeably.

[0234] In the present disclosure, occurrence of an event, satisfaction of a trigger condition, satisfaction of an event [instance] condition, occurrence of M event instances within a measurement window, and a counter [for the measurement window] reaching M may be interpreted as interchangeable. In the present disclosure, event [instance] evaluation, determination of an event instance [condition] at an [event] evaluation opportunity, and determination of the measurement results of a new / current beam [RS] may be interpreted as interchangeable. In the present disclosure, occurrence / occurrence of an event instance, and satisfaction of an event [instance] condition at an [event] evaluation opportunity may be interpreted as interchangeable.

[0235] The UE may receive a CSI reporting configuration (e.g., CSI-ReportConfig), which may indicate or be associated with at least one of the following: RS of the new / current beam, ID, periodicity, and timing of the first PUCCH resource, evaluation occasion, Mode A or B, and event type that triggers the report. Mode A or B may be associated with the configuration of the first PUCCH resource.

[0236] <Embodiment A0> This embodiment relates to the inhibit timer for the first UL channel.

[0237] The UE may determine whether to transmit the first UL channel based on an inhibit timer / time window associated with the first UL channel.

[0238] <<Choices 0-1>> The UE may be configured with an inhibit timer for the first UL channel.

[0239] The inhibit timer may be an inhibit timer specific to the first UL channel of the UEIBR.

[0240] The prohibition timer may be set, for example, using a specific RRC parameter (eg, 1stPUCCH-ProhibitTimer).

[0241] The value of the prohibit timer may be set separately (may be a different value) from the value of other prohibit timers (for example, the prohibit timer for SR (sr-ProhibitTimer)).

[0242] The value of the prohibit timer may be set in common with the value of other prohibit timers (for example, the prohibit timer for SR (sr-ProhibitTimer)).

[0243] For example, the UE may apply the value of another prohibit timer (eg, the prohibit timer for SR (sr-ProhibitTimer)) to the prohibit timer for the first UL channel of the UE IBR.

[0244] The start timing of the inhibit timer may be a specific timing based on the primary / secondary UL channel associated with the inhibit timer.

[0245] The particular timing may be, for example, at least one of the following: · First symbol after the end of the first UL channel. · First symbol after the end of the second UL channel.

[0246] A common prohibition timer start timing may be applied to Mode A and Mode B.

[0247] Different start timings of the prohibition timers may be applied to Mode A and Mode B. In other words, different start timings of the prohibition timers may be set / applied to Mode A and Mode B.

[0248] For example, in Mode A, the prohibit timer may start at the first symbol after the end of the second UL channel.

[0249] For example, in Mode B, the inhibit timer may start at the first symbol after the end of the first UL channel.

[0250] <<Choices 0-2>> An inhibit timer for the first UL channel may be [implicitly] defined / set.

[0251] For example, the prohibit timer may be determined based on a specific time window (which may simply be referred to as a time window).

[0252] The time window for the first UL channel may be configured for the UE.

[0253] The time window may be used, for example, for at least one of the following purposes: · Event evaluation period corresponding to the 1st UL channel [resource]. - 1st UL channel [transmission] prohibition period for other 1st UL channels.

[0254] When the time window is used as a first UL channel [transmission] prohibition period for other first UL channels, and the first UL channel A is arranged in that order in time, and the first UL channel A is transmitted within the time window corresponding to the first UL channel B, the first UL channel B does not have to be transmitted.

[0255] FIG. 2 is a diagram showing an example of a time window for options 0-2. In the example shown in FIG. 2, the length of the time window is T window In the example shown in FIG. window The time window corresponding to PUCCH A (resource) is from time t to time t, and the time window corresponding to PUCCH A (resource) is from time t' to time t window The time window corresponding to PUCCH B (resource) is from time t to time t'. The processing time (T proc ) after which each PUCCH resource starts.

[0256] When the time window is used as a first UL channel [transmission] prohibition period for other first UL channels, in the example shown in FIG. 2, the time from t' to T window When PUCCH A is transmitted within a time window from time t to time t', the transmission of PUCCH B corresponding to that time window is prohibited (PUCCH B is not transmitted).

[0257] In the present disclosure, the prohibition timer and the time window may be interpreted as interchangeable, and option 0-1 or option 0-2 may be applied as appropriate.

[0258] In this option, the first UL channel and the second UL channel may be interpreted as interchangeable. For example, in this option, "the first UL channel is transmitted within a time window" may be interpreted as "the second UL channel is transmitted within a time window."

[0259] For example, in the case of Mode A, the prohibition criteria for the first UL channel may be "when the second (or first) UL channel is transmitted within the time window."

[0260] For example, in the case of Mode B, the prohibition criteria for the first UL channel may be "when the first (or second) UL channel is transmitted within the time window."

[0261] According to this embodiment, it is possible to appropriately define a prohibition timer / time window that can suppress frequent retransmissions and reduce transmission waiting time / delay.

[0262] <Embodiment A1> This embodiment relates to an example of operation related to the prohibit timer / time window.

[0263] For the [new] UCI (e.g., UEIBR-UCI / CSI) for the first UL channel, the inhibit timer / time window may be associated with at least one of the following: One primary UL channel resource. Multiple 1st UL channel resources. · One or more event settings. One or more CSI reporting settings. One or more Component Carrier (CC) IDs. Mode (e.g. Mode A / Mode B).

[0264] The association of the prohibition timer / time window may be determined based on rules defined in advance in a specification, may be configured using RRC signaling, may be determined based on reporting of UE capability information, or may be determined based on a combination of at least two of these.

[0265] <<Embodiment A1-1>> Embodiment A1-1 may be applied to, for example, single CC and multi-event cases.

[0266] For example, a UE IBR using one CC may be configured for the UE.

[0267] For example, a UE may be configured with a UEIBR for multiple events.

[0268] Hereinafter, the [CSI] reporting setting [ID] may be simply referred to as setting [ID].

[0269] The association of the first UL channel with the configuration event / configuration may be at least one of the following cases 1-1-1 to 1-1-3: Case 1-1-1 (see Figure 3A): Multiple events / settings are associated with one primary UL channel resource. Case 1-1-2 (see FIG. 3B): Multiple events / settings are associated with multiple primary UL channel resources. One event / setting is associated with one primary UL channel resource. Case 1-1-3 (see FIG. 3C): Multiple events / settings are associated with multiple first UL channel resources. Multiple first UL channel resources may be associated with one event / setting, or multiple events / settings may be associated with one first UL channel resource.

[0270] If the operation of the prohibition timer for SR in the existing system is applied / reused for the prohibition timer of the UEIBR, it is assumed that the prohibition timer is applied for each first UL channel (PUCCH) resource.

[0271] In this case, considering the above cases 1-1-1 / 1-1-2 / 1-1-3, there is a concern that transmission latency / delay may occur due to the occurrence of more primary UL channel transmissions (Issue 1A). The following describes a solution to this problem.

[0272] The implementation / operation of the inhibit timer / time window may be at least one of the following options 1.1A to 1.4A: · Option 1.1A: The prohibition timer / time window operates per primary UL channel resource. · Option 1.2A: The prohibition timer / time window operates per event / setting associated with one primary UL channel resource. · Option 1.3A: The prohibition timer / time window operates per configured event / setting in one CC. · Option 1.4A: Inhibit timer / time window does not apply.

[0273] For case 1-1-1, for example, application of options 1.1A / 1.2A / 1.4A is suitable.

[0274] For case 1-1-2, for example, application of option 1.1A / 1.4A is suitable.

[0275] For case 1-1-3, for example, application of options 1.1A / 1.2A / 1.3A / 1.4A is suitable.

[0276] For example, the UE may not evaluate other events while the inhibit timer is running, and after the inhibit timer expires, the UE may resume evaluating events.

[0277] For example, the UE may evaluate other events while the inhibit timer is running, and after the inhibit timer expires, the UE may resume evaluating the events.

[0278] In this case, if the event condition of the other event is satisfied while the prohibit timer is running, the UE may transmit the first UL channel corresponding to the other event after (immediately after) the prohibit timer expires.

[0279] In this case, if the event condition of the other event is satisfied while the prohibition timer is running, the UE may drop the transmission of the first UL channel corresponding to the other event.

[0280] In this case, if the event condition of the other event is satisfied while the prohibition timer is running, the UE may determine whether to transmit or drop the first UL channel based on the priority of the event related to the prohibition timer and the priority related to the other event.

[0281] Figure 4 is a diagram showing an example of the operation of the prohibition timer according to option 1.1A. The example shown in Figure 4 shows an example in which evaluation of each event (number of event instances) is performed for the RSs of the current beam and the RSs (RS#0-RS#N) of the new beam. In the example shown in Figure 4, when the event condition is met a certain number of times (e.g., M) within the evaluation window of each event instance (when the event instance reaches M), the UE is triggered to transmit the corresponding first UL channel. The M may be set for each event, and in the example shown in Figure 4, M=5 for event 2 and M=1 for event 7.

[0282] The arrangement of each first UL channel resource / RS / first DL signal / second UL channel and the evaluation of the event instance (for example, the value of M) are similar in the following similar drawings, and therefore will not be described again.

[0283] 4, at a certain time, the event instance of event 2 of RS#0 reaches M (=5), and the corresponding first UL channel is triggered, and the prohibit timer corresponding to the first UL channel is started.

[0284] In the example shown in Figure 4, even if the trigger conditions of other first UL channels (the first UL channel related to event 7 of RS#0 and the first UL channel related to event 2 of RS#1) are met while the prohibition timer is operating, the other first UL channels will not be transmitted.

[0285] FIG. 5 is a diagram showing an example of the operation of a time window according to option 1.1A. In the example shown in FIG. 5, time windows corresponding to each first UL channel resource are shown. In the example shown in FIG. 5, at a certain time, the event instance of event 2 of RS#0 reaches M, and the corresponding first UL channel is triggered. Furthermore, at other times after the certain time, the trigger conditions of other first UL channels (the first UL channel related to event 7 of RS#0 and the first UL channel related to event 2 of RS#1) are satisfied.

[0286] In the example shown in Fig. 5, the first UL channel corresponding to event 2 of RS#0 is transmitted within the time window corresponding to the resource of the other first UL channel. In this case, the UE does not transmit the other UL channel.

[0287] Although not shown in FIG. 5, a time window corresponding to each first UL channel resource may operate.

[0288] Figure 6 shows an example of the operation of the prohibition timer for options 1.2A / 1.3A. In the example shown in Figure 6, at a certain time, the event instance of event 2 of RS#0 reaches M, and the corresponding first UL channel is triggered. The prohibition timer corresponding to the first UL channel (prohibition timer for event 2) is started.

[0289] Furthermore, while the prohibition timer for event 2 is running, the trigger conditions for other first UL channels (the first UL channel for event 7 of RS#0 and the first UL channel for event 2 of RS#1) are satisfied. In this case, the UE transmits the first UL channel for event 7, which is different from event 2, and does not transmit the first UL channel for event 2 of RS#1. This is because the prohibition timer is configured / applied for each event / configuration.

[0290] FIG. 7 is a diagram showing an example of the operation of the time window according to options 1.2A / 1.3A. In the example shown in FIG. 7, a time window for each event corresponding to each first UL channel resource is shown. In the example shown in FIG. 7, at a certain time, the event instance of event 2 of RS#0 reaches M, and the corresponding first UL channel is triggered. Furthermore, at other times after the certain time, the trigger conditions of other first UL channels (the first UL channel related to event 7 of RS#0 and the first UL channel related to event 2 of RS#1) are satisfied.

[0291] In this case, the UE transmits the first UL channel related to event 7, which is different from event 2, and does not transmit the first UL channel related to event 2 of RS#1. This is because a time window is set / applied for each event / setting, and even if the first UL channel related to event 2 is transmitted during the time window of event 7, transmission of the first UL channel related to event 7 is not prohibited.

[0292] Although not shown in FIG. 7, time windows (for event 2 and event 7) corresponding to each first UL channel resource may operate.

[0293] For example, in option 1.3A, when a prohibition timer for a certain event is running, transmission of multiple (for example, all) configured first UL channels associated with the event may be prohibited.

[0294] Also, for example, in option 1.3A, if a first UL channel is transmitted within a period of a time window corresponding to a plurality of first UL channel resources that are configured, even if the event instance satisfies the trigger condition again, transmission of the first UL channel associated with the event for which the trigger condition is satisfied among the plurality of first UL channel resources that are configured may be prohibited.

[0295] 4 to 7, the RS of the current beam and the RS of the new beam are transmitted using the same period (and different start positions / offsets), but these are merely examples and are not limited to the examples shown. For example, the RS of the current beam and the RS of the new beam may be transmitted using (different) periods / start positions / offsets that are set separately.

[0296] Also, in options 1.2A / 1.3A, the start position / length of the prohibition timer / time window for each event / setting may be set / specified in common, or may be set / specified separately (e.g., may be different).

[0297] According to embodiment A1-1, even in the single CC and multi-event cases, it is possible to appropriately define the operation related to the prohibition timer / time window of the first UL channel.

[0298] <<Embodiment A1-2>> Embodiment A1-2 may be applied to, for example, multi / cross CC and single event cases.

[0299] For example, a UE IBR for one event may be configured for the UE.

[0300] For example, a UEIBR that uses multiple CCs (which may be called multi-CC / cross CC) may be configured for the UE.

[0301] The association of the first UL channel with the configuration event / configuration may be at least one of the following cases 1-2-1 to 1-2-3: Case 1-2-1 (see FIG. 8A): Multiple CCs are associated with one primary UL channel resource. Case 1-2-2 (see FIG. 8B): Multiple CCs are associated with multiple first UL channel resources. One CC is associated with one first UL channel resource. Case 1-2-3 (see FIG. 8C): Multiple CCs are associated with multiple first UL channel resources. Multiple first UL channel resources may be associated with one CC, or multiple CCs may be associated with one first UL channel resource.

[0302] If the operation of the prohibition timer for SR in the existing system is applied / reused for the prohibition timer of the UEIBR, it is assumed that the prohibition timer is applied for each first UL channel (PUCCH) resource.

[0303] In this case, considering the above cases 1-2-1 / 1-2-2 / 1-2-3, there is a concern that transmission latency / delay will occur due to the occurrence of more primary UL channel transmissions (Issue 1B). The following describes a solution to this problem.

[0304] The implementation / behavior of the prohibition timer / time window may be at least one of the following options 1.1B to 1.4B: · Option 1.1B: The prohibition timer / time window operates per primary UL channel resource. · Option 1.2B: The prohibition timer / time window operates per CC associated with one primary UL channel resource. · Option 1.3B: The prohibition timer / time window operates per configured CC among multiple CCs. · Option 1.4B: No prohibition timer / time window applies.

[0305] For case 1-2-1, for example, application of options 1.1B / 1.2B / 1.4B is suitable.

[0306] For case 1-2-2, for example, application of option 1.1B / 1.4B is suitable.

[0307] For case 1-2-3, for example, application of options 1.1B / 1.2B / 1.3B / 1.4B is suitable.

[0308] In embodiment A1-2, the above embodiment A1-1 may be applied by replacing "event / setting" with "CC."

[0309] According to embodiment A1-2, even in the multi / cross CC and single event cases, it is possible to appropriately define the operation related to the prohibition timer / time window of the first UL channel.

[0310] <<Embodiment A1-3>> Embodiments A1-3 may be applied to, for example, multi / cross CC and multi-event cases.

[0311] For example, a UE may be configured with a UEIBR for multiple events.

[0312] For example, a UEIBR that uses multiple CCs (multi-CC / cross CC) may be configured for the UE.

[0313] The association of the first UL channel with the configuration event / configuration may be at least one of the following cases 1-3-1 to 1-3-4: Case 1-3-1 (see Figure 9A): Multiple CCs / events / settings are associated with one primary UL channel resource. Case 1-3-2 (see FIG. 9B): One CC among multiple CCs is associated with one first UL channel resource. Multiple (or one) events / settings are associated with one first UL channel resource. Case 1-3-3 (see FIG. 9C): Multiple (or one) CCs are associated with one primary UL channel resource. One event / setting is associated with one primary UL channel resource. Case 1-3-4 (see FIG. 9D): Multiple CCs are associated with one primary UL channel resource. Multiple events / settings are associated with one primary UL channel resource.

[0314] In this case, considering the above cases 1-3-1 / 1-3-2 / 1-3-3 / 1-3-4, there is a concern that transmission latency / delay will occur due to the occurrence of more primary UL channel transmissions (Issue 1C). The following describes a solution to this problem.

[0315] The implementation / behavior regarding the prohibition timer / time window may be at least one of the following options 1.1C to 1.6C: · Option 1.1C: Inhibit timer / time window operates per primary UL channel resource. · Option 1.2C: The prohibition timer / time window operates per CC associated with one primary UL channel resource. · Option 1.3C: The prohibition timer / time window operates per event / setting associated with one primary UL channel resource. · Option 1.4C: The prohibition timer / time window operates per configured CC among multiple CCs. · Option 1.5C: The prohibition timer / time window operates per configured event / setting in one CC. · Option 1.6C: The prohibition timer / time window does not apply.

[0316] For case 1-3-1, for example, application of options 1.1C / 1.2C / 1.3C / 1.4C / 1.5C / 1.6C is suitable.

[0317] For case 1-3-2, for example, application of options 1.1C / 1.3C / 1.5C / 1.6C is suitable.

[0318] For case 1-3-3, for example, application of options 1.1C / 1.2C / 1.4C / 1.6C is suitable.

[0319] For case 1-3-4, for example, application of option 1.1C / 1.6C is suitable.

[0320] The embodiment A1-3 may be applied in combination with the embodiment A1-1 and the embodiment A1-2.

[0321] According to embodiment A1-3, even in the case of multi / cross CC and multi-event, it is possible to appropriately define the operation related to the prohibition timer / time window of the first UL channel.

[0322] <<Embodiment A1-4 (Variation)>> For each of the above options (eg, 1.2A / 1.3A / 1.3C / 1.5C), the inhibit timer / time window may operate per event / setting.

[0323] In this case, a prohibition timer / time window may operate for each of multiple event / setting combinations.

[0324] An inhibit timer / time window may correspond to multiple events (e.g., events 1 / 2 / 7).

[0325] The combination of the multiple events may be specified in advance, may be configured / indicated using RRC signaling / MAC CE / DCI, may be determined based on a report of UE capabilities, or may be determined based on a combination of at least two of these.

[0326] For example, if the event condition for event 2 is met, the inhibit timers associated with events 2 and 7 may run.

[0327] For example, if the first UL channel for event 7 is transmitted within a time window associated with events 2 and 7, the transmission of the first UL channel for both events 2 and 7 may be prohibited (may not be transmitted) for the first UL channel resource corresponding to that time window.

[0328] Furthermore, for each of the above cases, which option is applied may be specified in advance in a specification, may be configured / indicated using RRC signaling / MAC CE / DCI, may be determined based on a UE capability report, or may be determined based on a combination of at least two of these. For example, for each of the above cases, which option is applied may be configured / indicated [semi-statically / dynamically] using RRC signaling / MAC CE / DCI [based on UE capability], or may be switched [implicitly] based on a NW / UE configuration.

[0329] Also, which option applies may be determined for each mode / first UL channel resource.

[0330] For example, if a first UL channel resource is associated with mode A for one event (e.g., events 2 and 7) and another first UL channel resource is associated with mode B for another event (e.g., event 1), one option (e.g., option 1.2A) may apply to the one first UL channel resource and another option (e.g., option 1.4A) may apply to the other first UL channel resource.

[0331] Note that the events / modes / options are merely examples, and any (combination of) events / modes / options in the present disclosure may be applied.

[0332] According to this embodiment A1, it is possible to appropriately define the operation related to the prohibition timer / time window of the first UL channel, and it is possible to reduce the transmission waiting time / delay caused by the first UL channel.

[0333] <Analysis B0> In option 1, one measurement window corresponds to (is associated with) one first PUCCH resource, and the measurement window ends at a point preceding T_PUCCH (the transmission timing of the first PUCCH, i.e., the PUCCH preparation time T_proc) and starts at a point preceding T_window. An event instance may occur if an event instance condition is met during an evaluation opportunity within the measurement window. T_proc may be the processing time or preparation time for the first PUCCH, and may be configured by RRC (reported as UE capability and based on that report).

[0334] <Analysis B1> The event evaluation period may be the period of [event] [instance] evaluation [opportunity]. The new beam RS period may be the period of [periodic] RS for measurement of the new beam. The current beam RS period may be the period of [periodic] RS for measurement of the current beam. The first PUCCH resource period may be the period of [periodic] first PUCCH resource. When option 1 is applied to the measurement window, it is considered that the event evaluation period is equal to the period of the new beam RS and the current beam RS with respect to the event evaluation period, new beam RS period, current beam RS period, and first PUCCH resource period.

[0335] <Embodiment B1> When option 1 is applied to the measurement window, the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period may have at least one of the following relationships: -◆Relationship 1: The event evaluation period, the new beam RS period, and the current beam RS period are smaller than the first PUCCH resource period. -◆Relationship 2: The event evaluation period, the new beam RS period, and the current beam RS period are equal to the first PUCCH resource period. -◆Relationship 3: The event evaluation period, the new beam RS period, and the current beam RS period are greater than the first PUCCH resource period.

[0336] When option 1 is applied to the measurement window, the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period may be based on any of the following options:

[0337] Option 1 All of Relationships 1 to 3 may be specified in the specification. All of Relationships 1 to 3 may be assumed. There may be no constraints between the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period. Option 1 ensures flexibility in resource configuration and can adapt to various use cases and requirements.

[0338] Option 2 One or more combinations of Relationships 1 to 3 may be specified in the specification, and relationships not specified in the specification may not be considered / assumed. There may be constraints between the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period. The measurement process and [event] evaluation process considered in Option 2 are simpler than those in Option 1, and can be easier to implement and operate.

[0339] Which of Relationships 1 to 3 is enabled / assumed may be specified in the specifications or may be notified from the NW to the UE by the RRC IE / MAC CE / DCI.

[0340] Embodiment B1 can be applied to modes A / B.

[0341] According to this embodiment, the relationship between the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period becomes clear, and the UE can appropriately perform event evaluation, measurement of the new beam RS, measurement of the current beam RS, and transmission of the first PUCCH.

[0342] <Analysis B2> The introduction of a prohibition timer is being considered.

[0343] <Embodiment B2> An inhibit timer, or an equivalent method to an inhibit timer, may be applied to any of the above options 1 to 4 regarding the measurement window.

[0344] The UE may apply a first PUCCH transmission prohibition process that prohibits / cancels transmission of a specific first PUCCH for which a first PUCCH transmission prohibition condition is satisfied.

[0345] For any of the measurement window options, an inhibit timer may be applied.

[0346] For option 1, an equivalent method to the inhibit timer may be applied using a measurement window (or dedicated window).

[0347] In designing the first PUCCH transmission prohibition condition, a false alarm (false detection) may be taken into consideration. A false alarm may be a case where the NW falsely detects the first PUCCH and schedules the second PUSCH even though the trigger condition is not met. Including the second PUSCH caused by a false alarm in a specific signal may cause prohibition / cancellation of the first PUCCH transmission even after the second PUSCH is transmitted due to the false alarm. A report may not be transmitted immediately after an event is triggered.

[0348] To prevent excessively frequent first PUCCH transmissions, at least one of the following multiple options x may be applied:

[0349] <<Option 1>> The UE does not have to transmit the first PUCCH that satisfies the first PUCCH transmission prohibition condition (it may cancel the first PUCCH transmission that satisfies the first PUCCH transmission prohibition condition).

[0350] Any of the following options 1-x may be applied:

[0351] ◆Option 1-1 A prohibition timer is applied. While the prohibition timer is running, the UE may not transmit the first PUCCH (new UCI) (may cancel the first PUCCH transmission during the prohibition timer running period). The UE may transmit the first PUCCH when the prohibition timer is not running (may transmit the first PUCCH outside the prohibition timer running period). The prohibition timer may be started at the end of the specific signal.

[0352] The first PUCCH transmission prohibition condition for the first PUCCH may be that the resources of that first PUCCH overlap (or are included in) [part or all of] a specific period (prohibition timer operation period) after the transmission / resource of a specific signal.

[0353] ◆Options 1-2 A method using measurement windows (or dedicated windows) is applied. If a specific measurement window contains a transmission of a specific signal triggered by [an event within] another measurement window, the UE may cancel the first PUCCH transmission for the specific measurement window. If a specific measurement window does not contain a transmission of a specific signal triggered by [an event within] another measurement window, the UE may transmit the first PUCCH for the specific measurement window.

[0354] The first PUCCH transmission prohibition condition for the first PUCCH may be that the transmission / resource of the specific signal overlaps (partially or entirely) with (or is included in) the measurement window (first time window) corresponding to the first PUCCH (of the event (first event) that triggers the first PUCCH). The specific signal may be transmitted / triggered based on the occurrence of an event (second event) in a measurement window (second time window) different from the measurement window corresponding to the first PUCCH.

[0355] 10 shows an example of cancellation of the first PUCCH according to option 1-2 of embodiment B2. The first PUCCH#A is triggered by an event in measurement window #A, and the first PUCCH#B is triggered by an event in measurement window #B. In this example, the specific signal is the first PUCCH, and the first PUCCH transmission prohibition condition for the first PUCCH#B is that the transmission / resources of the specific signal (first PUCCH#A) overlap with a portion of the measurement window #B corresponding to the first PUCCH#B. Since the first PUCCH transmission prohibition for the first PUCCH#B is satisfied, the UE may cancel the transmission of the first PUCCH#B.

[0356] If a dedicated window is applied, its window width (eg, T_prohibitwindow) can be set to a value different from T_window.

[0357] If T_window<first PUCCH resource period (or T_prohibitwindow<first PUCCH resource period) and the configuration indicates (guarantees) that a specific signal is not included within the measurement window, the UE may not transmit the first PUCCH (new UCI) if the following additional conditions are met: ◆ Additional condition: A specific signal is transmitted between the end of the measurement window and the end of the previous measurement window.

[0358] <<Option 2>> Choice 1-x may be applied for each of at least one parameter among the following choices 2-x: The CSI-ReportConfig may be associated with a first PUCCH resource [ID] (may include information indicating the first PUCCH resource). The first PUCCH resource [ID] may be associated with an event type (the information on the first PUCCH resource may include information indicating the event type). ◆Option 2-1: New beam [RS]. ◆Option 2-2: CSI reporting configuration (CSI-ReportConfig) associated with the same first PUCCH resource [ID]. ◆Option 2-3: Event type associated with the same first PUCCH resource [ID]. ◆Option 2-4: First PUCCH resource [ID].

[0359] <<Option 3>> The type of the specific signal may be specified in the specification or may be set / indicated by the RRC IE / MAC CE / DCI. The type of the specific signal may include at least one of the following multiple options 3-x:

[0360] ◆Option 3-1 1st PUCCH.

[0361] ◆Option 3-2 Second PUSCH. The second PUSCH may be one of the following options 3-2-x: -◆Option 3-2-1: Optional second PUSCH. - ◆Option 3-2-2: Second PUSCH requested / triggered by valid first PUCCH Whether the first PUCCH is valid or invalid may be any of the following options 3-2-2-x. Option 3-2-2-1: If the first PUCCH is within a request period before the transmission of the second PUSCH, the UE may consider (determine) that the first PUCCH is valid (the second PUSCH is requested / triggered by the valid first PUCCH, or the second PUSCH is a specific signal). Otherwise, the UE may consider that the first PUCCH is invalid (the second PUSCH is not requested / triggered by the valid first PUCCH, or the second PUSCH is due to a false alarm). The length / start / end / timing of the request period may be specified in the specification, or may be configured / indicated by the RRC IE / MAC CE / DCI. --◆Option 3-2-2-2: The determination of whether the first PUCCH is valid or invalid may depend on the UE implementation.

[0362] ◆Option 3-3 Both the first PUCCH and the second PUSCH (set), where the second PUSCH may be any of the options 3-2-x above.

[0363] Applying option 3-2-2 or option 3-3 may prevent the inhibit timer from starting after the second PUSCH transmission triggered by a false alarm.

[0364] For option 1-1, option 3 except option 3-3 can be applied. For option 1-2, all options 3-x of option 3 can be applied.

[0365] For Mode A, Option 3 except Option 3-2-2 can be applied. For Mode B, all Options 3-x of Option 3 can be applied.

[0366] <<Option 4>> For Mode A, when Option 3-2 or Option 3-3 is applied, the specific signal may include DCI scheduling the second PUSCH in addition to the second PUSCH itself.

[0367] If options 2-4 are applied (for each first PUCCH resource), the specific signal may be restricted by at least one of the following options 4-x: ◆Option 4-1: The specific signal is configured by configuring the first PUCCH resource (for example, firstPUCCHResourceConfig-UEIBR) based on the occurrence of an event (satisfaction of a trigger condition) within the measurement window [corresponding to the second PUSCH]. ◆Option 4-2: The specific signal is triggered by the same beam [RS] as the (measured) beam [RS] used when an event occurs within the measurement window (when the trigger condition is met). ◆Option 4-3: The specific signal is associated with a configuration (CSI-ReportConfig pointing to that first PUCCH [resource]) associated with the first PUCCH [resource] based on the occurrence of an event within the measurement window (the fulfillment of a trigger condition). ◆Option 4-4: The specific signal is associated with an event type (of the event) associated with the first PUCCH [resource] based on the occurrence of an event (satisfaction of the trigger condition) within the measurement window.

[0368] According to this embodiment, it is possible to prevent excessively frequent transmission of the first PUCCH due to false alarms or the like.

[0369] <Embodiment C1> This embodiment may be applied to option 1 below. ◆ Option 1: The measurement window is from T_PUCCH-T_proc-T_window to T_PUCCH-T_proc. T_PUCCH is the first PUCCH transmission occasion. T_proc is configured by RRC.

[0370] 11 shows an example of a measurement window according to embodiment C1. In this example, the start time of the first PUCCH resource #A is T_PUCCH, the end time of the measurement window #A is t=T_PUCCH-T_proc, and the start time of the measurement window #A is t-T_window. When an event occurs in the measurement window #A (when a trigger condition is satisfied in the measurement window #A), the UE may transmit the first PUCCH in the first PUCCH resource #A and then transmit the second PUSCH in the second PUSCH resource #A.

[0371] For option 1, at least one of the following embodiments C1-x may be applied.

[0372] <<Embodiment C1-1>> In Mode A / B, the UE may not be able to transmit the first PUCCH in the pre-configured first PUCCH resource depending on the situation (the first PUCCH resource is unavailable).

[0373] In the present disclosure, the following may be interpreted interchangeably: the first PUCCH resource is unavailable; the first PUCCH resource overlaps with the transmission / reception of other channels / signals; the priority of the first PUCCH resource is lower than the priority of the transmission / reception of the other overlapping channels / signals; and the first PUCCH resource is configured / indicated as a DL resource / symbol / slot.

[0374] If it is known that a first PUCCH resource is unavailable before the start of the measurement window for that first PUCCH resource, the UE may omit event evaluation in that measurement window. In the example of Figure 11 above, if it is known that a first PUCCH resource #B is unavailable before the start of the measurement window #B for that first PUCCH resource #B, the UE may omit event evaluation in the measurement window #B. The omission of event evaluation may be based on at least one of the following examples. ◆ Example: The UE does not perform measurements on RS resources that fall within its measurement window. ◆ Example: The UE does not perform measurements on RS resources that are only contained within its measurement window. ◆ Example: The UE performs measurements on RS resources included within its measurement window, but does not perform event evaluation within the measurement window.

[0375] <<Embodiment C1-2>> In Mode B, the UE may not be able to transmit the second PUSCH in the preconfigured second PUSCH resource (CG-PUSCH resource) depending on the situation.

[0376] In the present disclosure, the following may be interpreted as interchangeable: the second PUSCH resource is unavailable; the second PUSCH resource overlaps with the transmission / reception of another channel / signal; the priority of the second PUSCH resource is lower than the priority of the transmission / reception of the other overlapping channel / signal; and the second PUSCH resource is configured / indicated as a DL resource / symbol / slot.

[0377] When the first PUCCH is transmitted or received, the UE may transmit the second PUSCH in a specific second PUSCH resource thereafter. The NW may assume that when the first PUCCH is transmitted or received, the UE will transmit the second PUSCH in a specific second PUSCH resource thereafter.

[0378] If it is known that a second PUSCH resource (CG-PUSCH) is unavailable before the start of the measurement window for the first PUCCH corresponding to that second PUSCH resource, the UE may omit event evaluation in that measurement window. In the example of Figure 11 above, if it is known that a second PUSCH resource #B is unavailable before the start of the measurement window #B for the first PUCCH resource #B corresponding to the second PUSCH resource #B, the UE may omit event evaluation in the measurement window #B. The omission of event evaluation may be based on at least one of the following examples. ◆ Example: The UE does not perform measurements on RS resources that fall within the measurement window corresponding to the unavailable second PUSCH resource. ◆ Example: The UE does not perform measurements on RS resources that are only included within the measurement window corresponding to the unavailable second PUSCH resource. ◆ Example: The UE performs measurements on RS resources that fall within a measurement window corresponding to an unavailable second PUSCH resource, but does not perform event evaluation within that measurement window.

[0379] If a second PUSCH (CG-PUSCH) resource is known to be unavailable before the start of the measurement window for the first PUCCH corresponding to that second PUSCH resource, the UE may perform an event evaluation in the measurement window for that first PUCCH and, if a trigger condition is met, transmit the first PUCCH and may transmit the second PUSCH in the first available second PUSCH (CG-PUSCH) resource after the [unavailable] second PUSCH resource.

[0380] 11, when the configured second PUSCH resource #B is unavailable, an event evaluation may be performed in a measurement window #B for the corresponding first PUCCH resource #B, and if a trigger condition is met, the first PUCCH may be transmitted in the first PUCCH resource #B, and the second PUSCH may be transmitted in the next available second PUSCH resource #C. This operation may be based on at least one of the following examples. ◆Example: When an event evaluation in measurement window #B for the first PUCCH resource #B does not meet the trigger condition, the UE may include a report to be transmitted in the [unavailable] second PUSCH resource #B (a report based on an event in measurement window #B for the corresponding first PUCCH resource #B) in the second PUSCH in the [available] second PUSCH resource #C. ◆Example: When the event evaluation in the measurement window #C for the first PUCCH resource #C meets the trigger condition, the UE may include at least one of the following reports in the second PUSCH in the [available] second PUSCH resource #C: -◆Report: Report to be sent on the [unavailable] second PUSCH resource #B (report based on an event in measurement window #B for the corresponding first PUCCH resource #B). -◆Report: Report based on an event in the measurement window for the first PUCCH resource #C corresponding to the second PUSCH resource #C [available]. -◆Report: Report based on the event with higher priority between an event in measurement window #B corresponding to the [unavailable] second PUSCH resource #B (corresponding first PUCCH resource #B) and an event in measurement window #C corresponding to the [available] second PUSCH resource #C (corresponding first PUCCH resource #C).

[0381] According to this embodiment, in option 1, even if the pre-configured first PUCCH resource or second PUSCH resource is unavailable, the UE can still operate properly.

[0382] <Embodiment C2> This embodiment may be applied to option 1.

[0383] In mode A / B, the event evaluation period may be equal to the new beam RS period and the current beam RS period. The relationship between the event evaluation period, the new beam RS period, the current beam RS period, and the first PUCCH resource period may be based on at least one of the following embodiments C2-x.

[0384] <<Embodiment C2-1>> The event evaluation period may be: event evaluation period = new beam RS period = current beam RS period < first PUCCH resource period.

[0385] For a measurement window to include one or more evaluation occasions, T_window ≧ event evaluation period. When a value of M is set, T_window ≧ M* event evaluation period.

[0386] The UE may have a counter that counts event instances (the fact that event instance conditions are met). M may be the maximum value / threshold of the counter for event instances, may be defined in the specification, or may be notified from the NW to the UE by RRC IE / MAC CE / DCI. When the counter reaches M, the UE may determine that an event has occurred or may trigger the transmission of the first PUCCH / report. The counter may be reset at the end / completion of the measurement window.

[0387] When the event evaluation period ≦ T_window < the first PUCCH resource period, some evaluation opportunities may not be included in any measurement window. In this case, the operation of the UE may be based on any of the following multiple options x. ◆ Option 1: The UE performs measurements on the RS at all evaluation opportunities and does not use the RS outside the measurement window for event evaluation. ◆ Option 2: The UE does not perform measurements on the RS at evaluation opportunities that are not included in any measurement window.

[0388] In the example of FIG. 12, the event evaluation period < T_window < the first PUCCH resource period, and some evaluation opportunities are not included in any measurement window.

[0389] When the event evaluation period < the first PUCCH resource period ≦ T_window, all evaluation opportunities are included in some measurement window. In this case, the UE may perform measurements on the RS at all evaluation opportunities. In the example of FIG. 13, the event evaluation period < the first PUCCH resource period = T_window, and multiple measurement windows are consecutive. In this case, all evaluation opportunities are included in some measurement window.

[0390] <<Embodiment C2-2>> The event evaluation period = the new beam RS period = the current beam RS period = the first PUCCH resource period may be true.

[0391] For a measurement window to include one or more evaluation occasions, T_window ≧ event evaluation period = first PUCCH resource period. When the value of M is set, T_window ≧ M * event evaluation period = M * first PUCCH resource period.

[0392] 14, the event evaluation period = first PUCCH resource period = T_window, and multiple measurement windows are consecutive, in which case all evaluation opportunities are included in one of the measurement windows.

[0393] <<Embodiment C2-3>> The event evaluation period may be: event evaluation period = new beam RS period = current beam RS period > first PUCCH resource period.

[0394] For a measurement window to include one or more evaluation occasions, T_window ≧ event evaluation period. When a value of M is set, T_window ≧ M* event evaluation period.

[0395] If the first PUCCH resource period < event evaluation period ≦ T_window, multiple measurement windows for consecutive first PUCCH resources may include the same evaluation opportunity, making the first PUCCH resource redundant. In the example of Figure 15, the first PUCCH resource period < event evaluation period = T_window, and measurement windows #A and #B corresponding to first PUCCH resources #A and #B include the same evaluation opportunity. This embodiment may be based on any of the following options: ◆Option 1: The UE does not assume embodiment C2-3. ◆ Option 2: Transmit the first PUCCH in only one first PUCCH resource among a plurality of first PUCCH resources for a plurality of measurement windows that include the same evaluation occasion.

[0396] According to this embodiment, the UE can perform event evaluation using an appropriate relationship between the event evaluation period, the new beam RS period, and the current beam RS and the first PUCCH resource period.

[0397] <Embodiment C3> This embodiment may be applied to option 2 below. ◆ Option 2: The measurement window is from T_Instance-T_window to T_Instance. T_Instance is configured by RRC. T_Instance is the evaluation occasion of the event instance. The UBER in the second PUSCH is based on the most recent measurements for the RS of the new / current beam.

[0398] 16, M=3. In this example, within each measurement window, when an event instance based on a measurement of a new beam RS occurs, the UE may increment a counter of event instances within the measurement window. When the counter reaches M, a UE IBR is triggered and the UE may prepare the first PUCCH transmission.

[0399] <<Measurement window constraints>> T_window may be greater than or equal to the first PUCCH resource period so that the measurement window includes one or more evaluation occasions.

[0400] <<Constraints on the number of overlapping measurement windows>> Without constraints, the measurement windows overlap in the number of evaluation occasions they contain.

[0401] The number of overlapping measurement windows (number of overlaps) may be limited. The maximum value of T_window may be limited. There may be a constraint that the first PUCCH resource period * number of possible overlaps > T_window. The number of possible overlaps may be the maximum number of overlaps. The number of possible overlaps may be reported information of the UE capabilities or may be set by RRC [based on the UE capabilities].

[0402] Measurement windows may be thinned. The UE may start one measurement window for N evaluation occasions [of an event instance]. The number of evaluation occasions may be N times the number of measurement windows. N may be greater than 1. N may be specified in the specification or configured by RRC.

[0403] A new parameter may be set that indicates the amount of overlap allowed.

[0404] The number of overlaps may not be limited.

[0405] According to this embodiment, in option 2, the UE can evaluate the event using an appropriate measurement window.

[0406] <Embodiment C4> This embodiment may be applied to option 4 below. ◆ Option 4: If an Event 2 instance for a new beam is obtained at time t, the UE starts (restarts) a timer (time window) for the new beam, the expiration time of which is equal to the length set by the NW of the time window (T_window).

[0407] Regarding the determination of the triggering event for Event 2, at least Candidate #2 of the following multiple candidates supports resetting the count. ◆Candidate #1: RS reconfiguration / update or MAC CE signaling is received for a new beam. ◆Candidate #2: The command TCI state [based on the measured current beam] is updated. ◆Candidate #3: UEIBR is sent. ◆ Candidate #4: NW response (eg, DCI in step 2 of mode A) is detected. ◆Candidate #5: The time window (measurement window / timer) expires. ◆Candidate #6: The threshold for event evaluation is reconfigured by RRC signaling.

[0408] In the example of Figure 17, M = 3. In this example, when an event instance based on measurement of a new beam RS occurs, the UE may start / restart a timer for the measurement window and increment a counter of the event instance. If the counter reaches M while the timer is running, a UE IBR is triggered and the UE may prepare for the first PUCCH transmission and reset the counter. If the timer expires, the UE may reset the counter.

[0409] After a specific new beam satisfies the trigger condition, when the UE is unable to transmit the corresponding first PUCCH, or when the UE transmits the corresponding first PUCCH but is unable to receive DCI, if an event instance does not occur / occur in a subsequent evaluation occasion, the UE may cancel the retransmission of the first PUCCH. The UE may cancel the retransmission of the first PUCCH based on resetting a counter or expiry of a timer. The UE may control the counter / timer based on one of the following options:

[0410] Option 1 The UE may wait for the timer (time window) to expire and then reset the counter. While the timer is running, the counter value remains equal to or greater than M unless a counter reset operation is performed due to another factor. If the prohibition timer is not running, the UE may attempt to transmit the first PUCCH again. The first PUCCH may be transmitted even if the trigger condition has changed from being satisfied to not being satisfied by the time of transmission of the first PUCCH.

[0411] Option 2 When a timer (time window) is running and the counter value is greater than or equal to M, and one or more of the conditions in the following options 2-x are met, the UE may stop the timer and reset the counter [when option #5 applies], or may only stop the timer, or may only reset the counter. -◆Option 2-1: No event instance occurred at the evaluation opportunity after the first PUCCH transmission [intention / decision]. -◆Option 2-2: No event instance occurred in X evaluation opportunities after the first PUCCH transmission [intention / decision]. -◆Option 2-3: Of the evaluation opportunities after the first PUCCH transmission [intention / decision], no event instance occurred in X consecutive evaluation opportunities.

[0412] The value of X in options 2-2 and 2-3 may be specified in the specifications or may be set / indicated by the RRC IE / MAC CE / DCI.

[0413] According to this embodiment, in option 4, the UE can appropriately control the first PUCCH transmission.

[0414] <Embodiment C5> This embodiment may be applied to Mode A.

[0415] In Option 1, Mode A, there are two possible cases x:

[0416] Case 1 When Option 1 is applied to the measurement window, if an error occurs in the first PUCCH transmitted by the UE, the following procedure is assumed to occur: -◆The UE transmits the first PUCCH to the NW. -◆The network cannot receive the first PUCCH correctly. -◆The NW does not transmit the first DL channel (DCI scheduling the second PUSCH) to the UE. - The UE cannot receive the first DL channel. -◆The UE does not transmit the second PUSCH to the NW. -◆The network cannot receive the second PUSCH.

[0417] Case 2 When option 1 is applied to the measurement window, if an error occurs in the first DL channel (DCI) transmitted by the NW, the following procedure is assumed to occur: -◆The UE transmits the first PUCCH to the NW. -◆The network receives the first PUCCH. -◆The NW transmits the first DL channel (DCI scheduling the second PUSCH) to the UE. - The UE cannot receive the first DL channel correctly. -◆The UE does not transmit the second PUSCH to the NW. -◆The network cannot receive the second PUSCH.

[0418] In case 1 / 2, the second PUSCH corresponding to the first PUCCH transmitted by the UE is not scheduled correctly, so the [beam] report is not transmitted.

[0419] <<Embodiment C5-1>> In case 1 / 2, if the event is not met in the first or up to Xth measurement window (measurement window #B) after the measurement window (measurement window #A) that triggered the first PUCCH corresponding to the not-transmitted report, one of the following multiple actions x may be taken for that report:

[0420] ◆Operation 1 The UE may not transmit the first PUCCH in the first PUCCH resource corresponding to measurement window #B and may discard (drop) the not transmitted report (corresponding to measurement window #A).

[0421] ◆Operation 2 The UE may transmit a first PUCCH in a first PUCCH resource corresponding to measurement window #B, and transmit the report that was not transmitted [corresponding to measurement window #A] in a subsequent second PUSCH [corresponding to measurement window #B].

[0422] The conditions for transmitting the first PUCCH (first PUCCH transmission conditions) may include the following exceptions. -◆If the event evaluation condition is not met within the measurement window, and a first PUCCH has been transmitted in the first or up to Xth first PUCCH resource after the first PUCCH resource corresponding to that measurement window, and DCI corresponding to that first PUCCH has not been received, or a second PUSCH corresponding to that first PUCCH has not been transmitted (is not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to that measurement window.

[0423] The conditions for prohibiting / canceling transmission of the first PUCCH (first PUCCH transmission prohibition conditions) may be set or may be specified in specifications. The first PUCCH transmission prohibition conditions may include the following exceptions (conditions for transmitting the first PUCCH). -◆If a first PUCCH is transmitted within a measurement window and DCI corresponding to that first PUCCH is not received, or a second PUSCH corresponding to that first PUCCH is not transmitted (not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to that measurement window.

[0424] When a first PUCCH is transmitted, the subsequent second PUSCH scheduled accordingly may either transmit / carry the contents of the report that was not transmitted as is, or may transmit / carry the contents of the latest report at that time based on the same settings as the report that was not transmitted.

[0425] The value of X may be defined in the specification or may be set / indicated by the RRC IE / MAC CE / DCI.

[0426] <<Embodiment C5-2>> In case 1 / 2, if an event is met in the first or up to Xth measurement window (measurement window #B) after the measurement window (measurement window #A) [of the event] that triggered the first PUCCH corresponding to the report that was not transmitted, one of the following multiple actions x may be taken for that report:

[0427] ◆Operation 1 The UE may not transmit the first PUCCH in the first PUCCH resource corresponding to measurement window #B and may discard (drop) the not transmitted report (corresponding to measurement window #A).

[0428] This operation may be an operation when a first PUCCH transmission prohibition process is applied / set. The first PUCCH transmission prohibition condition for a specific first PUCCH may be that another first PUCCH [triggered by the same beam [RS] as the beam [RS] that triggered the specific first PUCCH] is included in the measurement window corresponding to the specific first PUCCH. The first PUCCH transmission prohibition process may be that the UE does not transmit the specific first PUCCH when the first PUCCH transmission prohibition condition for the specific first PUCCH is satisfied.

[0429] ◆Operation 2 The UE may transmit a first PUCCH in a first PUCCH resource corresponding to measurement window #B.

[0430] This operation may be an operation when a first PUCCH transmission prohibition process is applied / set. The first PUCCH transmission prohibition condition for a specific first PUCCH may be that another second PUSCH [triggered by the same beam [RS] as the beam [RS] that triggered the first PUCCH] is included in the measurement window corresponding to the specific first PUCCH. The first PUCCH transmission prohibition process may be that the UE does not transmit the specific first PUCCH when the first PUCCH transmission prohibition condition for the specific first PUCCH is satisfied.

[0431] When the first PUCCH transmission prohibition process is applied / set, the first PUCCH transmission prohibition condition may have the following exceptions: The first PUCCH transmission prohibition condition for a specific first PUCCH may be that another first PUCCH [triggered by the same beam [RS] as the beam [RS] that triggered the specific first PUCCH] is included in the measurement window corresponding to the specific first PUCCH. The first PUCCH transmission prohibition process may be that, when the first PUCCH transmission prohibition condition for the specific first PUCCH is satisfied, the UE does not transmit the specific first PUCCH. -◆If a first PUCCH is transmitted within a measurement window and DCI corresponding to that first PUCCH is not received, or a second PUSCH corresponding to that first PUCCH is not transmitted (not scheduled), the UE may transmit the first PUCCH in the first PUCCH resource corresponding to that measurement window.

[0432] When a first PUCCH is transmitted, a subsequent second PUSCH scheduled accordingly may transmit / carry any of the following contents: -◆The second PUSCH is the content of the report that was not sent [corresponding to measurement window #A]. -◆The second PUSCH may transmit / carry the contents of the latest report at that time based on the same settings as the not transmitted report [corresponding to measurement window #A]. - The second PUSCH may transmit / carry reports on configurations that met the triggering conditions in measurement window #B. -◆The second PUSCH may transmit / carry the content of a report that has a higher priority between a report that was not transmitted [corresponding to measurement window #A] and a report based on measurement window #B.

[0433] Any of the following actions may be taken on a report that has not been sent: - The UE discards reports that were not sent. - The UE keeps the unsent reports until the next second PUSCH transmission opportunity. - The UE retains the unsent report until the specified / configured retention time expires.

[0434] The priority may be based on any of the following priorities: -◆Priority is applied based on CSI-ReportConfig, which stores the settings for each report. -◆The priority based on the CSI-ReportConfig in which the settings of each report are stored may be determined by one of the following multiple determination methods. The priority of an event type may be defined in the specification or may be set by a higher layer parameter. The UE may determine the priority of each report by referring to the event type of each report. --◆Whether the report triggered earlier or the report triggered later is given priority may be specified in the specification or may be set by a higher layer parameter.

[0435] The value of X may be defined in the specification or may be set / indicated by the RRC IE / MAC CE / DCI.

[0436] The lower the priority value of a report, the higher the priority of that report may be.

[0437] The priority based on the CSI-ReportConfig may be based on several calculation methods:

[0438] ◆Calculation method 1 The priority value is calculated using the existing CSI reporting priority value formula, Pri iCSI (y,k,c,s)=2 N Cells M s y+N cells M s k+M s ·c+s may be used. Here, y=0 for aperiodic CSI reporting carried on the PUSCH, y=1 for semi-persistent CSI reporting carried on the PUSCH, y=2 for semi-persistent CSI reporting carried on the PUCCH, and y=3 for periodic CSI reporting carried on the PUCCH. k=0 for CSI reporting carrying L1-RSRP, and k=1 for CSI reporting not carrying L1-RSRP. c may be the index of the serving cell, and N Cellsmay be the value of the upper layer parameter maxNrofServingCells (maximum number of serving cells). For CSI reporting configured using ltm-CSI-ReportConfig, c may be the serving cell index for which the reporting configuration is configured. s may be reportConfigID (ID of CSI-ReportConfig), and M s may be the value of the upper layer parameter maxNrofCSI-ReportConfigurations (maximum number of CSI reporting configurations). For CSI reporting configured using ltm-CSI-ReportConfig, s may be the ltm-CSI-ReportConfigId, and M s may be the value of the upper layer parameter maxNrofLTM-CSI-ReportConfigurations (the maximum number of CSI reporting configurations for LTM). The ascending order of the priority values ​​may be the ascending order of the reportConfigIDs, and the descending order of the priority may be the ascending order of the reportConfigIDs.

[0439] For UEIBR, y may be 0 or any other value {1, 2, 3}.

[0440] Since the smaller the reportConfigID, the higher the priority, it may be assumed that a CSI-ReportConfig that should be given higher priority has a smaller ID.

[0441] ◆Calculation method 2 The priority value is calculated using the existing CSI reporting priority value formula, Pri iCSI (y,k,c,s)=2 N Cells M s y+N cells M s k+M s Part of c+s may be modified and reused. Events may be reflected in the priority.

[0442] In order to allow the reporting priority to differ depending on the event configured by CSI-ReportConfig, a variable indicating the event type may be added to the calculation formula for the priority value.

[0443] For UEIBR, y may be 0 or any other value {1, 2, 3}.

[0444] The variable indicating the event type may be e, where e=0 for the event type with the highest priority, e=1 for the event type with the next highest priority, and e=2 for the event type with the lowest priority. In this case, the formula for calculating the priority value may be one of the following formulas: -◆Pri iCSI (y,k,c,s)=8·N Cells M s e+2 N Cells M s y+N cells M s k+M s c+s -◆Pri iCSI (y,k,c,s)=6·N Cells M s y+2 N Cells M s e+N cells M s k+M s c+s -◆Pri iCSI (y,k,c,s)=6·N Cells M s y+3N Cells M s k+N cells M s e+M s c+s -◆Pri iCSI (y,k,c,s)=6·N Cells M s y+3N Cells M s k+3 M s c+M s e+s -◆PriiCSI (y, k, c, s) = 6·N Cells ·M s ·y + 3·N Cells ·M s ·k + 3·M s ·c + 3·s + e

[0445] According to this embodiment, even if an error occurs in the DCI that schedules the first PUCCH or the second PUSCH in mode A of option 1, the UE can operate properly.

[0446] <Supplementary> <<Notification of Information to UE>> The notification of any information from the [network (NW) (for example, base station (BS))] to the UE in the above-described embodiment (in other words, the reception of any information from the BS by the UE) may be performed using physical layer signaling (for example, DCI), upper layer signaling (for example, RRC signaling, MAC CE, RRC message, LTE positioning protocol (LPP) message), a specific signal / channel (for example, DCI, PDCCH, PDSCH, reference signal), or a combination thereof.

[0447] When the above notification is performed by the MAC CE, the MAC CE may be identified by including a new logical channel ID (LCID) that is not defined in the existing standard in the MAC subheader. The MAC CE may be an extension of the existing MAC CE. For example, the MAC CE may be one in which a new octet is introduced into the existing MAC CE.

[0448] When the notification is performed by DCI, the notification may be performed by a specific field of the DCI, a Radio Network Temporary Identifier (RNTI) used to scramble Cyclic Redundancy Check (CRC) bits assigned to the DCI, the format of the DCI, etc. The specific field may be an existing DCI field or a new DCI field. The RNTI may be an existing RNTI or a new RNTI. The format of the DCI may be an existing DCI format or a new DCI format.

[0449] Furthermore, notification of any information to the UE in the above embodiments may be periodic, semi-persistent (triggered by the UE or the gNB), or aperiodic (triggered by the UE or the gNB).

[0450] In the above embodiment, the UE may receive information (QCL information) of at least one of the following several QCL rules / QCL types from the NW: ◆QCL Type A (Doppler shift, Doppler spread, mean delay and delay spread) ◆QCL Type B (Doppler shift and Doppler spread) ◆QCL Type C (Doppler shift and mean delay) ◆QCL Type D (spatial reception parameters)

[0451] In the above-described embodiments, the QCL source RS for each QCL type may be at least one of the following several RSs: ◆SSB ◆CSI-RS with / without repetition ◆TRS ◆DMRS for PDCCH / PDSCH

[0452] In the above embodiments, the information from the NW may be set / instructed by the following method. ◆ Common to multiple UEs or UE-specific ◆ Cell-specific or common to multiple cells ◆ Per UE / Per CC / Per BWP / Per band / Per cell / Per cell group (CG)

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

[0454] ]> When the above notification is performed by MAC CE, the MAC CE may be identified by including a new LCID not defined in the existing standard in the MAC subheader.

[0455] When the above notification is performed by UCI, the above notification may be transmitted using PUCCH or PUSCH.

[0456] Also, the notification of any information from the UE in the above embodiments may be performed periodically, semi-persistently (triggered by the UE or gNB), or aperiodically (triggered by the UE or gNB). [[ID=二十六]]

[0457] <<Regarding the application of each embodiment>> In the UE / BS, specific (one or more) processing / operations / controls / assumptions / information regarding at least one of the above embodiments may be applied (used) when any one or a plurality of the following conditions are satisfied: · An upper layer parameter indicating the above specific processing / operation / control / assumption / information is set. The specific processing / action / control / assumption / information is determined based on the relevant upper layer parameters. The above specific processes / actions / controls / assumptions / information are specified / activated / triggered by MAC CE / DCI / UCI / resources / channels / RS. Reporting or supporting specific UE capabilities indicating (or relating to) the above specific processes / actions / controls / assumptions / information. · The application of the above specific processing / action / control / assumption / information is judged based on specific conditions.

[0458] The specific UE capabilities may indicate at least one of the following: Supporting specific processing / operations / control / information for at least one of the above embodiments. Support event-triggered beam reporting / UEIBR. Support MIMO / mobility for Rel.19 and later. Support UEIBR using MAC CE / UCI. Supports event combinations (e.g., events 1 / 2 / 7). · Total / total number of beams reported. · Number of beams that meet the condition. Support for prohibit timers / time windows for specific events (e.g., events 2 / 7 / 1). Supports cancellation of the first UL channel.

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

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

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

[0462] Information on whether one or more of the above embodiments / options / choices / examples apply / are used, or which of the above embodiments / options / choices / examples apply / are used, may be based on several of the following methods: The information is configured by one or more higher layer parameters / RRC IEs. The information is determined by one or more relevant higher layer parameters / RRC IEs. The information is directed by the MAC CE / DCI. The information is determined based on one or more UE capabilities. The information is described / defined in the specification. The information is based on the conditions described / defined in the specification. The information is determined by a combination of several pieces of information above. For example, the information is determined by higher layer parameters / MAC CE / DCI settings / indications and reported by UE capabilities.

[0463] The above embodiments / options / choices may be combined into one embodiment / option / choice.

[0464] In the above embodiments, the RS to be measured may be a QCL source RS in an active TCI state / indicated / unified TCI state.

[0465] (Addendum) The following inventions are added regarding one embodiment of the present disclosure. <Appendix 1> a receiver for receiving a reference signal; a control unit that, when a first event based on the reference signal occurs within a first time window, determines whether to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window; If the PUCCH resource overlaps with a specific period after transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window, the control unit cancels transmission of the first PUCCH. <Appendix 2> The terminal described in Supplementary Note 1, wherein the specific period starts from the end of transmission of the specific signal. <Appendix 3> 3. The terminal of claim 1 or 2, wherein the specific signal is transmitted based on the occurrence of a second event within a second time window different from the first time window. <Appendix 4> A terminal described in any of Supplementary Note 1 to Supplementary Note 3, wherein the specific signal includes any of a PUCCH other than the first PUCCH, any physical uplink shared channel (PUSCH), and a PUSCH triggered by a PUCCH within a requested period. <Appendix A> a transmitter for transmitting a reference signal; a control unit that controls reception of a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window when a first event based on the reference signal occurs within the first time window, If the PUCCH resource overlaps with a specific period after transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window, the base station cancels the transmission of the first PUCCH.

[0466] <Supplementary information> The terminal in Supplementary Notes 1 to 4 may be a user terminal 20. The receiver / transmitter in Supplementary Notes 1 to 4 may be a transceiver 220. The controller in Supplementary Notes 1 to 4 may be a controller 210. The base station in Supplementary Notes A may be a base station 10. The receiver / transmitter in Supplementary Notes A may be a transceiver 120. The controller in Supplementary Notes A may be a controller 110.

[0467] The UE may receive and measure the RS of the new / current beam [at the resource / evaluation opportunity for the RS of the new / current beam]. If a first event based on the RS occurs within a first time window (measurement window), the UE may determine whether to transmit a first PUCCH on a PUCCH resource (associated with the first time window) after the first time window.

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

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

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

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

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

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

[0474] The wireless communication system 1 may utilize Multi Input Multi Output (MIMO). For example, one cell may be formed by one antenna / base station 10, or may be formed by multiple antennas / base stations 10. One [virtual] cell (which may be called, for example, a super cell) may be composed of multiple [virtual] cells (which may be called, for example, sub-cells). A super cell may correspond to a cell whose physical range is fixed, and a sub-cell may correspond to a cell whose physical range varies semi-statically / dynamically. In this case, the wireless communication system 1 may be called a cell-free system.

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

[0476] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band 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 be a frequency band higher than FR2.

[0477] Furthermore, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.

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

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

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

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

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

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

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

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

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

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

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

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

[0490] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," etc. in the present disclosure may be read interchangeably.

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

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

[0493] 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, 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 as DL-RS.

[0494] 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 the SS (PSS, SSS) and the PBCH (and DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as reference signals.

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

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

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

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

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

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

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

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

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

[0504] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0523] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), or the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0538] 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 a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

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

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

[0541] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, a cache, a main memory, or the like. The memory 1002 may store executable programs (program codes), software modules, and the like for implementing a wireless communication method according to an embodiment of the present disclosure.

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

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

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

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

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

[0547] Note that the devices included in the core network 30 (for example, network nodes that provide NFs) may also be realized by the above-described functional block / hardware configuration.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0562] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

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

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

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

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

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

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

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

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

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

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

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

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

[0575] Note that the physical layer signaling may be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be called an RRC message, such as an RRC connection setup message or an RRC connection reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

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

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

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

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

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

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

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

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

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

[0586] Furthermore, in this disclosure, terms such as "QCL," "QCL assumptions," "QCL relationships," "QCL type information," "QCL properties," "specific QCL type (e.g., Type A, Type D) properties," and "specific QCL type (e.g., Type A, Type D)" may be interchangeable.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. a receiver for receiving a reference signal; a control unit that, when a first event based on the reference signal occurs within a first time window, determines whether to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window, If the PUCCH resource overlaps with a specific period after transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window, the control unit cancels transmission of the first PUCCH.

2. The terminal according to claim 1 , wherein the specific period starts from the end of transmission of the specific signal.

3. The terminal of claim 1 , wherein the particular signal is transmitted based on the occurrence of a second event within a second time window different from the first time window.

4. The terminal according to claim 1 , wherein the specific signal includes any one of a PUCCH other than the first PUCCH, an arbitrary physical uplink shared channel (PUSCH), and a PUSCH triggered by a PUCCH within a requested period.

5. A wireless communication method for a terminal, comprising: receiving a reference signal; and determining whether to transmit a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window when a first event based on the reference signal occurs within the first time window; 10. A wireless communication method for a terminal, wherein the terminal cancels transmission of the first PUCCH when the PUCCH resource overlaps with a specific period after transmission of a specific signal, or when the transmission of the specific signal overlaps with the first time window.

6. a transmitter for transmitting a reference signal; a controller configured to control reception of a first physical uplink control channel (PUCCH) in a PUCCH resource after the first time window when a first event based on the reference signal occurs within the first time window, If the PUCCH resource overlaps with a specific period after transmission of a specific signal, or if the transmission of the specific signal overlaps with the first time window, the base station cancels transmission of the first PUCCH.

Images